new user new settings new MSM files

Crashes in color correction mode.

Anyone else seen this?

What version of the software? There have been some reports of this in the Tiger versions over on the 'Pro forums.

Most of the time that the CC crashes, I've found it due to corrupt media or a drive problem....possible?

Avid MC Adrenaline version 1.8.1
Mac Dual 2.7 4 gigs of RAM
OS 10.4.2
Ultra 320 dock with 12 73 gig stripes.

Threw out suspect media. I am on the phone with Avid right now. We made a new project imported bars on a new line. If you click around on the time line it will eventually go to the spinninng beach ball of death.

It is also happening on the machine upstairs that is configured identical.

We have all been digitizing without any problems. Just so happens that we are just now starting to color correct our projects after upgrading.

If it's any consolation, I just did a quick check on my systems and had no problems so there may be a solution out there.

If you take ALL of your media offline and just try to C the Media Offline slides...does this still happen?

If you take ALL of your media offline and just try to C the Media Offline slides...does this still happen?

 

Yes, it did still happen.  I downloaded a clean copy of the Avid software and uninstalled/installed it again.  Tech support has an email going out trying to find a cure to this one.

So far there is only one machine that will do it even with new user settings/project/site settings, but I will keep experimenting in the morning.

If any of you has an idea don't be afraid to give it.  I will keep trying till I have to clean install the entire machine. (last resort of course)

Avid MC Adrenaline version 1.8.1
Mac Dual 2.7 4 gigs of RAM
OS 10.4.2

A Couple of thoughts....

4 gbs of ram?  Who makes the additional ram, there have been problems with Kingston Ram.

Have you treied the CHUD utility.  The CPU is dual processing but Avid only runs on one.

.Do a Google search for Apple + Chud.  The Chud utility temporarily turns off the second processor.

HTH

Good suggestions mvegas

All of my RAM came from Avid and is Crucial in brand.

I would follow the CHUD path but we have 2 machines that have not shown this problem.

I have a strong suspicion that it is some sort of corruption. I am going to once again try trashing the old and using newc user/project/settings/msm across the board and see what happens.

What resolution is the media?  If it's anything other than 1-1, digitize and try again on a 1-1 clip.

Todd

I think we have found the solution.

We moved the projects to the desktop into another folder. Deleted the projects folder and user folder so that the software would create new folders for projects and users.

We deleted the Settings folder inside the Media Composer folder.

We deleted the MSM files on all stripes AND all render files for effects rendered yesterday.

Repaired disk permissions, restarted, made new user and project and tested...no crashes.

Made a new project and pulled the suspect project's bins (and bins only) into new project and went back to same sequence that was the original crashing sequence....no crashes.

I will keep you all posted but I think everything is going now. I believe there were corrupted files transfered to both my machine and the other that was crashing. I will update as I try this fix and let you guys know what happens.

I expect a few more bugs since we just installed 6 MC Adrenalines (4 mac and 2 PC), 9 Xpress Pro stations (PC and Mac some with Mojo, some not) and a LANshare system.

We will be the guinea pigs for you guys.

just out of curiousity...where you using the YC waveform in the "next" or right hand window when your color corrector was crashing?

I reported this problem as few weeks ago on my G5 2.7 and blackdog has been waiking me through all kinds of possibie remedies, but tonight, after following your proceedure, I noticed it happened only when I had the waveform on.

I just looking for some similarity to report.

just out of curiousity...where you using the YC waveform in the "next" or right hand window when your color corrector was crashing?



As a matter of fact I did have it in my window.

We are still going pretty well as far as I can tell. I think we might have isolated the problem. We transfered some projects via Firewire to both machines from an Xpress Pro station (we did not have the LANshare going then). I had to jump through major hoops to isolate and delete corrupt media files that all came from those projects.

It was a complete across the board delete of projets folder (move your projects out of course before you delete the main folder), user settings folder, settings folder inside the Media Composer Adrenaline folder and MSM files from the drives to isolate and delete corrupt files.

The only part that was tough was finding the corrupt media because the software would lock during MSM rebuilding, so I had to use the method of creating another folder on one drive at a time...moving all the media from that drive into the new folder and moving files back a few at a time till I deleted all the bad files and the MSMs built back without a problem.

I will post again early next week if things go cross-eyed again.

thanks for your reply.
I noticed that when I used any appliance in the right window"
Quad, vectorscope, waveform, etc...I would get a black and white, slow spinning ball when I moved the curser around any of the timelines. Master or the color window. It would go away when I stopped movement, but appear again as so as I start. When I returned the right "next" screen to an image, the black & white ball went away and so did the problems.

I found all this after following your suggestions/directions about moving project folders and all that.

It may be a G5 2.7 thing, not sure yet, but mow that there is more than one of us, they might listen a little closer.
Thanks for your input
Chuck

You are back working again, right duckyou?

I will try to see if I can make another machine crash by changing the next to an app when I get some time.

Maybe you are right and Avid will start working on thiis. I can't say if it is a 2.7 problem since all 4 of our Mac MC Adrenalines are 2.7 models, but I would have to be doubtfull of that being the culprit.

If it was just the window and not the projects I will be ticked since I virtually lost an entire day on this project that is due next week.

I can't get too angry...I am having far less problems than I did the last major upgrade and install.

Yup. Thanks to your post, and some insight from blackdog, I kept reloading stuff and hence, re-setting my settings. It was only after I changed that third window that the problem returned, so I began to do some with and without tests.
I didn't lose a whole day, but I lost a ton a work just before delivery. As for the 2.7. I'm just looking for parallels

Thanks again