![]() ![]() However I always removed the 'merged' portion of the name each time in order to preserve naming conventions for later on in the workflow.Ģ.2 So currently I do in fact have a mix of transcoded (see above specs) and native format in one project - however I don't think this is the issue as I have used merged clips for the entirety of project before.ģ. Import media into Premiere Pro CS6 and edit with these clipsĢ.1 At one point to save time and due to an assistant being incompetent, I had to sync media in Premiere Pro CS6 using the 'Merged Clip' option. Import media into Da Vinci Resolve 12.5 - Sync & Transcode out as Apple Pro Res 422 1920 x 1080 25p. The footage I am working with is from the Canon 5D and GoPro Hero 2/3 (never got the exact specs from paragliding instructor)ġ. My workflow for post production has been as follows so far. It gets to about file 1645 of 2000+ and then CC 2017 crashes with the message "A serious error has occurred." However it then attempts to reconnect all my footage. Now I did a bit of research online and it looked very likely that my CS6 project would be compatible with CC 2017, so as far as I can tell that's not where the problem is originating from as CC2017 was able to open my project. However I was worried that when it came to the final export these errors may come back to haunt me in the form of corrupted exports or something, thus I bought cc 2017. So I opened up the code again, saw nothing had actually changed as it was still 'Quicktime', saved the file anyway, said a quick prayer to the Post Gods and tried to open the project. The solution was to change all occurrences of 'I-Frame Only Mpeg' to 'Quicktime', which would allow me to open the project, however upon trying to open the project in the follow sitting, I would get the same error. I looked up this error online and found a solution that involved editing my project file on a friend's Window's Machine using Notepad++ That seemed to be working for me until about a week ago when the project came up with an error when I tried to open it, stating something like "You do not have the correct codec installed". Reached 3 crashes in a space of about a month. In each case I would save the project with a new name when prompted after a recovery and indicated which crash number I was on in the project name to keep track. I'd had a total of 3 serious crashes since the start of post production. I originally bought CC 2017 this morning because I thought it would fix the issue I was having with CS6 recently, so perhaps that issue may help shed some light on the new problem.Īdditional Monitor: DELL S2340L (23-inch, 1980 x 1080)Īfter working on a feature film for my Masters for several days, I am now sitting at 43 minutes so that's what is at stake for me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |