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

avid mxf red workflow

purchasing

purchasing

when i come back to the mac
monday 8th june
jamfuze will be available to buy.
you'll have to paypal some money ($49) with an email address in your paypal info and when I get that showing up
i'll email you the fully featured no holds barred 23.98 app (or a link to the app).
I'm deliberately (:)) keeping the gui quite basic now as when hans is done, all the gui stuff will be done by clipfinder and jamfuze will be a plug in for clipfinder.
that means you get all the coolness of Hans' User Interface with the option to encode directly to mxf from that application.
I'm looking forward to cropping!
Also Hans knows all about ale creation so maybe all you guys and gals who want ale stuff can have it from Hans' side of things.

if you purchase jamfuze you'll get the plugin version either with it or soon after (when me and hans have sorted it!)
just to let you folks know...
j
 
Jamie,

I'd hate for you to have to make a CUT specific version, and I don't know how many other people use my workflow.

I think most people do use Monkey Extract for DPX creation. We use RedCine because we haven't seen a need yet to purchase M.E. if it can be done through RedCine.

Our workflow is based on the workflow at avid.com/red.

R3D to DNxHD QTs using RedRushes
R3D to ALE using RedCine (& TestXSLT to translate)
Import ALE / Link to QTs. Fast-Import.
edit.
Sequence to FilmScribe XML to RedCine (& another round of translation using TestXSLT)
RedCine to DPX for online to Smoke

JamFuze will make everything so much easier and faster, but we'd either have to purchase M.E. for DPX creation, or have options to customize a few metadata items to allow the JamFuze MXF media to be relinked to our RedCine created ALE.

Thats our workflow, thanks again.

-James
 
Hi Jamie

I did download the demo version 1.0 and am having some problems.

The converted files are not getting with the MXF. The Avid is not recognizing the format of files generated. xxxx.mov.dnx
Neither found the button which says that the files have r3d audio.

The program is fantastic and I just bought, but not yet received the link to the full program :(

Many thks,
Alexandre Xavier
 
Xavier

Xavier

Hi Xavier
the xxx.mov.dnx files are NOT the avid files!
they are just intermediate files to help make the MXF media

the .MXF files are the avid files and they may be in your avid mediafiles/mxf/1 folder (if you ticked the move to avid media folder box)
they will look like this A001_XXXX_001_JP_V1.MXF
or something like that
these files can be read into your project with Media Tool in AVID Media Composer
they DO NOT need "IMPORTING"
The audio tickbox isn't needed anymore as JamFuze detects whether there's audio in the R3D and acts accordingly.

please make sure the demo works for you BEFORE sending any money.
phew!

HOWEVER JamFuze will NOT work with 25fps stuff so if you need that I'll have to give you your money back!!!!
please let me know.
i'm taking the paypal link off RIGHT NOW!!!!
I forgot people are watching my website. it's a novel experience.
8th June People then I'll be ready for ya!
j
 
Hi Jamie

The framerate was wrong. I believe that it was not converted to MXF.
The only JamFuze converts R3D to 23.98 now, right? The material that was tested was shot in 24fps
I have a question.
The JamFuze not use all the cores of the MacPro, right? There he used to force all cores to facilitate the conversion?

I will be waiting for news on June 8 ... :)
 
xavier 24fps!!!!

xavier 24fps!!!!

Right!
24fps is not supported yet as jamfuze is mainly aimed at TV which is done at 23.98
it wouldn't be too hard for me to add 24 support if people want it.
You do so that's 1!
jamfuze uses all 8 cores when doing the R3D to .mov bit and then not so much when doing the unwrap and rewrap to MXF as this is ffmpeg and writeavidmxf which are not so multithreaded possibly.
This is a lot easier though so it still goes around 120fps on my mac - that is 5-6x faster than real time. so it's OK!
I've refunded you your money (I found that button!!) and will try and do a demo that works at 24fps for you so you can evaluate it properly.
cheers
j
 
june 8th stuff

june 8th stuff

Chris
june 8 is just my self imposed cut off point
i'm releasing it to buy then
w h a t e v e r s t a t e i t i s i n

the integration with clipfinder will come real soon after i'm sure
and people will get that fer nuthin from me if they bought jamfuze
but there are a few things i want to do before the 8th like

24fps support for xavier
more metadata in the mxf for mmost
cleverer online stuff so if someone puts "too dark" in the comment of the EDL JamFuze will bump up the iso rating to 1000asa automatically (you get the idea...)
working out what the hell an ale actually is/does....
then i've got to get back to the day job as the TV stuff comes in thick and fast after 8th june.

also I did a Arri D21 vs RED comparison the other day
I think RED just about swung it because it was lighter to carry!
D21 definitely beat it on the highlight handling (but not by much)
and the outside stuff looked really nice on the RED when not deliberately over exposed. The DP was testing it to breaking point and they both held up remarkably well he thought.
he still likes film better though. ah well.
j
 
i vote for support of all things not PAL essentially :) since your boss is keeping PAL to himself for now. you could even support 29.97 technically. Although i don't shoot in that.

Here is the description of an ALE straight from MichaelP (phillips) from AVID

http://www.24p.com/ALE.htm

enjoy!
 
ale spec

ale spec

thanks for that jason
I've just read the doc and had a look at the sample ale
that is probably what i need to understand it/make it work.
just one thing
23.976 is not mentioned anywhere.
25 24 and 29.97 only.
is there a newer ale spec out there somewhere?
j
 
smokeyfuze for CUT

smokeyfuze for CUT

hello james and other Smoke type people

http://www.jamieparry.demon.co.uk/smokeyfuze.zip

this gets you a version of jamfuze offline (called smokeyfuze offline)
that lets you use edgecode if you wish
and removes the .mov from the tape name in the avid metadata

try this with your current workflow

then
do it again but don't use edgecode
do the usual edit,decompose make new sequence and put the decomposed clips in that
output EDL red16 template from that "allclips" sequence
look at the videos on
http://www.jamieparry.demon.co.uk

for more info on the avid bit.

then try smokeyfuzeDPX online
don't use spaces in anything!!!!
this will generate dpx's at 1920x1080 in a folder structure like this
chosenoutputfolder/projectname/1920x1080/tapename/clip.00000.dpx-clip00100.dpx
then you'll have to do the proper edl (from your real sequence) relinking in smoke somehow.
there was a good video on how to do it at autodesk but i guess you'll know how to do it anyway.

let me know if i'm close
it was pretty easy to do so i can work on it a bit more if we're close....
j
 
24fps demo--- AQXavier

24fps demo--- AQXavier

ok

http://www.jamieparry.demon.co.uk

the jamfuze demo now at 0.73
this lets you do 24fps stuff as well as 23.976
credits done also

on the online demo you still have to pick fps manually
it will still be black and white until you buy the real thing

cheers
j
 
Jamie,

SmokeyFuze worked great! MXF media generated by smokeyfuze can be relinked to an ALE created via RedCine/XSLT. So SmokeyFuze is perfect for our workflow now.

As for the SmokeyFuze ONLINE portion, I'm sure it would work, but my Smoke artists are particular about their DPX files. Sometimes they want 1920x1080, sometimes they want 2k/4k if its green screen stuff. So unless the online portion gave me a full range of choices for generating DPX files, then I would just stick to making the DPX files from RedCine.

I will test SmokeyFuze ONLINE later today though, and report once I've successfully generated some 1920x1080 DPXs.

But wow, what a great job you've done. I've only had a chance to test JamFuze/SmokeyFuze out on a few clips, but I can't wait to try a full simulated workflow, or even better, a real job.

Keep up the great work, can't wait to grab to company credit card and pay you for your hard work. ;-)

-James

***NOTE TO MICHAEL P. / AVID****

I went to Avid.com/Red to make sure I had the latest XSL files. The XSL files posted on there are not working as advertised. The "REDCINE_318_ALE_16.xsl" file no longer generates 16 character tape names for the ALE. As far as I can tell, "REDCINE_318_ALE_16.xsl" and "REDCINE_318_ALE_4.xsl" both generate 4-character tape names. This must have been updated at some point, because I have an older copy of "REDCINE_318_ALE_16.xsl" (modified 11/25/08) that correctly generates 16-character tape names for the ALE. The "REDCINE_318_ALE_16.xsl" posted on there currently has a modified date of 2/23/09. When this is corrected I'll be able to test the process of going back to RedCine to make DPX files, using the JamFuze+ALE method. For now, I just crash RedCine when trying to use my old 11/25/08 XSL.

**** UPDATE x2 *****

I have modified the .XSL file myself to use 16-character tape names. I've attached it if anyone else needs it, or if Michael/Avid would like to update the one on avid.com. Using this updated "REDCINE_318_ALE_16_CUT.xsl" file, ALEs created by RedCine can be relinked to MXF media created by SmokeyFuze, and then brought back to RedCince after editing using FilmScribe/XSL method with no problems.
 
Jamie,

I set a batch of R3Ds to convert using SmokeyFuze, and found a quirk/issue.

I told it to use the Folder's RSX file. Problem was, only half of the RDC folders contained .RSX file. The other half didn't. So when it reached the RDC folders that didn't contain an .RSX, it created MXF media that was solid white video.

Perhaps an option to use .RSX file "if present" would be handy.

Thanks, keep up the good work.

-James
 
James Rayburn said:
Jamie,

I set a batch of R3Ds to convert using SmokeyFuze, and found a quirk/issue.

I told it to use the Folder's RSX file. Problem was, only half of the RDC folders contained .RSX file. The other half didn't. So when it reached the RDC folders that didn't contain an .RSX, it created MXF media that was solid white video.

Perhaps an option to use .RSX file "if present" would be handy.

Thanks, keep up the good work.

-James
Click to expand...

just playing devil's advocate, but if there is NO .rsx file... then what?

if no .rsx then use metadata? if no .rsx in the .rdc folder, then use this other .rsx file? how would the software know?

isn't that what '1 .rsx to rule them all' (i hate that he changed that label) is for?

MAYBE the software could trap the error & ask 'HEY, there's no .rsx for this one... now what?'

that'd be sweet.
 
You must log in or register to reply here.
Back
Top