OpenRAW - The 2006 RAW Survey Forum

Digital Cameras

chrisce0806 — Wed, 03 Jan 2007 03:13:09 +0900

Iam getting ready to purchase an Olympus Evolt E-500.....will the RAW files be compatible with this program.....and will I be able to create great pics with the files from this camera ......as you can tell, I am a novice at the Raw Image process but greatly look forward to working in this medium....comments will be greatly appreciated....

registration

rgb1945 — Fri, 28 Jul 2006 04:07:41 +0900

I would like to register raw shooters essential 2005. sayscan not access internet but here I am

Canon EOS 30D

Bertram — Sat, 29 Apr 2006 21:48:15 +0900

Jeg har købt et EOS 30D kan det passe at jeg ikke kan bruge RAW billeder fra dette kamera i RawShooter?? for det er ikke muligt hos mig eller er der noget jeg mangler? kan ikke læse dem.
den kan godt se billedet, men viser 1 billede som 4 sammen-satte billeder misfarvet??????
kan i hjælpe mig?????

mvh.

bertram lange

Suggestion for extra analysis

Barry Pearson — Sat, 29 Apr 2006 16:48:41 +0900

I have a suggestion for extra analysis of the survey results to give two pieces of information that can't be obtained directly from the report:

1. What proportion of surveyed photographers use software that doesn't support DNG, some / most / all of the time?

This would reveal the proportion of surveyed photographers who can't fully adopt a DNG-based workflow because of constraints in the tools they use.

2. How do attitudes to DNG correlate with "1" above?

This should show whether attitudes to DNG (for / against) are correlated with whether one's tools of choice support it. (I doubt if the survey could reveal cause & effect here, for example whether use of DNG dictates tool choice, or tool choice dictates attitude towards DNG).

Welcome to a new forum!

Juergen Specht — Tue, 25 Apr 2006 20:56:39 +0900

We look forward to read your feedback about the 2006 RAW Survey here!

API for abstraction of decoding raw files

John Valentine — Mon, 10 Apr 2006 20:24:39 +0900

Here's an idea I've put on the mailing list, and want to represent my idea here in a concise form, for opinions, and suggestions for a way forward if viable.

I propose that an API be written (primarily for image processing applications, and later for image readers and writers), that allows the embedding and use of processing methods within the raw file.

Features:

API and associated file format that allows embedding of plug-in VM byte-code (e.g. Java).
Methods embedded within a raw file can describe the associated raw data, without the application needing to know how to interpret the raw file.
Object-oriented approach, where the methods may also be overridden by applications, so that improved algorithms can be used in future, and the embedded algorithm is then regarded as a fallback.
The architecture is extensible, and may be periodically ratified.
Supporting standards may be created, both for source raw files, and for the version of API support. Thus, updated methods can be matched to files.
Locally enumerated and named embedded resource chunks, which may be accessed by the API.
Enumerated and named published embedded properties are optionally supported by implementors, which may be queried through the API. Initially, this will query the EXIF data elements, but may be expanded to query other locally-enumerated or named resources. Property implementation remains with the embedded code.