Re: Device/Midi-Output mapping

ok. I pulled and built latest git and loaded about half-a-dozen pieces that

previously would have needed me to remap devices to their midi outs.

They all auto-mapped perfectly.

'great job. Thanks for the swift action.

Chuck.


On 03/07/2024 3:30 pm, Ted Felix wrote:
> This should be fixed in the latest git.  Please test.
>
>   We were avoiding assigning devices to ports that were in use. 
> Probably an ok thing to do when there are no matches at all, but not 
> good if a many-to-one configuration was intentional.
>
> Ted.
>
> On 7/1/24 1:00 PM, chuck elliot wrote:
>> My experience is that although RG is quite happy for you to map >1
>>
>> device to a single midi output, it won't remember these 
>> multi-mappings correctly
>>
>> over restarts and will allocate one device ok but the others will be 
>> null-mapped and will
>>
>> have to be manually re-assigned every time.
>>
>> I noticed this because I had created separate device files for my 
>> Korg-M3's various
>>
>> sets of banks. Ok, I can create a single device file for the M3 
>> (please see attached) but it seems
>>
>> that this might also be a problem for users with more devices than 
>> midi outputs seen by
>>
>> RG. I don't know if this is a bug but I would have thought that if 
>> it's legal to do this then RG ought to
>>
>> be able to remember it too?
>>
>> Chuck.
>>
>>
>>
>> _______________________________________________
>> Rosegarden-user mailing list
>> [email protected] - use the link below to 
>> unsubscribe
>> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>
>
> _______________________________________________
> Rosegarden-user mailing list
> [email protected] - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user


_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user