Thank you for the no-oscillator-reset trick. Now I enjoy using the LXR again! Now figuring out how to make this the default for the first 2 oscillators...
After several perfomance switches controls freeze still. Pretty sure I know what's going on there... If this happens when the sequencer is playing, the sequence continues, but the screen stays on 'Loading Perf'? Are you doing anything like sending mod wheel or program change at the same time? (not that there's anything wrong with that, but might give me some ideas)
>If this happens when the sequencer is playing, the sequence continues, but the screen stays on 'Loading Perf'?
Yes, seq is playing. Screen showing section which was active while perfomance was loading. Then you can navigate within this section with encoder but all buttons are inactive. Only restarting LXR helps.
>Are you doing anything like sending mod wheel or program change at the same time? (not that there's anything wrong with that, but might give me some ideas)
There are OT Part specific PC command (i did not removed this one) and CC00 which i use instead of PC. LXR also handles MIDI thru to 2 other units with their PC commands, clock and transport (i plan to use midi splitter later though)
I'm getting some very strange behaviour when I try to send more then one midi CC to the lxr. Namely i sent slope and decay changes to one voice and the whole machine started lagging and going nuts as soon as the second automation kicked. Are we hitting some kind of processing ceiling?
I remember you hinting at this not being the firmware to use extensive midi cc's to control, would this be related to said statement?
Interesting. Last friday i got my brand new diy 8x midi splitter and got rid of long midi thru chain.
So now looper works really fine. I went back on previous FW and it works ok too, it steadily switces perfomances via CC00 nearly without errors. Latest FW switches perfomances without errors too but UI freezes after several times.
I wanted to stop using LXR while preparing live set because of this issues but LXR sounds so awesome and i got used to its playability.
Yes, seq is playing. Screen showing section which was active while perfomance was loading. Then you can navigate within this section with encoder but all buttons are inactive. Only restarting LXR helps.
Yeah, I am seeing this come up every once in a while too when I do bank changes, I'm working on it, but things will be a bit slow for the time being. If you need to roll back to a previous FW for now, take a look at the custom-develop-activestep branch on github
I'm getting some very strange behaviour when I try to send more then one midi CC to the lxr. Namely i sent slope and decay changes to one voice and the whole machine started lagging and going nuts as soon as the second automation kicked.
I haven't seen this, but I will look into it when I can. Do you have multiple voices stacked on the same MIDI channel? (You should be able to do this and not hit errors, but this isn't how mine is set up, so I might be missing something). Are you by any chance inadvertently sending mod wheel or bank automation along with the other CC's?
Normal MIDI processing shouldn't contribute much to the overhead. Ideally you should be able to saturate the MIDI bus and the LXR might miss messages, but shouldn't act otherwise erratically. Mod wheel and bank changes are exceptions to normal midi messages, since the message trigger actions for the AVR to process. The AVR does get bogged down sometimes, so I might need to put in some more restrictions on how frequently these can be triggered. Voice MIDI messages are normally very fast to process, much faster than the 1000 or so messagese/second MIDI can transmit.
No voice stacking, all voices had their own channel and 5 voices are being sent midi notes. Host is ableton and I'm not sending any other midi data to that channel (unless live's doing funkyness behind the scenes).
Hello Brendan! I've been using the new OS a lot, and It's been good so far, again instant pattern switching is so good! I've been noticing one bug, and it happened a few times with the last iteration of your OS. When recalling an ALL file, there will be spurious pattern next choices made, that were not saved that way! It seems to happen pretty randomly though. Any ideas? Cheers!
Thanks for the bug reports! Please keep them coming, even if it seems like I'm being slow to work on this. I have a lot to do at the moment. It may take me a while to fix all the bugs, so for now I've put up an older firmware on the folder on my website, so brendanclarke.com/files/LXR/ has two firmwares:
FIRMWARE.BIN - this is the 'custom-develop-activestep' branch from github. It has all the additions except for the 'fast file loading' and the envelope position automation. This is recommended for stability at the moment. This WILL realign patterns at every pattern switch.
FIRMWARE-BETA.BIN - this is the latest FW and the one I will be working on (and using, personally), with the new loading method and envelope automation option. You'll need to re-name it to load. Note that files saved in this firmware will not be fully compatible with older FW versions.
Hello Brendan! I've been using the new OS a lot, and It's been good so far, again instant pattern switching is so good! I've been noticing one bug, and it happened a few times with the last iteration of your OS. When recalling an ALL file, there will be spurious pattern next choices made, that were not saved that way! It seems to happen pretty randomly though. Any ideas? Cheers!
Can you check what FW this loads correctly in? Can you send me the 'all' file? If you change the next/repeat back and re-save it (in a different location!) does it then load correctly?
Bug report with latest OS. This occurs in the load screen. If I try to mute a track pressing shift, the sequence continues to play but LXR freezes.
Thanks! I'll be sure to fix that - voice button functions were simply undefined for save/load modes before, they just inherited function from whatever page was active before. I'll have to go through and explicitly define shift functions for load/save. But yes, I understand it's very useful being able to mute when on the save/load pages. I'll make sure to retain that functionality.
Not sure if this has been addressed or was intentional but I am unable to unmute all tracks simultaneously while in Performance mode as shown in the wiki manual. ie shift+voice button
Never mind. I see that the alternate functionality is to silently select a track. Is there anyway to unmute multiple tracks without using 7 fingers lol?
In performance mode, the unmute actually happens on button release, I think you can, say, hold drum 1, press and release all the voices you want to mute/unmute, then release drum 1? Haven't used this in a while, but I think that was my original intention, the 'unmute up to' seemed a bit arbitrary.
OK! One thing i just discovered, I just saved an 'ALL' with the pattern next instructions set to themselves (pattern loops until changed). I then reloaded the 'ALL' with the sequencer running and one of the pattern nexts had changed. I stopped the sequencer, and reloaded the 'ALL' and the pattern nexts came back as saved!
So as far as i can see, its a recall thing, rather than a save thing. This makes the random nature of the fault a bit easier to understand.
I'm practising for a gig next week, and using the LXR a lot, so I'll try to replicate the fault a few more times.
Thanks again Brendan, great that you're pushing this OS forward
do you remember what it was changed TO? IIRC, it sets next/repeat to own pattern, 0 repeat if it doesn't read valid data. If you've got a gig next week, I'd recommend rolling back to something more stable, maybe even the custom-master branch on github.
Hey Brendan. It changed to pattern1. I'm interested to see if it had this error when you load ALL with the sequencer stopped, which wouldn't be such a biggie for me for this particular gig. I really don't want to roll back to something without instant pattern switching and the pattern reset though, it's too much fun!
how was your gig ? how did you overcome this bug playing on stage. I am planing to do the same , but yesterday my lxr has frozen in the middle of a song. i had to power it off and on again.
I'm trying to get the no-oscillator-reset trick enabled by default on track 1. It's easy to save a pattern with all steps velocities set to 0 and the Veloc EGPosition set. But is there a way to load this pattern automatically on startup?
I am testing beta firmware and have experienced bug with track output rooting. No sound or wrong output on voice. It shows output L1 but sound is coming out from R1, No sound was during my attempt to remove click
with automating EGPositioning, i went in to auto. menu and the sound was gone .
Comments
After several perfomance switches controls freeze still.
Pretty sure I know what's going on there... If this happens when the sequencer is playing, the sequence continues, but the screen stays on 'Loading Perf'? Are you doing anything like sending mod wheel or program change at the same time? (not that there's anything wrong with that, but might give me some ideas)
I remember you hinting at this not being the firmware to use extensive midi cc's to control, would this be related to said statement?
Normal MIDI processing shouldn't contribute much to the overhead. Ideally you should be able to saturate the MIDI bus and the LXR might miss messages, but shouldn't act otherwise erratically. Mod wheel and bank changes are exceptions to normal midi messages, since the message trigger actions for the AVR to process. The AVR does get bogged down sometimes, so I might need to put in some more restrictions on how frequently these can be triggered. Voice MIDI messages are normally very fast to process, much faster than the 1000 or so messagese/second MIDI can transmit.
I've been noticing one bug, and it happened a few times with the last iteration of your OS. When recalling an ALL file, there will be spurious pattern next choices made, that were not saved that way! It seems to happen pretty randomly though.
Any ideas?
Cheers!
FIRMWARE.BIN - this is the 'custom-develop-activestep' branch from github. It has all the additions except for the 'fast file loading' and the envelope position automation. This is recommended for stability at the moment. This WILL realign patterns at every pattern switch.
FIRMWARE-BETA.BIN - this is the latest FW and the one I will be working on (and using, personally), with the new loading method and envelope automation option. You'll need to re-name it to load. Note that files saved in this firmware will not be fully compatible with older FW versions.
Never mind. I see that the alternate functionality is to silently select a track. Is there anyway to unmute multiple tracks without using 7 fingers lol?
I'm interested to see if it had this error when you load ALL with the sequencer stopped, which wouldn't be such a biggie for me for this particular gig. I really don't want to roll back to something without instant pattern switching and the pattern reset though, it's too much fun!
The next step errors still happen upon loading, are random and happen with both the sequencer running and stopped!
Cheers
The bug popped up again on one song, next pattern>#1 instead of itself! I just had to avoid that pattern for the song!