MOTUnation.com

Six or seven crashes in that last two hours as I've been tried to mix some drum recordings. I've got 11 tracks (recorded in a Pro Tools studio). I've imported the tracks and painstakingly loaded each take into a separate "take" track. I'd like to use the "Show Takes" feature to expand the takes and the Comp tool to audition the different versions and assemble a master comp... but DP7 is crashing when I click on a track with the Comp tool. I've lost so much work tonight it's ridiculous.

Sorry, I seem to be mentally challenged with this new unicornation skin. How to post a "new" topic??? I had a company do a data recovery on a maxtor drive (boooo!!)

They said this:


To open those two .rsc files you'll need to use the same software which was used to create them.
Regretfully, we have no ability to check or open them, as we do not have that software.

Before that I said this..

Hello, I was able to read the list of files no problem. Do I need special software to open the recording files? I am not understanding what I need. The program they were created in is on my computer(s).

Thanks, DD

Anyone have any experience with normal DP files after data recovery now listed as .rsc? I am a recording engineer not a Computer Whiz... The two are merging faster than I can scream.


DD

detroitdiesel wrote:Sorry, I seem to be mentally challenged with this new unicornation skin. How to post a "new" topic??? I had a company do a data recovery on a maxtor drive (boooo!!)

They said this:


To open those two .rsc files you'll need to use the same software which was used to create them.
Regretfully, we have no ability to check or open them, as we do not have that software.

Before that I said this..

Hello, I was able to read the list of files no problem. Do I need special software to open the recording files? I am not understanding what I need. The program they were created in is on my computer(s).

Thanks, DD

Anyone have any experience with normal DP files after data recovery now listed as .rsc? I am a recording engineer not a Computer Whiz... The two are merging faster than I can scream.


DD

They probably used a PC utility to get back the files who knows but those are resource files. Just go and buy Data Rescue II... that should get your files back but you have to audition each one because they loose their naming conventions when recovered... which is a pain but you do get them back so. When I archive, I always just render any VI's and freeze all the tracks and save them to another file called "archive'. Then, if something craps on you, you at least know that each track of the song is going to start @ 0 and you just have to find each file. But the best way is to just back up your drives!!!!!

I almost never crashed when using DP5 since then I have upgraded to DP7(skipped DP6)
I am still getting many crashes. Can anyone read Crash Logs and HOW do you post them ? THANKS..FV

Please, Davinci, include your setup in your signature (board User Control Panel) :
Soundcard, Mac, OS, VIs, DP release, other musically related hardware and software...

I'm late to the Crash Party, but I'm getting back up to speed with DP 7.1, after 2 years away (last version DP 5).

Tons of crashes and processor overloads; all the tips above duly noted. PLAY from East-West is a central processor culprit. Keep purging samples and fiddling with the engine. (1 or 2 level works best for me.)

One helpful thing I found: look at /Library/Logs/CrashReporter. It might give you a clue. I found over two dozen "M-Audio FirmwareLoader" crash reports. At one point I had downloaded the latest M-Audio driver, thinking I needed it to use my portable M-Audio keyboard as an input device (my CME UF8 is fried, but that's a whole other drama. Don't buy 'em.) Anyhow, I found "M-Audio Firmware Loader" in the /Library/StartupItems and threw it away. Far fewer crashes.

MAS sometimes just stops putting sound into the MOTU 828 on playback (all the level meters are active as if there were sound); I'll let the sequencer run (in silence) for a 45-60 seconds and output suddenly kicks back in. Software or hardware? (It's the 1000-year-old original 828.)

I await Apple's imminent 6-core Mac Pro, and I'm beefing up RAM in the meantime.

Tech Support read me the usual stuff (new user account, etc. etc.) and stopped replying to my follow-ups.

Mac Pro 2x2.66 GHz Dual-Core Intel Xeon, 5GB 667 MHz RAM (Leopard 10.5., Bus 1.33
MOTU 828
East-West PLAY Symphonic Gold/Goliath
Kontakt 3, 4, Garritan GPO Aria, MOJO Horns, FirstCall Horns, Garritan JABB
MOTU Mach 5

HI Hoisingbreit - I am crashing way more than normal since I updated to 7.1 from DP5 , I never crashed in DP5.1 ...as I explained in my early threads. I have the "M-AUDIO Oxygen 2" keyboard..do you think that is screwing DP up?? I also get a crash with my 2408-MK3 hardware setup (screenshots below) the software/hardware just decides to stop and prompts me that I do not have enough memory..which is wrong if you read my gear specs. I even crash sitting idol if i take a phone call.. and then there's the sudden quit while either recording or mixing, etc...anything can cause these crashes it seems..

Here are 2 screen shots re: memory---

OK, I'm made some more discoveries.

Are any of you fellow crashers using Mozy Home Backup?

Rip it out and throw it away. I found two dozen crash items just today in the /Library/Logs/Crashreports -- after something like that many Digital Performer crashes. (Digital Performer is not showing up in the Crashreports.) There were also some "mdworker" which I believe is related to Spotlight, which Mozy (and other backup services) use in their nefarious operations.

I may be overly optimistic, but I think after trashing Mozy, I just got a major bump in internet speed, general operation, and one of my network hard drives (which also has sound libraries) has stopped constantly chattering and grinding away at God knows what.

I'll let you know tomorrow if there's a perceptible difference in Performer's stability.

Davinci, regarding your post above -- I'm a babe in the wood and hardly one to dispense advice -- I'm the one who begs for it. But try trashing the M-Audio Firmware thing as I did in my above post, and see if you get an improvement. Check your Crash logs to see if it was implicated. (Can't quite read your error messages.)

Use Activity Monitor (located in /Applications/Utilities) to see how much RAM each program or activity is using. (Mozy used hundreds of MB of RAM, by the way.)

I wonder if running Logic AND Performer is stressing your memory? You've got a lot of audio tracks running -- where are they, all on the system drive? Most people here think they should be spread around other networked drives (or at least on one, not the system drive.)

And how is Logic, by the way?

Now here's a basic question that I'm embarrassed to ask, but I will:

1. I bounced MIDI tracks played by virtual instruments, intending to use the resulting audio in the final mix. The volume fader in the Mixing Board had not the slightest effect on the volume of the resulting audio track (yup, enabled, etc.)... The only thing that would affect the volume was drawing in stuff called "Bite Volume" in the Soundbites window. That's no way to mix. Why won't the Mixing Board fader work on Bounced audio? It works on audio from a Freeze, and audio recorded in real time into a new Audio track.

2. I recorded 4 MIDI tracks into a new Audio track, with the Audio track's input set as Analog1-2, output Analog 1-2 -- and nothing goes into the Audio track. Why not? The only way I could get a recording was to use an input of Bus 1-2 (setting the virtual instruments to output into Bus 1-2) -- and then I can't hear what's being recorded, no way, no how.

I'm probably doing something idiotic, or don't understand something basic, but knock yourselves out. Fill me in.

Roughly 20 crashes today. It only happens when I:

1. Save. Poof, gone are the changes. 5 times out of 10.

2. Playback. Poof, the program vanishes. 5 times out of 10.

3. Anytime. Maybe 3 times out of 10.

I've been through the war since 1990, since the early days of Finale 2, Vision, Cue, Vision Studio, then the switch to DP.

I've never experienced anything like this.

I'm getting more RAM on Wednesday, but after 3 weeks of troubleshooting, scouring, fixing, de-bugging, I'll hit MOTU for a refund on the DP 7 upgrade and give this Logic thing a try. I'm not afraid of no learning curve -- an associate uses it and has never experienced anything like what I've been through these three weeks, on a similar set-up, with far more complex work than the baby song I've been doing.

NOTE: PLAY library stopped sending processor spikes after getting rid of Mozy. So that's the good news.

(Tech specs above.)

hoisingbreit wrote: I'll hit MOTU for a refund on the DP 7 upgrade and give this Logic thing a try.
---
NOTE: PLAY library stopped sending processor spikes after getting rid of Mozy. So that's the good news.

Somewhere in the section on MOTU hardware was a note about problems with the original 828 and an recent audio driver update. Also somewhere above, or maybe another thread was a note about issues with Play. Really hope you can figure out what is wrong with your setup. I'm amazed by how solid and especially how efficient DP 7.1 is on my ancient G5.

But if not, good luck with Logic. I've just abandoned it for good after my third attempt in five years to find a workflow that makes sense and reliable performance. The only use I have for it is to port projects that someone started in Logic, and cannot finish, into DP. Aside from a few gimmicks, I've been unable to find anything Logic does better than DP.

bayswater --

Thanks for the reply. I'll look for the notes about the original 828; it's high time I replaced it anyway, since it's something like 15 years old, and I had suspected it might be contributing to the weird MAS drop-out on playback (15-30 seconds of silence at unpredictable moments.)

Since East-West PLAY has some outstanding libraries, I hope that if there are in fact issues with DP, the two companies get together and resolve them immediately. At the moment, they're playing nicely together, unless PLAY is somehow implicated behind the scenes in the egregious DP crashes. PLAY is indeed a new element in my studio, so I have given it special attention in trouble-shooting.

An associate has rock-solid performance in Logic, and used it on a TV show we did together -- I don't care if it "does anything better than DP," as long as it doesn't vanish from the screen and crash time and time again, making work utterly impossible.

MOTU Tech Support has very limited resources, time, or sense of follow-up. I appreciate the difficulties we all face in using software from multiple companies and expecting them to work together -- but we do, and they must. Does MOTU (or Apple-Logic) issue specs to the sample library companies and virtual plug-in industry to GUARANTEE compatibility? Or is it the Wild Wild West? I suspect the latter.

Most of my crashes have been on startup and I think it is related to Omnisphere loading up. I'm running 6 tracks in Omnisphere and about 40 other tracks through 5 different kontak instances. Omnisphere is 3rd in line on the loadup and when it has finished loading, there appears to be a delay with the next kontakt instance loading and then it crashes. I changed all my Omnisphere patches to a lite version and it crashes much less, but still happens exactly the same way.

Any other crashes I have had were very rare and only when I have a full pallet of sounds loaded up, like 70+ tracks.

Hi Guys!

Do you have tips on how to avoid crashes with DP 7.12? Thanks.

I am crashing too .. The update has made some tasks
difficult .. I crash when making edits , tweaking plug ins,
moving to fast for Dp etc.... I have a very powerful MAC
and new interfaces. Everything is updated to the latest
drivers and versions..
so why is DP 7 crashing so much since I updated
When I was working in Dp5 it was flawless ..

davinci53 wrote:I am crashing too .. The update has made some tasks
difficult .. I crash when making edits , tweaking plug ins,
moving to fast for Dp etc.... I have a very powerful MAC
and new interfaces. Everything is updated to the latest
drivers and versions..
so why is DP 7 crashing so much since I updated
When I was working in Dp5 it was flawless ..

I don't understand this at all. You guys must have gotten a completely different version of DP 7.12 than I did. It makes ABSOLUTELY no sense.