[Ken Pugh]

Actually, here’s another….

Mark in, use make edit command, move forward 4 frames, use make edit command, delete the cut section you have made, how many frames have gone…. 4!

So how can it be logical to the simple mind of an editor (especially one that came from film) that when you move forward four frames from an in point, the technique from my previous email (mark in and out) deletes 5 frames while this technique deletes 4?

I know the argument goes that the make edit command is cutting on an in point in both cases, but what are the rules that says that the cursor cuts on a different frame depending on whether it thinks it’s an in point or an out point? Certainly my film splicer did not make such presumptions under my firm and unwielding grip, try as it might….

And come to think of it I’m sure my old and trusty Media 100 system did not work this way, maybe not all NLE’s have this ‘quirk’.

Anyway, rant mode off. I’m on assignment sitting in a hotel in Dakar with not much else to do – posting when I should be listening to Mbalax at some groovy nightclub. Sad but true. But I do enjoy this fine forum.

Best,

Ken.

[Ken Pugh]

No no no – don’t believe the hype – its not you it’s FCP – written by a programmer not an editor.

My case – mark an in point – move forward four frames – mark an out point – select the region with the alt-A command an delete. How many frames have gone? Five.

I rest my case.

Ken. 🙂

[Ken Pugh]

Thanks Don,

No, I don’t have a f/w card with this computer (had one for my old G4), however still get the problem with the deck disconnected. Next time I get a dv project I’ll try editing without the Kona card – see if this helps. I run activity monitor now most of the time, and I notice when the computer starts to slow down, one of the processors activity bar fills up – even after I’ve quit all programmes it still stays mainly blue. Logging in and out doesn’t free it up either, only rebooting.

Best,

Ken.

[Ken Pugh]

Occasionally I’ve had a deck on the f/w 400 – but assumed this was a different bus to the 800.

Otherwise nothing on the 800 chain except a couple of drives.

I’ve also had this problem when running off the internal SATA drives (I have 4 x 500). But I keep media to the non-startup.

Ken.

[Ken Pugh]

The render time is creeping up again – 5 hours now – so I’ll take your advice prior to the next reboot and run tech tools. Shame I can’t play out of the Kona LHe straight back to the hard disc – much quicker! Maybe if I got another Kona card for my old G4 system I could do that – cheaper than a DigiBeta and then I have realtime SDI transcoding….

Thanks,

Ken.

DVCAM, HDV, BetaSP and DVCPRO DECKS

[Ken Pugh]

I’ve dropped the DVCPRO HD 1080i clip into a FCP uncompressed 10 bit anamorphic timeline. I got a green bar so hit render and initially got an render estimate for about 14 hours. Rebooted the computer and this has come down to 2 hours. I’m finding if I work with multiple codecs the computer quickly starts to get clogged up somehow and everything slows down – until I reboot. Is this normal when working with FCP and HD?

Cheers,

Ken.

[Ken Pugh]

Fantastic, I’ll do that.

Thanks,

Ken.

[Ken Pugh]

Typical – just posted then finally worked it out – select all the keyframes then then move by dragging the bounding box. Apologies. Ken.

[Ken Pugh]

Removed AJA IO drivers and trashed the FCP prefs – still getting uncompresed 8 bit when selecting AJA KONA LH- PAL 8 bit to DV

Running out of ideas here…. emailed AJA help desk, but no response yet.

Ken.

[Ken Pugh]

Yes, that’s the one.

I have discovered I also cannot digitise to DVCPRO 50 – the only codec that works for me in SD is the uncompressed – the HD codecs seem fine. I’m now wondering if there is a conflict with the AJA IO drivers I have – although the manual states both systems (KONA LHe and IO LA) can sit side by side.

Will try removing IO drivers next,

Ken.