#1786 autoload.rg problem with flatpak
When no midi device was found, it seems like importing a .midi file and then exporting back to .midi will either omit the instrument mapping or the tracks entirely. Inside Rosegarden, it seems like all tracks suddenly all map to the same instrument slot too.
I'm guessing this might be some conceptual problem, where if there are no midi devices it doesn't have configurable banks and then I guess it may just redirect all instruments on import to some dummy instrument...?
However, sometimes you don't even need audio to work on a track, and in that case all the instrument mappings shouldn't just collapse on import/export. So it would be nice if e.g. there was always a silent dummy general midi device available for which I can configure banks and where general midi imports will map the instruments too, so that the instrument mapping is retained on export.
I saw this using the rosegarden x64 flatpak release 26.06.
I'm having a hard time recreating this. For me, everything seems to work fine. Import a .mid and I get tracks connected to appropriate "General MIDI Device" channels. Export and I get the same. When importing a MIDI file, we use the autoload as our starting point. Perhaps that's not a good idea and we should instead have a hard-coded autoload for MIDI files in case the user has modified their autoload.
By "no midi device found", do you mean there are no MIDI playback devices in the Manage MIDI Devices window? Or there are no available MIDI outputs on that window (other than "[No Port]" which should always be available).
Have you modified your autoload? When you do a File > New, what is in the Manage MIDI Devices window's MIDI Playback section? The usual "General MIDI Device"? Or nothing?
Sorry, I should have attached a screenshot! This is how the midi device dialog looks like. This is the fresh install via flatpak, I never had it installed before on this machine so the settings should all be the defaults.
And here is how an imported track looks like. It's all just reset to some single synth instrument variant #1, and after exporting it back to midi without changing anything, the result plays in silenence which I assume means all the instrument assignments have gone out the window.
When I use File >New, the manage midi device section is still empty. So it's not like the import somehow cleared it out, it appears to always just be empty.
I wonder if it's some pipewire compatibility problem? Anyway, it would be nice if the instrument mappings would be retained even when pipewire somehow fails to offer a midi output.
It might be a problem with the flatpak. Somehow autoload.rg isn't working.
This should fix it:
If all went well, a File > New should now give you a General MIDI Device. Importing MIDI files should work normally now. If not, I'm expecting problems at step 7 or step 10 as they rely on resources that we store in the user directory.
We should probably track down why that flatpak appears to break autoload.rg. Where did you get it from?
ResourceFinder::getAutoloadPath()is the routine that unbundles autoload.rg (copies it to the user's home directory) and returns its path. autoload.rg usually ends up here:I got it via flathub, I also filed an issue here that might be related: https://github.com/flathub/com.rosegardenmusic.rosegarden/issues/24
That's actually two issues. Getting JACK running and this autoload.rg issue.
Pipewire might already offer a JACK server. Try launching rg without launching JACK. Look at the icons in the bottom right of the rg window. If you see a yellow triangle warning icon, click it and it will tell you whether it had problems finding JACK. If you see a green sound wave icon, JACK was found.
If you're getting the warning icon, you have two options: get pipewire's version of JACK working, or kill pipewire and run JACK itself.