[GourouLubrik]

What was the problem with the TH900/V200 combo?

Biggest problem is the weird soundstage, lacks of depth, very frontal. It was also be quite harsh in the 10khz region.
Please see my old posts about this:
http://www.head-fi.org/t/723304/pioneer-u-05-usb-dac-amp-with-dual-es9016/15#post_11034137
http://www.head-fi.org/t/723304/pioneer-u-05-usb-dac-amp-with-dual-es9016/15#post_11056165
 
Chaining the 2 listening was a very destabilizing experience.

 

[Cornan]

Regarding the What Hifi review, I've compared side by side Pioneer U-05 and the Audiolab M-Dac In dac mode (feeding a Violectric HPA-V200)... And I've kept the Pioneer.
I never liked the M-Dac HPA, it was so boring, so It's no match neither...

I've told it before and will told it again, I think that the Pioneer U-05 HPA sounds much better in balanced mode. It does't have enough power for orthodynamics such as Audeze or Fostex T50RP mods. HPA is more on the warm side, but without sacrificing details, I use NoS, Short filters, and maximum lock range available. I've sold the Violectric HPA-V200 for my use with the Fostex TH-900. But would have kept it for IEMs or orthodynamics use.

Although I use id much less, dac output sounds clean, neutral, maybe a little analitycal/cold but not really thin. It's not boring and I find it has excellent dynamic. it's fairly transparent and respect the character of the amplifer. As I told in intro, I prefer the pioneer over my ex Audiolab (but that's not a huge gap, just a matter of preference), and it's much better that the Integrated dac of my Rotel RA-1570 (much bigger gap ).

Why do you want to keep the lock range on full? As far as I can hear the sound improved with less lock range. Below setting 5 it is getting vastly improved. Åt this stage I am even figuring balanced mode will not improve things too much.

 

[kuko61]

I bought it a week ago as my first desktop DAC/Amp. I'm very satisfied with him, Sound is dynamic and very clear and detailed.
I tried it with all my vintage Sennheiser headphones and Pioneer very well working with them. Headphones playing clearly better than with Fiio E17  

 

 

 

 

 

[GourouLubrik]

Why do you want to keep the lock range on full? As far as I can hear the sound improved with less lock range. Below setting 5 it is getting vastly improved. Åt this stage I am even figuring balanced mode will not improve things too much.

Got it the wrong way, I meant minimum, narrowest lock range.
BTW, I can't do that on my Essence STX coaxial output, It does droupout.
Still your wrong with the balanced TH-900, going SE to BAL is way mooooooore obvisous that changing any settings on the Pioneer.
 
@Kuko61: nice pics ... do you plan to reterminate your sennheiser to try it balanced ?

 

[kuko61]

Thanks. Yes, I am planning change 6.3 mm TRS connectors to 4-pin XLR. Connectors I have already ordered.
I want to modify some original cables and also create new DYI balanced cables and XLR -> TRS adapter

 

[Cornan]

I am using JplayStreamer for Tidal and by some reasons (clock 3/KS/UltraStream/1Hz/10sec settings) I need to change the clock resolution to 15,6ms (Windows default) selected in Jplay but Pioneers drivers seems to push down the clock resolution to 1ms. That is normally a good thing...but not with my settings. Does anybody know if it is possible to change the latency settings on Pioneers drivers and how I should do to make this happen? I use to have a Stello U3 with TheSycon v1.61 were it was possible to change the latency that affects the clock resolution...but Pioneers drivers does´nt have a control panel so I guess this means that I will have to find the right folder and make the change somehow. Appreciate a reply in this matter.

 

[hercule]

Have you tried ASIO instead of kernel streaming?
In ASIO mode, you should be able to change the latency value.

 

[Cornan]

Have you tried ASIO instead of kernel streaming?
In ASIO mode, you should be able to change the latency value.

Yes, it works in Asio mode but not in KS mode. Do you know why this is? I prefer the sound with KS and would like it to work. Were do you find the Asio settings you attached?

 

[hercule]

What is the nature of your audio problem?

 

[Cornan]

What is the nature of your audio problem?

No problem really. Just curious. If I could get my clock resolution to 15,6 ms the sound should be even better according to many others. I am really happy with the sound as it is.

Actually it does'nt work with Asio. Just for a second. I am actually thinking that the clock indeed are 15,6 ms while running JplayStreamer...but I cannot check it since I need to stop playing to see the clock resolution in Jplay panel and if I stop playing the Pioneer driver puts on hold. Tried to download Clockres v2 to check my clock resolution while playing a track but it does'nt seem to work on my W10 computer.

Thanks for trying to help me. I will continue on my own to find another Clockres checker that works on W10 to find out IF it is actually 15,6 ms while playing through JplayStreamer. It sounds brilliant...but I am too curious not to find out!

 

[hercule]

Tools like ClockRes ( https://technet.microsoft.com/en-us/sysinternals/bb897568.aspx )may help you to determine the actual high resolution timer that jplay could obtain.
By definition kernel streaming is a method to achieve  low latencies and bypass the mixer and so on ...
I am not a low-level system engineer, but from my understandings, jplay may use a 15 ms latency resolution timer.
It may be easier to check the MMCSS settings and ensure that jplay is in a high priority class ( https://msdn.microsoft.com/en-us/library/windows/desktop/ms684247%28v=vs.85%29.aspx. See also https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/75eb41aa-ee34-4171-9fa2-9bae03030907/timer-resolution-altered-in-exclusive-mode).
 
 
Some readings on the audio latency and Windows 10 :
https://msdn.microsoft.com/en-us/library/windows/hardware/mt298187%28v=vs.85%29.aspx
 
edit: the ASIO panel is a foobar binary. It's purpose is to interface foobar with ASIOPIONEERUSBDA64.dll or ASIOPIONEERUSBDA.dll.

 

[Cornan]

  Tools like ClockRes ( https://technet.microsoft.com/en-us/sysinternals/bb897568.aspx )may help you to determine the actual high resolution timer that jplay could obtain.
By definition kernel streaming is a method to achieve  low latencies and bypass the mixer and so on ...
I am not a low-level system engineer, but from my understandings, jplay may use a 15 ms latency resolution timer.
It may be easier to check the MMCSS settings and ensure that jplay is in a high priority class ( https://msdn.microsoft.com/en-us/library/windows/desktop/ms684247%28v=vs.85%29.aspx. See also https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/75eb41aa-ee34-4171-9fa2-9bae03030907/timer-resolution-altered-in-exclusive-mode).
 
 
Some readings on the audio latency and Windows 10 :
https://msdn.microsoft.com/en-us/library/windows/hardware/mt298187%28v=vs.85%29.aspx
 
edit: the ASIO panel is a foobar binary. It's purpose is to interface foobar with ASIOPIONEERUSBDA64.dll or ASIOPIONEERUSBDA.dll.

Thanks hercule! Very useful tips!
I am going to check this tonight when I am back from work. I am also considering that one of the following tweaks I done previously might affect my settings (run in command promt as administrator):
 
bcdedit /set useplatformclock yes (or bcdedit /set useplatformclock true)
bcdedit /set useplatformtick yes
bcdedit /set disabledynamictick yes
 
These make sure to make use of HPET (disabled in Windows 10) and system clock effectively and force it to run in full capacity for timing domain. I am figuring at lest useplatformclock might bring down the clock resolution. But first of all I will make sure if it is actually running with 15,6 ms clock resolution. I actually think that it is only a running software that actively could change the clock resolution...not a tweak...but cannot be too sure! 

 

 

[plakat]

Reading that I have to say I'm quite happy with CoreAudio...
 
Btw.: the U05 works with an iDevice connected through the Camera Connection Kit. Very welcome indeed.

 

[hercule]

I have not found free program to set timers.
But if you have some coding knowledge, you can find code to set timers on the msdn.
Here is some c# code taken from this URL: https://social.msdn.microsoft.com/Forums/en-US/8aea13d9-35f1-4b66-a5b4-726651d985f7/how-to-set-timer-resolution-to-05ms-
 

You may use NtSetTimerResolution function, try this:
 
        [DllImport("ntdll.dll", EntryPoint = "NtSetTimerResolution")]
        public static extern void NtSetTimerResolution(uint DesiredResolution, bool SetResolution, ref uint CurrentResolution);
        private void Foo()
        {
            uint DesiredResolution = 9000;
            bool SetResolution= true;
            uint CurrentResolution = 0;
 
            NtSetTimerResolution(DesiredResolution, SetResolution, ref CurrentResolution);
 
        }

 
It should compile with Visual studio Community Edition.

 

[Cornan]

I have not found free program to set timers.
But if you have some coding knowledge, you can find code to set timers on the msdn.
Here is some c# code taken from this URL: https://social.msdn.microsoft.com/Forums/en-US/8aea13d9-35f1-4b66-a5b4-726651d985f7/how-to-set-timer-resolution-to-05ms-

.
You may use NtSetTimerResolution function, try this:
 


        [[COLOR=2B91AF]DllImport[/COLOR]([COLOR=A31515]"ntdll.dll"[/COLOR], EntryPoint = [COLOR=A31515]"NtSetTimerResolution"[/COLOR])]


        [COLOR=0000FF]public[/COLOR] [COLOR=0000FF]static[/COLOR] [COLOR=0000FF]extern[/COLOR] [COLOR=0000FF]void[/COLOR] NtSetTimerResolution([COLOR=0000FF]uint[/COLOR] DesiredResolution, [COLOR=0000FF]bool[/COLOR] SetResolution, [COLOR=0000FF]ref[/COLOR] [COLOR=0000FF]uint[/COLOR] CurrentResolution);


        [COLOR=0000FF]private[/COLOR] [COLOR=0000FF]void[/COLOR] Foo()


        {


            [COLOR=0000FF]uint[/COLOR] DesiredResolution = 9000;


            [COLOR=0000FF]bool[/COLOR] SetResolution= [COLOR=0000FF]true[/COLOR];


            [COLOR=0000FF]uint[/COLOR] CurrentResolution = 0;


 


            NtSetTimerResolution(DesiredResolution, SetResolution, [COLOR=0000FF]ref[/COLOR] CurrentResolution);


 


        }

 


It should compile with Visual studio Community Edition.

Thanks for your effort hercule!
I have'nt got enough time to check it tonight. However, found another tool called Windows System Timer Tool that looks interesting http://vvvv.org/contribution/windows-system-timer-tool
I have'nt got enough knowledge to code it myself I'm afraid.
I will check tomorrow and report back if I figure it out!