Page 1 of 1
Live stops receiving MIDI data from Remote SL and others
Posted: Wed Jan 09, 2008 3:28 am
by Geezus
This is a weird one...when I start a new project my midi controllers work fine (trigger finger, axiom 49, and remote sl zero control surface). However, sometimes it reaches a certain point in a project where live stops being able to receive MIDI data from any of them. I can hit keys and move sliders but live wont respond, it wont even blink the midi signal square at the top. The remote sl still receives data from live (i.e. it can still read parameters from plugins) but it cant control anything back. Once it has reached this point in Live, no midi will work in any project...even new ones. I have to restart Live to get things working again, but if I saved a project where the midi dropped out it will automatically drop the midi again when I load the project up and I have the same problem.
Anyone else know anything about this?
Posted: Wed Jan 09, 2008 5:40 am
by Timur
If you're using Live 7 on a Windows machine try the following for all of your USB midi devices (these usually do not come with native DirectMusic drivers):
- Go to Preference -> Midi
- Click on the small arrow left to the Midi port name
- Change "Port Type" from DirectMusic to MME
PS: Why am I the only one spreading the word about this around here? Isn't this the job of Ableton's staff?
Posted: Wed Jan 09, 2008 6:19 am
by tricil
On a Mac this still happens... lemme guess, you're playing with the XY pad on the SL?
that's what happens to me and Tone Deft.
seems to be a novation bug.
Posted: Wed Jan 09, 2008 1:54 pm
by LiquidFix
I'm having a problem with my remote sl zero where roughly every four measures live sends a sync messege to the sl which for some reason causes feedback, a CPU spike, and audible glitch/momentary stutter.
Posted: Wed Jan 09, 2008 2:29 pm
by Geezus
Timur wrote:If you're using Live 7 on a Windows machine try the following for all of your USB midi devices (these usually do not come with native DirectMusic drivers):
- Go to Preference -> Midi
- Click on the small arrow left to the Midi port name
- Change "Port Type" from DirectMusic to MME
PS: Why am I the only one spreading the word about this around here? Isn't this the job of Ableton's staff?
Thanks this seems to work, albeit a little buggy but still much better than it was before. Cheers!
Posted: Wed Jan 16, 2008 8:28 pm
by Alex
Thanks this seems to work, albeit a little buggy but still much better than it was before. Cheers!
Geezus, please give the latest Live 7.0.2 beta a try:
http://www.ableton.com/forum/viewtopic.php?t=82619
Since Live 7.0.2b2 there is a fix which should improve the behavior when using a MME MIDI port.
LiquidFix,
I do not know if you use Live on Window or not. If yes, please also try the latest beta and use MME instead of DirectMusic.
Regards,
/Alex
Somewhat the same Topic
Posted: Sat Jan 19, 2008 4:25 am
by Shae
So this topic is similar enough that I don't think it warrants the creation of a new "Topic". I have Live 7.01 installed on my computer. I have my KORG Microkontrol hooked up via USB to my computer and in the Prefs>MIDI Sync section this is what I see:
Control Surface Input Output
1. microcontrol None None (OR Microsoft GS
Wave SW Synth)
MIDI Ports
Output: microkontrol output (Microsoft GS Wave SW Synth)
Where it says "Input: None" the "none" is greyed-out so I can't change it no matter what I do. No input shows up in the MIDI Ports section.
No MIDI signals are recognized when i try to send patches from my KORG to Live and the indicator has never lit up...
What should I/can I do?
Posted: Sat Jan 19, 2008 4:21 pm
by Timur
The Padkontrol issue is nowhere close to the Remote issues of this post, but nevertheless make sure that your Korg drivers are installed properly. If you already installed the latest version then try uninstalling them and use the Microsoft Standard drivers first. If that works install the Korg drivers again.