-
Notifications
You must be signed in to change notification settings - Fork 14
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
Audio stopped working on Linux Mint 22 #100
Comments
Hmm isn’t that functionality supposed to be built into the operating system
itself?
lör 21 sep. 2024 kl. 14:30 skrev DEFENSE MECHANISM ***@***.***
…:
It seems that I am not able to hear any audio output from the kit editor,
possibly due to the patcher selecting an incorrect default audio output? I
am still testing pipewire audio setup in Linux Mint, but it might be nice
to consider if there is an easy way to select an audio device, possibly via
commandline argument.
—
Reply to this email directly, view it on GitHub
<#100>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAY34O66WA4U7DDEKB2J43DZXVRH5AVCNFSM6AAAAABOTRUEMCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DAMRSG4YDGNA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
…by that i mean… if i have windows running, i can click a speaker icon and
select the output…
Is it different in Linux?
lör 21 sep. 2024 kl. 18:34 skrev Johan Kotlinski ***@***.***>:
… Hmm isn’t that functionality supposed to be built into the operating
system itself?
lör 21 sep. 2024 kl. 14:30 skrev DEFENSE MECHANISM <
***@***.***>:
> It seems that I am not able to hear any audio output from the kit editor,
> possibly due to the patcher selecting an incorrect default audio output? I
> am still testing pipewire audio setup in Linux Mint, but it might be nice
> to consider if there is an easy way to select an audio device, possibly via
> commandline argument.
>
> —
> Reply to this email directly, view it on GitHub
> <#100>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAY34O66WA4U7DDEKB2J43DZXVRH5AVCNFSM6AAAAABOTRUEMCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DAMRSG4YDGNA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
Yes, but the java app seems perhaps to ignore the default audio device. I've spent some time researching the issue but unfortunately haven't stumbled upon anything helpful yet. |
Not sure if this is related, but wav files exported from Reaper only play the first 1 second in kit manager, but the whole loop is actually saved to the kit. Other wav files seem fine, not quite sure what the difference would be. |
That seems weird. Could you attach such a wav file here to this issue and I
can have a look?
mån 23 sep. 2024 kl. 11:10 skrev John Hobson ***@***.***>:
… Not sure if this is related, but wav files exported from Reaper only play
the first 1 second in kit manager, but the whole loop is actually saved to
the kit.
Other wav files seem fine, not quite sure what the difference would be.
—
Reply to this email directly, view it on GitHub
<#100 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAY34O726RRWGWFGC45JJITZX7LJ5AVCNFSM6AAAAABOTRUEMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRXGYZTKMZRGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think I just figured it out. It's ok if exported as 16bit PCM wav, it's 24bit PCM wavs that it just plays first second. So there is as solution, probably not a priority to fix, if a fix is even needed. Links to download the 2 wavs: |
I tried adding the 24-bit sample and it worked just fine on my computer. |
Good to know. 16 bit is fine anyway, not like you need especially high quality source audio! I'm using pipewire, so might be something related to that. |
I was able to replace some of the code in Sound.java to use the "pulse" audio device and this is working for me. In the future it would be more ideal to implement this as a menu item, I may work on this and provide a pull request if I ever have enough free time. // Get the specific mixer (audio device) containing "M4" in its name
Mixer mixer = getMixerByName("pulse");
if (mixer == null) {
throw new LineUnavailableException("No audio device found containing 'pulse' in its name.");
}
// Get the Clip from the selected mixer
Clip clip = (Clip) mixer.getLine(new DataLine.Info(Clip.class, new AudioFormat(PLAYBACK_RATE, 16, 1, true, false))); |
It seems that I am not able to hear any audio output from the kit editor, possibly due to the patcher selecting an incorrect default audio output? I am still testing pipewire audio setup in Linux Mint, but it might be nice to consider if there is an easy way to select an audio device, possibly via commandline argument.
The text was updated successfully, but these errors were encountered: