Welcome to our community

Be a part of something great, join today!

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

SDK Update

Deanan

Red Team
Joined
Jan 19, 2007
Messages
3,844
Reaction score
0
Points
0
We've started to email the SDK bundles out. We're not fully automated yet so it will take some time to get them all out. The first batch is going out tonight and the rest will go out tomorrow.

Deanan
 
Perfect! Just getting the lab set up in our new castle on the hill. Jacob's ladder installed earlier. The pipe organ guys had one hell of a time getting it installed up in the loft. Just waiting for a good thunderstorm!

Now where did I put that Bach sheet music...
 
Deanan, that is a great news - thank You! I have asked this before, but never got a direct answer: Can I use the SDK to write a small utility to "trim" RAW files? The idea is to preserve only the section of the RAW file You want with IN/OUT points and then re-save the new file as original RAW without any actual image processing. This will save tons of space for both online RAID's and backup storage. It will also assist greatly with upload of RAW files on the net... I would gladly make the utility free and send You back the source code in case You would want to include it in Red Alert... :)
 
Yeah, it was me asking, but they only said that this would be possible "later on". My question is - would this be possible with this particular version of the SDK? Of course a new RAW file would be created keeping the original untouched - I have no problem with that at all... :)
 
"Software Developers Kit" - it's a kit of software tools, files and code that allows a programmer to develop software that works with the RED R3D files.

Graeme
 
Deanan, that is a great news - thank You! I have asked this before, but never got a direct answer: Can I use the SDK to write a small utility to "trim" RAW files? The idea is to preserve only the section of the RAW file You want with IN/OUT points and then re-save the new file as original RAW without any actual image processing. This will save tons of space for both online RAID's and backup storage. It will also assist greatly with upload of RAW files on the net... I would gladly make the utility free and send You back the source code in case You would want to include it in Red Alert... :)

I answered that in another thread. Trimming will come a bit later in the SDK.
 
Deanan - my apology for repeating the question.
I don't want to sound to pushy, but I don't see any reason why this utility is not integrated already in the Red Alert or as a stand-alone. It is a very straight-forward and very simple tool to write and the benefits are huge to everyone - I don't think there is a single Red One owner who would not wish for such a tool... There is also no "negative" side to it from Your (RED's) perspective, as such a tool couldn't be used for anything else as it would only relate to the raw sensor data from Your sensors...

Am I asking too much? If so - just ignore me...
I will get busy in the meantime with our main purpose for the SDK...

Take care

Peter

PS: Do You guys still have (or can provide) the fiber-optic unit for the uncompressed data?
 
Pardon my presumption for answering what should be answered by Red, but I'll just point out that so far the only thing we've seen that generates R3D files is the Red camera. For all we know, even RED may not have a standalone software tool to do it. They may well wish to add something to the file format as a flag saying "this file is not original", or maybe even tracking past filenames and a revision history, and they might not have figured out how they want to handle that yet. Anyway it might be one of those things that seems simple but can become complex when you consider all the possibilities.
 
Deanan - my apology for repeating the question.
I don't want to sound to pushy, but I don't see any reason why this utility is not integrated already in the Red Alert or as a stand-alone.
PS: Do You guys still have (or can provide) the fiber-optic unit for the uncompressed data?

Trimming is not trivial at all considering the rate at which the file format is changing. We will add it at some point but there is HUGE list of priorities that are interdependent. To push one to the top can have severe impacts on deadlines and stability if the order of priorities is not balanced. Trimming is one of those functions that impacts everything.

There is not enough demand for uncompressed output at this point to justify it's development. (think .001% interest from customers)
 
Pardon my presumption for answering what should be answered by Red, but I'll just point out that so far the only thing we've seen that generates R3D files is the Red camera. For all we know, even RED may not have a standalone software tool to do it. They may well wish to add something to the file format as a flag saying "this file is not original", or maybe even tracking past filenames and a revision history, and they might not have figured out how they want to handle that yet. Anyway it might be one of those things that seems simple but can become complex when you consider all the possibilities.

The thing is that You don't need to "generate" anything. All You do is keep the header, cut out the individual frame blocks of data, modify header to reflect the changes and save. The file will still be "original" RED file - You have not added anything to it. You have only removed unwanted frames. This could be almost done on a binary level without even the SDK...


Deanan - I understand where You coming from and I won't bother You again about it... :)

In regards to the uncompressed output: In this case You may want to consider removing it from the tech specs:

http://www.red.com/cameras/tech_specs

scroll to the very bottom and see:

"All formats recorded as 12 bit linear uncompressed or compressed RAW"
 
When you modify the header, it's not the original file any more... the devil is in the details... eg. file name conventions, does the internal time/date refer to the original or modified file? I don't know if they have any checksumming functions over the full file, but they might. What about sound? At least for some frame rates there is not an integer multiple of sound samples per frame, I think... there are just a bunch of details.
 
Hi Peter,

There were some applications that fell into a grey area and your might have been one of them. I'll send you an email.

Cheers,

Deanan
 
Back
Top