| 4 |
MIDI-OX / Mapping Questions / Re: re-mapping velocity "note off" event |
Oct 27th, 2024, 10:54pm |
| Started by Harken | Last post by Harken |
Thank you very much for taking the time to reply to my question. Your very detailed explanation helped me find that it was actually sending it as Note On (9) with a zero velocity. I was able to implement a mapping to change that message to a Note Off ( , however the plugin still did not work in the DAW. I eventually did find the problem with this situation. It turns out that the Alesis was sending both the Note On and Note Off events with the same exact MIDI timecode, which must have been interpreted by the DAW plugin to mean zero duration for the note. I was able to use MIDI-OX mapping to add a delay of 50ms to the Note Off time and it now works like a like a charm in the DAW. Thank you again for your help. |
 Reply  Quote  Notify of replies
|
| 5 |
MIDI-OX / Questions and Discussion / Re: feedback loop with both MIDI in and out connec |
Oct 27th, 2024, 12:22pm |
| Started by porkbot | Last post by porkbot |
Thank you so much for taking the time to answer this question.
Yes, the problem was having the input and output port connected in the MIDI Port Routing panel. I saw the routing panel, but didn't understand the significance of what I was seeing. Not sure why you would want to connect the input and output internally.
Another problem was that I was using "01" for channel 1 instead of "00"
So my Sysex command should have been:
F0 - System exclusive
40 - Kawai ID number
00 - Channel number
01 - Function number - All Tone Request
00 - Group Number - Synthesizer Group
01 - Machine ID number - K3m ID number
00 - [0] - 50 internal tones, [1] - 50 cartridge tones
F7 - EOX
But now everything is working seamlessly and I'm looking forward to using MIDI-OX for all things MIDI. |
|
Reply Quote Notify of replies
|
| 7 |
MIDI-OX / Mapping Questions / Re: Mapping a toggle button |
Sep 8th, 2024, 8:42pm |
| Started by zeroalpha_nz | Last post by Breath |
Hi
"If I use the script, do I not have to use the translation map to convert the note on/off to CC?
Currently the buttons on my midi controller are sending note on/off "
Any Midi message can be used.
As it is a toggle switch you are building you really only need to detect one message.
OK... I'm using Hexadecimal - in the js script, for hex, you will use "0x' then the number eg 0x90 is Note on message for channel 1
So
0x = this is a hex number
9 = NoteOn message
0 = channel (always 1 less than the 'musicians' channel value) ie channel is 0x0 to 0xF (0 to 15 decimal or 1 to 16 in normal Midi)
Middle C can have various values C3 or C4 being the more common. C4 is the default in MidiOx although it can be changed.
C1 is Key 18 (24 decimal) in the standard setup of MidiOx.
C1 can vary depending on the designers preference.
Press your C1 Key just to make sure what it is and Note down the number in MidiOx.
In the script you will be using that number.
There are multiple ways to trigger it from the keyboard.
NoteOn - hit it and forget... use 0x9c where c = (channel -1)
or you could hold down the note and release it at the right moment to trigger the event.
The safer version for live performance as you have already selected the key.
Remember there are two different Note Off messages...
You can use 0x8c with the Key and the Off Velocity
The other type of Key Off message (often used by Yamaha) is to use 0x9c (note on) then Key then 0x00 as the velocity.
Back to note on... Raw Note On to be changed
if (statraw == 0x90 && dat1 == 0x18 && dat2 > 0) // NoteOn is C 1 and as NoteOn velocity 0 is really NoteOff so you don't want that)
if you want to work in decimal just leave the '0x' out. 24 instead of 0x18
Hope that helps
Royce |
|
Reply Quote Notify of replies
|
| 8 |
MIDI-OX / Mapping Questions / Re: FC50 Foot controller |
Sep 7th, 2024, 6:33am |
| Started by Serial06757 | Last post by Serial06757 |
wow i got it to work, assiging ccs 100 to 107 onto the pedals of the Boss FV50 midi foot controller.
My DAW , Mixcraft recongnizes and i am able to f.i. assign the transport options.
One thing i dont manage : when using a learn function it recognizes the CC , but it doesnt change the min max. I am trying to set a virtual switch to on/ off. Is there a trick?
Many thx !!!
Ralph |
|
Reply Quote Notify of replies
|
| 9 |
MIDI-OX / Questions and Discussion / roland Td 8 module |
Sep 5th, 2024, 10:53pm |
| Started by ludwigz | Last post by ludwigz |
| Hi all, not sure if asking this question in this forum is ok but I have a roland td -8 module the screen is blank it was working good, I tried to update the firmware now it powers on with just a blank screen. wondering if anyone has a td-8 module syx backup file if that would work |
|
Reply Quote Notify of replies
|
| 10 |
MIDI-OX / Questions and Discussion / Re: Filter on selected MIDI outputs |
Aug 24th, 2024, 1:14am |
| Started by campbellr | Last post by Breath |
Hi
You can split and filter the data.
Just to make sure that the General data filter isn't removing the QtrFrame already click menu Options / Midi Filter...
One of the Lines in 'Filter' box is System Common.
Select the '...' button to the right of it and remove 'F1-MIDI Time Code Quarter Frame' line if it is in the list to filter.
Let's do a quick demo by using the MIDI-OX Event port as the 'Midi_In_Port' (bottom left) in the MIDI Port Routing window.
In the MIDI Port Routing window draw a connection from the MIDI-OX Event port (bottom left) to 'Midi_Out_All' (the one to get the F1 data) on the right side
and a connection from the MIDI-OX Event port to 'Midi_Out_No_QtrFrame' (No time code for this one)
Open menu View / MTC Transport
Any MTC settings should work. Press Play and let it run for a second or so.
Look at the Monitor Output window and you should see the F1 messages being sent to the two outputs. ie both connected but not filtered.
Look for the small square in the middle of the line connecting the MIDI-OX Event port to 'Midi_Out_No_QtrFrame' and click it.
In the new dialog, on the System box is 'Common(MTC)'.
Make sure it is NOT ticked (ie the QtrFame is not passed through this connection)
Back at MTC settings window press Play and let it run for a second or so.
Look at the Monitor Output window and you should see the F1 messages being sent to only the 'Midi_Out_All' output. ie connected but Time Code filtered.
If all is well redo the above with your 'Midi_In_Port' instead of the MIDI-OX Event port and don't forget to change the connection properties to filter out the Time Code.
All the best
Royce
|
|
Reply Quote Notify of replies
|
Return to the board index.
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register