Hey, I'm sorry if this problem has been answered before, but I'm having issues with controlling my Radias with Ableton. The biggest problem is that, while the presets and other patches I've downloaded play notes fine, most patch I've made myself doesn't make a sound when there's incoming midi. There is one original patch I made that works, but I can't spot any differences between it and other patches that would adhere to midi data. My global midi stuff all seems to match, I just have no idea why the presets work but my own sounds, including empty patches (just a saw with nothing else), do not.
Edit: I've actually realized that not all presets respond to midi data either. The one I noticed was A03: "Tronik Sign."
Edit 2: Okay, so I figured out the reason A01 is missing the vocoder part and A03 doesn't play is because I set the midi clock to external. Is there no way to have the stuff sequenced in the Radias while the midi clock is external? Arpeggiations seem to work fine, it's just the mod sequencer that gets messed up.
Korg Radias Midi Issues
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Play the sequence on the Radias using the internal clock. Record the midi in the DAW. Edit the midi in the DAW to clean it up. Set the midi clock to external. Send the midi in the DAW to the Radias. Same result. When you have a DAW like Ableton Live, it can do all the sequencing far better than the primitive sequencer in the Radias.
Based on your edits to your original question, I think you may be misintrepreting the nature of the problem you are experiencing. Because you said that one patch is working ok, then that proves that at least the Radias is responding to midi in at least one instance. The two other patches you identifed were apparently responding to midi, but you didn't hear anything because they had other dependencies that you didn't realize, such as having one be a vocoder patch that won't work unless there's an audio source for the vocoder. Have you downloaded and installed the latest editor/librarian software? Have you tried ALL the programs from Ableton? If you only tried a few, it may be that only a few aren't producing sound because of dependencies while the rest are OK. You haven't described a specific instance of a program that you think should work after you have examined all the parameter in it. So based on what you said, I think your Radias is properly responding to midi from Ableton, however you aren't getting what you expected because you aren't familiar with the details of the programs you've selected, and you've only tried a limited number of programs that happen to not work the way you expected. But you may have done more testing than you've described to this point. I'm not sure that there is any actual problem other than you not getting what you expect, unless you can provide at least several specific instances of programs that do not make sounds when you select them, after you've examined them carefully to see that they don't have any dependencies that would prevent them from playing.
There are plenty of different things you can try to more specifically identify the nature of the problem. For example, you could put InitPatches on A01, A02, B01, B02, etc., modifying each just enough to make them distinctive, such as a different basic waveform on each, and then test only those simple programs from Ableton. That will eliminate midi as being the source of the problem. This is a generally helpful diagnosis strategy that you can use to narrow down any kind of problem - reducing the number of variables of potential problems by simplifying the test scenario to the most simple, minimal cases that should work, but don't, instead of using complex cases. Radias programs can be rather complex, while InitPatches are the simplest case.
There are plenty of different things you can try to more specifically identify the nature of the problem. For example, you could put InitPatches on A01, A02, B01, B02, etc., modifying each just enough to make them distinctive, such as a different basic waveform on each, and then test only those simple programs from Ableton. That will eliminate midi as being the source of the problem. This is a generally helpful diagnosis strategy that you can use to narrow down any kind of problem - reducing the number of variables of potential problems by simplifying the test scenario to the most simple, minimal cases that should work, but don't, instead of using complex cases. Radias programs can be rather complex, while InitPatches are the simplest case.
I did kinda go off on a tangent with the Radias sequencing not working, I apologize for that. The real problem is that while plugging a midi keyboard into the Radias works perfectly, through Ableton "Init" patches don't work, even ones I've made edits to. I have a few Radias patches I've downloaded and dumped into the Radias that work just fine as well, but the factory and downloaded patches are the only ones that work, none of my own make any sound when I give them midi data through Ableton.
Thanks for your help, I really appreciate it.
Thanks for your help, I really appreciate it.
Are you using the latest editor/librarian software?
What happens when you move a program that is working onto a different program's position that isn't working? Let's say that A02 is working and A01 isn't. Write A02 to A01 to see what happens. If A01 then works fine then it must be something different about the program that was in A01 that got overwritten. If A01 doesn't work, then confirm that it's exactly the same program as what's in A02 by using the editor to compare them. Also, how are you sending midi to the Radias, hardware midi port or USB-midi? What is the midi setting in the global parameters?
What happens when you move a program that is working onto a different program's position that isn't working? Let's say that A02 is working and A01 isn't. Write A02 to A01 to see what happens. If A01 then works fine then it must be something different about the program that was in A01 that got overwritten. If A01 doesn't work, then confirm that it's exactly the same program as what's in A02 by using the editor to compare them. Also, how are you sending midi to the Radias, hardware midi port or USB-midi? What is the midi setting in the global parameters?
I changed positions between a working program and a non=working program and nothing changed (the working program works and the non-working doesn't). I'm sending midi data through a midi cable, and the midi settings in global are all default except the clock is now external and the midi channel is 06 (1-5 are taken by other synths).
Ok. This is the third time I'm asking the following question without any response from you.
Are you using the latest editor/librarian software?
If you're not using the editor/librarian software and only menu diving, then you might never find the difference between the programs. Too many parameters - too little time. The editor makes it easy to compare differences.
Set the midi clock to back to internal. Send a few simple midi notes to the problem programs. Be sure that the notes are held for several measures. Don't try to sync the Radias to Ableton yet. You gotta learn to walk before you run. There's a very high chance that the programs that don't seem to work have an obvious difference - like a sequence or vocoder mode that is keeping it from working.
Chaining hardware midi is also very unreliable and slow. You should get USB-midi working, then you won't need to chain it at all. It will have its own ports and midi channels.
Are you using the latest editor/librarian software?
If you're not using the editor/librarian software and only menu diving, then you might never find the difference between the programs. Too many parameters - too little time. The editor makes it easy to compare differences.
Set the midi clock to back to internal. Send a few simple midi notes to the problem programs. Be sure that the notes are held for several measures. Don't try to sync the Radias to Ableton yet. You gotta learn to walk before you run. There's a very high chance that the programs that don't seem to work have an obvious difference - like a sequence or vocoder mode that is keeping it from working.
Chaining hardware midi is also very unreliable and slow. You should get USB-midi working, then you won't need to chain it at all. It will have its own ports and midi channels.
Yes, I'm using the editor software.
The programs all work perfectly when a midi keyboard is plugged directly into the Radias instead of going through a DAW. I'm not running into problems when I tell Ableton to play the Radias, the problems arise when all Ableton is doing is being there in the middle, midi keyboard to Ableton out to Radias. I didn't sequence anything on Ableton, all I'm doing is playing the keyboard and while the factory patches work empty and/or self-edited patches do not, but only when the data goes through Ableton instead of directly to the Radias.
The programs all work perfectly when a midi keyboard is plugged directly into the Radias instead of going through a DAW. I'm not running into problems when I tell Ableton to play the Radias, the problems arise when all Ableton is doing is being there in the middle, midi keyboard to Ableton out to Radias. I didn't sequence anything on Ableton, all I'm doing is playing the keyboard and while the factory patches work empty and/or self-edited patches do not, but only when the data goes through Ableton instead of directly to the Radias.
Oh, well that's completely different. I looked back over your prior messages - you never previously said that the problem was only when attempting to use Ableton to relay midi from a midi keyboard to the Radias. That's no big deal, but it just has greatly extended this thread in the wrong direction. The problem is likely something with the routing in Ableton. You need to ask about how to do midi routing in an Ableton forum. It's not a Korg issue, I think.
To confirm this, download the free MIDI-OX program to test the routing without loading Ableton LIve. If the midi keyboard events route through MIDI-OX without a problem, then you know that the problem is in Live. MIDI-OX takes a bit of time to learn, but it's worth it to see exactly what midi events are being sent between devices.
To confirm this, download the free MIDI-OX program to test the routing without loading Ableton LIve. If the midi keyboard events route through MIDI-OX without a problem, then you know that the problem is in Live. MIDI-OX takes a bit of time to learn, but it's worth it to see exactly what midi events are being sent between devices.
Try the following. Hook the midi controller midi out to the Radias midi in. Hook the computer through a USB cable. You don't need to have Ableton routing the midi to the Radias. Set midi routing in the Radias Global settings to USB+midi. That way the Radias will respond to midi from either source without having to do external routing.
I plugged the Radias in using the USB and everything worked the same as it always had.
I also discovered a few things that could help. A few cases where I thought that the whole program worked a few timbres were not, which means that the issue isn't program-specific. I also found out that it wasn't that these timbres (whether in an otherwise working program or on a fully "broken" program) weren't making noise, they're just REALLY REALLY quiet. If I turn everything up (Radias and audio interface) I can hear it, even if just barely.
This means there is something in the Radias, most likely the timbres themselves, that's keeping these sounds really quiet when controlled by my computer (straight midi keyboard to Radias doesn't cause this issue). But that doesn't sound like anything I could get help on from an outside source, just something I'll have to guess-n'-check myself by messing with parameters and settings and stuff.
Edit: I was messing with a program that had two timbres, one that worked normally and one that was super duper quiet and I couldn't find any differences save for the osc PCM (it was choir voice and nylon string guitar), EG 2 (AMP) and the dry/wet for an effect (it was the same effect with all the rest identical). The odd thing was that when I would mess with the EG on the quiet timbre is would make the working one louder and reverberate more. I assume that there was something that got messed up internally so I tried to just load up factory settings but that didn't fix a thing.
I also discovered a few things that could help. A few cases where I thought that the whole program worked a few timbres were not, which means that the issue isn't program-specific. I also found out that it wasn't that these timbres (whether in an otherwise working program or on a fully "broken" program) weren't making noise, they're just REALLY REALLY quiet. If I turn everything up (Radias and audio interface) I can hear it, even if just barely.
This means there is something in the Radias, most likely the timbres themselves, that's keeping these sounds really quiet when controlled by my computer (straight midi keyboard to Radias doesn't cause this issue). But that doesn't sound like anything I could get help on from an outside source, just something I'll have to guess-n'-check myself by messing with parameters and settings and stuff.
Edit: I was messing with a program that had two timbres, one that worked normally and one that was super duper quiet and I couldn't find any differences save for the osc PCM (it was choir voice and nylon string guitar), EG 2 (AMP) and the dry/wet for an effect (it was the same effect with all the rest identical). The odd thing was that when I would mess with the EG on the quiet timbre is would make the working one louder and reverberate more. I assume that there was something that got messed up internally so I tried to just load up factory settings but that didn't fix a thing.
Ableton live is the wildcard variable at the moment. Eliminate it from the testing scenario entirely. Use MIDI-OX as the only midi software on the computer. Ableton might be sending some midi CC commands that could cause the volume on a timbre to be turned down.
If you want to control something on the Radias via midi, test it and do it using MIDI-OX first. It's great for that because it can show you and log everything sent or received via midi, so you can know exactly what's going on. Something is probably being sent via midi that you don't know about from Ableton Live. MIDI-OX is a better diagnosis tool.
If you want to control something on the Radias via midi, test it and do it using MIDI-OX first. It's great for that because it can show you and log everything sent or received via midi, so you can know exactly what's going on. Something is probably being sent via midi that you don't know about from Ableton Live. MIDI-OX is a better diagnosis tool.
This actually sounds like what the issue is because every now and then it happens to me when using Ableton. I think the problem happens when a MIDI track is selected and armed for recording, then you make a volume adjustment. Even though the sequencer is stopped, it still might be embedding the CC data into the clip or track you have selected. If you delete the volume envelope for the track, it will go away. The new version of Ableton also has a CC box for each MIDI clip, so that's another thing to check.xmlguy wrote:Ableton live is the wildcard variable at the moment. Eliminate it from the testing scenario entirely. Use MIDI-OX as the only midi software on the computer. Ableton might be sending some midi CC commands that could cause the volume on a timbre to be turned down.