This didn’t used to happen but now when I play a song it starts with all of my programmed Mutes off and all sounds ablazing. If I take it out of Songmode and then put it back into Songmode before hitting Play this doesn’t happen. Any suggestions on a way to solve this issue? Thanks
Does it happen on all songs or just 1 song in particular in one project? Good way to check and see if it’s an overall behavior of the device or if it’s a problem wth the project data would be to arrange a song in another project, even a short one, then save it and let’s say exit the project by loading another, power off, wait the recommended 30 seconds then power on, reload the project with the new song and test to see if the behavior is the same as the project with the current unmute issue.
Also, it’s another kind of a lame way to go about it, but you could copy the same current data to a new project slot and recreate the song from scratch, if it happens there as well, it’s probably a bug. If it doesn’t happen, then something got messed up in your old project file. corrupt data. a bad save. something like that.
It’s a roundabout way of doing things, but you’re unlikely to find a better solution as this is not an issue dealing with rational numbers and it doesn’t sound like you’re the problem, i.e. you didn’t do anything wrong but something happened none the less. So, unless you just so happen to have the data backed up on your computer from right before it happened, and you want to try reloading the project (Which you could do) you’re left grasping at straws.
Still sometimes though, it seems like corrupt data hides at the firmware level, you might have to level the playing field, reload the OS and reload all your projects to the device to get rid of the issue and since we can’t confirm the specific issue other than that there’s other similar reports of people saying mutes in song mode aren’t complying with the way they’re saved, the only steps that can be taken are more like experiments. If you have time to do any of this, I’d encourage you to try it out but be cautious about these things if no back up exists, only do non-destructive actions like the suggestion of copying the data to a new project and recreating the song.
That’s the best I got, hope that helps. And FWIW as much as I try to help people with stuff like this, it’s all a gamble because some of these glitches, bugs, data errors, whatever you want to call this type of behavior just don’t conform to others even similar in nature. People seem to have better luck with firmware reloads over sysex, probably because a component of the FW load differs from that which you get over usb, I assume it’s something to do with the internal formatting or reformatting, but I’m not a software guy so I just don’t know the facts, only things that are vague but may help if you’re motivated and want to give it a shot.
1 Like
Thank you for your advice shigginpit 
1 Like
No promises of any fix, but hopefully this will help you determine if it’s time to submit a bug report or maybe attempt the firmware reload. To at least set you on a path of action.
Good luck, update if there’s some progress or other change of the situation.
1 Like
It happened with all four songs that I had programmed recently and performed at an intimate birthday party this weekend. Not a big deal there but if performing at a show venue it would make for awkward transitions. Other folks on here have reported the same problem so I am feeling like it is probably a bug. I’ll check my older songs that I programmed pre-firmware update when I get a chance tomorrow and share any progress.
1 Like
Yes, please do. I’m now interested. I mostly use pattern chains and not song mode so I naturally use a lot of green mutes and not purple. It sounds like this has to do with the structuring of the songs using the purple mutes, or the memory of those songs and that it defaults back to the arrangement after stop/start is very strange. I think you could easily call this a bug, please if possible, update with your findings.
Yes even on songs made before the last firmware update I am having the same issue. Maybe time to issue a bug report?
I would consider doing the sysex firmware reload as a last step and then in a new project check for the same behavior but otherwise I think a bug report is the best possible next step, though my expectations of reaching a resolution by submitting a bug report are low, that’s why even if it doesn’t seem to quite make sense, trying that last step on your own may be the correct choice.
specifically, you’ll need to do it with din midi, through a din interface to your pc using the sysex provisioning in the transfer software.
How to update your device via sysex transfer : Knowledge Base (Beta) (elektron.se)
1 Like