Page 1 of 1
Split Track command causes crash in DP 6.0
Posted: Fri Aug 08, 2008 2:25 pm
by Ken Kugler
Anyone else run into this? When I try to Split a track to do an edit DP 6.0 crashes repeatedly. I haven't had much time to investigate but it keeps happening. This is getting really annoying. I repaired my permissions and rebooted and it's still happening. Any ideas?
I'm running a 2.8 GHz Quad-Core Mac Pro with OSX 10.5.4
Posted: Fri Aug 08, 2008 2:49 pm
by Phil O
Both split at counter and the scissors tool are working for me. But I'm on an Intel Mac. Wonder if it's a system specific bug? All I can say is it's working on my system.
A variety of problems are being solved in DP6 by trashing prefs. Have you tried that yet?
Phil
Re: Split Track command causes crash in DP 6.0
Posted: Fri Aug 08, 2008 5:40 pm
by wurliuchi
Ken Kugler wrote:Anyone else run into this? When I try to Split a track to do an edit DP 6.0 crashes repeatedly. I haven't had much time to investigate but it keeps happening. This is getting really annoying. I repaired my permissions and rebooted and it's still happening. Any ideas?
I'm running a 2.8 GHz Quad-Core Mac Pro with OSX 10.5.4
Yes. I have the same problem on both systems. I sent a crash log to Magic Dave who sent it to whoever works on that stuff but I haven't heard anything back. That was a month ago tomorrow. No doubt they're busy after the release.
Posted: Fri Aug 08, 2008 8:58 pm
by martian
some problems are solved by hiding automation - with the quickview filter... ( show active layer only
( I was gettign th eoccasional cash on dragging in sound bite for instance -
Posted: Sat Aug 09, 2008 2:27 am
by ghobish
I'm not having the specific 'split at counter' problem, but I'm getting a lot of crashes on editing as described above (plus some crashing with stuff as simple as deleting a marker). Seriously, if I'm cutting enough tracks as a group, the simplest edit moves will cause a crash, especially if I'm zoomed in.
(New Tiger install, clean system, tested with no plugs installed, removed Mouseworks software, all that stuff.)
This on an 88.2K session with about 20 tracks and no plugs. Sent 4 crash reports on a techlink that has yet to be answered.
Grrr.
However, I've had no problems on my mastering sessions- usually 2 stereo tracks with heavy plugs (Waves mastering and vintage, plus MW EQ) and plenty of automation.
Posted: Sat Aug 09, 2008 3:35 am
by martian
i suspect this is something to do with the pre rendering that they introduced in 5?
it's something to do with the graphics as well -
that's what lead me to the hiding of automation... there's somethign wrong on several peoples systems - and this has solved a few -
i just look at the automation I want when I need to..
less than optimal but after a while seems ok - screen is clearer too!
interested to see if this aligns with my theory... perhaps if enough peopel report this - they may try and fix it..
Hey I'm cheap - I DONT actually want to spend money on expensive software like nuendo...
DP now working pretty well for me.,..
Posted: Sat Aug 09, 2008 9:11 am
by ghobish
martian wrote:i suspect this is something to do with the pre rendering that they introduced in 5?
it's something to do with the graphics as well -
that's what lead me to the hiding of automation... there's somethign wrong on several peoples systems - and this has solved a few -
i just look at the automation I want when I need to..
less than optimal but after a while seems ok - screen is clearer too!
interested to see if this aligns with my theory... perhaps if enough peopel report this - they may try and fix it..
I'd be inclined to agree- I NEVER had these problems in 4.61- even though:
- The sessions it happens to me the most in do not have ANY plugs, and no VIs- so in my case at lease, what's getting pre-rendered?
- It definitely seems like a graphics issue, but I think it's tied to CPU use and disk communication. It always is less stable for me if I'm zoomed in, or editing in large groups (like editing tracking sessions into a master take), or doing pitch correction.
Posted: Sat Aug 09, 2008 12:00 pm
by wurliuchi
Another problem I'm having with DP6 is when adjusting bite gain, the little window that comes up will be blank and I have to click in it to make it fill in, but sometimes even clicking won't work. DP will lock up and maybe two minutes later the window will fill in or maybe DP will crash completely.
This release has too many gotchas for me.
Posted: Sun Aug 10, 2008 2:32 am
by martian
I was super paranoid and uninstalled every version one by one - 5.13 - 5.12 -5.11 5.0
then I installed 6...
blast off -
dp going like a rocket
( thanks to frodo for this suggestion - may his toe hair curl in a pleasant manner!)
Posted: Sun Aug 10, 2008 2:33 am
by martian
i guess I was trying to say that sounds strange.... re install?
Posted: Tue Aug 12, 2008 10:16 am
by ghobish
ghobish wrote:I'm not having the specific 'split at counter' problem, but I'm getting a lot of crashes on editing as described above (plus some crashing with stuff as simple as deleting a marker). Seriously, if I'm cutting enough tracks as a group, the simplest edit moves will cause a crash, especially if I'm zoomed in.
(New Tiger install, clean system, tested with no plugs installed, removed Mouseworks software, all that stuff.)
This on an 88.2K session with about 20 tracks and no plugs. Sent 4 crash reports on a techlink that has yet to be answered.
Grrr.
Perhaps a partial answer regarding this specific session:
http://www.motunation.com/forum/viewtopic.php?t=30713
Posted: Tue Aug 12, 2008 10:46 am
by Shooshie
martian wrote:I was super paranoid and uninstalled every version one by one - 5.13 - 5.12 -5.11 5.0
then I installed 6...
blast off -
dp going like a rocket
( thanks to frodo for this suggestion - may his toe hair curl in a pleasant manner!)
Are you saying that most of your former problems are now gone? (except for the obvious ones for which everyone is in agreement)
Shooshie
Posted: Tue Aug 12, 2008 8:51 pm
by martian
yes I am ( kind of )
DP is pretty stable for me now..
the only crashes have been either
when I "fumbled" double clicking in the timeline... ( twice in 2 or 3 weeks )
or when I leave automation visible dragging clips in ( I have a key to hide auto now - show active layer

- this has happened 2 or 3 times - but its a low occurance percentage as all I do is drag clips in from audio finder....
haven't had a crash on save - ( with or with out automation showing)
and as I am simply hitting save ( as oppose to save as and an incremental number ) a lot of the pain has left my world........
small caveat - yesterday my assistant had a crash on save - BUT on investigation her work method was different to mine... she was looking at all 60 tracks in the SE when hitting save (auto hidden )
I never look at more than 16 as I find it way faster to option click on foley track folder than attemt to scroll up there - its a very organised way of working
So I think there are still minor issues - DP is having probs when displaying a lot of data.. ( ie 60 odd tracks - or 16 tracks with shed loads of automation
I seem at the minute to be able to side step the issue - we will finish this feature in the next 2-3 weeks - so I guess that's the acid test,,, the project isn't yet at full complexity..
fingers crossed.
Posted: Tue Aug 12, 2008 9:44 pm
by Tonio
No problems here.
On a fresh MAC PRO , or on my G4 w/ 4.61. either a fresh project or migrated 4.61.
T