Channel Strip causing crashes

[dix]

I keep the Sequence Editor on one of my dual screens and the Consolidated Window on the other. When the new Channel Strip occupies a spot in the CW having any window other than the Mixer open in another CW spot will cause a crash. For example if the CW just has the Mixer and the CS everything is fine, but if I change the tab from Mixing Board to MIDI or Tracks Overview touching the Channel Strip will cause a crash. I've tried several variations, but basically the CS only seems compatible with the Mixer in the CW on my system.

Anyone else getting this?

Thanks

[bayswater]

I tried a setup with all the meters and monitors in the CW. Put the Mixer, TO, and SE in separate windows using Spaces. I put the channel strip in the CW with the Meter Bridge. I think that's pretty close to what you have, and it was fine.

But I'm wondering about the fact you are running 10.4 on the 8 core? I thought I read that it doesn't work? Did it come with 10.4? Often a Mac will not run with an OS version older than the Mac itself.

[Shooshie]

I'd upgrade to Snow Leopard, where at least we can give you up-to-date information. It's been a long time since I looked at 10.4.x.

[dix]

Yes. 10.4 came installed on this 8core. I know I should upgrade. Been waiting for Snow Leopard, but have been in a project since it came out. I'm basically very stable, other than this issue.

Thank you so much for trying to replicate my screen setup. I'm not sure if you have it right or not. My screen config is:

Left monitor (transport and) Consolidated Window with three vertical panes. 1st pane=Track Selector, 2nd pane=Mixer or MIDI Editor or Track Overview depending on the tab. 3rd pane=Channel Strip.

Right Monitor has the Sequence Editor.

Clicking on a track in SE brings up the Channel Strip in the far right pane of the CW. If the Mixer is showing in the center pane all is good, but if the ME or the TO are in the center pane DP crashes.

Thanks again for checking this out!

[dix]

I'd upgrade to Snow Leopard, where at least we can give you up-to-date information. It's been a long time since I looked at 10.4.x.

Believe me, it's a high priority, but I'm rock solid except for this issue.

Can you confirm this is not an issue in SL as I describe it above?

Thanks!

[James Steele]

I wonder if dual screens has anything to do with it? I don't think I can reproduce this on my system as I've used the CS in the CW a lot and never had this crash. I haven't tried your recipe though.

[HCMarkus]

Add another hard drive and install Snow Leopard on it. You may find SL works great, possibly a lot more efficient. If you don't, you'll have your current system a mere re-boot away at all times.

[bayswater]

Yes. 10.4 came installed on this 8core. I know I should upgrade. Been waiting for Snow Leopard, but have been in a project since it came out. I'm basically very stable, other than this issue.

Thank you so much for trying to replicate my screen setup. I'm not sure if you have it right or not. My screen config is:

Left monitor (transport and) Consolidated Window with three vertical panes. 1st pane=Track Selector, 2nd pane=Mixer or MIDI Editor or Track Overview depending on the tab. 3rd pane=Channel Strip.

Right Monitor has the Sequence Editor.

Clicking on a track in SE brings up the Channel Strip in the far right pane of the CW. If the Mixer is showing in the center pane all is good, but if the ME or the TO are in the center pane DP crashes.

Thanks again for checking this out!

Tried your exact setup on my system, and had no problems (using DP7 -- haven't updated my profile)

[dix]

Thanks all! Turns out if I divorce the CS from the CW, and dedicate a window to it, it doesn't crash, so that will work for now.

There is one other subtlety to my process that might be relevant: With the CW showing the ME in the center pane and a track is selected and active in the SE (in a separate non-cw window), if I click on the MIDI grid and THEN make a move on the CS I don't crash. It's only when I go to directly to the CS and make a move, without first clicking somewhere in CW (making the CW active), that I get the crash.

I guess upgrading to SL is my next move. I just need to carve out a day or two to let the dust settle. ....it's not just matter of cloning and reverting to the tiger clone if need be. it's potentially a bit more involved as is outlined here: http://www.motunation.com/forum/viewtop ... =1&t=38314

Thanks again

[dix]

Although I never got around to reporting this issue, it seems to be fixed in 7.01. However, I've found I like having an autonomous CS. I can't afford the real estate to use the new in-line meters/controls in the mixer, but having just one channel, the CS, with all of 7's in-line features is doable and helpful.

[miditime]

I get the crashes from the channel strip as well.

It will crash consistently every time I touch it in the CW if there's a lot going on in the mix.

Seems to work okay with simple mixes though.

Took a while to figure out what was causing the crashes.

I hope MOTU can fix the channel strip and disabled / broken Vocalign issues in 7.03

See you at NAMM!

[Armageddon]

I'm still on 10.4.11 and DP 6.03, but it looks like (ulp!) I'll be making the big leap to Snow Leopard in the next couple of days. Tiger has served me well, but I desperately need a more-stable DP, as well as the better processing Snow Leopard seems to promise (DP is the most processor/memory-intensive thing I run on my MacBook), and it seems like quite a few people on here are having good experiences with the Snow Leopard/6.03 combo. Until I have the dough to upgrade DP and finally snag my Nehalem iMac, I figure I might as well get with the times and deal with all the rude surprises upgrading from Tiger to Snow Leopard will cause now, as opposed to after I drop $2,000+ on a new system.

6.03 isn't doing badly on my current system, but the oddest things, like simply selecting a note in the Graphic Editor, will cause an inexplicable crash or the Spinning Beachball Of Doom®. I've begun to suspect that this isn't DP's fault however; I think it's the OS, so I figure investing $29 in a system upgrade might be a good idea to start with. Hell, Tiger's three years old or so, it's practically DOS-age!