Ernie Santella
Forum Replies Created
-
I must be doing something wrong. OK, Browser, Effects Tab, Dissove Bin, I changed ALL the dissolves (Additive, Cross, etc) to :20.
But, when you Cntl-Click Add Transistion – Cross Dissolve, It puts in a :30.
This is insane!
-
No good. Yes, you can change the preset time in the EFX length window, and when you drag a dissolve into the transition, it takes that time, that’s great.
But, when you Cntl-Click ‘Add Transistion’ it’s always inserts a 30 frame diz. That’s the rate I want to change.
-
What they mean is, if you have a deck that can be controlled by TC, the M100 can go back and redigitize from your bins and timeline with accuracy from the source tapes.
The normal workflow ‘used’ to be (before large, cheap HD storage) was to digitize at a off-line or low resolution, like 60k. Then after you’ve finished your editing, you can then have the M100 re-digitize only the shots in your timeline at the highest resolution.
This saves an enormous amount of time and storage space as you could have hours of shots in all your bins, but only use 5 minutes of final shots in the timeline.
-
For what it’s worth, when my SCSI raid went south, I bought a FW400 drive with a fast Oxford 911 interface for a quick interm fix. It worked perfect up to 300KB on M100 8.2.2 (I don’t have uncompressed).
So, FW800 should be no problem also.
Other inexpensive drive systems to consider are SATA raids. Much faster than FW800 and cheap. Here’s an interesting article.
https://www.hdforindies.com/2004/12/review-of-firmtek-seritek-1se2-and
-
HHHHHAAAAAA!
The crowd goes wild!!!(It happened to me too)
-
Are you feeding Black Burst into the composite input of M100 while digitizing? If so, could the BB generator have gone bad?
-
Everybody should be rendering AE projects using the M100 codec? (Instant import).
That’s not the issue. It’s that video is digitized in Y,Yb,Yr and anything created on the computer is RGB. When you combine the two, that’s were you get this phase issue. It’s been posted before. There is no fix.
-
That has always been an issue with M100. It’s due to combining RGB and NTSC video. It happens to everyone. there is no fix for that. I hate it too.
The work around is to color correct the clip below it. Add about +4 to +6 to the tint of the video below, that usually fixes it. I know it’s a pain, but as they say… Whadayagonnado?
-
Is your setup removable? If you have a RAID like the FirmTek, it’s easy.
https://www.firmtek.com/seritek/seritek-1en2/
I have this setup. Now you can just have a set of two drives for each client. I have sets of 2x250gig Hitachi drives. At a cost of about $250 per set, it’s reasonable. And it works great. Pop ’em in and go. The best part is then you have unlimited drive space.
-
The problem was you shot with a US camera that runs at 60Hz and the lights flicker at the countries native 50 Hz power rate. I’ve edited footage that was shot like this and there isn’t a ‘plug-in’ to fix it. Same issue when DP’s shoot variable frame-rate with HMI lighting and no flicker-free ballasts.
A quick trick on shooting (next time) is to set your US camera’s shutter to 100 Hz (double the 50Hz) and it works pretty well.