David J
Forum Replies Created
-
It also affects me – I had to reset my cookie yesterday when the forum refused a posting. Had lots of trouble like this a little while ago which seemed to have gone away till now.
I went through the ‘reset cookie’ link which seems to have fixed it this time.
-
Click in the source monitor to make it active, then JKL applies there.
I guess you can also tab between windows and watch the blue topbar if the mouse is infra dig.
-
That’s two of you with the problem then. As I said, JKL works in both source and program windows on my system.
-
Given that the problem here is to eliminate a noisy channel from a stereo pair generated from a twin feed into the camera, the reduction to mono is a side issue. What is required, from the original question, is to get the ‘good’ channel across both channels and eliminate the parallel noisy channel. Hence the suggestion to use Fill effects rather than sub mixes etc.
-
You can apply the ‘Fill Left” or “Fill Right” audio effect to populate both channels with the audio from one of the original pair. This makes it effectively mono on a stereo audio track.
You can use keyframes to turn this effect on and off within a clip using the ‘bypass’ parameter.
-
You don’t give information about your clips, version of Premiere, or hardware/drivers on which to base a detailed answer, however…
Small size changes have been noted with some capture systems, mostly with pre-Pro versions of Premiere, when a clip is rendered. Unchanged sections of clips are not affected, so the change to/from a rendered section can cause a slight ‘jump’.
The ‘trick’ to work around this issue, which is generally attributed to the capture card and associated CODECs rather than Premiere, is to apply a ‘do nothing’ effect to the whole clip to mask the size change.
‘Do nothing’ effects include Color Balance (HSL) with no change from neutral.
The cost is that more of the timeline may need rendering, but the benefit is to ‘fix’ the problem you may be describing.
-
Works for me OK.
-
The original version of Scenalyzer split clips that already had been captured using optical scene detection. It is still available as a free download from scenalyzer.com. Might be worth a try for you.
BTW, the Pinnacle DV500 included a scene-splitter filter with the v4 drivers, but this is not portable from 6.x to PPro. So the technology is well understood, but apparently in the wrong camp.
-
Scenalyzer Live only works with DV inputs, but if the source is analogue via a converter/passthrough then lack of date/time for scene detect can be overcome by switching to optical scene detection instead.
Try before buy (watermarked captures) from http://www.scenalyzer.com. Get the v4 beta, which is very stable and has many more useful features than the original release.
-
No. Premiere does not give variable speed, only fixed speed changes per clip or sequence. After Effects Time Remap gives the required flexibility, but so far this has not been ported to Premiere.
There used to be a Panopticum Tools plug-in for older Premiere versions that gave variable speed control, but as far as I am aware that has not been updated for PPro.
I’m not aware of any PPro plug-ins for variable speed, although there are some for AE.