Audio Output Buses Not Visible

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Audio Output Buses Not Visible

Jim Aikin
I'd like to be able to use Csound in conjunction with my eurorack modular, for long step sequences, multisegment envelopes, and so forth. I'm using Windows 7 64-bit. I have a PreSonus Audiobox 1818VSL, which has the ADAT lightpipe connectivity, and the ADAT cables connect to my Expert Sleepers ES-3 and ES-6 modules. I know the ADAT connections work, because Reason has no trouble either sending or receiving audio via those buses.

Csound, however, can't see them. Tonight I downloaded and installed the latest version (6.07 beta, CsoundQt 0.9.1). The PreSonus analog and SPDIF output buses are listed in the dac list, but the lightpipe outputs aren't.

Oh, and here's a new fillip. I was going to attach a screenshot of the available dacs to this message -- but now CsoundQt is refusing to leave the drop-down menu open. It does something insanely fast and then closes the menu. It was working the first time I tried it tonight, but now it's toast. So I'll toss in a screen grab from Run In Terminal instead.

Suggestions would be welcome. Is there a way to troubleshoot this? Have other people had success sending Csound audio to a lightpipe?

Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

Tarmo Johannes-2

Hi,
If you run csound in command line with -odac999 option, is your device listed?
I wonder is it problem of portaudio, asio drivers or what should this connection use.
Not sure if it helps...
Tarmo

28.03.2016 8:24 kirjutas kuupäeval "Jim Aikin" <[hidden email]>:
I'd like to be able to use Csound in conjunction with my eurorack modular,
for long step sequences, multisegment envelopes, and so forth. I'm using
Windows 7 64-bit. I have a PreSonus Audiobox 1818VSL, which has the ADAT
lightpipe connectivity, and the ADAT cables connect to my Expert Sleepers
ES-3 and ES-6 modules. I know the ADAT connections work, because Reason has
no trouble either sending or receiving audio via those buses.

Csound, however, can't see them. Tonight I downloaded and installed the
latest version (6.07 beta, CsoundQt 0.9.1). The PreSonus analog and SPDIF
output buses are listed in the dac list, but the lightpipe outputs aren't.

Oh, and here's a new fillip. I was going to attach a screenshot of the
available dacs to this message -- but now CsoundQt is refusing to leave the
drop-down menu open. It does something insanely fast and then closes the
menu. It was working the first time I tried it tonight, but now it's toast.
So I'll toss in a screen grab from Run In Terminal instead.

Suggestions would be welcome. Is there a way to troubleshoot this? Have
other people had success sending Csound audio to a lightpipe?

<http://csound.1045644.n5.nabble.com/file/n5748187/dacs.jpg>



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

rorywalsh

Could be a portaudio issue. Does Pd see the lightpipe connection? It also uses portaudio..

On 28 Mar 2016 09:29, "Tarmo Johannes" <[hidden email]> wrote:

Hi,
If you run csound in command line with -odac999 option, is your device listed?
I wonder is it problem of portaudio, asio drivers or what should this connection use.
Not sure if it helps...
Tarmo

28.03.2016 8:24 kirjutas kuupäeval "Jim Aikin" <[hidden email]>:
I'd like to be able to use Csound in conjunction with my eurorack modular,
for long step sequences, multisegment envelopes, and so forth. I'm using
Windows 7 64-bit. I have a PreSonus Audiobox 1818VSL, which has the ADAT
lightpipe connectivity, and the ADAT cables connect to my Expert Sleepers
ES-3 and ES-6 modules. I know the ADAT connections work, because Reason has
no trouble either sending or receiving audio via those buses.

Csound, however, can't see them. Tonight I downloaded and installed the
latest version (6.07 beta, CsoundQt 0.9.1). The PreSonus analog and SPDIF
output buses are listed in the dac list, but the lightpipe outputs aren't.

Oh, and here's a new fillip. I was going to attach a screenshot of the
available dacs to this message -- but now CsoundQt is refusing to leave the
drop-down menu open. It does something insanely fast and then closes the
menu. It was working the first time I tried it tonight, but now it's toast.
So I'll toss in a screen grab from Run In Terminal instead.

Suggestions would be welcome. Is there a way to troubleshoot this? Have
other people had success sending Csound audio to a lightpipe?

<http://csound.1045644.n5.nabble.com/file/n5748187/dacs.jpg>



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

rorywalsh

A quick search shows Pd correctly  listing ADAT devices:
http://lists.puredata.info/pipermail/pd-list/2009-01/067119.html
Did you generate that list using -odac999 as Tarmo suggested?

On 28 Mar 2016 09:59, "Rory Walsh" <[hidden email]> wrote:

Could be a portaudio issue. Does Pd see the lightpipe connection? It also uses portaudio..

On 28 Mar 2016 09:29, "Tarmo Johannes" <[hidden email]> wrote:

Hi,
If you run csound in command line with -odac999 option, is your device listed?
I wonder is it problem of portaudio, asio drivers or what should this connection use.
Not sure if it helps...
Tarmo

28.03.2016 8:24 kirjutas kuupäeval "Jim Aikin" <[hidden email]>:
I'd like to be able to use Csound in conjunction with my eurorack modular,
for long step sequences, multisegment envelopes, and so forth. I'm using
Windows 7 64-bit. I have a PreSonus Audiobox 1818VSL, which has the ADAT
lightpipe connectivity, and the ADAT cables connect to my Expert Sleepers
ES-3 and ES-6 modules. I know the ADAT connections work, because Reason has
no trouble either sending or receiving audio via those buses.

Csound, however, can't see them. Tonight I downloaded and installed the
latest version (6.07 beta, CsoundQt 0.9.1). The PreSonus analog and SPDIF
output buses are listed in the dac list, but the lightpipe outputs aren't.

Oh, and here's a new fillip. I was going to attach a screenshot of the
available dacs to this message -- but now CsoundQt is refusing to leave the
drop-down menu open. It does something insanely fast and then closes the
menu. It was working the first time I tried it tonight, but now it's toast.
So I'll toss in a screen grab from Run In Terminal instead.

Suggestions would be welcome. Is there a way to troubleshoot this? Have
other people had success sending Csound audio to a lightpipe?

<http://csound.1045644.n5.nabble.com/file/n5748187/dacs.jpg>



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

Jim Aikin
In reply to this post by rorywalsh
Sorry -- I'm not really a command line user. (Not since I sold my Kaypro.) Running csound -odac999 in the Command Prompt gives me a full list of the command-line flags, but it doesn't show any dac I/O at all. Can you be more specific about what exactly I should type at the command prompt?

Also ... yes, I tried Pd, and it doesn't see the lightpipe either. I have no idea what portaudio is, but offhand I'd say your guess may be a good one.
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

rorywalsh
Hi Jim. PortAudio is the library that Csound uses to interact with audio hardware. The reason why you were shown all those command line flags is most likely because you didn't pass a Csound file. The following should work as long as the file can be found:

csound myfile.csd -odac999

The idea behind this little trick to get the numbers for the DACs available. Once you know the one you want you replace the 999 with the corresponding DAC number. PureData also used PortAudio. If it doesn't list the lightpipe than it might be a PortAudio limitation. Can you access the lightpipe using ASIO? if you select the ASIO driver from the list and then open the ASIO settings and select the appropriate card from there?     

On 28 March 2016 at 17:24, Jim Aikin <[hidden email]> wrote:
Sorry -- I'm not really a command line user. (Not since I sold my Kaypro.)
Running csound -odac999 in the Command Prompt gives me a full list of the
command-line flags, but it doesn't show any dac I/O at all. Can you be more
specific about what exactly I should type at the command prompt?

Also ... yes, I tried Pd, and it doesn't see the lightpipe either. I have no
idea what portaudio is, but offhand I'd say your guess may be a good one.



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187p5748200.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

Jim Aikin
Using that command line gives me the same result I uploaded as a screenshot in my first message -- no lightpipe. Curiously, the AudioBox 1818VSL line outs are all listed twice. Switching Csound (back in CsoundQt now) to dac15, which is the AudioBox ASIO driver, I still get sound through the line out 1/2, nothing to do with lightpipe.

The Asio4all control panel also can't see the lightpipe. I rather doubt it's using portaudio, but I suppose it might be.

In any event, Reason can see and use the lightpipe when I ask it to use the 1818VSL ASIO driver. But if there's a way to use that driver in Csound and direct the audio signal to the lightpipe, I wouldn't know what it would be. Possibly by setting nchnls=16 and then using outc 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, asigL, asigR? What do you think?
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

Tarmo Johannes-2

I wonder is there something like jack for windows? (Or therr is jack for wondows?) Jack is a audio server used mostly on linux and osx - it can connect various programs between themselves and to physical outputs. Csound has good jack support.
Shooting in the dark but that could be a possible solution.
Hardly it helps though...

Tarmo

28.03.2016 20:35 kirjutas kuupäeval "Jim Aikin" <[hidden email]>:
Using that command line gives me the same result I uploaded as a screenshot
in my first message -- no lightpipe. Curiously, the AudioBox 1818VSL line
outs are all listed twice. Switching Csound (back in CsoundQt now) to dac15,
which is the AudioBox ASIO driver, I still get sound through the line out
1/2, nothing to do with lightpipe.

The Asio4all control panel also can't see the lightpipe. I rather doubt it's
using portaudio, but I suppose it might be.

In any event, Reason can see and use the lightpipe when I ask it to use the
1818VSL ASIO driver. But if there's a way to use that driver in Csound and
direct the audio signal to the lightpipe, I wouldn't know what it would be.
Possibly by setting nchnls=16 and then using outc 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, asigL, asigR? What do you think?



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187p5748202.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

rorywalsh
It's a bit of a workaround, but you could host your Csound instruments as VSTs within a host that does give access to the lightpipe output? Reason won't host VSTs, but perhaps Reaper or another DAW can interface with it? Tarmo's suggestion to use Jack is also a good avenue to explore although I've never used it myself on Windows.

On 28 March 2016 at 18:42, Tarmo Johannes <[hidden email]> wrote:

I wonder is there something like jack for windows? (Or therr is jack for wondows?) Jack is a audio server used mostly on linux and osx - it can connect various programs between themselves and to physical outputs. Csound has good jack support.
Shooting in the dark but that could be a possible solution.
Hardly it helps though...

Tarmo

28.03.2016 20:35 kirjutas kuupäeval "Jim Aikin" <[hidden email]>:
Using that command line gives me the same result I uploaded as a screenshot
in my first message -- no lightpipe. Curiously, the AudioBox 1818VSL line
outs are all listed twice. Switching Csound (back in CsoundQt now) to dac15,
which is the AudioBox ASIO driver, I still get sound through the line out
1/2, nothing to do with lightpipe.

The Asio4all control panel also can't see the lightpipe. I rather doubt it's
using portaudio, but I suppose it might be.

In any event, Reason can see and use the lightpipe when I ask it to use the
1818VSL ASIO driver. But if there's a way to use that driver in Csound and
direct the audio signal to the lightpipe, I wouldn't know what it would be.
Possibly by setting nchnls=16 and then using outc 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, asigL, asigR? What do you think?



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187p5748202.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

Jim Aikin
Good suggestion, Rory. I'd have to learn Cabbage to do that ... and also, I've been using Reason exclusively to capture all of my modular's audio. Switching to Cubase at this point in order to run a VST is possible, but it would be a headache.

I think we all wish Propellerhead would add VST support to Reason, but it will never happen. Their revenue model won't allow it. And I can't use ReWire to run Cubase and Reason in sync, because Reason 8.3 is 64-bit and my install of Cubase is 32-bit. I can't upgrade Cubase to 64-bit without tossing out or reinstalling a bunch of VST's that require 32-bit. Another big headache.

I can't help thinking it's weird that PortAudio won't recognize audio I/O buses that are right there in the system. But I'm totally not savvy about such things.
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Audio Output Buses Not Visible

rorywalsh
For all I know PortAudio is more than capable of interfacing with these devices, but I just don't know enough about it. Regarding your 32/64 bit woes, you could use Reaper 64-bit to host your VST plugins. It has ReWire support as far as I know. And it's about as lightweight as a DAW can get without compromising any functionality. 

On 28 March 2016 at 20:37, Jim Aikin <[hidden email]> wrote:
Good suggestion, Rory. I'd have to learn Cabbage to do that ... and also,
I've been using Reason exclusively to capture all of my modular's audio.
Switching to Cubase at this point in order to run a VST is possible, but it
would be a headache.

I think we all wish Propellerhead would add VST support to Reason, but it
will never happen. Their revenue model won't allow it. And I can't use
ReWire to run Cubase and Reason in sync, because Reason 8.3 is 64-bit and my
install of Cubase is 32-bit. I can't upgrade Cubase to 64-bit without
tossing out or reinstalling a bunch of VST's that require 32-bit. Another
big headache.

I can't help thinking it's weird that PortAudio won't recognize audio I/O
buses that are right there in the system. But I'm totally not savvy about
such things.



--
View this message in context: http://csound.1045644.n5.nabble.com/Audio-Output-Buses-Not-Visible-tp5748187p5748213.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here