Bridge CC slow? Here's a fix for some situations

Like so many of you, I have been having issues with my Adobe Bridge CS6 & Adobe Bridge CC 2014 installations both being very slow (5-10 seconds to open any context menus, folder update taking minutes, etc). Even though my machine was more than capable, something was limiting my Bridge performance.
After experimenting, I finally came up a solution that fixed it for me and others in my company.
It seemed like any action I took in Bridge was making it ping my distant network drives, which added a huge delay to any operations. I realized that this might be stemming from the fact that my company operated a Windows desktop syncing server / domain (no clue what i's actually called..) that would back up our user profiles automatically. By creating a local user and running Bridge through that (even while logged in on my main account), my performance is 1000% better.
Here's what I did:
1) While logged in on my main account, I created a new basic user on my local machine following these guidelines, writing down the username/password that I used for this new user
2) I went into "All Programs", right clicked the Bridge CC 2014 icon, and chose "Send To > Desktop (Create new shortcut)"
3) On my desktop, I right clicked the newly created Bridge icon and selected "Properties"
4) Under the "Shortcut > Target" option, I entered: C:\Windows\System32\runas.exe /user:COMPNAME\NEWUSER /savecred "C:\Program Files\Adobe\Adobe Bridge CC (64 Bit)\Bridge.exe" (Where COMPNAME is is my computer name and NEWUSER is the username of the user I created in step 1)
5) Clicked "Change Icon..." and then "Browse", navigated to "C:\Program Files\Adobe\Adobe Bridge CC (64 Bit)", and chose the Bridge.exe file to use as my new icon
6) Clicked OK to save the shortcut
7) Then I ran the shortcut and was prompted for the password I setup in step 1, which I entered, then hit "Enter" (it should save this from now on, due to the /savecred option we used in step 4)
Like that, my Bridge was back to performing like it did in CS5! As long as I used the new shortcut I created, my Bridge continued to work well. Using the "old" shortcuts wouldn't break anything, but Bridge would run very slowly.
Some things to note:
1) You will have to resetup ALL of your preferences/keywords panel/favorites/windows/etc for this "local" Bridge - none of your actual image files should be affected, though
2) In order to access network drives through this "local" Bridge, you will need to use "Switch User" to login as the user you created in step 1, map the network drives while logged in as that user, and then logout (and this may add the same slowness back to Bridge!)
3) Performing actions on network drives with the "local" Bridge may actually be slower using this method, which is why we now use the "local" Bridge only for local work and the original Bridge for working on a network drive
4) May make your systems administrator mad if they don't want you setting up new users..
5) Plugins/Scripts may need to be edited to work with the "local" Bridge
Here's some background on my computer:
Windows 7 Professional 64 Bit
NVIDIA Quadro K2100M 4GB
i7 4900MQ @ 2.80GHz
I hope this helps other people as much as it has helped us!!

Never should have been a question - sorry.

Similar Messages

  • What is the fix for some applications repeatedly asking permission to accept incoming connections?

    What is the fix for some applications repeatedly asking permission to accept incoming connections?
    On every restart, AutoPairs and Epson Event Manager asks me to reject or agree to allow incoming connections. It is very aggravating and time-wasting. I know other Mac users who have the identical problem with other applications on their Macs.
    Isn't there some way to make my Mac understand that "Yes" means "Yes" once and for all?
    I am presently running Yosemite, but this was a problem with prior OS X versions too.

    This is a comment on why you might, or might not, want to use the built-in Application Firewall.
    The firewall blocks incoming network traffic, regardless of origin, on a per-application basis. By default it's off, and when turned on, it allows applications digitally signed by Apple, and only those applications, to listen on the network. It does not block outgoing traffic, nor can it distinguish between different sources of incoming traffic, nor does it filter traffic by content.
    No matter how it's configured, the firewall is not, as some imagine, a malware filter. If that's what you expect it to do, forget it. All it will do is bombard you with pointless alerts.
    Consider some scenarios in which you may expect the firewall to be useful.
    1. You enable file sharing, and you allow guest access to certain folders. That means you want people on your local network, but not outsiders, to be able to access those shared folders without having to enter a password. In the default configuration, the firewall will allow that to happen. The router prevents outsiders from accessing the shares, whether the application firewall is on or off. But if your computer is portable and you connect it to an untrusted network such as a public hotspot, the firewall will still allow access to anyone, which is not what you want. It does not protect you in this scenario.
    2. You unknowingly install a trojan that steals your data and uploads it to a remote server. The firewall, no matter how it's configured, will not block that outgoing traffic. It does nothing to protect you from that threat.
    3. A more likely scenario: The web browser or the router is compromised by an attacker. The attack redirects all web traffic to a bogus server. The firewall does not protect you from this threat.
    4. You're running a public web server. Your router forwards TCP connection requests on port 80 to your Mac, and the connections are accepted by the built-in web server, which is codesigned by Apple. The application firewall, still configured as above, allows this to happen. An attacker hacks into the system and tries to hijack port 80 and replace the built-in web server with one that he controls. The good news here is that the firewall does protect you; it blocks incoming connections to the malicious server and alerts you. But the bad news is that you've been rooted. The attacker who can do all this can just as easily turn off the firewall, in which case it doesn't protect you after all.
    5. You're running a Minecraft server on the local network. It listens on a high-numbered port. You, as administrator, have reconfigured the firewall to pass this traffic. An attacker is able to log in to a standard account on the server. He figures out how to crash Minecraft, or he just waits for you to quit it, and then he binds his own, malicious, Minecraft server to the same port. The firewall blocks his server, and because he's not an administrator, he can't do anything about it. In this scenario, the security is genuine.
    6. Here is a more realistic scenario in which you might have reason to enable the firewall. Your MacBook has sharing services enabled. You want those services to be available to others on a home or office network. When you're on those networks, the firewall should be off. When you move to an untrusted network, you can either turn off all the services, or enable the firewall with a non-default configuration to block them. Blocking is easier: one click instead of several.

  • [svn:fx-trunk] 10229: Fixes for some transform effects problems.

    Revision: 10229
    Author:   [email protected]
    Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
    Log Message:
    Fixes for some transform effects problems.
    - We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
    - A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
    - A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
    QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
    Doc notes: None
    Bugs: sdk-23177
    Reviewer: Hans
    Tests run: checkintests, Mustella transform effects
    Is noteworthy for integration: No
    Ticket Links:
    Modified Paths:

  • Possible fix for some dlink routers with wifi issues

    I found something online that stated that if you turn off a feature  called WMM that it can help or fix some wifi issues, and on my dlink  dir-268 it seems to be working. Now without this feature turned off I  could connect to my wifi but not much else, with it off I have checked  websites online and also for the first time been able to download a  300MB+ file.  I dont know if it is still used on the newer dlink routers  but it could be at least a temp fix for some.  For my router it is located under the advanced/ advanced wireless settings
    Please post your results if you find this feature on your router, and list what model you have and if it worked so if it fixes problems for enough people mabe we can let dlink know of this find. could help in getting a fix out for the router firm ware or mabe even the android os.

    Wouldn't really be a fix... more a workaround. However...
    Both my Plus account, and a free test account I set up, don't have reliable push... so I think the problem is a little more complex than this.
    While there has been a theory that free accounts work (which I have not experienced), I don't think Apple or Yahoo have ever stated that push was only intended to work for free accounts...

  • [svn:fx-trunk] 11223: * Quick fix for some mxmlcunit failures.

    Revision: 11223
    Author:   [email protected]
    Date:     2009-10-28 07:12:00 -0700 (Wed, 28 Oct 2009)
    Log Message:
    Quick fix for some mxmlcunit failures.
    QE notes:
    Doc notes:
    Bugs: SDK-23865
    Reviewer: Gaurav
    Tests run: checkintests
    Is noteworthy for integration: No
    Code-level description of changes:
    Added null destination check to completeTwoWayBindings().
    Ticket Links:
    Modified Paths:

  • Here's a fix for Safari hanging and taking down the system..

    There appears to be a serious bug in Mac OS X's lookupd which can pull the rug right out from under Mac OS X Tiger. While this bug could possibly be triggered in a number of different ways, there has been a recent rash of reports that have been tracked to some mainstream Web sites such as using links to an adware site This document describes a quick way out of the hang and a simple way to block links to from taking down Tiger again. While this doesn't fix the underlying lookupd bug itself, it prevents Mac OS X from hanging, while allowing you to continue using Web sites like with full Java and JavaScript access enabled.
    The symptoms of this problem are as follows:
    • You're surfing the web and the page you are on fails to completely load.
    • No further pages will load in your browser.
    • You can switch to other applications that may already be running and save any open files.
    • You can no longer launch any additional applications, their icons will bounce in the dock for a while and then they will just stop bouncing.
    • You can no longer use any other Finder functions.
    • You can no longer use command-option-escape to force quit.
    • You can not log out, restart or shut down.
    Apparently these symptoms indicate that a low-level component of Mac OS X, lookupd, has hung. Since lookupd is used by many other parts of Mac OS X, it effectively hangs Mac OS X itself.
    If this sounds like a problem you are having, try the steps in the following link to fix it.
    Mac OS X Tiger lookupd bug & adsonar fix
    Hope it helps,
    [The above link goes to a bug fix on, my commercial website. While neither I nor DreamLight receives any compensation for this fix, or for visits to the site, increased traffic to the site could of course indirectly lead to additional business opportunities.]

    Hi Bee,
    There is indeed "such a bug", though you may be fortunate enough to not be affected. Unfortunately MANY others are affected by this. I spent three days helping track this down (many of those 38 posts were while tracking it down in the Tiger discussions) and find a fix to this and thought that others might benefit by my efforts... By the way it's NOT a Safari bug, it happens in any browser, it's a "lookupd" bug which may be triggered by surfing to certain sites which contain links to "", which if you have JavaScript enabled can hang lookupd and take down your entire system... consider yourself lucky that it hasn't happened to you...
    Here is some background information if you don't believe me:
    Apple Discussions: "Fixes" for lookupd Problems, some via Java Updates
    Apple Discussions: System unresponsive within the last week
    MacFixit Discussions: Progressive Freeze and Network Access under Tiger
    MacFixIt Special Report
    MacFixit Follow-up: Another fix for system-wide freezes when Web browsing
    I only posted this fix to the specific threads where people were having Safari hang, incase it might help them. Forgive me for trying to help them... I thought that was the point of these boards and that was why they started threads about their issues... I'd be willing to bet that this fix will indeed fix many of their problems...
    I also posted one additional new topic here on the Safari board and one on the Tiger board for new readers looking for solutions to the same system hangs they may be getting while surfing.
    If this fix does indeed help any of you other readers, please post back here so that Bee can indeed see that I'm not just posting here to waste my time...

  • Here's the  FIX for one quicktime installation error

    Can't believe this isn't mentioned in here anywhere or in any of the threads on the Web. I got help from the Ubergeeks on the Well, where I should have started in the first place.
    If you can't install because Quicktime won't install (error -3, error 1402 etc.) and you can't get permissions to enter the registry keys...
    Run: regedit
    navigate to the folder mentioned in the error message. For me it was HKEYLocalMachine\Software\Microsoft\Windows\CurrentVersion\Uninstall\Quicktime
    This seems to be the most often-cited culprit.
    Right-click on the Quicktime folder. Select Permissions. Hit Advanced. Click the "Owner" tab. Click on yourself in the lower window. Hit OK.
    Install your software and enjoy.
    This may not fix everyone's problems, but I bet it fixes the vast majority of those that are similar to the one I had, which I spend hours and hours trying to fix before I simply asked someone who knew what they were doing.
    Maybe if the folks at Apple see this, they can, you know, add it to their troubleshooting guide. It's a very common problem.

    In case anyone is reading this thread, I found a fix for this problem. In another discussion thread, a nice person referenced an article at that explains what to do with these kinds of permission errors (1402 and 1406). I followed the instructions and also made the changes to the specific line item I had a problem with. Installation ran successfully although there were a couple of error messages about not being able to unregister a couple of .dlls, which apparently is not fatal to the installation.

  • Here is A Fix for Axiom Pro control surface on Logic 9 on OSX10.10.2

    here's a fix 4 problems mapping Axiom Pro to Logic 9: paste these drivers into Applications/ Logic ...right click...choose Contents/Midi plugins folder:
    Axiom Pro.bundle
    If this cut and paste is non-functional ( after I click 'post')'ll find them on the M-Audio support site...but be sure to select this newer pair of files they created on : 13/09/2011
    it will probably work all the way down to osx 10.7 and maybe 10.6.8 too.
    have a nice day.

    That is not for Apple to fix, check with M-Audio.

  • Here's my fix for Forte installer hang on WinMe.

    Hi all (all those with problems anyway :) ,
    (I tried to post this in the Sun ONE Studio forum
    but always got an error)
    I had a problem installing Sun One Studio 4 Update 1.
    It would keep freezing when it started searching for
    the J2SDK, with the message: "Searching for suitable
    J2SDK, please wait..".
    Well, here's what worked for me on WinMe. Not all of
    these steps may be necessary.
    Install J2SDK to "C:\j2sdk1.4.1_01". First I uninstalled
    it because it was in a folder with a space in the name. I
    heard that was an issue with some OS's.
    Create a text file containing the text "jh=C:\j2sdk1.4.1_01".
    Close it and rename it as "ffj_ce_win32_en.sp". It's appar-
    ently important that its name is the same as the installer,
    except for the "sp" extension of course.
    Put it into the same directory with ffj_ce_win32_en.exe
    ( the Forte installer ).
    Leave the name of the Forte installer as original (instead
    of renaming it to something more descriptive for example ).
    Mine was named "ffj_ce_win32_en.exe".
    In C:\Windows\
    Rename java.exe to java-.exe
    Rename javaw.exe to javaw-.exe
    The important thing here is to make sure their new names are
    unlikely to conflict with the names of any other files that
    might be placed there later.
    Now run the installer again and make it (finally !),
    After I did all the above, it immediately found the correct
    folder (instead of the usual freeze-up).
    Hope this helps someone else too.

    Thanx!!! A frustrating hour and a half later I found your post and it worked beautifully!

  • HT1645 I had about 1:40 run time on my video for DVD and chose "professional" as I didn't need to rush. Got Multiplexer Error message. Found no reason or fix for this situation.  What am I to do to fix?

    This site doesn't seem to get answers.  I typed the problem above, then it asks same question before post. What help is that? Needs to be clearer what it wants from me.  Others seem to have same issues with iDVD's clarity of information.  I have been editing for 12+ years and still can't figure out solutions more than trail and error.

    1:40 - can mean 1 sec 40 frames - or - 1 minute 40 seconds - or - 1 hour 40 minutes
    1 hour 40 minutes is 100 minutes and iDVD only cares about duration
    • Pro Quality encoding - up to 120 minutes (movie + menu) (menu can be 15 minutes or even more
    • Best Performances - up to 60 min. - High quality on final DVD (Can be best for short movies)
    • High Quality (in iDVD08 or 09) / Best Quality (in iDVD6) up to 120 min. - slightly lower quality than above
    Reg "Multiplex Error" - This is a tough one and can have a lot of reasons. Read on
    Multiplexing error is a very complex problem due to many things (long long list following) - one common but not obvious reason is that material on the iDVD menu goes outside the TV-Safe area (or just touching it).
    So first - turn on TV-Safe area and move any object well inside of this.
    Wide screen stretched - usually (as I think) it is due to making a 4x3 movie in a 16x9 wide-screen project OR the other way around. This forces one to on flat-screen TV (or other) set the presenting view right - My has 4x3, wide-screen, zoom and auto-wide-screen and I have to switch this by my remote for some DVD I've made "wrong" way.
    Now my long long list on Multiplex Error
    Multiplexing Error
    PART One.
    Use of strange video/audio material e.g. .avi, .wmv, .mp3 etc.
    I only use.
    Video - StreamingDV (miniDV tape via FireWire) and
    Audio - .aiff (as on audio-CDs) (else converted to this .aiff 48KHz)
    Photo - .jpg (.bmp known problematic)
    Chapters !
    A.    Using strange letters in video project name e.g. +,/; etc. keep to a-z and 0-9 strange letters in project name e.g. +
    as described by Donnyboy69.  Does the title of your project have any symbols or decimal points in it. If so, that is why you are getting the error. I had a project that had a + sign which caused the same problem. I renamed it without the symbol and low and behold, it worked.
    B.    Location of Chapters
    • Can’t be at start or end of movie (Skip first/start one - iDVD sets this by it self. At the End - no need)
    • Not in a transition (or within 2-3 seconds from it)
    Important when from iMovie HD6 or previous - Now also observed when using FCE 4
    PART Two.
    from Robert Modero.
    "Multiplexing Error. Problem during initialization of tracks"
    Simply remember to add subtitles to your Quicktime files and menu buttons.
    Once I did that, I was back in business.
    from Boise Jim
    Do a safe reboot (by holding down the shift key until you see the spinning gear on gray background, then release, then restart when your start-up screen appears).
    I always makes a DiskImage first and test this so that it runs OK
    I use only - Verbatim DVDs
    I use only - DVD-R
    I burn at an as slow speed possibly e.g. x1
    This gives good DVDs
    PART Three.
    Multiplex Error
    Chuck, Chicago 2/7/2009.
    Back again. Here is what I have found to work. I also have and use a LaCie DVD-R/RW DL external drive and a LaCie external hard drive as well. Since yesterday I have tried a few ways to burn a themed iDVD project having four 56 minute movies on it, amounting to 226 minutes onto a DVD DL disc, capacity 240 minutes. Apple tech support really didn't know what to do but gave me a very good tip. I had two options left. Apple tech support's tip was to try disc image. One of the replies on a thread with this subject said not to, but my experience today is good. Put your project onto "Burn to disc image," under "iDVD, file." Yesterday encoding took me 23 1/2 hours. Overnight for iDVD disc image, encoding took 21 1/2 hours (again) while I slept. This morning I tried to copy/burn disc image to a DVD with Roxio Toast 7, and it stopped near the end of the burn with some kind of "error" message. So then I tried Utilities> Disc Utility> Burn icon, and followed it through. Be sure to click the DVD DL drive in the window "Burn disc in.". I had one other problem though. At the end of a 46 minute copy, it started to verify, and at the end of verify it rejected the burn. So I tried again, and when "verify" appeared, I clicked on "Skip." The disc finished burning and is doing fine and well. A long and tortuous process, but at last something works. I made several additional copies using Disc Utility. Best wishes. Chuck, Chicago.
    2. Disconnect any other external devices not absolutely needed.
    e.g. external USB/USB2 hard disks, other FW hard disks etc.
    3 Chapter marks in transitions - minimum 2 sec from
    FROM Bev.
    (Not a 'guy' but I will answer!)
    First, I do not think that mixing wide-screen and standard makes a difference in iDVD.
    Second, you should use a better brand of DVD disk. Also, many of us have experienced fewer problems on playback with DVD-R disks. Recommended brands here are Verbatim, Maxell and Taiyo Yuden. Memorex and TDK are not consistent and may not give you a correct burn. They apparently have fewer layers in the composition of the disk. I have always used Verbatim DVD-R disks and have not had any burn problems.
    Also, choose a slower burn speed, 4x or less.
    Third, to determine if the iDVD project will burn properly, create a disk image file (from within iDVD, go File->Save as Disk Image) and test it. Mount the disk image and then open DVD Player (in Applications) and view your project. If it plays correctly, you can then burn the actual DVD disk from the disk image file using Disk Utility.
    From. Boise, Idaho
    I did everything I've seen suggested, but a friend (who used to be an Apple Genius) suggested that I do a safe reboot (by holding down the shift key until you see the spinning gear on gray background, then release, then restart when your start-up screen appears).
    It worked, and I got a clean burn from iDVD.
    Hopefully this can help other people.
    by dheb0422
    Well, I finally got it, and it was odd enough to post here incase anyone looks this topic up again. Many things were tried, including burning the unedited film, the edited film without titles and chapter markers, abbreviating the chapter markers in case length was the issue (remember the old iMovie used to truncate them when moving to iDVD?). In the process, I noticed that one, and only one, chapter marker was on the same line as the title marker. All the others were on the line above. The only way I seemed able to change that was to clip a few seconds of film. After that last clip, the offending marker took a place on the line above, as were all the others. That run published, compiled completely and burned. That's one for the books.
    One user more writes
    To add my experience with Multiplex Errors using iDVD (7.0.4), I recently created two iDVD projects
    Video from both passed from FCE 4.01 with chapters
    One project worked fine in creating disk image file
    The other gave Multiplex Errors
    I tried suggestions to remove special characters and no chapter marks at beginning, but nothing worked
    Note that I've used iDVD for dozens of projects and this is first time I've run into Multiplex Errors
    Anyway, for problem project, I tried an experiment where I removed all chapters in FCE and passed to new iDVD project
    This time multiplex errors gone
    So had something to do with chapters
    So now I tried numerous experiments to remove individual chapters and try again creating disk image with new iDVD project
    After numerous tries, I was able to narrow problem down to 1 "Bad" chapter mark
    That is, when I left the "bad" chapter in my FCE project and passed to iDVD, iDVD gave multiplex error
    When I removed "bad" chapter mark (and others in), no multiplex error
    As a final experiment, I moved "bad" chapter mark about 5-10 sec's beyond original point and passed to iDVD, the multiplex errors now magically went away and I was able to finally create my disk image.
    I have no idea why this worked, but thought I'd mention here in case someone else runs into similar problem.
    In addition to Bengt's fine advice, burning errors can occur if you have located any of your menu buttons wholly or partly outside of the safe TV viewing area. Go to your main project menu, then click on View/Show TV Safe Area, to check. Drag into the safe viewing area any buttons that are outside the safe viewing area.
    Russ One - suggest this
    Multiplex Error-There was an error during muxing preparation
    One thing that worked for me was to export the video w/o chapter markers as a self contained movie (thereby not loosing the edits & etc). Then make a new FCE project and import that movie into a new sequence and add the chapter markers. I've used "-", "&" and "," with no problem in the chapter names. Removing the markers or exporting without them did solve the problem but renaming them with just numbers 1,2,3....5, did not solve the problem and since this problem seems to happen with with iMovie as well, it would suggest the problem is in the video or audio and in combination with the chapter markers iDVD just can't handle it. The only other possibility is that both iMovie and FCE share the same or similar chapter marker code that some how is corrupting the markers.
    Summary - What to try
    1. Chapters
    • Only A to Z and 0 to 9 in chapter title
    • No Chapter mark at very beginning of movie
    • No Chapter mark in or within 2 seconds from any transition in movie
    2. TV-safe area for buttons (no one outside this)
    3. Safe re-boot
    4. No other external devices connected - that are not needed
    SDMacuser adds to this
    • On #4 ... No ext. devices. Some think this applies mainly to ext. FW. Not the case. Also applies to ext. USB2 as well (not to mention flash drives too).
    Do not leave 3rd party devices / camera / camcorder plugged in unless it is being used with iDvd's One Step process. Certain web cams can trigger this also (especially ones with added features like LED light/s that draw additional power from the FW or USB bus).
    5. Minimum of 25Gb free space on Start-up hard disk
    6. Make a DiskImage first - reduces where problem originates
    7. Trash iDVD pref. file
    8. Make a new iDVD project
    9. Movies in project with same aspect ratio e.g. 4x3 or 16x9
    10. No other programs/applications running during iDVD process. e.g. Internet, screen & energy savers
    Yours Bengt W

  • An easy fix for some iTunes Match glitches

    I found that some cover art would not display on my iPhone, even though the same album would show cover art on my iMac and on the MacMini, from which it was uploaded to iCloud. Other problems occurred, too weird to describe here.
    Investigating the problem, I found that this was caused by some "stuck" sync attempts, trying to download songs from iCloud to the iPhone.
    1. disable iTunes Match on the iPhone.
    2. Delete all music from the iPhone (right swipe, click delete)
    3. some music will remain and can neither be downloaded nor deleted. These are the "stuck" items that cause the problems.
    4. Attach iPhone to iTunes
    5. Select your iPhone in iTunes, then click on "Music".
    6. You will see the "stuck" songs, greyed out. Most of my problematic songs showed up twice or three times, with a non-moving sync indicator in the first column.
    7. delete these songs (select all, right click, delete). I had to do this twice for some unknown reason. Force a sync and check again, to verify that they are indeed gone.
    Once the songs are gone, disconnect the iPhone from your computer. Check the music application. It should display no songs. Now, go to settings and re-enable iTunes Match on the iPhone. Wait until the busy indicator disappears. This may take several minutes, depending on the size of your music library. I assume that this is the time it takes to download cover art and metadata, needed to display the list of albums.
    What is displayed on your iPhone should now match what is in the cloud.
    At this point, I am just guessing, but it seems that the iTunes Match code on the iPhone is not yet 100% bullet proof, and that it can sometimes become confused by a combination of intermittent network connectivity on the iPhone and updates to the iCloud library. Once a sync attempt gets stuck, the affected file seems to be locked and will never display the proper cover art, sometimes affecting the display of the whole album.
    I will keep an eye on this. Probably the code will become more robust over time.

    i got this problem since yesterday.
    at first (a couple of days)  --> i could delete all the songs by a simple sync due itunes....
    --> clean music app
    but now...  everything stuck in itunes match sync
    --> no fix, worked for me
    i thought i had played around with the iphone to much, so i took the ipad...
    and did a VERY CLEAN delete.... close music app --> disable itunes match --> wait for the spinner --> open the musik app --> wait for the spinner --> close music app --> usage --> delete all music --> itunes sync..
    but same problem like on the iphone about 10 songs stuck in itunes match sync... not able to get rid of them.
    on ipad and iphone!  --> strange!
    i tried also to delete all grey songs by (managing music and video manuelly)... after new sync i see the grey songs again.
    i have also noticed that there is a sync problem when you are changing any "Metadata" - cover, ablum, genre... so you have to clean your music app - (fresh itunes match sync)
    so i stuck
    and im not able to sync any new data from itunes match.
    where is the magic? Apple?
    this is like windows ME

  • Wireless Problems: Observations/Possible Fix for Some (No Guarantees)

    Hi All:
    I have been following our wireless problem threads. To a large extent, they revolve around lost connections, weak signals, etc. On my machine, I previously noticed what appeared to be wide fluctuations in signal strength, although I could almost always pick up one distant network that has to be at least 125' away regardless of my apparent signal strength. Also, I never lost my connection. I also have noticed that my Windows notebooks pick up more networks than my MBP, even though some must be farther away than 125'.
    Recently, I had to reinstall all my software. Once resolved I'll explain why and what to look out for. Anyway, before the reinstall, I had done all updates. When I reinstalled, I also did all updates. The bottom line is that I have not seen the wide fluctuations in signal strength since reinstalling. Sometimes I see more networks than I am used to seeing.
    Am I suggesting that you reinstall to eliminate the types of problems mentioned above? Definitely not especially if your problem is pretty minor. However, if your problem is significant, then think about it. Perhaps a greater than expected number of partially bad factory installs accounts for some of our problems.
    I finished my reinstall only about 24 hours ago. I'll continue to monitor and will post back if I begin to see the wide signal strength fluctuations again.

    Nope, thanks. I certainly advocate all trying any possible fixes prior to taking the drastic step of reinstalling. Hope the update works for all. I must of installed it yesterday with a number of other updates. Thus, it wasn't what "fixed" my system. But, it looks like it didn't hurt it either. Both are good to know:) Gosh, and looking at some of the recent posts in this category, I am glad that none of the recent updates hosed anything on my machine. Then, I'd me reinstalling again and being more selective about the updates.
    I have to admit I have been throwing caution to the wind on doing all the updates. I think I'd better go back to my old style of seeing if there are update rumblings before I install them.
    Message was edited by: donv (The Ghost)
    Message was edited by: donv (The Ghost)
    Message was edited by: donv (The Ghost)

  • Permanent Fix For Some FF4 Oddities?

    I just upgraded to FireFox 4, but the minor annoyances are about even with the helpful new features. I've found some about:config fixes for most of the things that irk me, but the problem is that they only seem to last for the current session...when I close FireFox and open it again, it seems as though I need to apply those fixes yet again. And since one such fix is restoring my open tabs whenever I close and reopen my browser, you can imagine how irritating this can be. Is there some way to make these about:config tweaks permanent? What is it that causes them to return to the default each time?
    It really baffles me that FF4 defaults to such bizarre habits that FF3 had no issue with, but that's the beauty of customization. However, if I can't get my personal taste tweaks to stick, well...that's when I really come to take issue with the design team's bizarre new decisions. :/

    I tried everything on that list and it's not working. Though it seems there's only one preference that's being reset now; I think I changed about three settings in about:config and the others seem to be retaining their new values whenever I close and reopen my browser. The one that isn't is keyboard.url - this now defaults to chrome://browser-region/locale/ while I want it to change and stay changed to and it just doesn't seem to want to stick. Is there any reasonable explanation for this happening? I'm tired of using the awesomebar to search for things the easy way I did in FF3 such as "the beatles wikipedia' and having it give me this error when it used to direct me to the wikipedia entry of whatever I plugged in. This is an incredibly annoying change for something that used to just work, and I want my changed setting for it to stick permanently.

  • Here's a fix for slow iPhoto 5.0.4 (burst the beachball!)

    Hi all,
    I've been scanning my back catalogue of photos from about the end of last year. I've never really used iPhoto before, so have no previous with earlier versions. Without a digital camera, I'm forced to use an HP scanner. Owing to the fact that the Cube only has USB 1, this is already not the fastest job in the world, but patience is on my side.
    Despite the fact that I've chosen to put the iPhoto library on my ext HDD, I'm faced with one of the infuriating aspects of the HP scanning application, which is its need to put all scanned input into a folder within /home/documents on my Cube HDD. I only discovered this when I poked around after a system warning that my startup drive was nearly full.
    I think this critical point caused a few permissions conflicts, because ever since, iPhoto has been screwing (that's less harsh here in the UK) my Mac. I got all the symptoms others have been complaining about with regard to slow system performance after having used iPhoto at all. This was true when switching between applications, as well as using applications after having used iPhoto, not to mention during the use of iPhoto itself. The only way to correct this degradation was with a restart, which itself would take forever, because of the slow system performance.
    I had a fairly small library.iPhoto file, so was not assured that the bloat was the same as others had with certain cameras. In looking through the posts, however, I found one which suggested trashing iPhoto 5.0.4 and reinstalling version 5.0. The respondent stated that he/she was at the point of trying something 'as drastic as that'.
    So I got to thinking: if the application iPhoto has caused system-wide damage, then that's the damage to treat. I did an archive and reinstall of OSX and the difference is phenomenal. So many have reported massive amounts of RAM in use, as well as GIGABYTES of swap memory. Have we forgotten the background of the Mac as a graphic artist's tool of choice?
    I'm here to tell you that a properly seated operating system will run iPhoto quite happily with a gig of RAM, and whilst a 450Mhz processor won't put the fear of god into many in this day and age, it's perfectly adequate for image manipulation in iPhoto.
    If you'd asked me this a week ago, I would have concurred that I obviously needed to upgrade to a G5 twin 1.8 or some such animal, but having noticed colleagues in these forums with systems that should eat this kind of workload, I'm at the conclusion (like I'm an expert) that a system reinstall should be at the beginning of the troubleshooting with such huge differences between expected and actual performance.
    Go on, give it a try. What's to lose, apart from half an hour installing OSX?
    Best of luck,
    G4 Cube 1GB RAM/G3 iBook 640MB RAM; AirPort Express/G3 iMac Rev B 640MB RAM/iPod   Mac OS X (10.4.4)   iMac OSX 10.2.8

    Never should have been a question - sorry.

  • Here's a fix for uploaded files that won't play.

    Is this you?  You've found a lot of files were uploaded, instead of matched.  Some of those files might even be on albums where other tracks matched. Sure you want them ALL to match, but meantime, it would be nice if uploaded files would actually play!  Sure, you can see their names, track durations, etc. but if you try to play them directly, nothing happens and if you try to play an album through, when it gets to an uploaded track, it stalls or skips past it.  You've checked the file type and it's an AAC so you figure it can't be a file encoding incompatibility problem and besides, whatever the file type, Apple is red-flagging anything incompatible, tells you it's ineligible, right?
    Guess Again - not all AAC files are produced with the same encoder and some of them, while they'll get past Apple's eligibile/ineligible screening process, probably shouldn't.
    I routinely record vinyl using Audacity and at various times I've used different encoders (not that I knew it until now).  As a result of checking which uploaded files play and which do not, I'm pretty confident of the following. While some AAC files created outside of iTunes might work, those encoded using Lavf52.36.0 will not.  Neither will files encoded using Lavf52.64.2.  There may be others.
    So what's the fix?  The same one recommended for getting files flagged by Apple as ineligible to pass muster.  You need to make an AAC copy in iTunes and swap that for the uploaded files that won't play.
    Here are the steps I use to get it done. You may be able to streamline the process though.
    (1) Turn off wi-fi to prevent iTunes Match from attempting to match any new files until you're good and ready.  If you don't to this, you may end up with files you've just created being flagged as duplicates.
    (2) Select all files in an album that has some bad uploaded files. Select Advanced > Create AAC Version.  (NOTE: I don't bother trying to separate uploaded from matched, just too much hassle.)
    (3) Select one of the files, so you can File > Reveal In Finder. Generally this will get you to the album folder that includes both sets of tracks.  The ones you just created will have a "1" in the file name.
    (4) Create a folder on the desktop and move all the newly created files to it.  Delete the "1" from the file names.  Name the folder based on album title.
    (5) In iTunes, delete the listings for the newly created files.
    (6) Turn on wi-fi and wait for iCloud to reconnect.  Watch the cloud icon - it'll tell you.
    (7) Delete the album from iTunes (You're now getting rid of the copy that was originally uploaded, so be sure you've really got the new AAC files handy to replace them with).  Note you will see an option to delete from iCloud too.  Check it.  You want these files GONE!
    (8) Select Store > Update iTunes Match. If you do a search for the album from an iCloud enabled iOS device (I use Apple TV) after the update is completed, you shouldn't be able to find the album.
    (9) Select File > Add To Library and go get the folder of tunes you created.
    (10) Run Update iTunes Match again.
    (11) Watch the iTunes progress bar. Once the matching process has checked to see if you've added anything to your library, you'll see fresh copies of your songs uploading.
    (12) As another means of confirmation, once several of the songs have uploaded, do an iOS device search for the album. You should  be able to get the album to appear before the upload is complete. You may have to back out of the search and back in to get it to work, but chances are when you first see the album, the song titles will all be grayed out.  Once the update is complete, give it a minute and everything should become available to you.
    (13) Pick a track that wouldn't play before and watch to see if the timer starts to move, followed by music! It is now time to do a little happy dance.
    I know this is a far cry from figuring out what it takes to get songs that should match to actually do so, but that's a whole different ball of wax.

    Thanks this was useful. I have been ripping my audiobooks and I was finding that they would get uploaded to iCloud in the process, which in itself was fine, but then iTunes would not let me change the media type to Audiobook, which is annoying as it effects how iTunes treats the media. Like showing you the skip back 10 seconds button.
    The general outline here helped me work around the issue and change the media type before the media was re-uploaded to iCloud.

Maybe you are looking for