[Anthony Popolo]

Thanks. That’s good to know.
Unfortunately, for this project I’m putting a lot on each dvd, so my bitrate is below 3. I’ve been using VBR and the finished quality is better than I would have expected. At a bitrate that low, do you think CBR would do the job, or do you think I should stay VBR?
A

[Anthony Popolo]

Oops. My bad. I just realized the “frame” I was using was in fact from a previous 1080 project (not the current 720), so yes, there was downscaling occurring (albeit not a whole lot, but math is math) for each frame, just as you pointed out.
Thanks for highlighting that.
A

[Anthony Popolo]

Thanks,
The bug is actual size for the video, and it was created in pshop as an alpha layer on a canvas the same size as the video (720×1280). In other words I have a transparent pshop document 720×1280 with the small logo located in the corner. So there was no scaling required, but there is “transparency” of the pshop file over the rest of the frame. Is all the photoshop “transparency” still adding to the render time?

Thanks
Anthony

[Anthony Popolo]

Thanks,
I understand each frame had to be rendered, but it makes no sense to me why adding one layer of video quadrupled the render time. At worse case I would think double maybe.
My previously rendered footage (without the logo) was rendered and compressed to SD mpeg2 so I didn’t want to import compressed footage as my base video for the logo version.
-A

[Anthony Popolo]

I think the start up procedure on the 700 is a little different than the others as well. Here’s the procedure for the 700 (I’ve done it and it works fine)…

Set the camera to 720 60p HQ

Turn the camera off

While holding down the display button turn the camera on

Press the Menu button while pressing the Focus Assist button

Advanced Menu will be displayed

Select the Advanced Function Menu and then push the Set button

Select Pixel Compensation and push the Set button

Change the parameter to Execute, then push the Set button

Pixel Compen Executing will appear

Pixel Compen End will appear

Reboot operation is required to reflect the pixel compensation data

[Anthony Popolo]

Hi,
I have the 700 which is a different procedure than the 110.

Try this thread…its for the 100 which may be the same for the 110.https://forums.creativecow.net/thread/36/815989#816366

or do a search for “dead pixels”. There are a bunch of threads

[Anthony Popolo]

So I’m thinking I only have two options for workaround:

1. Export the sequential clips from the timeline to create a new clip (time and drive space hog, kinda defeating the purpose of the SDHC capture)

or

2. Multi-clip edit with the clips separately and then use the individual clips to bridge the gaps at the seams on the multiclip. A little messy, but probably what I’ll do.

The JVC camera came with software called “media manager”, but I can’t run it since it needs the intel processor, but I’m wondering if it has a utility to merge the clips before importing into FCP.

Anyway, looks like a JVC to FCP on a PowerPC detail fell through the cracks!
I’ll take it up with JVC…

thanks
Anthony

[Anthony Popolo]

I only tried briefly to multiclip a nest. Maybe FCP can multiclip nests. I will investigate it further. Thanks!

[Anthony Popolo]

Yes, thanks. I found out how to do it after emailing a JVC engineer. I thought I only had one pixel dead, but when I ran that fix, it looked like 3 of them lit up during the fix. Nice to know that menu item!
Thanks
Anthony

[Anthony Popolo]

I see.
Yes, in FCP, i can make a multiclip with different camera angles, but I run into trouble near the end of the clip where one camera’s clip ends before the other (because of the limited file size)… Then the next clip has a staggered in point as well. I tried to “nest” the smaller clips together (i think similar to what you are talking about in AE), but when I nest the clips together, I can’t make a multiclip with a nested clip in FCP (FCP can’t apply “clip” properties to “nested sequences”.
But thanks for your help!
Anthony.