The DAM Forum
Welcome, Guest. Please login or register.
April 24, 2018, 07:56:08 PM

Login with username, password and session length
Search:     Advanced search
28033 Posts in 5147 Topics by 2906 Members
Latest Member: kbroch
* Home Help Search Login Register
  Show Posts
Pages: [1] 2
1  Software Discussions / Media Pro & Expression Media / Re: iView -> EM -> and Now Media Pro! on: May 11, 2011, 06:30:06 AM
Hmm. It's a welcome step forward but I've had some stability issues already. On a MacBook Pro running 10.6.7, I'm seeing the background metadata importer thread crash repeatedly. Not on every file but enough to make me very, very cautious about doing much more with it until I know what's going on. I've filed a support request with PhaseOne so we'll see if the customer support has improved.




2  Software Discussions / Media Pro & Expression Media / Re: EM2 - Synch Annotations Between Catalogs? on: January 07, 2009, 08:48:25 AM
I currently use Iview, but thinking about now buying the updated Expression Media2.  As described in the DAM book, I keep one archive of all my "master" raw files, and a separate archive with derivative files (PDS, TIFF, JPG).  I use the the MetaSync application with Iview to "copy" or synchronize annotations, metadata, etc. between my two archives.  Can anyone tell me if EM2 provides for this capability, or, alternatively, will MetaSync work with EM2?

Funny you should ask this! I've just updated MetaSync to work with EM2 and posted it for download. The version that works with both MediaPro 3 and EM2 is 1.5.4. You can download it here



3  Software Discussions / Aperture / Re: Aperture Library on the GO on: February 17, 2008, 12:13:50 PM
There's no syncing function, but you can get by with exporting/importing Projects from one machine to another and deleting the old copies of the Projects. Just make sure you are using referenced Masters or the Project files sizes will be absurd

This approach is a lot more feasible with Aperture 2.0 - they added the ability to force the reconnection of referenced masters. When you move projects between machines like this, you'll need to reconnect the masters to their new location on disk. The gotcha with the 1.5.X release of Aperture was that it wouldn't always reconnect - it often found "differences" between the masters when none existed.

In 2.0, you can hold down the option key and force the reconnection to the files that you know are the same.


4  Software Discussions / Aperture / Re: Aperture won't reconnect some files on: April 21, 2007, 09:46:15 AM
I just tried 1.5.3 in the hope that they'd managed to fix this problem. Sadly, altho' they've listed improvements to the reconnect logic in the fixed bugs for 1.5.3, Aperture doesn't seem to be any better behaved when reconnecting images that have been edited in an external editor. I guess I need to refile the bug with Apple...


5  Software Discussions / Lightroom / Re: Updating Lightroom Images on: February 19, 2007, 02:09:07 PM
works perfectly - thanks

You're welcome - it took me a moment today to work out how to do this myself as I'd forgotten to sync my recent iView catalog changes to my DNG files and wanted to know how to update Lightroom. The Lightroom documentation is a little obtuse in this area but it does work.


6  Software Discussions / Lightroom / Re: Updating Lightroom Images on: February 19, 2007, 01:53:04 PM
Still in the throes of changing some metadata outside Lightroom.  Other than deleting and re-importing (what a pain) I have not found a way of rebuilding.

If you're working with images with embedded XMP metadata (i.e. DNG, TIFF, etc) or with raw images with sidecars, there is a way to force Lightroom to pull in the metadata again from disk. Simply select the files you want to update in the Library view and then use the

   Metadata->XMP->Import XMP Metadata From File

menu option. This pulls in the info from the file again. If you have Lightroom set to use external XMP metadata (in the preferences) rather than the Lightroom database, you'll get a small exclamation mark on the thumbnail when the file changes on disk behind Lightroom's back. Click on the exclamation mark and it'll prompt you for what to do next. The import XMP trick works if you have a lot of changes too.

7  Software Discussions / Aperture / Aperture won't reconnect some files on: January 19, 2007, 09:09:02 AM
At the moment, I'm trying to run Aperture and iView MediaPro/ACR/Photoshop in parallel to get some experience with Aperture to see if it's something I want to migrate to. Obviously, I'm running Aperture with referenced files into my primary image archive.

Last night I ran across something that I figured I'd share with folks as it's a pretty serious bug for folks trying to do this. Due to some remote work, I often have to reconnect images from one drive to another - no big deal, the drives all have the same basic structure so it's just a matter of picking one file in the heirarchy and hitting "Reconnect All" in the dialog box.

Unfortunately, there's a problem here.

The Aperture logic for reconnecting files seems to expect the files to be *exactly* the same as they were when they were originally imported. This would match Apple's approach to dealing with raw files. Oops. I had a bunch of DNG files that I reworked in ACR4 and updated in my archive. I also had a couple of TIFFs that I reworked, recropped and resaved. All of these files refuse to reconnect in Aperture. This is pretty frustrating as I *know* the files are the same but they're failing some silent, internal Aperture check that makes them eligible to be reconnected. As far as I can tell, its being keyed on either image size or file size but it's fairly frustrating all the same.

I'm going to try a few experiments over the weekend to see if I can work out what the exact trigger is but I figured I'd mention it here in case someone runs into the same thing.

Oh, I'll be filing it as a bug too...
8  Software Discussions / Aperture / Re: Moving referenced files on: January 19, 2007, 08:58:40 AM
Joe Schorr talked about this on one of the inside aperture podcasts. You can even rename the files and it will find them. It will loose track if you move the images to another volume. I think this was mentioned in part 2 of the first two podcasts.

Well, like all well-intentioned plans, I found a gotcha. The problem here is if you try to point the references to another disk with identical structure to the new arrangement (like a backup or "on-the-road" external copy). Aperture goes looking for the files in the *old* directory locations, not the new ones. Which means a whole load of work to match 'em back up again.

Apparently, Aperture doesn't update the internal reference to the new locations of the files when it plays this tracking trick, which sounds like a bug to me.

Something to be aware of...

9  Software Discussions / Aperture / Re: Moving referenced files on: January 08, 2007, 06:12:16 AM
Isn't that simply what you'd expect from the operating system? I'm relatively new to the Mac (OK I briefly used one c 1989) but I thought you could move and rename files and the OS helped track them.

Yeah, you'd think so, wouldn't you.  Wink The problem is that not everyone plays by the rules for tracking files when writing applications. Whether this works or not is an application-specific thing rather than always coming for free via the OS. I've come across quite a few programs in the past that track paths and not file references. This, of course, goes horribly wrong when a file moves. Now, you'd expect Apple to get this right but I've been burned enough times to be surprised when it works correctly...

It would be interesting to know what would happen if you used another computer to move those files - say if they were held on an external drive that you attached to that other machine. When you then connect the drive back to your Aperture machine, I'm pretty sure that it would pick up where they now are. Have fun....

I suspect it'd work just fine - the references are driven as part of the file system so it should work, regardless of the system used to drive the change...


10  Software Discussions / Aperture / Moving referenced files on: January 08, 2007, 04:44:44 AM
This is just a quick hint for folks using Aperture to manage media by reference.

I just got finished cleaning up and regularizing the directory heirarchy for all of my derivative image files - I'd been lazy before and some smaller projects didn't have the heirarchical bells and whistles that the larger ones did. Now they're all the same and I'd resigned myself to an afternoon of trying to rematch the references in Aperture with the new media locations.

However, I just got a pleasant surprise. Aperture obviously tracks the file references, not the paths to them so if you *move* a referenced file to a new directory, it seems to keep track of it correctly. I haven't tested out the bounds of this support yet but it could be very useful for those of us who sometimes decide to tweak our directory heirarchies.

YMMV, but it definitely saved me an afternoon of grunt work.

11  Software Discussions / Aperture / Re: Managing derivates with Aperture on: December 27, 2006, 10:29:57 AM
It would also be noce if Aperture allowed the user to make some use of the embedded preview in the DNG file.


Yup - Aperture's DNG is definitely a bit awkward at the moment. Given Apple's philosophy about not touching masters for any reason at all, I guess I'm not confident of them eventually doing a DNG update with a freshly rendered preview. It's going to be hard enough to see 'em rewrite metadata in a DNG header.


That said, I find Aperture much less clunky to use as a general image navigator than Lightroom at the moment. Whilst I could really use the (promised) tighter integration between ACR and Lightroom conversions (and it looks like they're nudging the ACR4 basic parameters towards Lightroom), I'm just not that excited about the Lightroom interface. I guess I'll need to check it out again at the 1.X release...


12  Software Discussions / Bridge/ Camera Raw / Re: ACR 4 / Bridge 2 Ready for Use? on: December 27, 2006, 07:24:07 AM
What do you folks think about using ACR 4 and Bridge 2 for everyday work right now? Is it safe?

It works relatively well altho' I've had a few bad crashes in Bridge2 working in ACR. All of the crashes came when trying to change crops on a previously cropped image. I've changed my usual default method of working on a rough first pass to doing the adjustments required, closing ACR to checkpoint the changes and then doing the crop/rotation work on a separate pass.

13  Software Discussions / Aperture / Re: Managing derivates with Aperture on: December 27, 2006, 04:14:41 AM
I've been playing with Aperture 1.5 to see whether it's ready to replace iView as my main day-to-day DAM navigator. I've been using ACR for the past few years for raw conversions and convert all of my raw images into DNGs.

I've got parallel directory heirarchies for my raw, DNG and TIFF derivatives. My raw archives are usually left alone and are only for backup. At the moment, I've imported my DNG and TIFF archives into Aperture, leaving them managed "in-place" rather than using the Aperture database to store them. I also use Annoture to pull all my metadata across into Aperture from iView. I import my portfolio images as "rolls", usually with a couple of hundred images in a roll. Each roll is arranged as a project and the DNG and TIFF images for a roll are in the same project. Note that you *have* to arrange them this way if you want to stack them - Aperture won't stack images outside of a project.

My DNG and TIFF images are stacked, with any TIFF image at the top of a stack. This way, I can do quick and dirty conversions in Aperture for selects and "upgrade" them with TIFF images worked in Photoshop if need be.

There's a couple of niggles with Aperture tho' that I think would make it unpleasant if you tried to pull in a load of derivative images and stack them. The principle one is that the stack arrangement is not scriptable in Applescript. That's not helpful at all and some scripting interface here would make life a *lot* simpler. If you automatically stack DNG and TIFF files, the TIFF files go to the bottom of the stack (thanks to alphabetical order, I think). A trick if you're stacking by hand is to select the top of the stack first before selecting the images below it - Aperture always puts the first selected image on top (i.e. I always select the TIFF image first).

Aperture is close to what I want but it's not quite there yet. If it imported metadata from DNG files and allowed DNG exports, I'd use it all the time. As it is, I use it to navigate around my archives, run slideshows and provide JPEGs for web and presentation use.

14  Software Discussions / iView MediaPro / Re: iView loads DNG's slowly on: April 12, 2006, 09:26:30 AM
are there any iview settings for rendering, or raw handling that can speed this up a little?

Sounds like you're not using the embedded previews to view the DNG. If you go into Preferences->Media Rendering and click on the Raw tab, you'll see a checkbox for "Use Embedded Preview". This will show you the embedded JPG in the DNG (which is usually more accurate anyway, as it's been generated using the embedded raw settings).

15  Software Discussions / iView MediaPro / Re: DNG converting after iView import and catalog? on: March 29, 2006, 04:55:39 PM
when should we be looking for the 2.0 release?


I've started work on the release so I expect it should be ready in a week or two.

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