NSFPlay 2.2

[Eugene.S]

I've found a bug:
http://youtu.be/9UpEN84BFrQ

[koitsu]

I've found a bug:
http://youtu.be/9UpEN84BFrQ

Can't reproduce this on my XP SP3 system; all pulldowns show their proper contents.

[Eugene.S]

I have this problem both on
Windows XP x64 SP2 eng with Server 2003 MUI (OS version 5.2.3790)
and Windows XP SP3 rus (OS version 5.1.2600)

I've switched to Win9x-like windows classic theme, but problem still here.

[rainwarrior]

That's really odd Eugene.S, the style of the combo box is supposed to have "integral height" that automatically sizes the drop down to the list. I can't duplicate the problem, myself, but I tried increasing the height value on the box (even though it's not supposed to be used). Redownload this and tell me if the problem persists:

-- removed link --

arfy, I'll see what I can dig up, re: patched NSFs.

Edit: jrlepage fixed all of robokabuto's old N163 NSFs: https://dl.dropboxusercontent.com/u/340 ... kabuto.rar

I don't know what other N163 NSFs are out there from the period before we learned that error. If you find some you can let me know, I might just write a python script to fix them quickly if there's more than a few. (Possibly there are others that aren't PPMCK, which will require some debugging to fix.)

[Eugene.S]

https://dl.dropboxusercontent.com/u/883 ... ay23b4.zip
Yes, new build works fine now.
Old build work fine also, when i've updated old nsfplug_ui.dll to new from 17.07.2013

[rainwarrior]

Good! Yeah, the only thing that changed was the ui DLL, so that's why you can transplant it.

[Eugene.S]

I think the DMC pop reducer of NSFplay need to be more soften.

I've recorded DMC from Batman - first level.
Nestopia, puNES and NotSoFatso pop-reducers work more soften,
but NSFPlay still have clicky sound.
nestopia
NotSoFatso
nsfplay

[arfy]

@rainwarrior. Thanks for the link to the fixed n163 nsf's. some nice goodies in there I'd almost forgotten about, especially Ligaya! Genuine nsf trance, probably the first example of such. Anyway, unless there's other common n163 drivers other than ppmck and famitracker in use today, then I suspect the only other n163 nsf's are from namco themselves. I was also thinking of writing a general n163 patcher, probably in either PureBasic or python. Now if only someone was doing for the gameboy what your doing for the nes, then I'd be very happy.

[rainwarrior]

Eugene.S pop reduction is an option, it is not something that happens by default.

The option "Enable $4011 register", on by default. If you uncheck this all pops caused by $4011 writes will disappear.

There is another option called "Eliminate clicking noise", which does not disable the $4011 register, but removes its sound while preserving the nonlinear mix it normally causes.

Toggling either of these options will remove the DMC clicks.

[Eugene.S]

Thank you, eliminate clicking noise works very good.

But it have some problem, when enabled:
Look at 2:41 and 2:05 please.

Here is my in_yansf.ini (wait 10 second to download)

[rainwarrior]

Agh, it looks like the counter-offset I'm using to suppress the $4011 pops eventually overflows if the DPCM direction goes opposite the $4011 too many times. I'll try to see if I can think of a way to fix it. If it's a DPCM heavy track you might just used the disable $4011 option instead, because the nonlinear mix won't be an issue.

[tepples]

How leaky is your counter-offset?

[rainwarrior]

It doesn't leak at all, that's why it eventually overflows. I'm going around it a different way now, though.

[rainwarrior]

Okay, I was going to try to inject the counter-pop into the highpass filter and let it gracefully remove the offset, but this solution was becoming too much to change for the release.

So, for now I just put in a very, very simple linear fade to prevent overflow. Not ideal, but it seems good enough for the time being.

Eugene.S please verify that it no longer overflows:
-- removed link --

[Eugene.S]

Eugene.S please verify that it no longer overflows:
https://dl.dropboxusercontent.com/u/883 ... ay23b5.zip

Hmm, this build still buzz.
Can you reproduce this problem on your machine?

ps: this build labeled as "beta 4"