You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bit Invader wave gets corrupted on saving with a controller connected to the 'Length' knob.
Probably same issue as first noted here: #4705 (comment)
Comment from @PhysSong in #4705
I dumped the saved data. For some reason the decoded data contain Base64 data. I think the data were corrupted while converting to Base64 but not sure why.
The Bit Invader has also produces bad data (nan/inf). Unsure if that is directly connected to this issue.
Steps to reproduce
Add a Bit Invader and an LFO Controller.
Connect the Length knob to the controller.
Save and Reload multiple times and watch the graph of the Bit Invader get more and more destroyed in steps.
It also looks like this is related to when in the controller cycle you do a save. If the Length knob is at it's minimum you get the issue. If it's at it's maximum then I haven't seen any issues.
zonkmachine
changed the title
Bit Invader - Corrupted data when saving with connected controller
Bit Invader - Corrupt data when saving with connected controller
Nov 21, 2020
Added to the description that it also looks like this is related to when in the controller cycle you do a save. If the Length knob is at it's minimum you get the issue. If it's at it's maximum then I haven't seen any issues so far.
BitInvader is created with a default sinewave, length 200, then whatever saved waveform is loaded and writes over the default one. If the saved wavefile is less than 200 samples long there will be a trailing part of the sine left in there. This is seen in graph 2-4 in the issue description. A quick fix for this could be to not load a default sinewave or the rest of the sample shape be written as 0 on load.
The Bit Invader wave gets corrupted on saving with a controller connected to the 'Length' knob.
Probably same issue as first noted here: #4705 (comment)
Comment from @PhysSong in #4705
The Bit Invader has also produces bad data (nan/inf). Unsure if that is directly connected to this issue.
Steps to reproduce
Length
knob to the controller.It also looks like this is related to when in the controller cycle you do a save. If the Length knob is at it's minimum you get the issue. If it's at it's maximum then I haven't seen any issues.
Screenshot
Created on lmms-1.2.1
Affected LMMS versions
Shown on lmms-1.2 and master (87875a1).
The text was updated successfully, but these errors were encountered: