Referenced Images

Has anyone tried using their iPhoto library for referenced images (in other words, unchecking the "Copy Photos To The iPhoto Library" box in preferences)? I have always wanted more control of my file structure in iPhoto, and thought this might be a viable solution. My option is Aperture, which I own, but still find the learning curve daunting.
Any advice or tips would be welcome. Thanks.

I have always wanted more control of my file structure in iPhoto
You’re rather missing the point of iPhoto, I’m afraid. The point is to organise your Photos without reference to your files. If you want to organise Files, use the Finder, that’s what it’s for.
In referenced Mode: iPhoto will create an alias in the Originals Folder that points to your file. It will still create a thumbnail and, if you modify the pics, a Modified version within the iPhoto Library Folder.
However, you need to be aware of a number of potential pitfalls using this system.
1. Import and deleting pics are more complex procedures
2. You cannot move or rename the files on your system or iPhoto will lose track of them on systems prior to 10.5 and iPhoto 08. Even with the later versions issues can still arise if you move the referenced files to new volumes or between volumes.
3. Most importantly, migrating to a new disk or computer can be much more complex.
Always allowing for personal preference, I've yet to see a good reason to run iPhoto in referenced mode unless you're using two photo organisers.
If disk space is an issue, you can run an entire iPhoto Library from an external disk:
1. Quit iPhoto
2. Copy the iPhoto Library as an entity from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
If you're concerned about accessing the files, there are many, many ways to access your files in iPhoto:
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

Similar Messages

  • Referenced Images Say They are Referenced But Are Not.

    Is anyone having the following problem? I have about 4500 images that were Imported into Aperture as Referenced. Have been working with them over the past month. Tried making a Web Journal recently and after exporting the pages, many of the images did not show up in the web pages although the caption did. I went back to my Album and went through the images. The ones that didn't show up in the web pages were very strange looking within the Album. As a thumbnail they looked fine but when I put the loupe on them at 100% it was obvious that they were some sort of small jpeg or something due to lots of jaggies and poor quality. Even though the Reference icon was supposedly fine, telling me it was online since it did not have a yellow warning label, for some reason Aperture was not accessing the original RAW file.
    I now have hundreds of images I have to try and find in the Album that say they are referenced but really are not.
    Prior to this web journal problem showing up Aperture had been showing me many of these files were not online even though the drive was definitely hooked to the computer and I was able to go to the same images via the Finder and actually see that they were there. One minute the overall project registered images offline, I would click on an Album and they would register as Online. Then switch back to the Project and amazingly they register as online. Back down to the Album and it tells me they are off line. Back and forth from project to album and a different icon 50% of the time. I knew something was up.
    I eventually tracked down many of the images that said they were online but by reviewing them it was obvious they were not due to the jaggies I mentioned above. When I would find one like this I went to Manage Referenced Photos and reconnected the image even though it's telling me it is already connected. After doing this to many of the images I reproduced the web pages and they then showed up. I nearly had all the images showing up except for one that I must have missed in reconnecting so I went back to do just that. As I scrolled through the Album and the Web Journal, many of the thumbnails would turn gray and then finally an image would show up. This happened to dozens of images. I found the one that had not shown up in the last export of the web pages, reconnected it (even though it said it was connected) and then exported the web pages again. Unfortunately I was back to square one. Once again dozens of images were now not showing up in the export of the web pages again.
    I just can't believe how buggy 1.5.2 seems to be. I thought maybe it was something to do with Repairing Permissions so I went and did all of that. Still no luck! Anyone else experience anything like this? I'm about ready to give up on this software.

    Victor,
    Yes larger hard drives will help but the day they are large enough to fit in a laptop with a professional photographers entire collection is a long way off and may never happen. There is no reason why Referenced files needs to be so difficult. Two quality programs that handled it with ease was RAW Shooter (now gone having been bought by Adobe) and Photo Mechanic which is superb for some tasks. For Aperture to have this many issues with referencing images is unacceptable and the market place will bear this out. I've quite using the program all together and have gone back to Photo Mechanic combined with IView and Photoshop. There's still room for an Aperture like product but Apple better get moving to make it work better. Microsoft just announced some of the upcoming IView capabilities that will be available next year. Adobe has CS3 and Lightrooom and I'm guessing Photo Mechanic isn't resting on it's heels. I really, really wanted to like Aperture and I worked with it day in and day out for nearly two months. As time went on the Referenced files just kept getting more and more unstable and I lost a ton of work due to it no longer being able to see some of those files.
    MacBook Pro Mac OS X (10.4.7)
    MacBook Pro Mac OS X (10.4.7)
    MacBook Pro Mac OS X (10.4.7)

  • How to move referenced images to a new Hard Drive

    All my Aperture referenced images (about 80.000) are stored at a 300gb firewire HD. That's not enough and I plan to move all my photos to a new HD, 1Tb probably.
    I understand that I can't move the images directly from one drive to another. So what's the easiest and painless way to upgrade and still maintain the integrity of Aperture Library ?

    {quote:title=Bauhausler wrote:}I understand that I can't move the images directly from one drive to another.{quote}
    Well, that's exactly what you can (and should) do. Then use the "Manage Referenced Files..." command.
    Take a look at my answers in this recent thread:
    http://discussions.apple.com/thread.jspa?threadID=1721897
    Regards
    Paul K

  • Moving Referenced Images to a new HD

    Hi,
    I have my 500GB external HD almost full with all my Aperture referenced images.
    I got a new 1TB HD.
    I Would like to move all my original folders keeping Aperture modifications on the images (metadata, adjustments, etc...).
    Can I just copy the content of 500GB HD into the 1TB and somehow give to Aperture the path to the new HD? (the library file is on the computer's HD)
    Thanks!

    You can copy everything and then reconnect the files, but you'd be better off using the File>Relocate Masters... command.
    Ian

  • Exporting projects with referenced images

    I want to import referenced images from an external hard drive, edit them and then export the project in order to archive it. Is this something that I can do now? Will I end up with a bunch of referenced previews in my library and an exported project that can link back up to the master images that are on a separate hard drive?
    Antonio

    No, this only exports a "copy" of your projects and does not remove the master image. It is still in the Aperture Library. I am also trying to find an easy way to move the entire project outside of the library and still maintain a reference link to wherever I move the images to. Any thoughts?

  • Upgrading from Aperture 2-3. What happens to referenced images?

    I'm upgrading from Aperture 2 to 3. I have referenced images on some external hard drives. Will my referenced images be okay and still read correctly from my HD if I upgrade?

    Hi
    I had no problems it retained the Referenced File location info you will have to ensure the externals connected.
    If they are not linked as indicated by a red line through the referenced file icon bottom RH corner
    Select the images that need reconnecting and then go to File / Locate Referenced Files
    You will get a dialogue box which enables you to find the Referenced File/s then click Reconnect or Reconnect All
    I just had to do it because I renamed an external drive
    Hope this helps

  • Loupe Offline for Referenced Images?

    In the Aperture 3 documentation, we get this...
    Even though the masters are offline, you can browse, search, and assign metadata to preview images. You can even use the Loupe to zoom in on preview images, because they are high-quality JPEG files.
    And in Aperture 2, this was correct. Now that I have finally gotten around to upgrading to Aperture 3, I find this functionality is broken. The loupe is displayed as "offline" for referenced images and refuses to magnify my previews (though I can zoom in on them just fine).
    This is a big problem, because i rely on the loupe for sorting images, and don't always have my master images available.
    Is there a way to restore the loupe for viewing previews like Aperture 2?

    In the Aperture 3 documentation, we get this...
    Even though the masters are offline, you can browse, search, and assign metadata to preview images. You can even use the Loupe to zoom in on preview images, because they are high-quality JPEG files.
    And in Aperture 2, this was correct. Now that I have finally gotten around to upgrading to Aperture 3, I find this functionality is broken. The loupe is displayed as "offline" for referenced images and refuses to magnify my previews (though I can zoom in on them just fine).
    This is a big problem, because i rely on the loupe for sorting images, and don't always have my master images available.
    Is there a way to restore the loupe for viewing previews like Aperture 2?

  • Updating Referenced Image Folder names

    Hi,
    My Aperture library is a Referenced Library. My referenced images are stored on an external FW 800 drive and my file system is setup as: Folder Name/Project Name. This has worked great for me, but causes issues when I make changes to the organizational system of my library. I know that Aperture is smart enough to still link the correct files even if the folder/project system is off.
    My question is: How do you keep the folder system synced and intact when using a Referenced Library after making changes to the names of Projects, etc? Is this possible? If not, what system of fouler organization works best for keeping things simple, organized and in sync with as little confusion and downtime in terms of work flow?
    I'm looking for some general (and specific) ideas from users here.
    Thanks,
    Mac

    macorin wrote:
    The question for you is: What need are you trying to meet by mimicking in your Master file storage and retrieval structure?
    Kirby,
    First, thanks for the lengthy and helpful response. In thinking about what you wrote, I probably don't need to worry about my Master file storage structure. So long as Aperture is able to find my Masters no matter the folder, project, album they sit in, I should be fine. My initial thinking was that if I wanted to access my Masters (for some reason) outside of Aperture, it would be easier for me to know where everything was. That being said, I don't really ever need to do that, as everything can be done straight from within Aperture. Still, it just makes me a little uneasy knowing that my images are organized and structured one way in Aperture and another outside of it where those images are linked to.
    Don't let it make you uneasy. Even if they are all in one 55-gallon bag (or Finder folder), they are easily sorted by date (and time) taken, and by file name. These two alone -- esp. if you have renamed your Masters with a good and rigorously applied file-naming convention -- should meet every need you might have.
    Moreover, your Aperture Library of images should be deeply hyperlinked. That's a big reason to use Aperture. None of those hyperlinks are create-able in a file storage system.
    At the risk of being (even more) off-putting than usual: think on that. Beginning to understand that difference allows you to manage your data in much more successful ways.
    The second reason I was asking is because when I import into Aperture as a Referenced Library, I also back up those images to a second external hard disk. I generally keep this back up archive organized and structured the same way as my Masters structure. If I ever deleted a Referenced Master and then later on wanted to re-import it from my back up archive, it makes it easier to find things, etc if they are organized the same way.
    I don't buy it. Can you give an example of a situation in which you need to find a file and you don't know the date it was taken (at least roughly) or some part of the file name?
    Your Masters need almost no storage structure at all.
    IME, once I started using Aperture's extensive image management tools, I found I had almost no -- zero, nada -- file management needs beyond back-up.
    If you read what I wrote just above, I guess this plays to that. How do you manage your back-up file management system if things change in ways that I have suggested, i.e. renaming projects, etc and moving things around from one project to another?
    I try to keep two additional copies of every Library and every set of Referenced Masters at all times. One set is kept off-site. It's not hard to do -- but I do run copy operations that last all night. Aperture's Vault can serve as one of the Library copies. I have found it easier to manage when I don't use Vaults, so I stopped using them. If you find Vaults convenient, use them.
    Just to be clear: My main goal is to make sure that my back-up file management structure mimics my Aperture Library Folder, Project, Album (well, not album as you can't organize at this time by album name) structure. I am not talking about the structure of where my Masters are stored, but rather the structure of my back-up. I hope this makes sense.
    This does not make sense. +File management+ refers to Referenced Masters and not to Aperture Folders, Projects, or Albums.
    Your Aperture Folder, Project, & Albums (all of 'em) structure is part of your Library. Back up your Library, and you have backed up that structure.
    The files an Aperture user needs to back up are
    - your Aperture Library (an OS X package of hundreds of thousands of files)
    - all your Referenced Masters.
    That's it.

  • Corruption of the Location of Referenced Images

    In other threads we have discussed problems with Aperture becoming confused about which referenced files it is supposed to connect with. Here is my analysis of one aspect of this problem.
    When you have a group of referenced files, if you move some of them to another folder on the same volume or rename them Aperture attempts to find the moved file and change the reference to it. This might be what you want, or it might not, so Aperture ought to ask you whether to change the reference or not. But it does not.
    If the volume on which you have your original files is not mounted, Aperture will mark the files as unavailable but will not change any links. This is clearly the behavior one would expect.
    A problem occurs when your files are missing, but the volume they were on is mounted. This might happen if, for example, if one of your folders had been inadvertently deleted and needed to be reclaimed from a backup disk. In this situation Aperture "reconnects" the references in your Aperture library to what appears to be arbitrary files on the volume. The new references likely bear no relation to the files you really want. This is clearly not the behavior you would expect or want. When this happens it is usually impossible to use the "Manage Referenced Files" command to reconnect the files, because the correct files and the ones now referenced in the database aren't the same size and don't share the characteristics which permit the "Reconnect" button to be enabled when the reference and correct file are selected in the "Referenced File" dialog. Even the "option key" trick which sometimes allows the "Reconnect" button to be forcibly enabled will not work once this happens.
    Obviously, this is a potentially catastrophic issue if a huge number of file references become corrupted in your library. The only way to fix things that I have found is to reimport all of the correct referenced image files, then lift and stamp metadata and image corrections from the corrupt reference entries in the library to the "new" referenced files. This is extraordinarily tedious if the number of files affected is large.
    In any event, this is a serious bug and it should have been found long ago in Apple quality assurance testing and fixed. It ought also to be possible to just hand enter the correct reference to a referenced image in the library if nothing else works.

    Possibly going to settings, general, international, region format, then select the country you are in.

  • How can I tell whether a project has managed or referenced images

    Hi all,
    Another noob question.
    I started working with Aperture and imported about 20GB of photos from my hard drive into one big project. But I can't remember whether I imported them as managed or referenced images. I want to clean up my drive and delete one set of these if they're duplicates.
    Is there an easy way to determing if the images in the Library are managed or referenced? I've looked all over for an answer, but can't find one.
    Thank you!

    The "badges" in the lower right corner of each image will tell you if the image is a "referenced" image.
    See this page for an explanation of the badges: http://documentation.apple.com/en/aperture/usermanual/index.html#chapter=11%26se ction=9%26tasks=true
    The badge icon will either be a small rectangle (which represents your photo) with an arrow (indicating that the real photo is elsewhere -- aka "referenced", or it will the rectangle will have a red slash through it, meaning it's a referenced image but the master is currently offline.
    There's a third possible icon... which is yellow warning triangle (has a "!" in it) with the arrow. This means the referenced master was not found (e.g. the Mac can find the filesystem & folder, but your image is not there.) This means someone decided to delete or move images in the filesystem -- bypassing Aperture.
    On a related note... it is possible to change your mind about whether you want images to be "referenced" vs. "managed". The "Aperture" -> "File" -> "Relocate Master..." will allow you to pick a folder on the hard drive and Aperture will copy the masters to that location -- converting a "managed" image into a "referenced" image. The "Aperture" -> "File" -> "Consolidate Master..." will do the opposite... it will convert a referenced image to a managed image, but does offer the choice of whether the "copy" vs. "move" (e.g. do you want to leave a copy of the image out in the filesystem which is no longer associated with Aperture vs. have the only copy of the master living inside the Aperture library.)
    Message was edited by: Tim Campbell1

  • How to find referenced images in Aperture Library

    Hi,
    On starting Aperture it tells me I have 18 referenced images. When creating a vault it tells me all but these 18 referenced images will be backed up. Problem is, try as I might I can't find these referenced images anywhere in my Aperture library, and yes I've even checked my rejected images.
    Can anyone shed any light on this?
    Thanks in advance.
    Alistair

    The apfile for a referenced image contains an extra key: fileAliasData.
    So get a copy of TextWrangler (or BBEdit) and search the library for all files ending in apfile that contain the string fileAliasData. This will tell you which images are affected and where they are.
    The other difference is that fileIsReference is set true for referenced masters and false for managed masters.
    See this link for some idea of how to do multi-file searches with TextWrangler:
    http://www.bagelturf.com/files/97660a1a1ba5b7f45c1d43b34dbce327-812.html

  • Displaying paths of referenced images

    I would like to see the path to the finder of my referenced images. Not one by one, using "Show in Finder" nor using "Locate refrenced files", but as Metadata.
    Is there a way to display this information? Other posibility would be to display it in the list view
    Thanks

    OT:  Hi Kevn.  Glad to get a name on your handle.
    You didn't directly comment on it. You just kept his misspelling.
    I commented on it -- just not directly.  That's at least a couple of elevator buttons above just repeating the error.
    Fwiw, I assumed since Frank first filled out his location data that his was an ironic comment.  I guess the raised eyebrow lifted my sight.
    We now return you to our regularly scheduled program  .  I think we have whining scheduled in Studio J at 3 PM.

  • Anyone care to write up a workflow solution using referenced images?

    So, I'm having a little bit of a hard time figuring this out, but I think I got something. I'd like others to share their thoughts and opinions about how to get a good referenced workflow going. Maybe we can come up with an efficient method of working on, say, two machines with only one folder of images and a way to archive them efficiently too.
    I'll post what I think I can now do with Aperture 1.5.
    1 - I shoot a bunch of shots, in the field, and download them to my Powerbook
    2 - I rename the raw files in the finder (my preferred choice) and save them out to an external hard drive
    3 - I fire up Aperture on my laptop and import those pix from my external hard drive as referenced images. This does a couple of things: One, it keeps my internal laptop hard drive from filling up and, two, it will allow me, when I get back to my fast killer desktop, to transfer, or work on, the images from this external hard drive.
    4 - I doodle away, in Aperture, on my laptop until I'm happy.
    5 - When finished, I can export a copy of the project I just worked on to the external drive, but make sure that the "consolidate images" option is off (no need to have 2 copies of the RAW file on the same external hard drive). This will give me, on the external drive, a project with all the adjustments (and preview images) along with a folder containing the RAW files. I'll also have a copy of the project on my laptop hard drive as a backup (I suppose I'd have a backup of the raw files on a burned DVD or another hard drive too).
    6 - I get back to my desktop and plug in the external hard drive.
    7 - I import the project from that external hard drive. Since the RAW files are still on the hard drive, there's no problem with the project finding the actual files.
    8 - But, I do not want to work the files from the external hard drive (speed is an issue). So I copy the folder of RAW files to my internal hard drive and delete the RAW files from the external drive.
    9 - Aperture tells me (through the badges underneath the thumbnails) that the RAW images are no longer connected to the project.
    10 - I select all the images in the project and right click (or control click) and choose from the contextual menu, "Manage Referenced Files."
    11 - From the dialog box that appears, I navigate to the internal hard drive where I copied the RAW files to and choose to "reconnect all images." The badges under the thumbnails update to let me know that the images are back online.
    12 - I futz with the images some more and do whatever else I need to do.
    13 - Done. Job finished. No need to have access to RAW files anymore, although I want to keep preview images in Aperture for websites, email, etc.
    14 - At this point I think I can do several things. I can export the project and "consolidate images into exported project," and archive that exported project to whatever medium I use for archiving. Or I can just archive the folder of RAW images and eventually delete them off my internal drive. This last option will leave me with preview images inside Aperture (along with badges that tell me the originals are offline). I can back up that project using the vaults method that comes built into Aperture. That way I'll have several copies of the project (with the JPEG previews) and offline RAW files (also copied and archived) that I can reconnect at anytime I want to in the future. This will help keep my Aperture library smaller and more manageable with plenty of backups.
    How does that sound?

    I tried out something like your flow, though I attempted to let Aperture do the intake step right to the Aperture library on the laptop and then work to a portable drive by exporting the consolidated project (I tried my iPod as a temp drive which worked just ok) from there.
    The G4 17 in - lorez - is pretty marginal for Aperture. Working with a few images was just ok, but I really don't think it's up to a couple of gigs of NEF files. What I wanted to accomplish the same goal - a reference set of pictures on the working hard drives with originals offline and archived in a couple of places.
    But after trying this I'd say your scheme of importing to the portable drive and working in the finder and renaming with ABetterFinderRename prior to any import is a better one. The more I can hold down the Aperture's processing overhead the better. The other thing I plan to try is to use iPhoto for the first look. No messing with the images, but I can look at them and toss out the garbage, do some tagging and then, on the G5, let Aperture import the resulting file structure from the portable hard drive and carry on with your scheme.
    Once the images are to my liking in aperture I can export a finished set for iPhoto on my Laptop for emails and etc.
    After messing with this for awhile, I don't see anything in your workflow that is not going to work.
    I imagine as time goes on that lots of people will be going through all these steps. I hope the designers can figure out some simplifications. A media manager in Aperture, much as the one in Final Cut Pro would be welcome for much of this. Or droplets or buttons with the more tedious bits of the workflow included would be welcome.

  • Problem with Referenced Images

    Hi all,
    I have some documents that all follow the same structure.
    doc1\doc1.book
    \*.fm
    \images\A.jpg
    doc2\doc2.book
    \*.fm
    \images\A.jpg
    In both documents, I have an imported image file that I want to be "images\A.jpg".
    my doc2 directory would have been created by copying and renaming doc1 (because they all follow the same document template/format). But in doc2's .fm file, my referenced image file's path is "..\doc1\images\A.jpg", referencing to the original file.
    I've tried renaming doc1\images\A.jpg to doc1\images\B.jpg, and opening the doc2 .fm, which then says it can't find "..\doc1\images\A.jpg" and asks me to replace it with another file. So, I use "images\A.jpg" (which is in the doc2 directory). That seems to work. But this seems to also change the link in the doc1 .fm file to point to "..\doc2\images\A.jpg".
    So, the problem seems like both .fm files will always point to the same image file. I don't know how to disconnect these, so that they can work independently from each other. i.e. each doc directory (doc1 and doc2) is self-sufficient.
    Any ideas?
    Thanks in advance.
    Kevin

    Kevin,
    If I understand you correctly, you have created the doc1 folder, inside is the doc1.book, *.fm files, and an images folder. One of the *.fm files references the A.jpg image in the images folder.
    Create the doc2 folder, then copy all the files and folders inside doc1 to inside doc2. Do this in Windows Explorer, NOT FrameMaker.
    Rename the doc1.book inside the doc2 folder to doc2.book. Everything should be as you want it to be.
    NOTE that if you open doc1/*.fm in FrameMaker and then save it as doc2/*.fm, then FrameMaker recalculates the path to A.jpg to point to the file doc1/images/A.jpg, because FrameMaker assumes you want to retain your links to the original image files. The difference from the procedure above is that you are doing the copying within FrameMaker, not within the Windows file system.
    Van

  • Unsuported Image Format error with referenced images

    Hi,
    importing referenced images does not work for me: when selecting "store images in their current location" (i.e., referencing them), the preview is visible for a moment and then becomes gray; the large preview says "Unsupported Image Format" (if AP doesn't crash at all).
    When moving the same images into the library, it works fine. This applies to Nikon RAW (NEF) files (from a D70 and D2H) as well as plain JPEGs.
    I'm using Aperture 1.5.2 / OSX 10.4.8 on a Mac Pro; DigitalCameraRAWUniv200601.dmg is installed.
    Thanks in advance for any hints,
    Bernhard
    Mac Pro 2.66   Mac OS X (10.4.8)  

    Just if anyone cares (somehow this seems to be a rare issue), using referenced images seems to work if I choose a specific location ("Pictures") in the import dialog. The images get copied to a project-specific subfolder of ~/Pictures/ from where they are referenced, seems to work ok.
    BB

Maybe you are looking for

  • Excise internal document getting reversed on reversal of GR(Imports)

    Hi! On reversal of imported GR docuement, the internal document is getting reversed resulting in-correct figure in the part-1 register. e.g : I have 3 documents in a PO(Qty-10MT), i.e. GR1-5MT, GR2-3MT & GR3-2MT     At this point the Entered field wi

  • Unable to run Solution Manager Diagnostic in txn DSWP

    Hi, In txn DSWP, I click Goto-Solution Manager Diagnostics, the browser is launched with this address: http:<hostname>:8000/smd However, it says "Page cannot be displayed" I have checked that the its services in txn SCIF are activated. I can see HTTP

  • Online Code Walk-Through Wednesday on How To Build an OSMF Player Strobe Media Playback

    Wednesday November 17 at 12:00 noon PDT the OSMF User Group is hosting an online  code walk-through of the open source Strobe Media Playback video  player codebase. The code walk-through will be lead by Andrian Cucu who is  Adobe's Project Leader on

  • Error on Call Manager 7

    Hi all we have 2 Call Manager 7.1.2.31900-1 boxes. Recently we had a power outage and the servers were not shut down properly. One remaining issue we are having trouble resolving is this error below. It appears in the logs every 15 seconds or so. Any

  • Install Oracle Developer with oracle database 8i

    Hi, My laptop has a 8.1.7 database already installed, 9ias as well installed. Know i've need to install Oracle Developer 2.5. I had run the oracle installer and i did installed the Oracle developer in a new oracle Home . Know i cant't start my databa