-
Notifications
You must be signed in to change notification settings - Fork 20
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
PortAudio usage fails under PipeWire 1.0.3 #72
Comments
Interesting. I can run agbplay just fine with Pipewire 1.0.4. Does your sound card happen to have more than 2 output channels? The reason it's trying to use JACK is because agbplay explicitly asks for JACK. I implemented this a while a go to reduce latency while being under the impression that any system that does have JACK shouldn't have a problem with it. |
It... shouldn't. Everything is setup as "Analog Stereo".
I can get it to work by exporting a |
I'm not quite sure. Even if the sound card would have had more channels I would've expected portaudio would handle this just by using only the first two channels. If your sound card is mono only, I would not be surprised that this happens when using JACK. Can you check in the qjackctl Graph View that your sound card do indeed have two channels? Is it possible that agbplay tries to output to a different sound card than intended? In regards to the usage of ALSA: I can imagine what's causing it as agbplay uses a suggested minimum latency setting from portaudio, which I've seen is sometimes reported as 0.0 ms. Unfortunately I currently do not have much time to get into this, but in about a month that will change. |
The problem likely is that agbplay tries to connect to 'Voice Modulation Source'. If you use branch 'agbplay_v2' it will now output which device failed to open. |
I just get the following in the error window:
Nothing will play, it used to work just fine several years back.
I'm not even sure why it's trying to use JACK either. I can't find any options or environment variables to make PortAudio cooperate.
The text was updated successfully, but these errors were encountered: