Works fine so far, but one question is coming up, maybe my ignorance, but aren't the output routings supposed to be saved with a kit ? Yesterday i made a new kit, and every setting seems to be saved except the output routing of the voices.
@macMOE the chords were a side effect of the midi notes not turning off. May be a good config option... @nightworxx that sounds like a bug as they should be saved per voice.
I noticed the output routing issue last night as well. The kits I made on .24a seem to have the bd going to a single mono left out now. I attempted to correct them but it wouldn't save.
hmmm I can't really confirm the routing bug. The save code has not changed. I just tried changing the routing of the 1st preset "Slak" and I can successfully change, save and recall the output routing of voice 1. I have not tried the others so far.
Is it not working in general for you or just in some specific cases?
and about the midi bug (the LXR works only on the channel one) ? when can we choose the midi channel ? can we hope it will be on the next update ? it's a fantastic machine ...
Midi can send on any channel, but the receive is whatever channel the first drum voice is set to. Also there may be a bug in the official firmware that makes it only receive when that is set to channel 1 (I think I fixed this in the custom firmware, but need to test that particular aspect).
Heh, I used to have the RM1X. It was a love/hate relationship, and I ended up selling it. It's very powerful, but you need to spend a lot of time programming it. The midi sequencer is great though. I got the Motif XS6 which has a very similar engine, but they learned their lessons on a few points I think. I wouldn't mind playing around with the RS7000 (maybe I'll grab one some day).
If you like you can try the custom non-official firmware at https://github.com/rudeog/LXR/blob/master/firmware image/FIRMWARE.BIN (go to that link then click the raw button and save as). I think it should let you specify a different midi channel. But bear in mind that it still is based on the midi channel that is specified for drum voice 1 (in other words, you should go to drum voice 1 and set the midi channel there, and then you should receive notes and prog chg from that channel. start/stop are system msgs and are not channel specific) The fix I did removes the restriction that channel 1 is used, however I haven't tested this specific aspect. Also, the only notes that will trigger the LXR are C2 thru F#2 (it doesn't take into account the midi note setting yet). @Julian the fix for allowing channels other than 1 is simple and is in midiParser_handleStatusByte the switch(data) should be masked against F0 and the same fix in midiParser_parseMidiMessage.
The other functions are the same. Julian took my changes recently, and I synchronized with the official firmware before making these new changes. As for your error, can you open the actual firmware.bin file in an editor and make sure the first 4 characters are SPFI. The rest of the characters will look like garbage.
When you download the BIN you'll have to right-klick and then "save as", if you download the file by directly klicking the link, you'll get a crippled file. Happened to several other members in this forum...
there is another bug : the settings of the snare changing alone ... I have saved my snare, played with it few minutes, it was fine, and after few minutes, the snare has changed settings, I load another patch et reload the patch with my snare and the snare working fine ... and change after few minutes ! strange ... (I don't had this bug on the 0.24 )
it change without touching anything, I play sequences from RM1x to LXR, LRX run well, I stop the sequence ... and I replay the sequence, and the settings are changed ! I did not another else than midi notes ...
Comments
I just did some minor things :-.
@nightworxx that sounds like a bug as they should be saved per voice.
The save code has not changed.
I just tried changing the routing of the 1st preset "Slak" and I can successfully change, save and recall the output routing of voice 1. I have not tried the others so far.
Is it not working in general for you or just in some specific cases?
If you like you can try the custom non-official firmware at https://github.com/rudeog/LXR/blob/master/firmware image/FIRMWARE.BIN (go to that link then click the raw button and save as). I think it should let you specify a different midi channel. But bear in mind that it still is based on the midi channel that is specified for drum voice 1 (in other words, you should go to drum voice 1 and set the midi channel there, and then you should receive notes and prog chg from that channel. start/stop are system msgs and are not channel specific) The fix I did removes the restriction that channel 1 is used, however I haven't tested this specific aspect. Also, the only notes that will trigger the LXR are C2 thru F#2 (it doesn't take into account the midi note setting yet).
@Julian the fix for allowing channels other than 1 is simple and is in midiParser_handleStatusByte the switch(data) should be masked against F0 and the same fix in midiParser_parseMidiMessage.
As for your error, can you open the actual firmware.bin file in an editor and make sure the first 4 characters are SPFI. The rest of the characters will look like garbage.