Bugs still in 10.7.4?

Does anyone know if there still any bugs in 10.7.4 because I really want to update for the reopening windows after logging in fix, but is there still bugs in the update??
Any answers will be much appreciated
Thanks
Sebastian

There are no major bugs in 10.7.4 as far as I know. I'm sure there must be some in there somewhere, but they won't be fixed until 10.7.5, which will have its own bugs (none of which are likely to be major).
Don't make the mistake of paying too much attention to reports of problems here. Keep in mind that the only people you hear from in a place like this are the ones having trouble.

Similar Messages

Index with "or" clause (BUG still exists?)

The change log for 2.3.10 mentions "Fixed a bug that caused incorrect query plans to be generated for predicates that used the "or" operator in conjunction with indexes [#15328]."
But looks like the Bug still exists.
I am listing the steps to-repro. Let me know if i have missed something (or if the bug needs to be fixed)
DATA
dbxml> openContainer test.dbxml
dbxml> getDocuments
2 documents found
dbxml> print
<node><value>a</value></node>
<node><value>b</value></node>
INDEX (just one string equality index on node "value")
dbxml> listIndexes
Index: unique-node-metadata-equality-string for node {http://www.sleepycat.com/2002/dbxml}:name
Index: node-element-equality-string for node {}:value
2 indexes found.
QUERY
setVerbose 2 2
preload test.dbxml
query 'let $temp := fn:compare("test", "test") = 0
let $results := for $i in collection("test.dbxml")
where ($temp or $i/node[value = ("a")])
return $i
return <out>{$temp}{$results}</out>'
When $temp is true i expected the result set to contain both the records, but that was not the case with the index. It works well when there is no index!
Result WITH INDEX
dbxml> print
<out>true<node><value>a</value></node></out>
Result WITHOUT INDEX
dbxml> print
<out>true<node><value>a</value></node><node><value>b</value></node></out>

Hi Vijay,
This is a completely different bug, relating to predicate expressions that do not examine nodes. Please try the following patch, to see if it fixes this bug for you:
--- dbxml-2.3.10-original/dbxml/src/dbxml/optimizer/QueryPlanGenerator.cpp     2007-04-18 10:05:24.000000000 +0100
+++ dbxml-2.3.10/dbxml/src/dbxml/optimizer/QueryPlanGenerator.cpp     2007-08-08 11:32:10.000000000 +0100
@@ -1566,11 +1572,12 @@
     else if(name == Or::name) {
          UnionQP *unionOp = new (&memMgr_) UnionQP(&memMgr_);
+          result.operation = unionOp;
          for(VectorOfASTNodes::iterator i = args.begin(); i != args.end(); ++i) {
               PathResult ret = generate(*i, ids);
               unionOp->addArg(ret.operation);
+               if(ret.operation == 0) result.operation = 0;
-          result.operation = unionOp;
     // These operators use the presence of the node arguments, not their valueJohn

IPad Safari Landscape innerHeight/outerHeight bug still not fixed in iOS 7.1.1

iPad Safari Landscape innerHeight/outerHeight bug still not fixed in iOS 7.1.1
No bug in Chrome or other third party browsers.
When are Apple going to fix this bug? It's painful.
more info here:
http://stackoverflow.com/questions/19012135/ios-7-ipad-safari-landscape-innerhei ght-outerheight-layout-issue

Tell Apple not other users.
Use http://www.apple.com/feedback/ipad.html

Users steal ownership of Wiki Articles in Profile Activity -- Is this bug still happening?

Is anyone seeing this Wiki/Profile bug still happening (not just the results of how it happened last year):
Users steal ownership of Wiki Articles in Profile Activity
This is where the wrong person gets credit for the article (they were an editor but not the author) in the Profile Activity tab and thus, they get the Author points.
Still happening?
Meaning that the bug starts happening this year (and not just the issues with it last year).
Thanks!
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

You have a macbook pro too (as noted), does this happen with yours? If apple changed things and it's normal, like as you stated that it was lite so you'd know you're computer is 'on' but I'd like to know for sure if that's what it's supposed to be doing. (nip it in the bud if there's a problem)
I know it isn't sleeping (not pulsing) but since the light is on (steady), it is something I noticed right away. For example, right now as I type this, with the MBP on my desk w/ the cinema display plugged in (w/ a keyboard) and the lid is closed on the MBP, the light is ON right now. Not pulsing, but a steady light. Doesn't seem like it should be, to me. (at least in my view)
Thanks for your reply Josh.

Does the "Warning! Not Enough Memory" bug still exist in Logic 8?

Hello everyone,
I'm wondering if the dreaded "warning, not enough memory" bug still exists in Logic 8. Here is a detailed account of the bug from Logic 7: http://discussions.apple.com/thread.jspa?messageID=767597&#767597
If this is fixed, I'm seriously considering upgrading mid-project! The film score I'm working on has many doubling parts that I'd like to edit at the same time in the matrix editor. However, editing multiple parts in the matrix editor seems provoke the little bugger, and I've already been bitten a few times in this project already. The only solution I've found is to stay clear of editing multiple parts at once (i.e. edit each parts individually, which obviously takes more time) or save before editing and hope I dont get bit.
I would LOVE to hear a report that this bug has been exterminated, and perhaps may upgrade mid project if thats the case.
Thanks in advance for your reply!

Heya,
I'm not familiar with the bug you're talking about. But would, as a fellow film composer, strongly urge you against the mid project switch.
I loaded in LP8 and ofcourse had a look at what it was all about, and it's really really fantastic. It also seems very stable. I fortunately have a side project that I am working on so switched to LP8 for that. Whilst I'm thankful to get my head around a very new approach for logic, I'm also thankful that I have this side project as it has illuminated a multitude of problems that exist with LP8 that would make any scoring process a bit of a headache to say the least. The main one being that if you don't have a very very powerful mac (I'm prepping a really fully loaded 8 core) you are not going to get anywhere near the performance out of Logic as you do with 7. This is a bottom up overhaul and it needs hardware to match. Heck even my 30" cinema display seems cramped and insubstantial on this new version. I would be so bold to say hold off until you have a hearty new mac and at least 8.2 is released IMHO but maybe try and get on it onto a smaller project to familiarize yourself before hand.

IOS6 WIFI bug, still not work now, exhausted,help...

Been like this a week now, tried every possiable way still not any help at all, it can connect the wifi, internet works for 1or 2 minuts then will faile again, changed one router and tried all different settings as still not work, someone told me they don't have this problem they are using different router,maybe it's because IOS6 have sort of confict with some brand router? I am using TPlink, should I keep invest different router and try? Or should I wait for bug fixed?
Apple didn't give any suggestion to customer and time schedule for bug fixed, this is really **** me off...
I will try to visit apple store to check if they can change a new one with IOS5 for me.

They will not change you back to iOS 5. I asked.
I spent almost 1 week trying to resolve this. Reboot the ipad, reboot my router, delete the network, rejoin the network. Nothing seems to work. I called the Apple support, spent 2 days. After trying every single solution (that I've already done before calling.. duhhh)..
They told me to:
- Go to iTunes.Back up all your data, transfer all purchases to your computer. Of course when I tried to transfer all my purchases, they stuck for hours, then crash everything. I had to redo this 3 times. HOURS!!!
- Restore your iPad from your iTunes. It will erase everything in your iPad, then start fresh as new
- Turn off your iPad
- Turn off your router, give it 10-15 minutes, turn on your router
- Turn on your iPad, join the network
Even though finally it looks ok. I am still going to return this iPad and get a replacement. I just don't feel confident with the device anymore. I just bought my iPad less than 3 months, still got the box. The support told me I could swap my iPad, all I need is to see the Apple Genius. So I made appointment, otherwise the Genius won't see you.
I got tons of questions again from the Genius. He said it is my router problem. Basically, I have a crappy router that came from my internet provider. He said that since they opened the store, he only knew TWO people came in with WIFI issue. I told him, all my other devices connect just fine... but of course, they're "oranges" not Apple.
I thought I'll be getting my replacement right away, but no.. Genius had to place an order first, and they will call me again, and I have to make another appointment to pick it up. I wonder why they don't have one in stock. It's the NEW iPad!!! I hope they're not getting my replacement from some kinda refurbished factory.
This is my first purchase with Apple. So far it is not a pleasant experience.

3.1EA2 bug still not fixed - Members of package body not listed in the tree

Hi, I was working today with SQL Developer again and found that this bug is still not fixed even when it was reported more than 1 year ago!!!
I did a quick search and found it here
Package Body Tree not always showing
The problem is when you expand the package specification or package body tree, not all members of the specification/body are listed. This is mostly observable in the package body, but it regards to the specification as well.
Consider this case:
CREATE TABLE EMP (
    ID               NUMBER(6,0) DEFAULT 0,
    NAME             VARCHAR2(20 BYTE) DEFAULT NULL,
    DEPT             VARCHAR2(20 BYTE) DEFAULT NULL,
    FUNCTION         VARCHAR2(20 BYTE),
    PROCEDURE        VARCHAR2(20 BYTE));
CREATE TABLE LOOP (
AREA    VARCHAR2(5),
VALUE   VARCHAR2(2));
CREATE OR REPLACE PACKAGE Test_Package1 AS
gvc_const CONSTANT VARCHAR2(10) := 'xxx';
PROCEDURE Test(p_RC OUT NUMBER,
               p_ID IN NUMBER);
END Test_Package1;
CREATE OR REPLACE PACKAGE BODY Test_Package1 AS
PROCEDURE Test(p_RC OUT NUMBER,
               p_ID IN NUMBER)
IS
BEGIN
--INSERT INTO EMP (ID, NAME, DEPT, PROCEDURE) VALUES (1, 'Tina', 'xxx', 'xxx');
--INSERT INTO EMP (ID, NAME, DEPT, FUNCTION) VALUES (2, 'Jeff', 'xxx', 'xxx');
--INSERT INTO LOOP(AREA, VALUE) VALUES('a','b');
NULL;
END;
END Test_Package1;Compile the package specification and the body. Expand the spec + body in the tree. Uncomment any of the commented lines in the package body and compile the body again. Now expand the package body again and look what is displayed.
Why? It is because SQL Developer handles words "Function", "Procedure" and "Loop" as keywords and according to them does the parsing.
Another case
CREATE OR REPLACE PACKAGE Test_Package1 AS
gvc_const CONSTANT VARCHAR2(10) := 'xxx';
TYPE Loop_rec IS RECORD(
item1   LOOP.AREA%TYPE);
PROCEDURE Test(p_RC OUT NUMBER,
               p_ID IN NUMBER);
END Test_Package1;Compile just this specification and try to expand it in the tree. Again, during parsing the package, SQL Developer takes the word "LOOP" into consideration and fails to parse the specification.
There is exactly the same problem when you declare functions from external dll libraries in package body. Since there is no "END;" in this case, SQL Developer's parser fails...
To me it seems you simply blindly took some keywords like "FUNCTION" and expect there will be some "END;" keyword corresponding with it.
Can anyone have a look at this and finally fix it?

Hi,
Thanks for trying out SQL Developer 3.1 EA2 and providing a clear, reproducible test case for this issue. I logged an internal bug for it:
Bug 13438696 - 3.1EA2: FORUM: CERTAIN KEYWORDS IN PKG BODY BLOCK MEMBERS FROM CONN VIEW TREE
It seems the bug noted in the other forum thread you reference has been fixed, but really had nothing to do with problems discussed either here or there. That fix involved adding an Edit Body... item to the Package context menu in the Schema Browser, not displaying Package members correctly in the Connection view tree.
Regards,
Gary
SQL Developer Team

Old screensaver bug still present in Snow Leopard

This bug has driven me mad in the past (since Tiger!) and I am still getting it on Snow Leopard.
Scenario:
1. Invoke screensaver
2. Wake computer
3. Get password prompt for a split second - (it disappears, like a focus issue).
4. left with a blank screen and cursor. No means of logging in.
5. try to re-invoke screensaver by either putting to sleep via power button or closing lid.
6. Awaken computer - same thing happens.
This doesn't happen 100% of the time but it does require a hard reboot to get out of.
This is one of those bugs that i've managed to live with for a few years but i'm starting to go mad when its still present in the Snowleopard! (pls excuse my venting!)
Obviously the easy issue is to disable the screensaver password - but you'd think this would be fixed by now - Or am I just being stupid and missing something obvious?
Cheers,
Steve </vent>

I am experiencing both your size issue and a different bug concurrently.
I also get the 'white' image bug if scrolling through images and then quickly backtracking to a previous one. Then that image will remain white until I close quicklook and reopen it on a different file. Reopening on the same file still results in a white image. Happened under 10.9 and is happening to me under 10.9.2 on a Macbook Pro, 2010 iMac and non-apple branded um, mac. Size and file type don't matter.
I get a similar log entries once in a while but the backtracking white image thing doesn't cause quicklookd to spam any console info that is searchable in the console.
Removing quicklook plugins, clearing it's cache and whatnot didn't do anything.
*EDIT*
http://support.cocoatech.com/discussions/announcements/6-quicklook-issues-pf-652
Apparently my 'snap back' issue is was caused by the version of Path Finder 6 I was running on those machines.
It would seem that there are a number of other issues with the 10.9 quicklook API. I guess I'm going to wait and hope it gets fixed.

Lookupd bug still an issue???

Hi there!
Is it true that the old problem of the crashing lookup demon is still not patched?? At the first glance I only found discussions about this issue nearly a year ago.
I'm experiencing some of the problems
- network connection going down (but can be "reanimated" by disconnecting the cable for a few seconds)
- applications suddenly hang one after the other
- bad system.log entries like "lookupd hanging up"...
After some research I discovered some ways that should be help:
- install unlockupd
- disable CrashReporter
And indeed: A lookup-Crash now doesn't kill ALL my applications any more. But I realize that there is still a problem, because my network is going down.
In this case I normally try to shutdown all applications manually to avoid any data loss and try to reboot.
The problem is that it doesn't always work. Either it's because of the lookupd bug or my iDisk mirror image is somehow corrupt forcing the MirrorAgent to hang. Anyway: It's annoying...
Just yesterday I had to power off my Mac with the result that I found "HFS: removed 139 orphaned files" in my system.log and the systems looks "different" (meaning: some preferences were corrupt). As the times before, a check with disk utility after the crash found no errors at all. So I had to restore my home directory... again...
Is there a way to get rid of the lookupd bug? Or some maintenance stuff one can do to avoid crashing the demon? It's still annoying and reminds me of the Windows crashes in the old times. :-((
Thank You at least for listening...
Martin
PowerBook G4 Mac OS X (10.4.8)

This bug has indeed been around for far to long. It impacts certain iMac's using ATI video cards and we're working closely with Apple and ATI to address it. I'm hoping we see a resolution on it soon.
Chris

Weird Bug Still On Going

I have recently upgraded my home PC with new motherboard, CPU and RAM. Since then i have a weird bug that i cant seem to get my head around to fix.
Basically whenever i am in the metro UI start screen, at random times when i left or right click it will hang my system with NO BSOD. My monitors go to sleep my PC is still on and the fans are still on as well as the LEDS andmy keyboard and mouse but
they are frozen.
I cant remote onto it from my logmein account to see what is going on.
I have tried the following:
change power options to disable sleep timeout
re installed fresh windows 8 then update to 8.1
changed my main HDD and re installed windows 8 then updated to 8.1
installed and updated all of my hardware (mouse, keyboard, motherboard chipset)
It is very random and frustrating as i am an IT engineer and i cannot figure out what is going on. I have estimated that my system at peak load pulls around 590W of power and i have a 750W Modular Gaming PSU.
I also have a NVIDIA GTX 295 Pre watercooled.
I really cannot think what this could be and would really appreciate some guidance/assistance with this. In my opinion I do not think it is to do with my PSU or GPU as it is ONLY doing this in WINDOWS 8.1 METRO Screen and nowhere elese not even the metro
screen in windows 8 before I update to 8.1
Many thanks in advance for this.

try to check whether this issue also happen in safe mode or BIOS, if still hang there than high possibility hardware compatibility or HW issue itself
try to remove all 3rd party HW like printer, LAN cable, usb dongle and do power cycle to isolate 3rd party HW compatibility or HW issue
if you suspected this is windows issue, I suggest create 1 partition and installed windows 7 or any others OS to proof that this is not HDD or any other HW related issue
because you already reformat your OS, I suggest try to troubleshoot from the hardware side first (HDD, RAM, connection cable SATA and power etc)

RGB printing bug still not fixed with 6.0.4

I guess I should not be surprised.
After three major releases of OSX and 20 updates and two major version and 8 updates of Indesign the monitor profile is still being introduced into the RGB printflow.
What the HELL does it take to get this bug fixed?
And, yes I know you can use "Print as Bitmap" or "Fast Graphic Process" in the Canon drivers to work around this problem.
Just maybe if IDCS5 uses the Cocoa print path that PS and LR now use it will be fixed then.

Anyone know if CS5 has fixed/addressed this problem?

PDF From MS Word 2010 Reported Bug Still Exists

I need to create a PDF file today that contains images in a MS Word 2010 document. There is a bug in Acrobat XI Professional that I reported months ago. This bug is still here, and now I need help. Can anyone tell me what I can do to fix this issue?
Here is what happens, and I just reproduced this problem I found awhile back. As I stated, I did report it, but this issue is still here!
I am creating a user guide for software. I insert BMP images that are screen shots. On any page where a BMP image exists within Word, the resulting PDF document does not allow selecting of text in Acrobat Reader XI. The selection goes totally insane and highlights random text through the entire page. This is a software defect for certain.
My question is can I easily fix this with minimal time? I had to fix this last time by removing all images from MS Word and instead pasting the image in Acrobat XI. When I do this, selecting text works. The problem with this bug work-around is that this take lots of time (that I do not have).
Help please???

I found something even better. There is a non Adobe PDF creator on my office computer that correctly creates a PDF. The issue is within PDF creation, because I am using Acrobat Reader XI and selecting text with no problem at all.
I did not have to change a thing other than not use Adobe Acrobat Professional to create the PDF. The software that works correctly where Adobe's own fails is called PDF Xchange Driver by Tracker Software Products LTD.
...and as I already stated, I reported this issue many months ago...

Old kexi bug still exists?

So I was looking into using something other than phpMyAdmin for editing my databases, so I looked into kexi. When I used the import "Structure and Data" option, it just populates the tables with empty values.
After some searching, I found that this use to be an issue a while back: Problem and Resolution.
Can anyone else confirm this as a still-existing (or reoccurring) bug?
Or, am I just messing something up along the way?
Thanks.

I hope someone can help me... it is very important and i am desperate for answers (BUMP)

8.0.2 horrendous bug still exists!!!!!!!!!!!!!

The effects and sample caching bug is horrendous in my opinion. It's been there for years. It wastes huge amounts of my time. While there are some things you can do to minimize these glitches, there are NO 100% reliable work arounds. If you work in Logic and want a professional result you absolutely must listen to the finished bounce very carefully for glitches. These glitches come in many forms and will often times only be noticed after you receive the finished product from the mastering house.
The main culprits are:
1. Reverb and delay tails. If you have reverb or delay on a track and you stop playback and move your position, the reverb or delay will begin where it left off.
2. Samples. For example I often replace kicks and snares with samples. When I go to start a bounce random samples will play at the beginning of the track.
3. Clicks from compressor and EQ plug ins. These are less obvious, but generally mastering brings them out loud and clear after it's too late.
Keep in mind that these glitches don't generally happen until a split second before a region starts. That means it is very common for them to happen in the middle of the song. Starting and stopping playback a few times does NOT completely clear the cache.
It's a total craps shoot and the most embarrassing, time wasting aspect of Logic.
I really wish I could trust Logic to give me a bounce that is exactly "as expected."
I just sent a bug report... I encourage you all to do the same. They are obviously working on stuff and I think it's our responsibility to make it a priority for them.
http://www.apple.com/feedback/logicpro.html

Hi Rohan,
I meant to begin my last post "with all due respect". I read you all the time, you are always well informed, plus you came up with the 8.02 key command fix/discovery..
Rohan Stevenson1 wrote:
hi pancentre,
no mate that's not correct re logic flushing the buffer. that is actually my point - it can't, not the way the audio engine is designed - god, but my memory is sketchy on this - i remember getting the ins and outs of this a long time ago...
Right, I understand exactly what you're saying, this is indeed the way Logic works... my point was it's an archaic system that was devised at a time when computers had 1/1000th the processing power we have now. There's no need for such great efficiency, plugins can be kept partially active, this is how 9 out of 10 DAWs flush the buffers, the plugin is always active to some extent.
one of the things that makes logic efficient is the way it handles plugs - it doesn't process them the whole time - only when there is sound to process.
Agreed, see above. I think this is related to a couple of Logic's other quirks.
Efficiency in one area is causing less efficiency in other areas, the overload messages. What happens when a song is playing and it comes upon three regions with a couple of space designers and an instance sculpture? Instead of these plugs being partially active and using a little processor, they all become active at once and often cause a spike... ie; system overload or other kind of glitch.
it is the 3rd party plugs that have to flush its own audio buffer - its not something logic can effect without changing the way it works to become much less efficient.
but if you were to call it a 'logic bug' then i would find it hard to disagree with you:
Well, I guess it's hard to say but it seems like Apple came up with a workaround for Logic's behaviour and then asked everyone else to do the same. Until Apple version 7.xx Logic's plugins used to do the reverb tails and all other manner of little tics & glitches.
There's still a couple of Logic's plugs that aren't all the way compliant.
pancenter-

9.0.0 horrendous bug still exists!!!!!!!!!!!

Just reintroducing my pet peeve with Logic in general. It's the one thing that frustrates me most about Logic and it still persists after many many years. Here's my original post from 8.0.2:
http://discussions.apple.com/thread.jspa?threadID=1531297&start=0&tstart=129
The effects and sample caching bug is horrendous in my opinion. It's been there for years. It wastes huge amounts of my time. While there are some things you can do to minimize these glitches, there are NO 100% reliable work arounds. If you work in Logic and want a professional result you absolutely must listen to the finished bounce very carefully for glitches. These glitches come in many forms and will often times only be noticed after you receive the finished product from the mastering house.
The main culprits are:
1. Reverb and delay tails. If you have reverb or delay on a track and you stop playback and move your position, the reverb or delay will begin where it left off.
2. Samples. For example I often replace kicks and snares with samples. When I go to start a bounce random samples will play at the beginning of the track.
3. Clicks from compressor and EQ plug ins. These are less obvious, but generally mastering brings them out loud and clear after it's too late.
Keep in mind that these glitches don't generally happen until a split second before a region starts. That means it is very common for them to happen in the middle of the song. Starting and stopping playback a few times does NOT completely clear the cache.
It's a total craps shoot and the most embarrassing, time wasting aspect of Logic.
I really wish I could trust Logic to give me a bounce that is exactly "as expected."
I just sent a bug report... I encourage you all to do the same. They are obviously working on stuff and I think it's our responsibility to make it a priority for them.
http://www.apple.com/feedback/logicpro.html

lwilliam wrote:
It's an inexcusable bug. It's one of the few reasons left why I can't use it in front of clients. How embarassing to have to trim the beginning of a bounced file to get rid of a reverb tail!
1. If it were truly an AU-only bug, then wouldn't Cubase also exhibit the same behavior? I've not heard of Cubase users complaining about that.
2. If were really an plugin not following the AU spec, then why do these 3rd party plugins pass the validation test?
Since I go way back with this... I can tell you this behavior started with version 4.xx when Emjk adapted Logic to use VST instruments. At that time all of Logic's plugins (reverbs...internal synths) exhibited these problems as well as 3rd party VST. it was a KNOWN issue and had to do with the manner in which Logic handles buffers and and unhooks plugins/AU from the CPU at stop. Plugins, VST & AU become inactive with data in their buffers. It was never a problem with any other DAW as the plugins are kept active long enough to empty the buffers. The onus being put on the plugins was added to the AU spec at a later date to cover Logic's behavior. (which really P.O.'d some plugin developers, so much so that some won't even fix what to them is not their problem.)
I don't know about the latest version of Garageband but interestingly enough, it doesn't exhibit this problem, or if it does, nowhere near as bad as Logic. It was something that was "fixed" in Garageband.
I dislike when companies try and rewrite history, as mentioned, this was a
-known- issue. It was discussed between users and programmers... (back in the day).
over and out on this.
pancenter-

Lightroom 1.2: XMP-bug still present and some other things

* I just upgraded to 1.2, but the XMP-bug is still present. When I turn on autowrite XMP LR starts using 50% (1 of 2 cores) of my CPU for quite a long time (15+ minutes) after startup. During that time the interface is somewhat sluggish (probably because of the lack of multi threading).
This behavior was also present in LR1.1. Turn off autoxmp and the cpu-usage will drop to 1-2% within a few moments of starting LR. Turn it on, and it will use your cpu for quite a long time (29.000 photos in my DB).
* One other thing I still notice: when using identity plates for printing, the identity plate doesn't rotate with the photo when switch from a landscape to a portrait photo (auto rotate is on to make things a lot easier). The print module is one of the greatest things in LR, but this still annoys me)
* Decent support for multi core CPU's is still lacking it seems. I have to run two export batches simultaneously to get my CPU to 100% cpu usage. Maybe it's an idea to split one export batch into several smaller ones so the can be processed at the same time using both cores.

1.2 fixes a bug in the auto-write mechanism that severely effected the performance of auto-write when files with changes were offline. Unfortunately, we didn't have time in the cycle to drastically enhance performance of the XMP auto-write mechanism for making large batches of changes or toggling the option on and off. The Lightroom team is aware of these issues and is working to resolve them for a later release.
The wording of the download page is pretty obscure. For a more accurate, detailed review of the changes in 1.2, please refer to the blog post at http://blogs.adobe.com/lightroomjournal/ . For a better understanding of ways to use the auto-write mechanism in the interim, check out my post at
Dustin Bruzenak, "Performance & Auto-write XMP" #, 10 Jul 2007 8:29 am
Dustin Bruzenak
Lightroom Engineering

Bugs still in 10.7.4?

Similar Messages

Maybe you are looking for