Dissolves, mixes, cross fades..help wanted!!
Moderator: Ken Berry
-
dalsegno
Dissolves, mixes, cross fades..help wanted!!
Greetings. In any format, when I do a mix between pictures, the result is very poor. I see hondreds of squares just blending together (like a mini square wipe) as oppsed to a smooth mix. On ULEAD 3 it works fine but on ULEAD 7 the results are terrible! Any suggestions gratefully received.
-
alosada
In my experience, if you use Constant Bitrate (CBR) at 8000 kbps or higher as your Video data rate at the Share, Create Video File step, VideoStudio fails at properly re-rendering not only transitions, but also cut points in an mpg file. The result is two bad (heavily pixelated) frames in the portion following the transition or cut that make the video shake or seem frozen for a fraction of a second (80 milliseconds to be precise).
The effect is especially marked if any subject in the picture is moving or the camera was panning or zooming as these situations challenge the rendering engine's capabilties.
I have found three workarounds:
1. Using a constant bitrate (CBR) lower than 8000 kpbs;
2. Using variable bitrate (VBR) or
3. Unchecking the "Perform SmartRender" box
when creating the mpg file after editing in the timeline.
These solutions do not work on a previously saved file containing the buggy frames, so they have to be applied before saving any editing changes made to an mpg file.
Unless one must definitely use CBR at 8000 kbps or higher, workarounds 1 and 2 are to be preferred if the long waiting times involved in creating a video file with SmartRender disabled are to be avoided.
Hope this helps.
The effect is especially marked if any subject in the picture is moving or the camera was panning or zooming as these situations challenge the rendering engine's capabilties.
I have found three workarounds:
1. Using a constant bitrate (CBR) lower than 8000 kpbs;
2. Using variable bitrate (VBR) or
3. Unchecking the "Perform SmartRender" box
when creating the mpg file after editing in the timeline.
These solutions do not work on a previously saved file containing the buggy frames, so they have to be applied before saving any editing changes made to an mpg file.
Unless one must definitely use CBR at 8000 kbps or higher, workarounds 1 and 2 are to be preferred if the long waiting times involved in creating a video file with SmartRender disabled are to be avoided.
Hope this helps.