|
Post by qdtjni on Jan 22, 2016 7:41:17 GMT -5
With one exception, I have no problems at all with latency on either a Mac Mini with OS X or on an Intel I5 based NUC ruling Win 7 Professional. I use Roon, squeezelite, Tidal & Pure Vinyl and it works fine with all the sample rates supported by DIRAC (i..e 44-192 KHz).
The only problems have been with Roon Transcoding DSD 5.6 Mhz to PCM, which was fine with LMS transcoding it for squeetelite.
|
|
|
Post by qdtjni on Jan 22, 2016 7:45:37 GMT -5
The demo PC version worked just fine for me. No problems at all. But I see no reason to opt for it with the full version on the XMC unless you want to switch filters quickly AND you run everything through the PC it's installed on. On other reason would be for source material with higher sampling rate than 48 kHz or if you don't want 44.1 kHz resampled to 48 kHz.
|
|
|
Post by millst on Jan 22, 2016 10:52:33 GMT -5
The Mac Mini and NUC use mobile versions of Intel processors, not exactly powerhouses. That's a data point towards it being a software problem or an issue with the output device.
-tm
|
|
|
Post by greenpsycho on Jan 22, 2016 19:03:20 GMT -5
I'm beginning to think its may not be built for Windows 10. Honestly, I searched for probably 2 hours online and poured through all the manuals and documentation regarding how to get past the "could not open the recording device" error. Finally, I just started stopping services, and once I killed cortana, it found the mic and everything was fine. Just curious if anyone else has had luck (or heard 2nd/3rd hand?) regarding dirac and windows 10?
|
|
klinemj
Emo VIPs
Official Emofest Scribe
Posts: 15,090
|
Post by klinemj on Jan 22, 2016 19:09:40 GMT -5
I'm beginning to think its may not be built for Windows 10. Honestly, I searched for probably 2 hours online and poured through all the manuals and documentation regarding how to get past the "could not open the recording device" error. Finally, I just started stopping services, and once I killed cortana, it found the mic and everything was fine. Just curious if anyone else has had luck (or heard 2nd/3rd hand?) regarding dirac and windows 10? I have only used it with Windows 10. Works fine. Mark
|
|
|
Post by monkumonku on Jan 22, 2016 20:42:37 GMT -5
I'm beginning to think its may not be built for Windows 10. Honestly, I searched for probably 2 hours online and poured through all the manuals and documentation regarding how to get past the "could not open the recording device" error. Finally, I just started stopping services, and once I killed cortana, it found the mic and everything was fine. Just curious if anyone else has had luck (or heard 2nd/3rd hand?) regarding dirac and windows 10? Ran Dirac full on Windows 10 with no problems.
|
|
|
Post by greenpsycho on Jan 23, 2016 8:06:20 GMT -5
Just to clarify, we're talking the Dirac live calibration and audio processor standalone PC software, not the measurement side for the XMC-1 (slightly different software on the measurement side, and obviously the XMC-1 does the audio processing, not your PC software)
|
|
|
Post by overtheair on Jan 23, 2016 13:54:56 GMT -5
Greenpsycho - just a thought but did you have JRiver's WDM driver in operation when you tested Dirac on the PC? This might explain the audio from different sources than expected and the latency, if something wasn't set up as required between JRMC, Windows 10 and Dirac. The software is so glitchy and the lag is a good 30s behind where the PC is at. The few times that I got it to work successfully, I had to select one of my sources that I DID NOT want to use (hdmi out on my video card) and then I got music coming through my DAC. Stupid stupid software. Additionally, I'm not so sure it works with 192/24 music. It might be advertised that way and I know you can create filters for those levels, but according to jriver, it was downsampling. [/quote]
|
|
|
Post by greenpsycho on Jan 24, 2016 9:23:58 GMT -5
Honestly, didn't even know what that was, until now. Looks cool though, I might have to test that out for a few specific cases
|
|