On 10/09/2015 06:02, Tom Lechner wrote:
> Thanks for the response!
>
> 1...
> Say you have 2 (vertical) tracks. Each has one segment. Both tracks use
> the same instrument and play back to the same midi channel. In the first
> track, the segment starts at time 0. In the second track, the segment
On 10/09/2015 10:42, Abrolag wrote:
[...]
>> [...]
>
> Not certain about this, but I think RG sends a 'reset all controllers' per
> track. I've a suspicion it does this when it sees the first segment of the
> track. If I'm right putting a dummy segment at the start of the track should
> fix it.
>
> On 10/09/2015 06:02, Tom Lechner wrote:
>> Thanks for the response!
>>
>> 1...
>> Say you have 2 (vertical) tracks. Each has one segment. Both tracks use
>> the same instrument and play back to the same midi channel. In the first
>> track, the segment starts at time 0. In the second track, the
>>
>> 3. In matrix mode, it is very easy to select and move around notes, but
>> if you have ranges to remove, the controller inputs very easily get out
>> of sync. I end up deleting all the sustain pedal events, and rerecording
>> just the pedal.
>
> This is really a problem with having the
Hi,
I don't have accesss to my machine with rosegarden. But while you wait
for some ore authoritative sources of wisdom on the list...
> 1. If I have multiple tracks for the same piano instrument, if the
> tracks do not begin at the same time, when the later one starts, it
> causes a break in
On Wed, Sep 09, 2015 at 03:18:15PM +0200, Lorenzo Sutton wrote:
> I agree though that controller editing has always been suboptimal in
> rosegarden (e.g. it should be possible to select a bunch of controller
> and drag them etc. to make the thing really usable - see how e.g.
> qtractor does it)
