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

Hi Conrad.
This is regarding the problem I was having of checking the destination checksums post copy problem I was having a few weeks ago.

I am using a new gen MBP late 2008 release, the few that were released with an express card slot, 4GB RAM 1067MHz. A Stardom raid set to raid 1 with 2X 1TB 7200 Barracudas in it connected via Esata to a Silicon Image Esata to express card adapter in the express card slot. In addition to this I will have a second Esata drive connected to the second Esata slot on the adapter either a Lacie 1TB or Soho raid 1 - 2X2TB HDD or Nexstar raid 1 - 2 X2TB HDD. Copying from a Reddrive connected via the FW800 or a CF in a Lexar reader connected via FW800.

I have ever since discovered that the checksum files were being written to only one of the destinations I was copying to. I was able to run a check on the destinations that had the checksum files but not on the others as they didn't have the checksum files in them. So when I added the formally destinations to the source window that did not have the checksums the “verify all checksums” button remained greyed out. I couldn’t find in the preferences any options relating to the destination checksum writing.

How can I make R3D Data Manager write the checksums to all destinations?

Thanks,
Nir.
 
I find the same thing Nir - was going to ask the same question, but you've done it for us! Thanks. :)
 
We havent been able to duplicate this in our test suites, but we think we have found the culprit.

For now, if you are having this issue, just copy to one destination, and then copy from the destination to the next, OR manually copy the md5sums.txt files from one RDC folder to the duplicate.

Thanks.
 
Conrad, I've been having the same issues with the checksum files only being written to the first destination. I'm on a MacBook Pro as well.
 
I've had the same problems and I'm using a MacPro...I just did a transfer a couple of minutes ago: checksum files written to only the first destination.
Any idea when 6.2 will be out?
 
Other topics and areas of R3D DM...

Other topics and areas of R3D DM...

Hello,

When using "QT Batch Renders", the "Output Settings" codecs do not reflect the CineForm codec that I own (Neo4K). Is there any particular reason for not supporting it?

Also, under the same section, but the "Rendering Settings", it contains "RedFilm" as one of the gamma options. To the bet of my knowledge, this is not implemented yet via their grading software (RC-X), unless you have a very good inside connection.

If it is not officially implemented yet (again, vis RC-X), what does it really do? I know that Graeme is working on this, and provided a brief explanation of his intention. I would like you to elaborate more as to what really does when selected on your software.


BTW, Great improvements!!!


Thanks!
 
Luis Otero said:
Hello,

When using "QT Batch Renders", the "Output Settings" codecs do not reflect the CineForm codec that I own (Neo4K). Is there any particular reason for not supporting it?
Click to expand...

Its not supported by REDline.

Luis Otero said:
Also, under the same section, but the "Rendering Settings", it contains "RedFilm" as one of the gamma options. To the bet of my knowledge, this is not implemented yet via their grading software (RC-X), unless you have a very good inside connection.

If it is not officially implemented yet (again, vis RC-X), what does it really do? I know that Graeme is working on this, and provided a brief explanation of his intention. I would like you to elaborate more as to what really does when selected on your software.
Click to expand...

When its supported in REDline, our software will instantly support it. Its not currently supported by REDline, so it doesnt really do anything at the moment. I believe it will default back to whatever is selected in the R3D's metadata. We scripted it so that all the options override the R3D metadata - and since its not supported, it should default back to the metadata.
 
Very cleaver...

Very cleaver...

OK, got it. Very cleaver from you to be ready for the new REDGamma when implemented!

As for the CF Codec, that is a bummer... Why then RC-X v261 (current) and the "Great-Old-Redcine" v20, which I still use for specific occasions, are capable of exporting it without a single problem? Something does not seem right here; it does not make sense...!

So, what then is needed? Modify/selectively or completely deactivate REDLine so your software will be able to see it and process it? This is half joking and half serious. Can something be done? That will add so much power to your software if you really understand the incredible and realtime, but underestimated attributes of CF Codec.

Please advise if something is possible,
 
Is it part of your plan to include CF Codec at one point of the R3D DM development cycle? That would give you an extra chunk of clients that can be using your tools for a very useful, time-saving task.

BTW, What will be the effect (final product) of selecting the "RAWCodec" listed as part of the supported codecs?

Thanks,
 
Luis Otero said:
Is it part of your plan to include CF Codec at one point of the R3D DM development cycle? That would give you an extra chunk of clients that can be using your tools for a very useful, time-saving task.
Click to expand...

Im afraid you are not understanding the issue. Its not us that is limiting the choice of codecs. This is a limitation of the current version of REDline, made by Red.
 
R3D Data said:
Im afraid you are not understanding the issue. Its not us that is limiting the choice of codecs. This is a limitation of the current version of REDline, made by Red.
Click to expand...

REDline can use any codec if you create an export preset in REDcineX first and then use that preset in REDline.
 
With all due respect...

With all due respect...

R3D Data said:
Im afraid you are not understanding the issue. Its not us that is limiting the choice of codecs. This is a limitation of the current version of REDline, made by Red.
Click to expand...

With all due respect, but sometimes (really very frequently), cyber-colleagues forget or maybe do not fully understand, that the fundamental existence of this forum is to help to illuminate artists and producers about technological advancements, and is not a forum that was borne for a new species of "RED-Geek Squad".

We have accepted that in order to maintain ourselves competitive we need you guys very much! And by negating or refusing that we need to acquire a new set of technological skills in order to succeed, is digging yourself your own burial hole, and very very deep.

So, with that reality, we depend on people that have mastered those skills in order to develop the tools that can help to create that right balance of having just enough tech knowledge, but not forgetting that this is an artistic and managerial based industry.

I need to admit that I have no idea, nor I am extremely intended to learn, about command lines, codes, etc, to do it by myself. I really need to be savvy enough to ask the the questions that will push the envelop for those who are tech oriented, to build the tools that can facilitate our job and passion.

So, as Deanan explained, if this can be done under the hood (and who knows what else more) by creating some presets, then take the opportunity and use such route to develop new functions that will indeed increase your customer base, hence increasing the revenue opportunities. At the same time, this will help the artists and managers, to offer better end results to our clients.

We have demonstrated beyond any doubt that we are willing to pay, as we have done it again and again, for the enhancements of the tools so they can facilitate and make more efficient our work.

The question that is in order now is: are you up to the task, or willing to hear about real world workflows, so that you can adjust and enhance the tools you offer us, so that your product is driven by our needs, and not the other way around, by limiting or forcing us to accommodate our workflow based on the available tools?

Respectfully,
 
PS

Do not get me wrong, I think that your software is one of the most advanced tools that is available for the Red users. It is just a petition that I hope will sparkle the addition of extra functions to make it the best one.

Also, I still do not know what is the effect of selecting "RAWCodec" listed as part of the supported codecs?
 
Deanan said:
REDline can use any codec if you create an export preset in REDcineX first and then use that preset in REDline.
Click to expand...


Deanan,

Is the how-to-do-it explained somewhere? I know how to create presets in RC-X, but the use of them in REDLine... That is another story.

I would like this to be integrated, but if I can try to do it now that I need it, it would be really helpful!
 
Luis Otero said:
We have accepted that in order to maintain ourselves competitive we need you guys very much! And by negating or refusing that we need to acquire a new set of technological skills in order to succeed, is digging yourself your own burial hole, and very very deep.
Click to expand...

Please again understand that not once have I refused help or refused to offer new code for new enhancements. I have, and will continue to, offer new code and enhancements. I do so concurrently to offering support to new systems & platforms, offering support to filmmakers who dont even use my product, and working on film sets (as Im currently in the Ukraine (Im Los Angeles based) doing as I type this).

However, I can only do as much as Red allows me to do. Specific requests by me were made on features like this that were not followed up on. Knowledge was not shared. Perhaps I missed a feature in the command help, and I understand that Im on my own here. But I shouldnt have to be, with respect to coding new features that rely on Reds tools.

Luis Otero said:
So, as Deanan explained, if this can be done under the hood (and who knows what else more) by creating some presets, then take the opportunity and use such route to develop new functions that will indeed increase your customer base, hence increasing the revenue opportunities. At the same time, this will help the artists and managers, to offer better end results to our clients.
Click to expand...

I would love to offer these things, and will as time moves forward. However, as I pointed out above, its very difficult to do such things when there is little communication.

Luis Otero said:
The question that is in order now is: are you up to the task, or willing to hear about real world workflows, so that you can adjust and enhance the tools you offer us, so that your product is driven by our needs, and not the other way around, by limiting or forcing us to accommodate our workflow based on the available tools?
Click to expand...

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.
 
You must log in or register to reply here.
Back
Top