Safe to trim clips with no in and out point Redcine?

[AndreasOberg]

Hiya

We need to trim most of our clips.
Is it safe to trim a clip that had no in or out point?
The reason is I want to batch export all clips also those that do not need trimming

Fast answer would be appreciated
From what I can see they are identical which is good.

 

[Bob Gundu]

There is no degradation in trimming. You can also remove trim marks to restore original lengths too.

 

[AndreasOberg]

Hiya Bob!
I dont think you can restore the file once its trimmed since it cuts out data.
I found some strange cases while testing. Sometimes it doesnt trim at all. Also had a few clips where the trimmed file ended up being just a few frames. Testing some more. If this works it will be a good workflow. Anyone having issues?

 

[Bob Gundu]

Sorry, I meant the original clip can be reset to clear the in out points. And yes, I have also encountered incorrect trimmed files before. To be honest I usually avoid doing that. Perhaps DaVinci has more predictable results.

 

[AndreasOberg]

Hiya. Yes I thought you meant that.
I notice it collapses the files into fewer files.
I found a workflow that seems pretty safe. Will write what I found

 

[Björn Benckert]

easy test.
1. put all your trimmed files in a timline and save xml.
2. conform from your folder with the trimmed clips using the same xml.

scrub trough, if all is good then I would say its safe to ditch the original.

 

[AndreasOberg]

Good idea Björn, will try. Do you mean make the timeline in Redcine?

What I did to verify was:
1) Count the duration of the clip and compare the trimmed with the non trimmed to make sure they matched up. So I basically checked manually the 100 clips
2) Import to FCPX to see that they all start and then do the same in Davinci. Only thing was that FCPX seemed to mess up the date, it used the date when the trimmed was created, but I think I can make it use the internal date from the red file.

I had a few problems.
1. One of the files that had no in and out point did not get exported. It just wasn't there. Even when I tried again. So I ended up copying it manually
2. If I would reexport the result would usually be horribly wrong. If the file was supposed to be 10sec it would often end up being 0.5 sec for no clear reason. However if I deleted all the clips in a bin and then draged them from the media browser to the bins and THEn reexpored it seemed to work.

Good think was I managed to pretty quickly cut down the file size from 350GB to 260GB.

Our 2x 3.8TB SSD enterprise drives are working very well. It has been a blessing to offload data to them. Now I'm moiving 1 weeks shot to slower 2.5 drives and it of course takes forever. Maybe the best way would be to get a 10TB 3.5 drive instead of the 2 2.5 disks. Should be 3-4x faster and not that much more heavy.

Andreas

 

[Björn Benckert]

Good idea Björn, will try. Do you mean make the timeline in Redcine?

What I did to verify was:
1) Count the duration of the clip and compare the trimmed with the non trimmed to make sure they matched up. So I basically checked manually the 100 clips
2) Import to FCPX to see that they all start and then do the same in Davinci. Only thing was that FCPX seemed to mess up the date, it used the date when the trimmed was created, but I think I can make it use the internal date from the red file.

I had a few problems.
1. One of the files that had no in and out point did not get exported. It just wasn't there. Even when I tried again. So I ended up copying it manually
2. If I would reexport the result would usually be horribly wrong. If the file was supposed to be 10sec it would often end up being 0.5 sec for no clear reason. However if I deleted all the clips in a bin and then draged them from the media browser to the bins and THEn reexpored it seemed to work.

Good think was I managed to pretty quickly cut down the file size from 350GB to 260GB.

Our 2x 3.8TB SSD enterprise drives are working very well. It has been a blessing to offload data to them. Now I'm moiving 1 weeks shot to slower 2.5 drives and it of course takes forever. Maybe the best way would be to get a 10TB 3.5 drive instead of the 2 2.5 disks. Should be 3-4x faster and not that much more heavy.

Andreas

RCXP works but normally we use resolve and do a media managing thing where we export all selects as r3d trims with some set number of frames as handles. Then we relink to those and if the edit is still good the trimming was ok. I came across r3d clips that resolve simply will not trim. When that happens I simply narrow it down so I know what clip did not fly and just copy over that r3d as a whole. Not sure why that happens but normally it´s less than one clip out of 400 or such so no biggie.

I like the r3d trim as it´s a really nice way to get the material narrowed down and still stay raw. Usually when we got the the trims done we export prores versions of the clips into the same source folders. So every r3d folder has a nice setup of proxies in different weight and then if needed we dump dpx files in there as well. Simply it makes the search for a specific clip very simple. In resolve you can then just import the whole file structure with subfolders and then delete out what you dont want by sorting them of file type. An easy way to jump between prores / r3d and dpx source.

 

[AndreasOberg]

That is really interesting Björn. I also love the possibility with trim. I have been trying to film eagles flying with a 1200mm and I can tell you that a big chunk of the clip is blurry blurr and then a few seconds of hopefully sharp eagle so trimming is a God sent.
I'm interested in your folder structure so if I understand correctly it looks like this:

A018_C001_042222.RDC
A...R3D (raw file)
A.... (pro res)
(A... (dpx)
The proress folders, is this only for editing? So they are 2k then, or?
And dpx I guess is for maximum quality or when you need to move between different post programs?

Does it work well to have them all in the same folder. I'm used to organizing files like this
- Red RAw
- Proxies
- DPX
This is how we organize in games, but I like the way you do because in some ways, because if I need to move clip 1 I move that folder and everything follows.

/Andreas

 

[Marc Wielage]

Sorry, I meant the original clip can be reset to clear the in out points. And yes, I have also encountered incorrect trimmed files before. To be honest I usually avoid doing that. Perhaps DaVinci has more predictable results.

Resolve has had issues in the past with trimming R3D's that span across multiple clips. I don't know if this problem has been solved recently or not. Generally, when I media manage, I take along the entire clip regardless of how much wound up in the final, just in case the editor needs to make changes and some clips wind up slipping in the final edit.

 

[Björn Benckert]

Resolve has had issues in the past with trimming R3D's that span across multiple clips. I don't know if this problem has been solved recently or not. Generally, when I media manage, I take along the entire clip regardless of how much wound up in the final, just in case the editor needs to make changes and some clips wind up slipping in the final edit.

Still there I think.
But I guess with the new formating options of the ssds there is no real need for r3d splits any more.