Lightroom 4.1 RC2 movie problem

When I try to extrat some fotogram from an ".mov" movie, I found a problem beacause, after the extraction I need to restar the movie from the beginnig.
So is very difficult to extract consecutive image, because every time is necessary to restat from the beginning.
If I try to jump to a specified position in the movie, the acquisition result is a black image.

Yeah, I just checked : I have OS X 10.6.8...
The runniong at 64-bit, I'm not quite sure where to look/change that.... But I am running lithroom 4.0 without any problem (?)

Similar Messages

Lightroom 4.1 RC2 - Keep crashing

I downloaded lightroom 4.1 RC2 cause the 4.0 was crashing ( randomly )....
Now i have the same problem using a SINGLE monitor with the release candidate 2 of lr 4.1...
when i change setting fastly, lightroom simply crashes.
I am seriously thinking to go back to version 3 and get a refound by adobe. My studio had to process over 3k images at day and it's impossible to work with this new version.
i am working directly to 5d mk2 cr2
My pc is a windows 7 sp1 64bit:
quad 9300
8gb ram 5-5-5-15 geil black dragon 8500
crucial m4 ssd 128gb
ati 3400 hd
dual monitor ( actually i am using one monitor cause of the known bug of crashes and wrong saturation and contrast in secondary monitor issue )

I am also crashing on Win7 64bit...but not just Lightroom, it actually crashes my whole machine. I'm on a fresh install of Win7 with only CS6 & Lightroom installed. Lightroom so far has been the only program to cause this, and it typically happens when I'm adjusting filters or moving sliders for example. I'm guessing it's when I'm taxing the CPU/memory a bit...However, when performing the same type of tasks in Photoshop, AE, etc., I have not experienced any crashes. I've ran some diagnostics on my memory as well as my hard drives to hopefully rule out any hardware issues, and it all seems to check out OK. Because it's crashing the whole machine, I'm unfortunately getting no feedback in the system/error logs. I'm at a loss right now, and it seems others are only having application crashes.
System specs:
Windows 7 Pro - 64bit - Service Pack 1
Intel i7 960
6GB RAM / (2) SATA III 2TB Drives
NVIDIA GeForce GTS 450 w/ Dual Monitors
CS6 Creative Cloud
Lightroom 4.0

Lightroom 4.1 RC2 - Secondary monitor issue

Hi
lightroom 4.1 rc2 seems to have solved the crash issue when using a secondary monitor.
NOW i have another HUGE and HEAVY problem...
The image that appears in the secondary monitor have total different colors than the reality... and when switching the configuration ( so main window go into secondary monitor ) colors are fine ( so this isn't a bad configuration between monitor and lightroom.... ).
Images in secondary monitor appears less contrasted and greenish. And that's a big issue ( cause i use secondary monitor for the correct balancement for printing ).
I repeat that the main window of lightroom shows the image correctly when working with secondary monitor as main...

Known bug.
http://feedback.photoshop.com/photoshop_family/topics/lr4_rc2_differences_in_rendering_in_ library_and_develop_modules

In Lightroom mobile how can move photos within the collection????

In Lightroom mobile how can move photos within the collection????

What you can do is to move (or copy) a photo form one collection to another. This can be triggered via the top right app menu item from grid view. Same menu is available when you open up an image for editing. Hope that helps. -Guido

I can not import photos into lightroom 4.4 Had no problem before this time.

I can not import photos into lightroom 4.4 Had no problem before this time. I have camera raw7.4 and use a NikonD7100. I have a Mac using 10.6.8. I can see the images and selected for import in Lightroom, but after I check "import" I get a message that Lightroom could not read the files. This happens with both raw and jpeg files. Thanks for a repl

thanks for the reply. would you please tell me how to check for the folder to have write permission. I have done the same settings as before but this time does not transfer. It says can not read files with a code "298". I can see the thumbnails on the screen prior to trying to import the photos, also can see them with the card in the camera and using the view mode. I have up to date camera raw 7.4 for my Nikon D7100 and the settings allow for 7.1 and above

Lightroom 4.1 RC2 (1:1 previews, slow editing large files, stops working)

I am running win7 64 bit with 12GB RAM and installed Lightroom 4.1 RC2. 1) I am (trying) to edit large panoramic files, and the 1:1 preview images do not seem to be saved from session to session. Images take quite a while to load in Library and even longer in Develop. 2) There seems to be a major memory leak. Upon startup I can edit a couple of panos, but then the machine becomes very slow and basically quits working. 3) I don't see "x64" in the tile bar. Is it running 64 bit?

Running Win7 64-bit here as well and installed LR 4.1 RC2 last week. There is definitely a memory leak of some sort, as I too am experiencing major latency after a few minutes of editing. When I check memory usage in Task Manager, I'm seeing more than 2GB (of 4GB) of RAM being consumed by LR and my machine is running like molasses.

Avendo installato l'ultima versione ( Lightroom CC ) e trasferito tutti i cataloghi della precedente versione ( Lightroom 5 ) nella nuova versione, posso ora disinstallare completamente Lightroom 5 dal computer ( senza problemi tecnici o di licenza ? ) G

avendo installato l'ultima versione ( Lightroom CC ) e trasferito tutti i cataloghi della precedente versione ( Lightroom 5 ) nella nuova versione, posso ora disinstallare completamente Lightroom 5 dal computer ( senza problemi tecnici o di licenza ? ) Grazie

Lightroom 4.1 RC2

Lightroom 4.1 RC2 has quit and when I try to start the program it tells me the Beta version has experied. I cannot find lightroom 4.1 (which i purchased) Hellp?

You can follow the directions listed at http://forums.adobe.com/thread/1006208?tstart=0 to download the install files from your account. Also since it is Photoshop Lightroom you can download the Photoshop Lightroom 4.1 update from the Product Update page at http://www.adobe.com/downloads/updates/.

On a Mac, Just upgraded from Lightroom 4, to 5. Problems with Catalog transfer.

So I did the upgrade version of Lightroom 5 from 4. I did the catalog transfer to move all of my images over from lightroom 4 to 5. But now when I click on any of my old images (from a lightroom 4 catalog) in lightroom 5, I get an error message that says Lighroom has a problem reading the images. Last night I tried to export from lightroom 5 to my desktop and it did not work with the same error message coming up. Help!!! What am I (did I) doing wrong?

-Once I put the disc in I followed the procedures to upload LR5. This was successful. The first time I opened LR5 I was prompted to transfer my old LR4 catalogs to LR5 which I did.
-Now when I click on any image, once I click away, in the lower scroll bar of images an exclamation mark in a small circle. When you click on the exclamation mark this message appears "Lightroom has encountered problems reading this photo. You will not be able to make adjustments to the photo." This happens to every image I click on.

Lightroom 4.1 RC2 Crashes

Windows 7 64 SP1 with all MS patches. Had crash problems with 4.1 RC1 also and hoped RC2 would fix them. No problems with LR 3.6. LR runs OK for a while but eventually crashes. Can't identify any action in particular that causes it to crash. Here's the info from the crash dialog:
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 4.1.0.11
Application Timestamp: 4f9700dd
Fault Module Name: mfc100u.dll
Fault Module Version: 10.0.30319.415
Fault Module Timestamp: 4d26eaa8
Exception Code: c0000005
Exception Offset: 0000000000264dd8
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 2c25
Additional Information 2: 2c25001fd5296f082fed0942ce10eaf7
Additional Information 3: f531
Additional Information 4: f53123819697f9a972934918a649d0df

Hi,
This can also occur with LR 3.6. I had multiple crashes with LR 3.6 since I installed the 64-bit version under Windows 7 64-bit Ultimate (8GB memory available). Like you, I couldn't relate the crash to any particular action.

How do i move photos and catalog to a new drive and have lightroom make the same move

I am trying to move all my photos to a new drive with different drive letter. I know I can do a backup and restore inside PSE13 to perform that. However, I also have Lightroom 5 on the current setup. How would I now use the new location for the photos in lightroom if they are already moved by PSE?
Hope this makes sense!

I don't recommend the Time Machine or Migation Assistent approach. The first tneds to be very slow and the second often carries baggage that is probably best not transferred to a new computer.
Lightroom doesn't use activation, therefore, can be installed on your new Mac without having first removed it fom the old. Your images and catalogs can be copied across to the new Mac using an a portable disk drive as the transfer medium. Typically, on Mac computers, the catalog and image files are stored in the Pictures folder. If this is where you have them then then copy them to the same location on the new Mac. Once copied you can open the catalog folder then double click on the .lrcat file to launch Lightroom.

Lightroom 1.3.1 Printing Problems with Apple OSX 10.5 (aka Leopard)

Whilst the majority the majority of Leopard related print issues were addressed when Adobe updated Lightroom to 1.3.1 and printer vendors released updated drivers some issues remained and it has been left to users to establish workarounds. One such proven workaround is presented below:
Information and text by Jason Hicking
I've been having exactly the same issues running a nearly identical system but on a MacBook Pro with an external Eizo 24" monitor for critical work. My results also mirror yours ie slightly greener and darker prints from LR than PS.
I've spent literally hours troubleshooting this as I own a digital imaging company that offers printing and colour management to our customers, many of whom have the same setups and same issues. Well I'm glad to say that I seem to have found a (temporary) fix. Read on and let me know your thoughts...
If you go into the Apple ColorSync Utility (in the Utilities folder on your hard drive) then follow these steps I'm pretty sure you'll get accurate prints that match Photoshops output.
Step 1 Open ColorSync Utility and click on the Devices button at the top of the window.
Step 2 Click on the grey arrow to reveal the Printers list
Step 3 Click on the grey arrow next to "EPSON Stylus Photo R2400"
Step 4 Locate the profile that relates to the media setting that was used when you created your custom profile. For example I create most of my custom profiles for gloss or satin media using the Premium Semi Gloss media setting so in Colorsync Utility I choose "SPR2400 PremiumSemigloss"
Step 5 Click on the arrow next the text "Current Profile:" and choose Other...
Step 6 From the window that opens, choose the profile that you are using to print through in Lightroom, as an example I choose "R24 IlfSmGls PSG NCA" as this is the profile I made to print on Ilford Smooth Gloss and the one I'm selecting in Lightroom.
Step 7 Click on OK to accept this change and ensure that it's actually changed in the ColorSync Utility window. If everythings OK then close Colorsync Utility and return to Lightroom.
Step 8 Print from Lightroom, choose the exact same profile and rendering intent that you would normally, click on the Print... button, make sure the preset is set to Standard then select the matching media setting and quality settings that were used to create the profile (as you would when printing from Photoshop), remember to check that No Color Adjustment is set in this part of the driver.
Step 9 Click on the Print button and in a minute or so you should get a print that matches your Photoshop output and more importantly matches your 'calibrated' screen.
Step 10 Presuming this works save this setup as a template in Lightroom for future use.
This may seem long winded in text form but it's a one time operation and I wanted to make sure that every step was included for clarity.
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. Also note that even when your profiles are set this way in the Colorsync Utility there is no difference in accuracy or colour when you leave it set like this and print as usual from Photoshop.
Attached screenshot of ColorSync Utility provided by Ian Lyons
A Lightroom print tutorial is also provided at: http://www.computer-darkroom.com/lr_13_print/lightroom_print.htm

Well, maybe, CS3 is the only one fully compatible, but Photoshop CS and CS2 will work...mostly. There are a couple of niggling little problems, but I have been able to do what I want, one way or another, with CS1. Elements 2 is, like PS7, a dead letter in Leopard, but Elements 3 and 4 work. Of course, these older programs run in Rosetta, being non-Intel native, and so my MacPro runs them at the same speed as my old G4 dual 800. I'm looking forward to a speed boost when my Xmas upgrade to CS3 is installed.
Francine
Francine
Schwieder

9.2.2 install/move problem with G4 QS 2002

I have a G4 QS 2002 with two 500GB HD's. One is partitioned into six unequal partitions, Leopard, Tiger, Panther, System 8.6 - 9.2.2, Yellow Dog, and Scratch. The Leopard has a bootable System 9.2.2 and as soon I have 10.5 in my hands AND my problem is solved, will have the Leopard OS installed. The other HD has one very small emergency partition that was created by the installation of TechTool Pro with 10.3.9 and one "large" partition.
My problem is: 10.5 doesn't support/have the "Classic Environment" and I don't want to risk screwing up having a bootable 9.2.2 OS by the 10.5 installation, so I'd like to have the "System 8.6 - 9.2.2" partition be able to boot 9.2.2 instead but I haven't been able to achieve that yet.
What I've tried is:
1. Booted into 9.2.2 and attempted to do a copy but when booted into 9.2.2, it doesn't "see" the target partition because I don't let it reformat the partitions that it doesn't recognize such as the "System 8.6 - 9.2.2" partition when I boot into 9.2.2, so that partition and a few others are not mounted when I boot into 9.2.2 (I might let it reformat it if I can be sure which of the partitions it wants to reformat is which).
2. I created an image of the 9.2.2 bootable partition with Tiger's Disk Utility and tried to restore it with the "System 8.6 - 9.2.2" partition as the target. It didn't want to do that. I booted with the Tiger install DVD and restored the bootable 9.2.2 image to the "System 8.6 - 9.2.2" partition (selected the "Erase target" option). I restarted the Mac and I notice that the restored system folder is not graphically "blessed". I can choose the "System 8.6 - 9.2.2" partition as the startup disk but it won't boot and instead the Mac eventually boots another OS. If I restart and hold down the option key, I can see that there are two bootable volumes labeled "Leopard", the original one and the restored one which in the Finder and Disk Utility is labeled "System 8.6 - 9.2.2" but it won't boot with the "System 8.6 - 9.2.2" partition that way either.
3. I put the special version of the QS 2002 specific System 9 install CD into the DVD drawer, restart, and held down the "C" key, but the Mac eventually booted another OS. I booted into 9.2.2 and tried to launch the install SW but it couldn't see the "System 8.6 - 9.2.2" partition (see #1 above) and neither could any of the System 9 disk utilities with the CD. I boot Tiger, launch "Classic Environment" and try to run the installer but after a few screens it complains regardless if I let it do a clean install or update the restored 9.2.2 from the Leopard partition.
The options I think I have at this time are:
1. Boot into 9.2.2 and let it reformat the "System 8.6 - 9.2.2" partition if I can determine which partition it is and try the various steps again hoping that one will work.
2. Install 10.5 into the Leopard partition and hope that it doesn't screwup the ability to boot 9.2.2 afterwards.
3. Install 10.5 into the "System 8.6 - 9.2.2" partition, which is half the size of the Leopard/Tiger/Panther partitions, and live with the smaller size (or try a partition utility like iPartition, DiskStudio, or hope that the DU with 10.5 can resize partitions without really deleting them first).
4. Do what I did originally, locate my System 9 install CD, see if I can still boot with it and install a generic System 9 into the "System 8.6 - 9.2.2" partition and update the SW with the QS 2002 specific System 9 install CD so it is bootable.
5. Try a cloning utility like CCC, SuperDuper, etc. and hope it works better than creating an image and restoring it (isn't that how Apple intends for us to do backups and recoveries?).
6. Back up everything even though making images doesn't seem to be foolproof, repartition the HD and reinstall/restore (I don't like this since I don't seem to have the image/restore process working to my liking and this would take a very long time (maybe 10.6 will be shipping by the time I'm done but I doubt if it Apple will support G4's with 10.6)).
OR somebody tells me what I'm doing wrong or why my efforts don't work or what is the process that achieves my end state.
TIA.

Hi, barubin -
If a volume (volume = an unpartitioned drive, or a partition of a partitioned one) does not mount when the machine is booted to OS 9, this usually means the drive or the volume does not have OS 9 drivers installed. This usually results when the drive was last formatted using OSX's Disk Utility to initialize the drive, and the option to install OS 9 drivers was not selected.
Article #106849 - Disk Is Available in Mac OS X But Not in Mac OS 9
If a volume does not mount when the machine is booted to OS 9, then OS 9 can not be installed on it using an OS 9 Install CD (since it is not available to, can not be 'seen' by, the installer app); and it can not be used as an OS 9 boot volume (if OS 9 can not mount the volume, then OS 9 on it can not mount itself).
The above article suggests one possibile way to recover from that without re-initializing the drive - boot the machine to OS 9, run Drive Setup. Select the drive in question (Drive Setup can not do this for a single partition of a partitioned drive), then choose Update Driver from the Functions menu. Note that this is a non-destructive function - no data will be lost from the drive whether or not it works. If it does work, the drive, and its partitions, will then be mounted on the desktop.
Unfortunately that recovery method rarely works, and it then becomes necessary to redo the partition or the drive.
This can be done using OS 9's Drive Setup, but only on a whole-drive basis - Drive Setup can not re-initialize a single partition of a partitioned drive.
It can also be done using OSX's Disk Utility; Disk Utility may be able to redo a single partition of a drive (I don't use OSX so can not test that), but it is probable you would need to redo the entire drive. Be sure to select the option to install OS 9 drivers when using Disk Utility - that option is not always selected by default.
In either case select Mac OS Extended as the format.
<hr>
OS 9 has a boot limitation - the volume it is on can not exceed 200GB. 190GB is a safe max volume size to pick for an OS 9 boot volume when partitioning a drive.
<hr>
The installation of OSX (any version) on an OS 9 boot volume should have no effect on the OS 9 install or its bootability, provided the install method is a simple installation (no Archive and Erase, etc.).
<hr>
It is not necessary to use a cloning utiity to move/copy OS 9 to a different volume or drive, and have it be usable. OS 9 can be installed -
• From an Install disk valid for the machine
• Or by doing a simple Finder copy of it - drag the OS 9 Syatem Folder (and its associated folders, such as Applications (Mac OS 9) and Documents) to the target volume and let go, letting Finder copy it there.
Usually a copied OS 9 System Folder is usable immediately.
Occasionally it will arrive unblessed - it will not display the Mac OS glyph on top of the folder icon. The solution for that is to re-bless it. This can be done one of two ways (best done while booted to OS 9) -
• Open the System Folder, double-click the file System to open it. Close System; close the System Folder.
• Drag the files Finder and System out of the System Folder; close the System Folder. Drop the files Finder and System back into the closed System Folder.

Lightroom 2, 5.5 upgrade problems

Was printing to an Epson Stylus Pro 7600 from Intel Mac OS X v. 10.5.8 for some time without problem until upgraded to 5.5.
Now get "bundle could not be loaded because it does not contain a version for the current architecture. Print setting 3.09" message in the Print Dialog Box.
According to Epson using current printer driver.
Can still print from Photoshop CS4 without a problem.
Any thoughts to solution of the problem?

Have you upgraded Lightroom to version 2.5??????????.
The 5.5 you are referring to is ACR which is a plugin for Photoshop CS4.
ACR 5.5 in Photoshop CS4 provides the same develop functions/tools as Lightroom V2.5 in develop module.
Lightroom is a program that is completely independent of Photoshop, ie you do not need Photoshop for Lightroom to function.

Lightroom 4.2 RC print problems to Canon ipf6300

I have had repeated problems printing this image:
It was originally shot on an IQ180 then converted to TIFF before being loaded into Lightroom for further work. It has a lot of delicate blue colours many bordering on cyan. When I print it to the ipf6300 it always comes out with the blues so heavily shifted towards cyan that the prints are unusable. If I send the exact same file from Lightroom to Photoshop, and print it from there, the results are the same as the softproof image on screen, perfect.
I use Hahnemuhle Fine Art textured paper, with the correct profile and all the other setting are correct, though if I change from 16 bit to 8 bit or vary the quality, the results are the same, as they are if I use Canon's own Fine Art Textured profile.
I am really quite an experienced printer but this one really has me stumped: it can't be a corrupt profile because it works in Photoshop.
Any ideas, fixes, ot just similar experiences from others would be greatly appreciated!
Thanks

I have the iPF6350, and I am also struggeling a bit, but more with my (of course calibrated) screen not matching the white point of the prints (screen has red tint, compared to the prints).
Also some photos look just a bit different in PS than in LR, esp. yellow/orange tones. To me it seems like PS is (still) somehow rendering the photos in a slighty different way than LR (not only RAWs, also TIFF are shown different), which could explain why results of prints are different, too.
If you want to send me a version of this photo I could try if I can reproduce the problem here - but I have only PS5, not PS6 yet... but anyway it would be more interesting to get it correct in LR (too).
What happens if you make a print to jpg? Are the colors correct then?

Lightroom 4.1 RC2 movie problem

Similar Messages

Maybe you are looking for