VGMPlay / in_vgm

[Dekyo-NO]

Alpha 2 of foo_input_vgm was uploaded. For more details see the newly added "foo_input_vgm_EN.txt" file.

[LuNiney]

Alpha 4 was posted but... everything points to the dev not continuing development on it

[Dekyo-NO]

Actually, the dev put that message since Alpha 1.

[blitzlunar]

Beta1 released now, seemingly.
I'm just going to wait a little while longer until this flurry of updates concludes. I hope the dev knows how much this is appreciated by us fb2k users.

[Dekyo-NO]

YEAH! Core emulation selection and their options are now implemented!

[(Jazz) Jackalope]

The 0 and 1..9 playback shortcuts work fine for unlooped vgms, but they do not seem to work for looped ones... okay, no, it just started playing again, but it took anywhere from 30 seconds to a minute. I have infinite loops set, but I attempted this immediately after loading the song. (Don't remember which number I hit... could be 3, 7, or 9.) The song I chose is 11 seconds long.

This may be a known problem or unavoidable, but I thought I'd mention it.

[ValleyBell]

It is a bit of an unfortunate user interface choice: 0..9 seek to a certain position in the complete song that includes all loops.

If you have a 30 second song with a 20 second loop, it plays for 50 seconds total. However the displayed time goes only from 0 to 30s and then restarts at 10s.
So if you press "5", it goes to 50% -> 50s*0.5 = 25s -> display: 0:25.00 (1st loop).
So if you press "8", it goes to 80% -> 50s*0.8 = 40s -> display: 0:20.00 (2nd loop).

For a future version I intend to add an option to just show the "total time" instead of the "time inside the VGM".

[Dekyo-NO]

Just here to let you know that foo_input_vgm 0.30 beta 2 was released.

[Davedson]

The funniest part is that at this point it's actually much more preferable to use the Japanese foobar2000 plug-in rather than the standalone tool, since it's outdated as all hell while the Japanese foobar2000 plug-in is based on the latest (at the time of writing this) libvgm GitHub commit, bringing a ton of bug fixes, changes and additions still not present in the standalone tool, especially the ones concerning the OPL4 playback, just read the libvgm's commit history on GitHub and you'll understand the full scale of the problem.

[kirishima]

I'm a bit surprised that my old post from how many years ago is still the link in the 1st post for foo_input_vgm, considering how other users have already stepped up to report on new versions of the plugin.

[ValleyBell]

I updated the first post in the topic.

[Dekyo-NO]

foo_input_vgm 0.30 beta 3 is out, check it in the Japanese foobar2000 component repository.

[ValleyBell]

The end of the year is near, so let's do a new release, you we can begin the next year with improved VGM listening.

VGMPlay 0.51.1 (Win32 and Win64 binary) and in_vgm 0.51.1 (Win32 DLL, ANSI and Unicode version).
Source code can be obtained from GitHub: VGMPlay, in_vgm

The most important updates are:

• support "Mikey" chip used by Atari Lynx
• fixed old v1.00/1.01 VGMs not playing YM2612 and YM2151 data
• added per-channel padding for NES APU
• fixed missing panning in Apple II "Ultima" series VGM rips
• various emulation fixes and improvements
• [VGMPlay] added playback speed control (keys are: { [ ] and })
• [VGMPlay] added "TimeDisplayStyle" option, which lets you adjust how playback time is shown

Happy listening!

[ValleyBell]

Please redownload the players. Links are the same.
I accidentally broke playback speed controls due to a copy-paste error.

[Dekyo-NO]

foo_input_vgm v0.30 beta 4 released.