I'm using the ilok version, which seems to be their only solution to the crash on quit problem for the time being.
That’s quite bizarre that ilok versions cause crashes? I wonder why?
Moderator: James Steele
I'm using the ilok version, which seems to be their only solution to the crash on quit problem for the time being.
Maybe I'm reading that wrong, but he seems to be saying that the iLok version doesn't have this problem?toodamnhip wrote:I'm using the ilok version, which seems to be their only solution to the crash on quit problem for the time being.
That’s quite bizarre that ilok versions cause crashes? I wonder why?
Yes is Mis typedJames Steele wrote:Maybe I'm reading that wrong, but he seems to be saying that the iLok version doesn't have this problem?toodamnhip wrote:I'm using the ilok version, which seems to be their only solution to the crash on quit problem for the time being.
That’s quite bizarre that ilok versions cause crashes? I wonder why?
]toodamnhip wrote:I'm using the ilok version, which seems to be their only solution to the crash on quit problem for the time being...
Dude!! That's a really cool explanation. I like that word you used to describe the bug... "hook" in the system....nice. I feel enlightened.tommymandel wrote:]toodamnhip wrote:I'm using the ilok version, which seems to be their only solution to the crash on quit problem for the time being...
Ever since iLok 'changed' I have had a plug-in that I have to re-authorize everytime I restart my MBP. iLok says it's a Sound-Toys problem, and vice versa. So I would believe that iLok has some hook into the System that might be problematical or poorly coded. My hunch is it relates to the way you can now authorize a computer itself for an iLok-type authorization, instead of it residing on the physical iLok.
I selected three tracks, clicked Project > Track Groups > New Track Group, and changed the drop down menu from Edit and Mix to Custom, changed a few options and clicked OK. I tried it twice and got no crash.sdfalk wrote:When Creating track groups in DP , and going to custom, I find a repeatable crash there.
I agree. But it seems from reports on this board that DP9 is overall solid. It has been solid for me, in that there have been no crashes. Whenever I hit the spacebar to stop, there is a popping sound, like something suddenly shutting off.. could be a CPU spike, but I wouldn't know, I shut that indicator off a long time ago Other than that, works great.MIDI Life Crisis wrote:I really think that specific 3rd party system enhancements and plugs are largely responsible for odd crashes only individuals are seeing. A driver here. A graphic enhancement there. Even certain system settings., a corrupted plist file. I do believe they all play a role in the oddball crashed.
The system and software has gotten so deep and complicated that something is bound to go wrong sometime.
DP has always done this for me. There's an option for this in Setup>Event Chasing. Set to Notes it plays MIDI data from wherever you start the sequence.I'm not sure what it's called, but the MIDI now plays from the middle of MIDI events, i.e. you don't have to play from before a MIDI note to make it sound. So If you have a long chord, let's say a string pad, and (from stopped) you hit play somewhere in it, it will still play those chords, as though it were audio. Is this a result of under-the-hood changes that occurred to make MIDI mute happen?
Interesting.. never knew it was there. Maybe they've changed the default to have it on- that would explain why it's suddenly "new" to medix wrote:DP has always done this for me. There's an option for this in Setup>Event Chasing. Set to Notes it plays MIDI data from wherever you start the sequence.I'm not sure what it's called, but the MIDI now plays from the middle of MIDI events, i.e. you don't have to play from before a MIDI note to make it sound. So If you have a long chord, let's say a string pad, and (from stopped) you hit play somewhere in it, it will still play those chords, as though it were audio. Is this a result of under-the-hood changes that occurred to make MIDI mute happen?
Have you found a fix yet for this issue?jlaudon wrote:It's been great except for I can't seem to change MIDI channels (say I want to assign Machfive-1 MIDI channel to Machfive-2), as the pull down menu doesn't pull down - no response on MIDI track outputs when I click on them, but audio and axes are fine... I then updated to OS X 10.10.3, and that seemed to have taken care of the problem, but tonite as I went into a couple projects, the same non-response on MIDI channels has surfaced again....weird...
I suppose I'll try re-installing DP9 (DP8 works fine) and see what happens.