Monkey Extract - $100 off, this week only

[Nigel Stanford]

Hi guys,

Just a quick note to say that we're running a special offer this week.

Monkey Extract can be purchased (http://www.rubbermonkeysoftware.com?track.asp?id=13) for $249 - saving $100.

The offer expires Jan 10th, don't miss out.

Also note that Monkey Extract will support Avid Filmscribe XML within the next 3 weeks.

Thanks! :)

[Nigel Stanford]

doh... I posted the wrong URL. It's fixed now... :pinch:

[Michael Lindsay]

Hi guys,


Also note that Monkey Extract will support Avid Filmscribe XML within the next 3 weeks.



Hi Nigel

That sound great!! I've finally paid for Monkey a couple of hours ago. I hope I use it for more than copying.. (up to now we use a Avid-duck-fcp-crimson-redcine path for Online)

Will you create an ALE as well? (I think this is important)

kind regards

Michael L

[Nigel Stanford]

Hi Nigel

That sound great!! I've finally paid for Monkey a couple of hours ago. I hope I use it for more than copying.. (up to now we use a Avid-duck-fcp-crimson-redcine path for Online)

Will you create an ALE as well? (I think this is important)

kind regards

Michael L

Hi Michael,

What would be the workflow that it would be useful for monkey extract to create ALEs?

[Michael Lindsay]

Hi Nigel

Loving your responsiveness!

I'm imagining in 2 weeks time I will be able to:

Redrushes export DNxHD and ALE (as i do now)
Avid ALE import and fast import of clips merging with ALE (as i do now)
FilmScribe XML out
XML into Monkey for select pull
Monkey render to DNxHD 185x

Now at this piont I would like to have an ALE out of the same aplication that renders my clips. Otherwise we have to use metacheater which only has access to the QT metadata. You with Monkey have access to all the metadata that RR has?

I need an ALE to be able to relink the clips for my online?

Also I would ideally like to be able to use as few aplications as possible. I have a new editor at the moment and its hurting my head explaining all the twists, turns and unanswered questions of Red post.

For example why can't any Red tools render out a Uncompressed 10bit Avid quicktime? I know this is beyond your control:meh:

Also if your aplication added a couple of things missing from RR (and ALE out) then it could be my/our rushes creation tool as well?

regards

Michael L

[Nir Shelter]

Hi Nigel

I am very interested in monkey extract especially for the rendering tool. My concern is whether the render tool accesses the R3D files and performs a full debayer of the data?

In regards to the copy tool when used with an EDL does the tool read an EDL and create new R3D files accordingly or does it create references like proxies?
Is there a possibility to copy via the EDL with handles as well?

Thanks.

[Nigel Stanford]

Hi Nigel

Loving your responsiveness!

I'm imagining in 2 weeks time I will be able to:

Redrushes export DNxHD and ALE (as i do now)
Avid ALE import and fast import of clips merging with ALE (as i do now)
FilmScribe XML out
XML into Monkey for select pull
Monkey render to DNxHD 185x

Now at this piont I would like to have an ALE out of the same aplication that renders my clips. Otherwise we have to use metacheater which only has access to the QT metadata. You with Monkey have access to all the metadata that RR has?

I need an ALE to be able to relink the clips for my online?

Also I would ideally like to be able to use as few aplications as possible. I have a new editor at the moment and its hurting my head explaining all the twists, turns and unanswered questions of Red post.

For example why can't any Red tools render out a Uncompressed 10bit Avid quicktime? I know this is beyond your control:meh:

Also if your aplication added a couple of things missing from RR (and ALE out) then it could be my/our rushes creation tool as well?

regards

Michael L

Ahh, gotcha. You want to go back into the avid. We can look into this but it's a reasonably large amount of work.

Rather than ALE, would making a new XML referencing the new files work? That's what we do for final cut.

[Nigel Stanford]

Hi Nigel

I am very interested in monkey extract especially for the rendering tool. My concern is whether the render tool accesses the R3D files and performs a full debayer of the data?

In regards to the copy tool when used with an EDL does the tool read an EDL and create new R3D files accordingly or does it create references like proxies?
Is there a possibility to copy via the EDL with handles as well?

Thanks.

Yes, it does a full debayer if you select it, the app has all the red alert options. Check out the demo, and go to the render settings page.

The copy tool takes the entire R3D file for each cut and copies it to another location. So if you have a finished project, you can put all the R3D files that made it to the finished timeline into one place.

[Michael Lindsay]

Ahh, gotcha. You want to go back into the avid. We can look into this but it's a reasonably large amount of work.

Rather than ALE, would making a new XML referencing the new files work? That's what we do for final cut.

I'll look into it!

Michael L

[MichaelP]

Media Composer only takes in AAF. OMF, or ALE to describe sources or compositions. For referencing new sources, an ALE is the easiest way to go since it is basically a TAB delimited file. We could always make an XSL to translate XML to ALE as we do for REDCINE, but it is more streamlined to have an ALE match the batch process output of the QT wrapped DNxHD files created at the same time.

Michael

[Nir Shelter]

Thanks Nigel

[Michael Lindsay]

Hi Nigel

Even if Avid kindly makes another translating xsl file to transform an xml to ale it is not ultimately desirable.

Non-Redpioneers just don't want to hear about that kind of step.

I have a XML file that won't translate at the moment. It might be a 'user error' or simply a formatting bug. Either way I'm involved in an undesirable process alien to many film makers

It would be very apreciated, and key to being 'Avid compatible', to be able to write out an ALE.

thanks

Michael Lindsay

PS If you can write out an ALE Monkey extractor could be used as the ONLY tool (other than the editing aplication) for Red work...

[MichaelP]

Michael -

At what stage does your XML not translate? 3.1 made a lot of fixes in case you are on an earlier version. Also, if your sequence contains "nested" effects, the XML will not work with those yet. We are working on that. The workaround is to decompose the sequence with desired handles, create a sequence from the new master clips and continue from there - in that scenario an EDL should work directly to Monkey.

Michael