Frage von Robert Kleine:
Hello My dear,
I have the following problem for weeks and already looking for a solution.
When I cut the material and export makes me premiere rendering errors. Old pictures of the sequence rausgerenderten pure flash: sometimes so that it flashes - sometimes just a picture flashes briefly.
I have found a "solution": At the point where the speed camera's on, the video track to duplicate and overlap with 50% opacity ... So that Premiere should edit the part, in any case. This-let's call her "solution" is of course gefrickel it demotoviert the workflow and output declines.
've Tried different codec for export (HuffYUV, Lagarith) - but go zZsbesten with Quicktime.
Here are the dates:
* I'm working on a plank of footage (8-10 hours per week Ausgangs-/Endmaterial)
* Footage is 800x600, 15fps, TechSmith codec, 44.1 Khz, stereo
* Premiere Project is 800x600, 25fps, Uncomressed, 44.1 Khz, stereo
* Export Quicktime animation is 800x600, 10fps, 44.1 Khz Mono
(Hard disks are defragmented every night)
I know that the Source, Target and Premiere Project Settings not be matched ", but since the problem does not occur in each exported file (approximately 1 / 4 of the exported files) and it looks as if swallowed Premiere Pro, consider I am the production path for s.sich OK.
Has anyone had similar experiences and have tips?
Thank you for possibly Tips, Robert Klein
Antwort von Jörg:
Hi Robert,
First I looked again after reading your contribution date.
Nix DA 1 April.
Your "curtsy" seems synonymous to a non-gentle Ver Sche .....
. indicate
You do not really wonder why, on problems in the processing
and mix of these "standards"? Since the reference helps to next 5.xx not synonymous.
Do you take the export actually only salt and pepper, or even synonymous with Mayo Ketchup?
s.Ernsthaftigkeitsgrad highly skeptical of this paper greetings
Jörg
Antwort von Wiro:
In other words:
A software, called PRO, synonymous requires a user to the PRO. . .
;-)))
Greeting Wiro
Antwort von Robert Kleine:
Ok.
Perhaps I have expressed myself too cynical and would have to remain objective s.Problem. I did not convey the theme and just too dry - although I do very seriously and hope to help!
**** I edited my first post ***
@ Joe: No, the issue is not "Ver Sche ..." and I have not synonymous to 1 April missed.
The problem is clearly defined and I am looking for people who have gathered for a similar task with Premiere Pro and experiences may have tips.
@ Wiro: your comment I just let time stand-repellent, because I want to pull the thread is not willfully in the length ...
As I said, I'm sorry to have my problem as "subjectively presented," and thus offer front for "funny" remarks.
However, my problem is real - no Ver ... rsche - and please take it seriously.
Thanks, Robert
Antwort von Markus:
**** I edited my first post *** Good that I have read up to the end. It now says my "blackout" s.der first answer. ;-)
Antwort von Robert Kleine:
Thus,
at the Tread nochma upward boost:
I found the bug in Adobe Premiere Pro 1.5 by chance!
* When the "Export Movie" dialog and predefined settings, go to Settings (which you have) saved invites to come Blitzer.
* If you go in the "Export Movie" dialog NOT to Settings and the settings that has made it so does not change FIRST, DO NOT pass Blitzer of old frames from the sequence. (currently have ca.16 sequences rendered without error - previously all 3 sequences contained errors in them)
"Kling funny - but eat it!"
Regards, Robert Klein
