|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
60.227.51.246
In Reply to: Re: Probably not posted by Dawnrazor on February 4, 2007 at 19:11:47:
Don't use the ASIO output. Use DirectSound or WaveOut output plugins instead, and you will be able to use the volume control.The whole point of using ASIO in the first place is to preserve the bits (with minimal latency). If you don't intend to preserve the bits, why use ASIO?
*** The volume seems to work in Foobar with similiar plugins. ***
Foobar2000 is a different application than WinAmp. Just because something works in one doesn't mean it will work in the other. Volume changing is not something that's built into the ASIO spec.
Of course it is possible to implement a WinAmp ASIO output plug in that supported a volume control, but otachan hasn't done this (I suspect because it's completely against the philosophy of using ASIO in the first place). You could try asking him.
*** Everything is upconverted to 32 bits. ***
Actually, no. If you had an optimal ASIO configuration, it should be preserving the bits, so there should be no upconversion. Remember: the whole point of ASIO is to preserve the bits. Otachan's plug in for example can open the ASIO device in multiple modes, matching the bits in the input signal.
*** ANd, in this link, a poster says that it did but that was on a much earlier version, and I can't seem to find a similiar setting. ***
On some devices (with a hardware mixer), it is possible for the WinAmp volume control (which controls the Windows mixer) to affect ASIO (indirectly). This is because the actual volume control is implemented on the hardware mixer.
Again, just because something works on one set of devices does not mean it will work for your situation.
Follow Ups:
that this is somewhat of a non issue.Right now I am testing software such as win amp on a non audio pc, but on the big rig, I can use the lynx volume control if needed...even if the thought makes the ASIO designers shiver.
It is weird, because I do have asio set up in Foobar, and the lynx mixer reports 32 bits. If I read right, it should say 16. What is going on?
Finally on your 1212, is there a similiar volume control as in the lynx mixer?
I may be building a more budget audio PC for a friend, and the 1212 is probably the card I will choose if I can control the volume from it.
*** even if the thought makes the ASIO designers shiver ***LOL!
I don't think it will make them shiver, but you have to remember ASIO was never designed as a general purpose interface.
ASIO was originally designed by Steinberg to connect their digital audio workstation software (Cubase/Nuendo) to audio hardware. Because all the mixing is done by the DAW, what was needed was a direct connection between the DAW and the audio hardware that bypasses the Windows audio stack (to preserve bits and minimize latency).
I think PC audiophiles latched onto ASIO because it was also a convenient way for a music player app to bypass kmixer.
*** It is weird, because I do have asio set up in Foobar, and the lynx mixer reports 32 bits. ***
It's probably the foobar2000 asio implementation opening the ASIO device in 32 bits. In other words, the foobar2000 asio output plugin is doing the 16-bit to 32-bit conversion (which is a bit naughty).
otachan used to have a foobar2000 ASIO plugin (version 0.8 only). Unfortunately, it's no longer available for download.
*** Finally on your 1212, is there a similiar volume control as in the lynx mixer? ***
You can control volume using PatchMix. Unfortunately, as far as I know, there is no way of automating PatchMix (ie. control PatchMix functions from another program).
Actually, I would probably advise against using the E-MU for consumer applications. It is very pro-audio centric (quality and functionality above usability).
The PatchMix interface is rather daunting and has a steep learning curve - it closely resembles a pro audio mixer console. You may want to take this into account if your friend is not very PC literate. For example, just to change sample rates requires you to define and load a customized PatchMix session.
It's very difficult to change sample rates on the E-MU hardware because unlike the Lynx the E-MU uses dedicated clocks for each sample rate, so to change from 44.1 to 96 kHz for example effectively requires the DSP and DAC to be "rebooted" to a different clock.
The benefit of dedicated clocks (as opposed to the Lynx for example which uses clock synthesis) is much lower jitter, hence better sound quality.
At least the E-MU does allow sample rate changes via software. The other equipment I have that also uses dedicated clocks (an Edirol StudioCanvas) requires the device to be turned off and on again to change sample rates!
(which is a bit naughty).That was funny.
Thanks for the info on the Emu. This guy is pretty pc literate, so I shouldn't burden him with a steep learning curve.
.
This post is made possible by the generous support of people like you and our sponsors: