The DAM Forum
Welcome, Guest. Please login or register.
April 20, 2014, 06:58:50 AM

Login with username, password and session length
Search:     Advanced search
28003 Posts in 5130 Topics by 2912 Members
Latest Member: kbroch
* Home Help Search Login Register
  Show Posts
Pages: [1] 2 3 4
1  Software Discussions / Aperture / Re: Aperture 3 - Apple has been listening! on: February 10, 2010, 11:13:00 AM
In Aperture 3 I applied a star rating, then saved the metadata for that DNG out to a text file (right click on image, export > metadata).  The text file format appears to be a tab-del, for which Urgency is listed as 0, but there is a field named "Rating" which contains the star rating I applied.
2  Software Discussions / Aperture / Re: Aperture 3 - Apple has been listening! on: February 10, 2010, 10:30:06 AM
Something I noticed right away on import of a test set of files tagged using Lightroom 2.6 (and verified in Bridge that all metadata was saved to the files):  Aperture 3 doesn't recognize star ratings!

Per Apple, here's a mapping of various metadata fields across various applications, including Aperture 3: http://support.apple.com/kb/HT4028

No mention of star ratings (or colors).  Could this be a defective-by-design "feature" ?


Mike
3  Software Discussions / Lightroom / Re: Lighroom Produces DNG's 2x the Size of SRAW1 files for Canon 5D Mark II on: May 21, 2009, 10:42:18 AM
Thanks, Peter, for your pure semi-informed speculation.  It completely makes sense based on the results that I'm seeing.  I'm very surprised I haven't read more discussion about the Canon sRAW issues here or elsewhere.  Now I have a new mantra to be evangelical about:

Always shoot RAW (but don't use sRAW)

Do you mind if I quote you on my blog (mikewren.com) as speculative reasoning as to why the resulting DNG's from sRAW are as large as full-res RAW?  I'd really like to get the word out in the photog community that, like shooting JPG, shooting sRAW with Canon dSLR's is a recipe for later headaches, especially for those just starting out and don't know any better.
4  Software Discussions / Lightroom / Re: Lighroom Produces DNG's 2x the Size of SRAW1 files for Canon 5D Mark II on: May 13, 2009, 01:58:01 PM
I may have answered my own question:

http://forums.adobe.com/message/1800719#1800719

Quote
The sRaw format is not covered by the DNG specification. When converting, it must be changed; in fact, the amount of data needs to be increased by 50%.

Yuck!
5  Software Discussions / Lightroom / Lighroom Produces DNG's 2x the Size of SRAW1 files for Canon 5D Mark II on: May 13, 2009, 12:36:56 PM
So this afternoon I finally addressed something I have noticed when processing SRAW1 files from my Canon 5D Mark II.  SRAW1 files are being converted to a DNG file that is almost twice the size of the native CR2 (RAW) file in Lightroom v2.3.  This is a huge filespace premium to pay for maintaining my archive in DNG.  A quick search of Google turned up nadda.

Also annoying but minor, CR2 and DNG SRAW1 files display as an image with 0 x 0 resolution, and no preview image is displayed in Finder in MacOS v10.5.6

Here's the down and dirty:

Original Canon 5D Mark II SRAW1 .CR2 file: 10MB

DNG, no JPEG Preview, Preserve Raw Image, Uncompressed: 57.2MB
DNG, no JPEG Preview, Preserve Raw Image, Compressed: 18MB

DNG, no JPEG Preview, Convert to Linear Image, Uncompressed: 57.2MB
DNG, no JPEG Preview, Convert to Linear Image, Compressed: 24.9MB

DNG, no JPEG Preview, Preserve Raw Image, Uncompressed, Embed Original RAW file: 66.4

Anyone else experience this and know of a fix, other than to not to be stingy with my bits and shoot full res RAW?



Mike Wren
Albany, NY
http://mikewren.com
6  Software Discussions / iView MediaPro / Re: RAW files and keywords on: March 26, 2008, 08:45:21 PM
Good evening Eleanor,

What camera RAW format is your photographer shooting?  Have you considered converting to DNG earlier in your workflow to get around your metadata issue, despite the time involved with re-rendering DNG thumbnails?
7  Software Discussions / iView MediaPro / Re: iView 8.3 filename problem with Quicktime 7.4 on: March 26, 2008, 09:36:51 AM
Mike,
How many simultaneous users do you have, typically?
Peter


No more than three, but typically we would have two people working on our archive of 25k DNG and legacy JPG images.


Mike
8  Software Discussions / iView MediaPro / Re: iView 8.3 filename problem with Quicktime 7.4 on: March 21, 2008, 09:32:20 AM
Mike,
Have you looked at Expression?  Any issues for you?
Peter

We're holding off on upgrading to Expression (or any other 'next generation' DAM solution) until it supports read/write from multiple simultaneous users/workstations.  This summer I'll be investigating Portfolio.
9  Software Discussions / iView MediaPro / Re: iView 8.3 filename problem with Quicktime 7.4 on: March 18, 2008, 07:53:19 AM
In my experience, the latest version of QuickTime 7.4.1 does work correctly with iView 3.1.3 (as I mentioned in an earlier post on 28 February).

The filename problems mentioned by other posters may only apply to an earlier release of Quicktime 7.4.

Robert

Mac OS X 10.4.11,  QuickTime 7.4.1,  iView MediaPro Version 3.1.3 (Build 42E6)

Sorry, I should have been more specific.  I tried Quicktime version 7.4.1 and it caused the 8.3 filename issue with my iView 3.1.3 under Windows 2003 Server.

At this point, I starting to consider iView legacy software.  And with legacy software, upgrading dependancies can be a very bad thing.  Lesson learned.  Time to start shopping for another DAM solution.
10  Software Discussions / iView MediaPro / Re: iView 8.3 filename problem with Quicktime 7.4 on: March 17, 2008, 09:53:12 AM
I got caught up in this issue also.  Just what I wanted to deal with on a Monday morning. I should have known to check here before upgrading Quicktime.

My resolution was this:

Uninstall Quicktime 7.4, reboot, run the Quicktime v7.1.3 installer that was archived "just in case".  I just fired up IVMP and it appears that everything is OK and our catalog isn't corrupt.

Besides regular backups of our IVMP catalog, doing a weekly export/sync of metadata back to each file is part of our hedge against the worst case scenario, which I was really nervous about this morning.

I'm running iView Media Pro v3.1.1 on Windows Server 2003, which client workstations connect to via Remote Desktop.


Mike Wren
Albany, NY
11  Software Discussions / iView MediaPro / Date Created field not allowing input of dates earlier than 1904? on: December 19, 2007, 10:35:17 AM
While tagging some of the earliest images in our archives, iView v3.1.3 is not allowing me to set dates earlier than 1904.  For example, iView seems to be "correcting" the date 5/1/1903 to 5/1/2003.  Anything from 1904 and earlier seems to suffer the same fate.

However, if I add the correct date in Bridge CS3, then do a sync in iView, the correct date seems to be allowed by iView.

I did a quick search of the forum and couldn't find any mention of this.  Hopefully this helps someone out and saves a few hours of troubleshooting.


Update: Grrr... as soon as the correct date is imported/synced into iView, any metadata updates that are made to the file(s) in iView (such as changing the description field) will cause the date to jump to 2003 again.


Mike Wren
Albany, NY

12  General / General Discussion / Re: Forum Migration Soon - will be unavailable on: September 14, 2007, 08:05:03 AM
Very fast.  Was real slow before.

Mark

What Mark said; Great work!



Mike Wren
13  DAM Stuff / DNG / Re: How to verify the integrity of DNG files? on: August 31, 2007, 04:42:54 PM
Mike--

You can read all about IV here: http://basepath.com/ImageIngester/ivinfo.php.

It's a GUI program, not a command-line program. It writes its results to a log file.

--Marc

Any chance of being able to invoke IV via a DOS commandline, with some switches?   Grin

This would take care of the scheduling for Windows users (via Scheduled Tasks).
14  DAM Stuff / DNG / Re: How to verify the integrity of DNG files? on: August 17, 2007, 06:02:40 AM
Marc,

That sounds really snazzy! Is the checksum based on the just the RAW sensor data, or the entire DNG file (metadata and all).  Can IV be called via DOS commandline?  I'm really kind of tied to my nightly batch files.  I don't like having to check logs nightly, weekly, or even monthly.  For my backups, an email is sent notifying me of any warnings or errors.  I would like to apply the same kind of "set and forget" mentality to nightly/weekly DNG verify process.
15  DAM Stuff / DNG / Re: How to verify the integrity of DNG files? on: August 16, 2007, 01:36:22 PM
Peter,

While I agree with you in theory, my reality has been a loss of two weeks of metadata updates (50+ hours of work) due to database corruption in iView when I first approached the DAM game.  I was never able to figure out what caused the hiccup, but I've yet to have a DNG file be unusable due to corruption, network, disk or otherwise.  Then again, nor have I run into a database issue with iView.

As a bucket fills, we immediately burn it to DVD for our "bomb shelter" worst-case scenario.  The nightly backups are are pushed to a site across town to provide a little geographic redundancy.  We do weekly synch pushes with iView to keep the metadata in the DNG files fresh.

This configuration has worked flawlessly for almost two years.  Lightroom is currently not part of our workflow, just iView for metadata consistency and ACR hosted in Bridge for image tweaking.  I treat our entire collection as a work in progress  Smiley

A combination nightly DNG verification and full-sized JPG preview check/generation is very attractive, rather than waiting for ACR/Bridge to render previews, which when adjusting hundreds of files at once, can tie up a workstation for a while.

Again, in theory I agree with your approach 110%. I don't like touching the files every night either, but it's been perfect (knock on wood) for 125GB, 15000 DNG and TIFF files.


Mike
Pages: [1] 2 3 4
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!