Hello, sorry if i do anything wrong posting this. My problem is not very big for me, still looks by y git feeling like kind of bug, therefore might be helpful if i report it for everyone else to solve it.
So, here is the situation:
Debian 12 stable, up to date.
Audacity 3.7.1 from flatpak.
Configured to start by script disabling any sound system beyond pure ALSA (for several reasons - forseenable and stable latencies including).
So here is the script (just in case cause i don’t think this is any kind of problem):
#!/bin/bash
systemctl --user stop pipewire pipewire-pulse
systemctl --user disable pipewire pipewire-pulse
systemctl --user stop pipewire.socket pipewire-pulse.socket
systemctl --user disable pipewire.socket pipewire-pulse.socket
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=audacity org.audacityteam.Audacity
systemctl --user enable pipewire.socket pipewire-pulse.socket
systemctl --user start pipewire.socket pipewire-pulse.socket
systemctl --user enable pipewire pipewire-pulse
systemctl --user start pipewire pipewire-pulse
This is all good, works pretty well as long as i managed to test it (mostly multitrack recording and real-time effects, not much more).
But when trying to apply pitch change by 2 halftones up on 11 track project, it starts to process it, and at progres of about 75% suddenly disapears saying nothing.
Doesn’t matter if i choose high quality or not.
Yet didn’t test on single track one by one, nor on other projects, but here in this single one particular it is quite repeatable.
Unfortunately this is all i know for now - any help with grabbing diagnostic data if needed will be appreciated, because i simply have no idea how to do that - tried some debug switches to flatpak with no luck.
Last idea that comes to my mind would be to use strace, but it will produce a flood of output - there should be other,better way to do that.
Should anyone find usefull more tests to be done on my site - I’ll do that willingly.
Cheers:)
Update: tested on the same project but single tracks one by one, and worked well.
So it looks like kind of limitation of stuff to be tuned up, but it is still quite weird, because I would assume, that when I’m selecting all the tracks and apply the effect, program does it one by one anyway (or does it…? )