kmachman Posted October 3, 2013 Share Posted October 3, 2013 Today i fired up the M20D and it will show the stage background, but will not load my setup. It just freezes and show an error "App returned with status 134" Does anyone have any clue what this means? and how to fix this issue? The screen remain frozen. I tried rebooting and still the same. Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 3, 2013 Author Share Posted October 3, 2013 I got it working... kind of... I figured out if i have the "mute all" button on when i power down, when powering up it will freeze on the stage screen when loading setups. I clicked once on the mute all button, the light willl not go out as it is frozen, but i reboot it after pressing it once and now it loads up. Just to make sure that was the case i engaged the "mute all" button again and powered down. And yes it is the problem. It froze again. Then pressing that button as to turn it off and rebooting it will load correctly. Seems like a glitch in the new 1.20 software as I have always had the mute all button engaged when powering down before this upgrade without incident. Quote Link to comment Share on other sites More sharing options...
Digital-sound Posted October 4, 2013 Share Posted October 4, 2013 I am going to try that on my board. Seems like it would be common to have the mute all button engaged on power down. Quote Link to comment Share on other sites More sharing options...
nickinfrance Posted October 4, 2013 Share Posted October 4, 2013 I always have the mute button engaged when powering down. I've not had this problem at all. Quote Link to comment Share on other sites More sharing options...
actdmusic Posted October 4, 2013 Share Posted October 4, 2013 I've just tested it. I don't have that problem. Try re installing the firmware. And while you're at it download a new file just in case the one you have is corrupted. 1 Quote Link to comment Share on other sites More sharing options...
silverhead Posted October 4, 2013 Share Posted October 4, 2013 Like actdmusic said - looks like a firmware reinstall is necessary. Make sure to back things up first so you will be able to restore your setups and presets later. Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 4, 2013 Author Share Posted October 4, 2013 Ok I will try a reinstall. There was a bit of an issue installing it the first time so maybe that has something to do with it. Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 6, 2013 Author Share Posted October 6, 2013 Ok i re-installed the firmware and everything is back to working the way it should. Thanks. :D Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 8, 2013 Author Share Posted October 8, 2013 Nope.... today i booted it up, and the "mute all" button was not even engaged. It gave me that error code again. Had to reboot it. WTF? Quote Link to comment Share on other sites More sharing options...
ArneLine6 Posted October 8, 2013 Share Posted October 8, 2013 We have discovered a very rare occurrence where this happens during booting up. This does not happen during operation. Just power cycling resolves the issue and there is no risk that this happens during a show. Since this is a very rare issue please let us know if it happens more often. I am sorry for the inconvenience. Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 8, 2013 Author Share Posted October 8, 2013 It only began happening after the firmware update 1.20. Is there not a proper fix? It seems to happen quite often for me. I would have to cycle it more than once to get it to boot properly. Quote Link to comment Share on other sites More sharing options...
danielolsen_4 Posted October 25, 2013 Share Posted October 25, 2013 I have the same problem..!!!!!! and I have only had the mixer for 1 hour.. crap....! Quote Link to comment Share on other sites More sharing options...
rudarel Posted October 25, 2013 Share Posted October 25, 2013 Hi guys, i have the same problem.. This is a known esue with the new 1.2 update, it will not fully recognize setups crated under 1.1 software. The only way to fix this is to delete all older setups and re- create new setups under 1.2 software. This is to bad for me, i have over 20 setups for different venues i travel and different bands. If you only have one setup your in luck, just take pictures of all settings and then do a factory reset,you will de ok. Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 29, 2013 Author Share Posted October 29, 2013 Damn... that is crazy.... I would think Line 6 would fix this issue soon... That is a lot of work! It seems that about half the time i boot it up i have to reboot it at least once or twice to get it to work.... Not impressive on a $2000 machine... I have my doubts that re-doing the setups will make a difference as danielolsen_4 is having the same issues and his is only 1 hour old... Has anyone else tried re-doing all the setups from scratch? Is doing this something Line6 has mentioned as a fix? Sometimes mine gives an error code... but most of the time it just sits there and is frozen. Quote Link to comment Share on other sites More sharing options...
jeanpicasso Posted October 29, 2013 Share Posted October 29, 2013 oh no.. this makes me very unhappy... :unsure: considering that we have used ALOT of time with our setups, done by a soundtechnician (that we paid for) its really a huge issue if it doesnt work after upgrading to 1.2. (we have alot of setups). fortunatly i havent upgraded it yet. was actually going to do it today, but thats not going to happen. :wacko: I really need for line6 guys to respond to this issue. Quote Link to comment Share on other sites More sharing options...
ArneLine6 Posted October 29, 2013 Share Posted October 29, 2013 The setups are not related to the booting behavior. It is not necessary to to delete setups. Kmachman, please contact our customer service since what you describe sounds unexpected. 1 Quote Link to comment Share on other sites More sharing options...
kmachman Posted October 30, 2013 Author Share Posted October 30, 2013 I have created a support ticket... Waiting to hear back... Fingers crossed it gets fixed soon. Quote Link to comment Share on other sites More sharing options...
jeanpicasso Posted October 30, 2013 Share Posted October 30, 2013 ok.. took the chance and upgraded to 1.2 last night, seems to work ok, exept for now theres an occational crackling sound in the in-ear monitors that wasnt there before.. I "downgraded", loaded the same setup and scene and the crackling sound is not there...I upgrade to 1.2, and the weird sound is there again, still only occationaly. :unsure: Quote Link to comment Share on other sites More sharing options...
jaminjimlp Posted November 10, 2013 Share Posted November 10, 2013 I have the same problem just started A couple of days ago we were at a gig yesterday morning getting set up and I had to reboot it at least five times I pushed the mute buttons and unplugged everything but it seems like when I unplug the USB is when it was able to be back up I thought maybe because we were in a cold environment it was because of the temperature and itneeded to warm up some. Okay will be watching this one see when the fix comes Quote Link to comment Share on other sites More sharing options...
kmachman Posted November 16, 2013 Author Share Posted November 16, 2013 Really no help from the support ticket i created… They just want me to send the unit in for repair. Quote Link to comment Share on other sites More sharing options...
kmachman Posted November 16, 2013 Author Share Posted November 16, 2013 One thing i haven’t tried is to go back to version 1.10. Is this possible? Then reinstall 1.20. I have just tried to reinstall 1.20 over top of the existing 1.20. Can a person go backwards in firmware? 1 Quote Link to comment Share on other sites More sharing options...
kmachman Posted November 22, 2013 Author Share Posted November 22, 2013 I think i may have figured it out... I removed the SD card. The SD card had the firmware update and backups on it. Ever since i removed the card it has been flawless for almost a week now. I will reformat the card and try it again. Crossing my fingers. Quote Link to comment Share on other sites More sharing options...
amdenis Posted June 30, 2016 Share Posted June 30, 2016 I just completed many hours of testing, and found that it happens to me with all of the permutations noted above, in a somewhat random fashion. The StageScape also crashes (locks-up) on occasion (about once a day), when switching between various modes (e.g. Monitor, Recording, as well as other menu and tab changes). There are obviously some bugs in the software/firmware, which need to be addressed by Line 6. I expect that they are working on it, given that there appear to be dozens of people who have these issues. I also noted the noise problems that were not there in prior versions. I hope a fix is released soon, as it is no longer usable for important sessions. Quote Link to comment Share on other sites More sharing options...
66d35 Posted July 1, 2016 Share Posted July 1, 2016 I think you have a hardware problem. This is not normal and certainly does not happen with mine. I also have my doubts they are "working on" anything.... one of the reasons why, when needing a second mixer of this general specification recently, I purchased a QSC Touchmix rather than another M20D. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.