Reopening project right after successful render, shows red on timeline
Nanda_KP Feb 2, 2014 4:22 PMCS 6.0.5
Win 7 Professional 64-bit
i7-920 (OC 3.99)
gtx570 (latest driver)
24gb RAM
RAIDs for media, render, output, media cache etc
OS/CS6 - 1TB 7200 rpm
I have 2 video tracks in my sequence;
- track1: Matrox AVI (8-bit MPEG-2 i-FRAME)
- track2: MPEG (.MTS)
Track1 effects : Neat Video, RGB Curves
Track2 effects: Neat Video, Levels
Length of both tracks: ~3.5hrs
The following are most definitely bugs!
- when I tried Render Effects in Work Area, PPro memory usage climbs up steadily to 23.9 GB (all of the RAM) and it crawls to a halt and throws a Video Preview error: Error compiling Movie.
- I tried breaking up Track1 into multiple clips, still the same
- finally, I resolved this, by creating subclips of each clip on track 1 and then rendering the subclip in new sequence w/ the effects applied and then copying over the rendered subclip back onto the original clip in the first sequence. This way, the memory usage was steady without climbing up. There were no crashes.
- After working on each subclips in this manner, I Saved the project, closed it and reopned it, only to find portions of track1 showing up Red on the timeline, EVEN THOUGH the rendered files were there on the render disk and even though there were no crashes, errors, restarts.
- luckily I had AutoSave=every 20mins, #save files=5 and I went into the Adobe Premiere Pro Auto-Save folder in the project folder, and found 4 project files named - <projectname-1>..<projectname-5>. In one of them I found a nearly fully rendered track1, with just a few red portions (which had actually been fully rendered by previous attempts) which I then opened and re-rendered the red portions.
- I came across a workaround on the Adobe Forums, from Jim Simon (or Jeff Simon) who suggested to create an empty sequence after successfully rendering a sequence and then closing the Project, w/ the empty sequence displayed. This way when PPro is re-launched, it will open to the empty sequence and the original sequence should remain intact - this worked for me.
But I have no idea why PPro should fail miserably to detect the render files forcing me to restort to these gimmicks!.
for added caution, I saved the auto-save project, now showing all green on timeline for track1, saved it to original project file (overwriting the original project w/ the autosaved project) - closed PPro - reopened original project as well as autosaved project (<projectname-5 for example)>).
- then I proceeded to enable the 2 effects on track2, disabling output of track1 and then kicked off render of track2 (without using the subclip approach as with track1) - which was successfully rendered in 20hrs - Great!!.
There was no increasing memory usage like with track1 render action. At the end of the render, I see track2 video playing just fine.
- So I stop the playback, switch to empty sequence, Save project;
- then I go back to original sequence, enable output of track1 and the timeline is red!!
- So, I disable track2 output, leave track1 output enabled - still time line is red!!.
- I disable track1 output, enable track2 output - timeline is green!!!.
- I close PPro, relaunch it - it opens into the empty sequence as expected, then I switch to original sequence and still timeline is red with both track1 and track 2 output enabled. If I disable track1 output, timeline is green.
- I locate one of the AutoSave projects that was close to the time when the track2 render completed, open it and now timeline is green when track1 output is enabled, and red when track2 output is enabled.!!!
So now, I have track1 rendered files detected in one Autosave project, track2 rendered files detected in another project, but both are not being detected in the orignal project.
Track1 is camera 1
Track2 is camera 2
I want to create a multicam sequence cutting between the 2 camera angles, with the effects applied.
I thought of these 2 approaches:
1. render all tracks first, then create multicam sequence which would use the render files and do the final export
2. apply the effects on the tracks but keep them disabled, then create multicam sequence, go back to original sequence and enable the effects on all the tracks (which would cause multicam sequence timeline to show red), export the final multicam sequence
I preferred approach 1 so I can have a look at the final clips before doing the multicam edits.
Symptom1:
PPro CS6 loses track of previously rendered files in the even of a crash (already reported in forums)
Symptom2:
Pro CS6 loses track of rendered files by simply toggling ouput of a track, after another track is fully rendered
Symptom3:
Pro CS6 randomly inexplicably uses up all available memory doing a render of a clip, but does not do so, when the same clip is made into a subclip and rendered on a different sequence.
I've read lots of threads on Adobe forums about how PPro does not keep track of render files (lost render files) in cases like a crash etc.
I can understand losing track of the file being rendered at the time of a crash, but even files that were already rendered at the time of the crash are lost - which should be a bug.
But this is worse: the render files are lost right after a successful render, even when there is no crash, no hang, no high CPU usage, no high memory usage - where's the reliability?
Of What good is Mercury Playback, Dynamic Link etc, when you are forced to redo your renders repeatedly??
I'm very frustrated as have been others at the lack of a visible positive response from the Adobe staff to these symptoms on the forums.
I'd like to be able to demo this on a remote session.



