Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unability to leave the jack ports unconnected #140

Open
jpcima opened this issue Nov 22, 2016 · 5 comments
Open

Unability to leave the jack ports unconnected #140

jpcima opened this issue Nov 22, 2016 · 5 comments
Milestone

Comments

@jpcima
Copy link

jpcima commented Nov 22, 2016

When the jack stream is instanciated, the ports of the program are connected with those of the audio system. Depending on the kind of application, the developer may or may not desire this.

This is desirable, for instance, in a media player. In a musical application, it am pretty sure it goes against standard practice of Linux audio. It is common to let the user connect the program as he wishes, and let patchbay management persist the connections outside the program.

It appears there currently is no way to disable connection, beside commenting two jack_connect calls in jack.c and recompiling.

I believe it would be useful, while preserving default behavior, to introduce a flag to inihibit the automatic connection of ports on the Jack backend.

In the past a few people and I have requested a similar feature in the rtaudio library, which seems unfortunately to have fallen into deaf ears. I would appreciate a similar option in libsoundio which I believe is a better sound library overall.

@andrewrk
Copy link
Owner

Can you help me understand, what would be the utility in starting a SoundIoOutStream and not connecting to the JACK ports? What would you expect to happen? If you didn't want to connect to a JACK port, why would you call soundio_outstream_start?

@jpcima
Copy link
Author

jpcima commented Nov 22, 2016

I use the Qjackctl software to manage a jack audio environement, which includes the connection manager. A similar software is Patchage.
Take a typical linux softsynth, like Zynaddsubfx. Start the software, and you obtain a pair of output ports, unconnected. You can connect by using the audio connection tab of Qjackctl. Then, you may save this connection, also in Qjackctl, so it comes back automatically next time.

To make the connection automatic messes with this workflow, and the software patchbay cannot be used normally. The unconvenience is not big on the normal computer with a stereo soundcard, but it becomes in a studio configuration when you have several audio ports and routing necessary.
I hope this clarifies, if not please ask.

@andrewrk
Copy link
Owner

OK I understand now. There are 2 components here, the ports that libsoundio outputs audio to, and the fact that we can connect these ports to ports that will make the sound come out of system speakers.

It makes complete sense that you would want to only provide sound on these ports and not necessarily connect them to the system outputs.

@andrewrk andrewrk added this to the 2.0.0 milestone Nov 22, 2016
@andrewrk
Copy link
Owner

Hopefully I can tackle this, and some other issues this weekend. We're due for a release soon.

@jpcima
Copy link
Author

jpcima commented Nov 22, 2016

OK I can propose a push request soon since it's a trivial bit of development.
Like a boolean flag to add to the stream structure that takes effect in the open function, do you think the idea is good API wise?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants