Converted clipping path to frame (InDesign CS2)

I am working with files where the person has converted clipping paths to frames for the images. I need to resize the images but it leaves a blank silhouette of the hollowed out space (where the image was) and a view in the background of the full image, including the background. I'm new to InDesign and need to find out how to resize these images or how to undo the convert clipping path to frame. Any help would be appreciated.
Thanks.

How are you trying to resize the frames now? Try Pressing Ctrl + Shift BEFORE you click the mouse on a sizing handle and drag. (you shouldn't need to press the keys first, but there was a bug in CS3 and I think it may still be in CS4 on the Windows platform).
You can also use the scale tool (hold shift to size proportionally) or use the SCALE fields -- the third set from the left, not the second set which are height and width of the frame only -- on the control panel or in the transform panel. These scale both content and container together.
By default the scale fields will say 100% after any transformation, and ID expects you to input percentage values in them and interprets numbers without units as per cent, but you can enter any value you like as long as you specify the units, so you can put 3in into the width field and the frame will become 3 inches wide. Scaling using the control panel is relative to the control point in the proxy on the left end, so if you select the upper left point, the upper left point of the bounding box will remain stationary and everything else will move toward or away from that.
Peter

Similar Messages

  • Using frame as a clipping path for photo - InDesign CS4

    Hi, This sounds very simple but its just not happening.
    I am trying to crop a jpg image by using the shape I created with the a combination of the rectangle frame tool and the ellipse tool. First I created a rectangle. Then I created a circle. Then I cut the corner from the rectangle with the Scissors. Then I moved the circle into place on the cut corner. Then I grouped the 2 objects together. The result is a rectangle with the top right corner curved.
    I can fill it with a colour from the Swatches panel, and the colour conforms to the shape.
    I really need to place a picture into the shape, so that the shape crops the picture.
    The best I can do is fill the rectangle, it seems to disregard the circle.
    Is there a magic solution to this? I'm helping a work mate change over from using Microsoft Publisher. Apparently Publisher can do this easily, so its really embarrassing that I can't get InDesign to do the same.
    Thanks

    You don't have one object. You have a group.
    Use the pathfinder panel to turn it into one object and then place the photo.
    But a better idea would be to just use the pen tool to draw it.
    Bob

  • Missing Menu items - (Clipping Paths) InDesign CS3

    I've logged this before but had no success. However - I now know what's causing my problem.
    Ever since CS2, we've had a problem with missing clipping paths. We get the same in CS3 where Object>Clipping Path loses the 2 sub menus (Options and Convert Clipping Path to Frame). This problem seems to be on the increase and I'm having to fix about 10 per week on a base of 200 machines.
    If I log on to the faulty machine as a different user then it's OK (so it has to be preferences - doesn't it?). I don't want to delete prefs as we have certain settings which we want to keep. And then I discover that if I simply replace the InDesign contents in Applications, it fixes the problem.
    Because this is a very quick fix, and production being production, I didn't get time to work on the problem. But eventually I got a clone of a failed machine and was able to get to the problem.
    Domain/(domain name)/Users/(Users name)/Library/Caches/Adobe InDesign/InDesign SavedData.
    If I move this file between machines, I can move the fault around. If I bin the file, it gets recreated and all is OK.
    From what I've been able to discover, a combination of SavedData and InDesign Defaults make up the InDesign Prefs.
    So, the question is: what problems could I generate by binning SavedData every time a user logs on to the machine??
    As an aside - I thought initially that the SavedData file was giving the error when it reached 11.4 Meg, but then I find machines with 12 Meg files which were OK!

    "binning"? Is that like deleting or throwing out the trash?
    If so, I see no ill effect from deleting the 'saved data' file. Only if InD crashed last time it ran, you will lose the recovery of the last document(s). Deleting the other preferences or defaults will only reset InD to its factory defaults. If you have settings like special hyphenation, object or paragraph styles, preferences for workspaces or toolbars in single column or layout of pallets, you will lose those.

  • Converting tif with clipping path to solid spot color CS3

    There must be a better way to do this, I need to make an opaque white spot color overprint the silo'd 4/C image (this is for a window cling). In the past I would duplicate the tif, convert to grayscale, fill with black, duplicate the placed tif, re-link to the new grayscale tif and color it to the spot color. This works fine, but is there a way to simply duplicate the placed tif, delete the image and fill the path with a spot color? TIA

    Absolutely. First copy the image and then paste in place. Right click and choose convert clipping path to frame. Delete the image from that frame and fill it with color.
    Bob

  • Clipping Path vs Alpha Channel

    Not sure if this is the right place to ask, but wondering which is better for outlined images (no soft transitions, just hard outline.)
    I've used both and don't see an advantage to either EXCEPT when converting an InDesign file to PDF. Files with PSDs with clipping paths seem to make much larger pdfs than same file using PSD with alpha channel. Not important for a final press file, but when I have to email screen proofs, then it's a big deal.
    Anyone care to weigh in? Thanks.
    Ringo

    Hi, there,
    I found this discussion during a search for alpha channels vs. clipping paths for clipping (for a job I'm working on), and thought I'd offer my own feedback based on my own experiences w/ similar files. I can't really offer a printer perspective, however, although we do work closely with many and also print film fairly regularly for local printers who are not yet Direct-To-Plate.
    For what it's worth, I use paths, myself, and save the file as a TIFF. Then I use the Object: Clipping Path menu in InDesign to select the path (I don't specifically designate a path as an actual clipping path in Photoshop anymore, as sometimes an image will have more than one path to isolate different elements).
    I find that alpha channels don't look very good when used in InDesign. They're just not that smooth/precise, in my admittedly limited use.
    I've uploaded a quick sample to http://i486.photobucket.com/albums/rr222/Xiebinrui/Alpha_vs_Clipping.jpg -- it's pretty self-explanatory, but the left side shows the bottom of an image using an alpha channel created from the original clipping path (cmd-click on the path to create a selection and then click the "create channel" button in the Channels tab, which automatically creates an "Alpha 1" channel), with the original clipped version on the right. I've tried adjusting the threshold and tolerance in InDesign, but it just always looks bad.
    I also haven't used the behemoth Photoshop EPS format since my QuarkXPress/Mac OS 9 days (even then, it eventually became possible to use TIFFs w/ clipping paths -- I could finally see my photo correctly instead of with the horrible Quark EPS preview).
    Anyway, re: alpha channels, maybe it's just that I don't know the right way to use them, but they don't seem to be very smooth when importing into InDesign (I was working on a job yesterday and today for which I had to download hi-res images from the client -- many of which used alpha channels instead of actual paths, but they're used on white backgrounds in InDesign, so I just didn't use the channels).
    So, anyway, I personally use and recommend paths (vector masks, as Artdirectorringo mentioned, seem to work fine, too) as opposed to standard pixel-based alpha channels, in general, if you're going to be placing the file into InDesign.

  • Detecting clipping path in EPS file

    Hi All,
    I have problem with detecting clipping path settings in EPS.
    It's easy to find all cliping paths in file, they are listed in clippingPath.photoshopPathNames
    but when EPS is saved with clipping path selected, this path is always applied and clippingPath.clippingType is ClippingPathType.none
    I can't find any property which can be usefull to detect.
    Thanks!
    Piotr

    Hallo Piotr,
    Perhaps the following approach can help.
    The script places the eps (inside the selected frame) twice in a new layer: the first time with property epsImportPreferences.epsFrames = false and then with true. Afterwards the dimensions were compared and the layer deleted.
    Please note that it will only work if the paths are smaller than the image dimensions.
    #target InDesign
    var _eps = app.selection[0].epss[0];
    var _uerEPSFrames = app.epsImportPreferences.epsFrames;
    var _tempLayer = app.activeDocument.layers.add();
    try {
      if(_eps instanceof EPS && _eps.clippingPath.photoshopPathNames.length>0) {
        if(_eps.clippingPath.clippingType == ClippingPathType.NONE) {
          var _savedClippingPath = __savedWithClippingPath(_eps,_tempLayer);
          if(_savedClippingPath[0]) {
            alert("Clipping path applied in Photoshop" + "\r\r" + "Path name: " + _savedClippingPath[1]);
          } else {
            alert("EPS without applied clipping path (Photoshop and InDesign)");
        } else if (_eps.clippingPath.clippingType == ClippingPathType.PHOTOSHOP_PATH) {
          alert("Clipping path applied in InDesign" + "\r\r" + "Path name: " + _eps.clippingPath.appliedPathName);
    } catch(e) {
      alert(e);
    app.epsImportPreferences.epsFrames = _uerEPSFrames;
    _tempLayer.remove();
    function __savedWithClippingPath(_curEPS,_tempLayer) {
      app.epsImportPreferences.epsFrames = false;
      var _tempEPS_1 = __placeFile (_curEPS,_tempLayer);
      app.epsImportPreferences.epsFrames = true;
      var _tempEPS_2 = __placeFile (_curEPS,_tempLayer);
      if(_tempEPS_1.geometricBounds[2] == _tempEPS_2.geometricBounds[2] && _tempEPS_1.geometricBounds[3] == _tempEPS_2.geometricBounds[3]) {
        return [false,""];
      } else {
        _tempEPS_1.clippingPath.clippingType = ClippingPathType.PHOTOSHOP_PATH;
        return [true,_tempEPS_1.clippingPath.appliedPathName];
    function __placeFile (_file,_layer) { 
      var _filePath = _file.itemLink.filePath;
      var _fileToPlace = File(_filePath);
      return app.activeDocument.pages[0].place(_fileToPlace,[0,0],_layer,false)[0];  
    A little roundabout, i know, but i think you can not obtain the value in a direct way. But maybe someone else knows a better way.
    Roland

  • Does InDesign CS2 work with Snow Leopard

    I know, I know, I should be using CS4 but a client insists on sticking with CS2 and files made in newer versions aren't compatible with CS2.
    So, can anyone tell me if InDesign CS2 will work with Snow Leopard? It's only InDesign I'm worried about - I have current versions of Photoshop etc.
    Thanks
    Phil

    InDesign 4.0.5 is causing me real problems on Snow Leopard, and I'm considering rolling back to Leopard (which worked fine) unless there is a fix to this soon. As well as the disappearing text display problem that others have mentioned, InDesign is very hit and miss when it comes to exporting PDFs - often hanging during the process and then crashing. Error message is posted below. For me, this makes CS2 unusable, but I have a number of ongoing projects that have to remain in this format!
    Paul
    Process: translate [499]
    Path: /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2
    Identifier: com.adobe.InDesign
    Version: 4.0.5.688 (4050)
    Code Type: PPC (Translated)
    Parent Process: launchd [81]
    Date/Time: 2009-09-23 15:31:26.127 +0100
    OS Version: Mac OS X 10.6.1 (10B504)
    Report Version: 6
    Interval Since Last Report: 558 sec
    Crashes Since Last Report: 1
    Per-App Interval Since Last Report: 382 sec
    Per-App Crashes Since Last Report: 1
    Anonymous UUID: 46BCF64C-DE78-4C78-ABBF-723F95CD4F55
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x00000000000000c8
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread
    Thread 0 Crashed: Dispatch queue: com.apple.main-thread
    0 com.adobe.InDesign 0xb80c5e94 0xb8000000 + 810644
    1 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    2 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    3 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    4 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 1:
    0 libSystem.B.dylib 0x800c57da machmsgtrap + 10
    1 libSystem.B.dylib 0x800c5f47 mach_msg + 68
    2 com.adobe.InDesign 0xb819448f CallPPCFunctionAtAddressInt + 206155
    3 libSystem.B.dylib 0x800f2f39 pthreadstart + 345
    4 libSystem.B.dylib 0x800f2dbe thread_start + 34
    Thread 2:
    0 com.adobe.InDesign 0xb815ae44 spinlockwrapper + 90152
    1 com.adobe.InDesign 0xb8179d27 CallPPCFunctionAtAddressInt + 97763
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 3:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 4:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 5:
    0 com.adobe.InDesign 0xb815ac0f spinlockwrapper + 89587
    1 com.adobe.InDesign 0xb818c47b CallPPCFunctionAtAddressInt + 173367
    2 com.adobe.InDesign 0xb818ef7c CallPPCFunctionAtAddressInt + 184376
    3 com.adobe.InDesign 0xb80e8a4f 0xb8000000 + 952911
    4 ??? 0x812ce286 0 + 2167202438
    Thread 6:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 7:
    0 com.adobe.InDesign 0xb815aa4c spinlockwrapper + 89136
    1 com.adobe.InDesign 0xb8176e2d CallPPCFunctionAtAddressInt + 85737
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb8145da1 spinlockwrapper + 3973
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 8:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 9:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 10:
    0 com.adobe.InDesign 0xb815ac0f spinlockwrapper + 89587
    1 com.adobe.InDesign 0xb818c47b CallPPCFunctionAtAddressInt + 173367
    2 com.adobe.InDesign 0xb818ef7c CallPPCFunctionAtAddressInt + 184376
    3 com.adobe.InDesign 0xb80e8a4f 0xb8000000 + 952911
    4 ??? 0x812ce286 0 + 2167202438
    Thread 11:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 12:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 13:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 14:
    0 com.adobe.InDesign 0xb815ae05 spinlockwrapper + 90089
    1 com.adobe.InDesign 0xb816ae3b CallPPCFunctionAtAddressInt + 36599
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb8145da1 spinlockwrapper + 3973
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 15:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 16:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 17:
    0 com.adobe.InDesign 0xb815aa83 spinlockwrapper + 89191
    1 com.adobe.InDesign 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
    2 com.adobe.InDesign 0xb80c6c97 0xb8000000 + 814231
    3 com.adobe.InDesign 0xb80c01bb 0xb8000000 + 786875
    4 com.adobe.InDesign 0xb80dda6c 0xb8000000 + 907884
    5 com.adobe.InDesign 0xb814551b spinlockwrapper + 1791
    6 com.adobe.InDesign 0xb801d03b 0xb8000000 + 118843
    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x000000c8 ebx: 0xb80c5e6c ecx: 0x00000000 edx: 0x00000002
    edi: 0x000000c8 esi: 0x804040a0 ebp: 0xb7fffa08 esp: 0xb7fff9d0
    ss: 0x0000001f efl: 0x00010202 eip: 0xb80c5e94 cs: 0x00000017
    ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
    cr2: 0x000000c8
    Binary Images:
    0x80000000 - 0x8006afe7 libstdc++.6.dylib ??? (???) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
    0x800c5000 - 0x80269feb libSystem.B.dylib ??? (???) <E58B649F-FFDC-AB09-2028-8B706BEF7C0F> /usr/lib/libSystem.B.dylib
    0x802e9000 - 0x802ecfe7 libmathCommon.A.dylib ??? (???) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
    0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <211AF0DD-42D9-79C8-BB6A-1F4BEEF4B4AB> /usr/lib/dyld
    0xb8000000 - 0xb81defff +com.adobe.InDesign 4.0.5.688 (4050) <3E4E06B8-E1FC-B232-1371-643DC0FBE8C9> /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2
    0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <E58B649F-FFDC-AB09-2028-8B706BEF7C0F> /usr/lib/libSystem.B.dylib
    Translated Code Information:
    Rosetta Version: 22.23
    Args: /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2 -psn0176171
    Exception: EXCBADACCESS (0x0001)
    Thread 0: (0xb0a7fd74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf08a0dc0 r02: 0x00000000 r03: 0x00002103
    r04: 0x00000040 r05: 0x3b9aad19 r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9aad19 r09: 0x00000000 r10: 0x3b9aad19 r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b6d0 r22: 0xa0b4b6c4 r23: 0xa0b4b6cc
    r24: 0x0000035e r25: 0xaee33c8e r26: 0xa0b4b35c r27: 0x00000040
    r28: 0x0000000f r29: 0x224d2d19 r30: 0xa0b4b6a4 r31: 0x96170fc4
    Thread 1: (0xb019ed74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf0182dc0 r02: 0x00000000 r03: 0x00002403
    r04: 0x00000040 r05: 0x3b9aaa7f r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9aaa7f r09: 0x00000000 r10: 0x3b9aaa7f r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b790 r22: 0xa0b4b784 r23: 0xa0b4b78c
    r24: 0x00000361 r25: 0x589c31d8 r26: 0xa0b4b4d0 r27: 0x00000040
    r28: 0x0000000f r29: 0x224d2a7f r30: 0xa0b4b764 r31: 0x96170fc4
    Thread 2: (0xb022084c, 0xb815ac0f)
    0x00000000: No symbol
    0x976f70c0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : TS_exception_listenerthread + 128
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x95fefd84 ctr: 0x95fef650
    r00: 0xffffffe1 r01: 0xf0203df0 r02: 0xa0b52f30 r03: 0x03001000
    r04: 0x00000002 r05: 0x00000000 r06: 0x00000054 r07: 0x00003e0b
    r08: 0x00000000 r09: 0x00000000 r10: 0x03800000 r11: 0xa0b45180
    r12: 0x95fef650 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0x00000000 r22: 0x03001000 r23: 0x00000000
    r24: 0x00000054 r25: 0x00003e0b r26: 0x00000000 r27: 0x00000000
    r28: 0x00000002 r29: 0x00000002 r30: 0x00000000 r31: 0x976f7048
    Thread 3: (0xb08f9d74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf071ddc0 r02: 0x00000000 r03: 0x00002503
    r04: 0x00000040 r05: 0x3b9ab20e r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9ab20e r09: 0x00000000 r10: 0x3b9ab20e r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b7d0 r22: 0xa0b4b7c4 r23: 0xa0b4b7cc
    r24: 0x0000035b r25: 0x8d316d93 r26: 0xa0b4b54c r27: 0x00000040
    r28: 0x0000000f r29: 0x224d320e r30: 0xa0b4b7a4 r31: 0x96170fc4
    Thread 4: (0xb009ad38, 0xb815ae44)
    0x9616f588: /usr/lib/libSystem.B.dylib : _dispatch_mgrinvoke + 228
    0x9616f0c0: /usr/lib/libSystem.B.dylib : _dispatch_queueinvoke + 320
    0x9616f244: /usr/lib/libSystem.B.dylib : _dispatch_workerthread2 + 364
    0x9616f380: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 76
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9616f550 ctr: 0x960332d4
    r00: 0x0000016b r01: 0xf0080bb0 r02: 0x00000003 r03: 0x00000004
    r04: 0x00000000 r05: 0x00000000 r06: 0xf0080d0c r07: 0x00000001
    r08: 0xf0080d28 r09: 0x00000000 r10: 0x00000003 r11: 0xa0b44524
    r12: 0x960332d4 r13: 0x10624dd3 r14: 0x961beb2c r15: 0xf0080c0c
    r16: 0xf0080c8c r17: 0xa0b5f4ac r18: 0xf0080d28 r19: 0xa0b594f8
    r20: 0xa0b5a4f8 r21: 0xf0080d0c r22: 0xa0b59478 r23: 0xa0b593f8
    r24: 0xa0b5f4ac r25: 0x00000000 r26: 0x00000000 r27: 0xa0b4b5c8
    r28: 0xa0b4b300 r29: 0xa0b4b5c8 r30: 0xf0080d28 r31: 0x9616f4ac
    Thread 5: (0xb011cd74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf0101dc0 r02: 0x00000000 r03: 0x00002403
    r04: 0x00000040 r05: 0x3b9aaf4f r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9aaf4f r09: 0x00000000 r10: 0x3b9aaf4f r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b790 r22: 0xa0b4b784 r23: 0xa0b4b78c
    r24: 0x0000035b r25: 0x3d4dfb37 r26: 0xa0b4b4d0 r27: 0x00000040
    r28: 0x0000000f r29: 0x224d2f4f r30: 0xa0b4b764 r31: 0x96170fc4
    Thread 6: (0xb03a684c, 0xb815ac0f)
    0x95d19480: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopModeIsEmpty + 160
    0x95d1d98c: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRun + 1980
    0x95d1ea04: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 656
    0x95d1ec64: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRun + 72
    0x96211ad8: /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv : TSystemNotificationTask::SystemNotificationTaskProc(void*) + 556
    0x976b7628: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x95fefd84 ctr: 0x95fef650
    r00: 0xffffffe1 r01: 0xf0386060 r02: 0xa0b073fc r03: 0xf038617c
    r04: 0x07000006 r05: 0x00000000 r06: 0x00000800 r07: 0x0000a503
    r08: 0x00000000 r09: 0x00000000 r10: 0x00000000 r11: 0xa0b45180
    r12: 0x95fef650 r13: 0x00000000 r14: 0x7fffffff r15: 0xffffffff
    r16: 0x00000351 r17: 0x123cb1e0 r18: 0xf038617c r19: 0xa0b4c698
    r20: 0x95dd0d60 r21: 0xa0b06a58 r22: 0xf038617c r23: 0x00000000
    r24: 0x00000800 r25: 0x0000a503 r26: 0x00000000 r27: 0x00000000
    r28: 0x07000006 r29: 0x07000006 r30: 0x0000a403 r31: 0x95d1d1d8
    Thread 7: (0xb051cd74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf0488dc0 r02: 0x00000000 r03: 0x00002103
    r04: 0x00000040 r05: 0x3b9aaee7 r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9aaee7 r09: 0x00000000 r10: 0x3b9aaee7 r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b6d0 r22: 0xa0b4b6c4 r23: 0xa0b4b6cc
    r24: 0x0000035e r25: 0xc1c149f5 r26: 0xa0b4b35c r27: 0x00000040
    r28: 0x0000000f r29: 0x224d2ee7 r30: 0xa0b4b6a4 r31: 0x96170fc4
    Thread 8: (0xb0773d74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf060bdc0 r02: 0x00000000 r03: 0x00002403
    r04: 0x00000040 r05: 0x3b9ab0cd r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9ab0cd r09: 0x00000000 r10: 0x3b9ab0cd r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b790 r22: 0xa0b4b784 r23: 0xa0b4b78c
    r24: 0x0000035b r25: 0x37770f32 r26: 0xa0b4b4d0 r27: 0x00000040
    r28: 0x0000000f r29: 0x224d30cd r30: 0xa0b4b764 r31: 0x96170fc4
    Thread 9: (0xb0324d78, 0xb815aa4c)
    0x9608c544: /usr/lib/libSystem.B.dylib : _pthread_condwait + 880
    0x20522448: ./TINthread.dylib : ThreadUtils::ConditionVariable::Wait(ThreadUtils::MutualExclusion&) + 24
    0x2051d708: ./TINthread.dylib : ThreadUtils::ThreadPool::Dispatcher() + 180
    0x2051d1a4: ./TINthread.dylib : ThreadUtils::ThreadPool::ThreadProc(void*) + 20
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9608c59c ctr: 0x95fef6b0
    r00: 0xffffffdb r01: 0xf0305d30 r02: 0x00000001 r03: 0x00005f03
    r04: 0x00006003 r05: 0x00000028 r06: 0x00000030 r07: 0x00005e03
    r08: 0x00000000 r09: 0x00000001 r10: 0x00000eee r11: 0xa0b45674
    r12: 0x95fef6b0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
    r24: 0x00000000 r25: 0x00000000 r26: 0xa0b4c6e4 r27: 0x00000000
    r28: 0x1eef10d0 r29: 0x00000000 r30: 0x1eef1130 r31: 0x9608c1e0
    Thread 10: (0xb0877bcc, 0xb815ae05)
    0x95d2a214: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFSocketManager + 856
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x95d2a2b8 ctr: 0x9605011c
    r00: 0x0000005d r01: 0xf0694a90 r02: 0xa0b09ec4 r03: 0x00000040
    r04: 0x1d809740 r05: 0x1d809730 r06: 0x00000000 r07: 0x00000000
    r08: 0x00000290 r09: 0xa0b08b88 r10: 0xa08617f8 r11: 0xa0af3444
    r12: 0x9605011c r13: 0xa0b08b88 r14: 0xa0b08b88 r15: 0x1d809730
    r16: 0x95dd1edc r17: 0xa0b09ec4 r18: 0x00000000 r19: 0x1d809740
    r20: 0xf068ce60 r21: 0x1d809560 r22: 0x1d809580 r23: 0xa0b071e8
    r24: 0x00000000 r25: 0x00000001 r26: 0x00000040 r27: 0x1d80b1e0
    r28: 0x00000000 r29: 0x1d699db0 r30: 0x00000000 r31: 0x95d29ec4
    Thread 11: (0xb02a2d74, 0xb815aa83)
    0x976b66dc: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _MPWaitOnSemaphore + 40
    0x01039f90: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACESemaphoreList::Wait(unsigned long) + 36
    0x0103a1dc: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : ACEMPThread::Task() + 76
    0x01039ba0: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE : _TaskGlue + 28
    0x976b7628: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x976b6720 ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf0284d20 r02: 0x0162a3f0 r03: 0x00004903
    r04: 0x7fffffff r05: 0x00000000 r06: 0x00000000 r07: 0x00000000
    r08: 0x00000000 r09: 0x4d555458 r10: 0x9688399c r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
    r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
    r28: 0x00000000 r29: 0x7fffffff r30: 0x00000000 r31: 0x976b66c0
    Thread 12: Crashed (0xb7fff9d0, 0xb80c5e94)
    0x0145e9b4: No symbol
    0x01386fbc: No symbol
    0x013878c8: No symbol
    0x0138797c: No symbol
    0x013525ac: No symbol
    0x01352af0: No symbol
    0x013654ec: No symbol
    0x01365bc0: No symbol
    0x01365c4c: No symbol
    0x01355410: No symbol
    0x011191ac: No symbol
    0x01116204: No symbol
    0x23044cd4: ./EPS Page Item.framework/Versions/A/EPS Page Item : _GetPlugIn + 261076
    0x23007664: ./EPS Page Item.framework/Versions/A/EPS Page Item : _GetPlugIn + 9572
    0x23005560: ./EPS Page Item.framework/Versions/A/EPS Page Item : _GetPlugIn + 1120
    0x2c196ad4: No symbol
    0x2c195c9c: No symbol
    0x2c199b74: No symbol
    0x2c196ad4: No symbol
    0x2c195c9c: No symbol
    0x1e12485c: ./Layer.framework/Versions/A/Layer : dyldstub_bindinghelper + 17164
    0x1e1252f8: ./Layer.framework/Versions/A/Layer : dyldstub_bindinghelper + 19880
    0x182320ac: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 87852
    0x18b064ec: ./Master Page.framework/Versions/A/Master Page : dyldstub_bindinghelper + 17932
    0x18b12290: ./Master Page.framework/Versions/A/Master Page : _GetPlugIn + 41664
    0x18b12b4c: ./Master Page.framework/Versions/A/Master Page : _GetPlugIn + 43900
    0x18232c10: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 90768
    0x18232e6c: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 91372
    0x1e1252b4: ./Layer.framework/Versions/A/Layer : dyldstub_bindinghelper + 19812
    0x23d01c34: ./Spread.framework/Versions/A/Spread : dyldstub_bindinghelper + 9764
    0x23d03574: ./Spread.framework/Versions/A/Spread : dyldstub_bindinghelper + 16228
    0x23d04290: ./Spread.framework/Versions/A/Spread : dyldstub_bindinghelper + 19584
    0x182320ac: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 87852
    0x230ea9a4: ./PDF.framework/Versions/A/PDF : dyldstub_bindinghelper + 139924
    0x230e98c0: ./PDF.framework/Versions/A/PDF : dyldstub_bindinghelper + 135600
    0x230e859c: ./PDF.framework/Versions/A/PDF : dyldstub_bindinghelper + 130700
    0x230ebeb0: ./PDF.framework/Versions/A/PDF : dyldstub_bindinghelper + 145312
    0x2c040ff4: No symbol
    0x18bc1bdc: ./Utilities.framework/Versions/A/Utilities : dyldstub_bindinghelper + 5132
    0x18bc18ac: ./Utilities.framework/Versions/A/Utilities : dyldstub_bindinghelper + 4316
    0x18214e84: ./AppFramework.framework/Versions/A/AppFramework : dyldstub_bindinghelper + 82628
    0x18215378: ./AppFramework.framework/Versions/A/AppFramework : dyldstub_bindinghelper + 83896
    0x2c042a3c: No symbol
    0x23104090: ./PDF.framework/Versions/A/PDF : _GetPlugIn + 96224
    0x2c02a300: No symbol
    0x18b913f0: ./Import Export UI.framework/Versions/A/Import Export UI : _GetPlugIn + 17456
    0x18b91bd8: ./Import Export UI.framework/Versions/A/Import Export UI : _GetPlugIn + 19480
    0x26f86b70: ./PDF UI.framework/Versions/A/PDF UI : _GetPlugIn + 215024
    0x1ec55590: ./Generic Style Editor.framework/Versions/A/Generic Style Editor : _GetPlugIn + 27504
    0x2b0adfe8: No symbol
    0x1e20c0f0: ./Actions.framework/Versions/A/Actions : _GetPlugIn + 6176
    0x1e211d90: ./Actions.framework/Versions/A/Actions : _GetPlugIn + 29888
    0x182015e8: ./AppFramework.framework/Versions/A/AppFramework : dyldstub_bindinghelper + 2600
    0x1822051c: ./AppFramework.framework/Versions/A/AppFramework : _GetPlugIn + 15260
    0x00002c58: No symbol
    0x000024fc: No symbol
    0x00002370: No symbol
    0xa8f7ffbf: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x0138490c ctr: 0x01363cc8
    r00: 0x01386fbc r01: 0xbfffa090 r02: 0x00000000 r03: 0x00000000
    r04: 0x256dd0fc r05: 0x00000000 r06: 0x00000001 r07: 0x0086967c
    r08: 0x00856c1c r09: 0x00000000 r10: 0x00000000 r11: 0x00000000
    r12: 0x01363cc8 r13: 0x25e29234 r14: 0x00000200 r15: 0x00020077
    r16: 0x00000000 r17: 0x22e8bf44 r18: 0x00000001 r19: 0x00055134
    r20: 0x230b4e40 r21: 0x0146787c r22: 0x0135299c r23: 0xbfffa670
    r24: 0x00000000 r25: 0x01386e44 r26: 0x256ef638 r27: 0x00000000
    r28: 0x00001f80 r29: 0x256dd084 r30: 0x00000012 r31: 0x00000001
    Thread 13: (0xb049ad74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf0407dc0 r02: 0x00000000 r03: 0x00002303
    r04: 0x00000040 r05: 0x3b9ab2b3 r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9ab2b3 r09: 0x00000000 r10: 0x3b9ab2b3 r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b750 r22: 0xa0b4b744 r23: 0xa0b4b74c
    r24: 0x0000035e r25: 0xaee4304f r26: 0xa0b4b454 r27: 0x00000040
    r28: 0x0000000f r29: 0x224d32b3 r30: 0xa0b4b724 r31: 0x96170fc4
    Thread 14: (0xb097bd74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf079edc0 r02: 0x00000000 r03: 0x00002503
    r04: 0x00000040 r05: 0x3b9ab122 r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9ab122 r09: 0x00000000 r10: 0x3b9ab122 r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b7d0 r22: 0xa0b4b7c4 r23: 0xa0b4b7cc
    r24: 0x0000035e r25: 0xad909188 r26: 0xa0b4b54c r27: 0x00000040
    r28: 0x0000000f r29: 0x224d3122 r30: 0xa0b4b7a4 r31: 0x96170fc4
    Thread 15: (0xb06f1d74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf058adc0 r02: 0x00000000 r03: 0x00002403
    r04: 0x00000040 r05: 0x3b9aaa34 r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9aaa34 r09: 0x00000000 r10: 0x3b9aaa34 r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b790 r22: 0xa0b4b784 r23: 0xa0b4b78c
    r24: 0x00000360 r25: 0xff3d2372 r26: 0xa0b4b4d0 r27: 0x00000040
    r28: 0x0000000f r29: 0x224d2a34 r30: 0xa0b4b764 r31: 0x96170fc4
    Thread 16: (0xb07f5d74, 0xb815aa83)
    0x961710b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
    0x9616f3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
    0x9608fda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
    0x00000000: No symbol
    PPC Thread State
    srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
    cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x961710cc ctr: 0x95fef6c0
    r00: 0xffffffda r01: 0xf068cdc0 r02: 0x00000000 r03: 0x00002403
    r04: 0x00000040 r05: 0x3b9a1a86 r06: 0x00000020 r07: 0x00000000
    r08: 0x3b9a1a86 r09: 0x00000000 r10: 0x3b9a1a86 r11: 0xa0b45670
    r12: 0x95fef6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
    r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
    r20: 0x00000000 r21: 0xa0b4b790 r22: 0xa0b4b784 r23: 0xa0b4b78c
    r24: 0x0000035c r25: 0x6e250395 r26: 0xa0b4b4d0 r27: 0x00000040
    r28: 0x0000000f r29: 0x224c9a86 r30: 0xa0b4b764 r31: 0x96170fc4
    Model: MacBook4,1, BootROM MB41.00C1.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.31f0
    Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
    Memory Module: global_name
    AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.91.19)
    Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: FUJITSU MHY2250BH, 232.89 GB
    Parallel ATA Device: HL-DT-ST DVDRW GSA-S10N
    USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd100000
    USB Device: Apple Optical USB Mouse, 0x05ac (Apple Inc.), 0x0304, 0xfd130000
    USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd120000
    USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8501, 0xfd400000
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x022a, 0x5d200000
    USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000
    USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8205, 0x1a100000

  • Clipping paths

    This question was posted in response to the following article: http://help.adobe.com/en_US/indesign/cs/using/WSa285fff53dea4f8617383751001ea8cb3f-6f23a.h tml

    Can I combine alpha transparency with a clipping path on the same image in InDesign?
    When you invoke the Object > Clipping Path command in InDesign, it makes a path according to the basis you choose from the Type menu in the Clipping Path dialog. If the image already contained transparency via Photoshop layering, or an "alpha channel," that transparency, is of course, also preserved. So yes, you can have native transparency plus an InDesign-generated clipping path on the same image.

  • Clipping Path Inverted

    I have created a clipping path correctly on Photoshop. When I place it into InDesign CS3, the path is inverted. I have to choose the clipping path option in InDesign, I have to check the invert path checkbox.
    Seems to be the same behavior using eps or jpeg.
    Behavior is correct in Quark
    Ideas ?
    Thanks
    Brian

    Inspect the icons in screenshot
    http://clippaths.ning.com/photo/photo/show?id=2177661%3APhoto%3A5
    The white part is "inside", the dark part is "outside".
    >I have created a clipping path
    b correctly
    on Photoshop
    No, you didn't. You created the path in a way that says "I do not want to see the face".
    I don't know how you did this, but you did.

  • CS2 clipping paths incompatible with CS3 indesign

    Hi there
    I need to use photoshop images with clipping paths that were created in photoshop CS2 in a indesign CS3 doc (working on a mac OS X 10.5.4). I import the image ok, the trouble is every time I try to activate the clipping path I get the spinning wheel of doom and the application stops responding.
    The image opens up fine in CS3 photoshop, there only seems to be a problem with the path itself which I've tried copying onto other images which I know work and it does the same thing with them.
    I used the image in indesign CS2 as a test and it worked properly, which is why I think the 2 packages are incompatible.... oddly enough, I'm using some really old images which were created before CS was a glint in the milkmans eye and they work perfectly.
    Does anybody know a way around this, or indeed if this is a bug or something?
    Thanks

    It is a bug but Adobe fixed it.
    If you want to use EPS files with clipping paths, that is fine, but be aware that there were problems that InDesign recovered from about 2 years ago. I wrestled through that time with many problems with clipping and have lots of documentation I never want to drag out again.
    The thing is to have everything updated. Files that were saved will not be fixed by copying paths, you need to re-save the files in an up-to-date version of Photoshop by doing 'save as' to overwrite.
    Sorry you're having this problem, it stinks but was remedied in updates. Try one file that you know doesn't work and do the save-as to see if that fixes it. Open and save in the latest CS3 version of course.
    Get rid of your CS2 InDesign. Use CS3 only.

  • Cutting out images in indesign, clipping path problems

    Hi,
    I have been putting images of my drawings from photoshop onto indesign for my portfolio,  after looking around the only way I can seem to find to cut them out is using clipping path/detect edges.
    The problem I have is because they are scanned sketches this method produces really inacurate and shoddy results and no matter how much I play around with the threshold and tollerance this means I still have to mess around with the pen and arrow tool for ages on each image.
    Is there a quicker solution to cutting them out like the magic wand or lasoo tool on indesign?
    It has taken days now in in design , I have all the images already cut out from their original pages on photoshop but the white box always comes around again when I drag or place the images in indesign.
    I have been shorcutting some pages and doing layout on photoshop and placing the image behind which works fine sometimes but is really inconviiant when I want to move the layout around text ot anything...... i have attatched some pictures to show you what I mean.
    Thanks for your help in advance
    Leo

    Well Thats 2 days of my life Ill never get back!
    Thankyou very much! cant belive I was that stupid

  • White outline on outside of clipping pathed images brought into InDesign

    Hi. I am on a PC using CS6.
    I created some clipping paths in Photoshop on a bunch of images and most of them have a white outline (even in Overprint Preview) shown in InDesign.
    I thought I was being careful not to be too close to the edge in order to not get that white outline. I created the paths using the pen tool and path palette.
    Please take a look at the screen shots below and I was wondering if anyone has this problem or if there is something I am totally missing.
    As you can see in this photo the white outlines are around part of the box and most of the separate pieces of chocolate. This is a screen shot from InDesign.
    This same image is below shown in Photoshop with a black rectangle placed behind it and I do not see the white outline. The outline shows in the PDF too when exported so I don't know what to do and I worried it will print this way. Never had this problem before..

    Willi, I used your suggestion and I didn't know what I was doing, but it seemed to have worked. I followed that tutorial from that link I posted earlier. I guess I didn't have to worry about a background image. I wonder why that happened, I've never had this problem before.
    I used a Photoshop image rather than a tif file. I tried using a Photoshop file earlier on in the game and had the white edges still, but did not use the Alpha channels.
    Thanks all for your help and awesome time-saving tips!!!

  • Why clipping path postponed from a photoshop in indesign at operation of addition of the new channel by means of work path doesn't work

    why clipping path postponed from a photoshop in indesign at operation of addition of the new channel by means of work path doesn't work 

    Please elaborate the issue and Supply pertinent information for quicker answers:
    The more information you supply about your situation, the better equipped other community members will be to answer. Consider including the following in your question:
    Adobe product and version number
    Operating system and version number
    The full text of any error message(s)
    What you were doing when the problem occurred
    Screenshots of the problem
    Computer hardware, such as CPU; GPU; amount of RAM; etc.

  • Clipping paths not recognized (in InDesign)

    Some of my coworkers brought me some files that don't allow the clipping path to be selected in InDesign. These images are saved as PSD format, have a good path drawn and saved. When placed in InDesign, the option to use the clipping path or not is not even available, and the image is not clipped by default. If I place a file showing the import options, I can turn on the path, and it places on the page properly. But invoking the Clipping options in InDesign still shows Photoshop Path as unselectable, but it is checked as it is turned on.
    Saving the path as simply a regular path, or as defined as a clipping path, in an EPS file gives me the correct options to use the path in InDesign. Simply resaving the PSD file to another file on my desktop does not fix it.
    Is there any way to see what is going on in the file? Though it manifests itself as an InDesigns option problem, the error is inside of the Photoshop file. There is no way to resave the same image document and have it work properly.
    The only way for me to "fix" the file is to make a new doc the same size, copy the image, paste into new document, copy path, paste into new doc, and save as a new name. Then the "started from scratch" file works properly.
    Anyone have any suggestions?

    @WasDYP: It's only a couple of files so it's not something I'd think anyone could recreate really easily.
    Here are the files that are having this problem:
    ftp://ftp.clippermag.com/PhotoshopFiles/DAV44462.psd
    ftp://ftp.clippermag.com/PhotoshopFiles/DAV44463.psd
    ftp://ftp.clippermag.com/PhotoshopFiles/DAV44464.psd

  • CS2 message:  "Clipping Path Limited Reached for TIFF Preview"

    I searched the forum and knowledge base and did not find answers than can help me with a message I received while saving my Illustrator CS2 .ai file to .eps file. The message said "Clipping Path Limited Reached For TIFF Preview". The file size is 500KB and is a chart of black and white symbols. The chart is 52 squares wide X 126 squares long, each square 1pt each.
    I had split the chart into 2 separate files and the message appeared again before finishing the save to .eps format. I am running Wins XP and just recently upgraded to 2gig of memory.
    Would anyone know what this message means? Any help is appreciated.
    J.Chin "newbie"

    I don't know exactly what that message means (or what one would have to do in Illustrator to get it to appear), but you might try saving without the TIFF preview. (Select "none" under the preview section when you are in the EPS options dialog box.)
    A potential problem with that workaround (assuming it helps at all) is that some applications rely on the low-res TIFF preview for on-screen representation. EPS artwork with no preview, in such cases, will usually be represented by a nondescript placeholder box. Output to a PostScript device, however, will be unaffected.

Maybe you are looking for

  • Poor performance by Matlab and Windows benchmark tests

    Hello I have a Lenovo Thinkpad W520 with Windows 7 64bit installed. Compared to other Notebooks with comparable hardware, my Lenovo is very slow. To prove my thought, I carried through a Matlab (64bit) benchmark test and the Windows 7 benchmark test.

  • Why am I unable to use my unlimited Europe calling...

    Dear Community, I am confused as I just bought the Unlimited Europe calling package in order to be able to call landlines and mobiles in UK and whenever I try to call, the call is dropped and skype message saying that I need to purchase more credit. 

  • SAPSCRIPT to Web(pdf) has different line spacing than in SAP?

    When we issue to output the order in SAP it looks fine. When we open it in the web, using PDF, the lines are spaced differently. We have never had an issue before, but now we added a lot of text to a final page of the sapscript. Any suggestion how to

  • Address Book Wish List!

    Unless it's already possible, anybody know if Apple ever plans on updating "Address Book" to enable the user to password protect an address book and to have multiple address books.... Having multiple sign-ins is not really a solution. Thx MBP 2ghz 1g

  • Signing requires password  and I don't have it!

    Hi. A few weeks ago, I experienced some trouble on how to enable signing in Reader, and got good help on: http://www.adobeforums.com/webx/.3c05f3f4/1 I created my signature, enabled signing rights in Reader and managed to put my signature on a docume