Lighten a portion of picture
I am trying to lighten a portion of a picture. I have copied the layer, applied the blend mode screen to lighten the whole picture, then added a layer mask so I can pain on parts I do not want to lighten. I used the brush tool with black selcted and painted on image. Nothing happens. Any idea of what I am doing wrong. I am using elements 10.
Well, you can always reset the tool: When the Brush tool is selected, click on the tiny arrow at the far right left of the Options Bar, and choose "Reset Tool".
If that doesn't solve it, post a screenshot of your Layers Palette.
Ken
Message was edited by: photodrawken to correct error.
Similar Messages
-
my pics did not transfer to my new iphone 5c icloud
Use your computer's backup to transfer your iTunes library from your old computer to your new computer per the instructions included with this link, or do the same with both computers networked in some fashion, which shouldn't be hard to do if both computers are connected to the same wireless network.
http://support.apple.com/kb/HT1751 -
Lifting out portion of picture to paste into Publisher
I am new to Photoshop Elements. I have spent the day trying to get a photo that has been altered in Elements to correctly paste into Publisher. I've taken a photo and erased the background. I just want the person. Next I want to paste just the person into a brochure. Everytime I paste, the background comes back. I have searched everywhere I can to find how to fix this. I did it at home using Indesign, but don't have Indesign at work. Can anyone help me?
Try saving it as a tif, gif, or png and importing it to publisher. These formats support transparency. Jpgs do not.
Or, is it not possible to move your graphic back and allow other elements to show on top of the graphic? This is a workaround that often will be adequate for the problem. (of course the background color of your image needs to match the background color of the document) -
Photoshop CS5 and Windows 8.1 Screen brightness problem????
I just recently updated to Windows 8.1, and now every time I open up Photoshop, my screen automatically lightens, lightening up my work/picture as well. It's annoying as hell. I want the picture to look normal, the way it is supposed to look. When I view the picture through my picture gallery, the picture looks normal and is in normal lighting. But every time, I open it up in Photoshop, my whole screen lightens, including the photo. Like I said, this is extremely annoying and now I can't edit my pictures properly because I can't see it's true colors. Instead, I see a brightened version of it. Is anyone else experiencing this. If so, please help me fix it. Will I have to uninstall Windows 8.1? I researched this and read in several different forums that this isn't an option. And that SUCKS! Please help, if you know how to fix this. Thanks!
I have been using Photoshop on windows for more then 20 years on windows. Windows 95, Windows 2000, Windows XP and Windows 7. I never installed Windows ME, Windows Vista or Windows 8. I have never seen any version of Photoshop change a displays brightness or even the image color when scaling or going from float to tab to single image with PS UI to full screen. However I hardly ever use Photoshop in full screen mode.
At different zoom views image may seem like the color change because of the scale of the image or the portion of the image that is on screen or the color of the border around the image. -
What programs/functions do I need to master in order to create stop motion animation?
Hi,
Im just starting a new job, and will be creating a handful of films for my new employer.
I want to create something interesting, and have been leaning towards stop motion animation.
What initially inspired me was this music video:
http://www.youtube.com/watch?v=zfcHq0hhFWg
To me, it looks like a bunch of stop motion ( ex; the paper balls and hand colored individual frames of the guy playing guitar), paired with some digital animation (walruses). Please correct me if I am wrong about this.
So - to focus my question:
1) What program does one use to play all the individual pictures taken to create the stop motion animation? In other words, once I have shot all the individual pictures of the objects I want to animate, and am ready to organize them and set a playback speed, what program would I use? Do most people just throw all the pictures into final cut and do it that way?? Or is there a better program?
and
2) How do you cut portions of pictures / drawings / frames out to allow for a deep layering effect? I figure most people take each frame and manipulate it individually using photoshop (cutting portions of an image out so something else can be seen through the void). But is there a better way??
For example, lets say I have two crecent shaped pieces of black paper, and I want them to move towards each other from the left and right sides of the screen, and eventually completely obscure whatever is going on in the background behind the paper images. First I would take a series of pictures, moving the pieces of paper in small increments, until they closed the gap and overlapped each other. From that point, I would lay down whatever video I wanted playing in the background into the timeline. Next, I would import the series of photos with the pieces of paper moving towards each other - then comes the problem. The portion of the pictures used for the animation that is NOT PAPER would be obscuring my background video. So at this point, is it easier to shoot the animation against a white background and just chroma key the white out? Or do most people cut the non paper part out using photoshop? or is there a better way?frisbee681 wrote:
Hi,
Im just starting a new job, and will be creating a handful of films for my new employer.
I want to create something interesting, and have been leaning towards stop motion animation.
Congratulations on the job. Not many of them out there.
frisbee681 wrote:
1) What program does one use to play all the individual pictures taken to create the stop motion animation? In other words, once I have shot all the individual pictures of the objects I want to animate, and am ready to organize them and set a playback speed, what program would I use? Do most people just throw all the pictures into final cut and do it that way?? Or is there a better program?
Easy to search the app store, as mentioned, or just google stop motion for macintosh. Mastering the application is easy. Learning how to animate is where you need to start.
frisbee681 wrote:
2) How do you cut portions of pictures / drawings / frames out to allow for a deep layering effect? I figure most people take each frame and manipulate it individually using photoshop (cutting portions of an image out so something else can be seen through the void). But is there a better way??
In the odlen days, we used multiplane stages. Each set of drawings was placed on a glass stage, one under the other. INcredibly fun, absurdly difficult to keep clean and properly lit. Now all of that stuff is done with alpha channels and compositing software like Motion or Afer Effects.
frisbee681 wrote:
For example, lets say I have two crecent shaped pieces of black paper, and I want them to move towards each other from the left and right sides of the screen, and eventually completely obscure whatever is going on in the background behind the paper images. First I would take a series of pictures, moving the pieces of paper in small increments, until they closed the gap and overlapped each other. From that point, I would lay down whatever video I wanted playing in the background into the timeline. Next, I would import the series of photos with the pieces of paper moving towards each other - then comes the problem. The portion of the pictures used for the animation that is NOT PAPER would be obscuring my background video. So at this point, is it easier to shoot the animation against a white background and just chroma key the white out? Or do most people cut the non paper part out using photoshop? or is there a better way?
Umm, yes. You're only guessing. And, honestly (Did you want honesty?), your heart may be in this but you don't have much a clue. Techniques and effects (and the experience to guide the decisions to do them in camera, on the shooting stage, or in software) are not where you start animation. You start by learning how cameras work, how shutter speed and f-stop relate to ISO speed, how to shoot on-2s (or if you should), how to do eases and stretches and squishes, how to develop characterization in inanimate objects so you can invoke emotive responses from the audience, how to shoot to hooks in the soundtrack, how to plan, how to storyboard, how to budget time, how to establish and maintain quality shooting conditions, how to do animatic or rough tests, how to learn from the tests, how to have fun, how to make money, how to get it done.
This is kind of like saying you've just inherited a hundred acres and are thinking about getting into farming. You plant some seeds and do some stuff and then pick it and sell it. How hard can it be?
bogiesan -
My AluMacbook recently stopped filling the screen of my TV and macbook screen when in mirror mode. I have it connected to my Sharp LC-32D50U (max resolution, 1360x768) via the DVI input. When set at 1360x768 i get black borders on the sides of the TV and i also get a single black borders on the top of my macbook. When i set the macbook to 1280x720 the lower portion of picture is cut off on both the TV and the Macbook. I had it working flawlessly yesterday with the TV displaying a beautiful 1360x768 image and the Macbook maintaining its 1280x800 while in mirror mode but now it's randomly not working. Nothing has changed. Any ideas? Already zapped PRAM and issue persists. There is no overscan option on Display settings for me to select and the TV is set to 1360x768. Already reset TV settings and issue still persists as well. Looking for help here. Thanks!
Of course your TV does scaling. That's how a 720P signal fills the entire physical resolution of your TV (which you state as being 1360x768). Thus the original signal into the TV is 1280x720 and the TV upscales that to something near to 1360x768 (the full physical resolution of your LCD display). In this case (by design) the image looks about as good as it can (for your TV) and the image aspect ratios fit exactly which means that there is no distortion in the final image.
If you input a non-standard resolution into your TV it will try to scale the image as best as it can but it is possible that some combinations will result in black bars or overscan (parts of the image will be missing) or distortion in the final image (stretched vertically or horizontally). Your TV could offer some combination of settings that will get you closer to full screen without too much distortion but it's probably not going to handle every input it receives in the best possible way.
Remember also that LCD, DLP, and plasma TVs run at a fixed physical resolution. The only way they can support other "resolutions" is through scaling or by accepting overscan (you lose part of the image) or by placing black bars around the image (the latter to support input resolutions lower than your TV's physical resolution). Typically when inputing a non-standard resolution you will get some type of scaling which may also result in a distortion of the image (if the aspect ratios aren't the same).
The inputs that your TV will probably handle the best ("standard" resolutions) are standard definition NTSC and PAL, 480p, 720p, and 1080i. You can consider NTSC to be equivalent to 640x480. Your TV may also handle some of the standard PC video resolutions (such as VGA, SVGA, and XGA -- 640x480, 800x600, 1024x768 respectively). Anything other than these (or less) is probably supported only at the discretion of the particular TV manufacturer (or by pure "dumb luck").
Of course Apple is also figuring into this as in the "Mirror Displays" mode they apparently adjust the output resolution depending upon the settings for the MacBook's internal LCD (and vice versa). They may do this to try to keep the aspect ratios into reasonably close agreement (there may also be limitations in what Apple's video driver can support and also in what the graphics card can support).
I also would not completely trust what is shown in the MacBook's Displays control panel (for resolution) when in the mirrored display mode. What is shown there may only be approximate, the video driver probably does what it wants in order to achieve what it thinks is best in the mirrored display mode.
I guess what I'm saying after all of this verbiage is that your mileage may vary. However, I still think that setting the MacBook's external (DVI to the TV) resolution to 1280x720 and leaving the MacBook's LCD set to 1280x800 is your best option. With this setting you'll have small black bars on the top and bottom of your MacBook's LCD but the image aspect ratios will match (no distortion in the images) and your TV should run in full screen at near to its best image quality. -
I can't figure out which add-on is crashing
something is crashing in firefox, i don't think it's firefox itself. websites with text only continue working, icanhascheezeburger sites keep working, just the display portion - the picture itself, not the surrounding text adds, whatever, goes blank with a grey exclamation mark in it. if i force-close and restore it fixes it.
but i have no idea what is crashing, i get no message, so i don't know how to fix this.Start Firefox in [[Safe Mode]] to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
* Don't make any changes on the Safe mode start window.
See
* [[Troubleshooting extensions and themes]]
* [[Troubleshooting plugins]] -
A workflow (and the limits of the 'module' concept?)
Often, choices regarding the best shots (when shooting in difficult conditions, e.g. contre-jour) are determined by which picture better supports adjustments. You might want to check if you get better results by lightening the shadows on picture A or darkening highlights on picture B. So the first feature I thought would be cool, is to make adjustments in Develop while seeing two pictures side by side. You can do this using 'Compare' in Library and the quick develop panel, but after pressing those buttons a number of time, you lose track of the intensity of the effect applied (a basic soution would be to enable sliders in quick develop). I also understand that the picture displayed in develop is not the same as the one in Library? It seems to me that noise patterns tend to differ when you switch modules.
Processing also affects ratings, positions in stacks, etc.. With a substantial batch of similar shots, which differ by the processing you've applied, it's useful to do basic management while in develop. Unfortunately the filmstrip is bit underpowered at the moment. It responds differently than the gallery. I can't manage to alter the filmstrip view modes the same way I do it in the gallery, etc. I can have a big filmstrip with big thumbnails, but I can't display more rows. It'easy to get lost in your pictures in develop if they're superficially similar (when not at 100%), and if you switch to the gallery, you then might lose the picture you were developing. A sort of mini-gallery feature could be useful. You could for example toggle a mini 'Survey' view while working on your photos
This could be extended to all modules. Mini-gallery could be useful in Print and Slideshow too(basically, we already have mini-develop in Library). I think Lightroom saves time by streamlining the workflow a lot (it automatically gives sets of related tools), but in situations where no module offers all the tools, you find yourself constantly changing, and that can be confusing. Maybe the SDK will offer completely customizable Modules to the daring user?2-up (at least) compare mode in Develop, multi-row film strip, and film strip cells that are the same as grid-mode cells but with separate options have been on my request list for a while.
-
I saw this question on an ePub etc forum I lurk on, on Linkedin:
"Let me start this off with the preface: Epub is not the answer. Been there done that.
I have a client who wrote a book and put that book on a Powerpoint. I converted that to a compatibility mode word 2000 doc and now have to get rid of the text boxes, among other tweaks, before I can publish.
. Well the thing is one giant text box and in order to get rid of them, I end up deleting his pictures and graphs. I thought, based on experience with original Word docs, "No problem, I have all the graphs and art here so I'll just get rid of the text boxes and if I loose the pictures, I can just insert them". Grr. It's not working. I'm only getting portions of pictures if any and they are coming in with their own text boxes.
I know there has to be an easy way to do this and am trying to not have to retype the entire book for him - which I'm on the brink of doing. I need to do this to get this book and his others, which are also only PPT at this point, publishd. Any suggestions would be appreciated. I'll just throw in: Searching for objects so that all my text boxes are visible does not work at all. Hey, would I be better off using my old Word 2000? There's just gotta be a way to do this. Barring printing the entire book and rewriting it for him which I'm thinking about doing."
How do you think I should answer?
DerekAssuming I understand the scenario correctly, here is what I'd advise:
Text: Word is not good at systemically recognizing the contents of text boxes, so extracting the text content from that file will take a few steps. Convert the Word document to PDF by whatever means are available; but of course the method must be one that doesn't simply rasterize everything. Open the PDF and Save As... Text (plain). Now you've got a text file of the book...no need to retype anything.
Images: I get the impression an older version of MS Office is in play, so image extraction is a matter of the old Save As HTML trick. In Powerpoint, Save As...Web Page (.htm, .html). In addition to the HTML pages, a folder of images will be written to the Save As location. The folder will contain 2 copies of each image from the file; one at the size/resolution that was displayed by MS Office, and the other will be at the size/resolution originally imported. Take whichever is the larger file to recover an image. -
Keyword add in any photo's Info crashes iPhoto to desktop
Hello & thanks in advance:
Attempting any keyword add in any photo's Info frame crashes iPhoto to desktop. I can reopen iphoto no problem, but any further attempt to add even an already existing keyword to a photo's information causes another crash to desktop.
Have done the following so far:
- Performed each task in Photo Library First Aid in turn, 4 times.
- Deleted dozens of under-utilized keywords to lighten that portion of the database.
- OSX and all apps kept up to date thru App Store.
- Time Machine backups working & available.
Question: Is there a method to restore only iPhoto keywords from backup, as a "JIC that works" next step?
I have EtreCheck and can post output (but will wait until/if requested).
Thanks again.Thanks LarryHN:
iPhoto Crash Dump Aug 27 2014:
Any attempt to add KEYWORDS, new or existing, to a photo that either already has keywords or not, results in the following crash & dump.
*Pls Note: This continues to occur after deleting the iPhoto preference file, com.apple.iPhoto.plist, in User/Home/Library/ Preferences and folder User/Library/Containers/com.apple.iPhoto, rebooting and reopening iPhoto.
=========================================================
Process: iPhoto [1287]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.5.1 (902.17)
Build Info: iPhotoProject-902017000000000~3
App Item ID: 408981381
App External ID: 233642646
Code Type: X86-64 (Native)
Parent Process: launchd [170]
Responsible: iPhoto [1287]
User ID: 502
Date/Time: 2014-08-27 12:18:23.623 -0500
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 04F0EB7D-86DB-A862-E504-26A285F536EA
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayI objectAtIndex:]: index 4 beyond bounds [0 .. 3]'
abort() called
terminating with uncaught exception of type NSException
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff8a72b25c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff8e002e75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8a616d9f -[__NSArrayI objectAtIndex:] + 175
3 AppKit 0x00007fff8fcf1d38 -[NSTableView preparedCellAtColumn:row:] + 399
4 AppKit 0x00007fff8fcf1a5e -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 44
5 AppKit 0x00007fff8fcf1793 -[NSTableView drawRow:clipRect:] + 1629
6 AppKit 0x00007fff8fcf0fed -[NSTableView drawRowIndexes:clipRect:] + 776
7 AppKit 0x00007fff8fbba331 -[NSTableView drawRect:] + 1484
8 AppKit 0x00007fff8fb9304f -[NSView _drawRect:clip:] + 3748
9 AppKit 0x00007fff8fb918c4 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1799
10 AppKit 0x00007fff8fb91ca0 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787
11 AppKit 0x00007fff8fb91ca0 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787
12 AppKit 0x00007fff8fb91ca0 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787
13 AppKit 0x00007fff8fb8f706 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 841
14 AppKit 0x00007fff8fcbec13 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 303
15 AppKit 0x00007fff8fb8be9f -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2828
16 AppKit 0x00007fff8fb6b2da -[NSView displayIfNeeded] + 1680
17 AppKit 0x00007fff8fcb53eb -[NSNextStepFrame displayIfNeeded] + 156
18 AppKit 0x00007fff8fd30d40 -[NSWindow display] + 105
19 AppKit 0x00007fff8fb5e321 __67-[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:]_block_invoke + 237
20 AppKit 0x00007fff8fb5e1e8 NSPerformWithScreenUpdatesDisabled + 65
21 AppKit 0x00007fff8fb5e197 -[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:] + 197
22 AppKit 0x00007fff8fb56491 -[NSWindow _setFrame:updateBorderViewSize:] + 914
23 AppKit 0x00007fff8fb55a0e -[NSWindow _oldPlaceWindow:] + 652
24 AppKit 0x00007fff8fb54e3c -[NSWindow _setFrameCommon:display:stashSize:] + 1633
25 AppKit 0x00007fff901373f7 -[NSTextViewCompletionController displayCompletions:indexOfSelectedItem:forPartialWordRange:originalString:atPoi nt:forTextView:] + 2761
26 AppKit 0x00007fff9013221d -[NSTextView(NSKeyBindingCommands) complete:] + 750
27 AppKit 0x00007fff901450cd -[NSTextView(NSPrivate) _performUndoCoalescingAction:] + 84
28 AppKit 0x00007fff9015e995 __34-[NSTokenFieldCell textDidChange:]_block_invoke291 + 220
29 libdispatch.dylib 0x00007fff8dfaa1bb _dispatch_call_block_and_release + 12
30 libdispatch.dylib 0x00007fff8dfa728d _dispatch_client_callout + 8
31 libdispatch.dylib 0x00007fff8dfaeef0 _dispatch_main_queue_callback_4CF + 333
32 CoreFoundation 0x00007fff8a6924f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
33 CoreFoundation 0x00007fff8a64d714 __CFRunLoopRun + 1636
34 CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
35 HIToolbox 0x00007fff8e840a0d RunCurrentEventLoopInMode + 226
36 HIToolbox 0x00007fff8e840685 ReceiveNextEventCommon + 173
37 HIToolbox 0x00007fff8e8405bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
38 AppKit 0x00007fff8fa3424e _DPSNextEvent + 1434
39 AppKit 0x00007fff8fa3389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
40 AppKit 0x00007fff8fa2799c -[NSApplication run] + 553
41 AppKit 0x00007fff8fa12783 NSApplicationMain + 940
42 iPhoto 0x000000010e7ed2ff iPhoto + 66303
43 libdyld.dylib 0x00007fff8b2d35fd start + 1
44 ??? 0x0000000000000001 0x0 + 1
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8dfd6866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8b19d35c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff8bef0b1a abort + 125
3 libc++abi.dylib 0x00007fff93396f31 abort_message + 257
4 libc++abi.dylib 0x00007fff933bc952 default_terminate_handler() + 264
5 libobjc.A.dylib 0x00007fff8e00330d _objc_terminate() + 103
6 libc++abi.dylib 0x00007fff933ba1d1 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fff933ba246 std::terminate() + 54
8 libobjc.A.dylib 0x00007fff8e0030b0 objc_terminate + 9
9 libdispatch.dylib 0x00007fff8dfa72a1 _dispatch_client_callout + 28
10 libdispatch.dylib 0x00007fff8dfaeef0 _dispatch_main_queue_callback_4CF + 333
11 com.apple.CoreFoundation 0x00007fff8a6924f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
12 com.apple.CoreFoundation 0x00007fff8a64d714 __CFRunLoopRun + 1636
13 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
14 com.apple.HIToolbox 0x00007fff8e840a0d RunCurrentEventLoopInMode + 226
15 com.apple.HIToolbox 0x00007fff8e840685 ReceiveNextEventCommon + 173
16 com.apple.HIToolbox 0x00007fff8e8405bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
17 com.apple.AppKit 0x00007fff8fa3424e _DPSNextEvent + 1434
18 com.apple.AppKit 0x00007fff8fa3389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
19 com.apple.AppKit 0x00007fff8fa2799c -[NSApplication run] + 553
20 com.apple.AppKit 0x00007fff8fa12783 NSApplicationMain + 940
21 com.apple.iPhoto 0x000000010e7ed2ff 0x10e7dd000 + 66303
22 libdyld.dylib 0x00007fff8b2d35fd start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8dfd7662 kevent64 + 10
1 libdispatch.dylib 0x00007fff8dfa9421 _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff8dfa9136 _dispatch_mgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.AppKit 0x00007fff8fbd405e _NSEventThread + 144
6 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.proxtcore 0x0000000110369d17 -[XTMsgQueue waitForMessage] + 46
5 com.apple.proxtcore 0x000000011036986c -[XTThread run:] + 322
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec77 _pthread_cond_wait + 787
2 com.apple.Foundation 0x00007fff8c54e930 -[NSCondition waitUntilDate:] + 344
3 com.apple.Foundation 0x00007fff8c5457d8 -[NSConditionLock lockWhenCondition:beforeDate:] + 232
4 com.apple.RedRock 0x0000000110bda3f1 -[RKAsyncImageRenderer _backgroundRenderThread:] + 346
5 com.apple.proxtcore 0x0000000110369ede -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 149
6 com.apple.proxtcore 0x000000011036723c -[XTDistributor distributeMessage:] + 664
7 com.apple.proxtcore 0x0000000110366a2f -[XTThread handleMessage:] + 337
8 com.apple.proxtcore 0x000000011036987c -[XTThread run:] + 338
9 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
10 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
11 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
12 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 11:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.Foundation 0x00007fff8c57d967 +[NSURLConnection(Loader) _resourceLoadLoop:] + 348
6 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 12:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff8dfd69aa __select + 10
1 com.apple.CoreFoundation 0x00007fff8a699a03 __CFSocketManager + 867
2 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 13:: Dispatch queue: com.apple.root.default-priority
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.Foundation 0x00007fff8c57fadc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 253
6 com.apple.AppKit 0x00007fff8fce4036 -[NSAnimation(NSInternal) _runBlocking] + 366
7 com.apple.AppKit 0x00007fff8fce3ea6 -[NSAnimation(NSInternal) _animationThread] + 73
8 libdispatch.dylib 0x00007fff8dfaa1bb _dispatch_call_block_and_release + 12
9 libdispatch.dylib 0x00007fff8dfa728d _dispatch_client_callout + 8
10 libdispatch.dylib 0x00007fff8dfa9082 _dispatch_root_queue_drain + 326
11 libdispatch.dylib 0x00007fff8dfaa177 _dispatch_worker_thread2 + 40
12 libsystem_pthread.dylib 0x00007fff8b19def8 _pthread_wqthread + 314
13 libsystem_pthread.dylib 0x00007fff8b1a0fb9 start_wqthread + 13
Thread 14:
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.Foundation 0x00007fff8c57fadc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 253
6 com.apple.proxtcore 0x0000000110386ff5 -[XTRunLoopThread run:] + 343
7 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
8 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 15:: QTKit: listenOnDelegatePort
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.CoreFoundation 0x00007fff8a702811 CFRunLoopRun + 97
6 com.apple.QTKit 0x00007fff8b05be6c listenOnDelegatePort + 385
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 16:: QTKit: listenOnNotificationPort
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.CoreFoundation 0x00007fff8a702811 CFRunLoopRun + 97
6 com.apple.QTKit 0x00007fff8b05c334 listenOnNotificationPort + 353
7 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 17:: CVDisplayLink
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.framework.IOKit 0x00007fff92c6a6fe io_connect_method + 377
3 com.apple.framework.IOKit 0x00007fff92c111b5 IOConnectCallMethod + 266
4 com.apple.framework.IOKit 0x00007fff92c1148d IOConnectCallScalarMethod + 46
5 com.apple.IOAccelerator 0x00007fff91a64644 IOAccelContextFinishFenceEvent + 42
6 libGPUSupportMercury.dylib 0x00007fff95f131e9 gpuiFinishFence + 117
7 libGPUSupportMercury.dylib 0x00007fff95f168f0 gldFinishObject + 48
8 GLEngine 0x00007fff92276247 gleFinishFence + 94
9 com.apple.QuartzCore 0x00007fff9246a6a1 view_state_finish(_CAViewState*) + 54
10 com.apple.QuartzCore 0x00007fff9246942d view_draw(_CAView*, double, CVTimeStamp const*, bool) + 1397
11 com.apple.QuartzCore 0x00007fff92468e7f view_display_link(double, CVTimeStamp const*, void*) + 150
12 com.apple.QuartzCore 0x00007fff92468d40 link_callback + 237
13 com.apple.CoreVideo 0x00007fff976235cc CVDisplayLink::performIO(CVTimeStamp*) + 206
14 com.apple.CoreVideo 0x00007fff97622a08 CVDisplayLink::runIOThread() + 608
15 com.apple.CoreVideo 0x00007fff9762278f startIOThread(void*) + 147
16 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
17 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
18 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 18:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec3b _pthread_cond_wait + 727
2 com.apple.Foundation 0x00007fff8c57aa99 -[NSCondition wait] + 237
3 com.apple.iPhoto 0x000000010e87207d 0x10e7dd000 + 610429
4 com.apple.iPhoto 0x000000010e871e4c 0x10e7dd000 + 609868
5 com.apple.CoreFoundation 0x00007fff8a6169ac __invoking___ + 140
6 com.apple.CoreFoundation 0x00007fff8a616814 -[NSInvocation invoke] + 308
7 com.apple.RedRock 0x0000000110bb63f2 -[RKInvoker _invokeTargetWithPool:] + 60
8 com.apple.proxtcore 0x0000000110369ec9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 128
9 com.apple.proxtcore 0x000000011036723c -[XTDistributor distributeMessage:] + 664
10 com.apple.proxtcore 0x0000000110366a2f -[XTThread handleMessage:] + 337
11 com.apple.proxtcore 0x000000011036987c -[XTThread run:] + 338
12 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
13 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
14 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
15 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 19:: CVDisplayLink
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec3b _pthread_cond_wait + 727
2 com.apple.CoreVideo 0x00007fff97622a38 CVDisplayLink::runIOThread() + 656
3 com.apple.CoreVideo 0x00007fff9762278f startIOThread(void*) + 147
4 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
5 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
6 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 20:: NetworkLoad
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8a64df15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8a64d539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8a64ce75 CFRunLoopRunSpecific + 309
5 com.apple.GeoServices 0x00007fff8bad2b2f _runNetworkThread + 442
6 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 21:: CVDisplayLink
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec3b _pthread_cond_wait + 727
2 com.apple.CoreVideo 0x00007fff97622a38 CVDisplayLink::runIOThread() + 656
3 com.apple.CoreVideo 0x00007fff9762278f startIOThread(void*) + 147
4 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
5 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
6 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 22:
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 libclh.dylib 0x00007fff8ade9de9 0x7fff8a7da000 + 6356457
3 libclh.dylib 0x00007fff8a89fd42 0x7fff8a7da000 + 810306
4 libclh.dylib 0x00007fff8adeac39 0x7fff8a7da000 + 6360121
5 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 23:
0 libsystem_kernel.dylib 0x00007fff8dfd2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dfd1d18 mach_msg + 64
2 libclh.dylib 0x00007fff8ade9de9 0x7fff8a7da000 + 6356457
3 libclh.dylib 0x00007fff8a89fd42 0x7fff8a7da000 + 810306
4 libclh.dylib 0x00007fff8adeac39 0x7fff8a7da000 + 6360121
5 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 24:
0 libsystem_kernel.dylib 0x00007fff8dfd6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8b19ec3b _pthread_cond_wait + 727
2 com.apple.iPhoto 0x000000010e97888d 0x10e7dd000 + 1685645
3 com.apple.CoreFoundation 0x00007fff8a6169ac __invoking___ + 140
4 com.apple.CoreFoundation 0x00007fff8a616814 -[NSInvocation invoke] + 308
5 com.apple.RedRock 0x0000000110bb63f2 -[RKInvoker _invokeTargetWithPool:] + 60
6 com.apple.proxtcore 0x0000000110369ec9 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 128
7 com.apple.proxtcore 0x000000011036723c -[XTDistributor distributeMessage:] + 664
8 com.apple.proxtcore 0x0000000110366a2f -[XTThread handleMessage:] + 337
9 com.apple.proxtcore 0x000000011036987c -[XTThread run:] + 338
10 com.apple.Foundation 0x00007fff8c57d76b __NSThread__main__ + 1318
11 libsystem_pthread.dylib 0x00007fff8b19c899 _pthread_body + 138
12 libsystem_pthread.dylib 0x00007fff8b19c72a _pthread_start + 137
13 libsystem_pthread.dylib 0x00007fff8b1a0fc9 thread_start + 13
Thread 25:
0 libsystem_kernel.dylib 0x00007fff8dfd6e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8b19df08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8b1a0fb9 start_wqthread + 13
Thread 26:
0 libsystem_kernel.dylib 0x00007fff8dfd6e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8b19df08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8b1a0fb9 start_wqthread + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff8dfd6e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8b19df08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8b1a0fb9 start_wqthread + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff8dfd6e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8b19df08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8b1a0fb9 start_wqthread + 13
Thread 29:
0 libsystem_kernel.dylib 0x00007fff8dfd6e6a __workq_kernreturn + 10 -
My printer asked me if I want my document to be printed on usual 70 lines/inch or maybe on 60 lines/inch because it's a kind of quite uncoated paper. When I preflight my document, Colors and Inks says always 70lines/inch, it doesn't matter if I assign a coated or uncoated profile. Is my printer request somehow related to my color profile or not? I'm scared now that in order to have it not too dark and inked, because I used an uncoated profile, I lightened the image quite a bit and now they also will print with less lines... the result will be too light and soft?
My question is: how can I relate and control the line printed from my printer with my document profiles?
Thanks,
anTYou dont. The printer, in setting the job to image to their imaging device, be it film or direct to plate, sets the lpi. You don't. You can choose the nearest color space, ie, Web Uncoated v2, or Sheetfed uncoated v2; but you shouldn't be lightening nor darkening your pictures. You should work from a calibrated monitor, and simply strive to make your pictures look just right.
The inking heaviness or lightness is the responsibility of the pressman to get right.
The lpi sounds awfully low. What are you having the job printed on? And what kind of press?
Mike Witherell in Maryland -
The font is very light on the menu bar in CS5. However Bridge in CS5 is bold and easy to read (as is the menu in PS CS3). How do I adjust the appearance of the menu bar?
I would also like the gray color on the menu bar and tool bar and in the background of a picture to be lighter. In Bridge CS5 I can lighten the background to pictures and I would like this in Photoshop CS5.
Many thanks for help and suggestions.
Bob LMarilynn,
Hopefully, you will not have to go far down this general list.
You may try the following (you may have tried/done some of them already) and see whether it helps (the following is a general list of things you may try when the issue is not in a specific file; 3) and 4) are specifically aimed at possibly corrupt preferences):
1) Close down Illy and open again;
2) Restart the computer (you may do that up to 3 times);
3) Close down Illy and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (easy but irreversible);
4) Move the folder with Illy closed (more tedious but also more thorough and reversible);
5) Look through and try out the relevant among the Other options (Item 7) is a list of usual suspects among other applications that may disturb and confuse Illy);
Even more seriously, you may:
6) Uninstall, run the Cleaner Tool, and reinstall.
http://www.adobe.com/support/contact/cscleanertool.html -
Hey Folks,
We are proud to announce the kick-off of our Community Redesign! The goal is to make the Community easier to use, more fun, and more awesome. We will be making changes in stages and always announcing them here.
The first phase is to introduce the new "Suggestions Box!" board! This is for all ideas or questions about the community. To be clear, this is not the place to make suggestions for Tagged.
Your input as a member of the Community will help guide our actions as we re-build, better, cleaner, more Awesome!
Thanks!
Damon
And the Tagged TeamI just want to say that your redesign so far is not easier to read or use!!!!!!!You have narrowed down my pets buy history and it is actually making me look elsewhere for pets. I don't like it....I myself want the old page back...also I don't like having my pictures BIG and up in everybodies face. If I wanted everybody to see them than everybody would be my friend............................................ you need to get rid of that option....it's rude and also compromises our personal information. Trying to get in pet runs right now is NOT happening for me...and i'm sure for alot of others...I just know that I cannot play in a pet run. you have added a drop down phase for each pet buy and I tried for over 20 minutes to grab one pet and watched the same 2 players bounch it back and forth the whole time, ( a glitch) can't say for sure, I just know its not one of your better changes. Let's face it 90% of the people on here can't afford an Alien gaming computer because we are dumping our cash into pets gold most likely... and really lets be honest.with the pet gold rising who needs to do pet runs, make some fake pets up and keep them on your page after you buy gold....works for me.. This site was originally set up to meet people, but you see that it's turned into a large pet gaming site.. it's cutthroat pets..... I suggest an Icon , something like the gift box for gifts or heart for love, make a picture of a person with a red line thru it, this notates that we are not interested in meeting anybody!!!! I've met alot of people but not one person I want to date...... we are all fakes on here,the pictures, the identity's everything. Give us the choice of letting people know we are not interested so we don't have to write rude things next to our name.. Oh and one more thing, if somebody wishes to not play pets, find a way to show it so we we don't have to open up the pets history page to find out, maybe lighten up the pets picture in the pet lineup or put a red minus at the corner of their picture something people can see before buying...I had a pet on my page that opted out of pets, but people kept taking it off my page......... the only way to tell was by buying the pet and looking at its pet page.. fix that!!!!! NoBuys and pet ratings need to be looked into, but you already know that. Thanks for listening to a really longtime pet player.......love the game..... PS I've seen good friends turn on each other.....so for those of us who only come on here to play pets and work on their cafe's, how about listening to our requests and concerns ...
-
hey,
i have avi. footage that i have recently downloaded and am trying to put onto dvd. the files are all about a half hour long and i am trying to figure out the best and quickest way possible to do this. compressor seems to take over 15 hours just to do one file. i have mpeg streamclip, episode converter (though i am not very handy with it), as well as toast titanium. any suggestions on how i should go about this? the quality doesnt have to be perfect, but i would like to keep at least a majority of it. when using toast i can only fit around 4 files a piece and would like to get a few more on there, but toast doesn't compress to dvd like it does when you burn ts files. any help is appreciated.You can alter your 4x3 footage by a process called ARCING (aspect ratio conversion). To arc 4x3 to 16x9 you simply stretch the 4x3 image vertically by 133%, this will mean losing a third of your picture so you may want to scan the image to get the portion of picture you require. This will the give you an anamorhic image. When you view it 4x3 it will look stretched vertically, when you adjust your screen to 16x9 widescreen it will stretch the picture to edge of screen and bring the picture back into the correct aspect ratio.
-
Wait on Asynchronous Call - why so long?
LV 2013, Win7
I have a window which comes and goes, during program operation.
This window has 72 subPanels, each containing a reentrant copy of the same VI for a "block". I insert the VI in the subpanel, and then run the VI with a CALL and FORGET call.
When the user closes the window, all the block VIs terminate, and the window closes. I don't care if the closing behind the scenes still goes on after the window disappears.
But when the user QUITs the program, with this window up, I need to make sure that all the block VIs have terminated before I shut down other things (close files, etc).
To that end, I changed the CALL and FORGET to a CALL and COLLECT operation, and installed a WAIT ON ASYNCHRONOUS CALL for each instance at the end of the big window code. This is after the blocks have been commanded to die (via an event).
I see from the debugging file (a portion is pictured) that it takes over 1000 mSec to wait for all the instances to die.
The thing is, if I change that "0" to "1000", then what I would expect is that the actual waiting time would drop to < 100 mSec.
My thinking is that during that timed wait, the blocks would be dying anyway, so it would take less time to actually wait on them.
But when I do that, nothing really changes. The listed time is still over 1000 mSec.
If I limit the number of blocks to 12, the time is 97 mSec, for 24 it is 185, for 36 it is 576, and so on - it's proportional to the number of blocks.
So, what is really happening? If it's just waiting on things to die, why doesn't the timed wait affect the numbers?
I originally (when I used CALL and FORGET) kept track of how many were opened and how many were closed and waited until that became zero, but this is a cleaner way of doing it, at least in theory.
Am I missing something?
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Solved!
Go to Solution.Have you checked how long the first loop of the For loop takes, versus all of the others?
So I tried that, several times - the pattern is the same as shown here. The first few lines are from the blocks themselves, it's the last thing they do.
Looks like there's ONE case where there's a bigger delay than expected, All told, this takes about 600 mSec.
Maybe the debugging process affects that (* waves to Mr. Heisenberg * )
The 300-400 mSec is back to where I first saw this delay. Apparently the unreleased refs clog up the system enough to drive it up to 1000 (or 2000 mSec as I saw in one case).
Still, I don't understand why a timed delay ahead of the WAITS doesn't affect the WAIT time.
But I guess that's not important. It must be actually doing more work than simply asking "is it dead yet?"
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Maybe you are looking for
-
How do I download attachments to an external drive
How do I download attachments to an external drive
-
Upgrad FMW from 11.1.1.4 to 11.1.2.0
Hi Team, I recently upgraded FMW from 11.1.1.4 to 11.1.2.0 since then my report server not working even though it is up and running. [oracle@smiggins repsisupg]$ opmnctl status Processes in Instance: asinst_1 -----------------------------------------
-
Hi everyone... I want to make a simple application that integrates a flesh interface with a Java back end. I am using Eclipse Europa (V3.3.1.1) to make the Java part, and Flex Builder 2 (2.0.1) to make the interface (separated IDEs, since Eclipse Eur
-
Editing iPhoto library in Photoshop CS
When I try to open iPhoto 8 in Photoshop CS, it is greyed out. How can I see my iPhoto pics in Photoshop? Thanks.
-
Installing Labview runtime engine 2011
Hi, Is it mandatory to uninstall any previous version of the Labview runtime engine before installing the 2011 verstion ? Thanks.