The DAM Forum
Welcome, Guest. Please login or register.
May 22, 2018, 10:43:02 AM

Login with username, password and session length
Search:     Advanced search
28033 Posts in 5147 Topics by 2905 Members
Latest Member: kbroch
* Home Help Search Login Register
  Show Posts
Pages: [1] 2 3 ... 16
1  DAM Stuff / Scans and Camera Scans / Re: Adapters for Beseler Dual Mode Slide Duplicator on: December 28, 2012, 05:03:13 PM
For the camera... T mounts should be readily available.  I ordered one for Canon EOS a few months ago from B&H I think.  It's a Bower brand.  That screws onto the flange that fits into the bellows.  If you don't have that flange, that may be harder to source.  I seem to recall that B&H had quite a bit of T-mount items so maybe they have it all.  I would have assumed that part would come with the unit.  I have (and still use) one of these units that I purchased new in the mid eighties.  I know my unit came with those parts.  Even if you have to make something suitable, it really shouldn't be that difficult and could probably be accomplished with some epoxy and some other T-mount parts.

For the enlarging lens, I used epoxy to attach a Leica thread flange off of an enlarger to some odd lens mount part I had laying around the studio that fit into the bellows mount opening.  I looks like it might be another Nikon T-Mount part with the enlarging lens threaded piece glued to the front.  The Nikon bayonet end fits into the opening in the bellows and is held by the the set screws on the side that would normally grip a flange.  Been using it for years and it works quite well. 

Bob Smith
2  Software Discussions / Choosing Software/Other DAM Applications / Re: Chronosync - Bootable Backups on: May 29, 2012, 11:46:39 AM
I've had good experience with Chronosync bootable backups.  I think the point is to test your backup... no matter what method was used to produce it.  I've seen many examples where people think they've been making great backups.  Until they try to actually use one.  The time to find out that there may be a problem is BEFORE you're in a panic and truly need it.  That's especially true if you expect to boot from your backup.  I think the instructions not to launch apps is just to keep you from modifying various app preference files.  Those files may now have a newer creation date (and possibly altered settings from running on a different drive) than corresponding files on the original drive... and cause errors if you're doing further incremental backups of that drive to this same disk.  By all means test your apps with your backup method (Chronosync or otherwise) but you may also want a separate backup by the same method that is completely undisturbed.

Bob Smith
3  DAM Stuff / Loss and Recovery / Re: Photoshop for photographers on: March 27, 2012, 06:12:36 PM
landscape photography often requires blending of images for panos, simply higher res, or HDR.  You need a third party app to do that from Lightroom.  Working with Photoshop makes those operations particularly easy.  I suppose Elements could do this in a similar way but I don't know that for fact.  I love Lightroom but I still prefer Photoshop for more subtle and critical editing tasks.  Not every image needs that but those that do, get a trip to Photoshop.  How valuable Photoshop might be depends largely on your working style and imaging tastes.  I couldn't do without it.

Bob Smith
4  Software Discussions / Lightroom / Re: Color Settings help on: November 15, 2011, 07:26:29 AM
For the simplest, least likely to cause problems workflow, keep Photoshop and Lightroom set to the same workspace.  That sounds like what you've done.  I keep both apps on Adobe RGB myself. 

Monitor calibration should be auto set by your calibration software and Photoshop and Lightroom will automatically display everything with that calibration.  Nothing special to custom set.

You lab's recommendation would most likely only come into play when you create a delivery copy of an image for them.  You can create a custom set of export settings in Lightroom that saves out files exactly to your lab's specs including color space.  Even if you have a pile of layered PSD files in Adobe RGB, Lightroom can quickly export a copy of sRGB jpegs at a specific size if that's what your lab wants.

Bob Smith
5  Software Discussions / Aperture / Re: Exporting Ratings to DNG on: October 11, 2011, 12:24:54 PM
I switched from Expression Media to Lightroom a few versions back.  I think this is still true but not positive.  I seem to recall that Expression Media used the "priority" or "urgency" field to record ratings.  I could select all two star images for example in Bridge and set the priority field to the proper number (two?) and then ratings would show in Expression Media.  (Maybe I'm confusing labels and ratings?  Its been a while.  I know EM used "Priority" for one of them)

Experiment with that idea and I think you'll find your answer.

Bob Smith
6  Software Discussions / Lightroom / Re: Corrupt previews interrupting optimisation on: October 09, 2011, 04:43:37 AM
I edit on a 1920x1200 NEC monitor and I have the 1:1 preview settings set to 2048, high quality.

I don't have a definitive answer but am curious about responses as my catalog is similar to yours but running on much lesser hardware. 

One point of clarification though... the above settings are for STANDARD previews, not 1:1.  1:1 previews are created based on the actual pixels in the image file.  The preview is the exact same pixel count size as the actual image.  Making 1:1 previews speeds moving between images in the Library but it doesn't help in the Develop module (which is where I feel I really need something like that).  You may be needlessly creating 1:1 previews and that in turn may be seriously bogging down overall catalog performance.  Creating standard previews and moving the quality setting down a notch or two would probably dramatically improve your catalog performance while causing little, if any, issue in terms of evaluating images.  Your preview file would still be large but much more manageable in size.  My catalog contains about 170k images.  Most of my previews are 1440 medium quality versions.  My previews file is about 60GB.

Bob Smith
7  General / General Discussion / Re: File Sorting Problem in OS X on: October 05, 2011, 10:19:59 AM
Your first example is as expected when sorting by file name.  Think of it as alphabetizing rather than sorting by number.  It sorts by the first character in the name, then moves to the second, then the third and so on.  If you want numbers to sort correctly then each filename must have the same number of characters in the name.

I'm guessing that in your other examples you possibly had mistakenly set to sort by some field other than file name?

Bob Smith
8  Software Discussions / Choosing Software/Other DAM Applications / Re: DAM Catalog Software Choice for 10k image archive on: October 04, 2011, 03:02:12 PM
I moved from Expression Media to Lightroom a little over a year ago.  v3 of Lightroom was the tipping point for me.  I've been very pleased with the transition and feel like I finally have a really solid DAM workflow.  I miss a few things from EM but I'm extremely happy to be able to have just one catalog (currently about 180k images).  It makes it easy to find/sort anything quickly without having to deal with multiple catalogs.  I'm also extremely fond of its print module.  I do a lot of custom printing to a variety of wide format Epsons.  Once a library of suitable presets is built up, it takes just a few mouse clicks to find a "print master" version of an image... and output it at a variety of sizes on an assortment of media if desired.

The most annoying aspect of Lightroom is its lack of a really wide variety of document format support.  That gets better with every version and will surely continue to do so.  I'm managing a library of mainly photographs but I sure would like to at least see the presence of support docs or odd image formats that happened to be stored along side of a particular batch of otherwise "common" image files.

Bob Smith
9  DAM Stuff / Naming Issues / Re: Including date in filenames on: August 31, 2011, 06:17:47 PM
I switched (after reading the first DAM Book) to yymmdd-####.  I've been using that about six years now.  It's working very well.  I never have a duplicate file name unless its a different version of the same image.  Even in Finder or Window Explorer the default sort order using filename yields a list of images always in chronological order.  A "new" derivative will appear properly sorted next to "originals" created years earlier when using the same simple default sort.  File names are short.  They almost always are fully readable in just about any view in any software.

Bob Smith
10  Software Discussions / Lightroom / Re: Creating different catalogues on: May 16, 2011, 10:17:15 AM
I make collections as I need them... but I never trash them.  I just expand or refine them as needed in the future.  I'll typically make a collection the first time I need to access something from a particular job/client that's old enough to not be readily accessible in my "Working" folder.

I tend to make collections like this.  First I make a collection set for Acme client.  Then I make a really broad smart collection intended to find anything I've ever done for Acme client.  I do that by look for either Acme as a keyword OR "Acme" contained in the folder name.  On things that haven't been keyworded they're almost always in a folder somewhere in the directory structure that includes the clients name.  That smart collection finds loads of things, most of which will be images made for Acme.  From there I filter down to whatever I need and put those in other collection in the Acme set.  I'll also add more keywords and ratings if that might help future searches if need be.  Maybe a collection of Masters; or a collection of Acme DNGs... whatever is most useful for what I'm currently looking for.  If I come back months later and need other Acme files I may make other collections to put under the Acme collections set, but I'll use those existing collections to help build those.

Bob Smith
11  Software Discussions / Lightroom / Re: Verifying file integrity from Lightroom 3 on: April 24, 2011, 12:58:00 PM
I believe you could export a temporary set of DNG files (make a new DNG from your existing DNG... or other file).  That process will usually kick up an error if there's something wrong with the original file.  I believe Peter has suggested this before.  And this method of converting to DNG is a large part of what makes ImageVerifyer work.  If the new DNGs are successfully exported you have a good set of original files.  If any kick out an error, they are most likely corrupt.  If your originals are all fine, just toss the temp set of DNGs.

Bob Smith
12  Workflow Discussions / Tethered Shooting / Re: Tethered shooting file renaming problem in LR3 from a Canon 5D on: April 16, 2011, 06:57:40 PM
I agree with Canon.  I shoot tethered into Lightroom but prefer using EOS Utility to make the connection.  I shoot primarily with a 5dII now... but still have a 5D though its used much less now.

I'm not sure how I see that the EOS Utility changes the workflow in a significant way.  It gives you more control over the camera and more reliable constant camera connections in heavy shooting situations (granted I haven't tried Lightrooms native tethering again since it's early inception... maybe it's improved).  With EOS Utility you shoot into specific folder that is set as Lightoom's "watched" folder.  When Lightroom detects a new image it's immediately imported as per your instructions in Auto Import setup.  You tell it what folder to go into, what metadata to add, what initial develop settings to apply and how to rename.  If you shoot into Loupe View each new frame is displayed as the active image.  The extra import step adds maybe two seconds before the image pops up on screen versus shooting into Bridge or the Canon software that doesn't need to move the file before display.  How is any of this functionally different to letting Lightroom control the tether... as far as workflow goes?

I can't recall the exact setting... don't have camera and software in front of me... but what worked best was to tell EOS Utility to custom name the files yymmdd-####(my usual naming pattern).  The problem is that the #### part will start over at one each time without the right setting.  There's no way to get it to match what the camera is doing with cards natively.  However if you choose the proper setting it will remember where it left off at the last session and continue on with the next (won't reset to 1 again after each shoot).  Tethered shooting gives me one sequence of image numbers.  Shooting to cards gives me a different one.  That hasn't proved to be any sort of problem for me.  You can make the sequence number four digits long.

Bob Smith
13  DAM Stuff / Backup Strategies and Tools / Re: Chronosync + Folder Structure on: March 18, 2011, 08:29:38 AM
If the folder doesn't exist on the destination, you need to create it before doing the sync.  You can create it during the process of selecting the destination if you use the dialog to find the destination as opposed to dragging and dropping.  Note, using this method the target folder doesn't have to have the same name as the source (though you'd usually probably want it to).  What is being synced is the contents of that folder, not the folder itself.

Alternately you can sync one directory level above the folder you want to sync.  In the analyze tab can select everything except the folder you want to sync and "exclude" the selected items.  That will create the folder you want on the target drive as the sync is done if it doesn't already exist.

Bob Smith
14  General / General Discussion / Re: File Syncing Software Delete Bug on: February 12, 2011, 01:14:19 PM
I work on Macs and use Chronosync extensively to do exactly what you are trying to do (been doing it for years).  Works like a charm... and from all I've heard about Syncback it should too.

One point that I'm not really clear on is about your workflow description and where you "run the profile".  If I'm trying to do what you're describing I always run the sync operation from the same computer.  Even if the work I've done is on station B, I run the sync from station A if that's where I setup and defined the sync.  When running the sync operation data is collected and stored on the computer running the sync about what both sides looked like after the sync.  That info is used as the basis for determining what gets synced (what gets deleted or copied) the next time it's run.  If you run a sync from one machine one time and then from the other the next time you'll get results like you describe because the second machine has no idea what the state of both machines was at the point in time of the last sync.  The second machine doesn't know that you deleted files from it because it has no record of what was there at the last sync.  It sees files on the other computer that it hasn't seen before and your deleted files get replaced.

I hope that sort of makes sense.  I'm not sure if that's your problem or not but it sounds from your description of your workflow that it might be.

Bob Smith
15  Software Discussions / Lightroom / Re: Lightroom catalogs: Archive & Working on: February 06, 2011, 01:07:36 PM
I use a "Working" folder in which I keep work in progress.  The point is that there is one folder that contains all of this often changing data.  That one folder is backed up often to numerous different places.  I work primarily on a laptop that travels with me.  The working folder resides on that laptop and is then mirrored to other drives whenever I'm in the studio; or to portable externals if traveling.  That same "Working" folder is where my lightroom catalog itself exists too. 

I suscribe the advantages of having a few catalogs as necessary.  I currently work with one large Lightroom catalog.  The working folder is just one more "Folder" in that catalog.  I don't think you'd want "Working" as any sort of collection as that would imply that it's contents are scattered in different locations.  The point of keeping "Working" together in one place is to make it easy to backup and transport.  Once it's convenient to do so, files in "Working" are moved into buckets on my server as per DAM Book guidelines for raw and derivatives.  Since those folders are also in the same Lightroom catalog, moving and keeping track of the images is simple.

I use collections to keep track of something like all images for a particular client... though they may be scattered amongst "Working" subfolders and numerous different buckets all at once (some images "in progress" and some archived months or years ago).

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