Arturia Forums

Software Instruments => Vocoder V => Vocoder V - Technical Issues => Topic started by: sag_the_great on November 30, 2021, 10:45:12 am

Title: Cannot select input in standalone mode
Post by: sag_the_great on November 30, 2021, 10:45:12 am
Latest version for Vocoder. Can anyone replicate this? In standalone mode for ASIO driver, there is a list of available inputs in the Audio settings dialog, but I am unable to select any of them, so it seems we can no longer route audio into the vocoder in stand alone mode.
Title: Re: Cannot select input in standalone mode
Post by: LBH on November 30, 2021, 07:45:30 pm
Hi,

Have you been able to do this before, the way you try now?

You say ASIO. But what soundcard and microphone inputs do you use?

It does work with the new version 1.2.0.1783, if you have the right gear and or settings.

Unfortunately i in example have'nt found a possiblity to use Windows audio or ASIO4ALL and build in mic on my laptop. I'm not sure why. It was the same before the new update.
But on my main music PC where i use an external soundcard with mic inputs it work fine using my soundcards ASIO drivers.

I'm on Windows 10.
Title: Re: Cannot select input in standalone mode
Post by: sag_the_great on November 30, 2021, 08:33:25 pm
Yes it worked before. Audient evo 4 asio . Also doesn't work with the generic aside driver. Also on win10.
Title: Re: Cannot select input in standalone mode
Post by: LBH on November 30, 2021, 08:57:35 pm
In that case you can try to clean the preferences and to reinstall Vococer V through ASC, if you have'nt allready.
If that does'nt help, then i suggest you contact Arturia support through your account. I can't tell, if they have changed anything.

BTW: Just in case: Be sure your soundcard mic outputs are active, in case that matters.
Title: Re: Cannot select input in standalone mode
Post by: sag_the_great on January 04, 2022, 08:31:08 am
Seems this was a problem across several vstis, now fixed with tle latest updates
Title: Re: Cannot select input in standalone mode
Post by: LBH on January 04, 2022, 04:32:49 pm
Seems this was a problem across several vstis, now fixed with tle latest updates
Okay. Great it's solved. Thanks for reporting back.