Tuniac 100711

The Tuniac forum.
Post Reply
Site Admin
Posts: 269
Joined: Sun Mar 28, 2010 12:36 am

Tuniac 100711

Post by Brett » Sun Jul 11, 2010 1:45 pm

-Direct X June 2010 (XAudio 2.7)
-Force XP SP3 in installer
-std_infomanager supports wav track length and ape files. Remove those infomanagers
-BASS dll update

http://sourceforge.net/projects/tuniac/ ... ac/100711/

Posts: 1
Joined: Tue Jul 13, 2010 8:39 am

Re: Tuniac 100711

Post by shrisha » Tue Jul 13, 2010 8:50 am

Just found Tunaic and I have to say it's really nice! Neat and fast. Just wondering if you have a plan for WASAPI output option in future. Would be really great to have such a wonderful peace of software in audiophile grade level.I will happy to participate in testing if any.
Thanks so much for very nice player!

Site Admin
Posts: 269
Joined: Sun Mar 28, 2010 12:36 am

Re: Tuniac 100711

Post by Brett » Wed Jul 14, 2010 4:58 am

Thanks I love to hear from people that enjoy Tuniac :)

I dont plan to do anything all that major, maybe we can nag Tony Million to write something neat like that :)

Things to note:
-WASAPI would only work on Vista and 7.
-Tuniac uses XAudio 2 to output to the soundcard, which under Vista and 7 is using WASAPI in shared mode. Under XP it is directly controlling the soundcard hardware(hardware acceleration) like ASIO and WASAPI Exclusive mode do.
-Creative have released Creative ALchemy for Vista/7 to redirect DirectSound/XAudio to OpenAL to bypass WASAPI Shared mode and reintroduce direct hardware control(hardware acceleration) for DirectSound/XAudio.
-Realtek have 3D SoundBack and C-Media have Xear3D EX which atleast redirect DirectSound3d calls similar to Creative ALchemy. Not sure if they catch DirectSound/XAudio.
-Tuniac does all it's audio mixing itself for crossfade, volume, EQ etc in 32bit float precision not fixed point.
-ASIO is the only way to ensure sample matched audio *to* Creative and Asus soundcards. WASAPI will get resampled.
-Once the audio gets to the soundcard it is highly likely that on the soundcard itself the audio will also be resampled and/or converted to float. This means you cant get bit perfect playback with WASAPI, ASIO, Kernel Streaming and never have been able to.
-Your DAC is much less accurate then the slight rounding errors resampling and conversion to floats might introduce.
-Tuniac is doing very similar things to the audio that will always happen to your audio regardless of what you try to do to bypass things. Basically it is likely to get resampled and/or converted to float at some point in your audio pipe before the DAC. Tuniac does not resample however.

-Forget about bit perfect playback. It's a myth and doesn't actually matter.
-This isnt as simple as "send it to WASAPI and it will sound better".
-Cards handle the different paths differently. What is direct hardware support on one soundcard on one version of Windows, isnt the same on the next soundcard or next version of Windows.
-You wont hear any difference.
-It is likely that there is zero bit perfect playback paths to your soundcards DAC.
-The DAC itself has much more accuracy issues then the path to the DAC in these cases.
-And just for kicks the original PS3's that support it convert Sony's own SACD DSD format to PCM which is a "lossy conversion" even though it as a HDMI 1.3 player can send it as DSD. Where are the audiophiles on that one? :)

Post Reply