Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

LOG and TRANSFER duration issue

B

blakerblaker211

Member
Joined
Sep 10, 2008
Messages
11
Reaction score
0
Points
0
I am transcoding to PRORESS LT for my offline edit on a feature. For some reason some of my clips are not the full duration of the original R3d file making me have to hand check dozens of ingested clips and in turn I am having to reingest clips over again. Does anyone know of a fix. Or at least is this problem common in the workflow? I am trying not to queu as many clips seeing if that will work. ANY ideas out there?
 
Ask the Digital Loader if any of the clips had Corruption or Dropped Frames.

Also try to open Redrushes and encode that clip using any Compression as a test to see when the Frame Count Stops encoding on a particular clip. Check that Frame Number in RedAlert and Flag it for Corruption if RedAlert Crashes or shows you green and purple Solarization.
 
I am not using the Digital Loader. Is that a program I should download in order to figure this problem out?
 
Alex ment the edit assist who did the log and transfer ingestion. Digital Loader is not a piece of software.

If you think you do have dropped frames, see if you still have access to the camera source and try R3D Data Manager (software) which will perform a "Checksum" operation, insuring that the media you copied over didn't loose any info in the process.

BTW... NEVER set in's and out's in Log and Transfer when working with Red footage.
 
Have had the exact same issue once or twice. Just had to check all clips and re-ingest which was a pain. Re-ingest worked on same clips first time, so not sure what caused problem.
 
I am not setting in and out markers. Some clips are not transcoding to the full duration causing me to go back and reingest. Its causing me a lot of work. I am the assistant editor on this feature. i am organizing 6TB of footage and its a huge pain to have to reingest. I wil talk to the producer about purchasing the software.
THANKYOU by the way for responding in the first place!!
 
First of all, don't use FCP L&T, FCP is not multi-processor aware, whereas RedRushes and (I think) Clipfinder are, so FCP doesn't use all the processor cores of your MacPro - hopefully you're not trying to transcode on a laptop.

The partial clip problem is probably coming from using the computer for other stuff/having other software running while you're transcoding; general rule is to not even exhale in the direction of the machine while it's transcoding.
 
Thanks Joe that sounds right..
Unfortunately I am already pretty deep in the transcoding process to switch to RED RUSHES...I am on an quad core intel xeon with 8gigs of ram....but I was kicking out dailies yesterday through compressor when I noticed i Had the biggest problem with short clips...thanks for your tip...any other ideas
 
it could be a problem with the Corrupt Clips. Definitely test the problem clips in RedRushes.

Unfortunately R3d data manager won't help if you no longer have access to the Original Magazines from the Camera. You will be able to tell if the data from one drive to the next is an identical copy or not. But if you are seeing these issues with the Master Drives then that software wont help at this point. Its a great software and I recommend it should be used to check copies against the original while on Set and unloading the Magazines. Thats the most critical part... On Set, Post also is critical when making many duplicates or Backups/
 
If you use red rushes will the REEL name still be the RDM folder so when I reconform later it will still be able to batch capture the offline sequence
 
leave it alone

leave it alone

joe hedge said:
The partial clip problem is probably coming from using the computer for other stuff/having other software running while you're transcoding; general rule is to not even exhale in the direction of the machine while it's transcoding.
Click to expand...

I second this. You should leave the log and transfer window in the foreground and avoid using final cut or other apps. And by the way this happens with other media, not only .r3d files. It's an annoying bug that isn't fixed as of version 7.0.1 of final cut. So much for background tasks...
 
Alex Carr said:
it could be a problem with the Corrupt Clips. Definitely test the problem clips in RedRushes.
...
Click to expand...

I think it's probably not corrupt clips as they re-ingest OK.
 
RE-TRANSCODE IN SMALLER CARD BATCHES. I had the same issue using the L&T Tool in FCP. I noticed if I did individual clips over or even just one card at a time tthe results were fine. FOr whatever reason the bug occured when I had 2 or more cards in a batch at a time...
 
I've also come across this part clips issue. Also on an 8-core with 12 G RAM. Of course I was surfing in the background and doing some disk management on other volumes attached. Maybe that's why.

What was also frustrating is that when I did a L & T again, I got the same clip, now full but with a ' 2' or ' 3' suffix. Some got a bit more duration second time around, but not still full.

So I too, just nuked everything and exported again using Clipfinder.
 
Last edited:
Brandon Kraemer said:
BTW... NEVER set in's and out's in Log and Transfer when working with Red footage.
Click to expand...

Brandon can you explain why this is? When transcoding small pieces of long interviews in and out points can save a ton of hard drive space.
 
You must log in or register to reply here.
Back
Top