Jason Porthouse
Forum Replies Created
-
Ahhh, OK, seems like I have been barking up the wrong tree… I think Cinema Tools is for 24p to PAL rather than 29.97… correct? It seems like Nattress is the way to go….
Jason
-
I have to agree regarding the text and button size. It’s long been a bugbear of mine. My Silver had a customizable UI and BIG buttons, which I always found productive ’cause you didn’t have to be hyper-accurate to hit them.
The 30″ screens are even worse… text being that much smaller (seemingly). I think Apple really need to fix this one soon – I hope someone is listening, but I suspect it’s what happens when the geeks take over the asylum.
As to RSI and Carpal Tunnel, I second the Wacom, and I also find that variety is the spice of life… have a tablet, a mouse, and the keyboard and use them all. A good chair is a must too, and don;t skimp on it – some ‘ergo’ chairs are not ergonomic at all, they just look it. I’ve got a Herman Miller Aeron, cost me
-
Stick a camera in a room full of editors… and start them talking about aspect ratios. Eventually someone’s head will explode. Job done.
Jason
-
Stick a camera in a room full of editors… and start them talking about aspect ratios. Eventually someone’s head will explode. Job done.
Jason
-
Thanks Brett, i think this may well be it. I’ve got a lot (subbing 15 minutes worth of talking) and moving to a new timeline cured it… so i think it is a limit. Never come across it before though!
Ahh, you live and learn.
Jason
-
Yes, I agree and normally I would have… I did a test and all was well, but when the client called and said ‘We need to monitor audio whilst logging’, because of the nature of their setup I suggested turning preview audio on… not something that has given me a problem before, but thats been with the Kona ingest rather than FW. I think it must put some kind of overhead that chokes the firewire bus – I don’t think it would happen with a seperate FW PCI card. One for the learning bank , I think!
Jason
-
Update – it seems that the default setting for log & capture was audio preview on, and FCP didn’t like this one bit. I’m guessing its a firewire bandwidth issue…
Much of the suspect footage had dropped frames, but was barely noticeable due to the nature of the footage – talking heads with little movement. Recapturing clips with preview turned off seems to have cured the problem…
Jason
-
One thing… it is FCP 5.12 not 4.5 as stated, OS 10.4.8 with 5.5 gigs RAM.
Any thoughts?
Jason
-
Ahhh, someone else who has noticed this.
What I think he’s referring to is the fact that if you place a dissolve on a clip transition, and the incoming clip starts at the first frame of that clip’s media, the dissolve will be one frame long. FCP won’t then let you modify the length of that dissolve, even though it starts at the cut rather than centered or ending. I have to slip the clip in order to give it some ‘preroll’ before applying the transition. I’ve noticed this a few times now.
Anyone else?
Jason
-
David, you’re not mad. I’ve had odd things happen with audio files that I have no explanation for… I work with many audio files imported from CD as AIFFs. 99 times out of 100 fine, but then I’ll get a file that, whilst appearing to be fine on the timeline (one solid, uninterrupted file with correct waveform)has a cut in it… as if I’ve made an edit by mistake. The fix for me is usually to re-lay the file. Shortening then stretching the file makes no difference (I thought it might ‘refresh’ the timeline)but I haven’t tried re-linking the media…
I have had one occurence of this on a footage file (as opposed to an imported music file) and I’m leaning towards the 44/48 mismatch theory… It seems that whilst FCP should be able to cope with the sample-rate conversion it sometimes gets its knickers in a twist. Never had it happen in 4.x, only in 5…
Jason