Image Resizing/Editing Problems

hello,
i recently imported images from my digital camera and i wanted to resize the pictures..but i dont know how, i used iphoto...but i dont think it changed the resolution.
someone please help!
Thank you
Brad

Look at these links.
Resizing Photos for Emailing
http://www.apple.com/pro/tips/emailresize.html
Resize!
http://kstudio.net/
PhotoToolCM
http://www.pixture.com/software/macosx.php
SmallImage
http://www.iconus.ch/fabien/smallimage2/
ImageTool
http://www.macupdate.com/info.php/id/23281
ImageWell
http://www.xtralean.com/IWOverview.html
Resize JPEG Files
http://www.macworld.com/weblogs/macgems/2006/09/jpegresize/index.php
 Cheers, Tom

Similar Messages

Problem with attaching/uploading images after editing in Aperture

After I edit images in Aperture, I frequently have trouble uploading them to Flickr or attaching them to an email message because the attachment/uploading tool cannot find the image. When I go to Aperture to view images, the edited image is there; however, it does not appear among the images in the folder where it is stored when I attempt to attach it to an email message or upload it to Flickr. I've tried searching for it by image number and that doesn't help. This never happens to unedited images, only to the ones that have been edited. The issue tends to go away after some time - for example, when I try to repeat the action the following day, the image is "back" where it should be. However, simply restarting Aperture, Flickr, or my browser doesn't help. Obviously, this is extremely frustrating, as I edit virtually all my photos before sharing them. Has anyone experienced this issue and have you been able to figure out a solution? Thank you! Oh, one last note: I've never experienced this issue when editing images with other software, such as Photoshop or Picasa - it only comes up with Aperture.

Welcome to the user-to-user forum.
Aperture creates the adjusted images as needed, on-the-fly, from the adjustment instructions saved in the Version file. Aperture also keeps Previews of these images, both for its own use, and to share with other applications when a lower-resolution JPG is sufficient. That is why you cannot find your images using Finder or other "File→Open" attempts (which is what you seem to have been trying).
(Previews are worth learning about. Consult the User Manual (a/k/a the Help file).)
In order to create a file, you must export your adjusted Version using Aperture.
Any application which has access to the OS X Media Browser (Mail does) can access these Previews.
There is a free utility which gives similar access to all applications: iMedia Browser. It looks good, but I haven't used it enough to comment.
You should also be able to access images of your adjusted Versions via the "Media" category which shows at the bottom of the sidebar of applicable OS X "File→Open" dialogs.
But the easiest way to email a image from Aperture is simply to use the toolbar icon or the keyboard shortcut "{Option}+e". Select an email program and an image exporting preset (which sets the size and other parameters) via "Aperture→Preferences→Export".
Others may have advice for Flickr. I don't use it.
Message was edited by: Kirby Krieger

LR3-Library-Export-Image Resizing: Specifying Pixel WxH results in different WxH - tips please?

This is a multi-dimensional question (he he). I understand my problem is related to the original/developed WxH ratio. If the pixel WxH I spec in Export-Image Resizing doesn't match that developed proportion, the results are not what I want. In other words LR3 keeps the original/developed proportion and not what I want for that export. Ok, so I just answered my own question - but..... please give me some library or export tips for doing what I want to do.
What I do:
1 - I edit my images in RAW and like to keep them in their original proportions from my Canon camera as that is the proportion of HxW i use the most
2 - Later, if the image is really good (at least I like it), I may export it for different purposes and then may choose or require a different proportion.
3 - I would really like to not have to re-crop in Develop, then go back and Export, then go back to Develop and change it back to original.
Besides being tedious and time consuming, can anyone recommend a better way for me to do these "one off" exports (seems to happen more often lately) without screwing around in Develop and messing up my original work?
Background:
One of the reasons I do this is to create wallpapers for computers, for various printing/framing proportions, and then for web site situations. Windows XP (and I think the others) gets really slow if the program must re-size an image for wallpaper (why? go ask Mr. Gates... better get in line). So to keep performance high, it is best to create the image in the exact pixel dimensions of the monitor. This is always some weird number and not like anything else I do this for. The other reason is for a quick, custom print job for someone who wants an odd matting setup for framing (don't ask). This results in odd proportions. Regarding the web.... well smooshing a pic into a column etc. etc... Now while I am proud of my art and understand LR3 will expect me to re-crop to preserve my artistic brilliance, but really..... I would be happy with a proportional crop from the parallel sides of the offending dimension.
Also, when I spec a dimension, shouldn't the DPI gray out? What am not understanding here?
One last request: please give me tips on solving for world peace... this one really bugs me.
Thanx in advance!

Bruce,
As you correctly noticed, the WxH ratio in export represents a canvas, into which the exported image is fit. Here are some illustrations on what the different settings mean:
For what you are trying to achieve, you have to crop the image to the correct dimensions before doing the export. If I had to do it, I would create virtual copies of the original image as the last step and give each virtual copy its own crop, then export the virtual copies.
Bruce in Philly wrote:
Also, when I spec a dimension, shouldn't the DPI gray out? What am not understanding here?
The DPI resolution has no meaning for the size of the resulting image if you specify pixels in your export dimensions. But the resolution tag is written into the image, which might affect the way an image is printed, depending on the printing application.
But if you specify your export dimensions in inches or cm, the resolution together with the dimensions in inch/cm determine the size of the resulting image in pixels. I.e. if you specify 5x7" and 300DPI, your exported images size will be 1500x2100 pixels.
Beat

Is it possible to optimize this Bilinear Image Resizing Method more?

I'm trying to write a speedy bilinear image resizer, for displaying images so it doesn't need to me 100% accurate, just look correct.
So far i've come up with
 public static final Image resampleImage(Image orgImage, int newWidth, int newHeight) {
 int orgWidth = orgImage.getWidth();
 int orgHeight = orgImage.getHeight();
 int orgLength = orgWidth * orgHeight;
 int orgMax = orgLength - 1;
 int[] rawInput = new int[orgLength];
 orgImage.getRGB(rawInput, 0, orgWidth, 0, 0, orgWidth, orgHeight);
 int newLength = newWidth * newHeight;
 int[] rawOutput = new int[newLength];
 int yd = (orgHeight / newHeight - 1) * orgWidth;
 int yr = orgHeight % newHeight;
 int xd = orgWidth / newWidth;
 int xr = orgWidth % newWidth;
 int outOffset = 0;
 int inOffset = 0;
 // Whole pile of non array variables for the loop.
 int pixelA, pixelB, pixelC, pixelD;
 int xo, yo;
 int weightA, weightB, weightC, weightD;
 int redA, redB, redC, redD;
 int greenA, greenB, greenC, greenD;
 int blueA, blueB, blueC, blueD;
 int red, green, blue;
 for (int y = newHeight, ye = 0; y > 0; y--) {
 for (int x = newWidth, xe = 0; x > 0; x--) {
 // Set source pixels.
 pixelA = inOffset;
 pixelB = pixelA + 1;
 pixelC = pixelA + orgWidth;
 pixelD = pixelC + 1;
 // Get pixel values from array for speed, avoiding overflow.
 pixelA = rawInput[pixelA];
 pixelB = pixelB > orgMax ? pixelA : rawInput[pixelB];
 pixelC = pixelC > orgMax ? pixelA : rawInput[pixelC];
 pixelD = pixelD > orgMax ? pixelB : rawInput[pixelD];
 // Calculate pixel weights from error values xe & ye.
 xo = (xe << 8) / newWidth;
 yo = (ye << 8) / newHeight;
 weightD = xo * yo;
 weightC = (yo << 8) - weightD;
 weightB = (xo << 8) - weightD;
 weightA = 0x10000 - weightB - weightC - weightD;
 // Isolate colour channels.
 redA = pixelA >> 16;
 redB = pixelB >> 16;
 redC = pixelC >> 16;
 redD = pixelD >> 16;
 greenA = pixelA & 0x00FF00;
 greenB = pixelB & 0x00FF00;
 greenC = pixelC & 0x00FF00;
 greenD = pixelD & 0x00FF00;
 blueA = pixelA & 0x0000FF;
 blueB = pixelB & 0x0000FF;
 blueC = pixelC & 0x0000FF;
 blueD = pixelD & 0x0000FF;
 // Calculate new pixels colour and mask.
 red = 0x00FF0000 & (redA * weightA + redB * weightB + redC * weightC + redD * weightD);
 green = 0xFF000000 & (greenA * weightA + greenB * weightB + greenC * weightC + greenD * weightD);
 blue = 0x00FF0000 & (blueA * weightA + blueB * weightB + blueC * weightC + blueD * weightD);
 // Store pixel in output buffer and increment offset.
 rawOutput[outOffset++] = red + (((green | blue) >> 16));
 // Increment input by x delta.
 inOffset += xd;
 // Correct if we have a roll over error.
 xe += xr;
 if (xe >= newWidth) {
 xe -= newWidth;
 inOffset++;
 // Increment input by y delta.
 inOffset += yd;
 // Correct if we have a roll over error.
 ye += yr;
 if (ye >= newHeight) {
 ye -= newHeight;
 inOffset += orgWidth;
 return Image.createRGBImage(rawOutput, newWidth, newHeight, false);
 }I was wondering if anyone can see any problems with this, or suggest any faster ways of doing this.
Thanks
Edited by: chris.beswick on Nov 5, 2008 3:24 AM
Edited by: chris.beswick on Nov 5, 2008 3:40 AM - Changed title to reflect what I am after.

Thanks for the reply.
Sadly, both the methods in the link are for simple nearest neighbour resizing, which looks god awefull. In addition the first one on the page is insanely slow only only needed with much versions of J2ME that do not support directly accessing pixel data from Image (via getRGB()).
I started with something like the second example, and have them tweaked it down while adding in the weighted re sampling of the 4 nearest pixels, to remove jaggies. I've managed to get my "bilinear" version to be only around 4 times slower than nearest neighbour, which given that it reads 4 times the data for each pixel is not bad... just wondering if I can go any faster :D
My current intention is it use a fast nearest neighbour while the image is being moved around / zoomed, and then when there is a pause in user input update the image with the bilinear image.
Also, I'm trying to use variables (xA, xB, xC, xD) in place of arrays(x[0], x[1]. x[2]. x[3]) as I've read somewhere it is faster as there is no need for bounds checks when accessing a variable unlike an array,
Finally, does anyone have any good ideas on using bit shifting to approximate all the multiplication (ie x << 8 instead of x * 256) of the pixels by weights, the resulting answer may be "wrong" but if it is close enough it might work.
Chris
Edited by: chris.beswick on Nov 5, 2008 4:14 AM

Images as Buttons and Image Resizing in mxml

Sorry for all the questions but I've run into a problem when trying to create buttons that are just an image in mxml. When I first tried this I couldn't find a way to get the border around the button to dissapear so it ended up looking like my image had an extra black border around it. Then someone here suggested I just set the buttonMode property of an mx:Image to true which ended up working fine to a point. The problem I'm having is that even if I make the tabEnabled property of the image (that I'm using as a button) true, I can't tab over to it. Is there a way to either get rid of the black borders of a button or to make it so I can tab over to an image I'm using as a button?
My second question has to do with image resizing. Lets say I have an image of a horizontal line that I want to put at the top of the mxml page, and I want it to extend the full length of the page, even after the user has resized the browser. Is there a way to do that? I've tried putting the width as 100% or giving the image a "left" and "right" value so that presumably it would be stretched to fit within those but nothing has worked so far. Is there no way to do this or am I doing something wrong?
Thank you for any help you guys can give.

Of course, sorry about that. So the following is a barebones example of how I currently implement buttons and images as buttons:
<mx:Button id="facebookButton" icon="@Embed(source='image.png')" width="30"/>
<mx:Image buttonMode="true" id="button" source="anotherimage.png" enabled="true" click="{foo()}"/>
And within the image I've tried making the tabFocusEnabled property true but to no avail.
The following is how I've tried stretching out an image across the whole page:
<mx:Image source="yetanotherimage.png" width="100%" scaleContent="true"/>
<mx:Image source="yetanotherimage.png" left="10" right="10" scaleContent="true"/>
Is this more helpful?

Exclamation mark comes up instead of image to edit - why?

When double clicking an image to edit, some images appear as blank dark grey screens with an exclamation mark in the middle so can't be edited. Others open up normally.I think this has happened since I updated to iPhoto 6.0.6 but can't be sure. Is there any way of solving this problem?
MacBook Mac OS X (10.4.9)

Judy:
That indicates that the library has lost its link to the original imported file. That can happen if the user moves or renames files or folders within the iPhoto Library folder from the finder or the there's an interruption while iPhoto is writhing to its database file, Library6.iPhoto.
You can try rebuilding the library as follows: launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library. Select the first three options.
If that does not work you'll have to start over with a new library as follows:
Creating a new library while preserving the rolls from the original.
Move the existing library folder to the desktop.
Launch iPhoto and, when asked, select the option to create a new library.
Drag the Originals folder from the iPhoto Library on the desktop into the open iPhoto window.
This will create a new library with the same rolls as the original library. However dates on the rolls may be different but can be edited as you would the roll title.
Once this is completed you can delete the Originals folder from the desktop and the iPhoto Llibrary folder. If desired, you can keep the older library folder to try other fixes on it.
In the future I recommend you make a backup copy of the Library6.iPhoto file after each import and after doing a lot of editing and organizing in the library. Then if you experience a similar crash all you need to do is replace the damaged database file with the backup copy and you'll be back to the same place in the library as when you make the backup. See the tip at the end of my signature.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto 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 written an Automator workflow application (requires Tiger), 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. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Why won't Photoshop revert to earlier history state after image resize when scripted?

I've written an Applescript to automate watermarking and resizing images for my company. Everything generally works fine —　the script saves the initial history state to a variable, resizes the image, adds the appropriate watermark, saves off a jpeg, then reverts to the initial history state for another resize and watermark loop.
The problem is when I try not to use a watermark and only resize by setting the variable `wmColor` to `"None"` or `"None for all"`. It seems that after resizing and saving off a jpeg, Photoshop doesn't like it when I try to revert to the initial history state. This is super annoying, since clearly a resize should count as a history step, and I don't want to rewrite the script to implement multiple open/close operations on the original file. Does anyone know what might be going on? This is the line that's generating the problem (it's in both the doBig and doSmall methods, and throws an error every time I ask it just to do an image resize and change current history state):
 set current history state of current document to initialState
and here's the whole script:
property type_list : {"JPEG", "TIFF", "PNGf", "8BPS", "BMPf", "GIFf", "PDF ", "PICT"}
property extension_list : {"jpg", "jpeg", "tif", "tiff", "png", "psd", "bmp", "gif", "jp2", "pdf", "pict", "pct", "sgi", "tga"}
property typeIDs_list : {"public.jpeg", "public.tiff", "public.png", "com.adobe.photoshop-image", "com.microsoft.bmp", "com.compuserve.gif", "public.jpeg-2000", "com.adobe.pdf", "com.apple.pict", "com.sgi.sgi-image", "com.truevision.tga-image"}
global myFolder
global wmYN
global wmColor
global nameUse
global rootName
global nameCount
property myFolder : ""
-- This droplet processes files dropped onto the applet
on open these_items
-- FILTER THE DRAGGED-ON ITEMS BY CHECKING THEIR PROPERTIES AGAINST THE LISTS ABOVE
 set wmColor to null
 set nameCount to 0
 set nameUse to null
 if myFolder is not "" then
 set myFolder to choose folder with prompt "Choose where to put your finished images" default location myFolder -- where you're going to store the jpgs
 else
 set myFolder to choose folder with prompt "Choose where to put your finished images" default location (path to desktop)
 end if
 repeat with i from 1 to the count of these_items
 set totalFiles to count of these_items
 set this_item to item i of these_items
 set the item_info to info for this_item without size
 if folder of the item_info is true then
process_folder(this_item)
 else
 try
 set this_extension to the name extension of item_info
 on error
 set this_extension to ""
 end try
 try
 set this_filetype to the file type of item_info
 on error
 set this_filetype to ""
 end try
 try
 set this_typeID to the type identifier of item_info
 on error
 set this_typeID to ""
 end try
 if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
-- THE ITEM IS AN IMAGE FILE AND CAN BE PROCESSED
process_item(this_item)
 end if
 end if
 end repeat
end open
-- this sub-routine processes folders
on process_folder(this_folder)
 set these_items to list folder this_folder without invisibles
 repeat with i from 1 to the count of these_items
 set this_item to alias ((this_folder as Unicode text) & (item i of these_items))
 set the item_info to info for this_item without size
 if folder of the item_info is true then
process_folder(this_item)
 else
 try
 set this_extension to the name extension of item_info
 on error
 set this_extension to ""
 end try
 try
 set this_filetype to the file type of item_info
 on error
 set this_filetype to ""
 end try
 try
 set this_typeID to the type identifier of item_info
 on error
 set this_typeID to ""
 end try
 if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
-- THE ITEM IS AN IMAGE FILE AND CAN BE PROCESSED
process_item(this_item)
 end if
 end if
 end repeat
end process_folder
-- this sub-routine processes files
on process_item(this_item)
 set this_image to this_item as text
 tell application id "com.adobe.photoshop"
 set saveUnits to ruler units of settings
 set display dialogs to never
open file this_image
 if wmColor is not in {"None for all", "White for all", "Black for all"} then
 set wmColor to choose from list {"None", "None for all", "Black", "Black for all", "White", "White for all"} with prompt "What color should the watermark be?" default items "White for all" without multiple selections allowed and empty selection allowed
 end if
 if wmColor is false then
 error number -128
 end if
 if nameUse is not "Just increment this for all" then
 set nameBox to display dialog "What should I call these things?" default answer ("image") with title "Choose the name stem for your images" buttons {"Cancel", "Just increment this for all", "OK"} default button "Just increment this for all"
 set nameUse to button returned of nameBox -- this will determine whether or not to increment stem names
 set rootName to text returned of nameBox -- this will be the root part of all of your file names
 set currentName to rootName
 else
 set nameCount to nameCount + 1
 set currentName to rootName & (nameCount as text)
 end if
 set thisDocument to current document
 set initialState to current history state of thisDocument
 set ruler units of settings to pixel units
 end tell
DoSmall(thisDocument, currentName, initialState)
DoBig(thisDocument, currentName, initialState)
 tell application id "com.adobe.photoshop"
 close thisDocument without saving
 set ruler units of settings to saveUnits
 end tell
end process_item
to DoSmall(thisDocument, currentName, initialState)
 tell application id "com.adobe.photoshop"
 set initWidth to width of thisDocument
 if initWidth < 640 then
resize image thisDocument width 640 resample method bicubic smoother
 else if initWidth > 640 then
resize image thisDocument width 640 resample method bicubic sharper
 end if
 set myHeight to height of thisDocument
 set myWidth to width of thisDocument
 if wmColor is in {"White", "White for all"} then
 set wmFile to (path to resource "water_250_white.png" in bundle path to me) as text
 else if wmColor is in {"Black", "Black for all"} then
 set wmFile to (path to resource "water_250_black.png" in bundle path to me) as text
 end if
 if wmColor is not in {"None", "None for all"} then
open file wmFile
 set wmDocument to current document
 set wmHeight to height of wmDocument
 set wmWidth to width of wmDocument
duplicate current layer of wmDocument to thisDocument
 close wmDocument without saving
translate current layer of thisDocument delta x (myWidth - wmWidth - 10) delta y (myHeight - wmHeight - 10)
 set opacity of current layer of thisDocument to 20
 end if
 set myPath to (myFolder as text) & (currentName) & "_640"
 set myOptions to {class:JPEG save options, embed color profile:false, quality:12}
save thisDocument as JPEG in file myPath with options myOptions appending lowercase extension
 set current history state of current document to initialState
 end tell
end DoSmall
to DoBig(thisDocument, currentName, initialState)
 tell application id "com.adobe.photoshop"
 set initWidth to width of thisDocument
 if initWidth < 1020 then
resize image thisDocument width 1020 resample method bicubic smoother
 else if initWidth > 1020 then
resize image thisDocument width 1020 resample method bicubic sharper
 end if
 set myHeight to height of thisDocument
 set myWidth to width of thisDocument
 if wmColor is in {"White", "White for all"} then
 set wmFile to (path to resource "water_400_white.png" in bundle path to me) as text
 else if wmColor is in {"Black", "Black for all"} then
 set wmFile to (path to resource "water_400_black.png" in bundle path to me) as text
 end if
 if wmColor is not in {"None", "None for all"} then
open file wmFile
 set wmDocument to current document
 set wmHeight to height of wmDocument
 set wmWidth to width of wmDocument
duplicate current layer of wmDocument to thisDocument
 close wmDocument without saving
translate current layer of thisDocument delta x (myWidth - wmWidth - 16) delta y (myHeight - wmHeight - 16)
 set opacity of current layer of thisDocument to 20
 end if
 set myPath to (myFolder as text) & (currentName) & "_1020"
 set myOptions to {class:JPEG save options, embed color profile:false, quality:12}
save thisDocument as JPEG in file myPath with options myOptions appending lowercase extension
 set current history state of current document to initialState
 end tell
end DoBig

As many others here I use JavaScript so I can’t really help you with your problem.
But I’d like to point to »the lazy person’s out« – with many operations that result in creating a new file on disk I simply duplicate the image (and flatten in the same step) to minimize any chance of damaging the original file if the Script should not perform as expected.

Photshop CS6 image resizing tool.

Five time I have entered a support question but it does not seem to appear in the lists nor have I had a response, am I entering my request incorrectly?
My request is:
I have a PC using Windows 7. I have Photoshop CS6 which I have been using for some time. Very recently the image, image size tool has stopped working. I open the drop down window and the current size of my image is displayed. I then try and type the required changed size in the box but the box does not accept it. The size remains the same. I have un-installed and re-installed CS6 and put in all the latest updates. The first image I tried, it allowed me to change the size. The second image the resize tool would not allow any changes. We were back to where we started. Elsewhere on the support FAQs it was suggested such problems might be cured by deleting \adobe photo cs6 prefs.psp file. This I have done but still I cannot resize my images.
Please can someone help me??

If Photoshop has been working well for you then start acting strange the first thing that should come to you mind is your Photoshop preferences. Your Photoshop preferences are Photoshop setting made for your user ID for how you want Photoshop to behave. Each user ID has there own set of Preference files. These are not installed or removed when you Install or uninstall Photoshop. So if you un-install and re-install Photoshop your Photoshop preferences remain intact. If the Problem you are having is caused by a corrupt Photoshop preference file. You will still have that same problem. Did you try resetting your Photoshop preferences?
Though the Image size dialog is simple many users do not really understand everything about image resizing. Using a quick look at the image we see three section Top, Middle and bottom..
Top section is basicly image file size how many pixels are there in the image.
Middle Image Print Size.
Bottom Image Resize Image Controls.
To understand Image Resize you must start from the bottom. In the bottom control section Resample Image is the single control that governs the whole resizing process. When "Resample Image" is NOT checked all other controls have no roll in the resize process they are grayed out as is the top file size section. The file size will not change the pixel will not change. Note all that is grayed out in the above image. All that can be change is the print size. The middle section and all three sizes there are tied together as shown by the lines and link icon. Change one size there and Photoshop will calculate the other two and display the proper values. All thee setting in the center are sizes associated with length. Width number uints, Height number uints. and Resolution number Pixel/unit. Resolution therefore is pixels size and pixels have an aspect ratio. Most image pixel these days are square 1:1 aspect ratio. Photoshop support non square pixels but can only display image using square pixels display have.
So when Resample is not checked. The image has a Width with a fixed number Pixel, a Height with a fixed number Pixels and Pixel aspect ratio. Setting any one print dimension will also set the other two dimensions.
When resample is check the other controls in the bottom section become useable and so does the top file section. Normally you should check Constraint Proportions link Width and Height so your image will not distort during the resize. When you resample an image you wind up with an entirely new image with a different number of pixels. Some image quality has been lost for you either through way some details you had or created some details you did not have. The image quality will depend on the quality of the pixels you had and how well the interpolation method used worker with those pixels. IMO Adobe Bicubic Automatic is not a good general purpose method to it tend to add many artifacts to image that have been sharpened.
In newer version of Photoshop CC and CC 2014 Adobe has redesigned the Image Size dialog adding a preview image display. Made the dimension link icon the constrain proportion control when resample is checked. Also hid the scale style option under a gear icon in the upper right corner.

PSE5 Process Multiple Files Image Resize

I want to batch convert some TIFF files to JPG and make them all 300 ppi. I tried suing the Multiple file processor in the Editor just entering 300 in resolution and leaving width & height blank. I hoped it would perform the same process as going to image resize and and changing resolution with resample and constrain proportions turned off. Instead it has changed the ppi from 72 to 300, but kept the size the same i.e. has added lots of extra pixels making the file enormous.
The only way I can force it to shrink the image is to enter say 30cm as the width. The problem with this is twofold a) I have to trun all my photos so they are landscape b) if I have cropped a photo such that it doesn't have enough pixels to stretch then again it is getting resampled.
Is this a limitation of PSE5 that wouldn't be there in CS3 or am I doing something wrong? I only want to print tham out 15x10 but read I should resize everything to 300 ppi. To be honest I never did this before I had PSE and they seemed to come out OK from a Canon that saves the files as default 72 ppi but large dimensions. Maybe someone couldexplain in laymans terms why the photos need to be resized to 300 ppi anyway? Thank you

Well, you see, Process Multiple files is doing just what you asked it to do: it's
resizing the photos. But you don't really want to resize the photos, just change the ppi setting. Is there a particular reason you want them to be 300ppi? PPI is a setting that only matters for printing or if you are sending a photo somewhere that requires that marker to be set to 300. Your camera doesn't know anything about ppi, only absolute pixel dimensions (eg 2480 x 1795 or whatever).
When you go to print, however, your printer may prefer to have a higher pixel density, since it can play your pixels like an accordian: squash them closer together or spread them out thinner, depending on that ppi marker. The pixel density determines the inch/cm size of your print (at 72 ppi you'll get a print that's hugely bigger but less detailed; at 300 ppi a crisper smaller print.)
I'm wondering why you would want to batch convert a whole big bunch of images at once, though. It would help if you would explain just what you want to do with the photos that requires the 300 ppi.

Image Resize Menu not available

According to Mail Help, when I insert an image into an email, there is supposed to be an image resize menu in the lower right portion of the window and a message size indicator in the lower left of the window. Neither of these are appearing for me. I have tried attaching an image in a number of different ways with the "insert attachment at end of message" both on and off. Any ideas out there?

I've got the same problem. It only occurred after upgrading to Leopard.
Before it worked fine. (Leopard is for me not a success on this moment: my pages just stopped working, can't connect via bleutooth to my phone anymore using addressbook, eyeTV also stops at random and restarts are occurring often. I'm starting to get that 'trow this stupid thing out the window' feeling i had during my MS windows era.

Slideshow image resizing when adding new images

I am creating a series of slideshows on multiple pages. I created one slide show using the "basic" slideshow and resized it to the dimensions and settings I wanted. I have many pictures all of different proportion, therefore, I selected the "fill frame proportionally" so they would all fit the dimension I set. I wanted to use this first slideshow as a template for all of the rest. I added images to this first slideshow with no problems. All of my different sized images scaled or cropped to fit within the dimension I set. The problem comes in when I do two things: 1) When I add other images of different dimensions to this same slideshow gallery, they come smaller that the intended dimensions I set previous. I check the setting and it is still on "fill frame proportionally" similar to the first batch of pictures. 2) The second issue is when copy this slideshow as a template to other pages. When I try to replace or add to the slideshow gallery, the images come in cropped or smaller rather than filling the frame. Again, the settings are still the same from my very first slideshow that worked just as i intended.
I could resize all the images to all the same dimensions using another program like photoshop, but that is another step that is very tedious and it would seem that it should be something built into Muse.
Is there a way around this?. Am I doing something wrong? Or is this just one of those glitches that happens with Muse? I appreciate any help that I can get.
Thanks!

Hi, I got it to work like this:
Using background colours in Photoshop so that all sizes are the same in pixels. Then manually adjusting thumbnails by double-clicking on them so that a red square appears.
Cheers,
Elsemiek
Op 26 dec. 2014, om 00:50 heeft MediaGraphics <[email protected]> het volgende geschreven:
slideshow image resizing when adding new images
created by MediaGraphics <https://forums.adobe.com/people/MediaGraphics> in Adobe Muse Bugs - View the full discussion <https://forums.adobe.com/message/7043933#7043933>
Hi there Elsemiekagain,
I had to fiddle around with my slide show to get it to work. That is, it worked at first, then went funky, and I had to fiddle. So much fiddling that I can't possibly know what actually made it start to work again.
And to some degree, this is the way that I find Muse to be in general. That it requires finessing to get it to work as expected. This adds a good deal of time to every development project, though I am getting better at this with practice and experience.
Most of it is not even things that could be easily put in words as instructions, as many are nanced. But in fairness, this version of Muse is a complete code re-write this year. So we do need to cut Adobe some slack, and give the team time to iron things out.
If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7043933#7043933 and clicking ‘Correct’ below the answer
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7043933#7043933
To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"
Start a new discussion in Adobe Muse Bugs by email <mailto:[email protected]ftware.com> or at Adobe Community <https://forums.adobe.com/choose-container.jspa?contentType=1&containerType=14&container=47 59>
For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624 <https://forums.adobe.com/thread/1516624>.

Aperture corrupting images during editing

Hello,
Starting a few days ago, aperture started corrupting images during editing. This was normally at the time of my fist cut, going through doing simple straighten and croping. Sometimes it would happen when doing a small lighten or darken of the exposure. I purchased a new MacBook Pro about a month ago but this only started happening this week. No OS or Aperture upgrades this week. I did have a crash earlier this week and after the crash my Spotlight re-indexed my computer. I updated QuickSilver this week and Awaken. I tried quiting both QS and Awaken but problem still happens. The real scary thing is I usally have to go back and re-import the raw CR2 image to fix the problem, doing an update from master or resetting all adjustments does not fix the problem. Below is an example of an image with the problem. This is a Version Export of a corrupted image, as you can see the cor Can I get any help?

Ernie Stamper:
The Aperture Libraries are on the local drive. I do have an external Firewire drive I can use to test your theory but since I recently replaced the whole laptop at the Apple store so I am thinking it is not hardware related but one of three things: an Aperture bug, my configuration, or memory (see more on memory below).
leonieDF:
I don't think it is related to a hardware issue unless it is memory. I took the laptop into the mac store because I was having a hardware issue not discussed in this thread. The laptop was completely replaced except for the memory since I purchased 8GB of memory after the computer was purchased. I put the 8GB memory back into the new laptop. If this is a memory problem it is not showing up in diagnostics. I am planning on doing two things this weekend. First thing is putting back in the original apply memory and testing. If I still get the issue I am going to do a complete uninstall of Aperture and re-install maybe something in my settings/libaries are corrupted. I am reaching for straws at this point. I might also try a complete reformat and only install Aperture and test to see if something else installed might be causing this, but I can't think of what it would be.

Please verify my account so i can post an image of my problem. Thanks. Adam.

Please verify my account so i can post an image of my problem. Thanks. Adam.

All future people who find this thread - Click the link below and look for the current verification thread as a sticky:
https://social.technet.microsoft.com/Forums/en-US/home?forum=reportabug
EDIT: Clarification - accounts will be automatically verified after 15
points have been accumulated.
Don't retire TechNet! -
(Don't give up yet - 13,225+ strong and growing)

Launch and edit problem from Dreamweaver to Fireworks

> This message is in MIME format. Since your mail reader
does not understand
this format, some or all of this message may not be legible.
--B_3266405159_588474
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
Hi
Not sure if this is a Fireworks or Dreamweaver problem but
here goes.
I¹ve created a graphic in Fireworks CS3 on the Mac and
Exported the HTML and
related images. I open the HTML file in Dreamweaver CS3, all
fine so far.
Then I highlight the table and click the Edit in
Fireworks¹ button and it
throws up a warning dialogue saying Cannot launch and
edit. The Fireworks
table could not be found in the HTML. Please export from
Fireworks and
re-import the HTML into Dreamweaver.¹
What?!!
I¹ve only just exported it from Fireworks! It¹s
even got the Fireworks table
code in the Code section, so what¹s going here?
Has anyone else had this?
Gaz
--B_3266405159_588474
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Launch and edit problem from Dreamweaver to
Fireworks</TITLE>
</HEAD>
<BODY>
Hi<BR=
>
Not sure if this is a Fireworks or Dreamweaver problem but
here goes. 
I’ve created a graphic in Fireworks CS3 on the Mac
and Exported the H=
TML and related images. I open the HTML file in Dreamweaver
CS3, all fine so=
far. Then I highlight the table and click the
‘Edit in Fireworks&#821=
7; button and it throws up a warning dialogue saying
‘Cannot launch an=
d edit. The Fireworks table could not be found in the HTML.
Please export fr=
om Fireworks and re-import the HTML into
Dreamweaver.’ 
What?!! 
I’ve only just exported it from Fireworks!
It’s even got the Fi=
reworks table code in the Code section, so what’s
going here? 
 
Has anyone else had this? 
 
Gaz
</BODY>
</HTML>
--B_3266405159_588474--

> This message is in MIME format. Since your mail reader
does not understand
this format, some or all of this message may not be legible.
--B_3266407908_747577
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
When you export the sliced graphics from Fireworks it places
them into a
table. In my instance the code says...

So it recognises Fireworks was the the graphics app and jumps
back to it
when you want to edit the image. Fireworks then displays (or
should) a
Done¹ button over the window. You do your alts and
press Done to update the
HTML and graphics back in Dreamweaver automatically.
That¹s the only table I was referring to Murray.
On 4/7/07 3:02 pm, in article
[email protected], "Murray
*ACE*" <[email protected]> wrote:
> Why would you be wanting to edit the table in a graphics
editor, instead of
> an HTML editor?
--B_3266407908_747577
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: Launch and edit problem from Dreamweaver to
Fireworks</TITLE>
</HEAD>
<BODY>
When =
you export the sliced graphics from Fireworks it places them
into a table. I=
n my instance the code says... 
 
 
 
So it recognises Fireworks was the the graphics app and jumps
back to it wh=
en you want to edit the image. Fireworks then displays (or
should) a ‘=
Done’ button over the window. You do your alts and
press Done to updat=
e the HTML and graphics back in Dreamweaver
automatically. 
That’s the only table I was referring to
Murray. 
 
On 4/7/07 3:02 pm, in article
[email protected], "Murr=
ay *ACE*"
<[email protected]> wrote: 
 
> Why would you be
wanting to edit the table in a =
graphics editor, instead of 
> an HTML editor? 

</BODY>
</HTML>
--B_3266407908_747577--

Batch image resizing

Hi,
Can anyone tell me what the limits on the image resizing in Photoshop is. I need to run a regular batch of image resizing on about 38,000+ images (quiet a lot). I've also been looking around for a tool that can handle this number of images to resize, does anyone know if Adobe has such a tool?
Thanks
Stephen

I don't think there is an easy answer for you, if the files are on a server then there could be horrendous problems. You might need a custom script that breaks the batch into chunks and controled by Bridge.
Scripting expert Xbytor, has written scripts for people that does this sort of batch processing over at PS-Scripts.com, he may be able to help.

Image Resizing/Editing Problems

Similar Messages

Maybe you are looking for