Welcome to our community

Be a part of something great, join today!

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

Released: R3D Data Manager for Mac v6.1

BTW, ironic story: Red owes me a bit of money from a purchase that fell through. I asked for the money back, and they sent me a check, which promptly bounced. I traded messages with the people in accounting a few times, and they finally just never called back.

Ive since used some of that money to purchase some other things, but Im sure the guys at Red are super busy concentrating on shiny new toys, just as I would be. :)

And Id still rather deal with Red than any of the competition. Im shooting with 9 of them right now.
 
R3D Data said:
With all due respect to the Red team, and they are doing their best, I must point this question to them. I type this as much out of frustration as out of hope. I need an open line of communication, which just hasn't happened recently.
Click to expand...

If you type redline into the shell, at the very top you'll see:

REDline
REDline Build 298 3D

File Settings:
--i <filename> - input file (required)
--o <filename> - output basename
--pad <int> - filename padding [default = 6]
--outDir <path> - output directory path
--makeSubDir - Make a subdirectory for each output
--exportPreset <name> - Load settings from an export preset: [default = none]
"dpxhd"
"exr"
"prores422"
"tiff5k"
...

That's a list of presets that redline prints out.
 
Deanan said:
If you type redline into the shell, at the very top you'll see:

REDline
REDline Build 298 3D

File Settings:
--i <filename> - input file (required)
--o <filename> - output basename
--pad <int> - filename padding [default = 6]
--outDir <path> - output directory path
--makeSubDir - Make a subdirectory for each output
--exportPreset <name> - Load settings from an export preset: [default = none]
"dpxhd"
"exr"
"prores422"
"tiff5k"
...

That's a list of presets that redline prints out.
Click to expand...


Thx.

... and if you want to make a preset with RedCine-X you do?
 
Deanan said:
If you type redline into the shell, at the very top you'll see:

REDline
REDline Build 298 3D

File Settings:
--i <filename> - input file (required)
--o <filename> - output basename
--pad <int> - filename padding [default = 6]
--outDir <path> - output directory path
--makeSubDir - Make a subdirectory for each output
--exportPreset <name> - Load settings from an export preset: [default = none]
"dpxhd"
"exr"
"prores422"
"tiff5k"
...

That's a list of presets that redline prints out.
Click to expand...

Internal builds are quite far ahead of release BETA's then =)
 
Deanan said:
Make an export preset in REDcineX just as you normally do. They all automatically show up in redline.
Click to expand...

How would be the procedure to create a setting to export a QT of Cineform RAW file?
 
Glad there is an update. Is there a new update for the Trial as well? I have r3d datamanager but I would like to cross compare it on both my laptops. I'll be giving it a spin. Thanks so much guys for the update.
 
Hi Conrad.
Hope you get this before the next update. I have been asked by many companies lately not to format drives between reloads during the day. As a result I end up using the skip option in the 'If the RDC folder Exists:' menu which works well.
But the verify after source still reads all the checksums from previous backups made from the same drive ID.

Can you have an option to skip RDC folders that already exist during the checksum verify stage in the next update?
Simply to save time on set by not checking checksums that have already been checked.

Thanks,
Nir.
 
I've found this to be a big problem on the last shoot I was on as the drives were getting close to capacity by the end of the day. We normally don't format between reloads because a)why delete footage if you don't have to, they camera media becomes an extra back up at the end of the day and b)formatting the drives takes time, but not formatting we get quicker swaps.

The other problem I have is that when doing the destination verify the GUI doesn't really give me much information. It just sits on the last clip and the progress bar doesn't move until it's done. This is really frustrating as it's nice to have a least a vague idea of how much longer a copy has got (I do miss the estimated time remaining, even if it wasn't accurate.

Nir Shelter said:
Hi Conrad.
Hope you get this before the next update. I have been asked by many companies lately not to format drives between reloads during the day. As a result I end up using the skip option in the 'If the RDC folder Exists:' menu which works well.
But the verify after source still reads all the checksums from previous backups made from the same drive ID.

Can you have an option to skip RDC folders that already exist during the checksum verify stage in the next update?
Simply to save time on set by not checking checksums that have already been checked.

Thanks,
Nir.
Click to expand...
 
In my case yes 6.1.

If it is fixed that’s great as that is a very efficient way to work.
But in that case the progress bar is somewhat misleading, may be worthwhile implementing a more accurate ETA on destination verify. Or at least a read out of file names of the files R3D Data Manager is either reading or writing.

This is simply because then we can use the efficiency and give more accurate predictions on how long a download will take.

Thanks,
Nir.
 
Yes, 6.1. I also suffer from only getting the checksums written to the first destination bug if they related in some way.
 
So after having numerous bad experiences with RedCine-X I'm looking for a reliable and robust transcoder to make ProRes 422 HQ Quicktimes for FCP. I see that R3D DM does that. How does it perform? We need speed of course, but we need quality output too. After several days of torture I and my assist are pretty sick of RCXs pink and green files, crashing, refusing to launch etc. And this was on several different computers.
 
R3D Data Manager also does quicktime downconverts. However, if you are using the MX, you will need the latest version of Redline installed, which is included as part of RedCine-X. It has the same guts as RedCine-X. So if you are having issues, you can try our rendering features, but I suspect that your issue may be deeper than we can fix.
 
R3D Data said:
R3D Data Manager also does quicktime downconverts. However, if you are using the MX, you will need the latest version of Redline installed, which is included as part of RedCine-X. It has the same guts as RedCine-X. So if you are having issues, you can try our rendering features, but I suspect that your issue may be deeper than we can fix.
Click to expand...

We now think the crashing was due to a few corrupt files from the first day of shooting. RedCine-X did not handle these files gracefully at all. How well does R3D Data Manager handle corrupt files?
 
You must log in or register to reply here.
Back
Top