Advertisement
Hey guys,
I am dealing with a deep issue and need some help from a guru. Understanding this problem will require experience using a Novation Remote SL in tandem with Ableton Live.
My rig consists very simply of a Macbook 2 GHz Intel Core Duo running OS 10.4.11 with Live 6.0.1. It is connected via USB to a Novation Remote SL 25.
What I am attempting to do is this: I have a Live session with ten audio regions on one track in arrangement view (I am working only within arrangement view). I have placed a locator at the beginning of each region. My task is to assign each locator to a different button on my Remote SL. Very simple indeed.
On the Live side of this task, all this requires is entering MIDI map mode, and mapping the locators to the buttons on my Remote SL. This was easily accomplished.
On the Remote side, it is a bit more tedious. I have to create a new template in their template editor. My starting point for this process was a template that Novation provides, called 'MIDI CC Learn.syx', which is a template specifically for editing yourself.
All I really had to do was dictate what kind of MIDI messages those buttons would send. I decided to make them CC messages, with a default value of 0, a release/max value of 0, and a Press/min value of 127. I then designated the 'button type' as 'Momentary'.
So once I had done this, it was working pretty well: I press the button, and the cursor moves to the corresponding locator. And on the LCD display of my Novation, when I press the button, the value changes from 127 while I'm pressing the button, and goes back to 0 when I take my finger off it.
But there was an unexpected problem. For two of the buttons, when I pushed them the cursor would move to their locator, but then I could not execute any commands (such as 'play', or moving to another locator) for about 5 seconds. In other words, the cursor would be 'frozen' as that locator for about 5 seconds.
I noticed that on the LCD, when I would press either of these two problematic buttons, the CC value would stay at 127 for about 5 seconds, even after I took my finger off the button. Clearly, that was why the cursor was still locked at that locator after I took my finger off the button.
So it was time to troubleshoot. First, I double-checked that the template settings were the same for those two buttons as they were on other buttons. Indeed they were. Second, I considered that perhaps the buttons themselves were defective and getting 'stuck' in the pressed position. I tested this by assigning those locators to different buttons on my Remote SL. To my great surprise, the problem persisted.
So I figured there must be something in my Live session causing this to happen. I thus proceeded to change things in my Live session to see if I could figure out the problem. Here are the various things I tried:
1. I quit Live, turned off my Remote SL, shut down my computer, and then restarted everything. The problem persisted.
2. I deleted all the locators and the re-created them. The problem persisted.
3. I deleted all locators, then copy/pasted the two problematic audio regions to the end of my session, and deleted the originals in the middle of the session, where they were previously. I then created new locators. I found that the new copy/pasted duplicates of those original audio regions worked fine but, to my shock, now two other audio regions (and their locators) were behaving in the same problematic way!
4. I created a completely new Live session. I imported into it 10 random mp3s and arranged them as audio regions spaced across one track. I then assigned each a locator, and assigned them to buttons on my Remote SL. To my complete shock, I had the same problem!!! Two of the audio regions behaved in the same, problematic way!! Just for the heck of it, I once again reassigned the locators to different buttons on my Remote SL. Of course, just like before, it made no difference. The same two audio regions still behaved problematically.
Now I'm at a complete loss. Any help would be appreciated.
I am dealing with a deep issue and need some help from a guru. Understanding this problem will require experience using a Novation Remote SL in tandem with Ableton Live.
My rig consists very simply of a Macbook 2 GHz Intel Core Duo running OS 10.4.11 with Live 6.0.1. It is connected via USB to a Novation Remote SL 25.
What I am attempting to do is this: I have a Live session with ten audio regions on one track in arrangement view (I am working only within arrangement view). I have placed a locator at the beginning of each region. My task is to assign each locator to a different button on my Remote SL. Very simple indeed.
On the Live side of this task, all this requires is entering MIDI map mode, and mapping the locators to the buttons on my Remote SL. This was easily accomplished.
On the Remote side, it is a bit more tedious. I have to create a new template in their template editor. My starting point for this process was a template that Novation provides, called 'MIDI CC Learn.syx', which is a template specifically for editing yourself.
All I really had to do was dictate what kind of MIDI messages those buttons would send. I decided to make them CC messages, with a default value of 0, a release/max value of 0, and a Press/min value of 127. I then designated the 'button type' as 'Momentary'.
So once I had done this, it was working pretty well: I press the button, and the cursor moves to the corresponding locator. And on the LCD display of my Novation, when I press the button, the value changes from 127 while I'm pressing the button, and goes back to 0 when I take my finger off it.
But there was an unexpected problem. For two of the buttons, when I pushed them the cursor would move to their locator, but then I could not execute any commands (such as 'play', or moving to another locator) for about 5 seconds. In other words, the cursor would be 'frozen' as that locator for about 5 seconds.
I noticed that on the LCD, when I would press either of these two problematic buttons, the CC value would stay at 127 for about 5 seconds, even after I took my finger off the button. Clearly, that was why the cursor was still locked at that locator after I took my finger off the button.
So it was time to troubleshoot. First, I double-checked that the template settings were the same for those two buttons as they were on other buttons. Indeed they were. Second, I considered that perhaps the buttons themselves were defective and getting 'stuck' in the pressed position. I tested this by assigning those locators to different buttons on my Remote SL. To my great surprise, the problem persisted.
So I figured there must be something in my Live session causing this to happen. I thus proceeded to change things in my Live session to see if I could figure out the problem. Here are the various things I tried:
1. I quit Live, turned off my Remote SL, shut down my computer, and then restarted everything. The problem persisted.
2. I deleted all the locators and the re-created them. The problem persisted.
3. I deleted all locators, then copy/pasted the two problematic audio regions to the end of my session, and deleted the originals in the middle of the session, where they were previously. I then created new locators. I found that the new copy/pasted duplicates of those original audio regions worked fine but, to my shock, now two other audio regions (and their locators) were behaving in the same problematic way!
4. I created a completely new Live session. I imported into it 10 random mp3s and arranged them as audio regions spaced across one track. I then assigned each a locator, and assigned them to buttons on my Remote SL. To my complete shock, I had the same problem!!! Two of the audio regions behaved in the same, problematic way!! Just for the heck of it, I once again reassigned the locators to different buttons on my Remote SL. Of course, just like before, it made no difference. The same two audio regions still behaved problematically.
Now I'm at a complete loss. Any help would be appreciated.
Advertisement
Advertisement
