AndrewAction:

Scott Silva:

Right now since I am only worried about picture for color correct

I appreciate you need to get on with the Colour corrections but do you have time to try reimporting one of the offending BWF files from the field recorder directly into 6.0.3?  Thanks

I do not have access to the original field recordings to try that.  Only the MXF files created by my Assistant Editor.

Scott Silva:

I also suspect that the Matrox MXO 2 Mini is the cause for a lot of headaches, like long delays when switching between clips while color correcting.

I've found if you turn CAPS LOCK off (Audio Scrubbing) the Symphony performs much better with the Matrox MXO2 Mini.

Only had one error in Color Correction mode (so far) today.

Errors corrected for me are:

Video Underrun

Audio Underrun

BlipPlayer::NonThreadedPlayBlipField: Timed out waiting for single frame player to stop.

Do you have the same issues using Symphony as software only without the MXO2.

Radman.

No.  When the Mini is attached I need to keep CAP locks off to work.  When I work without it or on my laptop no issues.  And I can edit audio and scrub frame by frame without seeing a beachball spin or get an error.

BMDesigns had the same issues with their drivers until it was sorted.

The dataBase issue I am not sure of.

Radman.

How I love this Forum.

Back on topic- I now realise why I am here after midnight trying to rebuild the database on a Unity using Symphony 6.03.

I've still not been able to resolve this problem. I'm going to try 6.0.3.1 in hopes that maybe it'll make a difference. Otherwise, I'm assuming it has to be a bug.

I have not found a solution either.  I have found a work around.  I took the drive to the client location, which was a MC 5.5.3.  I had previously renamed the MFX internal folders from "1" to some other name .1 (ie: PW.1)  This way while on my system Symphony would not attempt to rebuild databases in those renamed folders.

Now while attached to clients system, I took the folder of 485 audio files, and renamed its folder to "1".  The databases rebuilt.  I then renamed the folder to PW.4, hiding the database from the rebuild process.  So far so good.

This is how I will proceed with future media sent from my client.  I know it doesn't help if YOU are the originator of the media, or if visiting your client is not geographically possible.  But it has helped me as far as a plan going forward.

I will download the patch myself and hope it prevents future problems, but I think the problem may be bigger.  Fingers crossed.  I am going to take the preventative step of renaming folders and only try and create media or render to a folder created by my system.

Scott Silva:

I will download the patch myself and hope it prevents future problems,

Since I'm not on Mountain Lion yet, no need to install this patch.

Scott et al.......

Good news....... 

Mac 6.0.3.x on Media Network will hang indexing databases.

This should be fixed in an upcoming 6.0.3.2 and whatever the next 6.5 patch/maintenance release will be - I dont have info yet on the dates or releases but I know the issue is resolved on Mac.

Marianna 

Hi

Since we upgraded our two symphony systems (last august) we have lost so much time trying to find a solution with those databases that couldn't proprely rebuild... Lost medias, application unable to start, crashes...

We upgraded from 6.0.1 to 6.0.3 whithout fixing that problem.

I'm really glad to read that the 6.5 release will fix that disaster ! But did anyone allready experience the end of the troubles after installing it ? 

Thanks

François

Symphony 6.0.3 / Mac OS X 10.7.4 / Unity - Fibre Manager 5.5.1

Glad to know there will be a fix in the future.  Thanks.  I patiently await the patch and will continue to find work arounds in the meantime. 

Hey all, I posted this in the other thread, but just in case you haven't seen it:

it my case it looks like the problem was cause by importing the audio files into a standard definition project. I imported the files into an hd project, deleted the old ones, rekindled and now I don't have the issue. Maybe it could work for you, not sure if everyone is having the same exact problem though.