 
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
|
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
71.210.236.132
In Reply to: RE: Using JRiver 19 to convert standard 44.1/16 wav to DSD posted by Mag4Life on July 12, 2014 at 17:51:06
I would highly recommend that option. I use it to feed my Resonessence DAC. IME it easily betters any other upsampling mode or filter (the DAC has 6). I also upsample high rez files. I did encounter significant softening and bass bloat when using 2X DSD though. I think it may be reaching a limit with the cable or perhaps the computer. I use an ASUS Gamer laptop with an Intel i7 chip and SSD. I played it for a meeting of the Sante Fe Audio Society and it was agreed that it sounded best in that mode. We left it in that mode for the remainder of a 4 hour meet. It only took about 20 minutes to reach the conclusion.
If you go that route be sure to limit the garbage running in the background on the computer. It takes a bit of computing power and speed to "do the math". Best of all, you can use the J River trial period to see how it will work (or not) for you.
Tony
Follow Ups:
Here is a thread that compares JR MC19, Foobar + SACD, and HQ Player
Thanks for the link. I'd missed this thread. I can confirm that HQPlayer requires careful selection of filters and other configuration settings to get good results.
One thing that I didn't understand was the comment that the lack of an idle core might lead to a timing error on a USB packet, implying that these go out every millisecond under software control. Is this correct? It seems more likely that the 1 msec isochronous packets are timed by the USB controller hardware which at least double buffers. Therefore if the CPU were less than 1 msec late the next packet would still go out on time. (It could be that it doesn't work that way with some drivers, if so I would consider that a bug.) In the case of the USBPAL driver for Windows that came with my Mytek if the processor can't keep up then then the error counters will increment. Usually I can hear a glitch anytime this happens, something that seldom happens when I am just listening to music, but happens frequently when using HQPlayer with room correction if I attempt to surf the web, etc... It is possible to reduce the frequency of this happening by increasing the number of these 1 msec buffers using the USBPAL control panel. The choices are 1, 2, 4, 8, 12, 16 msec. As expected, I found that lower numbers produced more frequent glitches but better sound quality between glitches, also the glitches were usually harder to hear when they happened.
I do not like the idea of trying to tune a system where there is no access to the necessary documentation, e.g. logic diagrams for the USB hardware and source code for the driver. With this information most questions about how the system really works could be immediately answered, rather than relying on guess work and speculation.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
Hi Tony,
I was just speculating on an explanation why the sound would be so screechy but no dropouts
Anyway changing the BIOS setting of the clock speed from 2.4 GHz to auto clock speed ranging from 1.8 to 3.2 GHz allows the i5 3470 to play Polysinc when converting 24/192 to DSD256 with no dropouts and screeching
Are you doing room correction with HQ Player with DSD native files ?
Best Regards
Ed
I have an older Intel core i5 and a Mytek DAC that goes up to DSD128. I use HQPlayer to do room correction on DSD64 without downsampling, but I run out of CPU if I try to output at DSD128. I can do room correction up to 352.8 and output the result at DSD128. (I use poly-sinc-shrt-mp and DSD 7.) I can hear my CPU fan on warm days, so I don't normally upsample to DSD when playing PCM in the summer.
One thing I've noted is that the version of HQPlayer that I've been using, Desktop 2.10.0 ASIO, sometimes does not give any error indication when it runs out of CPU, just an audible glitch. Apparently HQPlayer sends something on to the USBPAL driver for my Mytek, because when this happens no errors are counted by USBPAL (assuming there are adequate buffers configured on the control panel, not to be confused with the HQPlayer buffer time). I consider the lack of an error indication to be a minor bug, but I'm not sure whether this is a bug in HQPlayer or in the USBPAL driver.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
Post a Followup:
| FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
||||||||||||||
This post is made possible by the generous support of people like you and our sponsors:
Top of Page ]
[ Contact Us ]
[ Support/Wish List ]
[ Copyright © 2024, Audio Asylum, all rights reserved ]