![]() The advantage for me to having JRSS enabled is so if I do play a multichannel recording I at least get playback that sounds reasonably correct compared to just playing the L and R channels from the multichannel with no mixing and no subwoofer getting mixed in. The stereo signal passes right through and doesn't get changed or altered. Sometimes those problems cause applications to crash.Ĭlick to expand.For all of my stereo recordings the JRSS mixer does nothing, does no harm. And it causes problems with Windows media player programs. It is very easy to end up with very long file names and very long path names with classical. Too much legacy code and legacy APIs around still being used. Microsoft supposedly fixed that problem back in 2016 (finally), but not really. I'm quite annoyed that it's 2022 and I still run into problems with Windows programs not correctly handling file paths that are longer than 260 characters. And something for me to refer back to when I need to set up a new Windows computer for audio use. ![]() ![]() To help me jog my memory about the tweaks and optimizations I do. I don't have all these things written down in one place. Things I do to help any Windows program to better behave if they might have to process long file name paths. I'm just using this thread now as a repository for general things I do to help make Windows media player programs more stable and better able to handle long file names.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |