Sequence editor won't open (RESOLVED)

[Bobbyd]

I'm trying to find out what's causing this. Clicking on the SE or using the key command won't open the SE. Instead I get a pop-up that says, "Digital Performer has encountered an error. Unknown Exception error reported by MotuError: Unknown mode."

This doesn't happen all the time or with all projects. Once it happens in a project it will always happen again. Reopening or restarting the computer doesn't help. I was using DP 11.01 when it first happened. Upgraded to DP 11.11 which seemed to take care of it at first, but didn't.

Using an M1 macmini, 8GB of RAM running Big Sur. Upgraded to Monterey with no change.

[mikehalloran]

Sometimes I'll get that when I try to run two commands in rapid succession. Waiting a few seconds gets around that.

Otherwise, try booting DP in Safe Mode by holding the Shift key when starting. After DP is up, shut down and start normally.. This resets caches and fixes any corrupted paths to extensions and System files. I've not had to do this in DP 11.11 but had to do it a lot with DP 10 and 11.01.

If this is persistent, shut down and boot your Mac in Safe Mode, again by holding the Shift key. After logging in and making sure that any desktop icons have been rebuilt, reboot normally. In the pre-OS X days, this was known as Rebuilding the Desktop and done the same way.

[Polemarch]

Just had this problem this morning! Tried Mike's suggestions but no love. Bobby, were you ever able to sort out what was happening or figure out a way into your sequences window?

[Bobbyd]

Just had this problem this morning! Tried Mike's suggestions but no love. Bobby, were you ever able to sort out what was happening or figure out a way into your sequences window?

No Polemarch, Mike's suggestions didn't do it for me either. It appears that once it happens with any project it, will always happen with that project. Other projects somehow haven't had this problem, but if they do, something gets corrupted.

I was thinking that some templates are corrupted so I've been starting with empty templates and hoping for the best at this point. I've exported MIDI tracks and imported them into a new project. Or bounce MIDI tracks to audio and drag them into a new project. Might have to contact MOTU on this!

[HCMarkus]

Have you tried Loading the project in question into a new project?

[Bobbyd]

Yes HC. Loading just loads the glitch in along with the document. It's like a pandemic

[Bobbyd]

I got on the chat line with a MOTU tech this morning. Eliminating the data of one track at a time, testing after each, he narrowed down the possible cause. I ended up emailing one of the projects to him and he found (in the event list) an empty spot in a couple of MIDI tracks. That turned out to be the culprit in my case.

How did that happen? I started out with MIDI tracks from BIAB and I deleted some of their CC data.

[HCMarkus]

Glad you got it sorted Bobby!

So... the issue was, apparently, anomalous data.

[Bobbyd]

anomalous data

Yes Markus, an anomaly that was anonymous! I certainly learned a bit about logically breaking down problems like this.

[cuttime]

BIAB - Band in a box. Took me a while

[mikehalloran]

How did that happen? I started out with MIDI tracks from BIAB and I deleted some of their CC data.

Glad that MOTU Support was able to help you sort that out. Although I'm a beta tester for BIAB and a few other apps, it never would have occurred to me to go there.

[Bobbyd]

It turns out that BIAB exported the MIDI with the unassigned space. BIAB has caused problems with DP in the past but I don't recall seeing this happen.