Kindle Export plugin No image resize

Hi there,
I do all my formatting in inDesign and export to ePub or mobi using the built in ePub export or the Kindle export plugin from amazon.
I've pretty much got the whole ePub thing sorted out but have come across a problem when it comes to exporting the mobi file. If i have images in the book they all seem to do their own thing with regards to size. I find that most of the images scale down and display a lot smaller than i would prefer on the kindle.
I've tried playing with the export settings, optimise vs original vs formatted, not formatted and nothing really changes. Also i've physically change the size of the image in the inDesign docuement and still, no change.
I'm hear as a last resort before I lose my mind. Anyone out there that can help?

The advise I got from the Kindle people when I had the same issue was to use Images/Copy Images/Original. Remember that users will have the ability to zoom out the images.

Similar Messages

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

How can I export an edited image to a file?

I can't seem to find a way in iPhoto 09 do this. Can I export an edited image to a file, keeping the edits intact, or do I have to use a 3rd party editing app when I edit from inside iPhoto 09?
I would prefer to use iPhoto's editing tools so should I import previously cropped images into iPhoto? If yes, what file should I use? I was wondering if anyone does this on a regular basis and if there issues doing this.
I like the editing tools in iPhoto very much. In other apps I have always cropped, resized, corrected levels and a bit of color. I am not a power user by any means and I am close to doing this all in iPhoto if I could only export the edited image to a file.
The reason I want to do this is because the printing portion of my work flow is to upload files to my merchant who prints them and are ready for nearby pickup within an hour. This is all done at a very reasonable price and the color accuracy is very close.
Any advice would be greatly appreciated.
Regards,
Jim

You can edit from iPhoto by dragging to the desktop or exporting using the File -> Export command, setting the Kind to anything except original.
But you probably don’t need to:
There are many, many ways to access your files in iPhoto:
*For Users of 10.5 Only*
You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Apple-Click for selecting multiple pics.
Uploaded with plasq's Skitch!
You can access the Library from the New Message Window in Mail:
Uploaded with plasq's Skitch!
*For users of 10.4 and 10.5* ...
Many internet sites such as Flickr and SmugMug have plug-ins for accessing the iPhoto Library. If the site you want to use doesn’t then some, one or any of these will also work:
To upload to a site that does not have an iPhoto Export Plug-in the recommended way is to Select the Pic in the iPhoto Window and go File -> Export and export the pic to the desktop, then upload from there. After the upload you can trash the pic on the desktop. It's only a copy and your original is safe in iPhoto.
This is also true for emailing with Web-based services. However, if you're using Gmail you can use iPhoto2GMail
If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
*If you want to access the files with iPhoto not running*:
Create a Media Browser using Automator (takes about 10 seconds) or use this free utility Karelia iMedia Browser
Other options include:
1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
Regards
TD

Play from an Export plugin?

Hi,
From a complete novice at Photoshop plugins...
I am wondering if there is any underlying reason why I can't call sPSActionControl->Play() from an Import or Export plugin.
I have a very simple import and export plugin pair to port from Windows to Mac, and both call a third Listener plugin to keep track of open images. The Windows code creates a hidden window (HWND) in the Listener and messages that from Import and Export. I was thinking that I could replace this by calling Play to send a custom event to the Listener, but can't get it to work.
In fact any call to sPSActionControl fails. [The actual failure is sSPBasic->AcquireSuite in PIUSuites.h returns error 'Parm' when called for the sPSActionControl suite. sSPBasic has been set up, looks ok and sSPBasic->AcquireSuite works when called for sPSActionDescriptor suite].
As a test (to remove other sources of error), I pasted the following lines into the PluginMain function of the History plugin in the SDK sample code and this fails in the same way:
// TEMP code to test use of SPActionControl.
SPErr error = kSPNoError;
DescriptorTypeID typeID;
error = sPSActionControl->StringIDToTypeID("Save Prestige Image dictionary", &typeID);
So I'm wondering (a) is there some underlying reason why this doesn't work, or (b) is there some extra bit of initialisation or setup I need to do before calling sPSActionControl functions?
Tearing out what little hair I have left!! Any help or suggestions most welcome.
Thanks
Terry Smyth
PS Is there another way (apart from Play) to communicate from one plugin to another?

Yes, there are many reasons.
But the biggest reason is that it's an export plugin, and not an automation plugin.

Ways to implement image resizing using plug-ins?

Hi Photoshop developers,
I'm a developer with a few Photoshop filter and selection plug-ins under my belt, and I have a good understanding of the SDK and tools and suites it provides. My next project is an algorithm for enlarging/resampling images to different pixel dimensions. I'm wondering if anyone has any suggestions for or experience with the best combination of plug-in types to implement this.
Clearly, I can't just write it as a filter plug-in, since there is no way to change the image dimensions from within a filter.
I'd like the resized image to remain within Photoshop (as a new window or in the original one), so an export plug-in on its own is not sufficient.
Import plug-ins seem promising, since they allow the creation of a new document of the required size. However, as best I can tell from the Photoshop 6.0 SDK documentation, import plug-ins cannot access the image data from other open documents (or even the clipboard), nor do they provide any support for channel ports and the Channel Port suite.
My best idea at this stage is to create an export plug-in to provide the user interface and calculate the resized image, and then an import plug-in to import the resized image back into a new window. (I'm supposing a further automation plug-in would then be written to perform this export/import sequence.) The difficulty I see with this approach is how to communicate the resized image data between the two plug-ins. Since the resized image will potentially be very large, the ideal solution would be to store it in channels managed by the Channel Ports suite. However, I cannot see how the channel ports created in the export plug-in could be communicated to and used by an import plug-in. The alternative would be for the export plug-in to save the resized image to a temporary file on disk, however this seems unnecessary.
So, my questions, specifically, are:
a) Is it possible to create new channels using the Channel Ports suite (sPSChannelPorts->New()) in one plug-in, and have those channels persist to be used in another plug-in?
b) If so, how would the channel ports be communicated between the plug-ins?
c) Alternately, are there any alternative architectures available for implementing an image-resizing algorithm using the plug-in types that are available for Photoshop developers.
Any responses would be greatly appreciated; I know this is a low-traffic forum...
Thanks,
Matthew.

I would make an automation plug-in and a filter plug-in. 1) Run the automation which runs your filter to gather current image information 2) Create a temp file of the new document 3) Make a new document 4) Call the filter again to reload the temp data on disk <[email protected]> wrote in message news:[email protected]... > Hi Photoshop developers, > > I'm a developer with a few Photoshop filter and selection plug-ins under > my belt, and I have a good understanding of the SDK and tools and suites > it provides. My next project is an algorithm for enlarging/resampling > images to different pixel dimensions. I'm wondering if anyone has any > suggestions for or experience with the best combination of plug-in types > to implement this. > > Clearly, I can't just write it as a filter plug-in, since there is no way > to change the image dimensions from within a filter. > > I'd like the resized image to remain within Photoshop (as a new window or > in the original one), so an export plug-in on its own is not sufficient. > > Import plug-ins seem promising, since they allow the creation of a new > document of the required size. However, as best I can tell from the > Photoshop 6.0 SDK documentation, import plug-ins cannot access the image > data from other open documents (or even the clipboard), nor do they > provide any support for channel ports and the Channel Port suite. > > My best idea at this stage is to create an export plug-in to provide the > user interface and calculate the resized image, and then an import plug-in > to import the resized image back into a new window. (I'm supposing a > further automation plug-in would then be written to perform this > export/import sequence.) The difficulty I see with this approach is how to > communicate the resized image data between the two plug-ins. Since the > resized image will potentially be very large, the ideal solution would be > to store it in channels managed by the Channel Ports suite. However, I > cannot see how the channel ports created in the export plug-in could be > communicated to and used by an import plug-in. The alternative would be > for the export plug-in to save the resized image to a temporary file on > disk, however this seems unnecessary. > > So, my questions, specifically, are: > > a) Is it possible to create new channels using the Channel Ports suite > (sPSChannelPorts->New()) in one plug-in, and have those channels persist > to be used in another plug-in? > > b) If so, how would the channel ports be communicated between the > plug-ins? > > c) Alternately, are there any alternative architectures available for > implementing an image-resizing algorithm using the plug-in types that are > available for Photoshop developers. > > Any responses would be greatly appreciated; I know this is a low-traffic > forum... > > Thanks, > Matthew.

Any Flickr Export plugin available for Aperture 3?

I was happy to see Flickr included in Aperture 3, but to say the least, it really *****.
The worst thing is that it applies my own keywords to all the uploaded images. I don't want the (full) names of peoples in my pictures to display at Flickr and having my local-language keywords on my images probably doesn't help Flickr where most users are speaking english (compared to my local language).
Basically I wish the Flickr export feature would allow me to either "not sync keywords" or modify my keywords to determine if I want them exported or not - like Lightroom does.

Thanks for the warning Martin. I already know from iPhoto's flickr export that you gotta be careful. I guess the iPhoto/Aperture flickr export is great for those wanting REAL simplicity, but if you want to adjust just one or two settings, it's a no-go and it kinda *****
I hope there's an AP3 flickr export plugin out there? I would be willing to spend $10 on it.

Exporting Versions to image with meta data

Hey folks, I'm looking to find an Aperture Plugin that will export processed images (versions) with all its associated meta data in XML format.
I intend to use this exported data in a custom application - I've seen export plugins to Picasa, and others, but so far they just seem to handle the images alone.
Can anyone suggest a location to where I might find such a beast? (or is anyone in development of this? - I'm very surprised it isn't included as a built-in feature.
Thanks in advance,
Ted

Has anyone had success with Ubermind's Aperture to FileMaker?
I've had it work once or twice, but usually, despite rigorously following their apparently simple instructions, Aperture refuses to recognize the database.
Would be pleased to know if there's something they haven't been clear about in their instructions.
Regards,
Brent

Preserving Folder Tree Hierarchy using Export Plugins in 2.0

Hi Folks,
I've been trying to find a plugin that will allow me to select a top level folder and then export all images preserving the folders / subfolders.
i.e. Select 2008 and end up with export of all images in appropriate sub folders:
2008\beach shoot
2008\weekend shots
2008\wooded area
Anyone know if this is possible on 2.0 either natively or using a plugin ?
Thanks
Adam.
[email protected]

http://www.lightroomforums.net/showthread.php?t=2810
Here is a solution.

LR3 Flickr export plugin. Is the export without ICC profile available?

Hey guys,
I want to use the new integrated Flickr export plugin in LR3 to publish my picture on my photostream.
Since I want my pictures to look the same accross all browsers I want to convert them to sRGB and I don't want to embed the ICC profile.
I haven't seen any option in LR3 that allows me to do so. I have to do it in photoshop (save for the webs without profile) and then import it manually using Flickr update webpage. In my opinion, it is kind of weird that Adobe didn't think about that. Is there an option somewhere, a workaround?
Thank you,
jean bapt

Bob_Peters wrote:
jean bapt wrote:
Ohhhh my godddddd!!!
Here is the problem:
http://www.carlchapman.com/colour-management/new-safari-4-browser-color-manageme nt-error/
Safari 4 color manager is bugged!!!! And guess what I was using? Safari 4... I just upgraded to Safari 5 and now the color of the tagged images look great. They look exactly like in CS4 and FF 3.6.
Everything I could read or everything you explained didn't make sense with this stupid Safari bug as it was displaying crazy colors; But now it does. I do understand now why I don't need to strip the profile.
Thank you very much for taking the time to help me. I really appreciated your patience.
Have a good weekend
JB
At the risk of raining on your parade...
I just opened the files again in CS4 and in Safari 4.0.5 and the all look the same, just as they did in Safari 5.0.
Safari 4.0.5 displays the files as I would expect, at least on my MacPro and MacBook Pro. You may have found a solution but I'm afraid you don't really know what the problem was.
Sorry, JB. Safari does know how to correctly display images.
Ah ah! You are not raining on my parade. From the comments on the page I have mentioned, it seems that not everybody has this issue. Could it be an issue with another Safari version (4.0.??). I don't remember exactly which version I had. Could it be a compatibility issue with some driver or ...?
Even though I am not sure what the problem was, don't you think I can assume that the problem was not with my files or my calibration?

Newbie to LR3 - Local sharpen after image resize ?

Maybe someone can point me to help. I just post to web on Flickr, no printing yet.
I started photo editing with PSE5 & have moved to PSE8 since. A Mark Galer book about PSE started me on a path of .raw editing & i've been using his scheme since. I hoped i was moving to a smoother overall process with LR3, but now that i've gotten it i have a lot more doubts. I can see improves through the develop phase (sort of a curves, grad filter, noise removal, lens correction). After that, i feel only lacks (with my current low knowledge level).
The things i want included past develop are these: image resize, local sharpening (and blurring - after image resize) smooth border capability (with choice of color). One way of course is to export to PSE8. I expected more from LR3, though - rather than just 2/3 of a job for 3 * the price.

Pete Marshall pointed out one of the quickest resources for information on using Lightroom's tools, but that's not a tutorial! LR is best learned using one or more of the on-line tutorials or LR books available......and then using it! Lightroom's non-destructive workflow has been tailored to fit the specific needs of the "digital photographer" for processing Camera RAW image files. Photoshop has a vast arsenal of both destructive and non-destructive tools for general image processing, but with no specific focus on usage.
Everything you stated in your last sentence can be done very easily in LR, but using an entirely different workflow organization than Photoshop.
The things i want included past develop are these: image resize, local sharpening (and blurring - after image resize) smooth border capability (with choice of color). One way of course is to export to PSE8. I expected more from LR3, though - rather than just 2/3 of a job for 3 * the price.
1) image resize, local sharpening (and blurring - after image resize) - This can be done using the LR Export function and adjusting 'Image Size,' and 'Output Sharpening.' NO, it is not the same methodology as Photoshop. NO, it is not as flexible. YES, it does a very nice job with the vast majority of "digital camera image files," once you get used to a different workflow.
2) smooth border capability (with choice of color) - This can be done using LR's 'Slideshow', 'Print', and Web Modules, choosing the one most appropriate for your target usage. NO, it is not the same methodology as Photoshop, but it does a very nice job on the majority of "digital camera image files." LR also offers multi-media functions that are unavailable in PS.
In the final analysis you need to learn LR's non-destructive workflow procedures, editing tools and module functions, as a compliment to what you already know about using Photoshop. The two applications are mutually independent, but play together well when needed.

Image resizer - power toy's style program for osx ?

I hope this is the correct forum. I am new to the mac way of life and I have just began to explore my new (and first) mac (17" G4 powerbook).
I have Adobe elements that came with my Canon 300D, so I do have an image resizer, however I was hoping someone had information to a resize program that worked similar to the Microsoft power toys. Simply right click the image and choose the size you wish it to be.
If this exists, please point me in the right direction
Thanks a million!
Tiger 10.4 OSX

I think??? what you're looking for is QuickImageCM (a contextual menu plugin).
http://www.pixture.com/macosx.php
Enjoy!
PowerMac G4/Dual 800 Mac OS X (10.4.3)

Watch me write an export plugin

I have started blogging my experience writing an export plugin for Aperture:
http://homepage.mac.com/bagelturf/cocoa/rwok/rwok.html
It's actually pretty straightforward, but then I'm not very far along yet. The idea behind the plugin is that it exports images and gives them random names. Later I will add other randomness. I am calling it Random Wok.

The only way to do that would be with a script or automation plugin.
An export plugin assumes that you are going to be doing the file format writing (without calling back to Photoshop file IO).

Lightroom JPEG export VS Photoshop Image Processor

Hey guys:
Long time photoshop and lightroom user (long time user of all things Adobe). First post here in the forums. I did a search for my question but I think it was too specific, so it returned zero results.
My question is about Lightroom's JPEG export vs Photoshops Image Processor. When I export a RAW file to JPEG from Lightroom, the file size is freaking huge. The JPEG is as big as my original RAW file (~25mb). Settings are set to default - 100 quality. Everything else remains untouched.
However, when I use Photoshop's image processor (I launch it through Bridge, easier that way for me) and process the RAW images that way, my JPEGs are roughly 5-10mb in size. Settings in Image Processor are quality 10 and thats it. No actions being run or anything.
Can anyone shed some light as to why Lightroom exports JPEGs that are roughly 2-4 times the size of Photoshop's JPEGs? My initial thoughts are that the 100 quality setting in Lightroom is more like Photoshop's quality 12 (that always makes me think of Spinal Tap - "Why don't you just make ten louder and make ten be the top number and make that a little louder?" "These go to eleven.") Ideally, exporting out of Lightroom would be much easier for my workflow.
Thanks in advance.
-The Doctor

DrMilesBennell wrote:
Can anyone shed some light as to why Lightroom exports JPEGs that are roughly 2-4 times the size of Photoshop's JPEGs? My initial thoughts are that the 100 quality setting in Lightroom is more like Photoshop's quality 12 (that always makes me think of Spinal Tap - "Why don't you just make ten louder and make ten be the top number and make that a little louder?" "These go to eleven.") Ideally, exporting out of Lightroom would be much easier for my workflow.
You are correct: LR Quality 100 = PS Quality 12
Despite LR having 101 Quality settings (0 to 100) it actually only has 12 Quality settings the same as PS 'Baseline Standard':
JPEG Quality Setting Comparison
PS
LR
LR Range
Typical Reduction
0
0
0-7%
11%
1
10
8-15%
23%
2
20
16-23%
14%
3
30
24-30%
14%
4
35
31-38%
16%
5
40
39-46%
24%
6
50
47-53%
4%
7
55
54-61%
27%
8
65
62-69%
25%
9
70
70-76%
31%
10
80
77-84%
35%
11
90
85-92%
41%
12
100
93-100%
I keep a small copy of the above table taped to my monitor. I chose the numbers under the 'LR' column for the 12 steps (not AA's) to make it easier to remember. In actuality ANY number in the LR Range column will produce the same results for each step.
Under the 'Typical Reduction' column notice the small amount of reduction for PS 6 (LR 47-53%) Quality setting. If interested why AND why you probably shouldn't use PS 7 (LR 54-61%) Quality setting see this post:
http://forums.adobe.com/message/5641903#5641903

How to get the destination path in an photoshop sdk export plugin when using a batch action?

Hello,
I've written an exporter plugin (not save-as) that exports a given file to a custom format.
I was able to open a file selector dialog and choose a path that is then transported to the saving location.
Now my problem is: Another intended use is batch exporting many files. The user records an action with the export step and then applies a batch on it.
The PS batch window allows you to select the destination to be a directory where the exporter should write the data. Fine.
Now how do I get this path? When running in batch mode the silent flag is set for my plugin so I do not spawn a file selector dialog to annoy the user.
But I am also unable to obtain the path which was selected by the user in the batch window.
The SDK automation plugin Getter has some code to retrieve the path of the file and even that fails as it cannot obtain anything.
PropertyUtils.h has some PIGetWorkPathIndex and PIGetPathName functions but I always get 0 when asking PIGetNumberPaths, and get -1 with PIGetWorkPathIndex.
I would be thankful if somebody could hint me how I can retrieve directories.
It even seems impossible for me to get the path where the file is actually saved. The filter plugin called Propertizer utilizes a function called PIGetDocumentName but this only outputs the file name, not the full path.
(Just to be sure: The file on which the tests run is already saved to disk, if that matters)
Another fun part is: When I record an export step, what is the directory I am exporting into?

Ok, after lots of reading the sdk sample outbound I've realized that or plugin is broken.
When recording an action the outbound plugin stores the current path to gAliasHandle which is then recorded as a scripting parameter. Now when I execute the action I get the alias handle.
However how is this supposed to work with an export plugin and batch processing with a "destination" set to a target? Is this even possible or do I need to double click the export step in the action and "reset" the location even if that causes the entire exporter to run again?

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

Any ideas?

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

Kindle Export plugin No image resize

Similar Messages

Maybe you are looking for