INTERACT FORUM
More => Old Versions => JRiver Media Center 22 for Windows => Topic started by: mwillems on May 19, 2016, 02:13:11 pm
-
I was perusing the new MC22 features thread (I keep seeing neat new features added), but I was curious: what's "Sox"? Is it the resampling algorithm? Either that, or maybe a new Video scaler so demanding that the heat from your video card will warm your feet from across the room ;D
Either way, sounds neat.
-
I was perusing the new MC22 features thread (I keep seeing neat new features added), but I was curious: what's "Sox"? Is it the resampling algorithm?
That's what I thought too.
-
(https://i.ytimg.com/vi/Fu4lCvf4Fnw/hqdefault.jpg)
-
A warm winter awaits.
-
A warm winter awaits.
Winter is coming, get your Sox upgraded ;D
-
I plan on washing mine.
-
If we are talking more flexibility regarding resampling algorithms and making all these options available to the video side of things as well I am :)
-
Just a little note that I got SoX working today.
It was transcendent.
So, something to look forward to in MC22.
-
http://sox.sourceforge.net/ (http://sox.sourceforge.net/) perhaps. . . ?
Spike
-
@Matt:
Great news, happy to hear this in 22.
BR
Erich
-
Just a little note that I got SoX working today.
It was transcendent.
So, something to look forward to in MC22.
And all those silly users that say we just sit on our haunches with audio features!
Does that mean you plan to replace the existing transcoder engine by Sox?
Are your existing transcoders hand coded?
A shift to an external utility makes a lot of sense. And Sox is indeed very good and very fast.
Does this mean that we can look forward to new destination formats on DLNA / UPnP push in addition to the current MP3, L16 and L24 options?
Does this mean we can finally get proper Seek() support in DLNA / UPnP push?
-
Does that mean you plan to replace the existing transcoder engine by Sox?
Are your existing transcoders hand coded?
A shift to an external utility makes a lot of sense. And Sox is indeed very good and very fast.
Does this mean that we can look forward to new destination formats on DLNA / UPnP push in addition to the current MP3, L16 and L24 options?
Does this mean we can finally get proper Seek() support in DLNA / UPnP push?
This is all entirely unrelated to what this is about. It only uses SoX Resampling to optionally replace MCs current resampler.
No idea where you even get the DLNA reference, as SoX is not related to such technologies.
-
No idea where you even get the DLNA reference, as SoX is not related to such technologies.
Hi Hendrik,
The DLNA reference is because your current audio transcoder does not support seek to a time position ahead of the current output buffer size. So you have to wait until the transcoder run has finished before your HTTP server could support a seek on that part of the buffer file. By contrast, if you used the SoX transcoder instead of the MC transcoder you can simply call SoX with the -T time offset switch, to start a transcoder run at a specific time offset from the start of the track. Then you can pipe the output of SoX straight into your HTTP server output stream, and therefore support seek properly.
Believe me, if you think I am an idiot, I can assure you that I am not. I know very well how SoX works, and I have used it myself in my own Whitebear UPnP Media Server. If you want help on this, I can advise. I have been pushing for JRiver to fix this issue for years. SoX finally gives you the tools to do it properly, and rather easily..
-
Sox is available in MC22. You can download from the MC22 board.
-
Please use this thread now:
http://yabb.jriver.com/interact/index.php?topic=105946.msg736952#msg736952