D6: REDLine lacks REDColor3 and REDGamma3

Deadline
1

REDLine submission plugin lacks REDColor3 and REDGamma3.

2

Also if you don’t give it a frame range it fails. Shouldn’t it just by default render the entire clip if you’re rendering to quicktime?

3

Also Also Codec settings in the submission script don’t seem to be sticky like the filename.

Also Also Also if you try to render a ProRes QT it just fails but says “Successful” in the task status.

4

Also Also… … … the “UseMeta” Flag doesn’t appear to work. I added a conditional statement to the plugin

if not self.GetBooleanPluginInfoEntryWithDefault( "UseMeta", True ): And then put all of the ISO/Gamma/Colorspace inside of that. It seems to work.

5

Also… my quicktimes are half the size of the ones out of REDCine. AE reports them as “Trillions” of colors so I think they’re both 10 bit. But not sure why Deadline’s are half as big.

6

Also is there a way to submit more than one r3d at a time? Selecting 500 shots for conversion is a chore to say the least.

7

Also, you make me laugh with your posts Gavin! :slight_smile:

8

Where was this feedback during the beta? :wink:

I’ve uploaded a couple files here to address some of these issues. REDLineSubmission.zip should be unzipped to [repo]\scripts\Submission and REDLine.zip should be unzipped to [repo]\plugins\REDLine.

Added these options to the uploaded files.

The submitter no longer throws an error for an empty frame list. If it’s empty, a job with a single task is submitted, and the --start and --end frame options are not padded to redline.exe. You’ll need to test this to make sure it works.

Fixed in the submitter.

Can you send us the render log? Hopefully redline is printing out a message we can watch for and then fail the render.

Can you send us your modified REDLine.py file? Just want to make sure we set this correctly. Note that the files we uploaded here don’t attempt to fix this yet.

No idea. You could always check the command line arguments we’re passing to redline.exe to see if we’re doing anything unexpected.

You can select multiple files in the submitter. They’ll be separated by semi-colons in the submitter, and a separate job will be submitted for each. The submitter we uploaded here makes sure that each job is named based on its corresponding r3d file.

Thanks!

9

Attached my REDLine (Which also has the REDGamma3/REDColor 3 as well).

As to UseMeta, neither of us are correct. The UseMeta flag in the docs says that it will start from the meta data but override every setting explicitly flagged. Technically you need an enable/disable plugin checkbox for every color option so that you could override specific color options. So theoretically you should be able to say “–useMeta” but then also say “–iso 320” to use the white balance from the metadata but override just the ISO. Or use the MetaData for all the color but export everything as REDFilmLog. For the Color enums it would be easier probably just to have a ‘(as shot)’ default option.

I ended up just writing a maxscript to generate a list of command jobs and that works nicely since it will scan an entire magazine/folder for clips and add them all with a single configuration. My concern on the multiple clips at a submission was two fold: 1) the output file name appeared to just be changing to the last selected clip 2) the most time consuming part was navigating into 480 folders and selecting the clip so being able to add multiple clips wasn’t a time saver. And you had to click “Yes” every time you wanted to append a clip. Clicking “No” and submit" took essentially the same amount of time as simultaneously submitting them all.

If I have time in the next few weeks I’ll probably write a REDLineBatch submission script which will let you specific a redmag folder and then have it just add all of the clips in the magazine.

I found a couple other comments.

–loadRSX should have a checkbox to “use .r3d path” by default I have REDCine save all of the RMD files to the same folder. I don’t think even if you have “useRMD” flagged as true that it will look for the RMD in the same folder. Kind of a REDline bug but you could work around it with a little python intelligence. Also… you need a checkbox for that too. :stuck_out_tongue:

If you set “Processors” to 0 it seems to only use one core. However I don’t see a flag in the --help that mentions multi-core usage so is that just a Deadline plugin setting?
REDLine.zip (4.29 KB)

10

Thanks for the information! We’ll add checkboxes next to the color, curve, and gamma settings so that you can control which ones you can override. We’ll also add the RMD file option. I think we might do a little shuffling around of the options as well.

We’ll also fix the output filename bug when doing multiple submissions. The multi-selection works fine if all your files are in the same folder, but yeah, if they’re in different folders, it will still be a PITA.

The processor option must be from an older version of redline. We’ll just take that out.

Cheers,

  • Ryan
11

Here’s another thought. What if we removed most of those color, curve, and gamma settings, and instead added the ability to specify additional command line arguments. I guess it depends on the workflow. If all these settings are typically set in the R3D file, then users probably want to submiti the R3D file as is, without having to specify stuff in the submitter again. But if they want to override a thing or two without changing the R3D file, they can use the additional command line options.

If we do go this route, would it make sense to remove things like Crop and Scale settings, and Qt Burn In settings as well?

12

I like having all of the color options in there because I’ll often override the defaults. For instance I’ll render off H264s in REDGamma3 and then DPX files in RLogFilm. Or I just rendered off 500 clips and overrode the meta data to be just 5600K daylight for consistency between plates. But remembering all the flags is challenging.

Scale and crop absolutely need to stay in though. If you want to output DNxHD or ProRes proxies you need to scale it down to 1080p. And the native sensor is wider than 16:9 so you also need the Fit options. I could see the crop being useful too if you need to output 1.85 or 2.39 footage.

13

I just thought of how to make everyone happy. Don’t select .r3d files, select .RDC folders. To quote red

R3Ds are a little wonky anyway since they get broken up into 2GB chunks. So selecting two R3Ds might be the same clip twice. If I could just Shift+Select every .RDC folder then that would be easy enough. Also I would argue that a multi-submit should be tasks within a single job. Did you say they would submit multiple jobs?

14

Thanks again for the information. It sounds like we need to better familiarize ourselves with a typical RED workflow, and try to support it in a way that covers common use cases. I took a look at the command line arguments, and realized we don’t support things like 3d exports, audio, and export presets either. We’ll take a read through the manuals to learn about how RDC folders work, because it sounds like that should work well.

Cheers,

  • Ryan
15

So there is nothing in the REDCINE-X or REDLINE docs about “RDC” folders, so I must be looking in the wrong spot…

Am I correct in assuming that an RDC folder contains one or more R3D files, and that those R3D files are related and thus should be considered separate tasks for the same job that would be submitted to Deadline? If that’s the case, would the command line arguments be identical for each R3D file (other than the path to the R3D file)? How does exporting QT files work if there is more than one R3D file for a job? How do these folders work for 3D export jobs?

Maybe we just need to find a good R3D footage example that we could use, or maybe this is something you could provide us… :slight_smile:

16

You should have a metric ton of red footage in your S3 folder that Chris gave me access to already.

To give you a quick run-down on the RED file format it goes like this:

.RDM folder (This is the “magazine” aka card folder)

.RDC folders (These are the clip folders that contain the clip)

_001,_002.R3D
(These are the actual data but they are limited to 2048MB at which point they start splitting off into _002, _003 etc.
If you select _001 it will automatically use _002,_003,_004 etc in REDLine, it just needs to know about _001. The filename is consistent between the .RDC folder name and the R3D.

RMD files are their new XML sidecar with the color settings. These are generally used one of two ways. Either people choose to store the RMDs in the .RDC folder along with the R3D (which should be the default REDLine Submission path) or they will dump them into a project/global folder. This means you could save all of the RMD files to a DropBox folder and keep your grades sync’ed across machines and networks without copying the R3Ds.

17

Thanks again! Much appreciated!