DP 4.6 IS OUT

[Tritonemusic]

..

[blue]

Originally posted by jimmy330:

Originally posted by blue:
After successfully working on a file for an hour or so, I crashed in the middle of editing pitch automation on a soundbite. I reopened the file and it crashed almost immediately as I began editing the same bite. Now the file won't open at all without crashing. It will start to load my EWQL Gold patches, then crash.

Not sure what happened. Maybe DP's preferences got corrupted or something.

Blue, I just had that today with 4.52 & 10.3.9.
Launches but crashes while loading 1st Call Horns.
After many different tries I opened a "new" file from DP then "LOADED" the Seq. Somehow because the new file had no audio outs in bundle, 1st Call wasn't crashing out the program. DP sometimes corrupts files, the Load function can sometimes straighten them out.

Yea, the load feature in DP is a life saver when files get corrupted. After some troubleshooting, however, I deduced that maybe the file itself wasn't corrupted. Turns out, another version of the file in the same project would also not load without crashing.

In case you're interested, I started a new thread about all this here

[Splinter]

Originally posted by 666:

Originally posted by Brian W. Ralston:
I am starting to see a pattern on the boards of processor spikes and crashes alongside people running DP 4.6 under Tiger. I am running on 10.3.9 and have not seen any spikes and have not crashed yet on anything.

Maybe its just me...or am I wrong?

I'm using 10.3.9 and so far, it's been nothing but fun. No spiking or crashing.

-Dual 1.25 G4 MDD, 1.75 GB RAM-

Same here. Feels very stable so far. Not one crash with 5 or 6 hours of use. Dual 1.8 G5 and 10.3.9.

[bigdaddy]

Originally posted by blue:

Originally posted by Big Daddy:
As for the V-Rack, it's great for FX chains and the like, but almost useless for hosting VI's because you can't freeze anything in a V-rack. Whoops... did we forget something here

Can you route the output of the VI back into the main sequence on an aux track and freeze that? I hardly ever use the freeze tracks function, so excuse me if that's a stupid question.

Hey Blue - You can route the VI's in a V-Rack to a bus and then assign that bus as an input to an audio track for printing, but that's a step back IMHO.I'll try your suggestion as well. I hope MOTU continue to improve on the V-Rack feature and possibly get it to the point where you can (A) address an entire rack of VI's as one synth with one MIDI track if you so choose (B) one step freeze functionality, etc...

I'm not complaining here, I would just like to see this taken a step further. A sort of V-Stack type of functionality built into DP would be awesome - Of course, when that happens, I'll HAVE to upgrade to a dual G5

Judging from others response, it looks like 10.3.X is the better choice so I may be trying that as well.

<small>[ July 09, 2005, 09:13 AM: Message edited by: Big Daddy ]</small>

[wonder]

Originally posted by Kazrog:
MOTU rules!!!! This update is absolutely amazing. No crashes, and the new features are unbelievable! Everyone should print out and read the PDF that comes with the update!

I cant find that PDF....where is it posted?

[Splinter]

Originally posted by wonder:

Originally posted by Kazrog:
MOTU rules!!!! This update is absolutely amazing. No crashes, and the new features are unbelievable! Everyone should print out and read the PDF that comes with the update!

I cant find that PDF....where is it posted?

The PDF is in the DP 4.6 folder under Applications.

[bigdaddy]

Originally posted by Rush909:
Can you uninstall 4.6 update? I am still on 4.5 but would like to give 4.6 a try, but is there a way to revert... can I "save" my current 4.5 files and revert to them in case 4.6 give me trouble... is there a set of directories or files I need to save to be able to revert back? anyone done this?

thanks!

r.

While DP 4.6 does create a new folder and leaves the 4.5 stuff intact, be aware that it replaces your MAS plugins and possibly some other things. So a rollback to 4.5 would require a reinstall to write over the stuff 4.6 replaces. Hopefully, this would replace everything and not leave any 4.6 components lingering.

If a reinstall can't overwrite the 4.6 stuff, then manually removing all DP related components would work - That wouldn't be too much fun though.

[qo]

Originally posted by Brian W. Ralston:
I am starting to see a pattern on the boards of processor spikes and crashes alongside people running DP 4.6 under Tiger. I am running on 10.3.9 and have not seen any spikes and have not crashed yet on anything.

Maybe its just me...or am I wrong?

No, Brian, I don't think you're wrong. I surmised the same back on page 6 of this thread.

I think I've been able to eliminate the crashes though (of course, it'll probably crash as soon as I submit this ). It's been stable since early yesterday evening after I did the following:

1. Trashed prefs and AU info cache (I kept the old prefs to compare to see what might be different between them and the prefs I've reconfigured). i.e., in Terminal:

diff old.plist new.plist

2. Dragged the iSight Audio plugin out of the HAL folder

3. Removed a PPA 64-bit Firewire 800 card

I'm still getting spikes on larger projects (> 40 tracks with plugs sprinkled liberally) but I may be pushing the limits with these.

[thracks]

Originally posted by Big Daddy:
I hope MOTU continue to improve on the V-Rack feature and possibly get it to the point where you can (A) address an entire rack of VI's as one synth with one MIDI track if you so choose (B) one step freeze functionality, etc...

Couldn't you do this using Device Groups? I haven't tried yet and I'm not in front of DP right now but it seems like it would work. As far as freezing V-Rack tracks, I'd like to know too. It seems like a difficult process bussing each track out to record to audio. I initially asked this question here

[Sylver]

Well, I guess I should hang back for now. I'm a new Mac user and only have Tiger, so ...

Oh well, I'm a new DP user so I still have plenty of things to learn while they work out the bugs.

Is there anyone using Tiger on a G5 with 4.6 that isn't having problems?

[qo]

Originally posted by thracks:

Originally posted by Big Daddy:
I hope MOTU continue to improve on the V-Rack feature and possibly get it to the point where you can (A) address an entire rack of VI's as one synth with one MIDI track if you so choose (B) one step freeze functionality, etc...

Couldn't you do this using Device Groups?

Yep, thracks, that's the first thing that came to my mind as well. Yes, you can do this. I use VI's in Device Groups quite a bit. I'm sure there are some subtle differences, but I haven't played with V-Racks yet.

[blue]

Originally posted by thracks:

Originally posted by Big Daddy:
I hope MOTU continue to improve on the V-Rack feature and possibly get it to the point where you can (A) address an entire rack of VI's as one synth with one MIDI track if you so choose (B) one step freeze functionality, etc...

Couldn't you do this using Device Groups? I haven't tried yet and I'm not in front of DP right now but it seems like it would work. As far as freezing V-Rack tracks, I'd like to know too. It seems like a difficult process bussing each track out to record to audio. I initially asked this question here

When I set up a template, I almost always have my VIs routed to one bus or another for submixing. When I need to print something, I just create an audio track with the same assignments and hit record. I guess it's one more step than freezing a track, but I never notice because this is how I work. I almost never use freeze tracks.

Not that that's the only way to work, but it certainly doesn't seem hard to work that way.

[thermos]

Yeah, it possitively sucks ass in Tiger. I started getting insane audio dropouts and error messages during recording of one track, and thats with no plugins. I repaired permissions 1,000 times, and even deleted audio unit cache and prefs. Back to 4.52 I go!

[David Polich]

Well that's it, I'm waiting for 4.61.

Historically this has always been the case with updates from MOTU. I applaud them wholeheartedly for making such major new features available. I just can't recall ever seeing a new version come out that wasn't followed by a "small" update.

4.61 here I come!

[Kubi]

Originally posted by blue:

Originally posted by thracks:

Originally posted by Big Daddy:
I hope MOTU continue to improve on the V-Rack feature and possibly get it to the point where you can (A) address an entire rack of VI's as one synth with one MIDI track if you so choose (B) one step freeze functionality, etc...

Couldn't you do this using Device Groups? I haven't tried yet and I'm not in front of DP right now but it seems like it would work. As far as freezing V-Rack tracks, I'd like to know too. It seems like a difficult process bussing each track out to record to audio. I initially asked this question here

When I set up a template, I almost always have my VIs routed to one bus or another for submixing. When I need to print something, I just create an audio track with the same assignments and hit record. I guess it's one more step than freezing a track, but I never notice because this is how I work. I almost never use freeze tracks.

Not that that's the only way to work, but it certainly doesn't seem hard to work that way.

Yes, after I realized that Freeze is real-time, I actually consciously stopped using it a long time ago, and am recording and monitoring my "frozen tracks" instead. The "side benefit" of catching small musical and programming mistakes is just to good to pass up. So, while I use "bounce" a lot since it's usually a lot faster than real time, I never freeze.

And thus, BOY do I love V-racks with no caveats from my side... chunks are back to being very very useful again. Yay.

Oh, and just for the stats: no weirdness at all so far, knock on wood, with DP4.6 and 10.3.9 on 2x2G5, 3.5G RAM.

<small>[ July 09, 2005, 02:24 PM: Message edited by: Kubi ]</small>