Aperture's templates

H! there,
Does anyone know if I can use Iphoto's templates (Photo book theme's or templates) on aperture? Or does anyone knows if the aperture has colorful themes like the ones in iphoto? or Is there any way that I can manage the pages color while using each photo book's themes? It looks like the photo book themes on aperture has really plain color, either white or black.
Thanks!

What do you mean by upgrade?
Your signature states you are using MacOS X 10.6.8; that is incompatible with Aperture 3.3.2, so you cannot be running AP 3.3.2, unless the signature is wrong.
if you create your Books in iPhoto '11, you will not be able to view and edit the books in Aperture however, see:
iPhoto '11: Use iPhoto with Aperture http://support.apple.com/kb/PH7990
The choice of colors in Aperture depends on the theme you are selecting. Each theme offers a different set of colors, so you need to experiment a little to find a color scheme you like.
"Modern Lines" has nine background colors, "Journal" and Snapshots dito.
For example, the "Snapshots" Theme:
Regards
Léonie

Similar Messages

  • Iphoto 08 vs aperture book templates

    I too wanted to use the new book template from iphoto 08... But I can't get this accomplished... There should be an easy way to import / export (depending on which program) to use the new book templates from iphoto 08 into Aperture. This release of iphoto 08 without acknowleging us Aperture users is in my view a horrible mistake and the Apple executives should be embarrassed.

    One problem I am having is that if you browse the Aperture library using iPhoto 08 you can certainly import the previews but they are in fact not large enough/high quality enough to use for book or calendar printing. I use high qual previews in Aperture (9 out of 10) at large sizes and I still get the exclamation point when I import into iPhoto -- the only way I can get it to work properly is to export to the desktop the full-size versions, then import those into iPhoto. Not excatly seamless! Am I missing something that will make this work better? I mean, what is the point of sharing Previews if the Previews won't work well enough for printing?

  • Does aperture have templates for non-standard aspect ratios?

    i am not yet an aperture user, but i am interested in switching to it to improve on the photo book quality WRT iPhoto.
    i like very much to have photos with non-standard aspect ratios, either square or wide (like 3:1). these are cropped very badly by iPhoto; is it better in Aperture?
    thanks,
    b.

    The templates my have a few variations that use non-standard ratios, but you can specify any photo box ratio. You have the option to either right click and choose it from a list, or choose the custom option from that pull list, or use the "Size & Position" pane of the Aperture UI to specify an exact size, angle, and border thickness and color of a photobox. This works similar to the controls in Pages, but without some of the nice effects like transparency and drop shadows.
    If you want to create custom layouts, read the "Working with Custom Themes" section on page 609 of the user manual (download it with the trial). The trial is good for 30 days, so why not give it a spin, and if you don't think it's worth the $199, then you can always delete it at no cost to you other than your time.

  • Make my own template for a one page book?

    I need to make a book template that will appear in the list of possible book designs -- is that possible?
    Secondly -- I want to make a one-page book (call it a poster if you want) it's really a form that I want to print out with a different photo each time. It's actually a casting form/release for models. I want to be able to shoot a tethered photo of model, put it into a one-page form which already has a model release in it and print it out so they can sign it.
    I have not been able to work with any of the existing templates because they won't permit me to reduce the number of pages to one or two. (sure I can always just choose to print one page, but I want to keep all this as simple as possible as it will be casting assistants or studio assistants doing this).
    So my questions are:
    1. Can I create my own Aperture book template?
    2. Can I create a template that is only one or two pages?
    3. Can I enter the model's name, email, phone, etc in metadata and have that print out as a release form for them to sign?
    4. Can I use Automator to make this a "push the button" operation?
    Many thanks and open to all suggestions.

    Never mind. I figured it out already. Can turn off page numbering from the pop-up menu on "book action". Should have just the manual. Thanks.

  • Web Gallery generation speed is unacceptable

    Machine: DP 2 Ghz G5, 2 GB RAM, 160GB disk, 250 GB disk, 20" Cinema Display
    Aperture has it's library on the second SATA disk to improve I/O, likewise CS2 uses that disk for it's scratch and Bridge cache.
    Task: Generate web gallery, Aperture(Proofs template), Bridge/ACR/CS2(white dots on black background)
    -Raw images: Only 10 D2X NEFS
    -In both apps all NEFS were tweaked and sharpening applied.
    -Thumbnails 200x300
    -Enlarged image(after clicking thumbnail) 750x499, JPG quality: Aperture(high) CS2(level 8)
    On Aperture I selected "Export Web Pages", not "Publish to .mac"
    Both Aperture and CS2 wrote the gallery web dir(under different names) to the same second internal SATA disk.
    Aperture took 4:30
    Bridge/ACR/CS2 took 59 seconds
    Once again Adobe buries Aperture.
    This is only one of the many problems with this app.
    Note to Apple, if you want to be the leader then you need to beat the leader.
    NO, I do not work for Adobe.

    For me, the speed of Web page gallery creation isn't of great consequence. I don't make them that often. The speed of comparing images, selecting the pick from a stack, cropping, adjusting color, and so forth is much more important for me.
    I've found the selecting tasks to be much faster in Aperture than in iView Media Pro III, which I also use and like. I also use Photoshop all the time (I'm still on CS1) and think its the best program that I've ever used. But cropping and adjusting colors are much easier and more facile on Aperture.
    I wouldn't know how to conduct your test. Would I use the automation features to create the Web gallery, loading each image off of the hard disk in turn? If so, first I'd have to convert each to DNG. Then I'd have to adjust each on the fly. That makes no sense. So would I do the adjustments and then save out in PSD or TIFF format? Then the files are much bigger, so the disk i/o makes the test unfair for Photoshop and more about hard drive speed than anything the Apps are doing.
    I recognize that other people are having speed problems with Aperture, even in areas where it works well for me. I have tricked out hardware which certainly helps my experience.
    If I was making lots of Web image galleries every day, maybe the speed difference of a few minutes vs a few seconds would bother me too. I've noticed that the Web output from Aperture is very sharp with no noticable fringing. I think it looks great. But I also see that adjusting that sharpness isn't an option with Aperture. That hasn't annoyed me yet, but it might on some future project (like a portrait that wouldn't be as flattering if so crisp).

  • Deciphering Aperture Web Themes: the html templates v3

    version 3 of my Aperture Web Theme html template reference. enjoy
    the html templates.
    rkid attributes:
    Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
      <ul id="nav" rkid="navbar">
    These are the rkid values that I've identified so far:
      "navbar"
        a <ul> element containing all of the navigation elements.
      "active" and "inactive"
        rkid attributes to enable the coder to place different formatting on
        current and non-current page numbers in the navbar.
        eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
          <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
      "content"
        a <div> containing all of the album images and their metadata.
      "pictureblock"
        a mandatory <table> in which the images are placed, one image per <td>.
        the <table> must even be used on the Detail page where only one image is
        displayed.
        the metadata will be within the "pictureblock" table if more than one
        image is displayed so that the metadata can be tied to the image. if
        only one image is displayed; i.e., the Detail page; the metadata may be
        in a <td> outside of the table that the image is in but still within the
        "content" div, usually in the following format:
          <div rkid="content">
            <table>
              <td>metadata
              <td><table rkid="pictureblock">
      "image"
        the rkid for the <img> elements containing the album images, frequently
        placed in <dt> elements within the table's cells.
      "metadata" (added in Decipher v3)
        all metadata for the respective image is specified within this element.
        everything within the element is repeated for every metadata value.
        the Aperture themes use the <ul> element but <div> also works:
          <div rkid="metadata"><p>metaname: metavalue</p></div>
      "titleblock"
        a <div> containing the title text; usually <h3>; for Journals. the <h3>
        element within this element must be given the attribute rkid="text" or
        Aperture will ignore it.
      "textblock"
        a <div> containing the description text for Journals. as with the
        titleblock, the <p> element/s within this div must be given the
        attribute rkid="text".
      "text"
        the rkid given to the text data within the titleblock and textblock
        elements.
    Place holders:
      PageTitle
        used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
      IndexPageURL
        the gallery page/s URLs; may be more than one.
      ThumbImageURL
        the href links for the images, whether thumbnails or detail full size.
      DetailPageURL
      used within navbar:
        PageCount
        PageNumber
        PreviousPageNumber
        PreviousPageURL
        NextPageNumber
        NextPageURL
        PageCount the total number of pages
        PageNumber includes all of the page numbers listed in the navbar, one
          occurrence for each page.
        _Previous and _Next are more specific and are currently used to draw the
          prev/next arrows in the navbar.
      ImageName
      ImageNameSpace
      PlateNameSpace
      PlateNumberSpaceSlash
        *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
          chosen.
        used to represent an index of the image in the album. the first image
          shown gets the index 1, the second 2 and so on.
        for the Image placeholders, the word 'Image' is used.
        for the Plate placeholders, the word 'Plate' is used.
        space indicates an extra space after the index, probably for html
          formatting purposes because it's only used within <dt> elements.
        slash indicates an extra / character after the index.
        examples:
          ImageName > 'Image 1'.
          ImageNameSpace > 'Image 1 '.
          PlateNameSpace > 'Plate 1 '.
          PlateNumberSpaceSlash > '1 / '.
      metaname
      metavalue
        the placeholders for all of the metadata names/values in the selected
        metadata set.
      PageWidth
        not sure if Aperture calculates it based on the width and number of
        images being displayed in both gallery and detail pages.
        don't know why it's only used in the Special Occasion theme.
      CellWidth
        the width of the table cells containing the album images. not
        necessarily the width of the images. may include margins as specified in
        the albuminfo.plist files.
      ImageWidth
        the width of the image.
      TableWidth
        the width of the pictureblock table. it can probably be applied to other
        elements too but it's length is almost certainly calculated from the
        pictureblock table.
    Operative attributes:
      removeonfirstpage="yes"
        used in the navbar to remove the Prev link from the first page.
        because it's applied to the <a> element, the <a> element is removed
          while leaving an empty <li> in place.
      removeonlastpage="yes"
        used in the navbar to remove the Next link from the last page.
        because it's applied to the <a> element, the <a> element is removed
          while leaving an empty <li> in place.
      removeonsinglepage="yes"
        used in the navbar to remove elements when there's only one page.
        used in a <div> in the Art Collection to remove the whole navbar on
        single pages.
      contenteditable="yes"
        used in text elements to indicate that the user can customise the text.
        not necessary in titleblock and textblock rkid="text" elements.
        in elements outside of the titleblock and textblock elements, content
        will not be truly editable unless a textid is assigned to the text
        elements. unfortunately, all text elements with textids are always
        'common' and can not be specific to any one image.
      common="yes"
        the element is seen on all pages.
    Other attributes:
      metaseparator="|"
        used in metadata formatting, within the metadata lists.
        you can add additional characters. for example, the metaseparator
        in the Stock Black theme is " | "; ie, a | bar with a space on both
        sides. (Decipher v3)
        if the metaseparator is specified and the html template places the
        metadata into <li> elements as it does in most of the current themes,
        then it produces non-standard html code with the metaseparator between
        concurrent <li> elements.
      metalayout="paragraph"
        used in metadata formatting, within the metadata lists.
        if not specified, the metadata will not be exported. (Decipher v3)
      singlenesting="yes"
        used in metadata formatting. not sure what it does yet.
      textid="x"
        used to id text elements outside of the titleblock and textblock
        elements.
        possibly no limit to the number and id names used.
        examples used:
          textid="copyright"
          textid="header1"
      picturename="x"
      pictureimage="true"
        picturename gives the image an id.
        pictureimage="true" tells Aperture that the image is a static image
        which can be designated by the user during setup of the album. they show
        up in Aperture as grey blank rectangles with cross-eyes in the middle.
        they do not need to be inside the "content" element
        with picturename and pictureimage, we can place as many static images on
        the page as we wish.
    Assertions:
      Aperture uses the rkid values to identify the areas of the html to be
      repeated for the respective objects.
      standard id and class attributes are only used by the css for formatting and
      not by Aperture to write the html data.
    Notes:
      Aperture is hardcoded to expect and require that the album images are always
      within a <table rkid="pictureblock"> element. it is not possible to place
      album images outside of the table. all album images must be placed within
      <td> cells within the table. the <td> code is repeated for each image.
      image metadata is also normally within the rkid="content" element although
      it can be outside of the rkid="pictureblock" element.
      by default, the textblock rkid="text" element is added when the T+ button is
      pressed within Aperture. the textblock element is switched with the
      titleblock element when the Title/Text toggle button is clicked.
      width and height attributes of <img> elements are rewritten by Aperture
      based on the inserted images. placeholders aren't necessary within <img>
      elements.
      comments are stripped from the html before export some but some
      Aperture-proprietary attributes are forgotten and left behind.
      some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
      doctype.
      all markup is converted and exported in UPPER-CASE. personally, I prefer
      lower-case.
      high-ascii characters entered by the user are not converted to their html
      entities when available. eg, the © character.
      multiple <p> elements can be inserted into the titleblock and textblock
      <div> elements but each of them must have the rkid="text" attribute. any
      element without this attribute will be ommitted by Aperture.
      the reason there are Smart Galleries but no Smart Journals is because you
      need to write text between each row of images.
      titleblock and textblock elements will not be applied to Galleries or Detail
      templates; only to Journals.
      if there are more than one titleblock or more than one textblock, only the
      first will be used by Aperture.
      upon export, Aperture will remove everything from within the rkid="content"
      element which is not the pictureblock, titleblock or textblock elements.
      (Decipher v3)
      some of the Aperture templates have xhtml doctypes but are exported from
      Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
      that UPPER-CASE element names is not permitted with xhtml which is
      case-sensitive. (Decipher v3)
    Questions:
      are there variable scopes with each rkid? eg, within the "content" rkid, can
      every variable/placeholder be accessed?
      why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
      the images and related metadata in the table? easier css formatting?
    JavaScript: (Decipher v3)
      you can include JavaScript in the html code but cannot wrap it in html
      comments because Aperture will remove everything within comments.
      Aperture variables such as PageNumber will not be replaced within
      attributes such as <body onload="dialog(PageNumber);">.
      it is very difficult to use document.write anywhere within the html <body>.
      Aperture seems to be using JavaScript to export the html and its code is not
      able to cope with more than one instance of document.write in the html
      templates. after hours of trial and error, I found that the most stable way
      to use JavaScript within the html <body> was to only use one <script>
      element and place everything within it. using document.write within a second
      <script> element would almost certainly lead to unpredictable exported html,
      and instability and crashes in Aperture.
    iMac Duo Core 2GHz 2GB   Mac OS X (10.4.6)  

    It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
    1) one large image per thumbnail page (like a photo essay or photo blog style)
    2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
    The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
    This is great because I hate javascript but sometimes like the immediate visual effects it allows.
    This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
    The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
    PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
    So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
    Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today.

  • Hiring Someone to Create a Customized Aperture Web Journal Template

    I'm interested in creating a customized Web Journal template for Aperture. Does anyone know anybody out there I could hire to do such a project?

    The BEST way in my opinion is nothing mentioned in this forum:
    LIGHTSCRIBE BABY!!!!!!!!
    Laser burn ANY image on the DVD just like Hollywood Movies baught in a store.
    I paid $175.00 for a Lacie Dual Layer DVD Burner and it included Toast Titanium 7 and LightScribe Software - Best of all works on MACs ONLY (not PeeCee's) and produces flawless DVD's regardless of Brand name.
    No ink jets to buy! No paper to buy! No stupid bulky printer to have on your desk! Just a slim Stainless Steel looking DVD Burner that puts to shame Apple's own SuperDrive OR any Label or Printer kit on the market today.
    www.lacie.com

  • Templates for Aperture Books

    When I create a book in Aperture, I can modify the templates and save the modifications as new master templates.
    But when I go to another project to create a new book, the new templates that I created are not in the list. I see them only in the project where they were created.
    How do I store custom created templates so I see them anywhere in the program?
    G5 2 x 2 Gigahertz   Mac OS X (10.4.3)   2 Gigs RAM

    Daniel, I don't think that is possible. I believe the universal templates we see are built into the program itself, and the list is not user modifiable. I'm wondering if you can't just export the template as a template file, store it in a folder and then load that file when needed. I haven't tried this, so this is just a long shot on my part.
    Jeff Weinberg

  • Customize Aperture 3.4.4 Web Template

    I modified the "Stock Black" web template the way that I want to add the possiblity to get the next picture by simply clicking on the "big" detail picture,
    not only by clicking on the "next" arrow icon.
    But I fail at the last picture.
    1) If I add removeonlastpage="yes" the last picture is not displayed
          <table rkid="pictureblock">
            <tbody>
              <tr>
                   <td>
                        <a href="_NextPageURL_" removeonlastpage="yes">
                        <img name="img" rkid="image" src="_ThumbImageURL_" alt="" height="450" width="675" />
                   </td>
              </tr>
            </tbody>
          </table>
    2) If I add removeonlastpage="no" I get an out of range "page"
          <table rkid="pictureblock">
            <tbody>
              <tr>
                   <td>
                        <a href="_NextPageURL_" >
                        <img name="img" rkid="image" src="_ThumbImageURL_" alt="" height="450" width="675" />
                   </td>
              </tr>
            </tbody>
          </table>
    Is there any solution for my problem?
    detail.html:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
    <!-- STOCK BOOK DETAIL HTML -->
      <title>_PageTitle_</title>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
      <link href="assets/css/global.css" rel="stylesheet" type="text/css" />
      <meta name="description" localizable="true" content="Created by Apple Aperture" />
    </head><body class="detail">
    <div id="header">
    <h1 contenteditable="true" textid="header1" localizable="true" common="true">TITEL DER WEB-SITE</h1>
    <ul id="nav" rkid="navbar">
    <!-- The list items below need to be smashed together for IE on Windows -->
      <li class="index"><a href="_IndexPageURL_" localizable="true">Index</a></li>
      <li class="previous"> <a href="_PreviousPageURL_" removeonfirstpage="yes"><em class="previous_text" localizable="true">Zurück</em></a> </li>
      <li class="pageNumber">_PageNumber_ von _PageCount_</li>
      <li class="next"> <a href="_NextPageURL_" removeonlastpage="yes"><em class="next_text" localizable="true">Weiter</em> </a> </li>
    </ul>
    <div style="clear: both;">
    </div>
    <table>
      <tbody>
        <tr>
          <td style="width: 100%;">
          <div id="photo" rkid="content"><!-- Photo img, must be in a table -->
          <table rkid="pictureblock">
            <tbody>
              <tr>
                <td><img name="img" rkid="image" src="_ThumbImageURL_" alt="" height="450" width="675" /></td>
              </tr>
            </tbody>
          </table>
    <!-- End Photo Table --> </div>
          </td>
        </tr>
      </tbody>
    </table>
    <div id="footer">
    <h2>_ImageName_</h2>
    <ul id="metadata" metalayout="paragraph" rkid="metadata">
      <li>_metaname_: _metavalue_ </li>
      <li><br />
      </li>
    </ul>
    <p contenteditable="true" textid="copyright" common="true" localizable="true">© Copyright-Informationen hier</p>
    </div>
    </div>
    </body></html>

    For most posters here it helped to remove the Aperture application from the Applications folder and to reinstall Aperture from the original installation media.
    Did you originally install from a DVD/CD? Then use that to reinstall, or download from the AppStore again, if you bought it there.
    If you installed from a Trial version download, use the trial to reinstall.
    Download trial version from here Aperture 3.1 Trial
    If reinstalling should not help, post the first 60 lines of the crash log.
    Regards
    Léonie

  • Looking for iPhoto book template for Aperture

    I created a photobook in iPhoto and now need to add a few things that iPhoto wont permit ie images in places that are not on the templates. Therefore, I am trying Aperture since it allows me to modify templates. So, I now need to recreate a template in Aperture that is the same as the one I used in iPhoto. To speed everything up, I am looking to see if I can install the templates from iPhoto. If so, that would save me lots of work. Actually, if I could only import the photobook from iPhoto, that would be even better!
    So, does anyone know where I can get the templates/themes that are in iPhoto and how do I install them in Aperture?

    That is not a possibility - but you can do a page layout in Aperture (or any other program) and print it to PDF using the send PDF to iPhoto option to send an option of it to iPhoto and then add it to the iPhoto book as a full page photo
    LN

  • Collage templates in aperture?

    I`m about to buy Aperture. There is no trial, so I just wonder if aperture has collage templates?
    S

    No, Aperture does not have collage templates.
    Aperture does not support image or graphics compositing at all.
    Aperture is a tool to manage and to organise your photos in a library for easy access and to develope your photos and to adjust them to perfection.

  • Aperture to Pages 8 x 10 glossy template

    howdy,
    Pages 8 x 10 glossy headshot template .zip (4.1MB compatible with Page 5.x & 6.x).
    I've made and handled thousands of these for the modeling and acting industry for many years so the template is basic and ready to go just replace the image and pertinent information with your current model/actor.
    Pages 8 x 10 headshot template
    Once downloaded click on the Pages file to open Pages. Drag a new image in and fill out the info.
    love & peace,
    victor

    Hey, Charles
    You're welcome
    In Pages you crop by masking, so after you bring in your own photo select the photo and Format>Mask With Shape, btw, this is also nondestructive editing! So, bring in the entire image of the model and mask a shape onto it and then grab a handle and resize it accordingly.
    I was doing an export of the image from Aperture but now dragging in a Preview Quality High & Don't Limit from the thumbnail works as well.
    By selecting the Media tab Photos in Pages you can now also look into and select images directly from the Aperture 1.5 Library. Pretty sweet deal.
    Models with extensive credit lists are stapled onto the back of the 8 x 10 glossy.
    victor

  • Possible To Change The Colour Of A Theme Template For A Book - Aperture

    Hi
    I am using Aperture 3 and would like to make a photo book for a recent trip, combined with including the text of a blog I wrote during the journey.
    I like the journal theme that now exists in Aperture theme layouts, but I'd like to change the "bark" colour to a specific yellow that was used for all of the promo literature for the event. Is it possible at all, or am I limited to the few colours on the dropdown list?
    If it isnt possible, do you have any other ideas about how else I could achieve this? I have looked at some of the plug ins available and can only see a few that are either too "upmarket" for the job at hand, or also dont allow to change the background to a specific rgb colour.
    Any ideas anyone?
    Thanks!
    Andy

    .
    0* Proceed at your own risk *0
    There may be a much easier way to do this.
    The color information is stored in separate plists for the large and extra-large books. The plist files are at, for example:
    +/Applications/Aperture.app/Contents/Resources/Book Themes/Photo Journal/Extra Large/Backgrounds+
    You can edit the plist to show whatever color you want.

  • How do I remove a page that Aperture made on its own? I made a 20-pp. book, but Aperture added a p. 21 that cannot be edited or deleted. Even Apple store people could not figure it out. P. 21 has 5 or six images I used as a kind of template.

    I made a book and eventually settled on the 20-page minimum size. I also made a kind of template of one page with 5 or six images and copied-and-pasted them on new pages as a starting point. That bunch of images is now on p. 21 (which should be blank), and no image can be edited in any way, either singly or in a group. They can't be selected, moved, deleted, or otherwise affected. Apple Store people were equally unable to do anything. We tried adding pages in various places, but nothing would let us get rid of p. 21 or any part of it. We also tried copying the book and starting anew on the copy. Didn't work. Suggestions?

    Try this -
    <img src="assets/jpgs/Prodigy Logo Large 2014.jpg" width="180" height="180" alt="" style="display:block;">
    What you are seeing as whitespace is the space reserved for glyph descenders on any element that is rendered within a text box (i.e., an inline element). By making the image "display:block" you eliminate that space because a block element doesn't have descenders. If that works to your satisfaction then you can give the logo an id, and create a CSS selector containing that block style.

  • Editing slideshow reflections template in Aperture

    Hi. I'm trying to put an image+music slideshow together in Aperture for playback on TV. I quite like the reflections theme in Aperture 3 but does anyone know if it's possible to modify the default setting so that each slide shows just one picture? Currently the default appears to show multiple pictures on each slide.
    Any thoughts would be much appreciated.
    Many thanks in advance.

    The short answer is you can't.
    A few times when I needed to do this I skipped adding music in Aperture and just exported the slideshow out of Aperture with no sound. I then imported it into Garageband and added the music there. You can save the finished movie out of Garageband with the newly added audio without re-compressing the video.
    Changing themes is going to require another video editor to piece it together. Create separate slideshows in Aperture with the different themes and reassemble them in something like Quicktime Pro. Then open it with Garageband to add the audio.
    Seems like too much effort to continue to use Aperture for the slideshow. Might as well use iMovie from the beginning.

Maybe you are looking for