Re: scsynth.exe vs VoiceMeeter for online teaching

[email protected] Sun, 10 May 2020 17:19:50 +0200
Newsgroups gmane.comp.audio.supercollider.devel
Message-ID <[email protected]>
> Which audio API did you try for VoiceMeeter?
I've just seen that VoiceMeeter supports all common Windows audio APIs
(https://www.vb-audio.com/Voicemeeter/). For scsynth, the ASIO API
should be your best bet.

Christof

On 10.05.2020 11:55, [email protected] wrote:
>> So I would set both the meeting software and SC to use JACK ASIO?
> With the "JackRouter" ASIO driver you can easily interconnect
> applications on Windows as long as they support ASIO. But I suspect that
> your meeting software won't support ASIO...
>
> Regarding your issue with VoiceMeeter + SC:
>
>> SuperCollider: PortAudio --> VoiceMeeter input: boots up but playing
>> SinOsc.ar(440) produces only some randomly-timed very low frequency
>> pulses.
> Can you post the device list you get in SuperCollider? With portaudio
> you can actually choose between several audio APIs (MME, DirectSound,
> ASIO, WASAPI, WDM-KS), which can be a bit confusing for users not
> familiar with Windows. Which audio API did you try for VoiceMeeter?
>
> Christof
>
> On 10.05.2020 03:04, [email protected] wrote:
>> On Sun, May 10, 2020 at 1:25 AM <[email protected]> wrote:
>>> scsynth uses portaudio, so you should be able to just use the Jack ASIO
>>> Driver. But you have to watch out for problems like these:
>>> https://github.com/supercollider/supercollider/issues/4718
>> Consider me a Windows dummy.
>>
>> So I would set both the meeting software and SC to use JACK ASIO?
>>
>> I had been avoiding JACK because of the known JackRouter 64-bit issue.
>> (Did we ever figure out why that prevented the server from booting?)
>>
>> Oh, while looking for the JackRouter issue, I saw this comment from a
>> year ago:
>>
>> "SuperCollider uses a custom version of portaudio, so the problem
>> might be there." --
>> https://github.com/supercollider/supercollider/issues/2742#issuecomment-505463694
>>
>>
>> So there might be a concrete reason why SC's PortAudio behavior is
>> different from a few other PortAudio apps.
>>
>> hjh
>>
>> _______________________________________________
>> sc-dev mailing list
>>
>> info (subscription, etc.):
>> http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>> archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
>> search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/
>
> _______________________________________________
> sc-dev mailing list
>
> info (subscription, etc.):
> http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
> archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
> search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/