-
-
Notifications
You must be signed in to change notification settings - Fork 31
Description
I successfully installed BYOD using flatpak like described here.
The application seems to start without any problem, but when I try to use it with JACK server I can't see anything related to BYOD in the "Readable Clients/Output Ports" column of QJackCtl application, even if I set "JACK" in the "Audio device type" field in "AUDIO/MIDI Settings" section (I also can't choose anything but "None" in "Input" and "Output" fields in the same section)
To Reproduce:
Steps to reproduce the behavior:
- Start Jack server using QJackCtl application
- Start BYOD using flatpak with command
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=BYOD com.chowdsp.BYOD - Configure BYOD to use JACK selecting "JACK" in the "Audio device type" field in BYOD's "AUDIO/MIDI Settings" section
- Click "Connect" in QJackCtl application
- See that BYOD doesn't appear in "Readable Clients/Output Ports" column
Expected behavior:
I would expect to find some reference to BYOD in the "Connect" section of QJackCtl, so I could use it in my signal chain with JACK
Screenshots:
Desktop:
- OS: AVLinux, kernel: 6.0.0-10.1-liquorix-amd64, output of
uname -a:Linux elaudio 6.0.0-10.1-liquorix-amd64 #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.0-6~mx21+1 (2022-11-30) x86_64 GNU/Linux - Version: 1.3.0
Copy Diagnostic Info:
Version: BYOD 1.3.0
Commit: 3562e3c on HEAD with JUCE version JUCE v7.0.10
Build: 14 Sep 2024 16:06 on cncf-x86-4.flathub.org with GNU-14.2.0
System: with Linux (64-bit) on 24 Core, 13th Gen Intel(R) Core(TM) i7-13700F
Plugin Info: Standalone running in Unknown running at sample rate 44.1 kHz with block size 512

