Welcome to our community

Be a part of something great, join today!

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

Monkey Extract 2.0 - Rename Red Reels

Nigel Stanford

REDuser Sponsor
Joined
Feb 26, 2008
Messages
347
Reaction score
0
Points
0
Location
wellington / new york
Website
www.rubbermonkeysoftware.com
Hi Guys, Monkey Extract 2.0 is now live and available for download here.

Lots of new features... starting at the top:

Rename Reels
You can now rename reels or clips, changing the camera letter and / or reel number. For example, if you have two reels called A001, you can rename one of them to B001. The rename process alters all metadata and recreates the proxy files.

Thumbnail view of all footage
Select a directory of reels or clips, and the use the thumbnail view to select footage to copy or render.

Copy R3D Footage - from a timeline or thumbnails
For situations where the cut is finished, you can copy all the R3D files used to a new location. This is useful if you want to put all the used R3D files on a drive to send to a post house, and don't want to send everything that was shot. Or if you want to keep all the R3D files prior to rendering and move the rest off to an archive disc.

Render footage without an EDL
Monkey Extract previously required an EDL to render footage. Now you can browse to a directory and render out an entire reel, or just a single shot.

DPX metadata fixing tool
Select folders of DPX files and update the log / lin, reel, and FPS data.

Other improvements:
- speed enhancements
- support for new DNxHD codecs
- support for latest Redline versions
- set Log / Lin, black and white points for DPX renders
- custom folder and filenames for rendered DPX and Quicktimes
- fix for RED 16 EDL issues
- fix for RSX and color settings issues

Check it out and feel free to post your feedback :) Thanks!

Main page - the new tools...

 
Does the selection of the DPX file naming propagate to the source metadata in the header of the DPX file? Thanks for adding the rest of the DNxHD codecs!

I tried rendering a directory of R3D files to DNxHD36 with burn-ins - but it kept requesting an EDL... am I doing something wrong?

Michael
 
Does the selection of the DPX file naming propagate to the source metadata in the header of the DPX file? Thanks for adding the rest of the DNxHD codecs!

I tried rendering a directory of R3D files to DNxHD36 with burn-ins - but it kept requesting an EDL... am I doing something wrong?

Michael

Hi Michael,

You can set the DPX reel name metadata to match the render folder. The common options would be to set the reel name to A001 or A001C001.

I'll ask Craig about the other issue. I assume you're setting the radio on the main render page to 'Render all footage from the source directory'?
 
Yes, I am selecting the "render all footage" from the source directory.

Michael
 
Problem solved! Thanks for the always quick response to user's needs.

Michael
 
Have you provided a method to manually override the matching algorithm in the case of clips with identical reels sharing timecode (and no, I don't want to rename shots - this happens for us when the TC jam sync is dropped and the camera clock is a few minutes out from the TC source - you end up with two clips on the same reel with the same TC range sometimes)
 
Have you provided a method to manually override the matching algorithm in the case of clips with identical reels sharing timecode (and no, I don't want to rename shots - this happens for us when the TC jam sync is dropped and the camera clock is a few minutes out from the TC source - you end up with two clips on the same reel with the same TC range sometimes)

Hi Cali, renaming one clip would solve it. You would also need to go into the avid / fcp and change the tape / reel name for that clip so that any output XML or EDL was also renamed but I think that would do it.

Without renaming, I don't see how software further down the line is going to be able to spot the difference between footage with matching TC and reels.
 
I tried the latest demo but I couldn't make it to use more than 3 cpu cores out of 8. Is that deliberate?
 
I tried the latest demo but I couldn't make it to use more than 3 cpu cores out of 8. Is that deliberate?

Hi Akis, do you mean during render? The render engine behind Monkey Extract is Redline, so it should use as many cores as redline / redalert does.

How many cores get used when rendering from red alert?
 
I am using the latest RA/RR v3.60. This version has a new menu in RR that defaults to render one clip at a time and multiple processors per clip. Like that, I get 780% CPU usage in my MacPro. With your demo, I got only 280% CPU.

Akis
 
I am using the latest RA/RR v3.60. This version has a new menu in RR that defaults to render one clip at a time and multiple processors per clip. Like that, I get 780% CPU usage in my MacPro. With your demo, I got only 280% CPU.

Akis

I'll take a look, it's always used 8 cores before. Do you have the cores set to max on the render settings page? What percentage do you get if you set it to 8?
 
I tested again and the maximum I got was about 400%. So I think there might be some extra parameters you have to set with the new redline.

Also, the "rename" function doesn't work for me. It just creates a 0KB R3D file.

And, when rendering to DPX, the headers are not updated.

Akis
 
I tested again and the maximum I got was about 400%. So I think there might be some extra parameters you have to set with the new redline.

Also, the "rename" function doesn't work for me. It just creates a 0KB R3D file.

And, when rendering to DPX, the headers are not updated.

Akis

It appears this was to do with older builds, and has now been fixed...
 
Back
Top