Lightroom 1.3.1 breaks printing
I've searched the knowledge base as well as here, to find that lots of people complain that Lightroom throws a horrible magenta cast on prints, but nobody seems to have an answer. For what it is worth, I got beautiful prints from Lightroom 1.1, and when I upgraded to 1.3.1, suddently everything printed from LR is magenta. PhotoShop CS3 still makes beautiful prints from the same files. I am only semi-interested in a work around, what I'd really, really, really like is for Adobe to unbreak whatever it is that broke with the upgrade to 1.3.1. It is entirely enough of a pain in the butt to select the printer/ink/paper profile, specify LR (or PS) manages the color, then turn the color management off in the driver. I am tired of multiple clicks every time I print something, I want a solution that allows me to specify what I want done ONCE and be done with it. Why do I have to reinvent the damn wheel every time I want to roll out another print? And why do _I_ have to "work around" whatever lame-*** roadblock the software throws up in the path of progress?
Grab up torches and pitchforks, and let's storm the castle and demand the engineers building these products quit making color management harder and start making it easier. And most especially, quit blaming it on "those other engineers over there!" Here's a light for your torch, let's march! Who's with me?
Re: Jeff Schewe's comments . . .
I did not specify OS because (a) I have seen references here to this particular problem with both Vista and Leopard -- note Gordon Cahill's response below -- and (b) I was looking to make a protest more than for a particular work-around solution.
Re: Claude Biron's comments . . .
Thank you for pointing to the "official" discovered work around. I hadn't seen that particular article, but I had seen references to it enough to have tried it. It should be noted that on a properly set up Mac where the daily user account is NOT an administrator account, this does not work, because you have to be logged in as an administrator in order for that triangle next to the "Current Profile" to not be grayed out.
This works but is a "work around," not a solution to the essential problem, which is that it is no form of improvement to make the end user jump through MORE hoops to get properly color managed work through the flow. At the very least this is a pain in the butt. And although I haven't tried it on other ink/paper profiles yet, it would seem to require changing the setting in Colorsync Utility every time you change substrates, a REAL pain in the butt if it calls for logging out and back in every time you switch papers. Which I do a lot.
I note that Ian Lyons, the author of the article to which you pointed, says "What I feel is happening is that there is a double profiling issue with print stream from Lightroom
to the the Epson driver (v6.12) and by selecting the identical profile in both places we are
ensuring that no conversion takes place in the driver, something that simply setting 'No Color Adjustment' usually achieves in Photoshop and other older applications that use a different print stream to Lightroom." Mr. Lyons calls it a work around, as well.
That, frankly, is counter-productive, and the creation of a problem where none existed before. PhotoShop does not have this particular problem. Lightroom 1.1 did not have this particular problem. Pages does not have this problem. Preview does not have this problem. InDesign does not have this problem. Safari does not have this problem, and I can name many other programs that do not have it, either. The problem was introduced, as far as I can tell, in Lightroom 1.3. So I'm sorry, Adobe, but I call "BUG" on your software in this instance.
Adobe, whatever you changed in the print module to go from 1.1 to 1.3, change it back already.
Similar Messages
-
Lightroom 4.4 Crashes when Printing
I recently upgraded from Lightroom 3 to Lightroom 4.4. I use a MacBook Pro, running OX v 10.8.3, with 8GB of RAM.
Since the upgrade Lightroom crashes whenever I try to print, to any of my printers. I could print without problems using Lightroom 3, and can still print from other applications.
Lightroom 4.4 can print to JPEG without crashing.
I have re-installed all my printers, but this has not made any change.
Text of log from one of the many crashes shown below.
Any advice or suggestions would be really appreciated, as not being able to print is a major problem.
Process: Adobe Photoshop Lightroom 4 [7018]
Path: /Applications/Adobe Photoshop Lightroom 4.app/Contents/MacOS/Adobe Photoshop Lightroom 4
Identifier: com.adobe.Lightroom4
Version: Adobe Photoshop Lightroom 4.4 [891433] (4.4)
Code Type: X86-64 (Native)
Parent Process: launchd [180]
User ID: 501
Date/Time: 2013-05-04 13:30:50.983 +0100
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report: 57906 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 225990 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: 3B1811FA-C1B9-14FB-43E7-D21D09029F64
Crashed Thread: 37
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8e4b6686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8e4b5c42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff920ec233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff920f1916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff920f10e2 CFRunLoopRunSpecific + 290
5 com.apple.HIToolbox 0x00007fff8bccdeb4 RunCurrentEventLoopInMode + 209
6 com.apple.HIToolbox 0x00007fff8bccdc52 ReceiveNextEventCommon + 356
7 com.apple.HIToolbox 0x00007fff8bccdae3 BlockUntilNextEventMatchingListInMode + 62
8 com.apple.AppKit 0x00007fff8f148563 _DPSNextEvent + 685
9 com.apple.AppKit 0x00007fff8f147e22 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
10 com.apple.AppKit 0x00007fff8f13f1d3 -[NSApplication run] + 517
11 com.apple.AppKit 0x00007fff8f0e3c06 NSApplicationMain + 869
12 com.adobe.Lightroom4 0x0000000100001653 main + 1107
13 com.adobe.Lightroom4 0x00000001000011f8 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8e4b8d16 kevent + 10
1 libdispatch.dylib 0x00007fff8d4b7dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff8d4b79ee _dispatch_mgr_thread + 54
Thread 2:: ace
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.apple.CoreServices.CarbonCore 0x00007fff90b7a210 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff90b7a3e7 TSWaitOnConditionTimedRelative + 132
4 com.apple.CoreServices.CarbonCore 0x00007fff90adcb14 MPWaitOnQueue + 252
5 com.adobe.ag.AgImageIO 0x0000000105e17066 0x105c1f000 + 2064486
6 com.adobe.ag.AgImageIO 0x0000000105e16cf3 0x105c1f000 + 2063603
7 com.apple.CoreServices.CarbonCore 0x00007fff90b517e0 PrivateMPEntryPoint + 58
8 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
9 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 3:: cr_scratch
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.AgImageIO 0x0000000105d1f3da 0x105c1f000 + 1049562
3 com.adobe.ag.AgImageIO 0x0000000105ed51d2 0x105c1f000 + 2843090
4 com.adobe.ag.AgImageIO 0x0000000105ced8d9 0x105c1f000 + 846041
5 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 4:: Worker Thread Dispatcher
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
7 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
8 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
9 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
10 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
11 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
12 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
13 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
14 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
15 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
16 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
17 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
18 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
19 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 5:: Queue Processor - AgPhotoAvailability
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 6:: AsyncDataServer
0 libsystem_kernel.dylib 0x00007fff8e4b7b26 __fcntl + 10
1 libsystem_kernel.dylib 0x00007fff8e4b70cb fcntl + 232
2 com.adobe.ag.storeprovider 0x000000010705c326 0x107000000 + 377638
3 com.adobe.ag.storeprovider 0x0000000107009293 0x107000000 + 37523
4 com.adobe.ag.storeprovider 0x000000010700923e 0x107000000 + 37438
5 com.adobe.ag.storeprovider 0x00000001070095d5 0x107000000 + 38357
6 com.adobe.ag.storeprovider 0x00000001070541ee 0x107000000 + 344558
7 com.adobe.ag.storeprovider 0x000000010705388a 0x107000000 + 342154
8 com.adobe.ag.storeprovider 0x000000010700b120 sqlite3_step + 2372
9 com.adobe.ag.storeprovider 0x000000010700d9ef sqlite3_exec + 584
10 com.adobe.ag.storeprovider 0x0000000107001c71 0x107000000 + 7281
11 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
12 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
13 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
14 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
15 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
16 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
17 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
18 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
19 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
20 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
21 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
22 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
23 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
24 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
25 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
26 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
27 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
28 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
29 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
30 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
31 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
32 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 7:: Preview Server
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fc76 AgConditionLock_wait + 186
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
7 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
8 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
9 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
10 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
11 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
12 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
13 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
14 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
15 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
16 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
17 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
18 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
19 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 8:: Queue Processor - PreviewFileStore
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 9:: Queue Processor - NegativeQueue
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 10:: Queue Processor - HistogramQueue
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 11:: Queue Processor - RenderQueue_Render
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 12:: Queue Processor - RenderQueue_ReadPreview
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 13:: Queue Processor - RenderQueue_Video
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
7 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
8 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
9 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
10 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
11 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
12 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
13 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
14 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
15 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
18 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
19 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
20 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
21 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
22 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
23 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
24 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
25 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
26 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
27 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
28 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
29 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 14:: AgFileWatching
0 libsystem_kernel.dylib 0x00007fff8e4b8d16 kevent + 10
1 com.adobe.ag.substrate 0x0000000100173d70 0x10016d000 + 28016
2 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
3 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
4 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
5 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
6 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
7 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
8 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
9 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
10 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
11 com.adobe.ag.kernel 0x000000010001efe5 lua_resume + 112
12 com.adobe.ag.kernel 0x0000000100018be7 0x100015000 + 15335
13 com.adobe.ag.kernel 0x00000001000189c1 0x100015000 + 14785
14 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
15 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
16 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
17 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
18 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
19 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
20 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
21 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
22 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
23 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
24 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
25 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
26 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
27 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
28 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 15:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
7 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
8 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
9 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
10 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
11 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
12 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
13 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
14 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
15 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
18 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
19 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
20 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
21 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
22 com.adobe.ag.substrate 0x000000010017ed96 0x10016d000 + 73110
23 com.apple.Foundation 0x00007fff9135ccd2 __NSThread__main__ + 1345
24 libsystem_c.dylib 0x00007fff8d4ea7a2 _pthread_start + 327
25 libsystem_c.dylib 0x00007fff8d4d71e1 thread_start + 13
Thread 16:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff8e4b80fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8d4eefe9 _pthread_cond_wait + 869
2 com.adobe.ag.kernel 0x000000010003fbe5 AgConditionLock_wait + 41
3 com.adobe.ag.kernel 0x000000010003b791 AgTransitQueue_dequeueToLuaState + 96
4 com.adobe.ag.kernel 0x000000010003c638 0x100015000 + 161336
5 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
6 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
7 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
8 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
9 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
10 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102
11 com.adobe.ag.kernel 0x00000001000193a3 0x100015000 + 17315
12 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
13 com.adobe.ag.kernel 0x000000010001ef35 luaD_call + 93
14 com.adobe.ag.kernel 0x0000000100016f66 lua_call + 42
15 com.adobe.ag.substrate 0x000000010018afec AgLua_callWithAutoReleasePool + 87
16 com.adobe.ag.kernel 0x000000010001ed6c luaD_precall + 1102
17 com.adobe.ag.kernel 0x000000010002dbb9 luaV_execute + 4800
18 com.adobe.ag.kernel 0x000000010001ef46 luaD_call + 110
19 com.adobe.ag.kernel 0x000000010001e64d luaD_rawrunprotected + 54
20 com.adobe.ag.kernel 0x000000010001f1a4 luaD_pcall + 75
21 com.adobe.ag.kernel 0x0000000100016fe9 lua_pcall + 102So, I had this problem tonight after experiencing no problems with Lightroom 4 previously. I noticed that in the print dialog box, where you can select to print "all" the pages or a page range, the page range radial was highlighted and the defined page range was "7" to "7". I was only printing one image so I changed the print range to "1" to "1". And it did the trick. Crazy, eh?
-
Office 2010 mail merge with section breaks printing problem
Afternoon all,
We have an issue and I was wondering if anyelse has come across this and has a solution
Our office staff do many mail merges and once the merge is complete they then can print the whole document with no problems or select one page and do print current page. The problem occurs when trying to print a range i.e. pages 5-7. Once you click print nothing happens, no errors and nothing comes out the printer.
What I have found is that the mail merge is putting in section breaks between each page to seperate them but if I change these to page breaks in the document then I can select pages 5-7 and it prints with no problems.
So the only solution I have found so far is to do a find/replace and find all ^b (section break) and replace with ^m (page break). This is obvioulsy takes more time and is a pain if we have to do this for every mail merge.
I can't find any setting in the mail merge to tell it to use page breaks instead of sections breaks
Has anyone else come across this probem, is it a office bug ???
Any help would be great
DarrenJohn,
Replying to your posts works just fine. You can choose to reply to either of the other posts & address both in your comments just as you did. I see quite a few threads where the OP (original poster) posts a reply to each & every one who has replied. I think it makes it very difficult to find the actual answers. -
Is Lightroom sending sRGB to the printer driver?
Hello,
I've been trying to print something on a color laser printer with Lightroom. Unfortunately, Lightroom doesn't seem to support the profile of the printer, maybe it's a CMYK profile, and so I had to use the option "Profile: managed by printer" in Lightrooms print module.
In order to set up the printer driver correctly and let him handle the color management, I'd like to know what Lightrooms sends to the printer driver when the option "managed by printer" is set (and when draft mode is off!)
Thanks in advanceJeff Schewe - 12:08am Jan 1, 08 PST (#2 of 8)
Version 1.0 sent sRGB
Uh, no...since the beta process, when not using draft mode, Lightroom ALWAYS sent ProProto RGB. Draft mode will send either sRGB or Adobe RGB depending on the settings for the previews.
Since the OP is printing to a laser printer as opposed to a photo printer, the best bet would be to print using draft mode anyway.
Jeff,
You may be right and I am sure you know more about this than I do, but in 1.0 I could print contact sheets to my laser printer with no problems with "managed by printer" selected and draft mode off. Since 1.1 I have not been able to get acceptable results regardless of whether I choose draft mode or not and regardless of the settings in the export module. I would love to solve this as it is the number 1 issue I have with Lightroom.
Gordon -
Is anyone successfully printing from Lightroom 4 on an iPF5000 printer?
My iPF5000 prints fine from Photoshop 6, but not LR4. The photos just get qeued up when I click "print" in LR. In photoshop I use the "export" command to access the printer driver and everything works as it should.
I can select the printer and the paper profiles while in LR but the image never gets sent to the printer, at least that's what I think happens as the "Online" light on the iPF5000 never starts blinking.
Thanks in advance for your suggestions.
JDI think you are right. They never get to the printer. Does it print text from other software?
I use both PS and LR but I don't see any reason for either to intercept and stop your photos from being printed.
Are you sure you have all the correct setting in LR? You might want to double check.
EOS 1Ds Mk III, EOS 1D Mk IV EF 50mm f1.2 L, EF 24-70mm f2.8 L,
EF 70-200mm f2.8 L IS II, Sigma 120-300mm f2.8 EX APO
Photoshop CS6, ACR 8.7, Lightroom 5.7 -
Lightroom 5.7, Epson 820 printer. dark images
I am using Lightroom 5.7 and Epson 820 printer. i have calibrated my monitors using spider3, no printer ICC and using multiple different ICCs in lightroom and all the same result. All my images are dark and washed out. Need help. If I export my images and print from MS photo viewer they look pretty good.
As to my printer drivers, after installing Snow Leopard, I was unable to print using LR2.5. The print would fail generating an error. I then installed the new drivers from the Epson web site: epson13113.dmg for my Epson R2400. This "worked" in that it did not generate an error, but would just transmit to printer and then quit.
Up to that point I had done a minimum of web reading, I just had seen that Matt K. from Kelby and others had been using SN and LR2 successfully. With my two failures, I googled extensively. I deleted all my printers, downloaded the new 10/22 Apple Epson drivers, re-ran the Epson drivers, etc, etc, etc, stopping and restarting along the way until I was able to obtain CS4 prints using SL with my Epson R2400.
At that point, I returned to my initial objective, which was to obtain (re-obtain, if you will as I previously had them) quality prints from LR. The early prints were harsh and less than acceptable, and when I got the "Sun in the dark" picture that I could quantify, I knew I had a definite issue and posted to this forum.
(I am assuming that my deletion of the profiles while seeking to update driver is how I generated my initial inconsistency that was part of my original post).
I now looks like I had a color space problem. I have deleted and re-generated the psd "Edit in Photoshop" image. Again, on the screen, the edit and the original appear identical and as the CS4 print is correct, I am left, it appears to me, with a LR2.5 printing issue unless I can find some configuration issue. The two pictures are definitely different with the flesh tone pink and some of the background colors "lighter" in the LR2 print.
(As a side, I don't think this would matter, the original pics were taken as raw nef from a D700 camera using a 105mm VR2 macro lens).
Thanks for your time. -
Lightroom 4 book does not print to pdf correctly
I have one photo in a two page spread in a book in the the Book Module. When I print to pdf the two page spread prints as two pages, not adjoining. I have tried putting extra pages in, taking off the color coding, checking and unchecking the background. Nothing works through eight tries. Very frustrating, as I wanted to publish this book to pdf today.
hbbirdI tried all of the print/press options and they all do the same thing.
I have always used the pdf maker button from the MS Word ribbon.
I just tried using the print dialog and selected Adobe PDF with the 'high quality print' option that I need to use and this time it worked! But it is not really fixed as I make a lot of PDFs every day and need the one-click functionality.
In the PDFs that work and PDFs where the character fails I tried editing the text and it says that the font is substituted. In MS Word i am using Arial, Acrobat is using some "ArialMT" font that I never heard of.
The embeded fonts are also listed as ArialMT. -
Lightroom 3 Tethered shooting and printing
I have a very specific question. I need to shoot guests at a part in a "photo booth" style. I want to shoot tethered directly into LR3 and then have my assistant print the images as I continue to shoot the guests. However, I'm having a problem setting up the workflow. When we are in the print dialog setting up an image to print if I shoot another picture, LR3 automatically updates the working image to the newest capture. Basically this means that we can't simultaneously shoot and print at the same time. Does anyone have any suggestions about how to get around this? Thank you, I really appreciate it.
JacobI'm at work now, I'll try it when I get home. I spent I don't know how much time looking through the menus for an option just like this. It sounds like it will do exactly what I need it to. Thank you,
Jacob -
I can't get my Canon i99oo and Lightroom 3.4.6 to print from my Macbook Pro
I get the error that I need to install new software update but all sotware and printer drivers are up to date.
Hi There
Do you have an SD card?
If so plug it into your SD card slot and you will be able to view all of your images/videos from there!!
Hope this helps.
joe1828 -
Print Problem: inconsistent density between sizes and Lightroom/Photoshop
In the past I printed using only Photoshop. I recently made a batch of prints from Lightroom, using the same paper, printer profile, rendering intent, and noticed that the output does not match the output from Photoshop. The Lightroom prints have noticeably more density. I then noticed that large Lightroom prints, for example 16 x 24, have noticeably more density than smaller size Lightroom 6 inch x 9 inch prints. I find no difference in print density when printing from Photoshop regardless of the print size. I can not determine why I am experiencing these variations in print output.
All prints are made using an Epson 7900 on Museo Portfolio Rag, same ICC profiles, same exact setup in the Epson printer driver (off no color adjustment), PS: PS manage color and same icc profile specified in both Lightroom and Photoshop. The computer is a Windows 7 machine.
Has any one else experienced these problems? My first thought is that this is some sort of bug in Lightroom's color management. But if that was true, then it seems like a lot of people would be having this problem. I have been using a color managed workflow for a number of years and have gotten very satisfactory results. My prints are a close match to the soft proof in Photoshop. Since printing from Lightroom the prints do not match prints made from Photoshop, plus the prints made by Lightroom vary in density depending on the size. Bizarre.
Please helpSolved. Somehow the custom media setting for the Museo Portfolio Rag paper was lost when I set up the LR template. The custom media setting reduced the color density by -20 in the Epson Printer driver. With out this setting the color density was at the default zero and the density was greater.
This brings up another question that I will have to explore. I arrived at the -20 color density setting when testing various Epson Driver media settings for the 7900 prior to profiling this paper after Epson replaced the nozzle heads on my 7900 printer. I found at the default zero color density I encountered banding. Prior to the replacement of the nozzle heads the default zero color density worked fine and there was no banding. Interestingly, on the 16 x 32 print that mistakenly used the zero color density setting there was no banding. Now I want to go back and redo my media tests. Is it possible that the new print heads needed a breaking in period and that is why I encountered banding on both the Museo Portfolio Rag and the Epson mat paper? -
How do I Print Accurate Color from Lightroom?
I just got my Epson 3880 2 weeks ago. The problem I am having is getting accurate color when printing from Lightroom. I am running a p.c. with Windows 8.1. To eliminate my monitor as the problem, I created a series of color patches in Photoshop, printed them and read them in using the X-Rite Color Munki Photo. Here is a list of thing I have done:
1) I chose Lightroom manages color, chose the appropriate icc profile in Lightroom, chose the appropriate paper in the printer dialogue box, and choose no color management in the printer dialogue box. The results are as follows:
Blue (0,0,255) prints like Black
Photoshop RGB
Color Munki Reading RGB
1
(198,198,198)
(192,197,197)
2
(255,128,255)
(214,130,207)
3
(128,255,255)
(0,196,185)
4
(128,128,128)
(132,132,132)
5
(0,0,0)
(17,16,14)
6
(0,255,255)
(0,186,177)
7
(255,0,255)
(183,78,183)
8
(255,255,198)
(239,229,186)
9
(255,255,255)
(236,241,241)
10
(255,0,0)
(205,0,64)
11
(0,255,0)
(42,179,64)
12
(0,0,255)
(0,31,71)
13
(128,128,255)
(89,146,218)
14
(128,255,128)
(73,191,121)
15
(255,128,128)
(230,102,128)
16
(255,255,0)
(248,210,0)
Printing from Lightroom – Lightroom Manages Color
2) I chose Printer manages color, chose the appropriate paper in the printer dialogue box, and choose Epson - srgb in the printer dialogue box. The results are as follows:
Grays (198,198,198) and(128,128,128) prints too dark (1 - 2 stops?)
Photoshop RGB
Color Munki Reading RGB
1
(198,198,198)
(141,147,148)
2
(255,128,255)
(228,104,194)
3
(128,255,255)
(0,195,186)
4
(128,128,128)
(60,64,63)
5
(0,0,0)
(20,20,17)
6
(0,255,255)
(0,191,186)
7
(255,0,255)
(225,92,188)
8
(255,255,198)
(245,232,140)
9
(255,255,255)
(240,243,242)
10
(255,0,0)
(214,28,50)
11
(0,255,0)
(0,173,62)
12
(0,0,255)
(0,96,193)
13
(128,128,255)
(0,114,204)
14
(128,255,128)
(0,180,80)
15
(255,128,128)
(226,60,73)
16
(255,255,0)
(250,215,0)
Printing from Lightroom – Printer Manages Color
3) I chose Printer manages color, chose the appropriate paper in the printer dialogue box, and choose Adobe in the printer dialogue box. The results are essentially the same as 2.
4) I opened the image in "Windows Photo Viewer", printed the image, chose the appropriate paper in the printer dialogue box, and choose Adobe in the printer dialogue box. The results are as follows:
All Colors look close (for a color munki photo I guess)
Photoshop RGB
Color Munki Reading RGB
1
(198,198,198)
(188,192,191)
2
(255,128,255)
(238,143,209)
3
(128,255,255)
(77,205,200)
4
(128,128,128)
(121,126,125)
5
(0,0,0)
(17,16,14)
6
(0,255,255)
(0,190,186)
7
(255,0,255)
(224,89,189)
8
(255,255,198)
(244,239,186)
9
(255,255,255)
(239,242,242)
10
(255,0,0)
(214,22,41)
11
(0,255,0)
(0,173,52)
12
(0,0,255)
(0,96,198)
13
(128,128,255)
(99,147,218)
14
(128,255,128)
(82,196,118)
15
(255,128,128)
(236,118,122)
16
(255,255,0)
(254,215,0)
Printing from Windows Photo Viewer – Printer Manages Color
Did I miss something in the Lightroom print section?
Message was edited by: David Nestico. Rather than just posing a list of numbers, I summarized what I thought was important. All data is there in case someone smarter than me can make more sense of it :)I thought my problem could be Lightroom is in ProphotoRGB color space, and my printer is Adobe1998 color space. To test this, I changed the color space of my patches from prophoto to AdobeRGB. I checked my colors in Photoshop, and made them match the RGB number I specified. It was interesting to note that (128,128,255) had a noticeable shift to purple. the other colors shifted slightly. Now I printed the test page with Lightroom managing color and the printer managing color. Both images came out similar.
This study came about when I was printing some images, and the sky had a definite purple shift. So, I took the image into Photoshop and converted the colorspace from prophoto to Adobe. Printed the image, and the image came out much better.
So the question now is, do I need to convert each image I print in Photoshop, or am I doing something wrong in Lightroom? -
Unable to load icm printer profiles in Lightroom 5
I am unable to access correctly loaded RGB printer profiles in Lightroom 5.
In the print module when color management profile "Other" is selected no loaded profiles appear; and Lightroom usually freezes.
Using Photoshop v6 on same computer I can access all loaded printer profiles. I have reloaded LR5.
Does anyone have a solution or work-around for this problem?The "Include Display Profiles" checkbox is at the bottom of the list that comes up if you click "Other..." in the Lightroom Print Job panel. If this is the point where Lightroom freezes you won't get to it of course. So then the question is what prevents Lightroom from loading that list? Maybe someone else has suggestions, so hang on for a while.
Anyway, whatever the extension, the point is that the profile in question has to be the correct one for that particular printer/paper/ink combination. Apologies if this is stating the obvious, but you don't really have a choice between several, you just pick the right one. They install with the printer driver and are named for instance "Epson <model> Premium Semigloss" and so on, different profiles for different paper types.
Or you can make your own profiles. I believe the ColorMunki, for one, lets you create printer profiles as well as monitor profiles. -
Printer Profiles in Lightroom 4
I have a Mac Mini and Lightroom 4. I downloaded printer profiles from a local lab but don't know how to get Lightroom to recognize them for soft proofing and printing.
You need to put them in the correct location for the system to pick them up. This is in /Library/ColorSync/Profiles/ or in ~/Library/ColorSync/Profiles. After you put the profile there, restart Lightroom and they will show up when you select other in the profile dialogs in Lightroom. Unfortunately in the last versions of Mac OS X, the finder hides these folders by default. Simply go into the Go Menu and select "Go to Folder" or hit Shift-command-G and type the above locations. The drag the profiles in the resulting finder window. If you're the only user on the machine either location is fine.
-
Pros and cons Lightroom vs Photoshop printing
Greetings,
I'm only recently learning the details of Lightrooms Printing module. And I really like it. In fact I have a workflow of saving a PS file in an Auto Import folder so I can use LRs Print module in place of PS CS6.
A couple of questions. In PS I can select Black Point Compensation. But I don't see that option in LR 4.X.
I like that LR remembers my printing preferences. I use an Epson 1900 and 2400. My workflow is to print a 4x6 proof first, then a 13x19". I've learned to turn off Printer Manages color, I like Relative Colormetry, and I like that I'me able to save this as a Preset or template.
What I like In PS is I can grab the image and resize or move on the page.
An issue I have with LR, maybe someone has a solution, is if I want to type in an exact print size. Example for a 12x18" I want it to be 12.1" (a bit of extra space for matting) That is easy to just type in in PS.
What I hate about PS, is it doesn't remember any of my settings, Meaning I am compelled to check through the printer driver and advance setting each time to be sure color management is off and the Epson driver didn't switch paper types.
Under the hood, is the LR and PS printing the same?
In LR I can select the output to be say 360 dpi. In PS it sends what ever resolution to the printer, sometimes 900 dpi. Is there much of a difference between LR resizing to a specific DPI prior to print, or having Epson ingest the full resolution to print?
Final question. When selecting a paper type. There are two places. Inside the Epson driver. Example Premium Glossy, and also in Lightroom or Photoshop after selecting PS manages color. So which over rides which? If the Epson driver is set to Presentation Matte, and in either App I select Premium Glossy, who wins the fight?
Thanks!
MaxA lot of questions.
I would recommend that you watch some of the printing tutorials on Adobe's website. See here (and scroll down to "Printing"): http://tv.adobe.com/show/learn-lightroom-4/
As for the printing from PS vs. Lr (and under the hood), see here: http://forums.adobe.com/message/5229670#5229670
Generally speaking, there is no difference in print quality between Lr and PS if all parameters are set correctly. So it comes down to the question of preference of workflow: Do you rather print from Lr or from PS?
Also, you will - within a short time - notice that Lr has become not only your main image editor but also your image managing tool. In this situation it's just simpler to print from Lr instead of doing the round trip to PS. Also, in PS one tends to create an image copy for each print size; in Lr you can just do it with Virtual Copies. Or you can create a <saved print> that is added to a collection. That means you don't fill up your hard drive with file copies.
Your Final question: The paper type and size has to be selected in your printer driver. You do this from Lr by clicking on <Page Setup> in the print Module. The dialog that comes up is not Lr but your printer dialog / driver.
Lr will then "accept" the paper size selected in the printer driver / dialog. In Lr there is a selection for <Media Type> (not "paper type"!). Select what you are using - this selection affects the output sharpening that Lr applies "behind the scene". Also select the appropriate printing profile in Lr. The <Print Adjustment> sliders are best left alone. They are not necessary if your monitor is calibrated and set to the correct intensity (brightness). Apart from that these two sliders don't give you any feedback in Lr, i.e. you don't see their effects in Lr - only on the print. -
Lightroom 4 Export sizes not accurate? Print Space website london
Hi Guys,
I'm currently exporting my images from lightroom 4 to get them printed at the print space in London
i exported 3 files at A4 size in mm, i then uploaded them onto the print spaces website and all 3 images are very slightly off in dimensions
i took all 3 pics with the same camera, same lens, and they are not cropped at all, all exported at 300 DPI, all exported into Jpeg, all export dims bang on
i also exported another image which was 16"w x 22"h, again i uploaded to the website and same thing it stated the original file size was 16,9" x 23.2"
i sent the guys a message but they only use photoshop, so not that clued up with lightroom, has anyone else experienced this problem
when exporting an exact size and yet it comes out slightly different?
could it be that lightroom 4's measurements are out? i find that unlikely as everyone would complain!
i'm struggling for ideas on what else to try to solve this issue
One thing the guy mentioned at the print space was that you can switch to custom sizes and enter what ever size you require the print to be
but when you amend the width, it automatically changes the height... and vice versa, so you cant pick both custom H and W at the same time.
who would have thought that printing in A4 would be so difficult !!! :-)
Thanks for your time hopefully someone might be able to shed some light on this.
Cheers
ChrisWe'll need some details
For one such photo, we need the exact pixel dimensions of the photograph (you said you didn't crop, so I want the pixel dimensions of the uncropped photo)
We'll also need to know your exact settings in the Image Sizing dialog box (screen capture is best, but you can type these in if you need to)
And since I'm an American and not familiar with A4, exactly what are the dimensions of an A4 piece of paper?
Maybe you are looking for
-
<blockquote>Locking duplicate thread.<br> Please continue here: [[/questions/947572]]</blockquote> after I received the error message, i uninstalled and then re-installed mozilla firefox. my desktop now has a mozilla firefox icon and a separate folde
-
Adobe premiere Pro CC 2014.2 has stopped Working
Hey guys, I can start up my premiere pro CC 2014 but as soon as I choose a project to open, it loads for a second and then I keep getting the same error window that says: Adobe premiere Pro CC 2014.2 has stopped Working My computer: Processor: Intel
-
Bluetooth on iphone not connecting to mac
hi. i turn on my bluetooth on my iphone and the mac at school, but it never really finds my iphone, but it finds my friends regular phone that is a voyager. is there anything wrong with my iphone's bluetooth?
-
To distribute the qty with source
Hi I already have total qty in my report I wanted to have bifercation of that quantity with source for ex toatl qty qty source 200 100 112 100 231 how can i achieve the above if we already have total qt
-
Submit new Item Conditions via Function Module BAPI_PO_CREATE1
Hi all, I have problems using FM BAPI_PO_CREATE1. I want to transfer Item conditions via FM, but I am not able to change the netprice via FM, my Conditions are not displayed within the Item (only netprice of Item is displayed). I create POs out of a