Hi all
I've been trying to get my Micro X working with my MIDI sequencer - I'm currently using REAPER (www.reaper.fm).
With REAPER set to send MIDI clock to the Micro X and the Micro X set to receive this in the Global MIDI settings, I'm experiencing problems with the Micro X arpeggiator. Specifically if I have a patch selected which has the arpeggiator on, hitting play on the sequencer turns off the arpeggiator. You can manually turn the arp on again and occassionally it will stay on when you hit play, but then the arp fails to actually work properly. I also get a weird problem of the Micro X playing random notes, even with the DAW not playing, again when it's set to receive MIDI clock.
With the Micro X's tempo set to internal things work fine but obviously that's not a great way to work - having to manually set the tempo every time you change a patch. The problem persists whether or not I'm using the Micro X plugin software.
I've ruled out REAPER as a cause of the problem by trying a couple of other DAWs but have experienced the same issues unfortunately.
What I'd really like to know is if anyone is successfully sending MIDI clock to the Micro X and managing to use the arp without problems? If so, can you please let me know how you're doing this?
I'd love to hear any possible solutions or workarounds.
Many thanks!
Ben
Micro X - problems with MIDI sequencing and the arpeggiator
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
synths-of-silence
- Posts: 7
- Joined: Mon Aug 18, 2008 11:37 pm
I used to have a similar problem with my Yamaha CS1x, it seems that the arpeggiator just wasn't connected to the external clock. The simple and obvious solution is to do your apreggio in your host and just send the MIDI notes across. Unlike the CS1x, where the arp patterns were complex presets, at least you'll be able to look at the arp patterns and copy them easily enough.
-
synths-of-silence
- Posts: 7
- Joined: Mon Aug 18, 2008 11:37 pm
Hey Bones
Many thanks for your reply... and sorry for taking so long to respond.
I see what you're saying about doing the arpeggiating in my host, but to be honest one of the things that attracted me to the Micro X was the speed and ease of use of the arpeggiator - I like the idea of quickly finding an inspirational preset and just going from there. A lot of the combos in particular are completely based around the arp so it'd be a shame not to have access to this.
So for me at least this is a pretty fundamental problem - I was hoping that I was missing something and that there was a way around it! It's a pretty major bug in the Micro X if not! I can't believe it's not pissing anyone else off - is anyone else having this issue?!
As far as I understand it, the only way for this to be fixed would be if Korg upgraded the firmware of the Micro X. Does anyone know if they've done this to date, or if it's even possible?
Many thanks for your reply... and sorry for taking so long to respond.
I see what you're saying about doing the arpeggiating in my host, but to be honest one of the things that attracted me to the Micro X was the speed and ease of use of the arpeggiator - I like the idea of quickly finding an inspirational preset and just going from there. A lot of the combos in particular are completely based around the arp so it'd be a shame not to have access to this.
So for me at least this is a pretty fundamental problem - I was hoping that I was missing something and that there was a way around it! It's a pretty major bug in the Micro X if not! I can't believe it's not pissing anyone else off - is anyone else having this issue?!
As far as I understand it, the only way for this to be fixed would be if Korg upgraded the firmware of the Micro X. Does anyone know if they've done this to date, or if it's even possible?
-
synths-of-silence
- Posts: 7
- Joined: Mon Aug 18, 2008 11:37 pm
Hmmm well the problem is that if I set the MicroX to sync to host - which obviously I want to do - and want to use the arpeggiator, the arp randomly turns itself on and off and/or I the MicroX plays random notes when nothing should be playing!
For me at least this is a major problem. No one else finding this irksome and unworkable...?
Thanks
Ben
For me at least this is a major problem. No one else finding this irksome and unworkable...?
Thanks
Ben
No, because its not what I use the microX for. In any event, it seems like a simple thing to work around, you just need to adjust your perception to get past it. It seems to me that it is only a major problem because you choose to let it be, but if you just spent a few minutes programming your sequencer instead, you would solve the problem completely. Better still, go and find a sequencer with its own arpeggiator and it will be even easier. There is nothing you can do in the microX's arp that you cannot easily do in your sequencer.
When I bought mine, the arp was a big attraction. I've found that it has its uses but is ultimately very basic. A lot of the time I find it easier to do that stuff in my host and haven't ended up doing any of the things I had originally planned to do with the arp. OTOH, the CS1x arp did some very cool things with automation that I couldn't easily replicate outside of the machine, which I did find frustrating.
When I bought mine, the arp was a big attraction. I've found that it has its uses but is ultimately very basic. A lot of the time I find it easier to do that stuff in my host and haven't ended up doing any of the things I had originally planned to do with the arp. OTOH, the CS1x arp did some very cool things with automation that I couldn't easily replicate outside of the machine, which I did find frustrating.
-
synths-of-silence
- Posts: 7
- Joined: Mon Aug 18, 2008 11:37 pm
We'll have to agree to disagree. A bug is a bug and this is a fairly major one in my opinion, which affects my workflow. I find it bizarre that more people aren't up in arms about this, I can only guess that most people aren't using the MicroX for sequencing - weird!
I'll get on to Korg in the hope they'll address it in a Firmware upgrade. If not, as far as I'm concerned, this synth isn't "fit for purpose" and I'll be sending it back and asking for a refund.
Ben
I'll get on to Korg in the hope they'll address it in a Firmware upgrade. If not, as far as I'm concerned, this synth isn't "fit for purpose" and I'll be sending it back and asking for a refund.
Ben
Arps are for playing live. Sequencing is for recording. Any arp that you play can be recorded in the sequencer, then you don't need the arp anymore for playback. You can still use the arp for different tracks that you record in the sequencer.
Set the BPM on the Keyboard and DAW to match. Don't set the MicroX to external midi when playing the arp. In the DAW you can easily quantitize and perfectly synchronize the recorded arp. It doesn't need to be spot on when you record, since it's easy to fix it if it's even remotely close. Then you can set the MicroX to midi sync to the DAW for laying down the audio tracks for the final mixdown.
I think it's more a matter of understanding how arps fit within the workflow rather than a flaw of the MicroX.
Set the BPM on the Keyboard and DAW to match. Don't set the MicroX to external midi when playing the arp. In the DAW you can easily quantitize and perfectly synchronize the recorded arp. It doesn't need to be spot on when you record, since it's easy to fix it if it's even remotely close. Then you can set the MicroX to midi sync to the DAW for laying down the audio tracks for the final mixdown.
I think it's more a matter of understanding how arps fit within the workflow rather than a flaw of the MicroX.
Its not a bug, its just the way it is just as likely a problem with your computer or the way you have set stuff up as anything else. I have used mine with my sequencer without any problems. In fact, programming my sequencer is orders of magnitude easier than programming a pattern into the microX's arp. Maybe if you just want to use other people's work, but I prefer to do my own.synths-of-silence wrote:We'll have to agree to disagree. A bug is a bug and this is a fairly major one in my opinion, which affects my workflow. I find it bizarre that more people aren't up in arms about this, I can only guess that most people aren't using the MicroX for sequencing - weird!
That's what I'd classify as cutting off your nose to spite your face.I'll get on to Korg in the hope they'll address it in a Firmware upgrade. If not, as far as I'm concerned, this synth isn't "fit for purpose" and I'll be sending it back and asking for a refund.
-
synths-of-silence
- Posts: 7
- Joined: Mon Aug 18, 2008 11:37 pm
Hmmm well it's beyond me why you're blindly defending problems with the synth; I'm guessing you simply haven't come across these things. But it doesn't mean I'm not experiencing real issues - if you're not going to be helpful I'd suggest you just move along. As well as the arp problem I also wrote:
" I also get a weird problem of the Micro X playing random notes, even with the DAW not playing, again when it's set to receive MIDI clock."
Not a bug? User error? Nope. I have years of experience of using MANY hardware synths and I do do this for a living so I a) know what I'm doing b) have never had this before. You on the other hand continually refer to a Yamaha CS1x which is over ten years old and was never anything near a serious synthesizer.
And, for what it's worth, I never planned on making massive use of the arps and certainly am not into "other people's work"
However they are there to be used and when the synth simply won't let me trigger the arp, and doing so creates a bunch of other problems too, there is something wrong. Sorry if you fail to understand that.
Ben
" I also get a weird problem of the Micro X playing random notes, even with the DAW not playing, again when it's set to receive MIDI clock."
Not a bug? User error? Nope. I have years of experience of using MANY hardware synths and I do do this for a living so I a) know what I'm doing b) have never had this before. You on the other hand continually refer to a Yamaha CS1x which is over ten years old and was never anything near a serious synthesizer.
And, for what it's worth, I never planned on making massive use of the arps and certainly am not into "other people's work"
However they are there to be used and when the synth simply won't let me trigger the arp, and doing so creates a bunch of other problems too, there is something wrong. Sorry if you fail to understand that.Ben
I will try to replicate your problems in my setup
Hi Ben,
I've recently worked on some arpeggiated patterns that I need to chain together in my DAW (with the clock of my DAW being the master).
I will do the chaining in a few days (depending on my available freetime).
If you problem isn't a bug, I should have the same problems. So I will come back with my experiences as soon as I can.
One question: You say that a patch with the Arp on (button is lit) switches the arp off when you start the DAW sequencer. Does the light on the button also turn off or stays that on?
One problem that I had: when I play an arp thru the DAW and loop the ARP midi data back into the Micro-X then it gives unpredictable results and strange notes. But that is mentioned in the manual and is problably not the cause of your problems (but you never know).
Greetings,
Paul
I've recently worked on some arpeggiated patterns that I need to chain together in my DAW (with the clock of my DAW being the master).
I will do the chaining in a few days (depending on my available freetime).
If you problem isn't a bug, I should have the same problems. So I will come back with my experiences as soon as I can.
One question: You say that a patch with the Arp on (button is lit) switches the arp off when you start the DAW sequencer. Does the light on the button also turn off or stays that on?
One problem that I had: when I play an arp thru the DAW and loop the ARP midi data back into the Micro-X then it gives unpredictable results and strange notes. But that is mentioned in the manual and is problably not the cause of your problems (but you never know).
Greetings,
Paul
Tested it and might have some hints?
Hi Ben,
Just tested it yesterday evening.
I found out that it works OK for me, but I noticed the following things that might be related to your problems:
*) It is possible to configure the sync for the arpeggio as internal clock, external clock via midi or automatic. Using the automatic setting it syncs to the external clock whenever it detects one and syncs to the internal clock when not. This setting works fine for me.
*) When I configure the arpeggiators to sync to the external clock only things go wrong when my DAW is not running (not playing the track). This is because there is no clock info and syncing doesn't work well.
*) When I have the arpeggiator running (in the automatic sync configuration) and I start the DAW (playing the track) it also sometimes stopped the running arpeggio. This was because my DAW (very old version Cubase VST) searches back in the midistream for bank/patch select messages and sends them first. This (re)selects the program or combi and this causes the arpeggio to stop. However the arpeggio on buttoin is still lit and when the DAW sends key-on information the arpeggio starts OK. I can circumvent this problem in my DAW because this behaviour is configurable in Cubase.
*) It is possible to record an arpeggiator-on event in the DAW. Just record the Micro-X (or X-50) and hit the arpeggiator on button. This way I can switch the arpeggiator on at the beginning of the track.
Hope you can do something with this info,
Paul
Just tested it yesterday evening.
I found out that it works OK for me, but I noticed the following things that might be related to your problems:
*) It is possible to configure the sync for the arpeggio as internal clock, external clock via midi or automatic. Using the automatic setting it syncs to the external clock whenever it detects one and syncs to the internal clock when not. This setting works fine for me.
*) When I configure the arpeggiators to sync to the external clock only things go wrong when my DAW is not running (not playing the track). This is because there is no clock info and syncing doesn't work well.
*) When I have the arpeggiator running (in the automatic sync configuration) and I start the DAW (playing the track) it also sometimes stopped the running arpeggio. This was because my DAW (very old version Cubase VST) searches back in the midistream for bank/patch select messages and sends them first. This (re)selects the program or combi and this causes the arpeggio to stop. However the arpeggio on buttoin is still lit and when the DAW sends key-on information the arpeggio starts OK. I can circumvent this problem in my DAW because this behaviour is configurable in Cubase.
*) It is possible to record an arpeggiator-on event in the DAW. Just record the Micro-X (or X-50) and hit the arpeggiator on button. This way I can switch the arpeggiator on at the beginning of the track.
Hope you can do something with this info,
Paul
-
synths-of-silence
- Posts: 7
- Joined: Mon Aug 18, 2008 11:37 pm
Hey Paul
Many thanks for that - good info and I'm glad you've got it working! Quick question for you:
Are you using the USB MIDI driver for the Micro X or the normal MIDI in and out ports? I ask because I'm currently using the USB and I'm wondering if it's worth me trying the MIDI ports, although I'm guessing this is unrelated to my issue.
Potentially worth noting that you're using Cubase, to my REAPER, but again I'd think this isn't causual.
Cheers
Ben
Many thanks for that - good info and I'm glad you've got it working! Quick question for you:
Are you using the USB MIDI driver for the Micro X or the normal MIDI in and out ports? I ask because I'm currently using the USB and I'm wondering if it's worth me trying the MIDI ports, although I'm guessing this is unrelated to my issue.
Potentially worth noting that you're using Cubase, to my REAPER, but again I'd think this isn't causual.
Cheers
Ben
I experienced the same problems
Ben,
Yesterday evening I was sequencing a lot and did approximately 50 recording takes.
Everyting was quite well, but on two recording sessions I experienced exactly what you mention in your inital post.
The arpeggio didn't start when the DAW was playing MIDI note-ons, then after a few seconds arpA was starting and after another few seconds arp B was starting. Then continuining in the track the both arps were suddenly stopped (the arp on button light went off). I let the track go on and pressed the arp on button to switch it on. The arps started again, but died after a few seconds.
Very strange .... it was like the Micro-X wasn't able to succesfully sync the clock for some reason.
Happely this was only on 2 of the 50 recording takes, but it was annoying enough.
My temporary workaround is to record without the sync. The clocks are not completely in sync then but the slew is small enough to prevent real problems. After the recording session I quantize the recorded tracks. During playback of the tracks I use clock sync.
But of course I keep trying to figure out what goes wrong.
Paul
Yesterday evening I was sequencing a lot and did approximately 50 recording takes.
Everyting was quite well, but on two recording sessions I experienced exactly what you mention in your inital post.
The arpeggio didn't start when the DAW was playing MIDI note-ons, then after a few seconds arpA was starting and after another few seconds arp B was starting. Then continuining in the track the both arps were suddenly stopped (the arp on button light went off). I let the track go on and pressed the arp on button to switch it on. The arps started again, but died after a few seconds.
Very strange .... it was like the Micro-X wasn't able to succesfully sync the clock for some reason.
Happely this was only on 2 of the 50 recording takes, but it was annoying enough.
My temporary workaround is to record without the sync. The clocks are not completely in sync then but the slew is small enough to prevent real problems. After the recording session I quantize the recorded tracks. During playback of the tracks I use clock sync.
But of course I keep trying to figure out what goes wrong.
Paul