Author |
Topic: Slight lag in datamap loading? (Read 471 times) |
|
jamos
New Member
MIDI-OX Rules!
Posts: 7
|
 |
Slight lag in datamap loading?
« on: Feb 22nd, 2024, 3:36pm » |
 Quote  Modify
|
I am using a patch map in combination with a set of data maps. These data maps, in addition to transposing, filtering, etc., also send out patch changes to other instruments when I change a patch on my master instrument. Unfortunately, there is apparently an occasional lag before the new data map kicks in; the patch changes that are sent are from the previous data map. This only happens maybe once in every 8 occurrences; but it does happen.
Des anyone have any thoughts on why this happens, or how to work around it? (I am trying to train myself to hit the patch button twice on my master instrument, but that's not ideal.)
|
|
 IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1014
|
|
Re: Slight lag in datamap loading?
« Reply #1 on: Feb 26th, 2024, 5:27pm » |
Quote Modify
|
Hi
this sounds a bit tricky.
I would turn on logging (File / Log... ) and try to generate the error.
When it occurs turn off the logging (File / Log... )
This closes the file so you can read it.
Open it up in a text file reader. NotePad+ etc
Look towards the end and see if you can see what triggered the error.
Let me know how you get on.
All the best
Ryoyce
|
|
IP Logged |
|
|
|
jamos
New Member
MIDI-OX Rules!
Posts: 7
|
|
Re: Slight lag in datamap loading?
« Reply #2 on: Feb 26th, 2024, 7:24pm » |
Quote Modify
|
Excellent suggestion! But, as I would almost expect - when I enable logging, the problem seems to go away. Of course it's intermittent, so I will probably need to run this for a few days to see what happens.
Thanks for the suggestion -
|
|
IP Logged |
|
|
|
jamos
New Member
MIDI-OX Rules!
Posts: 7
|
|
Re: Slight lag in datamap loading?
« Reply #3 on: Feb 27th, 2024, 2:33pm » |
Quote Modify
|
Well, after much pulling of hair and gnashing of teeth, I finally have data. When I turned logging off, the problem returned immediately, so I used the copy functions of the monitor windows to capture this:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
Input:
838981 Hyd -- 176 0 0 1 --- CC: Bank MSB
838981 Hyd -- 176 32 18 1 --- CC: Bank LSB
838981 Hyd -- 192 9 --- 1 --- Program Change << Loads "Bloodhounds"
839029 Hyd -- 178 7 0 3 --- CC: Volume
839039 Hyd -- 178 7 4 3 --- CC: Volume
839046 Hyd -- 178 7 16 3 --- CC: Volume
839054 Hyd -- 178 7 28 3 --- CC: Volume
839062 Hyd -- 178 7 41 3 --- CC: Volume
839071 Hyd -- 178 7 53 3 --- CC: Volume
839082 Hyd -- 178 7 66 3 --- CC: Volume
839091 Hyd -- 178 7 78 3 --- CC: Volume
839100 Hyd -- 178 7 82 3 --- CC: Volume
841085 Hyd -- 176 0 0 1 --- CC: Bank MSB
841085 Hyd -- 176 32 18 1 --- CC: Bank LSB
841085 Hyd -- 192 13 --- 1 --- Program Change << Loads "Kill the Light"
841121 Hyd -- 177 7 21 2 --- CC: Volume
841126 Hyd -- 177 7 36 2 --- CC: Volume
841131 Hyd -- 177 7 52 2 --- CC: Volume
841135 Hyd -- 177 7 68 2 --- CC: Volume
841137 Hyd -- 177 7 84 2 --- CC: Volume
841142 Hyd -- 177 7 99 2 --- CC: Volume
841148 Hyd -- 177 7 105 2 --- CC: Volume
1131756 Hyd -- 176 0 0 1 --- CC: Bank MSB
1131756 Hyd -- 176 32 18 1 --- CC: Bank LSB
1131756 Hyd -- 192 13 --- 1 --- Program Change << Loads "Kill the Light"
1131805 Pro -- 180 123 0 5 --- CC: All Notes Off
1131805 Pro -- 180 123 0 5 --- CC: All Notes Off
Output:
Loaded Map: 'Bloodhounds.oxm'
838985 Hyd Pro 196 11 --- 5 --- Program Change
838985 Hyd Emu 191 32 1 16 --- CC: Bank LSB
838985 Hyd Emu 207 8 --- 16 --- Program Change
839029 Hyd Pro 180 7 0 5 --- CC: Volume
839039 Hyd Pro 180 7 4 5 --- CC: Volume
839046 Hyd Pro 180 7 16 5 --- CC: Volume
839054 Hyd Pro 180 7 28 5 --- CC: Volume
839062 Hyd Pro 180 7 41 5 --- CC: Volume
839071 Hyd Pro 180 7 53 5 --- CC: Volume
839082 Hyd Pro 180 7 66 5 --- CC: Volume
839091 Hyd Pro 180 7 78 5 --- CC: Volume
839100 Hyd Pro 180 7 82 5 --- CC: Volume
Loaded Map: 'Kill the Light.oxm'
841089 Hyd Pro 196 11 --- 5 --- Program Change << Same program change as "Bloodhounds"
841089 Hyd Emu 191 32 1 16 --- CC: Bank LSB
841089 Hyd Emu 207 8 --- 16 --- Program Change
841121 Hyd Pro 180 7 21 5 --- CC: Volume
841126 Hyd Pro 180 7 36 5 --- CC: Volume
841131 Hyd Pro 180 7 52 5 --- CC: Volume
841135 Hyd Pro 180 7 68 5 --- CC: Volume
841137 Hyd Pro 180 7 84 5 --- CC: Volume
841142 Hyd Pro 180 7 99 5 --- CC: Volume
841148 Hyd Pro 180 7 105 5 --- CC: Volume
Loaded Map: 'Kill the Light.oxm'
1131760 Hyd Pro 196 16 --- 5 --- Program Change << Correct program change
1131760 Hyd Emu 191 32 1 16 --- CC: Bank LSB
1131760 Hyd Emu 207 5 --- 16 --- Program Change
In case this is not self-explanatory... this is when transitioning between patches for two different songs, "Bloodhounds" and "Kill the Light". The first time I select "Kill the Light", the patch message for "Bloodhounds" is sent; the second time, the correct message is sent. This is not consistent; it can happen between any two songs. Or not.
Note that, the first time the Hydrasynth sends its program message, it sends some initial CC data; the second time the same patch is selected, it does not. I don't think this is affecting anything because that CC data is sent well after the patch change stuff has settled down.
Thoughts?
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender:
Posts: 1014
|
|
Re: Slight lag in datamap loading?
« Reply #4 on: Mar 6th, 2024, 9:49pm » |
Quote Modify
|
Intermittent errors as you well know are a pain.
I'm not sure why you are sending Bank MSB LSB and PC to change Patch Map unless you are passing this on to another synth.
Are you wanting to change the datamap and the new datamap converts the patch changes for the Pro and Emu?
Are you sending the Patch change through the new map (box at bottom of the Patch map dialog)?
You can always just make a list of lines in a single datamap that will perhaps do what you want to do.
Use "Pass original value on..." in the line editor so multiple lines will be affected/converted.
Hyd ->PC9 MOx Datamap ->... Lines only respond to PC9
Emu Bank change (MSB or LSB or Both) and PC8 (3 datamap lines)
Pro PC7 (1 data line)
Hyd ->PC23 MOx Datamap ->...Lines only respond to PC23
Emu Bank change (MSB or LSB or Both) and PC1 (3 datamap lines)
Pro PC17 (1 data line)
etc
for as many lines as you need (I think, I have no idea what the max is)
After you have done all the Patch changes you need and you need some other filtering use
Hyd ->PC68 MOx Patchmap ->... load different datamap for the second set or to do some tricky filtering etc.
Hyd ->PC0 MOx Patchmap ->... loads the first datamap
I know the function says "Patch Map", but the many lined datamap might be a better choice.
Let me know how you get on.
All the best
Royce
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print