Infoseite // repairing small error => render from scratch?



Frage von lx2:


Hi,

I have been working quite a while with Premiere.
As input material, I'm usually MiniDV (; completely normal PAL SD 720x576).


The main task of NLE's videos but it is cut. Right? Right!

How can it be that who you a File minimal cuts, the entire file must be re-rausgerendert. Somehow, it is because the main task - the premiere of why it exists at all - not really realized. The wait for the new file but is not proportional to the change ...

I mean, we face time before we have a huge project and would have had to deliver the "in-time" at a customer. Tons of effects on it and a playing time of over an hour.
All well (overnight, for all I care rendered synonymous in Network) 10 hours.

Shortly before submission, we notice that here and there a few frames were cut off too much, or slipped into a title has a spelling-> fixed -> and now?

Again 10 hours to render?? (; can not be true)

or

Only the point of failure to render and then stitch together with other programs. (; = inconvenient)


Somehow it still has a way to simply type in the output file will overwrite those positions. After this answer I am looking really for months ...

... I do not find it because you actually do not exist and he failed to CS4 Adobe has at least something simple such as Direct Stream Copy in VirtualDub integrated into Premiere??

PS: Lately I have read several times the keyword "Smart Rendering". Premiere is now somehow able (; render a pinch with plugin) in the output just to see what has changed and the need to render the already-rendered file s.den flaws can not override everything from scratch?

PPS: Is the Export to a file really quickly if you have pre-rendered with the Enter key yet?

For your answers many times have you!
Greetings from Munich

Space


Antwort von domain:

This is purely an internal organizational matter in NLE. How does the (; smart) rendering in Liquid and HP generally less than 1:1 and indeed synonymous for all, all previously rendered in the background Fx partitions. Mystery to me until today that this multitasking is not synonymous with absolute Timeelinepriorität NL is found in other editors.
So in Liquid and HP is enough to make those small changes and all the rest is again fairly quickly, "smart" rausgerendert.
Come with me several times before I stopped and then wait half an hour to 45 minutes in his new film version.

Space


Antwort von tommyb:

Instead of tapping huge stories that are short and concise question.

If the input material is DV, (, 25 mbit, 420, 48Khz), you play it up as such, are cropping it, play it again as DV, then many mitlerweile Programs able to use this very smart Rednering "too.

Sony Vegas for example, makes no major problems - the pace for the export of material if it thinks it highly of from the hard disk speed.

That is one thing.




If you have changed anything s.kompletten material, the whole will of course be calculated. And it's enough already when you export the color change (; eg of 0-255 -> 601 to 16-235 -> 709).

Space


Antwort von ksr:

In a nutshell: Naturally premiere Smart Rendering / Direct Stream Copy dominated, and not just since the latest version ...

The presumption is that the project settings match the Clipspezifikationen - that is, one can see the fact that - if only hard cuts and no effects will be rendered not exist at all -! Nevertheless, during export must be counted in 1 File - finally since the whole single clips, referenced to the premiere, according to his timeline "zusammenkopiert. Unless, however (again, the format of the Rohclips, dv-avi in your case) corresponds to that goes faster than real time.

But you should really all be clear when you are working for a long time with Premiere.

Quote: Only the point of failure to render and then stitch together with other programs. (; = inconvenient)

Premiere will be the exported file can not "remember" - exports are not even stored in the timeline so far may have already occurred are not re-export "when there are only small changes compared to a Neuexport.
Would be cool if that were feasible, I agree with you - but still can not see it as a core task.

Quote: PPS: Is the Export to a file really quickly if you have pre-rendered with the Enter key yet?
Yes - at precisely the time portion, which was previously used this rendering. But anyway here is the key:
You render it with "Enter", exportierst (and now is faster). Now, if everything fits, it took the same length, as if you were not "pre-rendered" would have. But you discover a mistake and made him mend, all the rest have (; = correct) prerendered points are not recalculated - so the export is (much faster, since only the actual clips) must be zusammenkopiert! Prerequisite: if you save the project file, after the "pre-rendering" (, = then the preview files are stored, the green bar stays in the timeline!).

Space


Antwort von lx2:

Succinctly:

But why then get out completely render output file instead of the old copy and replace the changed parts to?

Space


Antwort von pilskopf:

"LX2" wrote: Succinctly:

But why then get out completely render output file instead of the old copy and replace the changed parts to?

So and not otherwise, I'd make it synonymous. And then trptzdem with SmartRender course.

Space


Antwort von lx2:

Ok, I done a little test time. In fact, (; Ganau just as quickly when hardcuts) the export speed of Premiere like VirtualDub Direct Stream Copy

Hmm, well then I think I better stop workflow, if there has been an error:

eg

Track1: Repairs
Track2: Ausgebedatei
Track3: main movie, split into individual sequences

Then I can always beautiful and have Smartrendern synonymous nen good overview.

Thank you for your info

Space





slashCAM nutzt Cookies zur Optimierung des Angebots, auch Cookies Dritter. Die Speicherung von Cookies kann in den Browsereinstellungen unterbunden werden. Mehr Informationen erhalten Sie in unserer Datenschutzerklärung. Mehr Infos Verstanden!
RSS Suche YouTube Facebook Twitter slashCAM-Slash