Gavin Turnbull
Forum Replies Created
-
Yes! Thanks Michael,
4000 max pixel height or width… please add to my list above… and that shoudl just about cover it.
Cheers,
Gavin -
This is an old conversation … I am one of those rare stick in the mud FCP7 users, never managed to make the bridge to FCX.
FCP7 is a powerful tool but infuriating at times, and this is one of the most annoying problems, and within this issue being sent to the render manager even when it is empty drives me nuts! I have looked of answers many times and like you Phil, slowly built up a list of culprits to work through – “full cache, preferences, mismatched frame rates, RGB colour space on stills etc etc etc”
To add, make sure jpegs are 72dpi, make sure all the video media matches the project time line, but also…
– I have discovered it’s important to have the Scratch disk and raw material on different drives, making sure the drive the Scratch is on has loads of space. I create a new Scratch Disk folder for each project, I don’t have a dedicated drive that houses all my projects, I prefer to manually manage projects and media as much as possible (I guess that comes from 28 years! of using Macs, and back the OS9 days when under the hood mechanics was expected).
– Today’s search was because I thought I had come across an as yet undiscovered issue … but after emptying trash the render working, I realised the drive my Scratch disk was on was no where as empty as I first thought!
So… I am now thinking I have cracked it. Two core issues, watch those Jpegs and keep Scratch and Media apart.
Hope this avoids hair pulling for anyone else! It’s only taken me 10 + years!
Best, Gavin
-
Hi All,
This is indeed an annoying issue, I have posted about this before, but not sure where, but here is my experience again – with additional notes.
The common or regular issue is when there are still images on the time line, I use PNG as it handles transparency best, Jpeg and possibly TIFF can be used. The main thing to be aware of is make sure it’s 72dpi and as close to the final size you require on the time line, keep file sizes to a minimum.
I have found deleting render files, in particular ‘Constant Frames’ out of your scratch folder helps, I’ve done this in conjunction with restarting FCP7 as I suspect it will also clear out any bugs in the cache. You could try just deleting the ‘Constant Frames’ without a reboot of FCP7?
In general, keep your project small, work on 1 project/timeline at once, keep files small, and use 72dpi images. This is not necessarily part of this issue but make sure all you video files match in codec and also match your timeline settings.
Hope this helps,
Gavin (https://www.gtmp.tv) -
Hi All,
So, I have another issue that caused this ‘error’ while I was attempting to render a very short sequence of iPhone clips and stills.
I’d imported some iPhone footage that I’d converted to Pro Res LT. Only after I’d cut it I’d forgotten it was 29.97fps!!
I did check the stills were RGB and they were, so they weren’t the problem.
So re-transcoded the clips to Pro Res LT 25fps synced the clips up to the previous clips… forgetting that the timeline was still 29.97 fps…
So, after a few goes and eventually twigging my mistake I created a new time line in 25fps, copied-cut-pasted the clips from the 29.97fps into the 25fps timeline… solved! I rendered without issue.
As with other FCP7 complaints, it’s often down to not having the correct or mixed codecs in your project, preparation preparation preparation !
Hope that’s useful for someone.
Best,
Gavin -
Andy,
Many thanks, my problem is fixed.
This is an issue that plagues us all at one time or another and FCP does nothing to assist in offering an issue or solution!! Time passes enough to make the last solution found has long been forgotten.
Anyway, I wanted to add my experience in case it helps others.
I’d say, for me the main factor in creating this issue is using stills in a format that gives the RAM way too much work. Never mind how much space you have created in the settings. This occasion was three JPEGS I had used Photoshop to res up in DPI/Pixels to enlarge, but having read your pointers it made me think I need to res up using pixel ratio and keep the image to 72 DPI/Pixels … bang, there you go, fixed!! The time line now renders with no issue!
In the bigger picture, in the old days when I was learning, I often had this issue because I had a mix of media formats incompatible to the project. Best tip I can offer to all is make sure all you media is prepared and matching the project time line, ProRes for a ProRes time line e.g. PNG’s a good, make sure stills are RGB 72dpi, Audio files WAVE or AIFF… etc etc. That’s make your edit trouble free and whatever size your ram or machine, however many cuts or how large the project is, you should have a smooth ride.
NB – I have seen it suggested it might be too many plug ins, I’m pretty sure that’s not the issue.
Hope that’s useful.
Best, Gavin
https://www.gtmp.tv -
I may turn religious, but only for a moment, god bless you Bill.
It’s no wonder people are beginning to jump the FCP ship! With bugs like that. Your tip has saved me 8 – 12 hours work! If you’re in Edinburgh I’ll buy you a pint!
The export / import of project XML works folks. I can confirm it.
Cheers.
Gavin
https://www.gtmp.tv -
I have stumbled on this problem recently, it’s because we’re trying to take a freeze of a clip that have had it’s ‘dimensions’ altered. God knows why it can’t just freeze exactly what’s on the canvas rather than sourcing from the original clip?
Anyway, with this in mind here’s my fix. place pay head on frame you want on the time line. Select match frame to bring the source clip up in viewer. Take freeze frame from there instead.
Best, gavin@gtmp.tv