Author |
Topic: After restart won't map till midi ports changed (Read 6444 times) |
|
bmp02
New Member
MIDI-OX Rules!
Posts: 5
|
 |
After restart won't map till midi ports changed
« on: Nov 13th, 2013, 11:54am » |
 Quote  Modify
|
Hi there,
Got some weird stuff going on here. Not sure if this is a MIDI-OX or MIDI Yoke problem, so just posting it here.
I'm using MIDI-OX to transform midi info coming out of Cubase.
Cubase -> MIDI Yoke -> MIDI-OX -> Any midi port
Literally everytime that Cubase is restarted, mapping won't work. Midi data is coming in MIDI-OX, and going out exactly the same. Map file is selected though, also manual mapping @ translation map won't make a difference - Data goes out exactly the same as it came in.
Spent quite a few hours figuring this out, including re-installing both OX & Yoke, but the only way I can fix this, is by changing MIDI Yoke to another port in Cubase (out) and OX (in).
Restart again, same problem, change Yoke port, works again.
Any idea what this is or how to fix it?
It's like Cubase is sending data (although I can't seem to find anything weird) that stops OX from mapping every time.
The other way around (mixer -> Cubase), no problem there.
Thanks for your time!
|
| « Last Edit: Nov 13th, 2013, 11:54am by bmp02 » |
 IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1030
|
|
Re: After restart won't map till midi ports change
« Reply #1 on: Nov 13th, 2013, 11:07pm » |
Quote Modify
|
Hi
Why are you closing Cubase or is Cubase crashing?
I can't reproduce the problem in WinXP with Live or Sonar.
If I close the Sonar and restart it and reload the song it is fine.
You have to be a bit careful with MidiYoke and Midi Thru (echo) on a track in your DAW.
If MidiYoke detects a loop it will shut down.
So if you have a track that is listening to all the Midi input devices (it is the first option in Sonar and being lazy I often select it) then when you put out some Midi data it will come back in and a loop will be detected and the port shut off.
This can also cause instability in your DAW and may make it crash.
This is even true of the usually very stable Sonar.
All the best
Royce
|
|
IP Logged |
|
|
|
bmp02
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: After restart won't map till midi ports change
« Reply #2 on: Nov 14th, 2013, 6:26am » |
Quote Modify
|
Thanks for your reply!
Cubase isn't crashing, just have to shut down end of the day and startup the next, that's why I noticed, and started testing with restarting 
I wasn't actually testing with a midi track, but with the Cubase mixer instead, translating channel mute/unmute messages to a format which my external mixer understands.
This morning, I've tested with a midi track, made sure no midi echo would occur (no midi input selected). But things even get more messy now.
Tried to transform modulation wheel midi into all zeroes (ctrl 1, 1-127 -> ctrl 1, 0). If I play recorded modulation wheel by Cubase, sometimes it maps to the required zero, sometimes it doesn't. If I play it real fast (much data out fast), mapping works in like 25% of the incoming midi. If I play slower, the percentage decreases. If I play it down real slow, it won't transform any data at all.
If I use my synth as midi input and move the modwheel by hand, no mapping. Also changing Yoke output in this test won't help at all.
Afterwards tested on Ableton. And here, surprisingly, no problems at all. Restarted multiple times, tried note-on/note-off, tried modwheel and other ctrl numbers, everything works just fine!
So seems to be a thing with Cubase.
Thing is, within a few weeks I'll update to a new version of Cubase, and on a fresh and new computer. So I don't think that further tests would make sense, especially because it seems so random.
Will post in a few weeks how everything's doing with Cubase SX7 on Windows 7, hope it'll work out as it should
|
|
IP Logged |
|
|
|
bmp02
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: After restart won't map till midi ports change
« Reply #3 on: Dec 12th, 2013, 4:20am » |
Quote Modify
|
And here I'm back, with a new computer, Windows 7 and new version of Cubase.
Problem seems almost gone now. Worked well for a week. Till yesterday a similar problem occurred.
Data from Cubase mapped via MIDI-OX to Mixer worked well, but data from Mixer mapped via MIDI-OX to Cubase somehow didn't.
No problem shown in MIDI-OX, but somehow Cubase doesn't receive it, or doesn't receive it in the right way. Which results in nothing happening when it should.
Just like in my first post, changing the virtual midi port to another one in MIDI-OX as well as in Cubase, solves the problem. At least for some time it does.
---
Must say that, because MIDI Yoke doesn't work in 64bit, I've had to change it for LoopBe. Because I still have kind of a similar problem like I had before the computer and virtual midi ports changes, I assume the problem lies somewhere within MIDI-OX, but I'm not sure.
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender:
Posts: 1030
|
|
Re: After restart won't map till midi ports change
« Reply #4 on: Dec 12th, 2013, 6:11pm » |
Quote Modify
|
"changing the virtual midi port to another one in MIDI-OX as well as in Cubase, solves the problem."
When you do this the Midi port is closed and reopened which usually flushes the buffers. Perhaps there is a problem there.
Does LoopBe also have the same problem?
Another virtual Midi patch cable, Maple, is only 32-bit .
http://www.tobias-erichsen.de/software/loopmidi.html
loopMIDI is also available in 64-bit.
Unlike all the others it isn't an installable driver so you need to run the program to create the virtual Midi cables.
Royce
|
| « Last Edit: Dec 12th, 2013, 6:13pm by Breath » |
IP Logged |
|
|
|
bmp02
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: After restart won't map till midi ports change
« Reply #5 on: Dec 13th, 2013, 7:35am » |
Quote Modify
|
Yes, both Yoke and Loopbe show the same problem.
Is there some kind of other way to quickly close and re-open those ports when problem occurs? Or a way to keep those buffers from "flushing"?
Thanks for helping out
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender:
Posts: 1030
|
|
Re: After restart won't map till midi ports change
« Reply #6 on: Dec 13th, 2013, 7:57am » |
Quote Modify
|
Perhaps you can tell me what you are doing exactly.
"Cubase -> MIDI Yoke -> MIDI-OX -> Any midi port "
What 'mixer' are you talking about?
What are the messages you are converting ?
Why can't Cubase put out the messages without MidiOx?
|
|
IP Logged |
|
|
|
bmp02
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: After restart won't map till midi ports change
« Reply #7 on: Dec 13th, 2013, 8:03am » |
Quote Modify
|
Mixer is Behringer DDX3216.
DDX and Cubase can perfectly communicate when it comes to fader movements, but the mute buttons is a total mismatch in communications. And that's where I need MIDI-OX for.
On DDX, DATA1 104 stands for mute on. DATA1 105 stands for mute off. DATA2 displays channel no.
For example, when I hit mute on channel 5, it will output as 104-5, mute off on channel 5 will be 105-5.
Cubase, on the other hand needs a different DATA1 number for every channel, and DATA2 input should always be 127 for on, 0 for off.
That's where mapping is needed!
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender:
Posts: 1030
|
|
Re: After restart won't map till midi ports change
« Reply #8 on: Dec 15th, 2013, 1:23am » |
Quote Modify
|
on Dec 13th, 2013, 8:03am, bmp02 wrote:Mixer is Behringer On DDX, DATA1 104 stands for mute on. DATA1 105 stands for mute off. DATA2 displays channel no.
|
|
What is the Midi message Note On, Note Off, CC 07 ??
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print