User Forum    :: Powered by YaBB
  « MIDI-OX User Forum - The side effect of loading presets (6.5RC3) »
Welcome, Guest. Please Login or Register.
Jun 20th, 2024, 3:02pm


Home Home Help Help Search Search Members Members Login Login Register Register


   MIDI-OX User Forum
   MIDI-OX
   MIDI-OX Beta Bugs
(Moderator: Jamie OConnell)
   The side effect of loading presets (6.5RC3)
« Previous topic | Next topic »
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print
   Author  Topic: The side effect of loading presets (6.5RC3)  (Read 3935 times)
not2good2c
Member
**





   


Gender: male
Posts: 46
The side effect of loading presets (6.5RC3)
« on: Aug 28th, 2002, 1:46pm »
Quote Quote Modify Modify

Loading the preset 'mX>ed':
VERBOSE DEVICE INFORMATION
 OUT:  3) EDI input; 1 [MIDI Yoke Junction:  1]
which is only supposed to remove MIDI-OX Events from the editor’s input also removes Port Data Maps from the keyboard and the editor’s output.
 
DEVICE INFORMATION
 IN:   1) KEY [DS-XG MPU401 IN]
 IN:   3) EDI output; 2 [MIDI Yoke Junction:  2]
 OUT:  2) SYN [DS-XG Synthesizer]
   In: 1) KEY [DS-XG MPU401 IN]
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
     Port Data Map: "[v1-111=10-127].oxm"
   In: 3) EDI output; 2 [MIDI Yoke Junction:  2]
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
     Port Data Map: "[NRPN-cc].oxm"
   In: MIDI-OX Events
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
 OUT:  3) EDI input; 1 [MIDI Yoke Junction:  1]
   In: MIDI-OX Events
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
 Loaded Preset: 'mX>ed'
     14477 KEY SYN   176     0     0    1  ---  CC: Bank MSB      
     14479 KEY SYN   176    32     0    1  ---  CC: Bank LSB      
 DEVICE INFORMATION
 IN:   1) KEY [DS-XG MPU401 IN]
 IN:   3) EDI output; 2 [MIDI Yoke Junction:  2]
 OUT:  2) SYN [DS-XG Synthesizer]
   In: 1) KEY [DS-XG MPU401 IN]
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
   In: 3) EDI output; 2 [MIDI Yoke Junction:  2]
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
   In: MIDI-OX Events
     Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,RT,Sx
 OUT:  3) EDI input; 1 [MIDI Yoke Junction:  1]
IP Logged
Jamie OConnell
Administrator
*****






   
WWW Email

Gender: male
Posts: 2027
Re: The side effect of loading presets (6.5RC3)
« Reply #1 on: Aug 28th, 2002, 3:52pm »
Quote Quote Modify Modify

Presets don't ever 'remove' items, although it may seem like that. Presets need to contain the full definition of what they represent.
 
When you load the 'mX>ed' preset manually in MISI Devices, does it contain the "[NRPN-cc].oxm" map?
 
IP Logged

--Jamie
Music is its own reward.

not2good2c
Member
**





   


Gender: male
Posts: 46
Re: The side effect of loading presets (6.5RC3)
« Reply #2 on: Aug 28th, 2002, 7:10pm »
Quote Quote Modify Modify

In MIDI Devices the preset 'mX>ed' looks like this:
 
- EDI input; 1
     MIDI-OX Events
 
I have another preset called 'mo>ed' that looks like this:
 
- EDI input; 1
     - MIDI-OX Events
     - Channels
     - System
 
Am I wrong when I think that they should only influence the Output labeled EDI input?
« Last Edit: Aug 28th, 2002, 7:15pm by not2good2c » IP Logged
Jamie OConnell
Administrator
*****






   
WWW Email

Gender: male
Posts: 2027
Re: The side effect of loading presets (6.5RC3)
« Reply #3 on: Aug 29th, 2002, 3:20pm »
Quote Quote Modify Modify

I think I see the confusion.  Although a Preset used as a Patch Map can't open or close any new MIDI Ports, it still needs to describe the routing completely.  In other words, if you have  the following devices open:
 
IN:   1) KEY [DS-XG MPU401 IN]  
IN:   3) EDI output; 2 [MIDI Yoke Junction:  2]  
OUT:  2) SYN [DS-XG Synthesizer]  
OUT:  3) EDI input; 1 [MIDI Yoke Junction:  1]  
 
and a preset which connects only:
 
OUT:  3) EDI input; 1 [MIDI Yoke Junction:  1]
     MIDI-OX Events  
     - Channels  
     - System  
 
Then after the Patch Map is triggered, that should be your only connection -- regardless of your original routing.
 
If your preset has only  
OUT:  3) EDI input; 1 [MIDI Yoke Junction:  1]
     MIDI-OX Events  
 
It is the same as NO connection at all (no channels or system data will be passed).  MIDI-OX detects this and does not make a connection.
« Last Edit: Aug 29th, 2002, 3:21pm by Jamie OConnell » IP Logged

--Jamie
Music is its own reward.

not2good2c
Member
**





   


Gender: male
Posts: 46
Re: The side effect of loading presets (6.5RC3)
« Reply #4 on: Aug 29th, 2002, 7:25pm »
Quote Quote Modify Modify

Just asking:
Does it mean that I would have to practically duplicate the original preset to which I’m planning to apply a patch map and that I can’t apply a patch map to all different presets which include an Output (in my case labeled according to the external input to which it is connected) under which I’d like to switch MIDI-OX Events ON/OFF? The only problem is that this simple preset removes Data Maps from the Inputs under other Outputs (I discovered this when the velocities dropped – I had lost my [v1-111=10-127].oxm)… the way I see it is that such universal presets can still be loaded without side effects when other Outputs (seen from MIDI-OX) don’t include Data Maps.
 
This could be a little bug:
Although MIDI-OX Events can be completely removed in MIDI Devices, the port ‘MIDI-OX Events’ is back there when the MIDI Devices dialog is opened again (without Channels and System though). In Verbose Device Information the text ‘MIDI-OX Events’ is also gone – the way it should be… no?
IP Logged
Jamie OConnell
Administrator
*****






   
WWW Email

Gender: male
Posts: 2027
Re: The side effect of loading presets (6.5RC3)
« Reply #5 on: Aug 29th, 2002, 7:53pm »
Quote Quote Modify Modify

After looking at the actual code, I realize it doesn't work quite like I said.  Currently, connections that aren't addressed (defined) in the preset are left alone, except that the data maps are removed as an end result.
 
The original design was to work as I said before: Connections that weren't listed in the routing preset were not restored.  I am starting to sense that that is not an ideal situation.  
 
Would people prefer it if we retained connections not listed in the Routing Preset including the Data Map?  Or would it be better to remove all connections (and maps) not listed?  I am going to have to do one or the other within the next day, and I am leaning towards the former (less risky).  Maybe it ultimately could be a global option, but not for this release.
 
[Later On...]  I have decided for now, to retain connections and maps not listed or addressed in the preset.  I will also update the HTML help file about this.  I will issue another RC tonight.
 
Quote:
This could be a little bug:  
Although MIDI-OX Events can be completely removed in MIDI Devices, the port ‘MIDI-OX Events’ is back there when the MIDI Devices dialog is opened again (without Channels and System though).

 
I believe that would be possible, but since it's meaningless and harmless, I am not going to worry about it too much.  When you remove the Channels and System for an input device we don't immediately remove the device connection either, but it still is logically removed.
« Last Edit: Aug 29th, 2002, 10:06pm by Jamie OConnell » IP Logged

--Jamie
Music is its own reward.

Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print

« Previous topic | Next topic »


MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1!
YaBB © 2000-2003. All Rights Reserved.