Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: The View on July 06, 2007, 04:35:20 pm
-
1.1 has certain problems, that I hope will be fixed in a 1.2 follow-up.
1. Speed. 1.1 is noticeably slower than 1.0. This is a major problem if you are working on a G5.
2.. I had the film strip freeze twice, where only one image in the center of the strip displayed a changing row of images, all others stayed frozen. Remedy: quit LIghtroom, and reopen.
3. Healing tool tends to switch to clone when you switch between clone and no-clone tool.
4. Healing tool: spots cannot be enlarged. The marks for increasing the already done corrections appear, but when you want to drag and drop it larger, it does not react. Not even a beach ball. When you let go, the healing spot sometimes disappears, sometimes it stays the same size.
5. Healing tool extremely slow in 1:1 (it is as fast as usual in 3:1)
-
To be more specific about the slowness: it is about the loading of new images from library into develop.
Not always. But too often. And I can't say yet why or when.
I have the impression, that when I open many photos one after another and compare them, the application gets slower and slower.
-
1. Differing image quality. See other thread.
2. Speed.
Other than that, great stuffs, the sharpening is great!
-
I don't notice any speed difference so far. Overclocked 6700.
-
Yep, me too. LR 1.1 is going along fine, working beautifully for maybe thirty minutes or so, and then it's like a cork being tossed on a rough sea. Everything stops, the computer goes into a riff, with much huffing and puffing, the hourglass comes up on the skreen, so you go for a cuppa and come back later. After several minutes, everything settles down, LR returns to normal, and then the same performance happens again after another similar interval. It's as if the programme has run out of breath and needs to catch up on itself.
Another nuisance: it takes ages to export files into PS3. A lot more huffing and puffing, and sometimes crashes. I'm a PC user - is that part of the problem? My machine is relatively new, with loads of ram and disk space, not to mention two external hard drives with plenty of capacity. CS3 and Bridge run seamlessly with no problem, but I am very attracted to LR and want it to deliver what it says on the tin. So far, it hasn't - by a good mile.
It's very frustraing because the programme is a brilliant concept - sharpening vastly improved, clarity a fantastic tool, and so on. But bugs and many other issues reported here and elsewhere, particularly on the Adobe User to User Forum are really another disaster in the making as far as a smooth workflow is concerned. Hopefully, the Adobe creative team will get on top of the situation soon and put a lot of well disposed users out of their misery.
Seamus Finn
-
1.1 has certain problems, that I hope will be fixed in a 1.2 follow-up.
1. Speed. 1.1 is noticeably slower than 1.0. This is a major problem if you are working on a G5.
2.. I had the film strip freeze twice, where only one image in the center of the strip displayed a changing row of images, all others stayed frozen. Remedy: quit LIghtroom, and reopen.
3. Healing tool tends to switch to clone when you switch between clone and no-clone tool.
4. Healing tool: spots cannot be enlarged. The marks for increasing the already done corrections appear, but when you want to drag and drop it larger, it does not react. Not even a beach ball. When you let go, the healing spot sometimes disappears, sometimes it stays the same size.
5. Healing tool extremely slow in 1:1 (it is as fast as usual in 3:1)
[a href=\"index.php?act=findpost&pid=126885\"][{POST_SNAPBACK}][/a]
1. Speed - 1.1 is at least as fast as 1.0 was on my Mac Pro. That's just gut feel. I haven't done any formal speed tests.
2. Film Strip Freeze - No problems here. The only problem I had in 1.0, where I wasn't able to export my changes to an XMP file, now seems to be fixed. So hooray for 1.1.
3. Healing Tool Problems - Seems to work OK for me.
4. Healing Tool Speed - I haven't noticed any slow down.
All in all, I was happy with 1.0, and I'm equally happy with 1.1. But I guess Lightroom isn't the first tool to have differences across platforms, so I'm guessing that's what happening here.
-
Mostly I see little difference between the two versions.
Speed seems to be quicker, particularly getting started. Can't see why it should be slower but I'll bet there is a preference setting that has been changed. If Lightroom runs slow, it can be vastly sped up by using 1:2 instead of 1:1 in the loupe view. When you start working a number of photos, there is a lot of processing going on and this eases the load heaps. Use Apple+ and Apple- on a Mac to push this to 1:1 for the odd photo where 1:2 is not enough. Dead quick.
I found a very odd flaw today. Trying to print a custom size off a roll of canvas, the print screen fragmented. The ruler grid stayed put even when I moved to Library, Develop and Slide, even after I quit and reopened. It needed a very unMac-like reboot to fix this. But it did fix and it did my 17x14 print fine!
Otherwise, all the above mentioned improvements are great.
Don.
-
Here's a good one for you.... I found some History weirdness. I'm not sure how to word this, so I'll describe how to reproduce it...
In Develop module, pull up a photo to work on. Make a couple of changes so you have some history - for instance, adjust the Exposure and Clarity. Now, pick an adjustment that's been changed - say, Clarity. Click on the number on the right side of the adjustment, as if you were going to change the number by hand. It should change to an editable field with the existing setting highlighted. Now, while that number is highlighted, change something else in a way that won't un-highlight the setting you selected above - for instance, double-click the word Exposure to set Exposure back to its default. The highlighted setting should still be highlighted. Now hit Enter to accept that setting and save it.
Ok - what you've just done, in my example, is adjust Clarity and Exposure. Both settings should have been made and you should see their effects on the picture. BUT - you'll only have a history change for the Clarity adjustment!
There's also the weird alt-click on adjustments behavior I noted in another thread. I've seen more weirdness with other files on this. The short form is that, when adjusting sharpness settings at 1:1 magnification, if I alt-click any of the four sliders, I sometimes don't see the display at all - the normal image remains, or sometimes see an all white screen. In all cases, the adjustments still work - just that the alt-click display doesn't. I haven't gotten enough of a handle on this to file a well described bug, at this point....
Edit to add - 1.1 seems to be less stable for me, and is definitely slower than 1.0 on my system (Athlon64 3200+ w/ 2GB RAM, running XP). However, I can't say this is an apples to apples comparison - I didn't have anywhere near the number of photos in the library as I have after doing the upgrade.
-
I found that DNG's tweaked in Lightroom 1.1 dont open in Photoshop CS3 with the Lightroom ajustments. Not great if you ask me.
Damien.
PS: Same thing on an Intel mac and a G5 mac.
-
I found that DNG's tweaked in Lightroom 1.1 dont open in Photoshop CS3 with the Lightroom ajustments. Not great if you ask me.
[a href=\"index.php?act=findpost&pid=127038\"][{POST_SNAPBACK}][/a]
User error. . .how are you opening them? If you haven't synced the settings, Bridge/Camera Raw and Photoshop won't know the settings, of course.
-
User error. . .how are you opening them? If you haven't synced the settings, Bridge/Camera Raw and Photoshop won't know the settings, of course.
[a href=\"index.php?act=findpost&pid=127044\"][{POST_SNAPBACK}][/a]
Oh, doesn't the embedded metadata within dng gets saved when you close LR?
Why do we need manual sync, must be some reason.
Would it be not better to have it saved on exiting LR & then DNG if ever open in photoshop or other application that can read dng & its metadata they can process it.
-
Oh, doesn't the embedded metadata within dng gets saved when you close LR?
[a href=\"index.php?act=findpost&pid=127057\"][{POST_SNAPBACK}][/a]
No, unless you have write metadata on in the background...personally, I rarely need to bounce back and forth so I turn the option off and only worry about updating on an image by image or folder by folder basis...
And here's another real good reason you don't want to be writing updates unless you need to. Writing the change changes the modification date on the file which means it will get picked up in any date/time backup process. So even if you change ONE little setting, it's a whole new file that must get backed up.
That's one of the real benefits of using a database...
-
All in all LR is better with the sharpening ,clarity is great. I do not understand why the sliders on the sharpening drag though . The others are smoother then Ver 1.
What kills me in the clone and healing tool . I just send it to PSE3 to do so much easier. I mean the LR spots in those tools looks like damn planes on a air traffic controller's screen in LaGuardia Airport . Why do they have all the old ones all clumped up like that . I just hope the fixes remain free . I know a lot to ask !
Don
-
The sliders drag because you don't have enough CPU power to keep up. I'm fine at home buy my older work system isn't enough.
-
What kind of PC power woud you need to run LR smoothly?
-
Two LR 1.1 bugs that I encountered,
1. File export just stopped creating images mid-way.
Exported three separate collections output "thread" at the same time, the first with 1,100 images, second 500 images and the third 100 images.
The third thread never did generated a single completed image, in the target folder a partial work-in-progress file was shown. It then showed an output error. Re-started the third thread another two times and it gave the same error.
The first thread generated around 200 images and the second thread less than 20 images. Left the XP machine (3.2Ghz, 2GB ram) running for a few hours before I noticed that it was not really outputting anything after the first 30 minutes perhaps.
My guess is that the program got itself locked out by the first and second output threads perhaps holding onto some common system resource or database table. There is no other reason I can think of for causing this strange behaviour as running a single thread with 1,000+ images previously was fine (or had another second output thread with a small set of images running in parallel was ok too).
2. LR exited by itself and needed to be re-launched.
Was doing a quick image adjustment and output a single image after each adjustment before moving onto the next image (for a 1,000 images collection). Perhaps for most images spending less than 5 seconds each. Switching frequently between the image browser and the develop menu. All image adjustments were done in the develop menu.
After a couple of hundred image edit, LR suddenly exit by itself. Re-launched LR and checked the last few image adjustment settings. Nothing was lost but surprised that a program just exited without any error message.
This is the first time I am seeing stability issues with LR for large amount of images processed. Wondering if anyone else had tested LR through 'stress loads' and see if the program runs smoothly. Other than these "speed bumps", I am very happy with LR on the whole
regards,
Vic
-
What kind of PC power woud you need to run LR smoothly?
[a href=\"index.php?act=findpost&pid=127429\"][{POST_SNAPBACK}][/a]
Well, it runs smoothly (in every respect -- all sliders, changing modules, etc...) on my machine.
Athlon 64X2 Dual Core 4400 2.21GHZ
2 GB RAM
My only glitch so far is a large number of files being labeled with warnings that I have edited them externally -- but, I haven't. Hmmm....
-
Not sure why anyone should have smoothness issues. I only have a 1.67 G4 Mac with a gig of RAM and Lightroom runs very smoothly. That was not the case with Aperture, which made Lightroom an easy choice. I do have to wait with a large file sometimes if I enlarge to full size but it doesn't jam anything while I wait.
Don.
-
LR 1.1 runs smooth here with a Pentium 4, 3.20GHz and 2GB of RAM.
-
1. Slow export & opening in CS3 - am using quad core Mac with 3Gb RAM
1a. Sometimes the .PSD is locked once it is opened in CS3, have to Save As..
2. No proper network access. Eg can't run Library from a server
3. Multi photographer workflow. It is impossible for 2 photographers to work on the same Library at the same time, related to the above.
4. Web gallery is useless to me, since it can't handle custom watermark. Having a little bit of text on the bottom of the image is not good enough.
-
On my system (windows/ 3 GHz dual core/ 4GB ram) LR 1.1 is much, much slower in one aspect. When I load a new image to view in Library, Lightroom loads it, but it loads it in a blurry mode. For sharp focus to occur, it can take up to 8 seconds. The entire time I am waiting for sharp focus, Lightroom displays the "working' or "loading" alert at the bottom of the image window. It is very frustrating.
I wonder if the people who are not having problems are using smaller, or different format images. I am using full size RAW (CR2) from an EOS Mark3. When I was using LR1.0, most of my images were Raw from a D30. Perhaps that is the problem. I will have to run some D30 raw's through LR1.1 to see the result.
-
On my system (windows/ 3 GHz dual core/ 4GB ram) LR 1.1 is much, much slower in one aspect. When I load a new image to view in Library, Lightroom loads it, but it loads it in a blurry mode. For sharp focus to occur, it can take up to 8 seconds. The entire time I am waiting for sharp focus, Lightroom displays the "working' or "loading" alert at the bottom of the image window. It is very frustrating.
I wonder if the people who are not having problems are using smaller, or different format images. I am using full size RAW (CR2) from an EOS Mark3. When I was using LR1.0, most of my images were Raw from a D30. Perhaps that is the problem. I will have to run some D30 raw's through LR1.1 to see the result.
[a href=\"index.php?act=findpost&pid=128252\"][{POST_SNAPBACK}][/a]
Just for interest, I tried what you said using Olympus Raw files from an E300. I have to assume you are talking about loading at full one to one resolution? Just loading an image to view takes about one second, enlarging a fresh image one to one took about 14 seconds. I only have a 1.67GHz G4. If you are talking about the normal view, as opposed to a one to one view, I wonder if screen size has anything to do with it? Mine is only 15 inch.
Don.
-
My 'working' wait time has not increased. All my images are 30D RAWs. 2-3 seconds each, at most the first time.
-
It could be that G5s and older computers have to work harder under 1.1.
For example: when adjusting blacks or exposure, you could see the effect right away in 1.0.
In 1.1 there is a short blurry phase, and then you see the result of the slider operation.
-
2. No proper network access. Eg can't run Library from a server
3. Multi photographer workflow. It is impossible for 2 photographers to work on the same Library at the same time, related to the above.
That is also related to the use of SQLite, which isn't the proper choice for concurrent access by multiple users. For that, you really want a DBMS.
Adobe could, I suppose, ship the software of the option of storing the data in a database server accessible via ODBC or connecting "natively" to a selection of DBMSes (e.g. Oracle, Microsoft SQL Server/Sybase, PostgreSQL). But that means that your two photographers now also have to maintain a DBMS, or hire someone to do so.
I think Adobe's compromise is good enough for the time being, but would of course appreciate the option of using ODBC instead.
-
I asked this on another forum but not sure I understand the reply. When I open a folder, LR's presets automatically revert to Sepia and changes every image in the catalogue including all adjustments (exposure etc) which means I have to redo the lot manually again. Synchronise doesn't work for me very well because all my pictures are taken in a variety of conditions and lighting, mostly landscapes. I've tried everyting in preferences but can't solve the problem (the solution may be staring me in the face but I can't see it). Is there some box I should have ticked/ticked? Any ideas?
-
Seamus, are you importing a new folder, or just going to view a folder that you've already imported in the Library? If you're importing, there's a field to select a Develop Settings preset to apply upon import - you've probably got "Creative - Sepia" selected. Pick None, instead.
If you're looking at a folder that's already imported to the Library, I don't know what's going on - but you can fix it by going into Develop for each photo, and selecting the previous history step - there will be a new step for the application of the Sepia preset, and selecting the previous one gets you right back to where you began. No need for lengthy changes, etc...
-
Thanks for that, Dave - incidentally, the folders are already imported, and as I open each one, LR flips to the sepia setting and changes each image in that folder. Moving on to another folder, the same thing happens to every folder I open.
-
Dave,
That worked. The preset seemed to be stuck on sepia for some reason. I still don't know how it happened, however. Interesting how a solution is sometimes hiding in plain sight - especially when getting used to a new UI. Thanks
-
Cool - glad that was it, man
-
Using Win XP SP2 (fully tweaked) on a semi-ancient P4 2.0 Ghz with 1 GB RAM...
LR v1.0 was working smoothly. Happy.
LR v1.1 would often hang after about 15-20 mins of work, CPU usage climbing to around 90%. Import at times refused to work, either via the open dialog or dropping files into the library. Export - in most cases just nothing. And so on ...
Went back to LR 1.0. Happy.
Just to (re)state the obvious for anyone passing through here who is thinking of updating:
1) it is essential you read the release notes [ see link on the Adobe DL page ]
2) look through the relevant sections of the Help documentation.
3) make sure you understand how LR databases work and how to back them up - just in case.
For anything else (or more):
http://www.adobeforums.com/cgi-bin/webx/.3bc2cf0a/ (http://www.adobeforums.com/cgi-bin/webx/.3bc2cf0a/)
While v1.1 was up and running I did get a chance to test some of the new features and yes, some nice things to look forward to there.
My guess that the marketing guys at Adobe pushed for an early the release date when v1.1 wasn't quite cooked. It would have been more appropriate for Adobe to release v1.1 as a beta with a proper bug report system - an easier ride for all concerned. I just hope they consider that option for future updates.
Andre
-
Another annoying thing is the increased loading time of images. After going through three or four images in the develop module, loading time increases to up to five seconds, then shortens again. As if something was strangling the data pipeline.
I will definitely read those release notes Andre22 mentioned.
I hope there will be a 1.2 release soon to fix the 1.1 bugs.
-
Sth different I noticed:
After stacking pictures, the stacked group is moved to the end of the folder...
I tried to sort again > sort on capture time... but nothing changed! The stacked pictures were seperated from the non-stacked ones that were taken at the same time of day and moved to a place after the last day of that shoot.
Especially in large shoots, this is not such a good thing. I spend too much time looking for certain pictures.
I also noticed this moving of the order of files after setting new ratings.
Does this mean the sorting of pictures is a flaw in LR 1.1? Or does this mean I have a flaw?
Thanks, Giedo
-
All my issues seem to be related to a fat and overload......
My G4 (1.3gh, 1.25 gb ram) under 1.0 ran great, just without the nice features of 1.1.
1.1 seems to take more memory to do everything. Some of my photo shoots can contain 300-1600 images. Making preview web (in chunks of 500) sites was handled fine (but slow) under 1.0. But under 1.1, my machine can go away and never come back. When it tanks (just stops running), it comes back to the same menu it left off. If you don't catch it, it can tank again.
This application reaks of all the problems that were in Windows 3.0-3.1, where the application did the memory management - not the os.
In my opinion, if it can't work well in a gig of ram, it's time to recode. You can't blame sqllite, as I have Mysql server using 32meg of ram. I suspect it's coding style not enviornment.
-
I'm having a problem that I can't pinpoint yet, but I know it's being caused by LR 'cause it happens only when LR is running. I'm on a Mac, and after working in LR and trying to move to a different application via the Dock, rather than opening that application (whether it's already open or not), I get a Finder window with that application hi-lighted. I have to double clik on it to open it, even if it is already open. And then from there my keys start getting screwed up as if my CMD key or Option key were always being pressed down. I have to restart the computer to reset everything back to normal. Very frustrating.
-
I'm having a problem that I can't pinpoint yet, but I know it's being caused by LR 'cause it happens only when LR is running. I'm on a Mac, and after working in LR and trying to move to a different application via the Dock, rather than opening that application (whether it's already open or not), I get a Finder window with that application hi-lighted. I have to double clik on it to open it, even if it is already open. And then from there my keys start getting screwed up as if my CMD key or Option key were always being pressed down. I have to restart the computer to reset everything back to normal. Very frustrating.
[a href=\"index.php?act=findpost&pid=129802\"][{POST_SNAPBACK}][/a]
When you CMD + click on an icon in the dock, the Finder will open a window with the element being selected. So your diagnostic (Cmd key being pressed down) is correct. Either your keyboard is defective or you're using a wrong setting in the Universal Access system preferences or some process (LR?) is stealing all your CPU cyles. Check these first and then it might be interesting to run top command in a terminal window or use Activity Monitor to see what process is monopolizing your Mac.
-
Adobe could, I suppose, ship the software of the option of storing the data in a database server accessible via ODBC or connecting "natively" to a selection of DBMSes (e.g. Oracle, Microsoft SQL Server/Sybase, PostgreSQL). But that means that your two photographers now also have to maintain a DBMS, or hire someone to do so.
I think Adobe's compromise is good enough for the time being, but would of course appreciate the option of using ODBC instead.
[a href=\"index.php?act=findpost&pid=128313\"][{POST_SNAPBACK}][/a]
I've said it before - but I can't remember whether it was in these forums.
Adobe use MySQL for the server part of Version Cue. I wonder if it's possible to extend Version Cue to managing Lightroom's database for it. That will give them a multi-user setup that they already have both client and server for. Those of us who have a Creative Suite 3 suite installed probably already have the server running anyway, so there's no extra management overhead.
David
-
When you CMD + click on an icon in the dock, the Finder will open a window with the element being selected. So your diagnostic (Cmd key being pressed down) is correct. Either your keyboard is defective or you're using a wrong setting in the Universal Access system preferences or some process (LR?) is stealing all your CPU cyles. Check these first and then it might be interesting to run top command in a terminal window or use Activity Monitor to see what process is monopolizing your Mac.
[a href=\"index.php?act=findpost&pid=129829\"][{POST_SNAPBACK}][/a]
Yes.. that's exactly what's happening then... somehow the CMD key is continually being held down, but this only happens after I've been working in LR. I don't know what sequence of events I'm doing in LR to 'activate' this since I don't notice it's happening until I leave LR to clik on an icon for a different application. I can't see it being a preference since it doesn't happen without LR. I'm afraid I don't know anything about a terminal window to try that. Maybe I'll try another keyboard first... I have a spare one of those. I have a feeling however, that its LR stealing the CPU cycles... whatever that means. LR runs quite slow on my Dual 2.0 G5.
-
Yes.. that's exactly what's happening then... somehow the CMD key is continually being held down, but this only happens after I've been working in LR. I don't know what sequence of events I'm doing in LR to 'activate' this since I don't notice it's happening until I leave LR to clik on an icon for a different application. I can't see it being a preference since it doesn't happen without LR. I'm afraid I don't know anything about a terminal window to try that. Maybe I'll try another keyboard first... I have a spare one of those. I have a feeling however, that its LR stealing the CPU cycles... whatever that means. LR runs quite slow on my Dual 2.0 G5.
[a href=\"index.php?act=findpost&pid=130077\"][{POST_SNAPBACK}][/a]
Mike,
Here's a few things that you could try:
- Swap your keyboard for a another one, remove any card reader.
- Create a new user account (Apple Menu>System Preferences…>Accounts) and log-in under this new account. Try to see if LR also "locks" the Cmd key. If the issue is not present (when logged under this new account) then some preferences in your original account are probably responsible for the problem.
- Try to delete (or move to the desktop) the universal access preference file (~/Library/Preferences/com.apple.universalaccess.plist). Log-out and log-in again. The theory is that some key combinations might activate Universal access. It's unlikely but very easy to test.
- Now for the terminal trick. Go into your Utilities folder and open Terminal.app. Open LR and make sure that the window created by Terminal.app is visible (ie resize LR window). Type the following command in the terminal window:
top -ocpu -R -F -s 2 -n30
and press the Return key. This will give you a list of the different processes, sorted by CPU usage. Then, do your stuff in LR and keep an eye on the terminal window. You should see "who" is stealing CPU cycles. When you want to exit the terminal, just click on its window press q and the top process will terminate. Or you can force quit Terminal.app, it won't have any side-effect.
I'm also using LR on Dual G5s (2 to 4 GB of RAM) and while it's not as fast as on new Intel powered Macs it's still OK for the biggest Canon RAW files.
-
Those of us who have a Creative Suite 3 suite installed probably already have the server running anyway, so there's no extra management overhead.
It is plausible that you usually don't have any need to manage the database. However, databases don't completely manage themselves yet, and even automated systems may need tuning.
MySQL also offers a variety of storage backends (http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html) (MyISAM, InnoDB, merge, memory, BDB, cvs, NDB, ...), and in some usage patterns, it pays to switch to something different, especially in multi-user environments.
My guess is that database server management is an NP hard or NP complete problem, so I find it unlikely that there's "no extra management overhead" in the long run, even if Adobe were clever.
But for a few users, you are likely to be essentially correct.
-
Mike,
Here's a few things that you could try:
(...)
- Now for the terminal trick. Go into your Utilities folder and open Terminal.app. Open LR and make sure that the window created by Terminal.app is visible (ie resize LR window). Type the following command in the terminal window:
top -ocpu -R -F -s 2 -n30
Or you could go to the Applications folder, then Utilities, and start the Activity Monitor. Then hit command+1, and click on column headers to sort by them.
-
It is plausible that you usually don't have any need to manage the database. However, databases don't completely manage themselves yet, and even automated systems may need tuning.
MySQL also offers a variety of storage backends (http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html) (MyISAM, InnoDB, merge, memory, BDB, cvs, NDB, ...), and in some usage patterns, it pays to switch to something different, especially in multi-user environments.
My guess is that database server management is an NP hard or NP complete problem, so I find it unlikely that there's "no extra management overhead" in the long run, even if Adobe were clever.
But for a few users, you are likely to be essentially correct.
[a href=\"index.php?act=findpost&pid=130105\"][{POST_SNAPBACK}][/a]
What I was meaning is that the care and feeding of Version Cue only has to be done one, even if Lightroom traffic is added. If Lightroom's database could be handled by Version Cue, I'd expect Lightroom's database to be a separate database on the Version Cue MySQL server, utilising the existing user management provisions in Version Cue.
I run MySQL on my server here, so I'm familiar with the different storage backends. Unless I've missed something, Version Cue doesn't expose the choice of storage engine to the user - I'm 99% certain it uses MyISAM for everything, though maybe InnoDB makes more sense (because of its transactional nature).
David
-
Or you could go to the Applications folder, then Utilities, and start the Activity Monitor. Then hit command+1, and click on column headers to sort by them.
[a href=\"index.php?act=findpost&pid=130106\"][{POST_SNAPBACK}][/a]
Right but if some process is stealing a lot of cycles then Activity Monitor doesn't always refresh its window. I agree that Activity Monitor is more user-friendly.
-
I have found now when importing I can no longer insert a custom text token. I can add the year, date etc, but no custom text. Anyone seen this?
-
I would prefer that adobe adopted the c1's profile color system, with several profiles for each camera model. I like lightroom's camera profiler but I think that C1's system is better.
-
I just noticed that Slideshow does not work properly. It goes back to the first pic after 5 slides or so, while the selection is abaout 80. I tried several collections, all with the same result.
Really annoying!
How do I do a propoer presentation now. this is what I bought the app for (among other reasons).
Is there anything to prevent the program doing this and.. does someone experience the same flaw?
-
I am getting really fed up with the bugs in LR 1.1.
Within one hour Lightroom crashed three times in develop mode.
And the tab and shift Panel hiding does not work. Often the film strip does not reappear, and sometimes the film strip covers up the left panel, sometimes the left panel covers the film strip. It never works at the first go. You have to press shift tab several times.
Waiting for LR 1.2 bug fixes.