Input/Other decoders (special format) from Japanese wiki
32bit 64bit and dark mode Support
Not my release
VGM input (foo_input_vgm): https://foobar2000.xrea.jp/?Input+64bit#c23b8887
NPNEZ input(foo_npnez): https://foobar2000.xrea.jp/?Input+64bit#n6048770
WSR input (foo_input_wsr): https://foobar2000.xrea.jp/?Input+64bit#f44897bc
HES input (foo_input_hes): https://foobar2000.xrea.jp/?Input+64bit#g2b7cb70
Game Emu Player (foo_gep): https://foobar2000.xrea.jp/?Input+64bit#fda85f32
Highly Experimental (PSF Decoder) (foo_psf): https://foobar2000.xrea.jp/?Input+64bit#tdc79eb8
GSF Decoder (foo_input_gsf): https://foobar2000.xrea.jp/?Input+64bit#wea78c0b
LazyUSF (USF Decoder) (foo_input_usf): https://foobar2000.xrea.jp/?Input+64bit#aada4e80
2SF Decoder (foo_input_2sf): https://foobar2000.xrea.jp/?Input+64bit#xd389d72
Highly Theoretical (SSF/DSF Decoder) (foo_input_ht): https://foobar2000.xrea.jp/?Input+64bit#y2752f52
----------
Components for foobar2000 v2.0 beta 32bit/64bit
https://foobar2000.xrea.jp/?Components+for+foobar2000+v2.0+beta+32bit/64bit
All we need is SID decoding.
Thanks for your comment. :-\
What I guess I meant is we also need SID decoding. Though that could be done if I just got off my own arse and did it myself :/
Thanks for your comment.
There are many more. it's up to the Developer.
https://www.foobar2000.org/components/author/kode54
Thanks for your comment.
There are many more. it's up to the Developer.
https://www.foobar2000.org/components/author/kode54
If there's really a demand for it, I'm willing to adopt the component and port it.
The source code link looks dead??
https://gitlab.com/kode54/foo_sid/-/commits/main
Plenty of other projects are still live, just not that one...
https://gitlab.com/users/kode54/projects
The source code link looks dead??
https://gitlab.com/kode54/foo_sid/-/commits/main
Plenty of other projects are still live, just not that one...
https://gitlab.com/users/kode54/projects
I still have a copy. Don't recall where I got it from. I think SourceForge.
i
:O The ones I see are all dead.
foo_sid is a component that plays SID and MUS files.
The old foo_sid component has been archived by kode54. This version:
- Is a 64-bit component that is compatible with foobar2000 v1.6.13 and v2.0 or later.
- Supports dark mode
URL: https://github.com/stuerp/foo_sid/
Download from the Releases (https://github.com/stuerp/foo_sid/releases) page.
Thanks pqyt.
:O The ones I see are all dead.
Before I knew it... :(
Thanks pqyt. Now moved entirely to x64 (including using my own dsp component which was ported to x64 yesterday. just needs moar testing)
Added on 2022-12-04
Highly Quixotic (foo_input_qsf): https://foobar2000.xrea.jp/?Input+64bit#a22622a1
Thanks pqyt. Now moved entirely to x64 (including using my own dsp component which was ported to x64 yesterday. just needs moar testing)
Looking forward to installing your x64 dsp component :)
foo_sid is a component that plays SID and MUS files.
The old foo_sid component has been archived by kode54. This version:
* Bug fix: MUS and MUS+STR files play again.
URL: https://github.com/stuerp/foo_sid/
Download from the Releases (https://github.com/stuerp/foo_sid/releases) page.
Would anyone be able to do a 64bit build of the foo_input_adplug component? I have tried compiling myself in Visual Studio by cloning the GIT repository at https://bitbucket.org/losnoco/foo_input_adplug/src/master/ with my limited understanding but am struggling to do so, and ended up losing my build VM as it got into such a mess. In short, I had all components compiling except PPUI, which seems to replace the old ATL-style approach, so never got as far as linking, and this was 32bit only - I didn't get as far as configuring for 64bit.
It's the last missing piece of the puzzle for my full 64bit setup, thanks to efforts already on this thread.
Since I am free now with getting out beta 2 of my own shit I *could* look at some components to port. :)
Since I am free now with getting out beta 2 of my own shit I *could* look at some components to port. :)
I'll go out on a limb and ask for v2 64-bit versions of foo_enhanced_spectrum_analyzer and foo_musical_spectrum.
Thanks for the work on foo_dsp_effect!
I'll go out on a limb and ask for v2 64-bit versions of foo_enhanced_spectrum_analyzer and foo_musical_spectrum.
Good luck with that. Those components were never open source and the chance of anyone rewriting replacements from scratch is somewhere between slim and none. :o :))
I think mudlord was probably offering to take on existing projects (such as the ones left behind by kode54) where a few minor changes are required for fb2k v2 and not a lot more.
Exactly.
Me and my big mouth :))
I'll go out on a limb and ask for v2 64-bit versions of foo_enhanced_spectrum_analyzer and foo_musical_spectrum.
Good luck with that. Those components were never open source and the chance of anyone rewriting replacements from scratch is somewhere between slim and none. :o :))
Slim does not mean none ;-) I'm in the process of attempting a rewrite. The animation engine works. However, I'm currently stuck on the FFT and the logarithmic distribution.
Slim does not mean none ;-) I'm in the process of attempting a rewrite. The animation engine works. However, I'm currently stuck on the FFT and the logarithmic distribution.
Thanks pqyt, and good luck!
I finally have a 64bit build of foo_input_adplug working. The changes have been so extensive that i've renamed it to foo_adplug instead to avoid conflicts with Kode54's 32bit version.
Source and x64 binaries attached, release notes below. It will build in VS2022 Pro with the Windows 8.1 and 7.0 SDKs, and XP v141 compiler(!). Works fine on Windows 11 22h2 x64. I can't maintain it as I don't have the time, unfortunately, anyone is welcome to pick it and run with it. I've removed a lot of the legacy bits which replicated stuff that is now done by Foobar2000 itself, and updated to the latest AdPlug from GitHub and exposed more of the AdPlug decoders. It will compile against the 2022-11-16 SDK.
I've made some AdLib purist changes, limiting the sample rates to those only the OPL2 and OPL3 implementations themselves.
2022-12-09 4:00 GMT - Mark P
- Based on the superb original work from Kode54.
- Renamed to foo_adplug.dll
Optimisations
- Removed the built-in tags database, this is now better handled through a plugin such as foo_external_tags.
- Removed the built in built-in resampler, this is now much better handled through built-in Foobar2000 capabilities.
- Removed the built-in 'Surround Sound' function, this is now much better handled through other Foobar plugins.
- Removed the standalone DOSBox core, this is now handled by AdPlug as WoodyOPL
- Removed the exclusion of .lds files
- Removed all the various sample rates, just leaving the 49516 and 49716 per
http://nerdlypleasures.blogspot.com/2018/01/opl23-frequency-1hz-ish-difference.html
- Re-enabled .adl file handing. It's not right, but it will at least allow you to play your songs.
- Tidied up the UI a little.
- Updated to the latest Foobar2000 SDK
- Enabled 64bit builds
- Made 'usable' in Visual Studio 2022 Professional
- Updated to the latest AdPlug from Git
- Added all the software OPL cores from AdPlug.
- Set the default core to Nuked OPL3 at 49716Hz
- ToDo:
- The UI handling is a messy hack based on the old ATLHelpers, can someone rebuild using the latest PPUI libraries and support dark mode?
- The adplug and libbinio libraries and the plugin itself needs to be built with the Windows XP compiler tools (v141_xp),
against the 7.0 SDK. This needs updating to something more modern and sustainable.
- The includes are a mess, they need putting at the correct paths.
- I haven't bothered getting anything other than x64 release builds working.
- The plugin builds to a .dll only, it is not packaged.
- The 'Jarek Burczynski' decoder only seems to render the left channel.
- The 'configure' link is missing from the Filters view.
First-time contribution, offered without any guarantees/warranties, feels good to give something back at least!
Tested with the Commander Keen IMF files, Fuzzy's World of Space Golf LDS files, and some RAD files.
I'll go out on a limb and ask for v2 64-bit versions of foo_enhanced_spectrum_analyzer and foo_musical_spectrum.
Good luck with that. Those components were never open source and the chance of anyone rewriting replacements from scratch is somewhere between slim and none. :o :))
Slim does not mean none ;-) I'm in the process of attempting a rewrite. The animation engine works. However, I'm currently stuck on the FFT and the logarithmic distribution.
Someone already did that but for DeaDBeeF, see https://github.com/cboxdoerfer/ddb_musical_spectrum
I considered porting this port back to foobar, but I'm not experienced enough and had no idea what I was doing. Hopefully this can serve as an apt enough resource for finishing it up.
I personally preferred the enhanced spectrum analyzer, but I'll take either over the default.
Added on 2022-12-10
NCSF Decoder 1.19 (foo_input_ncsf.dll): https://foobar2000.xrea.jp/?Input+64bit#pd49a4e7
Thx. I didn't know about this port. I'll have a look at it.
Done a new build of my foo_adplug component. Now at v1.1. Changes as follows.
2022-12-10 23:01 GMT - Mark P
- Enabled Support for Dark Mode
- All headers now sensibly organised.
- Now builds with the Visual Studio 2022 Compiler, against the Windows 10 SDK.
- All ATLHelpers hacks removed, now using default SDK files. UI handling now much more sane.
- All Build Configurations now working (x86, and x64, in Debug and Release modes).
- Renamed Equaliser to Filter
- Adds the copyright notices for the AdPlug library.
- Made the default WoodyOPL (DOSBox) as this has better seek behaviour.
- More UI tidying, now matches the native Foorbar2000 look and feel.
- Version is now 1.1
Downloads below.
Added on 2022-12-11
SNSF Decoder (foo_input_snsf9x): https://foobar2000.xrea.jp/?Input+64bit#x91448b2
SPU log decoder (foo_input_spu): https://foobar2000.xrea.jp/?Input+64bit#cdb932f5
Continued work on foo_adplug at https://hydrogenaud.io/index.php/topic,123432.0.html (https://hydrogenaud.io/index.php/topic,123432.0.html)
I'll be keeping that thread up to date from now on.
foo_input_hvl?
foo_input_org?
Added on 2022-12-18
GSF Decoder / VBA-M (viogsf) (foo_input_viogsf): https://foobar2000.xrea.jp/?Input+64bit#xffc95e7
Is it possible to compile Pxtone?
https://github.com/EterCyber/Foobar2000-Input-Pxtone
How about vgmstream plugin. Is it possible to make 64-bit version?
How about vgmstream plugin. Is it possible to make 64-bit version?
Since I've ported already 2 of kode54's components I'll give it a go. My first question is: how do I test it?
you can grab streamd or synthesized format music from HCS Forum (https://hcs64.com/mboard/forum.php?showthread=26929), it may be help.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is re-compiled version of foobar2000 component that is included in the vgmstream project. This version:
- Is a 64-bit component that is compatible with foobar2000 v1.6.13 and v2.0 or later.
This is a crude version that compiles and produces some output for some of streams I tried. The code still needs a lot of cleaning up before I release it. Only the 64-bit version is included.
*Edit* Hmm... apparently adding the file did not work.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is re-compiled version of foobar2000 component that is included in the vgmstream project. This version:
- Is a 64-bit component that is compatible with foobar2000 v1.6.13 and v2.0 or later.
This is a crude version that compiles and produces some output for some of streams I tried. The code still needs a lot of cleaning up before I release it. Only the 64-bit version is included.
*Edit* Hmm... apparently adding the file did not work.
The proof-of-concept component can be found at: https://github.com/stuerp/foo_input_vgmstream/releases
upon installing:
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
upon installing:
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It works only on foobar2000 2.0 64-bit for now.
pqyt: has the code by cboxdoerfer on github for a foo_musical_spectrum port (https://github.com/cboxdoerfer/ddb_musical_spectrum (https://github.com/cboxdoerfer/ddb_musical_spectrum)) been of any help so far in getting your own attempt closer to a trial release?
pqyt: has the code by cboxdoerfer on github for a foo_musical_spectrum port (https://github.com/cboxdoerfer/ddb_musical_spectrum (https://github.com/cboxdoerfer/ddb_musical_spectrum)) been of any help so far in getting your own attempt closer to a trial release?
I've downloaded a copy but haven't had the time to look at it yet. Thx for the link. Real-life stuff, etc...
upon installing:
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It works only on foobar2000 2.0 64-bit for now.
I am on foobar2000 2.0 beta 17 64-bit.
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder.
edit: just tested and it actually installs but it's a debug build which you have to accept a prompt for. Not ideal.
edit2: and of course I have Visual Studio installed so I'll have the debug C++ runtime dlls installed that most people won't
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is re-compiled version of foobar2000 component that is included in the vgmstream project. This version:
- Is a 64-bit component that is compatible with foobar2000 v1.6.13 and v2.0 or later.
This is a crude version that compiles and produces some output for some of streams I tried. The code still needs a lot of cleaning up before I release it. Only the 64-bit version is included.
*Edit* Hmm... apparently adding the file did not work.
foobar2000 2.0 x64 beta 17:
Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000.
not work, but I'm still excited, thanks for your work.
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder.
edit: just tested and it actually installs but it's a debug build which you have to accept a prompt for. Not ideal.
edit2: and of course I have Visual Studio installed so I'll have the debug C++ runtime dlls installed that most people won't
You're right. Seems like a bug in my PowerShell script when only a 64-bit build is available. I'll fix that tonight.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is re-compiled version of the oobar2000 component that is included in the vgmstream project. This version:
- Is a 64-bit component that is compatible with foobar2000 v2.0 or later.
This is a crude release build that compiles and produces some output for some of streams I tried. Only the 64-bit version is included.
Component identification should be "vgmstream 0.1.0.1"
Download available on the Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page.
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It failed because the developer just missed this part of marc2k3's post:
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder
Unzip pqyt's vgmstream 0.1.0.1 package from github, extracting the "x64" subfolder; then make a new zip consisting of just the file content of the x64 folder--NOT the folder itself. The component will then load into Foobar v2 64-bit without error--I just tried it.
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It failed because the developer just missed this part of marc2k3's post:
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder
Unzip pqyt's vgmstream 0.1.0.1 package from github, extracting the "x64" subfolder; then make a new zip consisting of just the file content of the x64 folder--NOT the folder itself. The component will then load into Foobar v2 64-bit without error--I just tried it.
Embarrasing. I admit that I don't test the actual deployment of the component. It's installed in my test setup during the build. It's weird that foobar2000 uses a different strategy to unpack the content of a component when only x64 files are present.
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It failed because the developer just missed this part of marc2k3's post:
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder
Unzip pqyt's vgmstream 0.1.0.1 package from github, extracting the "x64" subfolder; then make a new zip consisting of just the file content of the x64 folder--NOT the folder itself. The component will then load into Foobar v2 64-bit without error--I just tried it.
I've updated the binary of the v0.1.0.1 release. It should install now without any zip-file hacking.
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It failed because the developer just missed this part of marc2k3's post:
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder
Unzip pqyt's vgmstream 0.1.0.1 package from github, extracting the "x64" subfolder; then make a new zip consisting of just the file content of the x64 folder--NOT the folder itself. The component will then load into Foobar v2 64-bit without error--I just tried it.
I've updated the binary of the v0.1.0.1 release. It should install now without any zip-file hacking.
It worked ! except xbox 360 xma. Thank you
EDIT: Fixed
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It failed because the developer just missed this part of marc2k3's post:
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder
Unzip pqyt's vgmstream 0.1.0.1 package from github, extracting the "x64" subfolder; then make a new zip consisting of just the file content of the x64 folder--NOT the folder itself. The component will then load into Foobar v2 64-bit without error--I just tried it.
I've updated the binary of the v0.1.0.1 release. It should install now without any zip-file hacking.
It worked ! except xbox 360 xma. Thank you
Can you point me to an example that does not work?
Still same issue with "vgmstream 0.1.0.1" on foobar2000 2.0 beta 17 64-bit.
"Failed to load DLL: foo_input_vgmstream.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000."
It failed because the developer just missed this part of marc2k3's post:
The packaging of the component looks wrong. The archive should only contain an x64 folder if 32bit and 64bit dlls are included. When it's 64bit only, it should go at the root without the folder
Unzip pqyt's vgmstream 0.1.0.1 package from github, extracting the "x64" subfolder; then make a new zip consisting of just the file content of the x64 folder--NOT the folder itself. The component will then load into Foobar v2 64-bit without error--I just tried it.
I've updated the binary of the v0.1.0.1 release. It should install now without any zip-file hacking.
It worked ! except xbox 360 xma. Thank you
Can you point me to an example that does not work?
https://vgm.hcs64.com/?site=xbox
Ex: Xbox Burnout 3: Takedown EATrax files
https://vgm.hcs64.com/?site=x360
Red Dead Redemption \ Red Dead Redemption - Undead Nightmare files
I've tested some format, and here is the result.
Platform: format: result: Game
3DS: wem: Unable to open item for playback (Missing ACM codec): Metroid Federation Force
PS2: svag: Unable to open item for playback (Unsupported format or corrupted file): Silent Hill 2
PSP: at3: NO SOUND: Silent Hill Origins
PSP: oma: Unable to open item for playback (Unsupported format or corrupted file): Silent Hill Origins
Switch: lopus: NO SOUND: Axiom Verge
Xbox 360: xma: NO SOUND: HALO 3 ODST
Xbox 360: fsb: NO SOUND: HALO Combat Evolved Anniversary
all these stream can be found in
hcs64 forum (https://hcs64.com/mboard/forum.php?showthread=26929)
I've tested some format, and here is the result.
Platform: format: result: Game
3DS: wem: Unable to open item for playback (Missing ACM codec): Metroid Federation Force
PS2: svag: Unable to open item for playback (Unsupported format or corrupted file): Silent Hill 2
PSP: at3: NO SOUND: Silent Hill Origins
PSP: oma: Unable to open item for playback (Unsupported format or corrupted file): Silent Hill Origins
Switch: lopus: NO SOUND: Axiom Verge
Xbox 360: xma: NO SOUND: HALO 3 ODST
Xbox 360: fsb: NO SOUND: HALO Combat Evolved Anniversary
all these stream can be found in
hcs64 forum (https://hcs64.com/mboard/forum.php?showthread=26929)
Thx. I tracked the Xbox 360 EAS problem down to the ffmpeg renderer that vgmstream uses. The sample buffer is never updated and hence produces no sound. The 'native' codecs seem to work though. Got some debugging to do.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Fixed the ffmpeg interface
This build plays all the test samples submitted to the forum.
Component identification should be "VGMStream Player 0.1.0.2"
Download available on the Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page.
Merry Christmas
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Fixed the ffmpeg interface
This build plays all the test samples submitted to the forum.
Component identification should be "VGMStream Player 0.1.0.2"
Download available on the Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page.
Merry Christmas
Many thanks to you, pqyt.
tested again, all worked well except the wem format. the error message is gone but NO SOUND.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Fixed the ffmpeg interface
This build plays all the test samples submitted to the forum.
Component identification should be "VGMStream Player 0.1.0.2"
Download available on the Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page.
Merry Christmas
Many thanks to you, pqyt.
tested again, all worked well except the wem format. the error message is gone but NO SOUND.
Do you have an example of a wem file?
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Fixed the ffmpeg interface
This build plays all the test samples submitted to the forum.
Component identification should be "VGMStream Player 0.1.0.2"
Download available on the Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page.
Merry Christmas
Many thanks to you, pqyt.
tested again, all worked well except the wem format. the error message is gone but NO SOUND.
Do you have an example of a wem file?
Never mind. I misread your post. The Metroid .wem files play just fine on my system.
for example
3DS: Metroid Prime Federation Force: streamedfiles 00052.wem
3DS: Metroid Prime Blast Ball: blastballeshop 00162.wem
and all other wem play NO SOUND
btw: original kode54's component can't play wem too, says 'Unable to open item for playback (Missing ACM codec)'
maybe an old issue in original code.
for example
3DS: Metroid Prime Federation Force: streamedfiles 00052.wem
3DS: Metroid Prime Blast Ball: blastballeshop 00162.wem
and all other wem play NO SOUND
btw: original kode54's component can't play wem too, says 'Unable to open item for playback (Missing ACM codec)'
maybe an old issue in original code.
for example
3DS: Metroid Prime Federation Force: streamedfiles 00052.wem
3DS: Metroid Prime Blast Ball: blastballeshop 00162.wem
and all other wem play NO SOUND
btw: original kode54's component can't play wem too, says 'Unable to open item for playback (Missing ACM codec)'
maybe an old issue in original code.
The only explanation I have is that the archives changed content over time. I tried the following ones and they do not contain the files you mention. All the other files play just fine:
Metroid - Samus Returns (2017-09-15)(Mercury Steam)(Nintendo)[3DS].7z
Metroid Prime - Blast Ball (2016-07-21)(Next Level)(Nintendo)[3DS].7z
Metroid Prime - Federation Force (2016-08-19)(Next Level Games)(Nintendo)[3DS].7z
for example
3DS: Metroid Prime Federation Force: streamedfiles 00052.wem
3DS: Metroid Prime Blast Ball: blastballeshop 00162.wem
and all other wem play NO SOUND
btw: original kode54's component can't play wem too, says 'Unable to open item for playback (Missing ACM codec)'
maybe an old issue in original code.
for example
3DS: Metroid Prime Federation Force: streamedfiles 00052.wem
3DS: Metroid Prime Blast Ball: blastballeshop 00162.wem
and all other wem play NO SOUND
btw: original kode54's component can't play wem too, says 'Unable to open item for playback (Missing ACM codec)'
maybe an old issue in original code.
The only explanation I have is that the archives changed content over time. I tried the following ones and they do not contain the files you mention. All the other files play just fine:
Metroid - Samus Returns (2017-09-15)(Mercury Steam)(Nintendo)[3DS].7z
Metroid Prime - Blast Ball (2016-07-21)(Next Level)(Nintendo)[3DS].7z
Metroid Prime - Federation Force (2016-08-19)(Next Level Games)(Nintendo)[3DS].7z
Thanks for remind me of archives updates.
you're right. it's the problem about wem files I have. maybe bad dump.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Added x86 version for foobar2000 v2.0.
- Added support for dark mode.
- Cleaned up the preference page a little bit.
- Switched to a clean ffmpeg 4.4.1 build using vcpkg.
- Converted libatrac9 to a link library.
Component identification is "VGMStream Player 1.0.0.0".
Download available on the GitHub Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page and the foobar2000 component repository (https://www.foobar2000.org/components/view/foo_input_vgmstream).
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Added x86 version for foobar2000 v2.0.
- Added support for dark mode.
- Cleaned up the preference page a little bit.
- Switched to a clean ffmpeg 4.4.1 build using vcpkg.
- Converted libatrac9 to a link library.
Component identification is "VGMStream Player 1.0.0.0".
Download available on the GitHub Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page and the foobar2000 component repository (https://www.foobar2000.org/components/view/foo_input_vgmstream).
Great work. Happy New Year.
foo_input_vgmstream is a component for playing streamed (prerecorded) video game audio.
This is a re-compiled version of the foobar2000 component that is included in the vgmstream project. This version:
- Added x86 version for foobar2000 v2.0.
- Added support for dark mode.
- Cleaned up the preference page a little bit.
- Switched to a clean ffmpeg 4.4.1 build using vcpkg.
- Converted libatrac9 to a link library.
Component identification is "VGMStream Player 1.0.0.0".
Download available on the GitHub Releases (https://github.com/stuerp/foo_input_vgmstream/releases) page and the foobar2000 component repository (https://www.foobar2000.org/components/view/foo_input_vgmstream).
Dear pqyt.
There is a small glitch when I "Get updates" from component repo.
It keeps reminds me New version 'v1.0.0.0' while I'm already in 1.0.0.0
Dear pqyt.
There is a small glitch when I "Get updates" from component repo.
It keeps reminds me New version 'v1.0.0.0' while I'm already in 1.0.0.0
Weird. There's nothing I can do about it. I put a version resource in my components but most don't. So foobar2000 must use a different mechanism to detect updates.
@peter, can you shed some light on this, please?
Your component version looks fine - looks like it's the v prefix on the website causing issues.
BTW, this is the macro typically used inside components for declaring the version...
https://github.com/marc2k3/foobar2000-sdk-2/blob/6d46283a0c7c2a5537c5454fc25888defef9fa5f/foobar2000/SDK/componentversion.h#L49-L62
Your component version looks fine - looks like it's the v prefix on the website causing issues.
BTW, this is the macro typically used inside components for declaring the version...
https://github.com/marc2k3/foobar2000-sdk-2/blob/6d46283a0c7c2a5537c5454fc25888defef9fa5f/foobar2000/SDK/componentversion.h#L49-L62
That's the macro I always use. I'll update the component registration on the website.
Hello, pqyt.
glad to see VGMStream Player v1.1.0.0 released.
There's a small problem on component's repo,
Supported processor architecture: x86 32-bit
foobar2000 v2.0 x64 can not update this component online.
manual install/update is ok.
I noticed that too. Those architectures are detected during upload of the component by the portal. It's not something I can configure. I think
@Peter is aware of the bug.
I'll try removing and uploading again.
Update: re-uploading did the trick.
vgmstream plugin r1810-120-g36f4dfea (foo_input_vgmstream) (2023-02-13) 32/64bit fb2k v2.0 Support
https://vgmstream.org/ (nightly build)
Home: https://github.com/vgmstream/vgmstream
・Add foo_input_vgmstream x64 SDK + automated build (2023-02-12)
・usage guide: https://github.com/vgmstream/vgmstream/blob/master/doc/USAGE.md#foo_input_vgmstream-foobar2000-plugin
glad to see x64 is out. :)) :)) :))
HivelyTracker decoder.
https://www.foobar2000.org/components/view/foo_input_hvl
Organya ("Cave Story") decoder
There exist no modern reincarnations of foo_input_mdx and foo_input_s98?
PMD Decoder (https://www.foobar2000.org/components/view/foo_input_pmd) plays PMD files.
PMD Decoder (https://www.foobar2000.org/components/view/foo_input_pmd) plays PMD files.
Is this a reply to my post above? It seems that PMD decoder can't play *.s98 files, that foo_input_s98 can play. Samples - https://www.dropbox.com/scl/fi/6l3pevu82upzt7gfvdljv/S98.zip?rlkey=qegb97tm5qesd2vo2li2ak7l9&dl=1. foo_input_s98 - http://www.vesta.dti.ne.jp/~tsato/arc/foo_input_s98_090419.7z
PMD Decoder (https://www.foobar2000.org/components/view/foo_input_pmd) plays PMD files.
Is this a reply to my post above? It seems that PMD decoder can't play *.s98 files, that foo_input_s98 can play. Samples - https://www.dropbox.com/scl/fi/6l3pevu82upzt7gfvdljv/S98.zip?rlkey=qegb97tm5qesd2vo2li2ak7l9&dl=1. foo_input_s98 - http://www.vesta.dti.ne.jp/~tsato/arc/foo_input_s98_090419.7z
You're right. .s98 is a different format. I was too quick to respond. But I'm reading up on those format albeit slowly because of most of it is in Japanese.
One VGM input can play .s98 two geting this error on the plugins from the first post
"Failed to load DLL: foo_input_2sf.dll
Reason: Not a valid Win32 application.
Failed to load DLL: foo_input_usf.dll
Reason: Not a valid Win32 application.
Failed to load DLL: foo_input_spu.dll
Reason: Not a valid Win32 application.
Failed to load DLL: foo_input_qsf.dll
Reason: Not a valid Win32 application.
"
Supports only 64bit.
32bit
https://foobar2000.xrea.jp/?Input#yd77854d
I am using the 64 bit build so I confused. Fixed windows .rar suport sucks 7zip fixed it
Oh it's true. Sorry.
Please use 7-Zip etc.
7-Zip
https://7-zip.org/
components
32bit 64bit Support.
VGM input v0.30 beta 3 (foo_input_vgm) x86_32 x86_64 (2023-11-26)
https://ux.getuploader.com/foobar2000/download/240
----
How to download: A small button above the image 「ダウンロード」click, Next Page > A small button above the image 「Download Now」click
PSF decoder / Mednafen 1.27.0-UNSTABLE v1.3 (foo_input_mdfnpsf) x86_32 x86_64
https://ux.getuploader.com/foobar2000/download/241
How to download: A small button above the image 「ダウンロード」click, Next Page > A small button above the image 「Download Now」click
foo_sid is a component that plays SID and MUS files.
The old foo_sid component has been archived by kode54. This version:
* Bug fix: MUS and MUS+STR files play again.
URL: https://github.com/stuerp/foo_sid/
Download from the Releases (https://github.com/stuerp/foo_sid/releases) page.
Sorry for the random/necro reply, but I noticed that any config that isn't reSIDfp with the filter 6581 set to 1.0 & the 8580 filter set to 0.0 has a artifacts or does not emulate properly, outputs a different reading on every play.
Don't know if this is a kode64 era bug or introduced in this port, or if it's even an expected result of the other configurations, but it's worth mentioning since i took a while to figure out the non-broken setting.
foo_sid is a component that plays SID and MUS files.
The old foo_sid component has been archived by kode54. This version:
* Bug fix: MUS and MUS+STR files play again.
URL: https://github.com/stuerp/foo_sid/
Download from the Releases (https://github.com/stuerp/foo_sid/releases) page.
Sorry for the random/necro reply, but I noticed that any config that isn't reSIDfp with the filter 6581 set to 1.0 & the 8580 filter set to 0.0 has a artifacts or does not emulate properly, outputs a different reading on every play.
Don't know if this is a kode64 era bug or introduced in this port, or if it's even an expected result of the other configurations, but it's worth mentioning since i took a while to figure out the non-broken setting.
I'll have a look at it because I have to upgrade to the latest libsidplayfp anyway.
v1.95.0.0, 2024-04-10, foo_sid
* Upgraded libsidplayfp to 2.7.0.
You can download it from the Component (https://www.foobar2000.org/components/view/foo_sid+%28x64%29) repository or from GitHub (https://github.com/stuerp/foo_sid/releases/tag/v1.95.0.0).
2SF decoder / DeSmuME v0.9.9 0.24 (foo_input_vio2sf) 2024-04-27
https://foobar2000.xrea.jp/up/files/up1957.7z