-
Strange Error Message
-
I’ve got CS 6. I didn’t already upgraded to 6.1 but I will soon.
Actually I “solved” the problem simply by copy all my timeline and past it to a new one… weird but for now the error message didn’t come again. -
People (including me) are still experiencing this (in CS6.whatever), and since this is one of the first threads that comes up when searching for a solution I’ll post what I know. The error occurs when a timeline is trying to play/render a wave file for any audio that is being conformed to a non-native fps. For instance, if you shoot a clip at 59.97fps and then conform the clip to play at 23.976fps (so it plays in slomo), the audio in that clip will generate this error. If you disable the audio or minimize the clip (so it doesn’t need to render the wave image), you shouldn’t get the error. Obviously his doesn’t help the situation if you are trying to edit conformed audio on your timeline and you need to actually see the waveform.
The “copy and paste to a new timeline” solution is not a fix. The error will return. As mentioned, if you don’t need to *see* the waveform, you can simply ignore the error (let it exist behind your main editing window). The audio in the clip (and likely more clips, as you continue to work) will appear blank, but you should be alright to continue editing your project. However, if you need to *see* the wave form (to edit the conformed audio on a timeline), you will need to keep closing and opening the program until the error occurs again.
I have noticed that the “copy/paste to a new timeline” fix does seem to allow the program to remain open a little longer than if you’re just trying to open the project exactly as it was when the error occurred.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit…https://TeahmBeahm.com
https://Digabyte.com -
Dude, I can’t express how stoked I am to see your post. Wsted 2 hours of my life tonight -on deadline no less-with the jack off’s from Adobe on IM who are clueless.
This makes sense, as I do alot of action sports-and stuff is shot at 60p but we finish 24p for film look, and over crank, BUT we bring in a lot of natural audio, not to mention music.
I tend to to my rough edits with mp3s and then the final with the .wav, so I get there’s A LOT of stuff going on.
This will help be manage variables. Thank you!!!
-dan
-
Glad to be of help.
I’ve been working a lot with overcranked footage (including audio) for a project I am currently working, so I have another tip to offer:
In Premiere, right click the audio file and open it in Audition. Click on the file in the Audition timeline and save it as a new file, and then bring that back into Premiere.
Audition will have converted it to a “normal” audio file so that Premiere isn’t trying to interpret slo-mo audio footage on the fly. This should completely solve the problem (as long as there are no more slo-mo audio files on your timeline).
Here’s a blog post I did on the subject.
:::::::::::::::::::::
This is my life, I edit and edit and edit and edit…https://TeahmBeahm.com
https://Digabyte.com
Reply to this Discussion! Login or Sign Up