jsynthlib-devel

[Jsynthlib-devel] two bugs

[federico <xa...@in...>]

1) the MKS7 driver i just developed, controls only one timbral part.
to get control of all three parts (chord,melody,bass), i have to create 
3 driver instances, with 3 different IDs and MIDICHANs.

so i created patches with ID 'MKS-7-B','MKS-7-M','MKS-7' (for the main 
part).
but when i save patchlib, close and reopen it, all sounds get remapped 
to the main id ('MKS-7').

i guess this ID is not stored in the file, so gets matched by the 
sysex_id of the driver...
or otherwise please enlighten me.

2) it happens sometimes that JSL stop receiving (or transmitting... i 
don't know) MIDI from the master keyboard.
i have to open Preferences->MIDI, make some change, undo it, and apply. 
this solves the problem.

i cannot give steps to reproduce the problem because it happen randomly.

thanks
-- 
Federico

Re: [Jsynthlib-devel] two bugs

[Brian <br...@ov...>]

>
>
>>
>> 2) it happens sometimes that JSL stop receiving (or transmitting... i 
>> don't know) MIDI from the master keyboard.
>> i have to open Preferences->MIDI, make some change, undo it, and 
>> apply. this solves the problem.
>

What platform are you using? (Operating System / Java Version / Midi 
Provider?

Thanks

Re: [Jsynthlib-devel] two bugs

[Hiroo H. <hir...@co...>]

Federico,

federico> 1) the MKS7 driver i just developed, controls only one timbral part.
federico> to get control of all three parts (chord,melody,bass), i have to create 
federico> 3 driver instances, with 3 different IDs and MIDICHANs.

I don't understand why you have to create 3 driver instances.  Why one
driver cannot handle those three parts?
-- 
Hiroo Hayashi

Re: [Jsynthlib-devel] two bugs

[Brian <br...@ov...>]

Hiroo Hayashi wrote:

>Federico,
>
>federico> 1) the MKS7 driver i just developed, controls only one timbral part.
>federico> to get control of all three parts (chord,melody,bass), i have to create 
>federico> 3 driver instances, with 3 different IDs and MIDICHANs.
>
>I don't understand why you have to create 3 driver instances.  Why one
>driver cannot handle those three parts?
>  
>

My understanding is that we have a driver / editor  that would work with 
a Roland Juno 106.
The MKS7 is actually three Juno 106's in one box. Each has its own midi 
channel, and oddly,
its own independant patch storage. It is no different than having three 
seperate devices
on the midi port, because they have no ability to communicate or share 
information with each other.

Brian

Re: [Jsynthlib-devel] two bugs

[federico <xa...@in...>]

Brian wrote:

> Hiroo Hayashi wrote:
>
>> Federico,
>>
>> federico> 1) the MKS7 driver i just developed, controls only one 
>> timbral part.
>> federico> to get control of all three parts (chord,melody,bass), i 
>> have to create federico> 3 driver instances, with 3 different IDs and 
>> MIDICHANs.
>>
>> I don't understand why you have to create 3 driver instances.  Why one
>> driver cannot handle those three parts?
>>  
>>
>
> My understanding is that we have a driver / editor  that would work 
> with a Roland Juno 106.
> The MKS7 is actually three Juno 106's in one box. Each has its own 
> midi channel, and oddly,
> its own independant patch storage. It is no different than having 
> three seperate devices
> on the midi port, because they have no ability to communicate or share 
> information with each other.
>
> Brian

you are right.
(i add only one word) it is like to have three different synths, each 
has its own midi channel, and they all have the same MIDI-SysEx header 
<this is the problem

bye
-- 
Federico