[Chris Hall]

If it’s a complicated sequence then 4GB RAM might not be enough.

You say it works fine on other sequences. What are the differences? Do you have more effects, layer of video or large stills etc? What is the video codec of your source material as some need more processing than others. If you create a new sequence in the project and just add one clip, does that play back OK?

Sometimes Premiere can be a bit sticky when scrubbing through but it shouldn’t be as bad as you’re experiencing.

[Chris Hall]

I’m not totally sure I understand your problem.

Is your timeline set to 1080 x 1920, and then you export to a 1280 x 720 file?

Is your problem that on your final export the timelapse doesn’t fill the screen leaving black at the sides?

It looks like your timelapse has a different aspect ratio to the timeline or final export, so it will not fill the screen fully. The only option is to increase the size of the timlapse clips once in the timeline so it fills the screen. You will lose a bit either at the top or bottom of the screen or both, but once you have increased the size so that you don’t have black at the sides, you can move each clip up or down to get a good framing. Then you can export.

[Chris Hall]

As well as a ‘Video Usage’ column there is also an ‘Audio Usage’ column. It looks like it is just the audio that has been deleted from the timeline so I suspect that one copy of the clip has been used to edit in the video and another to edit in the audio. So the clip that has it’s audio used in the timeline wont have any video usage, but it will show up in the audio usage column.

How did you come to have more than one copy of a clip in the bin?

[Chris Hall]

I’m getting this too. Very annoying when I open a bin in a new tab and have to close 15 extra tabs that are created!

Only started happening with cc2015.3. Is anyone using cc2015.3 and not having this issue? Could it be related to the operating system? I’m using mac os 10.10.5 like OP.

Seems strange that this obvious bug didn’t get picked up.

Chris
cc2015.3, Mac Pro OS 10.10.5

[Chris Hall]

Possible solution!

So I had the same problem with the Decklink SDI card causing my bluetooth mouse to grind to a halt. Whenever I started to use FCP or Premiere the mouse would stutter and not be very responsive.

Then I tried to connect a reference video input to the card and now the mouse works fine. I just used a composite video signal from a tape deck into the reference in on the card. On the Blackmagic control panel at the bottom it will say if it has a reference signal.

Strangely I found that the mouse still works perfectly even with the reference disconnected and has done for a few days.

So I’m not sure if this is all just co-incidence but it was the only thing I did and now it works. It would be interesting to see if it works on another system with this problem.

Chris

[Chris Hall]

Hi,

It looks blocky on a broadcast monitor. I’m using a slight border applied using boris which makes it worse.

I was using boris for years and thinking the results were OK but this improves it no end. Try it!

[Chris Hall]

Thanks for your responses,

So, are you saying that if I record 720/25pn then when I import from the P2 card to FCP it would create a 25fps (but slowmo) clip automatically. If so I will let the camera guy know this.

The workaround I have found is simply to apply a slowmo to the clip and work in a 50fps timeline. This looks ok but I imagine not as good as a proper frame for frame slomo.

Chris

[Chris Hall]

Hi,

Just wondering if you found a way to solve this as I’m having the same problem.

Many Thanks,

Chris

[Chris Hall]

Hi,

If you use a ‘mask shape’ filter before the basic 3D filter on the clip and use it to crop the image slightly by setting it to rectangle and using settings of 98 or 99 in the horizontal and vertical sliders, then it gets rid of the jagged edges. (you could then try adding a mask feather to smooth edges a bit more if necessary).

Chris

[Chris Hall]

Hi Alex,

Thanks for your help. However I tried to place a DV clip in a 10bit timeline and generally it looks ok but on bright reds I find that I get slight horizontal lines appearing in the red part of the screen. I only see it when looking at a component monitor, if viewed in composite it looks ok.

It seems like the dv to SDI or DV to component conversion is not that good. Are you working in PAL or NTSC?

If you have time maybe you could try looking at video with bright red areas and view the component out of either the Digi deck you are feeding or the kona component output.

That is, if I take the DVCam video with red in it and dub directly to Digibeta then look at the component out in a component monitor it looks fine. If I digitize in DV via firewire and play from either a DV timeline or 10bit rendered timeline and output SDI to digi and look at the same output from the deck it has these horizontal lines in red colours. If I digitise component from the DVCam deck to uncompressed the picture looks fine.

I would love to get this working. Maybe its a PAL thing.

Thanks,

Chris