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

Dragon Update + A.D.D.

Yup. Looking forward to going to 11 ...

16DR.jpg
 
David, not sure I understand. What do you mean with 72DPI?
The DPI setting for an image is just meta data, just like iso in an r3d file. If you want any other DPI you just change it. It got nothing to do with the quality of the picture it's just a number that tells your printer how big you want your image to be when it lands on a paper...

RCXP sets the DPI to 72 as that is an old standard value for images made for screens. Old Flames and other programs got difficulty reading tiffs at any other DPI than 72.

the dpi is actually not even metadata....it simply is a way of laying out the resolution...dots per inch....so if you have a 720x720 pixel file it can be 10x10 inch at 72 dpi or 1x1 inch at 720dpi.....its simple math....a 6000x3000pixel file is a 20x10 inch print at 300dpi.....or a 60x30inch print at 100dpi.....
screen resolution (before retina:)...) is/was 72 dpi.....for print you really don't want to go below 200dpi.....epson ink jets really like 270dpi....
regardless your sensor gives you your max number of pixels...how you "spread" them out is your choice...
 
34 said:
So is it similar to frame summing (or averaging), but in post? Could something similar be done with MX (just to a lesser extent)? Any chance of an example (presumably TIFF)?
Marketing will decide if they allow it to go to MX sensor. I was doing this technology over 6 months ago with OK results. You can look up the threads, I believe They were encouraged by my posted test images.
It's called "super resolution".
Note: it requires a light or no OLPF to work, as well as a razor sharp starting point. Even if you are slightly out of focus the technology will do nothing. MX has an overbearing lowpass . RED would need to offer a lighter one for ADD to have effect on MX.
 
Last edited:
Marketing will decide if they allow it to go to MX sensor. I was doing this technology over 6 months ago with OK results. You can look up the threads, I believe They were encouraged by my posted test images.
It's called "super resolution".

Nice try Les. You should probably put a " I think it is " somewhere in your claims so people know you don't actually know what you are talking about.

A.D.D. is not "super resolution".

That shit be old news... we have been playing around with "temporal resolution" for years. I even have a few old RCX builds from before you were even a memeber with it. You got one thing right in your post though, the results are just OK. Which is why we never implemented it.
 
the dpi is actually not even metadata....it simply is a way of laying out the resolution...dots per inch....so if you have a 720x720 pixel file it can be 10x10 inch at 72 dpi or 1x1 inch at 720dpi.....its simple math....a 6000x3000pixel file is a 20x10 inch print at 300dpi.....or a 60x30inch print at 100dpi.....
screen resolution (before retina:)...) is/was 72 dpi.....for print you really don't want to go below 200dpi.....epson ink jets really like 270dpi....
regardless your sensor gives you your max number of pixels...how you "spread" them out is your choice...

All true. But Bjorn is right as well. It's metadata in the file that tells the software which of those "spreads" to use.
 
Nice try Les.

A.D.D. is not "super resolution". You should probably put a " I think it is " somewhere in your claims so people know you don't actually know what you are talking about.

That shit be old news... we have been playing around with "temporal resolution" for years. I even have a few old RCX builds from before you were even a memeber with it. You got one thing right in your post though, the results are just OK. Which is why we never implemented it.
Isn't temporal demosaic just a 'flavor' of superrez .
I'm happy you have gone in that direction. I've posted a while back that motion should be part of the solution to debayer. DSLR guys just don't have that option. You guys win!
 
Isn't temporal demosaic just a 'flavor' of superrez .
I'm happy you have gone in that direction. I've posted a while back that motion should be part of the solution to debayer. DSLR guys just don't have that option. You guys win!

The goal of A.D.D is not to add resolution, so no.
 
Hey, I told you guys to do 6K a couple years ago . . . glad you listened ;-)
 
Hey, I told you guys to do 6K a couple years ago . . . glad you listened ;-)

Dibs on telling them to use carbon nano fibers... in something or another. '-)
 
Jarred. Quick question. How many fps you get with RR-X for processing ADD ?

Rivai
 
BTW.. God bless Compressed RAW aka .R3D.

Its so awesome to be able to go back to old Dragon footage already in the can and long forgotten about and be able to bring it back to life with the new stuff.
 
What is important to note here is NOT to confuse the need for RRX for rendering vs. Post workflow, two very different things...

RRX is still a Badass piece of gear any one in needs to work in Full Res needs to have, I for one I sure don't won't to go frame by frame at 1/2 res and then goto one to one back and forth till I find my better frame to pull...

RRX is an essential tool to do that and other jobs in full blast...

A.D.D. is for rendering out the absolute best juice off each frame and only in this process Jarred said that the RRX will only give a little more... But again don't confuse this with not needing the RRX for all other task in the process...


Unless I am getting this all wrong, which won't be the first time nor the last... ;)
 
Back
Top