Bridge Workflow

I'm trying to come up with a sort of action to run on files that can be used prior to archiving. One script that I have installed in Bridge currently is called "Write Filename to IPTC Title Field" and that needs to be utilized as well.
So basically the workflow would go as follows.
1. Append Metadata
2. Write Filename to IPTC Title Field
3. Build and Export Cache
It doesn't need to be in that exact order, in fact if someone suggests a specific order I'm open.
Any help on this subject would be great!
Thank you

If I am reading you correcty you could save them as a collection.
Then clicking on that collection would bring all the photos
up from the various locations.

Similar Messages

  • IPhoto and Adobe Bridge Workflow

    I finally picked up Photoshop CS3 and am curious as to the best method of integrating the applications in the most effective manner.
    I do like iPhoto, and I've used it extensively for some time now, but I wonder if it's better suited as simply a program to show and share my completed photos.
    Would it be best to use Bridge to organize and work with the photos directly out of my camera (including RAW files) and then merely use iPhoto as the last means of displaying them?
    It should be noted that the only Adobe application I use is Photoshop, so there is no need for thorough integration with other Adobe products.
    I suppose I'm curious as to how people might make use of Photoshop, Bridge and iPhoto in the most useful way possible.
    Thanks in advance.

    Using Photoshop (or Photoshop Elements) as Your Editor of Choice in iPhoto.
    1 - select Photoshop as your editor of choice in iPhoto's General Preference Section's under the "Edit photo:" menu.
    2 - double click on the thumbnail in iPhoto to open it in Photoshop. When you're finished editing click on the Save button. If you immediately get the JPEG Options window make your selection (Baseline standard seems to be the most compatible jpeg format) and click on the OK button. Your done.
    3 - however, if you get the navigation window that indicates that PS wants to save it as a PS formatted file. You'll need to either select JPEG from the menu and save (top image) or click on the desktop in the Navigation window (bottom image) and save it to the desktop for importing as a new photo.
    This method will let iPhoto know that the photo has been editied and will update the thumbnail file to reflect the edit..
    NOTE: With Photoshop Elements 6 the Saving File preferences should be configured: "On First Save: Save Over Current File". Also I suggest the Maximize PSD File Compatabilty be set to Always.
    If you want to use both iPhoto's editing mode and PS without having to go back and forth to the Preference pane, once you've selected PS as your editor of choice, reset the Preferences back to "Open in main window". That will let you either edit in iPhoto (double click on the thumbnail) or in PS (Control-click on the thumbnail and seledt "Edit in external editor" in the Contextual menu). This way you get the best of both worlds
    2 - double click on the thumbnail in iPhoto to open it in Photoshop. When you're finished editing click on the Save button. If you immediately get the JPEG Options window make your selection (Baseline standard seems to be the most compatible jpeg format) and click on the OK button. Your done.
    3 - however, if you get the navigation window that indicates that PS wants to save it as a PS formatted file. You'll need to either select JPEG from the menu and save (top image) or click on the desktop in the Navigation window (bottom image) and save it to the desktop for importing as a new photo.
    This method will let iPhoto know that the photo has been editied and will update the thumbnail file to reflect the edit..
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Okay, How do I Duplicate my Bridge Workflow?

    I shoot a Nikon D200. When I return to my studio, I import the files from my CF cards and convert to DNG in the process. The LR import does this well, so I can replace my Bridge import with LR.
    I then select the photos that I want to keep and adjust them in ACR. LR has that built in, so I'm good there, too.
    But...
    At this point, I typically use the "Image Processor" to create a new directory of those images, taken to PSD, and run an action on them that creates a number of custom adjustment layers. I then go into Photoshop and edit those images. I don't see how to do this in LR.
    Sure, I can edit them one-by-one in Photoshop, but that's rather time consuming.
    Is there a way to have LR batch process my selected DNG files into a new directory as PSD so I can then edit them for retouching and then move to the printing or web phase?

    I think you can go either way, if you want to make the target folder your watched folder. However, normally I think you may have to reimport but I don't know for sure.

  • Bridge CC lost all Plugins incl. Photoshop Scripts after uninstalling Photoshop CC.

    Reinstallation of Bridge CC brings no solution. It is the same Probleme like in this Post: https://forums.adobe.com/thread/1502288
    Also Capture One Pro 7 cant use his Scripts for Merge Images in Photoshop CC 2014.
    Please let me know when the bug is fixed... and when a new Process 2014 and Bridge version ist available.
    The quality in the sharpeness in the processversion 2012 is realy bad in Lightroom and Bridge in the current version (Canon 5D II and 5D III).
    It looks like a unsharp mask filter and not a real RAW sharpening. I think this is the most important feature!
    a lot of guys from our fototeam switched to COP7 because the quality. me to, but i like the bridge workflow and the interaction with some other programs and plugins.
    At the moment we use Bridge or Lightroom not as RAW converter. It is more a file manager.

    OK, it works after new installation vom Photoshop CC (previous version).
    now i wait for Bridge CC 2014 with an awesome RAW sharpening feature and better skin tones :-)

  • Watch out for timestamp differences, will produce Bridge / xmp problems!

    Hi all,
    Setup: CS5, Win 7 32b, Canon EOS600D.
    I forgot to change the camera's internal date/time from
    summer time to winter time. Because of this, Bridge
    would not accept and show changes made in ACR
    (not until one hour had passed!).
    It turned out that what timestamp a photo will receive
    depends on if you download the photo using
    Bridge / Photo Downloader or EOS Utility:
    Computer time: 14:31.
    Camera time: 15.25.
    Time stamps from Bridge download:
    created 14:31, modified 15:25, taken 15.25
    Time stamps from EOS Utility download:
    created 15:25, modified 14:31, taken 15:25.
    Using the workflow Bridge -> Photo Downloader.
    Bridge -> ACR | make a crop | click Done
    -> Back to Bridge, the Bridge thumbnail would not
    show the cropped photo, just the original, uncropped one.
    Using the workflow EOS Utility  -> Fetch ->
    Bridge -> ACR | make a crop | click Done
    -> Back to Bridge, the Bridge thumbnail will show the
    cropped photo as intended.
    Since the Bridge workflow had a modified time that was
    one hour ahead, it would take one hour before
    any ACR changes would be reflected in any
    Bridge thumbnail.
    So: which time stamp is "correct"?
    The created/modified from EOS Utility
    or the modified/created from Bridge download?
    The one which makes me able to see ACR changes in
    Bridge thumbnails at once, of course -- i.e. in my opinion,
    EOS Utility behaves correctly.
    Or are there any differing opinions?

    In Bridge, "Date Created" is the date the Photograph was taken: i.e the date recorded by your camera and stored within the file. "Date File Created" is the date when you created the file on disc, that is the date/time when you downloaded the picture from your camera.
    So when the date the picture is modified is an hour before the time the picture was taken I can see the confusion in Bridge.  Just looking at it as numbers, it is not possible to change something that has not been created yet.  That is what Bridge is saying.

  • Exploring and Exploiting the Bridge Libraries

    One of the things we did when we developed the Bridge Workflow Automation Scripts, was create a set of libraries to make bridge scripting easier and more productive.
    The libraries are AdobeLibrary1.jsx and AdobeLibrary2.jsx. There is an AdobeLibrary3.jsx, but it's primarily patches for the other two.
    Over the next few weeks, I am going to post some messages about those libraries to help get folks started bridge scripting.
    First up are some file handling utilities.
    getBridgeThumbnails and getBridgeFiles are two library functions that return the selected (in Bridge) Thumbnail objects or File objects. getBridgeFiles takes the output from getBridgeThumbnails and converts them to File objects. These functions also ensure that any Version Cue files that were selected are up to date on the local file system prior to returning the selected objects.
    The definition is:
    getBridgeThumbnails = function( mask, getFolderChildren, filesOnly, firstOnly )
    Where:
    mask is a comma delimited list of file extensions or Mac file type strings. The function will only return Thumbnails that point to files of these types. It defaults to no mask, which will return everything. If the user selected Thumbnails that are not included in the mask, the user will be warned by an alert dialog (the user has the ability to opt not to be warned again).
    getFolderChildren is a boolean. Set to true, it will return the first level children of any selected folder. The concept is that if a user selects a folder in bridge, they can operate the files in that folder. It defaults to true.
    filesOnly is a boolean. Set to true, it will return only files, no folders. It defaults to false.
    firstOnly is a boolean. Set to true, it returns only the first valid file found. This is useful when you are attempting to do an example of the result of one of the selected files. It defaults to false.
    One more thing: If the user has a document open in bridge, but has not selected anything, it will assume the entire contents of the document are desired. It will flip up a warning dialog if this is the case (the user can opt to not be warned again).
    We also extended the File Object in bridge (not the point apps) to do the file filtering for us. Part of that was the creation of a number of standard masks.
    TYPES.PHOTOSHOP
    TYPES.PHOTOSHOP_OPENABLE
    etc.
    var thumbs = getBridgeThumbnails( TYPES.PHOTOSHOP_OPENABLE, true, true );
    for ( var i = 0; i < thumbs.length; i++ ) {
    thumb = thumbs[ i ];
    // do something with the selected thumbnail

    John,
    Thanks.
    I'll try to get some basic examples up here too. I think the docs on Exchange were replaced with a non-read only set. Try downloading them again.
    Next Topic: The basic Bridge Scripting Paradigm
    Bridge being what it is, the typical usage of a script is to select a set of files, then select a menu item to perform some magic on the selected files.
    Scripts, therefore, typically need to create a MenuElement at startup, and then wait patiently for the user to call them.
    There are 2 ways scripts get loaded. The first is by placing them in the startup scripts folder. The best way to find the startup scripts folder is to click the button in Preferences.
    The other way is via Adobe ScriptManager. Script Manager is shipped with the full Creative Suite. It does what it says, pretty much. Provides a way to control what scripts load at startup and what don't. With ScriptManager installed (in startup scripts), it automatically loads scripts in the Workflow Automation Scritps folder (child of startup scripts for the full CS2 installation) and one other folder that is settable by the user.
    The Script Manager also has some nice to have features for scripters. When a user selects a script, the Script Manager displays information provided by the scripter. The information includes stuff like the script's name, description, help, author, website, etc. As a scripter, you should always write your scripts assuming the Script Manager is present and loading your script.
    To do this, the minimum script template is:
    // first is a target directive - tells the extendscript engine that
    // this script should be loaded into bridge. Makes it so that if a
    // user opens the script in Bridge, it will load it rather than
    // display the raw script in the ESTK
    #target bridge
    // next - all point products attempt to load all scripts in the
    // startup scripts folder, if your's is bridge-only, make sure it
    // only loads in bridge by wrapping everything in a condition like
    // this
    if ( BridgeTalk.appName == "bridge" ) {
    // always make a namespace object for your script. Make it something
    // that will not likely be something someone else might use. This
    // avoids possible name collisions between scripts
    myScript = {}; // namespace object for this script
    // next ditty is for the Script Manager
    try {
    myScript.scriptInfo = new ScriptManager.ScriptInfo();
    myScript.scriptInfo.set( "name", "My Script" );
    myScript.scriptInfo.set( "description", "A Cool Script" );
    myScript.scriptInfo.set( "help", "Help text" );
    myScript.scriptInfo.set( "author", "Your Name" );
    myScript.scriptInfo.set( "company", "Your Company" );
    myScript.scriptInfo.set( "copyright", "It's mine and you can't have it );
    myScript.scriptInfo.set( "version", "1.0" );
    myScript.scriptInfo.set( "date", "06-27-2005" );
    myScript.scriptInfo.set( "website", "http://www.adobe.com" );
    } catch ( e ) {
    // Your Script Goes HERE.
    myScript.ui = function( menu ) {
    // this function puts up any UI your script needs, then executes
    // the script
    // create your menu
    var menu = MenuElement.create( "command", "My Menu", "at the end of Tools", "tools/myScript" );
    menu.onSelect = myScript.ui;
    // the last thing for the Script Manager - after your script has
    // loaded, send the script info object to it.
    try {
    ScriptManager.reportLoading( myScript.scriptInfo );
    } catch ( e ) {
    } // closing brace for the if (appName == bridge) condition

  • Hiding subfolder content in folders - HELP

    Hi All,
    Does anyone have any idea how subfolder content can be hidden when looking at material in a folder?
    I am coming from Bridge workflow and have hundreds of folders that have the RAW files in the root directory, with sub-directories for PSD, JPEG, SRGB JPEG, WEB and whatever else I might need for that job.
    Whenever I click on a folder, the window displays ALL the files including the ones in the sub-directoy when all I want to see are the original RAW files.
    Thanks in advance,
    Tim

    People have suggested various, like color label the RAWs only one color and filter for them. Other such combos you shuld now be able to figure out.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

  • Fireworks Limitations for Photoshop Users

    This little bit of reading might be of interest to those more accustomed to the interactivity that used to exist between Photoshop and Image Ready.  This comes directly from the Fireworks manual.
    Individual layer masks convert to Fireworks object masks. Group masks are unsupported.
    Clipping masks convert to object masks, but their appearance changes slightly. To maintain appearance but lose editability, select the Clipping Masks preference.
    Blending modes for layers convert to blending modes for Fireworks objects, if corresponding modes exist.
    Layer effects are retained by default. If you prefer to convert these effects to corresponding Live Filters, select the Layer Effects preference. Note, however, that similar effects and filters might differ slightly in appearance.
    The first alpha channel in the Channels palette converts to transparent areas in the Fireworks image. Fireworks does not support additional Photoshop alpha channels.
    All Photoshop color depths and modes convert to 8-bit RGB.
    Adjustment layers are unsupported.
    The help manual should have made clarifications.  Especially if your were forced to use Fireworks.  I speak to those having used a Photoshop to Image Ready workflow for all those glorious years when a task was easier.
    1.  Say good bye to your Group Masks.  Object masks are not as powerful, or useful, as layer masks are in Photoshop.
    2.  The appearances of clipping masks change drastically.  Do not even attempt to use an image if you have a clipping image
         and expect it to be exported for use as a web graphic.  Fireworks muddles the final image with blurry edges.
    3.  In any case where your Photoshop image uses blending modes expect that Fireworks will not have the corresponding mode.
         Do expect the results to be not as clear as in the original image.
    4.  Layer effects ARE NOT retained, they are MERGED into the layer.  Open a Photoshop created image using layer effects (drop
         shadow, stroke, etc.).  Your effects have become merged into the latter.  Never, never save your PSD or TIF file from within Fireworks.
         You will lose all editability, FOREVER!
    5.  Fireworks Live Filters are a sorry, sorry instance of the powerful layer effects of Photoshop.  Each and every instance tried to date has
         shown Fireworks' iteration of filters to be different from those in use in Photoshop.
    6.  If you use your own patterns in Photoshop say good-bye to them.  Fireworks gives you no way to use your own.  Only a limited
         subset of those pre-packaged with Photoshop.
    6.  Since Fireworks does not support adjustment layers, masks, paths, etc., then what happened to cross program support and
         interactivity which Adobe praises?
    Why in tarnation does Fireworks support metadata in a web graphic?  Yes, the PNG file format allows for this.  Export a TIF or PSD containing metadata information from Photoshop to a PNG file.  Look at the file in Bridge.  It has no information.  If you do export a set of images using a batch operation you will find that some of the new PNG files cannot contain metadata.
    View the generated PNGs in Bridge.  Apply a metadata template.  You will find that some of the files will not accept the template.  You will have to individually re-export the image.  The reason I mention this normal Photoshop to Bridge workflow is because Fireworks' Help is touting it without explaining that not in all cases does it work.
    If you are coming over from Macromedia then you are used to a what was once an extremely good program.  Say good-bye to it.  If you were used to Image Ready — Good Luck!  At least it never crashed for no reason.  If you are new to Adobe then expect limited 60 day support and a company looking only at your bank account.
    Adobe needs to go ahead and kill this app and include its best features into Photoshop as they have done in the past.  Then get back to allowing prototyping in Photoshop and web graphic generation as an export feature as it once was!  I don't need two prototyping programs.  What I do need is a simple, easy method of getting my Photoshop designs to the web.

    Yes, Linda Nicholls is right. You will find FW better than PS.
    I also use FW only for anytype of graphics.

  • Copy file name to IPTC (core) Instructions

    Hello
    In the past Paul has written some great scripts to autuomate my Bridge workflow. I'm hoping for another brilliant concoction.
    I wish to copy my file name to the IPTC core- 'Instructions' field so that the original name will be preserved somewhere in case renaming more than once wipes that file name out of the File Properties palette.
    Thanks!
    Don

    I have Bridge CS2 and CS3 and for some reason the CS3 version has the "Preserve Filename..." checkbox grayed out and I cannot figure out why. I was also looking for a way to view the "Preserved Filename..." and the only way I could do this was by using Bridge CS2 (since it isn't working for me in CS3), going to rename the file I am trying to view the old name on, and select "Preserved Filename" under the dropdown menu. This is a huge hastle and for some reason Lightroom 1.0 does not have the capability of preserving filenames at all! The DAM capabilities of Lightroom truly need work, but it is a wonderful application nonetheless, and I use it now for everything and haven't needed to use Bridge since I got Lightroom.

  • PhaseOne iXA in Camera Raw?

    Does anyone know if the PhaseOne iXA (industrial sensor) 80mp system is compatable with Camera Raw/ Bridge workflow?

    Hey thanks Jeff
    I was thinking the same thing regarding the actual sensors being used - P1 is basically 'ruggedizing' their ground based cameras for aerial use.
    Re calling them: I haven't heard from them on a web inquiry so that looks like the next thing to do. Need a tactful was of saying "I don't want to use your software, but does Adobe's work?"
    Oh, and if you're still out there Jeff, as an owner of the P1's do you think its possible to overlay, pixel for pixel as an alpha channel an image captured with a IR filtered P1 sensor onto an RGB image simultaneously captured with a second P1 - given that a mounting system provides the same nadir point for the lenses?
    A medium format aerial camera system by Hexagon/Leica Geosystems (RCD30) does this with a beam splitter and two sensors using a single lens, however the image quality of the system (not to mention a 400k pricetag) we tested left a bit to be desired. So our engineers are looking @ using a couple P1 camera to accomplish a similar task more economically.

  • Renaming Individual Files  - needs simplifying

    In Bridge you click on double file name and name is highlighted and neatly excludes the file extention. Type, Copy or paste text and click on another file/hit enter and you're done. Simple, obvious, easy.
    In Bridge workflow is -
    Cntrl+T to show names/info, double click on name, rename.
    Double click on another file, rename.
    ... etc
    In LR, clicking, whether double, single, right has no effect, nothing in menus either, so where is it. Oh yes in the metadata panel, so obvious people keep asking in forums how to name files!
    In LR workflow is -
    Press J twice to see names/info, select file, move mouse to right to reveal panel [on autohide], click on metadata to open that part of panel [using SoloMode here], click on file name, deselect extension and finally rename. Move back to grid view and select another file, move over to panel to reveal it again, click on name, deselect extension, rename.
    ... etc
    A bit clunky in comparison, I'd say. Now as LR is aiming to be a DAM, why is renaming so obscure? Granted Batch renaming, once you find it in the menus [why no right click selection?] and go through the clunky set up for one's own template, is actually fantastic to use. Though I still right click everytime before remembering F2. I'm assuming an oversight here like Batch renaming was left out in Bridge Beta1.
    Now many people will use both LR and Bridge so why so much disparity in shortcuts and basic methodology for the same processes? You'd never guess both products were made by the same company.

    Just tried to edit a file name after editing in PS.
    God it's painful to do.
    LR imports and displays a file called "2007-03-15 004 Provia+Lomo-ed.psd no problem, yet when I edit it to "2007-03-15 Name 004 Provia + Lomo-ed.psd", LR changes it to "2007-03-15 Name 004 Provia @ Lomo-ed a [email protected]", where the @ symbol is actually a crossed out box in LR. ??????!!!!
    Now after a bit of playing around, I discover that if you edit an name, LR adds extention automatically, even if it's aready there. So, if you edit a filename to correct a typo you also have to delete the extension as LR adds it automatically. Not only that, undo doesn't correct the extention bug even though it corrects the name edit. Duh!
    Yet again LR takes a very simple thing, overcomplicates/breaks it and not only that, does it differently from other Adobe apps which weren't broken.
    Why can't I have a '+' sign in my file names or a ',' for that matter, they've worked until now with no problems.

  • Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,,  Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"

    Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,,  Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"

    Sorry for the late reply. My email firewall has become a little over zealous & sent a lot of my emails straight to my junk email folder, so I have only just now discovered your reply in my junk mail folder.
    The only "don't open files exceeding xxx megabytes" instruction I can find in my Prefs, is in the Bridge Prefs for Thumbnails, & mine is set at 1000mb. The biggest files I handle are bigger than 200mb so I should be able to open a few, not just one.
    However, this doesn't explain why I can open a psd format file of 180mb, close it, but then can't open a RAW format file of only 26mb immediately after.
    I can open the RAW file only if I restart my computer - very annoying!
    However, thanks for the advice about the video card & memory.
    So, I'm still stuck as to what the issue is.

  • Tapeless workflows and Sandy Bridge or other PC's: KISS or LOVE?

    Tapeless workflows and Sandy Bridge or other PC's: KISS or LOVE?
    Life used to be so simple when shooting video on a tape based camera. You shot your material, captured it for editing and stored your precious original footage on tape in a safe and dry place. Sure, it took time to capture, but the big advantage was that if you had a computer or drive failure, you would still have the original tape so everything could be recreated.
    Now with tapeless workflows we have the significant advantage of much faster import of the original footage. Connect the flash card or disk drive to the computer over USB and copy the data to a HDD on the computer, ready for editing. The data on the flash card or disk drive can then be erased, so you can reuse it for more shots. But, like Johan Cruyff has said repeatedly, every advantage has its drawback. In this case it simply means that you no longer have the original material to fall back on, in case of computer or drive failures. That is a very unpleasant and insecure feeling.
    The easy anwser to that problem is backups. Backup of the original media, backup of projects and backup of exports. This often means a bundle of externals for backup or NAS configurations. One thing is clear, it requires discipline to make regular backups and it costs time, as well as a number of disks. Four as a minimum: 1 for media, 1 for exports and at least 2 for projects. Note: This is excluding a backup drive for OS & programs.
    There are different backup strategies in use. Some say backup daily and use one disk for monday, one for tuesday, and so on.  Others say one disk for the first backup, the second for the second backup, then the first again for an incremental backup, etc. and once weekly a complete backup on a third disk. Whatever you choose, be aware that shelf live of a disk is far less than tape. There are horror stories everywhere about ball-bearings getting stuck after some time and without original tapes, you better be safe than sorry, so don't skimp on backups.
    What is the relevancy of all this? I thought this was about Sandy Bridge and other PC's.
    It is and let me try to explain.
    Card based cameras are for the most part DSLR and AVCHD type cameras, and we all know how much muscle is required to edit that in a convenient way. Adobe suggests in the system requirements to use raid configurations for HD editing and practice has shown that raid arrays do give a significant performance boost and improve responsiveness, making for a nicer editing experience. The larger the project and the longer the time-line, the more a raid array will help maintain the responsiveness.
    One thing you would not do is using a raid0 for projects, media and exports, even if you have backups. The simple reason is that the chance of disk failure multiplies by the number of disks in the raid0. Two disks double the chance of disk failure, three disks triple the chance, four disks quadruples the chance, etc.
    Remember: Disaster always strikes when it is most inconvenient.
    Imagine you have been working all day on a project, you decide to call it a day and to make your daily backup, but then the raid fails, before you made your backup. Gone is all of today's work. Then take into consideration the time and effort it takes to restore your backups to the state it was in yesterday. That does not make you happy.
    Another thing to avoid is using a software or mobo based parity raid, for the simple reason that it is slooowww and puts a burden on the CPU, that you want to use for editing, not house keeping.
    For temporary or easily recreated files, like the page-file, media cache, media cache database and preview files, it is very much advised to use a raid0. It makes everything a lot snappier and if disaster strikes, so what? These are easily recreated in a short time.
    This was a general overview of what is required with tapeless workflows. Now let's get down to what this means in terms of system design.
    Two approaches or train of thoughts
    KISS: Keep it stupidly simple or LOVE: Laughing over video editing
    The first one, the most economic one, is to use a system with 3 or 4 disks internally and 4 or more backup disks.
    A typical disk setup can look like this:
    This is a perfectly sensible approach if one does not have large or complex projects, long time-lines and is willing to take the risk of occasionally losing a whole days work, between backups. Many hobbyists and consumers fall in this category.
    The KISS approach keeps it stupidly simple. The drawback is that there is no logical way to add more disks or storage. The discipline, diligence and effort required for regular backups make it far from a laughing matter. In fact it can quickly become a bore. Add to that the fact that the disk setup is simple but not very fast, so less suited for situations where lots of clips are involved, multi-cam is a regularly recurring situation or lots of video tracks are involved.
    A number of video editors want more from their system than the occasional platonic KISS, they want to really LOVE their system, which lead to the other train of thought.
    This is more costly than the KISS approach, but you all know a fiancée or wife is more costly and dear than the occasional kiss on the cheek by an old friend.
    Let's start with a typical disk setup. It may look like this:
    Two striking differences in comparison to the KISS approach:
    1. Much easier disk organization and more disks and thus more space.
    2. It requires a hardware raid controller, causing a higher investment cost. It is like an engagement ring. You don't get LOVE for free, one of the guiding principles of the oldest trade in the world.
    These are easy statements to make, but what are the benefits or advantages, that you would fall in LOVE with such a system, and what are the drawbacks? Think back to Johan Cruyff's adage.
    The only drawback is cost. The advantages are multiple, easier organization, more speed, more storage, snappier editing, no jerkiness, lesser requirements for regular backups and - this is the major benefit - hardly a chance of losing a day's work in case of a drive failure. Keep in mind that a parity raid keeps all your data intact in case of a drive failure, so lessens the need for up-to-date backups.
    We all know, we get what we pay for: "If you pay peanuts, you get monkeys. OTOH, if you pay money to monkeys, you get rich monkeys". But in this case you get what you pay for, a much better editing experience with a much easier workflow.
    Using a parity raid (be it raid 3/5/6/30/50/60) you get security, ease of mind that you are protected against losing precious media, that you need not worry about the last time you made a backup, that the editing you did today may be lost and you save valuable time editing and a lot of aggravation because of a much more responsive system.
    How does this all relate to Sandy Bridge and other PC's?
    First of all, the price difference between a Sandy Bridge / P67 platform and an i7-950+ / X58 platform is very small. Of course the new architecture is slightly more expensive than the older one, but the differences are small, almost not worth talking about.
    So what are the differences? Look below:
    The first thing to keep in mind is that the Sandy Bridge is the successor of the i7-8xx CPU and as such it is much more evolutionary than revolutionary. The CPU power has increased significantly over the i7-8xx due to new architecture and a smaller production process (32 nm), but in essence all the capabilities have remained unchanged. Same memory, same PCI-e lanes, same version, same L3 cache and no support for dedicated raid controllers.
    It is great that the processor performs much better than the older i7-8xx CPU's, almost achieving the level of the i7-9xx range of processors, but is still limited:
    The Sandy Bridge is unsuitable for anything more than a KISS system.
    Why? Because it lacks the required PCI-e lanes to accomodate more than a 16 x PCI-e nVidia card with CUDA support to enable hardware MPE acceleration and the integrated graphics are not supported by CS5.
    You may wonder if that is a bad thing. The plain and simple anser is NO. It is a great processor, it delivers great value for money, is a solid performer, but it has its limitations. Intel had a reason to position this CPU as a mid-level CPU, because that is what it is, a mid-level performer in comparison to what is to come.
    The term mid-level performer may seem strange when compared to the old generation of i7-9xx CPU's, because they perform almost equally well, but keep in mind that there is a generation difference between them.
    So what about the i7-9xx and X58 platform?
    It still is going strong. About the same performance as a Sandy Bridge, with only the much more expensive hexa-cores clearly in the lead, both performance and price wise. The quad cores deliver about the same value for money.  The main difference however is the platform that allows a dedicated raid controller to be installed, thus making it the platform of choice for those who want to go from a passing KISS to true LOVE.
    And what lies ahead?
    Sandy Bridge E on the Waimea platform (X68). Now that is revolutionary. More than double almost everything a processor can offer: double the cores, double the PCI-e lanes, triple the memory, more than double the L3 cache, increase the PCI-e support from 2.0 to 3.0, etc...
    This is why Intel calls this a high-end CPU / platform.
    So what now?
    If you prefer a KISS approach, choose either a Sandy Bridge/P67 or an i7-950+/X58 platform.
    If you wonder whether in the future you may need multi-cam more frequently, edit more complex projects and longer timelines or even progress to RED, look at KISS/LOVE solutions, meaning the i7-950+/X58.
    If you can't have downtime, time pressure is high, delivery dates to clients are critical or you edit highly complex projects, lots of multi-cam situations or lengthy time-lines, choose a LOVE solution, an i7-950+/X58 platform.
    If you have the time to wait till Q4/2011, Sandy Bridge E/Waimea looks to be worth the wait.
    Hope this gives you some more insight into recent and future developments and helps you make wise investment decisions.

    I'm upgrading from an AMD 3800+, cutting with Vegas 7 Pro. Usually shoot DSLR or HDV, sometimes P2, EX or RED. I have ridiculously cheap access to Macs, FCP/FCS, all kinds of software.
    I've been agonizing over this for the last month, was originally hoping the UD7 mobo was the solution, read the read about the NF200/PCIe issue a few days ago, http://www.dvinfo.net/forum/non-linear-editing-pc/489424-i7-980x-now-wait-sandybridge-2.ht ml- and still decided to go for a 2600k. 
    My preference is to treat my video footage the same way as my digital imagery: I make (at least) duplicate back ups of everything before reformatting the cards, never delete the back ups, and only worry about the day-to-day stuff at night. Unless I'm rendering or involved in other long processes, in which case I'll back up the work in process the next day. If I am under a really really tight deadline I might back up as I go.
    Yes, a RAID might make it easier, but I'm paranoid enough to prefer a slower, safer backup. You can always duplicate, and usually improve upon, a days work, but you can never get back original footage you lost. I have only ever had one hard drive die on me (a few enclosures crapped out, though)- it took a couple of (mostly unattended) hours to rectify. As a matter of act, I've had far more loss/damage from tapes than from hard drives.
    I ordered the UD7, 2 F4s and 4 F3Rs, understanding I will probably want to upgrade to SBE when it comes out, or maybe next year. The 2600k/mobo/RAM will likely hold its value better than a 950/X58, likely because of the marketplace as much as merit.
    The UD7 / RAID card issue is in it's early days, there may be a solution/mitigation. Probably not. But if I really really need a RAID card, then I probably really really need a 980, NAS, etc etc.
    But Harm still rocks!

  • Workflow issue with Bridge and everything else

    Short and sweet. Well, not really.
    I use windows - so as a result, for some reason unknown to man (after a decade of waiting), I still cannot see "previews" of most, if not all of any adobe software in the windows dialogue boxes.
    think PDF's and the registry hacks we have to do to "enable" previews. But on a mac I can?
    So I have to use bridge - a lot.
    Now when I have a linked image in illustrator (or whatever) and choose "reveal in bridge" it will hunt and drill down through a multitude of folders and display the image in it's native folder - which I can then open in photoshop for instance - edit it - and Illustrator will detect the change and update. Awesome.
    But aside from running a script to send a batch job to a program, it really doesn't "do" anything else that one would expect a "bridge" to do;
         I cannot create a "project" portfolio that would track a client project and all it's related documents.
         Or collaborate with a team.
         I cannot have non destructive edits of a document (such as using an instance of a file like lightroom does) - or "send copy to photoshop" and have Bridge stack the results.
         I cannot combine and tag collections of documents (make a database of stuff).
         I cannot ask Bridge to tell me which documents have placed documents, or (vice versa) which documents are placed into other documents - that would be so cool.
              imagine being able to select a jpeg or psd file and have the option to "Find documents using this file"
              or looking at a "project" and having a list of all first level documents with all their subsequent "placed content" listed all drop down expandable
    So my beef today is that I finally spent an hour messing about thinking I had something "wrong" and went through Bridge CS6 with a fine tooth comb trying to find out if anything had changed.
    and nope - it still doesn't behave as one would think it would.
    Currently, I have some documents that require monthly changes to images, which for the most part came from one photo shoot, and all have essentially the same perspective, appearance, lighting and shading, but all different products and I have a folder of "preformatted images". So monthly I really only need to update the images, and a bit of text. Being posters, InDesign whines a bit for vector art manipulation, so I stick to Illustrator for this job.
    But in Illustrator, I cannot choose another image to replace my linked image - without either;
         a: (reveal in bridge), select new replacement image - place as a new image, which then needs to be manipulated as the "old" image was, "remaking" all the adjustments, and then finally deleting the original linked image.
         b: (reveal in bridge) keep bridge open on the image I need (and it's name), go back to illustrator to open the "relink" windows dialogue and "blindly" browse till I find the image I want as shown in bridge.
         c: simply relink and browse blindly to find a file you can't see a preview of and guess, or drag and drop, or all the other non practical ways to replace the image.
    Option B gives the desired end result where the image I have in a clipping mask, buried in a document in a certain way, with certain effects, is simply replaced without impacting anything else.
         But this takes quite some time when there are a lot of images.
    So Bridge and its promised workflow functionality still isn't living up to it's purpose exactly.
    Bridge isn't bridging.
    With indesign, it's the same issue - you can't "relink" by revealing in bridge, choosing a "replacement" image and "update"
    Maybe a "relink with Bridge" choice in the Links menu?
    and in bridge, since Illustrator triggered the request, a button appears to "Replace" - once you finish browsing and highlighting the replacement image you need, just click it and it's done.
    So two issues -
    Why can't previews of adobe files be shown in windows explorer (still)?
         if they did, I'd really have no use for Bridge.
    Why isn't bridge actually communicating with the apps connecting to it?
    - and yes, I understand that I cannot ask bridge to go find a placed file and replace it with "this" file, but when illustrator "asks" for "this", bridge should be able to "respond" and give "that" since the app initiated the request.
    Bridge should be a workflow tool as advertised - it should literally be able to be a proper workflow hub for all things adobe (and be able to catalogue and track all design file type previews - corel files, cad, 3d, etc)... but as it stands it's just a glorified windows explorer without workflow options.
    Bridge hasn't been altered in years, and it's still lingering around - I think - so that we can simply see thumbnails, rather than just allowing each adobe program to make "previews" windows needs.
    I can change metadata in windows, I can use freeware to change it extensively.
    So aside from the "open in" options and the ability to browse all adobe file types, what's the point?

    I couldn't read all through your post as I am jetting out of here.
    Buy this:
    http://www.fastpictureviewer.com/codecs/
    and install it. It's relatively cheap. Screen shot is from Windows Explorer.
    Handles ID, PSD, etc., files as well. Though the preview uses greeked text for the most part for the ID files.
    Take care, Mike

  • Bridge, Lightroom, InDesign workflow question

    Hey everyone,
    I've been using Adobe InDesign CS5 and Apple's Aperture software together (on a Mac) to do design projects over the past year and a half or so. I'd never been that interested in Adobe's other applications until recently, when I got a Creative Cloud membership, and now am reveling in the bounty of creative possibilities. Recently i've been interested in integrating Bridge into my workflow and transitioning away from Aperture to Lightroom (as i imagine many other people are considering/in the process of doing right now). I've been taking some video tutorials on Lynda.com and recently came across Terry White's "Bridge CC vs. Lightroom" youtube screencast (http://www.youtube.com/watch?v=vd8XLYG8A0s#t=20). While I really appreciated Terry's perspectives and find them helpful, I think he polarized the "Design" (Bridge) and "Photography" (Lightroom) paradigms that he used to distinguish the programs: Bridge is a file browser for working numerous file types across creative cloud applications, whereas Lightroom is a tool for photographers to do powerful non-destructive edits.
    Part of what I've liked about using Aperture with InDesign is that (however buggy this feature is) I can directly access my Aperture library from within the OS X open dialog box, thus allowing me to use files that i've edited and keeping all my work in one library. However, from what i've learned so far, and what Terry's video didn't (directly) address is what are some good practices for using edited photographs within an application such as InDesign. It seemed in the video he simply exported image files from Lightroom into folders, and then I suppose you could use mini-bridge to browse that folder. But i'm wondering if there isn't a better or simpler way to do this, and I'm wondering if i could solicit opinions from folks as to how they work between Everything i've tried to do in my workflow is minimize steps and keep track of the proliferation of images i work with. As much as I see that Lightroom is a better maintained tool than Aperture, it sure is nice to be able to directly access those image files from within InDesign…
    Very new to all of this. Thanks in advance for everyone's help.
    Quin

    Hey everyone,
    I've been using Adobe InDesign CS5 and Apple's Aperture software together (on a Mac) to do design projects over the past year and a half or so. I'd never been that interested in Adobe's other applications until recently, when I got a Creative Cloud membership, and now am reveling in the bounty of creative possibilities. Recently i've been interested in integrating Bridge into my workflow and transitioning away from Aperture to Lightroom (as i imagine many other people are considering/in the process of doing right now). I've been taking some video tutorials on Lynda.com and recently came across Terry White's "Bridge CC vs. Lightroom" youtube screencast (http://www.youtube.com/watch?v=vd8XLYG8A0s#t=20). While I really appreciated Terry's perspectives and find them helpful, I think he polarized the "Design" (Bridge) and "Photography" (Lightroom) paradigms that he used to distinguish the programs: Bridge is a file browser for working numerous file types across creative cloud applications, whereas Lightroom is a tool for photographers to do powerful non-destructive edits.
    Part of what I've liked about using Aperture with InDesign is that (however buggy this feature is) I can directly access my Aperture library from within the OS X open dialog box, thus allowing me to use files that i've edited and keeping all my work in one library. However, from what i've learned so far, and what Terry's video didn't (directly) address is what are some good practices for using edited photographs within an application such as InDesign. It seemed in the video he simply exported image files from Lightroom into folders, and then I suppose you could use mini-bridge to browse that folder. But i'm wondering if there isn't a better or simpler way to do this, and I'm wondering if i could solicit opinions from folks as to how they work between Everything i've tried to do in my workflow is minimize steps and keep track of the proliferation of images i work with. As much as I see that Lightroom is a better maintained tool than Aperture, it sure is nice to be able to directly access those image files from within InDesign…
    Very new to all of this. Thanks in advance for everyone's help.
    Quin

Maybe you are looking for