Re: foo_input_gsf

Reply #25 – 2018-06-07 04:43:57

Right, try updating your copy of foo_input_gsf, I've included some new changes. Just note, the Git master I pull my changes from is a month newer than the latest stable release of mGBA.

Re: foo_input_gsf

Reply #26 – 2018-06-07 05:04:28

I updated my copy of foo_input_gsf, and now there are no sound bugs! Thank you very much! I do not know what was wrong, but it has been fixed. Again, thank you very much!

Re: foo_input_gsf

Reply #27 – 2018-07-01 23:42:14

Is there any way to get old versions of this plugin? 3.0.6 from your site and 3.0.7 from f2k plugin repo got nasty playback flaw with minigsf and samples in Super Robot Taisen A, 3.0.1 should be fine, since i am sure i was using it two years ago.
Just realized that you could fix it, i haven't seen anything like that in games other than SRT A.
By the way, this is how it should sound like: link to mp3
And that is how it sounds like on 3.0.6/.7: link to mp3

minigsf rip

Re: foo_input_gsf

Reply #28 – 2018-07-02 00:06:54

Use the linked gsf2rom tool in this topic, compare with the latest mGBA and with an actual console using a flash cartridge, if necessary. Anything that sounds different from an actual console is a bug, anything which is replicated by an actual console is correct behavior, and possibly a sign that a soundtrack needs to be re-ripped.

Re: foo_input_gsf

Reply #29 – 2018-07-04 10:59:13

Thank you for helping, it is a bad rip.

Re: foo_input_gsf

Reply #30 – 2018-07-05 00:16:21

Yeah, maybe check out hcs64.com and ask there if someone has re-optimized the rip to include all of the needed data?

Re: foo_input_gsf

Reply #31 – 2018-11-12 18:43:06

Is it possible to create a menu like what you made for GEP for your other components, or even have gsf use the game emu player's controls itself, provided both are available?

Re: foo_input_gsf

Reply #32 – 2018-11-13 00:02:35

It doesn't really make sense for most xSF formats, since they usually allocate channels dynamically, either through rotation or random order, so muting won't really work the way you expect. Except for GSF, where you can mute the chip channels, or completely mute the PCM output, without any fine grained control over individual PCM source channels. And USF, where you can happily mute the PCM output, but not the individual source channels.

Re: foo_input_gsf

Reply #33 – 2019-01-26 20:10:26

@kode54 After I updated the component, it is failing with Hime Kishi Monogatari - Princess Blue downloaded from http://gsf.joshw.info. Specifically, the first song after 3 seconds the noise channel stops playing. In the previous version that did not happen.

Re: foo_input_gsf

Reply #34 – 2019-01-26 20:15:59

Also, a question. Why the noise channel is playing weird beeps? For example, trainer defeated from Pokémon Sapphire.

Re: foo_input_gsf

Reply #35 – 2019-01-26 23:26:00

Simple. It doesn't work right. I need to revert an attempt to fix it, and make it louder on the previous fix. Please try the latest version.

Re: foo_input_gsf

Reply #36 – 2019-01-27 15:17:45

the latest 3.0.11 makes foobar2000 crash whenever I open GSF Decoder Preferences Page

Re: foo_input_gsf

Reply #37 – 2019-01-28 04:17:46

Downgrade to the newly uploaded backup of 3.0.7, and kindly forget about any future updates for any of my components, until Visual Studio Gets Its Shit Together. I changed nothing, but updated Visual Studio, and everything just Stopped Working, but only in Release builds, not Debug builds.

Re: foo_input_gsf

Reply #38 – 2019-01-29 03:54:45

I see you try to fix the crash but I still get 3.0.11 from the foobar2000 component repo. From your component page, I get 3.0.7.

Re: foo_input_gsf

Reply #39 – 2019-01-29 23:51:02

That was an oops. Everything should be up to date now.