Raylight to Adobe Premiere Pro 3.1 Project File Crash Workaround.

[Demistate]

Just in case you didn't know, when you update your Premiere Pro to the newest 3.1 with DVCProHD support, all of your old raylight project files will make the editor crash when you try to import them in.

Uh-oh.

We'll the reason why Premiere Pro locks up is because PPro can see the secondary audio channel in the file. When you originally conformed the audio with raylight, only one stereo audio track was conformed. With the new version of premiere, it will freak out when it trys to read audio that was not conformed to the new standard with both audio tracks.

There are two work arounds to make your project files workable:

1) Before updating, or on another PC with Raylight and Premiere Pro 3.0.1 or earlier, you can do a sound export for all of your audio attached to MXF video, delete all of the audio in your timeline, replace it with the new wav files you've made, and then import old project into a new timeline.

OR

2) You can offline all of the files, save the project, make a new project in PPro 3.1 Import your old project and manually re-link all of your media.


I've found that #1 is easier to do for longer projects. I have not tested #2 but it should work as well.

WARNING:

If you have 720pn overcranked footage in a 1080i project, the video will show as offline on the 720P video, and you cannot re-link it no matter what. The only way to get this footage back is to re-import the 720pn footage again and just manually put the edit in.

Maybe this Crash could be fixed with an update from adobe, to force only A1 or A2 channels to be read instead of both being imported.

Use this thread to ask any questions related to moving your Raylight Projects to Native Premiere Pro.

 

[srfjm]

are you still able to work in your Raylight project with the Raylight settings? or is there a conflict such that you can't use the Raylight codec anymore?

Out of curiosity, have you tried starting a new project using Raylight settings? I'm wondering whether the problem is just with Raylight projects started before the CS3 update, or if Raylight is totally unusable for future projects as well... I like the Raylight codec for a lot of things...

I'm going to wait a bit to install the update.

JM

 

[tdoglovin]

I haven't been able to try the audio trick yet. I can confirm that method2 doesnt work. For some reason, doing it this way causes everything to be out of sync with the cuts.

This is disasterous for me.

 

[Demistate]

I haven't been able to try the audio trick yet. I can confirm that method2 doesnt work. For some reason, doing it this way causes everything to be out of sync with the cuts.

This is disasterous for me.

You may have to uninstall your Premiere Pro CS3, and re-install it, DON'T update it, and then reinstall Raylight just to work on your project.

 

[tdoglovin]

Thats what I ended up doing. Its a bummer because the native P2 support is far superior to Raylight. I was blown away by how fluid and sharp CS3s native support was. At least I'll get to use it for the next project!