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 :)

Clipfinder 2.2 beta 5 - switch between old and new color science

Hans-Georg Daun

Hans-Georg Daun

Well-known member
Joined
Apr 30, 2007
Messages
573
Reaction score
0
Points
0
Age
71
Website
www.hamingja.ch
I have just released Clipfinder 2.2 beta 5.
It is available from my server.

The main attraction this time is that I have found a way to allow you to instantly switch between old and new color science by clicking a checkbox in the preferences window.

You need to have at least REDAlert version 20 installed in order to be able to use the new color science.

Be sure to read the change notes in the "What's new in Clipfinder 2.2 ?" section of the integrated help pages (CMD-?).

Enjoy !

Hans
 
It's insane...

Users are not fast enough to follow the developer :)

Thanks so much Hans!

Antoine
 
WARNING !!!! BE CAREFUL WITH THE MOVE Directory function !!!

WARNING !!!! BE CAREFUL WITH THE MOVE Directory function !!!

BE CAREFUL WHEN YOU USE THE "Move directories to..." function !!!

IT MAY WIPE YOUR FILE, AND YOU WILL NOT RESTORE IT!


What happened?

I imported an XML from FCP (File menu)
I replaced MOV with R3D (Tools menu)
I moved directories to... (Tools menu)

I did it with a music video xml, to test the function, as I have been looking very much forward to it, because it allows to copy only footage, that is actually in the edit for conform and grading in Baselight. I talked with Hans about it some months back, and he finally implemented it I was eager to test it.

NOW HERE IS THE DANGER:

Clipfinder seems to be locked during the moving operation (it appears red in activity monitor). As I did not want to move everything, I aborted clipfinder violently....

... and lost the file, that was in the process of beeing moved. It was neither at destination, nor source.


Hans, please, while this is a very cool function, no program should delete the footage files. This is a thing, that one should fuckup personally via finder.

I strongly advise anyone to refrain of using it (beta4 and beta5) right now!!!


Hans, please if you could change "move" to "copy", and could allow a cancellation of the operation, that would be awesome. I may have wrongly used this command, but again a big warning to all, you may loose your data if your computer aborts for some reason during the move operation.


While the blame is on me, as I tested a beta version, while all my backups were 1200km away... It still is quite a shock. It is the first time I loose R3D footage!
I was too enthusiastic as I was looking forward to this function, and was not carefull enough.
However, I think this is quite severe. Again, I am not sure, why there is a "move" instead of a "copy", which seems to me as a too unsecure concept in the first place.


This is not a bashing on clipfinder, just a warning to others, who are not carefull as I was.
I hope that Hans will be able to fix that.

Otherwise, clipfinder is incredible - thank you big H. !!!!
 
Thanks for the feedback, Jonas.
The "move clip directories to..." function is not what you wanted, unfortunately.
It exists so that you can temporarily move clips to a single-level directory structure on the same disk as a preparation for log & transfer.
When used to move directories to another folder on the same disk, it is very fast and there is no danger of losing files.
I see your point, though.
With the next release, I'll make sure that it can only be used to to move between directories on the same disk.

Cheers,
Hans

P.S. I haven't forgotten about your request. There's just so much to do...
 
I understand now...

The moving works on other disks - if it is not interrupted, so it basically is the function I was wishing for, but a little suicidal.
With the Build 16 namings, every proper conform tool should find the files, though - Baselight certainly will, even when everything is in one directory.


If you can implement copy... which basically IS already there... :tongue_smilie::tongue_smilie::tongue_smilie:

Am I the only one, who might need that, and everyone is always copying everything for conform, to be sure?
 
I wonder if there is a permanent data archive (kind of DNA of the clip) that can be used to move back "the moved clips" to the original directory and so keep the original arborescence?

Hope you understand what I mean.

Thanks

Patrick
 
Jonas: if you don't mind having a flat structure (rather than the "day1", "day2", etc. structure I think you originally wanted) in the destination directory, then using copy & paste from Clipfinder to the destination directory will do what you want.

Patrick: Yes, you store the "original arborescence" in a Clipfinder document, then use "move clip directories to...". When you're done with L&T you use "move clip directories back from..." to move the directories back to where they came from.

Cheers,
Hans
 
I just did the "copy to conform" with the following workaround:

1. Import XML-FCP

2. Replace MOV with R3D (MOV badges change to R3D badges)

3. I created a folder "conform" - !!! ON THE SAME DRIVE !!!

4. Move Clip directories to ... (conform-folder)
Clipfinder indeed moved the xml-selected files to this folder within
seconds.
[clipfinder now shows a little "stopsign" next to the "R3D" badges - clips
do not show up in top window anymore]

5. Copy the files to another drive in finder. ... 40GB later

6. Move Clip directories back from ...
Clipfinder moves data back, and into the SAME file structure ... whew...

7. My editor Raphael in Paris just conformed, that he can FTP me the missing file from his backup ... whew..:lurk5:
 
Hans, just tried the way you said - sick.

It works!

NOW PLEASE TELL ME YOU GONNA MAKE A COOL
"COPY TO CONFORM" command .... :-D


Some remarks on the MOVE command:
I am not sure, if the move back from directory command should you even ask for a directory. If you say, this is only a temporary thing, and Clipfinder cannot do anything with the data anyway meanwhile ...

Why would someone move the directory again, when he is doing log&transfer?
I dont know, how clipfinder "knows" where the data were before (it must log it somehow, because it puts it back into the proper structure), but this might cause more headaches, no?

With Build16 and up, there are no issues with double filenames. So it is actually better from in my opinion, if the data is copied to conform into one directory only. (it might be an option later, though).

--> Now it seems, that this function works perfectly if you know exactly how to use it. I wish for a little safety here :-D


.... my file will be transfered through skype ... lets see how robust the network is ... :-D
 
COPY TO CONFORM
(copy only clips used in edit to folder for sending to post house etc.)
- import FCP XML (ALT-CMD-I)
- replace MOV with R3D
- select all (CMD-A)
- copy (CMD-C)
- create new folder in Finder (SHIFT-CMD-N) and open it (CMD-O)
- paste (CMD-V) .RDC directories into new folder

Cheers,
Hans
 
Splendid!

Hans-Georg Daun said:
I have just released Clipfinder 2.2 beta 5.
It is available from my server.

The main attraction this time is that I have found a way to allow you to instantly switch between old and new color science by clicking a checkbox in the preferences window.

You need to have at least REDAlert version 20 installed in order to be able to use the new color science.

Be sure to read the change notes in the "What's new in Clipfinder 2.2 ?" section of the integrated help pages (CMD-?).

Enjoy !

Hans
Click to expand...
 
I'm using the latest version with latest version of RA

We shot B17

Rendering from CF I'm getting red X's under the info and the renders are failing.

Anyone else encoutering this?

Last batch to SD (1k) worked. to 2k its a fail :-/

following in console over and over again ..

Error in Console is REDline reported the following
"AddMediaSample2(soundMedia) failed (-1309)"


Cheers

Si
 
Simon,

I have tried to reproduce this, but it works ok here.

Do you have "use old color science" checked ?
What codec are you rendering to ?
Does it still work with 1K ?

Cheers,
Hans
 
Follow up to Simon's problem:
Errors are due to known problems with REDline and Quicktime rendering files larger than 2GB to a network volume. It has nothing to do with either the Blackmagic codec or Clipfinder (REDrushes has the same problem, it just doesn't report it).

Cheers,
Hans
 
Thanks Hans. Quick update.

Just rendered DPX across to the server.

Slight update. All the DPX's rendered but in Clipfinder one of the shots still gave a red X under info and the render bar in the Render window isn't completed yet all shot are done. Still claims there are frames to render.

I have RSX in/out points chked.

Cheers

Si
 
Thanks Hans... improving our work flow
 
You must log in or register to reply here.
Back
Top