FCAM thing in a nutshell for non-developers... - Page 2 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 14 hrs, 56 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 3 hrs ago
more...

Page 2 of 15

< Prev

Next >

Last »

Thread Tools

	ossipena	2010-07-22 , 15:03
	Posts: 3,159 \| Thanked: 2,023 times \| Joined on Feb 2008 @ Finland	#11

well, with what settings are you viewing the dng?

because dng isn't a picture, it is raw data from sensor that has to be converted to picture in order to view it. i am betting on conversion settings.

__________________
Want to know something?
K.I.S.S. approach:
wiki category:beginners. Browse it through and you'll be much wiser!
If the link doesn't help, just use
Google Custom Search

Quote & Reply |

Crugath	2010-07-22 , 15:09
Posts: 38 \| Thanked: 18 times \| Joined on Mar 2010 @ Guildford, UK	#12

Default settings, it doesn't seem to store anything on White Balance. I set WB to 6400k in Fcamera and then viewed it in Bridge and the same problem occured. If you set the White Balance sliders to the extreme right in Camera Raw you can get it almost correct but the sliders don't slide quite far enough...

This is the closest I can get it with a temperature of 50,000 and tint of +150

http://the-buccaneer.co.uk/image_edi...1279811361.jpg

Quote & Reply |

	Switch_	2010-07-22 , 15:18
	Posts: 601 \| Thanked: 549 times \| Joined on Mar 2010 @ Redditch, UK	#13

I've got exactly the same problem, using Ps CS3 - heavy Cyan tinting on all the *.dng's. As you described above, I can't quite slide the adjusters far enough to remove the tint.

Thought it might be the case that I didn't have the fcam drivers installed, but then recalled that I went root and used the apt-get install command to ensure all dependencies were present....

Strange that the app writes to an Adove format and yet when opened in an Adobe application it all goes a bit..... Well...... Tits up?

Last edited by Switch_; 2010-07-22 at 15:18. Reason: Spelling

Quote & Reply |

The Following User Says Thank You to Switch_ For This Useful Post:
Crugath

Crugath	2010-07-22 , 15:23
Posts: 38 \| Thanked: 18 times \| Joined on Mar 2010 @ Guildford, UK	#14

Originally Posted by Switch_

Strange that the app writes to an Adove format and yet when opened in an Adobe application it all goes a bit..... Well...... Tits up?

My thoughts exactly!!

Hopefully some clever coder can sort out storage of metadata in the DNG, as currently the only metadata that Bridge/Photoshop reads from the DNGs are aperture and shutter speed, everything else is left blank with regards to camera settings when the image was captured.

I'd love to help code and sort this out, but I only know PHP, mySQL and Actionscript 3

EDIT: Rather than double post, I thought I'd add to this one. I made a post over on the garage page for FCamera and the devs say they also have this problem and are currently working on it!

HOORAY

I can't wait for the next version to get released!

Last edited by Crugath; 2010-07-22 at 23:03.

Quote & Reply |

The Following User Says Thank You to Crugath For This Useful Post:
Switch_

abadams	2010-07-22 , 23:51
Posts: 14 \| Thanked: 124 times \| Joined on Jul 2010	#15

Found the bug. We were casting a possibly-negative floating point value to an unsigned integer, so the color matrices stored in the DNG files (required to correctly interpret the raw data) went well.... tits up, as switch puts it.

We've got it fixed and checked into extras-devel. We're making sure we didn't break anything else and then we'll promote it to extras-testing and it should appear as an update in app manager.

Quote & Reply |

The Following 18 Users Say Thank You to abadams For This Useful Post:
AlMehdi, attila77, bergie, Bobbe, debernardis, Helmuth, jcharpak, joelus, maguitodelrock, Milhouse, ossipena, Rob1n, saveas, sjgadsby, steph, Switch_, wmarone, ysss

ericube	2010-07-22 , 23:58
Posts: 13 \| Thanked: 1 time \| Joined on Jun 2010 @ Glasgow, United Kingdom	#16

Originally Posted by Crugath

This is working great, I'll show some sample images in a bit. But I'm having trouble with the DNG images that are saved by FCamera.

The DNGs have a really heavy cyan tint on them when I view them in Adobe Bridge, which is not removable no matter what settings I use in Camera Raw. This is Adobe CS5 btw.

When I try to view them in Irfan View they display as a red garbled mess.

When I check the option to save as JPG as well, these images save absolutely fine.

Anyone got any ideas why the DNGs don't display properly on the PC?

Here's an HDR image I made earlier, merged in Photoshop CS5. http://the-buccaneer.co.uk/image_edi...1279809203.jpg

EDIT:

Here's a photo captured in FCamera - This is the automatic JPG exported image http://the-buccaneer.co.uk/image_edi...1279809705.jpg

And this is the same image but the DNG generated by FCamera as seen in Adobe Photoshop CS5 http://the-buccaneer.co.uk/image_edi...1279809766.jpg

I've got the exactlly same problem as yours mate, it's quite strange, ]http://the-buccaneer.co.uk/image_editor/images/Crugath/1279809766.jpg this one is same as what I've got for preview on my Mac through CameraRaw when I open the DNG with PS CS4

Quote & Reply |

The Following User Says Thank You to ericube For This Useful Post:
Switch_

Deaconclgi	2010-07-23 , 06:30
Posts: 337 \| Thanked: 192 times \| Joined on Feb 2010 @ Atlanta	#17

Here is a great article and video about the Fcam project.

http://www.physorg.com/news199011645.html

Quote & Reply |

The Following 3 Users Say Thank You to Deaconclgi For This Useful Post:
bergie, Petteri, ysss

	Switch_	2010-07-23 , 06:51
	Posts: 601 \| Thanked: 549 times \| Joined on Mar 2010 @ Redditch, UK	#18

Originally Posted by abadams

Found the bug. We were casting a possibly-negative floating point value to an unsigned integer, so the color matrices stored in the DNG files (required to correctly interpret the raw data) went well.... tits up, as switch puts it..

Awesome - thanks for digging into the problem so quickly - those damn negative floating point values and unsigned integers, always causing trouble of some description!

Apologies for the use of adjective too but when blessed with only a limited vocabulary and the eloquence of an ape, "tits up" is deemed to be a fair descriptor.....