Menu
▾
▴
[Rosegarden-bugs] [ rosegarden-Bugs-3114498 ] Using TPB controls to change device changes instrument to #1
|
From: SourceForge.net <no...@so...> - 2010-11-21 23:09:23
|
Bugs item #3114498, was opened at 2010-11-21 09:16 Message generated for change (Comment added) made by dmmcintyr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104932&aid=3114498&group_id=4932 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: sequencer Group: None Status: Open >Resolution: Accepted >Priority: 9 Private: No Submitted By: christian CHEVALIER (zwykx) >Assigned to: D. Michael McIntyre (dmmcintyr) >Summary: Using TPB controls to change device changes instrument to #1 Initial Comment: I'm trying to play one track with piano and another track with percussions. I have loaded PC51f soundfont into Qsynth. The problem is that after assigning the piano from bank 0:0 to the first track, when I select the 2nd track and check the percussion box in the instrument parameters area to access the percussion bank 1:0, this modification is applied to the first track too. The segments of each track are redrawn with dots instead of bars. Moreover, changing the instrument (inside the same bank) for one track assigns the same instrument to the other track. This problem does not happen with a studio built from scratch with Qsynth and is not easily reproducible. For me it could happen when my souncard Audigy MIDI device (or a Timidity device) is set too and after switching from Audigy (Timidity) to Qsynth instruments. ---------------------------------------------------------------------- >Comment By: D. Michael McIntyre (dmmcintyr) Date: 2010-11-21 18:09 Message: Now we're to the bottom of it. I'll accept it as a bug that changing the device using the Track Parameters controls also changes the instrument to #1, and this is confusing behavior. Without going into boring details, I have a pretty good idea what the technical reasons are for behaving this way. It was definitely the most sensible thing to do from a programming perspective. I will try to see if we can do something that is less sensible for developers, and more gentle to users. I think I probably can, but I am not very certain. I'll see what I can do. In the meantime, now you know what to look for. ---------------------------------------------------------------------- Comment By: christian CHEVALIER (zwykx) Date: 2010-11-21 14:22 Message: OK, you're right, I understand ! This is because when I switch from one device to another, the instrument assigned to the current track is reset to #1 so I have instrument #1 assigned to several tracks. Maybe it could help to avoid confusion by resetting (blanking) the instrument field when the device is changed. ---------------------------------------------------------------------- Comment By: D. Michael McIntyre (dmmcintyr) Date: 2010-11-21 13:28 Message: If applying a modification to track 2 has an impact on track 1, it is highly likely that both tracks have been assigned to play through the same instrument. The parameters in the "Instrument Parameters" (Paramètres d'instrument) box are for the instrument, not the track. Multiple tracks can be assigned to play through the same instrument, but the way Rosegarden presents all this does not make it all that clear that this is the case, and this has caused some confusion. It is most likely that you are simply confused, and that the problem you have reported is very easy to correct by adjusting the offending composition. It is possible that there is a real bug here too, but I would ask you to please double check the easy things first. You can tell which instrument a track is assigned to at a glance by looking for the #1, #2 and so forth. My bet is that you have more than one track assigned to #1, #2, etc., and that is why changing things in one place causes the change to happen elsewhere at the same time. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104932&aid=3114498&group_id=4932 |