My Blog of Nuendo crashes...

[colony nofi]

I might delete this topic yet... but we'll see...
I've been suffering instability issues with nuendo - perhaps worse than in recent months, perhaps I'm just in a worse frame of mind (getting sick of it)

So I've decided to document them here - just a brief description of each one. One, it might help me see more of a pattern, and two, others might see a pattern / notice things on their own systems as a result of it. I have a sneaking suspicion that there are three or more different problems rearing their ugly heads. Hopefully this will show it.

I might start a new post a week or something. Can you tell I haven't made up my mind quite yet about this whole idea? :)

Ok. For reference, these are the three machines I regularly use nuendo on.
Machine 1. Mac Pro 8 core early 2008, 8GB Ram, 4x750GB HD's, Metric Halo 2882 interface. Blackmagic Intensity.
Machine 2. Mac Pro 8 core early 2008, 6GB Ram (I always thought it had 8...!) Apogee Ensemble interface. Blackmagic Decklink.
Machine 3. Macbook Pro Core Duo late 2007. 4GB Ram. Metric Halo 2882 interface.

Main software (identical on all): Native Instruments Komplete, Voxengo, URS, Stilwell, IK, Izotope, Omhforce, DDMF plugs, Altiverb. Also have Logic 8 on all systems. Machine 1 also has Live, Digital Performer 6, Energy XT etc.

Any other details anyone thinks would help tie things down, let me know.

Thurs Aug 6.

3:55pm. Machine 2. New session. New Mac Boot. (5 mins into using the session, no tracks created yet.) Listening to samples in the media bay. All samples are on one drive only on all systems. Clicked on a file. Nuendo quit. Had successfully listened to 20 or more samples in the same directory already in that session. Confirmed that the file is ok. Have already auditioned it since in another new session.



Ok. So there you go. We'll see where this takes us.
Cheers! Brendan.

[TAFKAT]

Brendan,

Check with system 2 that you don't have some dead or problematic memory modules , that could be causing the flakiness, and also explain why you have lost 2GB if that is the case.

Another thought, memory in those Xeon systems needs to be perfectly matched, it sounds like you may have some miss matched modules , that could have happened when the Apple Dealer who you bought the system off just added some extra memory to the existing (crap) standard memory that the system was shipped with, as Apple in their wisdom did not spec the systems standard with the required 4 memory modules, only 2, or you added the RAM yourself, either way, its not recommended that you have miss matched modules.

Let me know what pans out there..

[colony nofi]

Heya Vin,

I will check - all the memory in both machines were put in at time of purchase - it is well worth checking though.
I'll be ordering a bucket of memory next week methinks - i think it will be prudent to just buy 12 or 16 GB of kingston for both machines and take all the old stuff out... If i had the time to investigate further, I would. But just not right now...

Thanks for the ideas...

Brendan Woithe : Nuendo crash free for 20 hours.

[The Guru]

I wouldn't beat my head against the wall, there's nothing wrong with your system. The problem lies with Mediabay. I can crash any project auditioning files in MB. This is the only time anything crashes here, my system is rock solid other than that. I never get corrupt projects or crashes except with audition.

Instead of Mediabay, I've been using the Sound and Loop Browsers with greater success. Set up MB to scan only DAW folders and close it and forget it.