Hi there I got the following problem.
I use my RADIAS in a live-setup, so its connected per midi to another device, so that the lfo in temposync works properly.
But as soon as I use it connected per midi, the rate of the LFO becomes slower by half, which means, if I select 1/64 as rate it only plays something like 1/16 or something like that.
I really don't know any solution for this, can anybody help?
EpikureeR
LFO Midi Problem
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
You don't make it easy to help when you omit vital information, like exactly what "another device" means? Let's say that mysterious device is sending a midi clock of 25BPM and you expect it to be 100BPM, then the Radias is behaving exactly how it should behave. In other words, you're assuming the problem is with the Radias, when it's more likely to be whatever you've hooked up, which you have inconveniently left out.
For once I use the application "Liveprofessor" which is set to 132bpm.
Inside Liveprofessor I've loaded 2 NI Maschines.
The Radias is connected with Midicable to Maschine.
Inside the Radias I selected in the Midioptions "Ext Clock" and "MIDI" (instead of USB, or MIDI/USB).
Inside Liveprofessor I activated the routing from maschine midi out.
I trigger my Radias from the Maschine.
EpikureeR
Inside Liveprofessor I've loaded 2 NI Maschines.
The Radias is connected with Midicable to Maschine.
Inside the Radias I selected in the Midioptions "Ext Clock" and "MIDI" (instead of USB, or MIDI/USB).
Inside Liveprofessor I activated the routing from maschine midi out.
I trigger my Radias from the Maschine.
EpikureeR
There could be, but what were the results of the test?
Why do you think you need 2 NI Maschines loaded? Why would both be sending midi to the Radias anyways? If you only need to sync to the BPM, then only one midi clock signal should be sent to the Radias. I'm not an expert with Maschine, but it seemed rather powerful all by itself when I played with it.
Why do you think you need 2 NI Maschines loaded? Why would both be sending midi to the Radias anyways? If you only need to sync to the BPM, then only one midi clock signal should be sent to the Radias. I'm not an expert with Maschine, but it seemed rather powerful all by itself when I played with it.
I play electronical dance-music.
The thing is, i need to overlap beats, which explains why i need 2 machines.
I concipated on each maschine-file a radias midi-out, which I mute till I finished the one before, then i change the programm and start the new midi-pattern.
I can't load everything I got in one Maschine instance.
I use Maschine for Live-Mixing my own tracks and want to get full advantages from my radias.
EpikureeR
The thing is, i need to overlap beats, which explains why i need 2 machines.
I concipated on each maschine-file a radias midi-out, which I mute till I finished the one before, then i change the programm and start the new midi-pattern.
I can't load everything I got in one Maschine instance.
I use Maschine for Live-Mixing my own tracks and want to get full advantages from my radias.
EpikureeR
How long have you been using Maschine?
I think you can overlap beats without 2 instances of Maschine. Who told you that you needed to load up 2 instances? Have you been working with NI support?
Regardless, your problem is due to your sequencer/computer setup, not the Radias, as I suspected. So the best place to fix the problem will be some NI Maschine forum, not here.
I would suggest that you ask for ways to transition between two different beats in the same instance of Maschine. I would be shocked if it couldn't do what you want in one instance, so I suspect that you've merely chosen the wrong solution to your problem by using Liveprofessor, when there's probably a much better way to transition between beats that you just haven't learned yet.
I think you can overlap beats without 2 instances of Maschine. Who told you that you needed to load up 2 instances? Have you been working with NI support?
Regardless, your problem is due to your sequencer/computer setup, not the Radias, as I suspected. So the best place to fix the problem will be some NI Maschine forum, not here.
I would suggest that you ask for ways to transition between two different beats in the same instance of Maschine. I would be shocked if it couldn't do what you want in one instance, so I suspect that you've merely chosen the wrong solution to your problem by using Liveprofessor, when there's probably a much better way to transition between beats that you just haven't learned yet.
Or maybe they have a way of turning off the midi clock being sent by one of the instances? The Radias only should be receiving clock from one source. Same goes for any external synth. Or maybe you can stop sending midi clock from either Maschine instance, and use only midi clock from Ableton Live as the master midi clock source?
http://www.native-instruments.com/forum ... p?t=104484
these are the answers
these are the answers
Notice that reply said that loading two Maschines was only one alternative. The other was "If you don't have ableton, you could try programming each song into One Maschine Project...that is assuming that you'd have enough room within the groups for each song." That is the approach I was suggesting as a possibility too.
You could view your whole set as one project. That might even allow a more natural transition between beats by connecting elements one at time, instead of the "DJ" approach of trying to merely crossfade between two different beats. Ask some more over there, and you might get other alternatives too.
You could view your whole set as one project. That might even allow a more natural transition between beats by connecting elements one at time, instead of the "DJ" approach of trying to merely crossfade between two different beats. Ask some more over there, and you might get other alternatives too.
Sure, set the LFO to 1/16 when you want 1/32.
How does the Radias know that you've got two different sequencers sending it midi clock? It doesn't. It's doing exactly what it's supposed to do. It's sync'ing the LFO to the clocks you send it. If you send it twice as many as you're supposed to, that's not the Radias' problem.
This will not only affect the LFO sync, but anything that syncs to BPM, such as the mod sequencer and arpeggiator.
The fundamental problem seems to be that you're sending double the midi clocks that you should send. All the rest are symptoms of that problem. Fix that problem, and all the other problems go away. As a general rule, treating the symptoms instead of the root cause will have lots of unintended consequences and will cause the problems to persist. I wouldn't be surprised if the Radias loses sync entirely if the two instances are set to different BPM values.
It could be very entertaining if your Radias flips out during your performance, although it might be more amusing to the audience than to you. Don't say I didn't warn you if it happens.
How does the Radias know that you've got two different sequencers sending it midi clock? It doesn't. It's doing exactly what it's supposed to do. It's sync'ing the LFO to the clocks you send it. If you send it twice as many as you're supposed to, that's not the Radias' problem.
This will not only affect the LFO sync, but anything that syncs to BPM, such as the mod sequencer and arpeggiator.
The fundamental problem seems to be that you're sending double the midi clocks that you should send. All the rest are symptoms of that problem. Fix that problem, and all the other problems go away. As a general rule, treating the symptoms instead of the root cause will have lots of unintended consequences and will cause the problems to persist. I wouldn't be surprised if the Radias loses sync entirely if the two instances are set to different BPM values.
It could be very entertaining if your Radias flips out during your performance, although it might be more amusing to the audience than to you. Don't say I didn't warn you if it happens.