Hi. Running 9.52 on Mac 10.13.6
I got a new version of a project I've been collaborating on. Only thing the guy did was merge some soundbites and rearrange tracks. Now, if I open the Sequence Editor to edit soundbites etc., it beachballs forever. Showing and hiding tracks is super slow, and it used to be snappy.
I did everything on this page:
https://motu.com/techsupport/technotes/ ... 20Glitches
I restarted many times. Nothing in my system has changed except for this project. It may be my imagination, but the behavior seems similar (slow) on other projects, but doesn't beachball nor is it quite as slow.
Also, when I open the Sequence Editor, it's just a white screen with the playback head for perhaps one or two seconds before drawing the usual Sequence Editor graphics. It's like you can see it thinking.
Never saw this before. F'ing weird.
Thoughts? Driving me nutso!
Edit: both the other guy and I thought the other used the Consolidated Window, due to it opening when we double-click a track in the Tracks window to open the Sequence Editor. The twist: neither of us use that Consolidated Window mode (it's a pref). Nonetheless, when we exchange files, the SE opens in the Consolidated Window first, with that annoying-ass Track Selector floating window. We close both and double-click Tracks again and the Sequence Editor opens in the desired, non-consolidated way. Recall I trashed my prefs, yet still happens. No idea if this is a clue?
Sequence Editor Graphics issue + beachball 9.52
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
italodisco
- Posts: 65
- Joined: Wed Jan 05, 2005 10:01 pm
- Primary DAW OS: Unspecified
-
italodisco
- Posts: 65
- Joined: Wed Jan 05, 2005 10:01 pm
- Primary DAW OS: Unspecified
Re: Sequence Editor Graphics issue + beachball 9.52
Updating in case anyone has the same trouble. Called MOTU tech support, if I'm blunt they weren't terribly helpful, although the guy I spoke with did validate my hunch that it was a display issue (although I was thinking it could be anything..I even rebooted my interfaces). We ended up at a dead end where workarounds were starting to be bandied about, which was a bummer. We tried changing prime milliseconds; it didn't help. The agent I spoke with couldn't really clearly describe what that did but said it had something to do with processing. I noticed a lag with the transport after (audio kept playing after hitting stop) and changed it back from the 500 that was recommended to the default 125.
TL;DR: I started noticing the problem only occurred when displaying a track with relatively dense volume automation that is being displayed. After we got off the phone, I tested more. It's definitely that, but there is a key details. When zoomed out, DP crawls to a standstill. If zoomed in so just a little bit (say a few measures) of automation is displayed, it's snappy and fine. If the tracks with volume automation aren't shown in the Sequence Editor, it's fine.
So the workaround is don't zoom out with dense automation, at least not on my system. Bummer, but workable. It's suck if I have an area of dense automation followed by, say, a very slow, long fade up or down that needs to be drawn, because that may require me being zoomed out AND needing to display the automation to draw or edit it. I imagine that will be frustrating to deal with. In the meantime I can get back to work, more or less.
TL;DR: I started noticing the problem only occurred when displaying a track with relatively dense volume automation that is being displayed. After we got off the phone, I tested more. It's definitely that, but there is a key details. When zoomed out, DP crawls to a standstill. If zoomed in so just a little bit (say a few measures) of automation is displayed, it's snappy and fine. If the tracks with volume automation aren't shown in the Sequence Editor, it's fine.
So the workaround is don't zoom out with dense automation, at least not on my system. Bummer, but workable. It's suck if I have an area of dense automation followed by, say, a very slow, long fade up or down that needs to be drawn, because that may require me being zoomed out AND needing to display the automation to draw or edit it. I imagine that will be frustrating to deal with. In the meantime I can get back to work, more or less.