Post Reply 
Transcoding probably not working
30-03-2025, 22:59
Post: #11
RE: Transcoding probably not working
Transcoding a radio stream from JPLAY is now working. No success so far with foobar. Trying to install upnp Browser I get the error:

Could not load component "foo_upnp.dll": This component was built for a different processor architecture.
Find all posts by this user
Quote this message in a reply
31-03-2025, 10:28
Post: #12
RE: Transcoding probably not working
I am pleased to hear you now have MinimStreamer transcoding of radio streams working with JPLAY.

For help with getting foobar2000 with the foo_upnp component configured and working correctly, I suggest you post to the foobar2000 support forums.
Find all posts by this user
Quote this message in a reply
02-04-2025, 05:42
Post: #13
RE: Transcoding probably not working
After perusing the HydrogenAudio forums it appears foobar is not interacting with MinimServer at all. I can stop MinimServer on my NAS and foobar still plays music files on the NAS just fine. The foobar upnp plugin sends the music stream to whichever upnp renderer I select.

There is an older, no longer supported, foobar upnp component that probably would work as a control point with MinimServer, but it appears 32-bit components are no longer supported by the current foobar and give the error I reported above.
Find all posts by this user
Quote this message in a reply
02-04-2025, 10:30
Post: #14
RE: Transcoding probably not working
Thanks for confirming the cause of this problem.

I am using an older version of foobar2000 (1.4.4) with plugins foo_upnp (0.99.49) and foo_out_upnp (1.3.1). With this combination I am able to browse my MinimServer library and use MinimStreamer transcoding for files and radio streams.
Find all posts by this user
Quote this message in a reply
03-04-2025, 09:05
Post: #15
RE: Transcoding probably not working
(02-04-2025 05:42)Lavcat Wrote:  There is an older, no longer supported, foobar upnp component that probably would work as a control point with MinimServer, but it appears 32-bit components are no longer supported by the current foobar and give the error I reported above.
32-bit components can't be used with 64-bit foobar, but 32-bit foobar is still being maintained (currently v2.24.3).
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)