View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009091ardourbugspublic2022-11-11 22:302022-11-27 00:41
ReporterBrank4 Assigned To 
PrioritynormalSeveritymajorReproducibilitysometimes
Status closedResolutionno change required 
PlatformLinuxOSOpenSUSE TumbleweedOS Version20221108
Product Version7.1 
Summary0009091: Start of looping clip resets MIDI instrument track
DescriptionWhen a clip restarts a loop (after Ardour has been closed and re-opened), the instrument selected from a soundfont for any given MIDI track gets reset to the soundfont's default instrument. If the channel is changed to a new instrument while playing, the new instrument will be used (and audible) until the clip loops, at which point the default instrument will be audible and the menu will show that the old instrument is configured.
Steps To ReproduceOn a MIDI track:
1. Ensure there is a Calf Fluidsynth or ACE Fluidsynth plugin
2. Select a soundfont
3. Change the instrument for channel 1 away from the default instrument for channel 1 on that soundfont
4. Record something with MIDI data
5. Bounce that recording, add it to the clips library
6. Add that clip to any slot for that track in the Clips editor
7. Play the clip (just to test that it works as expected)
8. Close Ardour
9. Re-open ardour
10. Play the clip again. The instrument will be reset to the default instrument on channel 1 of that soundfont. I.e. the bug is now observable
Additional Information- Persists between reboots
- I've only been able to test which channel 1 as the active channel
- Only the instrument for channel 1 gets reset (if I set the instrument for other channels, they do not get reset, though I haven't been able to test sending any midi data to other channels)

This is a somewhat evasive issue for me, but it's rather frustrating and it makes Ardour unusable for me until this is resolved since I rely on MIDI tracks.

On a positive note, I'm really enjoying clips and loops! Much appreciation to the team for that feature and the tool as a whole

Attachments are just to clarify the plugin(s) being used
Tagsclip, midi in

Activities

Brank4

2022-11-11 22:30

reporter  

2022-11-11-17:28:34.png (63,024 bytes)   
2022-11-11-17:28:34.png (63,024 bytes)   
2022-11-11-17:28:17.png (352,070 bytes)

paul

2022-11-20 05:45

administrator   ~0026912

THere's a button in the clip slot properties box to disable sending program changes, which is what is causing this. You have a clip/region with a program change in it, and every time it resets the program the synth (fluidsynth) is using.

Daniele1971

2022-11-24 23:02

reporter   ~0026940

Damn, i was about to do the same bugreport. IMHO should be off by default.

Brank4

2022-11-27 00:41

reporter   ~0026950

Thank you, Paul, this solved my problem. This can be closed.

Brank4

2022-11-27 00:41

reporter   ~0026951

Not a bug. From paul below:

> There's a button in the clip slot properties box to disable sending program changes, which is what is causing this. You have a clip/region with a program change in it, and every time it resets the program the synth (fluidsynth) is using.

Issue History

Date Modified Username Field Change
2022-11-11 22:30 Brank4 New Issue
2022-11-11 22:30 Brank4 File Added: 2022-11-11-17:28:34.png
2022-11-11 22:30 Brank4 File Added: 2022-11-11-17:28:17.png
2022-11-11 22:30 Brank4 Tag Attached: midi in
2022-11-11 22:31 Brank4 Tag Attached: clip
2022-11-20 05:45 paul Note Added: 0026912
2022-11-24 23:02 Daniele1971 Note Added: 0026940
2022-11-27 00:41 Brank4 Note Added: 0026950
2022-11-27 00:41 Brank4 Status new => closed
2022-11-27 00:41 Brank4 Resolution open => no change required
2022-11-27 00:41 Brank4 Note Added: 0026951