Page 1 of 1
Presonus 22VSL Interface [SOLVED]
Posted: Mon Nov 21, 2011 9:44 pm
by mdorren
Audacity is not seeing this interface in the preferences. Is anybody successfully using it with Audacity?
Thanks
Re: Presonus 22VSL Interface
Posted: Mon Nov 21, 2011 9:59 pm
by kozikowski
Windows has to see it first. Does it appear in the Start > Control Panels > Sound...
Koz
Re: Presonus 22VSL Interface
Posted: Mon Nov 21, 2011 10:28 pm
by mdorren
Thanks for the quick reply. Windows (7, 64bit) sees it in recording, but not in playback
Re: Presonus 22VSL Interface
Posted: Tue Nov 22, 2011 12:30 am
by Gale Andrews
Restart Audacity after connecting Presonus and having it recognised in Windows (both recording and playback).
Do you have the latest drivers from
http://www.presonus.com/products/Detail ... oductId=63 ?
Audacity will not see MIDI input or ASIO drivers, so if there is a choice in Presonus you have to use the WDM audio drivers.
Gale
Re: Presonus 22VSL Interface
Posted: Tue Nov 22, 2011 12:36 am
by mdorren
Yes, I have the latest drivers. Audacity sees the recording input but the signal is VERY faint. There seems to be no WDM driver for the Presonus interface. I have a post on their board also. Thanks
Re: Presonus 22VSL Interface
Posted: Tue Nov 22, 2011 1:15 am
by Gale Andrews
Make sure you are using latest 1.3.13 Beta (see Help > About Audacity for your current version).
Have you turned the Audacity input slider up, or is there a control panel for Presonus where you can do this?
Is your choice of Presonus input in Audacity's Device Toolbar just USB Audio Codec? How many input channels have you selected in Audacity? If you are connected to the right channel input you may have to record in stereo, split the track to mono using the menu in the track name then close one of the tracks.
Gale
Re: Presonus 22VSL Interface [SOLVED]
Posted: Tue Nov 22, 2011 1:21 am
by mdorren
Right you are! I was using the output slider on the track itself rather than the input slider at the top of the window (which for some reason seems to default to a low setting) Anyway, user error it is... what a surprise. Many thanks!