Bridge exports to sRGB instead AdobeRGB

Hi,
I've a problem with the Bridge export functionality.
When I export (Nikon) RAW files to jpg files (directly via the Bridge Export functionality, without using Photoshop) always sRGB is taken as profile for the jpgs (it doesn't matter if I open the Raw files before with Camera Raw and set AdobeRGB as profile).
I can't find a setting that enables Bridge to export with AdobeRGB profile (like in Lightroom).
Any hints?
My configuration:
Windows 7 Home Premium 64bit.
Photoshop CS5
Thanks,
Holger.

Thanks. Installing a third party plug-in will be my last solution.
I've read the description of the plug-in and was wondering if it was developped for CS4. At least the Bridge in CS5 has the Export functionality (I do not know the Bridge in the previous CS4 version, perhaps there the plug-in was needed).
In the CS5 version I can specify own presets like "High Quality" export or "Export for email". Very nice but the profile is wrong.
When I use the workaround "Tools - Photoshop - Image Processor" (sorry I do not know if this is the correct wording since I use the german version of CS5) the image processor from Photoshop will be taken. There I do not have my presets, but at least the profile is set to AdobeRGB.
I also tried already Lightroom. There the export functionality works fine. But threre are two drawbacks.
1) The color labeling will not be imported from Bridge (meaning when I specify a picture as "red" or "green" this will not be recogniced by Lightroom. Same, the other way round. Setting a color label or only exporting in Lightroom and opening the Bridge the label will be displayed as "white" (formerly red, green or whatever). So my labeling is lost (for the newly exported jpgs). I do not understand why there is not a better integration for this feature of these two Adobe products.
2) There is a known bug with the Spot Removal Tool and jpgs (at my system the tool is so slow with jpgs that you can't use it => Lightroom freezes for seconds with every move of the mouse, with Raw files it works perfectly)
One last question. If you do not use the export functionality from Bridge, how do you convert your Raw files to jpg?
Thanks for the plug-in link,
Holger.
Remark after post:
I have found a solution for the color labeling problem with Bridge - Lightroom.
They have to use the exact same wording (there is also a preset in Lightroom to use the Bridge standard). Then it works.
Message was edited by: H.D.

Similar Messages

Bridge Exports Changes Resolution from 300 to 72 dpi, resizing my image

I like to use Bridge (CS5) to export my photographs for printing, and frequently I will use the Export feature to resize the images (e.g., 5x7 vs full size), but every time I export it recharacterizes the images as 72 dpi, vs the 300 dpi I prefer.
Consistent with some of the previous postings (~2 yrs ago) I have seen on this topic the exported images are now "sized" much bigger (29"x20" for what should have been ~5"x7"), and hence expectantly I haven't lost any resolution, but it's aggrevating to have the dpi changed.
Can anyone tell me how to export without having the dpi changed?
And while I'm at it, can anyone confirm that I'm not loosing image resolution?
Thanks so much!!

Can anyone tell me how to export without having the dpi changed?
Can't find any other settings to change and just having tested it I can confirm that it sets ppi (it is pixels per inch -ppi- for a digital file which is made from pixels and dots per inch -dpi- from the ink dots of a print ) to 72.
And while I'm at it, can anyone confirm that I'm not loosing image resolution?
You already stated yourself that you did not loose pixels, therefor the size of the files stays the same. It is just a mater of figures. 300 ppi means a larger concentration per inch and 72 pixels per inch means a smaller concentration of pixels per inch. Given the same amount of pixels for both settings this means a smaller image dimension for 300 ppi and a larger image dimension for the 72 ppi.
300 ppi is some 'magic' number from printed press, but it really depends on the need of the job related printing machine. If you have a small image and need to look closely it should have a larger concentration per inch to reflect its sharpness.
However theoretically you would almost have the same visible quality when printed on 72 at billboard sizes. That's because you always have a large distance between your eyes and the bill board. If you look closely you will see the dots (because the billboard is a product of ink dots…) but of course it is not meant to study at that close range.
The same is for judging sharpness on your computer. Ideally you do so at 100 % for correct judgement at real size pixels. But in reality there will be almost no situation you will study a print at that same distance
Any thoughts on why these would be different? And am I fretting over things unncessarily?
Only guesses, the use a different algorithm or calculation scheme, in my case I tried a Canon Raw (converted to DNG) without any ACR settings then the basics applied and found that Bridge export jpeg 11 creates larger files then using PS.
But there are some other concerns I have and that certainly would make me fretting in use of export module:
First of all I almost never use it, merely in this cases for testing, because using the menu tools give a shortcut to Photoshop / Batch and inhere I have created several dedicated resizing and resaving actions that also places the files in preset folders.
But with this small test I found out that
a: it changes ppi to 72 ppi, not a very big deal but I did not asked for it nor did I wanted it.
b: it converts my Adobe RGB color space to sRGB and I certainly did not want that without my explicit wish for this conversion, so this is more then a bit worrying to my concern.
c: it seems to apply a sharpness that I certainly did not want to happen without my knowledge, and this rules the use of the export module out completely.
Since I only tried a DNG file without settings or retouch/developing in Photoshop the jpeg generated by PS was not very sharp. This makes sense to me because I have set my basic ACR to apply sharpening only to preview. There are a lot of different sharpening theories around but I use one in PS itself. So I was a bit shocked to learn that the export module did all those for me unwanted and not adjustable settings putting me completely out of control…
So if you want to have full control about things happening under the hood yourself just start creating actions in PS, it is very easy to record an action and even more easier to play it. Instead of every time dragging files to export module and always recheck the image options (it seems to reset itself always to jpeg quality 8 on my system) only select the files you want to resize and choose menu tool / Photoshop Batch and select the wanted action. hit OK and your almost done, PS does the rest.
The great thing of the latest PS CS6 action pallet is the extension with a so called 'insert conditional' that let's you create an 'if - then else' action for both landscape and portrait resizing actions so you don't need the 'constrain to fit' or 'fit image' option. Just once create an action for both resizing dimensions and then create a new action with insert conditional. choose If image is landscape play action…. / else play action….
It is really a very productive way. I have a lot of actions (organized in sets for better overview) and even one that creates 4 different sizes in 4 different folders using 1 go in Bridge

SRGB instead of ProPhoto or Adobe1998

sRGB instead of ProPhoto or Adobe1998
Hello to all ...
Why use ProPhoto or Adobe1998 color spaces in Lightroom (or even Photoshop cs3),
specially in what concerns to jpeg images, if many ( not all ) of specialized
printing enterprises will only adept sRGB to ( forcing me to convert them to this
color space after all editing work) ?
And, besides this, in my opinion, using sRGB has the advantage of being well interpreted by third party programs.
Please comment in detail if there is any the inconvenient of using sRGB !
Lots of thanks in advance,
Miguel Garcia

>Please comment in detail if there is any the inconvenient of using sRGB !
Well if you are shooting JPEG, staying in sRGB (in Photoshop) wouldn't be such a bad thing. But, Lightroom and Camera Raw were designed first and foremost as raw processors. There are a lot of reasons why one would want PP RGB or A RGB since your camera sensor is capable of capturing a lot more color than sRGB and many printers can print colors outside of sRGB.
But, if you are commenting on why Lightroom uses a linear ProPhoto RGB color space as it's processing space, well, I suspect you need to learn a bit more about image processing to really understand it. LR is using a linear (gamma 1.0) version of ProPhoto RGB in order to contain all colors any files can have to reduce errors and clipping. Processing JPEG & TIFF files as well as raw files benefit from the large gamut of color and the linear space.
The fact that photo labs require sRGB has more to do with lowering expectations (most people's displays are in sRGB so they'll get what they see) and the fact that the labs aren't too keen on having to hire knowledgeable (and costlier) personnel. Not all photo labs are, uh, so backwards...Costco, a low cost chain store actually has custom profiles one can download for most of their stores. An examination of their profiles reveals that Costco's printers (the same ones used by the "other photo labs" demanding sRGB) do indeed have a gamut of color larger than sRGB.
So, you use what you want. If you want to use sRGB, that's ok since that's one of the color spaces you can export in. But, I'll stick with ProPhoto RGB for everything other than images going to the web.

"/" key in bridge batch rename but instead it puts an "_"

Hi Guys
having problem with CS5! i want to type out the "/" key in bridge batch rename but instead it puts an "_". ANY HELP!?

"/" is an invalid character in filename of Windows file system, so Batch Rename automatically changes it to "_".
A filename can't contain following characters: \/:?*<>"|

Open with External Editor Profile sRGB instead of Adobe RGB

Hi,
I know in the export presets I can adjust what profile aperture will use. But what about when I open with External Editor. I like doing this because I can open my image in PhotoShop make my adjustments then save it and have aperture manage my files. But when I do this it opens the file with Adobe RGB, my lab and I sometimes want Adobe RGB. How can I change this without exporting the file and reimporting the file. Thanks.

Aperture uses a color space larger than AdobeRGB and sRGB. When an image is sent to Photoshop is converted to a 16bit AdobeRGB PSD file in order to get the largest color space to work with.
sRGB would be necessary when exporting to the web and/or send it to a printer that requieres that color profile, and that's why you have it in the export presets.

Color shift when exporting to sRGB (mac)

I just noticed the following: when I export an image (shot with my Nikon D80, RAW, developed from within Lightroom 2) as JPEG, 100%, sRGB color space, I get a strange color shift towards red, more saturated colors. Everything looks great when I view my image after export from within Finder or Apple Preview. However, when I drag that same file into the browser (Firefox) or then order prints from a photo service, the heavy red color shift is noticable. I've attached an image for you guys to see what I mean.
What am I doing wrong? Can someone please help?
I'm thinking that it might have to do with my color calibration? (I calibrated my monitor using the Spyder3 Elite device)
Edit: By the way, I just turned off my color calibration (changed display profiles), but that didn't fix the problem. Also, the color shift is not visible in Safari (I guess it is able to handle color profiles and Firefox isn't). But still, the color shift is there if I upload photos to a photo printing service and order prints. So, maybe there's something wrong with the color profile that Lightroom embeds in the JPEG file??

Problem continues (2)...
...from both Nikon and Canon RAW sources (I use a 5D MkII), but is it an LR3 issue or a Mac issue? Having read all the posts, I'm still struggling, but here's my contribution.
A while ago I noticed that colour files, once uploaded to the net, were way too red and saturated as per image below. Resolutions attempted so far below (all to no avail):
Tested different web browsers; found Firefox and Safari to be similar (to each other), Chrome very much brighter, but none of them are even close to original, so I'm not sure the Firefox loss of colour management mentioned by another contributor explains the issue.
Change web display vehicle; I find the same on my new web site as I did on Jalbum and various others.
Calibrate monitor (of course). Screen to output is 99% perfect on this monitor, when soft proofed with correct ICC profiles, so I very much doubt the wide gamut monitor is at fault. (I do find it hard to agree with the notion of it being the wide gamut screen. The whole point of a wide gamut screen is that it cn show a wider range of colours (e.g. in Adobe 98), and when an image's colour space is reduced (e.g. to sRGB) a wide gamut screen can still show that - especially if it is the same screen that didn't have this problem a year ago...).
Looked at images on a narrow-gamut screen. Same problem.
Changed colour space from Adobe 98 to ProPhoto in LR3 & CS3. Suspected mismatch between LR3 and CS3 because RAW files converted to DNG and edited in LR3, then pixel edited in CS3 and returned to LR3, come back in a different colour. Using ProPhoto has resolved that particular problem, but made no difference to faulty JPG display once on net.
Tested JPG conversion compared to other file formats; match between JPG and original RAW and PSD files perfect, whether displayed in LR3, CS3 or Preview, and whether exported to JPG from LR3, CS3 or Bridge. Problem definitely only occurs once images are on web.
Does anybody know anyone who doesn't have this issue and is using LR3 on a Mac with CS3 and OS 10.5.8?
Any updates or new ideas most welcome.

Export using sRGB IEC61966-2.1 color profile

HI,
I want to export some photos, in JPG format using color profile sRGB IEC61966-2.1. In the "Export to Hard Drive" dialog box I see where to select the color space where I can select sRGB, AdobeRGB (1998), ProPhoto RGB, or Other. When I select "other" I see a list of color profiles but sRGB IEC61966-2.1 is not included in the list.
How can I add sRGB IEC61966-2.1 to this list?
Thanks -- Dan

LR uses the standard v 2 profile (sRGB IEC61966-2.1) as I stated. You can, from the print module, replace it with a v 4 profile (sRGB_v4_ICC_preference. ). Of course this won't be used by any browser except Safari, may confuse print services, but does give some better results, unfortunately until at least Firefox sorts out their reluctance to allow v 4 profiles (and of course IE is beyond redemption) it isn't worth it. I wonder if Adobe will ever default to the v 4?

Adobe Bridge - Export - Manual Scale - Image Size Option

I would like to use Adobe Bridge to export a batch of images to a fixed height (e.g. 400px) where the width is dynamic. There are other software programs that would give me this option, but It would be wonderful if this "small feature" could somehow be added to adobe photoshop.
Thank you,
jjchinquist

Hello 1.csuebele, thanks for the comment.
I was surprised that this was in Photoshop and not in the Bridge, but that is ok.
I was not allowed to leave the width blank, nor enter -1 or 0 for variable. I worked around it by using a width that was so large, it would never be used because the maximum height would be used. For example width: 9000, height: 400.
Unfortunately in Photoshop scripts, there seem to be no method to override the image proportion so that I could force a thumbnail of 400 wide and 300 high.
After all that though, here is the result, thank you. http://www.ots.at/jahresrueckblick/2013/

Slice Exports as table instead of Div

Using FW CS5, when I export a sliced image to .htm file, the contents are all in a <table> format instead of as <div> tags, for example;
<table style="display: inline-table;" border="0" cellpadding="0" cellspacing="0" width="1024">
<tr>
<td colspan="3"><img name="background_r1_c1" src="background_r1_c1.png" width="1024" height="26" border="0" alt=""></td>
</tr>
Here is the image I'm trying to slice. All the images are created ok, but no .css file is generated. As you can see there are essentially 4 boxes with some overlapping, do I need to create each box as a separate image?

Linda,
Thanks for the response, however the link you provided is for CS3, not CS5 like I mentioned. Although in your defense the steps outlined are similar to what I read in the Help pages, http://help.adobe.com/en_US/fireworks/cs/using/WSF26E374A-45C0-482b-92E7-8BBA71F98D8D.html
I was able to get the image to export <div> layouts, however they were less than ideal, so I used Visual Web Developer to create the fixed position tags, it actually took less time to do than it did to write this response.

LR2: export jpg sRGB vs. print to jpeg sRGB - Same colors in MS explorer preview?

Hello !
Im using LR2 and do have problems understanding why "printing" to jpeg and exporting to jpeg give different results (colorwise) in the following case:
The first picture was exported using "jpeg" file format and "sRGB" color space.
The second picture was "printed" to jpeg using "sRGB" profile and rendering intend etiher "perceptual" or "relative" (doesn't matter).
I was just wondering, why in explorer preview(MS Windows XP sp3 with a calibrated monitor) colors of both pictures look different. The "printed" jpeg does have less red in it.
shouldn't the look the same in this case?
Did I miss something here?
Any hints appreciated.
Thank you very much
Sokrates

Hello,
thanks for pointing me to the related threads.
Indeed the results of the LR2 functions "print to jpeg" and "slideshow to jpeg" are dependent of the current monitor profile being used.
Here are my expamples:
http://www.tiga-online.de/downloads/comparison.jpg
if you have a closer look, it becomes more obvious:
upper left picture:
http://www.tiga-online.de/downloads/P5248984_print_sRGB_with_sRGB_monitor_profile.jpg
upper right picture (which shows different color):
http://www.tiga-online.de/downloads/P5248984_print_sRGB_with_sypder_profile.jpg
lower left picture:
http://www.tiga-online.de/downloads/P5248984_export_sRGB_with_sypder_profile.jpg
lower right picture:
http://www.tiga-online.de/downloads/P5248984_export_sRGB_with_sRGB_monitor_profile.jpg
Thanks again
Sokrates

ExtendScript CS5 - Bridge - Exporting JPEGs as 300DPI from PSDs

I know that Bridge has an Export menu that can be used to convert PSDs to JPEG and then convert them, but I can't figure out how to get access to these functions through the ExtendScript API.
I basically have an array of Thumbnail objects that I need to iterate through and export out 300 DPI JPEGs as I go.
Any ideas? I've already read through the manuals and didn't find anything of use.
My current relevant line looks like:
bm.exportTo(new File(exportFilePath),100);

You best drop this question in the dedicated Bridge scripting forum:
http://forums.adobe.com/community/bridge/bridge_scripting
Personally I would PS itself for this and create an action for this and the 300 ppi miracle figure is just what is, a figure, no more no less.
Many confuse it with dpi (dots per inch) but this is about the density of the ink dots used for printing. Ppi (pixels per inch) is the common term for digital images (that are made out of pixels, not ink dots… )
As long as you don't alter the amount of pixels you can use whatever figure you want without changing the total amount of the pixels, it just means the width and height are extended or increased because of the total amount of pixels used per inch. Anyone can alter this again without consequence for the image quality of the original file, as long as you don't start recalculating pixels to enlarge the or decrease the file size.
That said, In CS6 you have the option to create an action for both landscape and portrait using image / image size and fill in 300 pixels per inch and be sure to have the resample option unchecked. Also record a save action and without touching the original filename (if you do it records this also and overwrite each file with the new one) and choose a folder.
Create a new action and use 'insert conditional' (fly out menu top right of action panel) and choose the landscape action to play for landscape file, else: portrait.
Select the files in Bridge, use menu tools / PS / batch and select your action, hit OK and you are done.
You can also create a droplet but sadly enough you can't see them in Bridge and drop files on, but you can drag them to the desktop to let the action play.
Plenty of options I would think

[SSRS 2012] export to html (instead of mhrml) without attach file

Dear all,
I enable export to HMTL format on reporting services. But the issue is the file is sending in attachment instead of seing directly on mail body.
How I can have my report directly on mail (like MHTML export, but didn't work here (mail are sending, but exchange send a return error with message :
"This message exceeds the maximum message size allowed. Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller --
by removing attachments, for example -- and try sending it again, or provide the following diagnostic text to your system administrator." )
Thanks in advance,
BR

Hi phoneix75,
According to your description, you want to export your report into HTML format and display the report directly in the email instead of using an attached file. Right?
In Reporting Services, we can export a report into different format (MHTML, CSV, Excel…). For these type of files, only MHTML file can be displayed in email directly because Exchange/Outlook can only render MHTML format. It can’t recognize other format so
that they can only be kept in attached file. For an email, it also has max size for its content area. So if your report exceed this max size, it will come out the error message as you post. Unfortunately, your requirement can’t be achieved currently.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Metadata bridge export to Oracle9i OLAP

When I export a collection to Oracle9i OLAP using the Metadata Bridge, not all of the attributes are carried over. For instance, in my TIME dimension, Ihave columns for MONTH_END_DATE, MONTH_SHORT_NAME, MONTH_LONG_NAME, MONTH_TIME_SPAN. When I view the dimension attributes in OEM, the short_description and long_descriptoion fields both show MONTH_LONG_NAME. How do I get the MONTH_SHORT_NAME attribute to register in OLAP? Using OWB Client 9.2.0.3.0

Hi,
Given the naming conventions required by OLAP, and the fact that most dimensions have multiple attributes which cannot all end with the suffix _NAME, is there a plan to update the metadata bridge so that all the required meteadata is created by the bridge?

OLAP Bridge export

I keep getting the following error message when I try to create the AW, OLAP export file.
**! Transfer logging started at Tue Sep 28 15:58:19 CDT 2004 !**
OWB Bridge processed arguments
**! Transfer logging stopped at Tue Sep 28 15:58:33 CDT 2004 !**
Am I doing the export right? We want to take advantage of OWB and the OLAP feature. I'm using OWB 10g.

From the log you mention it is difficult to understand what is the problem. Are you getting some additional error messages? And, most importantly ... what version of OWB/DB are you using?
Regards:
Igor

Bridge, export to Harddisc has gone missing?

Hello,
I just bought CS5.5, from 5.0. But since it's a new version, I uninstalled the 'old' one first and then installed the 5.5.
There's one thing that I'm missing and that's the ' export to harddisc' function.
In Bridge 5.0 I would select Export-> and under services there was 'harddisc'. then I could convert it to almost any other format.
In Bridge 5.1 there is only 'services' greyed out available, but I don't see the option Harddisc anywhere.
Tried reinstalling and review my settings, but can't find anything on this matter. Can anybody help me with this?
Thank you in advance!
With regards,
John

I don't have CS5.5 but on the web it looks like export is in Windows heading. Have your tried there rather than in Files?

Bridge exports to sRGB instead AdobeRGB

Similar Messages

Maybe you are looking for