Premiere Export Plugin Migration

A few years back my current company created an export plugin on Premiere Elements 7 that brings up its own complex UI for creating video content for our Simulation Product. We have a need to move forward to the latest version of Premiere Element which is now 11. And it seems that somewhere around 9 the export went away and has been replaced with the Share window. From what I can gather you can create export plugins for the share window, but you provide a set of parameters to Premiere which it then uses to build a UI. This is not going to work for our particular application, is there a way to migrate our existing plugin to the new SDK that we can still launch our own UI?

Zac,
Thanks for the quick response. In looking at the new SDK it looks like the exportcontroller example is closer to what we need, at least in that it provides access to the ecStdParms struct which has a pointer to the piSuitesPtr. We use many of the functions on this object to get infromation about the video. Is it possible to get this piSuitesPtr from the "ex" interface? I haven't been able to find access to that. Are ExportController plugins also accessible thru the Publish+Share menu?

Similar Messages

Premier 7 Export Plugin Migration

For the last couple years our company has developed a plugin for Premier Elements 7 that we use to create video content for our product. We will need to move to the latest version of Premier as 7 is no longer available. But from what I can tell the Export plugin support is no longer supported in Premier 9. What is the process for migrating export plugins to the latest versions of Premier?
Thanks if advance for any help.

Welcome to the forum.
You pose a good question.
I do not know if any of the regulars here can help much, but perhaps an Adobe employee can stop by, and give you an answer.
I do not know of an SDK for PrE, but that does not mean that one is not available. I know that a few 3rd party developers DO write plug-ins for PrE, such as NewBlue FX, ProDAD, SmartSound and some more. They obviously have input from Adobe to help in their development process.
One consideration for a plug-in developer, is that as of PrE 10, there are both 32-bit and 64-bit versions of the program, and that usually means two different plug-ins, one for 32-bit, and one for 64-bit. When PrPro (there IS an SDK for it) went to 64-bit only, with CS5, it took a little time for developers to rewrite their plug-ins, CODEC's, etc., for 64-bit programs. Most were able to do that fairly quickly.
Wish that I had someone, or somewhere to direct you, but I do not. Maybe Steve Grisetti knows who/where you can get the necessary info?
Good luck,
Hunt

CS6 Exporter Plugin doesn't open in Premiere Elements 11 (Windows)

I want to make my (Windows) exporter-plugin compatible with Premeire Elements 11.
So far, I have been gotten my exporter-plugin to appear in Adobe Premiere Pro CS6 and Media Encoder CS6, and the plugin runs there correctly.
I then followed the directions for running Premeire CS6 to create an export a preset file (*.epr). I copied copied that exported *.epr file to "OTHERS/MyCompany/MyPreset.epr" in my Premere 11 [App installation folder]. (As well as copying the plugin-binary *.prm to Plug-ins/common
In the <Publish:Share> tab, when I use the mouse to highlight 'OTHERS', I receive an error-dialog-box :
"Premiere Elements has encountered an error.
[..\..\Src\Exporter_Accessors.cpp-213]"   [Continue]
After I click continue, I don't get the dialog-box for my exporter-plugin. In the <Publish:Share> tab, I now see the warning-triangle and some text next to it: "Export Settings Invalid"

Hmm, I forgot about using Visual Studio's debugger. After some debugging, the error was triggered the first time the SDK_Exporter plugin called anything involving the <exportParamSuite>.
After a little more digging, I found that Adobe Premiere Elements 11 doesn't support the latest version of the exportParamSuite (kPrSDKExportParamSuiteVersion4).
In the CS6 SDK sample project SDK_Exporter, the function exSDKBeginInstance() grabs all of the suiteAPIs. The following call fails:
     spError = spBasic->AcquireSuite(
         kPrSDKExportParamSuite,
         kPrSDKExportParamSuiteVersion, // CS6 supports v4, but crashes in Premiere Elements 11
         const_cast<const void**>(reinterpret_cast<void**>(&(mySettings->exportParamSuite))));
The original-call returns an spError code of <kSPSuiteNotFoundError>, which is actually misleading. I changed the version-argument to v3, and the error-call went away.
     spError = spBasic->AcquireSuite(
         kPrSDKExportParamSuite,
         kPrSDKMemoryManagerSuiteVersion3, // compatible with Premiere Elements 11
         const_cast<const void**>(reinterpret_cast<void**>(&(mySettings->exportParamSuite))));
so it looks like Premiere Pro CS6 SDK's sample SDK_Exporter project requires a few tweaks to run with Premiere elements 11.

Why Priemere sends 'exSelBeginInstance' selector twice to export plugin?

Is that correct, that my custom export plugin gets 'exSelBeginInstance' selector twice?
Try better explain:
Premiere run two instances of my exporter. It easy to see by looking at exporterPluginID value. It different. And at second instance exporter doesn't get selector 'exSelGenerateDefaultParams'.

Premiere and AME open the plugin multiple times.
If you put a breakpoint on the selector you'll find that it most likely also called exSelEndInstance between them.
here are the basic steps.
in exSelStartup set any Global information about your plugin (there shouldn't be any to make it multi threaded though).
in exSelBeginInstance|EndInstance Alloc/Free your export structure that holds EVERYTHING (your parameters and any per instance information that isn't expressed in the parameters) using the Adobe Memory Suite. BECAUSE AME/PPro call EndInstance you can't trust having your own ALLOC/FREE - you MUST use Adobe's since it keeps a copy of the pointer even after the plugin is unloaded and reloaded.
Don't initialize anything in the exSelCreateInstance. It isn't called when you click the "EXPORT" button. You have to put it in the exSelPostProcessParams.
If you do that you'll be thread safe (AME runs multiple instances of the plugin at once).
good luck,
Edward

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?

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.

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.

Premiere exports in incorrect pixel aspect ratio

My Panasonic camera shoots quicktime .mov JPEG videos in a 720X408 px resolution. I am having a very hard time editing them in Premiere, because I cannot get it to export them in a correct pixel aspect ratio.
Maybe you can figure out what I'm doing wrong. Here's what I do.
First, when opening a new project, the closest frame size I can choose is 720x480. So I choose that. I import the .mov file into it, and put it on the time line. At that point it looks like this:
http://img291.imageshack.us/img291/812/premierewindowoc9.jpg
Correct aspect ratio and no deformation.
When I try to export it as a .mov file, I do the following: I click on settings (in the file save dialogue), and go to video settings. I can choose any pixel aspect ratio, it all produces the same results, but for example, let's say, DVCPRO (1.5) (that's the closest to the size I need).
I can manually set my frame size to be 720x408 px, assuming that now the frame size will be exactly the same size as my video and no deformation will occur.
However, the result I get is this:
http://img6.imageshack.us/img6/6730/exportedmoviehl5.jpg
I've drawn arrows on that to make it clearer. So, I have a movie that's 720x408px. Premiere exports a frame sized 720x408, but then for some strange reason shrinks the actual video down to 483x480!!??!! Leaving completely unnecessary black bars on the sides.
Why does it do this?
When I export it with frame size 720x480, it doesn't add black lines on top and bottom as you'd expect. It does exactly the same thing you see in the image above.
I have tried many other combinations too. I have tried exporting it as every other available pixel aspect ratio, also as an avi file, nothing makes any difference. It always shrinks the original video in width, and adds black bars to the left and right.
What am I doing wrong??

Tina,
Lets see if we can get kitty onto YouTube.
There are four issues, that you will need to overcome:
1.) Project Preset to begin. Stanley lists the possible choices in post #8, based on the specs of your camera. You will have to determine which of these you used to record the files. These are *probably* set in your cameras menu area, and if you have not changed them, are probably still set. That will get you started in the right direction - but wait, theres more...
2.) It seems that your camera uses Motion-JPG as the encoder to create these files. There are at least two good Motion-JPG CODECs available, Lead and Morgan. Plus, your camera may well have come with its own Motion-JPG CODEC. The CODEC is what allows your camera to encode/compress the video data, and also what allows programs like Premiere to decode that data. Did your camera come with a CD/DVD with software on it? If so, the installation of that software *should* install any proprietary CODECs to your system. Now, if this was the case (or soon will be the case, when you locate that CD/DVD), Premiere *possibly* will be able to use that CODEC to handle the footage from your camera. If it does not, then it is *possibly* only a matter of purchasing, downloading and installing one of the two mentioned Motion-JPG CODECs. Both are relatively inexpensive, and Premiere *usually* can work with either, though your exact footage might not permit this. This is usually because a camera mfgr. chose to do their own thing. Thats why any disc that came with the camera is the first place to start.
3.) Now, you are in Premiere, have the proper CODEC installed on your system, and have Imported the footage into a Project with the proper Presets. If all is working, and I hope that it is, you just edit your footage.
4.) You have been working with Presets established based on your footage. That is likely not exactly what you will want to upload to YouTube. This is where Export comes into play. Unfortunately, YouTube seems to change the specs. weekly. About the time that someone publishes fool-proof details and settings for YouTube, they (YouTube) change everything. The best advice is to search as many fora, as you can for Export Settings for YouTube. Look at the dates for all articles. You really will only care about the most recent - very recent.
Going back up the list, there is another possibility. That would be to use a 3rd party conversion program to convert your footage to a DV-AVI Type II file. Often, with the proper CODEC installed, Premiere can do this internally, though not always, and even when it works, there can be problems. I use DigitalMedia Converter (Deskshare) a shareware program for most of my conversions. There are many freeware, and shareware, conversion programs available. Many get mentioned in this forum. Many get glowing reviews. Some are easier to use, than others.
Some balk at the thought of owning Premiere Pro and then having to use some 3rd party software to get their footage into a robust NLE, that they paid good money for. The fact is that Premiere Pro was designed to work primarily with DV-AVI Type II files, from mini tape cameras - the point made by several. That does not mean that it cannot work with other file types. It does, though not always without problems. Sometimes just passing the material through a conversion program will clear up all problems and no one is the wiser. I often use Premiere Elements, Pros little bitty brother, to convert some file formats, because it is more tolerant of many of these, than is Pro.
Good luck, and sorry that I do not have a current suggestion for Export to YouTube. Since it is a hot distribution medium, you should have no problem finding the correct settings for today - be sure to check the date of all articles, as the specs change all the time and in a heartbeat.
Let us know if you have any more questions. For "how things are done in Premiere," I recommend the Premiere-wikia: http://premierepro.wikia.com/wiki/Main_Page
for tutorials. Most that you could want to do will be there someplace. The current YouTube setting might be an exception, just because every time the Wikia gets updated, that info is out of date.
Hunt

How to replace missing export plugin in iphoto 9.4.7?

How to replace missing export plugin in iphoto 9.4.7? I am attempting to convert jpgs into html.

Reinstall from the original source?
LN

Flash Video Exporter plugin for FInal Cut Pro

Does anybody know how to install the Flash Video Exporter
plugin for Final Cut Pro so it shows up as an option in FCP?
I want to create FLVs directly from FCP.
Thanks

http://www.adobe.com/devnet/flash/articles/flv_exporter_03.htm
Scroll Down - its about mid page
This is on the intro page:
Note: You must have Flash MX Professional 2004 installed on
your machine to use the Flash Video Exporter with your video
editing application. The only exception is using the exporter in
Demo Mode.

Lightroom Export Plugins not on the Website?

Hi!
I was directed to this portion of the Adobe website:
http://www.adobe.com/products/photoshop-lightroom/plugins-presets.edu.html#export-plugins
I have found a few plugins that I would like to experiment with, namely the Costco one and the Blog one, however everytime I click on one of them I just get a page that says "We're sorry we've encountered an error processing your request" I am on Google Chrome on a PC, anyone know how I can actually get to these plugins where I can try to get them installed into Lightroom 5??

Thanks, I tried again this time using IE and was able to download them. For anyone paying attention at Adobe you might have an issue with some of those pages refrenced above with Google Chrome.

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?

Export plugin on Macintosh not honoring LrTasks.startAsyncTask ?

Hi -- I need some help again!
I'm writing an export plugin for my own application.
On Windows, everything works as expected -- I can start the export and then go back to doing other tasks in Lightroom while my application does its own thing.
But on Macintosh, Lightroom hangs with the rotating "busy" icon until my application quits.
I am baffled by this behavior because I think I've wrapped everything I'm doing in calls to LrTasks.startAsyncTask.
Apparently I'm missing something about how asynchronous tasks work in Lightroom, or at least in Lightroom on Macintosh.
Do you have any suggestions about how I can get the Mac version to keep Lightroom responsive while my exported-to application does its thing?
Thanks!
--Rik
For further information...
Mac OS X 10.9, Lightroom 4.2
Here is the current structure of my ExportToMA.lua file
local myLogger        = LrLogger("myLogger")
myLogger:enable("logfile")
ExportToMA = {}
ExportToMA.outputToLog = function(param)
myLogger:trace(param)
end
LrTasks.startAsyncTask( function()
    myLogger:trace("Entering outer LrTasks.startAsyncTask function")
    LrTasks.startAsyncTask( function()
        myLogger:trace("Entering inner LrTasks.startAsyncTask function")
        local activeCatalog = LrApplication.activeCatalog()
        local frameSet     = activeCatalog.targetPhotos
        local exportSession = LrExportSession( {
            exportSettings = {
                LR_exportServiceProvider       = "net.mydomain.MAloader",
                LR_exportServiceProviderTitle = "My Application",
                LR_format                      = "TIFF",
                LR_tiff_compressionMethod      = "compressionMethod_None",
                LR_export_bitDepth             = 16,
                LR_export_colorSpace           = "sRGB",
                LR_minimizeEmbeddedMetadata    = false
            photosToExport = frameSet,
        myLogger:trace("Before doExportOnCurrentTask()")
        exportSession:doExportOnCurrentTask()
        myLogger:trace("After doExportOnCurrentTask()")
        myLogger:trace("Exiting inner LrTasks.startAsyncTask function")
    end )
    myLogger:trace("Exiting outer LrTasks.startAsyncTask function")
end )
When run on Windows, the log file contains a sequence of messages like this:
12/30/2013 10:36:48 TRACE    Entering outer LrTasks.startAsyncTask function
12/30/2013 10:36:48 TRACE    Exiting outer LrTasks.startAsyncTask function
12/30/2013 10:36:48 TRACE    Entering inner LrTasks.startAsyncTask function
12/30/2013 10:36:48 TRACE    Before doExportOnCurrentTask()
12/30/2013 10:36:49 TRACE    After doExportOnCurrentTask()
12/30/2013 10:36:49 TRACE    Exiting inner LrTasks.startAsyncTask function
   <meanwhile my application continues to run while Lightroom stays responsive>
But when run on Macintosh, this is what happens:
2013-12-30 19:01:50 +0000, TRACE    Entering outer LrTasks.startAsyncTask function
2013-12-30 19:01:50 +0000, TRACE    Exiting outer LrTasks.startAsyncTask function
2013-12-30 19:01:50 +0000, TRACE    Entering inner LrTasks.startAsyncTask function
2013-12-30 19:01:50 +0000, TRACE    Before doExportOnCurrentTask()
<indefinitely long pause while my application runs>
2013-12-30 19:02:44 +0000, TRACE    After doExportOnCurrentTask()
2013-12-30 19:02:44 +0000, TRACE    Exiting inner LrTasks.startAsyncTask function
Ideas?

> I'm confused by your application: if you already have a renditions loop, then why are you starting another export
I apologize for the confusion.
In each case I've exercised, there is only one export and one renditions loop.
The code I've been showing you is what gets executed to service a menu entry in File > Plug-In Extras. I'm focusing attention on that case because it seems more transparent. Notably, I get to specify which task the export happens on.
The renditions loop in my processRenderedPhotos function is in another script. The renditions loop gets called in two places: 1) from File > Plug-In Extras via the explicit doExportOnCurrentTask (now doExportOnNewTask), and 2) from Lightroom's internal processing of File > Export... and File > Export with Preset.
> did you try doExportOnNewTask?
I tried it just now. It did not change the behavior.
I also added some more diagnostics. Here is what happens on the Mac:
2013-12-31 01:09:31 +0000, TRACE    Entering outer LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    Exiting outer LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    Entering inner LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    Before doExportOnNewTask()
2013-12-31 01:09:31 +0000, TRACE    After doExportOnNewTask()
2013-12-31 01:09:31 +0000, TRACE    Exiting inner LrTasks.startAsyncTask function
2013-12-31 01:09:31 +0000, TRACE    MyApplicationUploadTask.processRenderedPhotos prefs.maPath: /Users/myaccount/Desktop/MyApplication.app/Contents/MacOS/JavaApplicationStub
2013-12-31 01:09:31 +0000, TRACE    tempPath: /var/folders/4n/2lxf6v593x5_c3lmx_jghgnw0000gn/T/temp_lre_ma_1230170931
2013-12-31 01:09:31 +0000, TRACE    nPhotos = 2
2013-12-31 01:09:32 +0000, TRACE    source path/Users/myaccount/Desktop/jpeg-8d/testorig.jpg
2013-12-31 01:09:32 +0000, TRACE    destination path: /var/folders/4n/2lxf6v593x5_c3lmx_jghgnw0000gn/T/6F05FC8E-126C-47E0-AD51-C545CE0DA66D/tes torig.tif
2013-12-31 01:09:32 +0000, TRACE    source path/Users/myaccount/Desktop/jpeg-8d/testprog.jpg
2013-12-31 01:09:32 +0000, TRACE    destination path: /var/folders/4n/2lxf6v593x5_c3lmx_jghgnw0000gn/T/6F05FC8E-126C-47E0-AD51-C545CE0DA66D/tes tprog.tif
2013-12-31 01:09:32 +0000, TRACE    just before LrShell.openFilesInApp
   <long pause here, while I let my application run for a while>
2013-12-31 01:10:00 +0000, TRACE    just after LrShell.openFilesInApp
The LrShell.openFilesInApp call happens after my renditions loop, at the very bottom of my processRenderedPhotos function, which is now separated by 3 levels of asynchronous tasks from whatever task initially serviced the menu entry.
Nonetheless, on Macintosh only, as soon as LrShell.openFilesInApp is called, Lightroom comes to a grinding halt heralded by a spinning beach ball.
It's as if, deep under the covers, LrShell.openFilesInApp (on Macintosh only!) is telling the rest of Lightroom to wait until the spawned application terminates.
I know, it sounds crazy to me too, and I've been programming for close to 45 years.
At the moment, the only way I see to work around this problem is to provide a separate "application" that is actually a spawn-and-terminate, so that LrShell.openFilesInApp will see a rapid termination of the thing that it launches. That seems like a lot of trouble for what I've been hoping is a simple misunderstanding on my part.
The one thing I can see different between my app and anybody else's is that mine is written in Java, so the thing that gets launched by LrShell.openFilesInApp is the JavaApplicationStub.
Any other ideas?
--Rik
PS.
> Do you have this problem with hard drive export too?
I doubt it, but I don't know for sure. On my test Mac, at the moment, there are not enough files to keep hard drive export running long enough to notice.

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.

Export plugins

I've been playing with various online photo albums, flickr, picasa and gallery, and it's really nice that there are export plugins available for all three of them. However, I have some problems with two of them: the picasa and gallery plugins from Übermind (0 problems with the flickr plugin from Connected Flow).
What happens is that the upload hangs or that the plugin doesn't seem to want to export at all.
I've tried to contact Übermind to get some help in tracking down the problem but haven't received any answer. Does anyone have a suggestion for what the problem could be? (I'm using the latest versions of the plugins etc)

No answer

Premiere Export Plugin Migration

Similar Messages

Maybe you are looking for