It seems like Live and Sound Forge both want to grab the sound drivers, so I can't use use them both at once If I am using the low latency Echo drivers.
I get an error message in Soundforge and no sound.
If instead LIVE uses the "directx full duplex' driver, then soundforge/waveladb/live will alll work together, but latency too high.
The issue is that the lower latency ECHo WDM driver grabs the audio to itself.
Has anyone gotten this combo to work?
using Sound Forge? (Echo driver)
You won't get it to work- the ASIO and/or WDM drivers aren't multi-client.
You could do what I did- have SF use another driver. Since you're only editing clips and not plasying them back with the project at the same time, latency isn't really an issue. There really isn't any reason to use ASIO or WDM drivers with a wave editor...
ew
You could do what I did- have SF use another driver. Since you're only editing clips and not plasying them back with the project at the same time, latency isn't really an issue. There really isn't any reason to use ASIO or WDM drivers with a wave editor...
ew
Perhaps give the Asio4all driver a shot?drb wrote:It seems like Live and Sound Forge both want to grab the sound drivers, so I can't use use them both at once If I am using the low latency Echo drivers.
I get an error message in Soundforge and no sound.
If instead LIVE uses the "directx full duplex' driver, then soundforge/waveladb/live will alll work together, but latency too high.
The issue is that the lower latency ECHo WDM driver grabs the audio to itself.
Has anyone gotten this combo to work?
It's definately useful when you're using Sound Forge's "plug-in chainer" engine that allows realtime use of plugins on audio. While low latency isn't a necessity, it is definately prefered in this scenarioewistrand wrote:
There really isn't any reason to use ASIO or WDM drivers with a wave editor...
ew
Yeah, but you're editing and NOT doing anything like playing in realtime on other tracks with it. Latency doesn't make a bit of difference in this case- all it means is that the clip's delayed. Since you're only hearing THAT clip, I don't see where it makes any difference whatsoever. If you use the preview, you'll find out that the clip's delayed by a few ms, but you can still monitor the result.blastique wrote:Perhaps give the Asio4all driver a shot?drb wrote:It seems like Live and Sound Forge both want to grab the sound drivers, so I can't use use them both at once If I am using the low latency Echo drivers.
I get an error message in Soundforge and no sound.
If instead LIVE uses the "directx full duplex' driver, then soundforge/waveladb/live will alll work together, but latency too high.
The issue is that the lower latency ECHo WDM driver grabs the audio to itself.
Has anyone gotten this combo to work?
It's definately useful when you're using Sound Forge's "plug-in chainer" engine that allows realtime use of plugins on audio. While low latency isn't a necessity, it is definately prefered in this scenario :)ewistrand wrote:
There really isn't any reason to use ASIO or WDM drivers with a wave editor...
ew
ew
-
- Posts: 8803
- Joined: Wed Mar 31, 2004 3:12 pm
- Location: www.fridge.net.au
- Contact:
Right, but what if the intention is to modify plugin parameters and hear the result IN realtime. I'm not sure how you mean it wouldn't make a difference.ewistrand wrote:Yeah, but you're editing and NOT doing anything like playing in realtime on other tracks with it.
Pretend you're working with a two track pre-master through hardware processing units...
Would it bother you, for example, if you're tweaking your multiband crossover and threshold parameters and it took you half a second to hear the result EACH time?
Quite honestly, that would piss me off beyond belief.
Anyhow, all we know is that drb wishes to use his low latency Echo drivers IN sound forge. I'm just saying that there is in fact a use for low latency in sound forge, even though you may not feel the same way.