weird sound problem with LXR

edited February 2016 in General
Something weird is going on with my LXR since the last update (official version 0.37). basically when I use samples in a drum part, the volume sometimes fades and I get some weird audio glitches. Does anybody else experience this? I hope I'm not double posting this, I did search the forums, but I could only find issues with loading the samples. If I don't have any samples in a preset everything seems to be fine.

Comments

  • I think I've noticed something, wonder if it's related. Something seems buggy with the lfos.
    To see what I mean, load factory patch goa (#19).
    Set some steps for Drum 2 and let it play.
    Go to the lfo page for Snare 1.
    Change parameters frq, snc and mod.. (for example frq: 19, snc: 1/3, mod: 127)
    The lfo is modifying the sound for Drum 2 even though the initial "voi" parameter is set to 3.  
  • Yes indeed the problem I'm experiencing sounds a bit like an LFO, it's cyclic and relatively regular.
  • edited February 2016
    I think I've noticed something, wonder if it's related. Something seems buggy with the lfos.
    To see what I mean, load factory patch goa (#19).
    Set some steps for Drum 2 and let it play.
    Go to the lfo page for Snare 1.
    Change parameters frq, snc and mod.. (for example frq: 19, snc: 1/3, mod: 127)
    The lfo is modifying the sound for Drum 2 even though the initial "voi" parameter is set to 3.  
    Ok, I see what you're talking about. This is a problem in the stock firmware, too. This isn't just an LFO problem, the mod destinations are completely different if you load the same factory preset in version .21 (the one on the default SD card image) than if you load them in the stock .37 firmware. So, something about the way the mod target index is treated changed somewhere between those two versions.

    The sticky thing about this is that if you change the value to where it's supposed to be, and re-save the kit, it will then load properly. This means I can't just change how the mod index loads back to where it was, because it will fuck up every other kit that has been saved since the change.

    There is no "version number" to kits in the stock firmware (even though I submitted a pull request to add exactly this back in July, it has been ignored), so there is no way of identifying which kits use which mod index numbering. I checked stock firmware .34 and the old factory patches have the wrong mod destinations, too, so the change is at least a year old. As far as I can see, the best way to remedy this is to load up all the factory patches in .21, write down what all the mod destinations are supposed to be, then load them in the latest FW, adjust the params, re-save the kits, and redistribute the factory patch set. Any takers?
  • Alright. Thanks! I'll re-save the kits and see how that goes.

    I had a look into the code, but it was hard to see exactly what was going on. My first thought was that the mod target index wasn't calculated when loading a kit. If I changed the "voi" parameter in the example above from 3 to 2 and back to 3 it seemed to correct itself.  
  • If you really want to figure out what's going on, you're going to have to go back through those old commits. Fork Julian's code and roll back the master branch - probably to something in 2013 or 2014. The issue isn't going to show up as anything wrong in the new code - as far as the new code is concerned, new kits load fine. And even if you do identify what the problem is, there just isn't a fix that can be built into the firmware. The best you could do is make a utility to auto-fix kits the user ID'd as problematic. It will seriously be less work to make an excel spreadsheet of all the mod parameters for each voice and restore them in the newer firmware. There's only 30 kits - just 180 voices or 900-1080 parameters to correct (I'm assuming velocity mod is also problematic, so that makes 5 params - mod dest and amt for velocity and dest, amt, and voice for LFO, maybe retrig is bugged too).

    It's important to note that the LFO destinations come up completely wrong in the newer versions of the firmware - for example, in .21, drum2 of the 'goa' patch has its LFO assigned to filter freq, but in .37 it comes up as attack. You can also ID the problem parameters because if you click in with the encoder and try to adjust them, they will immediately jump to 'off'. Anyway, my point is, those "factory" patches won't sound exactly the way they're supposed to unless all those old mod params are carried over from version .21 and recreated with a newer firmware.
  • Okay. Seems like a lot of work, no question. Probably I'll have another look and come to the conclusion that my OCD level isn't high enough. But thanks again for the explanation and suggestions. Much appreciated! :)
     
  • @brendanclarke said:
    If you really want to figure out what's going on, you're going to have to go back through those old commits. Fork Julian's code and roll back the master branch - probably to something in 2013 or 2014. The issue isn't going to show up as anything wrong in the new code - as far as the new code is concerned, new kits load fine. And even if you do identify what the problem is, there just isn't a fix that can be built into the firmware. The best you could do is make a utility to auto-fix kits the user ID'd as problematic. It will seriously be less work to make an excel spreadsheet of all the mod parameters for each voice and restore them in the newer firmware. There's only 30 kits - just 180 voices or 900-1080 parameters to correct (I'm assuming velocity mod is also problematic, so that makes 5 params - mod dest and amt for velocity and dest, amt, and voice for LFO, maybe retrig is bugged too).

    It's important to note that the LFO destinations come up completely wrong in the newer versions of the firmware - for example, in .21, drum2 of the 'goa' patch has its LFO assigned to filter freq, but in .37 it comes up as attack. You can also ID the problem parameters because if you click in with the encoder and try to adjust them, they will immediately jump to 'off'. Anyway, my point is, those "factory" patches won't sound exactly the way they're supposed to unless all those old mod params are carried over from version .21 and recreated with a newer firmware.

    Thanks for this, I tought my LXR was messed up since almost all presets sounded really weird, only the 808one seemed to sounds good. Will try with the 0.21 firmware.

  • I had the same issues, with the latest BC firmware, it think. Almost anytime, when i am trying to tweak the LFO parameters, i end up with the LXR "crashing" (all voices sound like bassless glitch click), stopping and reloading ALL has helped.

    I hope there would be a fix for this in a FIRMWARE UPDATE, because now the cool factor of routing LFOs to all parameters leads to mostly very frustration results.

    And unfortunately i can't code!!!

    If anybody can, be a true HERO and do it for all of us.....PLEASE.

Sign In or Register to comment.