ASIO

I don't really use foobar. I still generally use Wavelab via PC when I need to but I do think it the best player sonically of those readily available. Problem is, I'm not into FLAC (ducks) but I find foobar fine though a bit rudimentary if I just select WAV tracks from the PC library with Foobar set as default player. Try WAV again when your dialed in though you'll hate me if you think it better as you won't be able to use your well setup interface as you'd like. Foobar and a WAV library are like oil and water. I'll have to try AIFF at some point. Did you notice that you can now rip with offset via Foobar?

http://www.foobar2000.org/comp...ts/view/foo_out_asio It was really close to the kernel stream option. A subtle difference via the Naim DAC so you may not need to try it. It just seemed to reach a hair further in. I'd just load and go at the defaults. I've read that some ASIO drivers or WASAPI can be affected by ASIO4all but a true ASIO driver really shouldn't be so I suspect you could have both. Of course, you also could just drag the ASIO4all dll out of the folder to the desktop and put it back later if you want to keep it but I prefer the kernel option anyways.

quote:

Originally posted by js:
http://www.foobar2000.org/comp...ts/view/foo_out_asio

This just enables foobar to use an ASIO driver as an output device. You still need to get an ASIO-driver from somewhere though.

-
aleg

Should already be loaded from his transit software. If I assumed wrong about it having one, you're right, he's out of luck but Kernel should still work and would still be a good choice in XP. Don't know what I'd choose in Vista/7.

I just did search and I think the driver is there. Pick output, ASIO virtual devices, M-Audio ASIO. Double click on it to set channels if needed. Output again, in output device select ASIO:M-audio. If you can't see any of this, remove the ASIO4all or reload your driver, or both in that order.

In case you don't have it loaded from Transit software you could try Otachan ASIO or commercially available USB ASIO drivers instead of ASIO4all.

Kinda the same thing as ALEG was talking about. He'll need the dedicated M-Audio driver but I'm pretty sure it's there. I did notice that there's both a DLL and EXE version of the Otachian winamp plugin while checking for a foobar plugin that they no longer list. I'll have to check which I installed and try the other. Seems folks that can use it, prefer the exe.

Gentlemen,

Thanks for the thoughts.

I do have the ASIO drivers for the Transit installed. I can add it as an ASIO device in Foobar then choose "ASIO-USB Transit" in output options. That is option #1

Option 2 - Use ASIO4all and set-up the same way as above. Set output to "ASIO4all-USB Transit"

Option #3 - Use "DS - Transit output" - My understanding from multiple sources was that if Windows is only playing one stream of audio and all system volumes are at 100%, everything remains bit-perfect.

Option #4 - Kernel Streaming, never tried it.

**********************

I cannot say I have heard any significant differences between the first three. So I just stuck with DS until recently.

The one thing I noticed with using Option #1 and #2, is that in both cases I have to switch settings (and stop playback) in order to go between Redbook (16-44) and Hi-res (24-96).

In Option #1, I change the settings on the Transit. In Option 2 I change the settings in asio4all.

When I use DS (Direct Sound) output, I can play both hi-res and redbook without changing any settings. Also without any drop-outs.

With BOTH asio options, I sometimes get static bursts in playback on hi-res files, scary, annoying and unacceptable.

*****************

That being said.....

I am curious about a few things.

1) Is DS downsampling/dithering my 24/96? I wonder because the 24-96s still play even when the Transit is set to "2-in, 2-out 16bit up to 48khz".

2) Why am I getting drop-outs with ASIO but not with DS?

3) Should I try the Kernel Streaming option?

Ideally, whatever I use can seamlessly go from hi-res to redbook.


thanks everyone!!!
Patrick

PS- I am willing to try anything. If anyone has a suggestion on how to output my Foobar I would love to hear about it and try it.

....also, I know this might not be the best place for this discussion. But seeing that Naim has somewhat endorsed the Transit for use with the forthcoming DAC, I thought it might benefit many down the road.

-patrick

You shouldn't get drop outs anywhere near the default player buffer settings. May want to check the Transit's dedicated settings but the default should always work with 44. ASIO is switching clocks in the transit when changing from 44 to 96 and may take a restart of the track depending on the ASIO device.

I don't think Naim would mind this stuff. It also demonstrates why a dedicated device is a plus.

JS,

You use Wavelab, the protools style audio editor for podcasters etc? Must sound great.

Re: drop-outs. Drop-outs only occur with hi-res when using ASIO-out.

Do you have any suggestions for settings?

Regarding ASIO switching the clocks in the transit: The Transit can be set-up for:

- 16bit up to 48k
- 24bit up to 48k
- 24 from 48 to 96K
(all with varying numbers of in/out)

If I set-up as 16-48, then hi res files will not play unless I chagne settings in Transit, and vice versa.

This is why I like DS, as I dont have to change settings. When using DS, am I not actually getting 24-96? It sounds like I am and without drop-outs to boot.

This is the one aspect of Foobar and DA replay in general, that I simply do not understand. It also seems like there are very few resources out there to educate oneself.

If you were going to st-up Foobar how would you do it?

thanks,
p

Patrick maybe you can play with different buffer values,
or just try other software (MM of JRiver, for instance) in order to check if the dropouts are a foobar issue,

Using the native Transit driver might be the best option, at least in terms of cpu usage, so I would say is more likely to expect dropouts with Hi-rez material in direct sound.

goldfinch... thanks!!!

I have tried all latency and buffer settings and haven't noticed a difference between any of them in terms of drop-outs on ASIO with hi-res.

FYI, I have never experienced ANY drop-outs with redbook. Only when using both ASIO and hi-res.

thanks again!

I'd always use native. I'd set it up for 16 bit and play a rip, start, stop and then restart a 24/96 file and if it plays, recheck the control panel and see if it's switched. I suppose if nothing else works, you could upsample CDs tp 88/24 if you didn't want to reset. If your volume works in XP, you're getting 48k at the transit, often also when defeted. I believe Kernel and ASIO are the only ways to get 96k out of XP. It may have been you but I remember someone mentioning that the record side of the transit had to be defeated for it to play 96k. Could be a resource thing at the M-audio end.

JS,

By native do you mean setting up the Transit as an ASIO output, and not using ASIO4all? Or do you mean using DS to the Transit?

I dont think simply starting or re-starting the playback helps with the Hi-res "switching". You have to manually change the settings in th Transit as well as restart playback.... if i am understanding you correctly.

Record is automatically defeated with hi-res, the only hi-res settings are "2-in" or "2-out", never both. So in a way it is correct that you "defeat the record side" although you don't have any other option.

Regarding the upsampler, as you saying use DS-output with a SRC dsp to output everything @ 24bit?

Is there a definitive way to know exactly what the Transit is getting in terms of bit depth a freq rate?

This is why I've used DS in the past, this is far too confusing....

Does going to Windows 7 alleviate all of these problems?

quote:

Originally posted by js:
I'd always use native. I'd set it up for 16 bit and play a rip, start, stop and then restart a 24/96 file and if it plays, recheck the control panel and see if it's switched.

If I do exactly the above, when trying to play 24/96 it will error and say "device does not support frequency rate".

Then I have to stop the audio, change settings in the Transit, then restart. This brings the drop-outs galore.

The only way to seamlessly go between the two, is to use DS. Then the Transit will play anything regardless of its settings. This leads me to believe that DS is downsampling evrything.

The strange thing is that when using DS, it doesnt matter what the transit's settings are.

quote:

Originally posted by pcstockton:
This is why I've used DS in the past, this is far too confusing....

Does going to Windows 7 alleviate all of these problems?

Depends on the interface and output. You're not playing 96k in XP-DS.

In theory , a W7 system with a dig out and WASAPI should work pretty well.

Aha... making more sense

hence the lack of drop-outs with HIres and DS. It isnt playing hires.

So there is NO WAY to use ASIO and be able to switch seamlessly between hires and redbook. That is strange. How does the HDX and other players handle it?

I will try things tonight with a more powerful PC to see if the drop-outs disappear. I will try 7 when a buddy get his copy.

What is everyone else using with their Foobar?

-p

It depends on the device and how it's used. By increasing the buffers, I can make the TC work pretty seamlessly but I prefer the way it sounds with different buffer settings so I live with restart. It literally only takes a second and it doesn't matter whether it's ASIO or via Kernel. If something is purpose built in a known environment it's easier to optimize.

It takes more than a second to open the Transit's settings and change them. Then restart playback.

People should know this about the Transit as we go down the road. I would recommend a device that will passthrough a larger range.

what. you are alive. what happened PC.

I have no issues changing from normal to high resolution tracks in my system (J.River and Lynx AES16). I just notice a very slight delay in playback with high resolution stuff because J.River has to transfer the track first to the physical memory. I also used an M-Audio 192 sound card and I remember I also had occasional dropouts but I always thought it was a mains interference problem.