Best practice for photo format: RAW+PSD+JPEG?

What is the best practice in maintaining format of files while editing?
I shoot in RAW and import into PS CS5. After editing, it allows me to save as various formats, including PSD and JPEG. PS says that if you want to re-edit the file, you should save as PSD as all the layers are maintained as-is. Hence I'd prefer to save as .PSD. However, in most cases, the end objective is to share the image with others and JPEG is the most suitable format. Does this mean, that for each image, its important to save it in 3 formats viz RAW, PSD and JPEG? Wont this increase the total space occupied tremendously? Is this how most professionals do it? Pls advice.

Thanks everyone for this continued discussion in my absence over two weeks. Going through it i realize its helpful stuff. During this period, i downloaded Aperture trial and have learnt it (there's actually not much learning, its so incredibly intuitive and simple, but incredibly powerful. Since I used iphoto in the past, it just makes it easier.
I have also started editing my pics to put them up on my photo site. And over past 10 days, here is the workflow I have developed.
-Download RAW files onto my laptop using Canon s/w into a folder where i categorize and maintain all my images
-Import them into Aperture, but letting the photos reside in the folder structure i defined (rather than have Aperture use its own structure)
-Complete editing of all required images in Aperture (and this takes care of 80-90% of my pics)
     -From within Aperture open in PS CS5 those images that require editing that cannot be done in Aperture
     -Edit in CS5 and do 'Save', this brings them back to Aperture
     -Now I have two versions of these images in Aperture - the original RAW and the new .PSD
-Select the images that I need to put up on my site and export them to a new folder from where i upload them
I would be keen to know if someone else follows a more efficient or robust workflow than this, would be happy to incorporate it.
There are still a couple questions I have:
1 - Related to PS CS5: Why do files opened in CS5 jump up in terms of their file size. Any RAW or JPEG file originally btn 2-10 MB shows up as minimum 27 MB in CS. The moment you do some edits and/or add layers, it reaches 50-150MB. This is ridiculous. I am sure I am doing something wrong. Or is this how CS5 works with everyone.
2 - After editing a file in CS by launching it from Aperture, I now end up with two versions in Aperture, the original file and the new .PSD file (which is usually 100MB+). I tried exporting the .PSD file to a folder to upload it on my site, and wasnt sure what format and size it would end up with. I got it as a JPEG file within reasonable filesize limits. Is this how Aperture works? Does Aperture allow you options of which format you want to save the file in?

Similar Messages

Best Practice For Referencing JPEG Path Using Servlets To Prepare HTML IMG

I am migrating a legacy app from Tomcat 5 to Weblogic 11g (10.3). In the legacy app, servlets write HTML that uses relative paths for <IMG src="../images/img.jpeg"> and <script src="../javascript/js.js">. The app is deployed as an exploded archive. Unfortunately, none of the images or script are being loaded. I've tried using http://serverIP:portNum/contextName/images/img.jpeg"> but it doesn't work. I've also checked to get the name of the context in the servlet and it's the root context. Could it have something to do with me having to append .war onto the application when I deploy it? Would it help if I deployed it as a war inside an ear? Basically, I want some best practices for doing this on Weblogic 11g. There are a lot of images and javascript and I'm really hoping they don't have to be inserted using ClassLoader.getResourceAsStream()... thank you.

Best Practice:
1. Move Static files like images, css, java scripts to a web server infrastructure if available.
2. If this is not your case, then please send your directory information how you have packaged your EAR. I can advice :)

Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.

Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.

There may be a few links in Apple Support, regarding articles about how to use iBooks Author
and iBooks Store, etc; these would be separated into two general categories by device used.
Since there is an iOS and an OS X version of each, you may have to look to see what Apple
Support says about the one you are interested in; and how far their database goes toward an
answer to your question. Otherwise, a general search engine approach may be necessary.
Not sure if anything along the lines of what you seek would be available in an App.
References to iBooks Author and iBooks Store, etc appear within these two categories in Support:
For Mac OS X:
http://www.apple.com/support/mac-apps/
For iOS:
http://www.apple.com/support/ios/
Appears a community host moved your earlier post into one of the iBooks Author or Store sections
after I'd replied to what otherwise may be a similar post. Not sure if the links to the Discussions area
of iBooks you are interested in, have similar questions or answers by others who'd visited previously.
Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.
In my reply to your earlier thread, prior to it being moved, those links to sections of iBooks Author, etc
are posted. You can also find them from the main Apple Support Communities page.
Sorry to not be of much help in this matter.
Good luck & happy computing!

Best Practices for Using Photoshop (and Computing in General)

I've been seeing some threads that lead me to realize that not everyone knows the best practices for doing Photoshop on a computer, and in doing conscientious computing in general. I thought it might be a good idea for those of us with some exprience to contribute and discuss best practices for making the Photoshop and computing experience more reliable and enjoyable.
It'd be great if everyone would contribute their ideas, and especially their personal experience.
Here are some of my thoughts on data integrity (this shouldn't be the only subject of this thread):
Consider paying more for good hardware. Computers have almost become commodities, and price shopping abounds, but there are some areas where spending a few dollars more can be beneficial. For example, the difference in price between a top-of-the-line high performance enterprise class hard drive and the cheapest model around with, say, a 1 TB capacity is less than a hundred bucks! Disk drives do fail! They're not all created equal. What would it cost you in aggravation and time to lose your data? Imagine it happening at the worst possible time, because that's exactly when failures occur.
Use an Uninterruptable Power Supply (UPS). Unexpected power outages are TERRIBLE for both computer software and hardware. Lost files and burned out hardware are a possibility. A UPS that will power the computer and monitor can be found at the local high tech store and doesn't cost much. The modern ones will even communicate with the computer via USB to perform an orderly shutdown if the power failure goes on too long for the batteries to keep going. Again, how much is it worth to you to have a computer outage and loss of data?
Work locally, copy files elsewhere. Photoshop likes to be run on files on the local hard drive(s). If you are working in an environment where you have networking, rather than opening a file right off the network, then saving it back there, consider copying the file to your local hard drive then working on it there. This way an unexpected network outage or error won't cause you to lose work.
Never save over your original files. You may have a library of original images you have captured with your camera or created. Sometimes these are in formats that can be re-saved. If you're going to work on one of those files (e.g., to prepare it for some use, such as printing), and it's a file type that can be overwritten (e.g., JPEG), as soon as you open the file save the document in another location, e.g., in Photoshop .psd format.
Save your master files in several places. While you are working in Photoshop, especially if you've done a lot of work on one document, remember to save your work regularly, and you may want to save it in several different places (or copy the file after you have saved it to a backup folder, or save it in a version management system). Things can go wrong and it's nice to be able to go back to a prior saved version without losing too much work.
Make Backups. Back up your computer files, including your Photoshop work, ideally to external media. Windows now ships with a quite good backup system, and external USB drives with surprisingly high capacity (e.g., Western Digital MyBook) are very inexpensive. The external drives aren't that fast, but a backup you've set up to run late at night can finish by morning, and if/when you have a failure or loss of data. And if you're really concerned with backup integrity, you can unplug an external drive and take it to another location.
This stuff is kind of "motherhood and apple pie" but it's worth getting the word out I think.
Your ideas?
-Noel

APC Back-UPS XS 1300. $169.99 at Best Buy.
Our power outages here are usually only a few seconds; this should give my server about 20 or 25 minutes run-time.
I'm setting up the PowerChute software now to shut down the computer when 5 minutes of power is left. The load with the monitor sleeping is 171 watts.
This has surge protection and other nice features as well.
-Noel

Best practices for applying sharpening in your workflow

Recently I have been trying to get a better understanding of some of the best practices for sharpening in a workflow. I guess I didn't realize it but there are multiple places to apply sharpening. Which are best? Are they additive?
My typical workflow involves capturing an image with a professional digital SLR in either RAW or JPEG or both, importing into Lightroom and exporting to a JPEG file for screen or printing both lab and local.
There are three places in this workflow to add sharpening. In the SLR, manually in Lightroom and during the export to a JPEG file or printing directly from Lightroom
It is my understanding that sharpening is not added to RAW images even if you have added sharpening in your SLR. However sharpening will be added to JPEG’s by the camera.
Back to my question, is it best to add sharpening in the SLR, manually in Lightroom or wait until you export or output to your final JPEG file or printer. And are the effects additive? If I add sharpening in all three places am I probably over sharpening?

You should treat the two file types differently. RAW data never has any sharpening applied by the camera, only jpegs. Sharpening is often considered in a workflow where there are three steps (See here for a founding article about this idea).
I. A capture sharpening step that corrects for the loss of sharp detail due to the Bayer array and the antialias filter and sometimes the lens or diffraction.
II. A creative sharpening step where certain details in the image are "highlighted" by sharpening (think eyelashes on a model's face), and
III. output sharpening, where you correct for loss of sharpness due to scaling/resampling or for the properties of the output medium (like blurring due to the way a printing process works, or blurring due to the way an LCD screen lays out its pixels).
All three of these are implemented in Lightroom. I. and II. are essential and should basically always be performed. II. is up to your creative spirits. I. is the sharpening you see in the develop panel. You should zoom in at 1:1 and optimize the parameters. The default parameters are OK but fairly conservative. Usually you can increase the mask value a little so that you're not sharpening noise and play with the other three sliders. Jeff Schewe gives an overview of a simple strategy for finding optimal parameters here. This is for ACR, but the principle is the same. Most photos will benefit from a little optimization. Don't overdo it, but just correct for the softness at 1:1.
Step II as I said, is not essential but it can be done using the local adjustment brush, or you can go to Photoshop for this. Step III is however very essential. This is done in the export panel, the print panel, or the web panel. You cannot really preview these things (especially the print-directed sharpening) and it will take a little experimentation to see what you like.
For jpeg, the sharpening is already done in the camera. You might add a little extra capture sharpening in some cases, or simply lower the sharpening in camera and then have more control in post, but usually it is best to leave it alone. Step II and III, however, are still necessary.

Best practice for reinstalling anti virus on reinstalling windows

Best practice for reinstalling anti virus after formatting drive and reinstalling windows No anti virus disc.
Hasty

Hello,
I'd ask in the Windows forum on Microsoft Community.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog:http://unlockpowershell.wordpress.com
My Book:Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Best Practice for Distributing Databases to Customers

I did a little searching and was surprised to not find a best practice document for how to distribute Microsoft SQL Databases. With other database formats, it's common to distribute them as scripts. It seems that feature is rather limited with the built-in
tools Microsoft provides. There appear to be limits to the length of the script. We're looking to distribute a database several GBs in size. We could detach the database or provide a backup, but that has its own disadvantages by limiting what versions
of the SQL Server will accept the database.
What do you recommend and can you point me to some documentation that handles this practice?
Thank you.

Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
detach/attach, script generation, Microsoft Sync framework, and a few others.
EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
backup/maintenance routine in your environment.
As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

Best practice for phone number column data type

Hi,
I hope I have posted this in the right forum, if not just notify me and i will remove it to the correct area.
What would be considered best practice for storing a phone number.
Number of Varchar2.
Ben

Well I was thinking that Number would have the following disadvantages,
1. Users entering phone numbers into a form may be tempted to pre format with spaces, thereby throwing up an error.
2. Mobile phone numbers may have leading zeros
3. Calculations are not carried out on phone numbers.
I was leaning towards a varchar2 type.
Ben

Best Practice for Conversion Workflow

Hello,
I'm converting video files from our "home grown" virtual media reserve to iTunes U. Some of the files are in RM format, some are already compressed .mov's (not H.264) and some I have the original DV files for.
Anyone out there have a best practice for converting these file types for posting to iTunes U? I have Final Cut Studio (Compressor), QT Pro and Squeeze available to me.
Any experience you have with this would be helpful.
Thanks,
Jeana

For converting old files to a podcast compatible video and based on the machine you have, consider elgato turbo.264. It is a fairly priced "co-processor" for video conversion. It is comprised of an application and a small USB device with a encoder chip in it. In my experience, it is the fastest way to create podcast video files. The amount of time that you will save will pay for the device quickly (about $100). Plus it does batch conversion of any video that your system currently plays through QuickTime. it has all the necessary presets and you can create your own. It has a few minor limitations such as not supporting (at this moment) enhanced podcasting features such as chapter markers and closed-captions but since you have old files for conversion, that won't matter.
For creating new content, the workflow varies a lot. Since you mention MP3s, I guess you are also interested in audio files. I would stick with GarageBand, especially if you are a beginner plus it supports enhanced podcasts.
In any case the most important goal is to have the simplest and fastest way to go from recording to publication. The less editing the better. To attain that, the best methods will require the largest investments. For example, for video production the best way is to produce the content live so when you finish recording it is only a matter of encoding and publishing. that will require the use of a video switcher that can ingest at least one video camera and a computer output to properly capture presentation material. That's the minimum. there are several devices that can do this for you. Some are disguised PCs and some connect to a PC for tapeless recording. You can check the Tricaster, which I like but wish it was a Mac and not a Windows Xp PC. Other routes may include video mixers from manufacturers like Edirol, Pansonic or Sony connected to a VTR or directly to a Mac for direct-ti-disc capture. I f you look at some of the content available in iTunes U, you will see what I explain here. This workflow requires preparation and sufficient live support but you will have your material ready for delivery almost immediately after the recorded event. No editing required. Finally, the most intensive workflow is to record everything separately and edit it later, which is extremely time consuming.

Best practice for importing non-"Premiere-ready" video files

Hello!
I work with internal clients that provide me with a variety of differnet video types (could be almost ANYTHYING, WMV, MP4, FLV). I of course ask for AVIs when possible, but unfortunately, I have no control over the type of file I'm given.
And, naturally, Premiere (just upgraded to CS5) has a hard time dealing with these files. Unpredictable, ranging from working fine to not working at all, and everything in between. Naturally, it's become a huge issue for turnaround time.
Is there a best practice for preparing files for editing in Premiere?
I've tried almost everything I can think of: converting the file(s) to .AVIs using a variety of programs/methods. Most recently, I tried creating a Watch Folder in Adobe Media Encoder and setting it for AVI with the proper aspect ratio. It makes sense to me that that should work:using an Adobe product to render the file into something Premiere can work with.
However, when I imported the resulting AVI into Premiere, it gave me the Red Line of Un-renderness (that is the technical term, right?), and had the same sync issue I experienced when I brought it in as a WMV.
Given our environment, I'm completely fine with adding render time to the front-end of projects, but it has to work. I want files that Premiere likes.
THANK YOU in advance for any advice you can give!
-- Dave

I use an older conversion program (my PrPro has a much older internal AME, unlike yours), DigitalMedia Converter 2.7. It is shareware, and has been replaced by Deskshare with newer versions, but my old one works fine. I have not tried the newer versions yet. One thing that I like about this converter is that it ONLY uses System CODEC's, and does not install its own, like a few others. This DOES mean that if I get footage with an oddball CODEC, I need to go get it, and install it on the System.
I can batch process AV files of most types/CODEC's, and convert to DV-AVI Type II w/ 48KHz 16-bit PCM/WAV Audio and at 29.97 FPS (I am in NTSC land). So far, 99% of the resultant converted files have been perfect, whether from DivX, WMV, MPEG-2, or almost any other format/CODEC. If there is any OOS, my experience has been that it will be static, so I just have to adjust the sync offset by a few frames, and that takes care of things.
In a few instances, the PAR flag has been missed (Standard 4:3 vs Widescreen 16:9), but Interpret Footage has solved those few issues.
Only oddity that I have observed (mostly with DivX, or WMV's) is that occasionally, PrPro cannot get the file's Duration correct. I found that if I Import those problem files into PrElements, and then just do an Export, to the same exact specs., that resulting file (seems to be 100% identical, but something has to be different - maybe in the header info?) Imports perfectly into PrPro. This happens rarely, and I have the workaround, though it is one more step for those. I have yet to figure out why one very similar file will convert with the Duration info perfect, and then a companion file will not. Nor have I figured out exactly what is different, after running through PrE. Every theory that I have developed has been shot down by my experiences. A mystery still.
AME works well for most, as a converter, though there are just CODEC's, that Adobe programs do not like, such as DivX and Xvid. I doubt that any Adobe program will handle those suckers easily, if at all.
Good luck,
Hunt

Best practice for Error logging and alert emails

I have SQL Server 2012 SSIS. I have Excel files that are imported with Exel Source and OLE DB Destination. Scheduled Jobs runs every night SSIS packages.
I'm looking for advice that what is best practice for production environment.Requirements are followings:
1) If error occurs with tasks, email is sent to admin
2) If error occurs with tasks, we have log in flat file or DB
Kenny_I

Are you asking about difference b/w using standard logging and event handlers? I prefer latter as using standard logging will not always data in the way in which we desire. So we've developed a framework to add necessary functionalities inside event handlers
and log required data in the required format to a set of tables that we maintain internally.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

What is the Best practice for ceramic industry?

Dear All;
i would like to ask two questions:
1- which manufacturing category (process or discrete) fit ceramic industry?
2- what is the Best practice for ceramic industry?
please note from the below link
[https://websmp103.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000409682008E ]
i recognized that ceramic industry is under category called building material which in turn under mill product and mining
but there is no best practices for building material or even mill product and only fabricated meta and mining best practices is available.
thanks in advance

Hi,
I understand that you refer to production of ceramic tiles. The solution for PP was process, with these setps: raw materials preparation (glazes and frits), dry pressing (I don't know extrusion process), glazing, firing (single fire), sorting and packing. In Spain, usually are All-in-one solutions (R/3 o ECC solutions). Perhaps the production of decors have fast firing and additional processes.
In my opinion, the curiosity is in batch determination in SD, that you must determine in sales order because builders want that the order will be homogeneus in tone and caliber, and he/she can split the order in diferents deliveries. You must think that batch is tone (diferents colours in firing and so on) and in caliber.
I hope this helps you
Regards,
Eduardo

Best practice for exporting from iMovie '08 to iDVD

I am looking to find out what is the best practice for exporting from iMovie '08 to iDVD. I have read the other postings that give the basic howto (export to Media Browser then select the video in iDVD). However, my question is a little more technical. I have 1080i HD projects. I am interested in burning them to DVD in the best possible quality. What setting should I be using when I publish to Media Browser?
I am wondering about quality loss due to more than one conversion/compression. I suspect that when I export to the Media Browser then this is occurring. If I am not mistaken iMovie is using something like H.264 for this. Then, when I run iDVD I suspect it will it do another conversion/compression, I think to get to MPEG2. Not only could this result in a loss of quality but also it will take extra time. I am interested to know what others think about this.
Finally, I am looking to create DVDs for a lot of video. I am wondering if there are any USB or firewire hardware devices out there that could speed up the compression. I use the Elgato Turbo.264 when I want to encode to H.264 but I wonder if there is something similar for DVD creation.
Thanks in advance.

the standards for videoDVD are 720x480, and usually mpeg2 encoded..
so, your HiDef project HAS to be 'downsampled' somehow..
I would Export with Qucktime/apple intermediate => which is the 'format' your project is allready, and you avoid any useless 'inbetween encoding'..
iDVD will 'swallow' this huge export file - don't mind: iDVD cares for length, not size.
iDVD will then convert into DVD-standards..
you can 'raise' quality, by using projects <60min - this sets iDVD automatically to highest technical possible bitrate
hint: judge pic quality on a DVDplayer + TV.. not on your computer (DVDs are meant for TVdelivery)

HTML and CSS Best Practices for Eloqua?

Hello Topliners Community,
My name is Ben and I am a Web Designer. I am currently looking for any guidance on HTML and CSS best practices when working with Eloqua. I am interested in the best practices for e-mail and landing pages.
Thank you,
Ben

Personally I like to upload my custom created html/css into Eloqua instead of using the WYSIWYG.
But if you must then right clicking on text boxes and click edit source is the way to go.
There was a good discussion on editing your forms with CSS:
Energize Your Eloqua10 Forms with CSS
created by Ryan Wheler on Nov 2, 2012 8:44 AM, last modified by Greg Stotler on Sep 19, 2013 2:00 PM
Version 2
CSS can be used to heavily customize the layout of forms in Eloqua10. In this article we will provide sample cover some common formatting use cases on Eloqua10 Landing Pages. Further details about uses of CSS in Eloqua10 form templates can be found here: EE12 - Do It - Eloqua - Energize E10 Forms
Eloqua10 Forms HTML Structure
Below is an outline of the structure of the HTML generated by Eloqua when a form is added to a landing page. By targeting the HTML classes highlighted below, we can control the layout of any form on your landing page.
For the rest of page: http://topliners.eloqua.com/docs/DOC-3015

Best Practices for Removing Shots from BDMV folder

CS6 Production Premium Suite
Win7x64
Canon XA10
I would appreciate feedback on the best practices for the following situation:
Using Windows Explorer, I copy the BDMV folder from the XA10 to my Talk2 project folder.
The BDMV folder has three one hour shots (talks) where each shot is one hour called Talk1, Talk2, and Talk3.
Each shot consists of several MTS files in the STREAM folder since MTS files have a maximum file size so a new MTS file is created when a given MTS file reaches the maximum file size.
Since I only want to have Talk2 stuff in my Talk2 project folder, I need to remove the Talk1 and Talk3 stuff from the BDMV folder.
I delete the Talk1 and Talk3 MTS files from the STREAM folder.
I delete the Talk1 and Talk3 CPI files from the CLIPINF folder.
I leave the PLAYLIST folder as is.
Using the Media Browser, I import Talk2 (which consists of two MTS files).
I edit the clip.
This procedure seems to work, but I do not know if there are any "got you" issues.
Thanks in advance.

Oh, don't do it that way. I know a lot of people do, heck, my boss does, but it's just asking for trouble.
Treat your card as if it was your original tape master (because it is). It is the most important thing you have. Don't delete or move any part of it.
If you want to break up the talks, do it as you shoot them. Use separate cards for each talk and archive each one separately. There is too much valuable information in the structure of the card format. You may not need it now but your editing program may need it later.
Hard drive space is cheap but digital recordings are priceless

Best practice for photo format: RAW+PSD+JPEG?

Similar Messages

Maybe you are looking for