Nudge function after Pro App update 4.0.1

Can anyone using one of the new MacBook Pros (2.2 or 2.4GHz) verify that the nudge command (Apple key + Arrow) is or is not working after installing the Pro Apps update 4.0.1?
Mine is not, and I'm trying to find out is it's the update or part of the ongoing MCP/Motion problem or something specific to my system.

Thanks Bert for confirming this for me.
Txiquim, I believe you have the MBP software update 1.0 installed - yes? That is probably why yours is working - of course you're crashing all the time though because of this (per your posts). Also, you're probably using a different keyboard layout (other then USA, Mexico perhaps?), which is why your nudge command isn't Command+Arrow.

Similar Messages

  • FCPro will not open after Pro Apps update

    Did recommended software updates at the end of the day yesterday. Quicktime, Pro App Support, Pro App Update, Audio Update, Security Update and Compressor. (Also iTunes, AirPort and Security 2007-07.
    Now Final Cut just freezes on the splash screen. Tried to trash the prefs, but FCP does not even load enough to see that the earlier prefs are gone.
    Am frustrated that I have again just taken Apple's word that an update will make things better, not worse.
    Any suggestions, gang? My client is not as patient as we are.
    -robert

    Thanks, Randy and Ed. I repaired permissions and restarted twice and the issue disappeared. For whatever reason the Pro Apps update only crippled iDVD and FCPro for five hours, then quietly went away.
    The prefs-trashing and permissions-repairing you suggested are what my dad used to call "kicking the mule"... there is no one reason that banging the side of the TV or resetting an unrelated thing on a computer helps it any more than giving the mule a kick, but sometimes that's all that is needed.
    That said, no actual mules or any other animals were harmed in the correction of this glitch. I may have to kick my client though.

  • Invalid Serial After Pro App Update 2007-02

    After updating all FCS2 apps today, it asked for a serial # which I provided again and was invalid. I trashed the text file in pro apps and it still remains a problem. My G** I have a project due tomorrow ! APPLE!!!!!
    What can I do ?

    You're in Miami....call a rental house and try and get a tower.
    Otherwise you'll have to reinstall everything, I think. Might be able to save time by just installing the apps and skipping all the motion, live type, and audio content.

  • Uninstall an OSX or Pro Apps Update

    Hi,
    I would like to be able to reverse an update after installing it because sometimes that update creates a confilct with other applications running, such as in my current case.
    I installed a pro apps update and now postgresql will not start...
    Is there any way, without using time machine, to back out of an update?
    I usually use time machine, but I'm waiting for a thunderbolt to e-sata adapter.
    Please let me know.
    The errors I am receiving are:
    could not connect to server: No such file or directory (PG::Error)
              Is the server running locally and accepting
              connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
    And
    Could not start on port 5432
    Thanks in adavance.
    Brian McDonough

    That's a great idea.
    I usually have backups to revert to, similar to the solution you're talking about, but, for once, I am working on the "razor's edge" to convert my external drive system to thunderbolt from esata.
    I don't think it's possible to back out of software updates, now handeled through the App Store in Mountain Lion and I think you are confirning that with your answer, but is there some way to make that a feature request?
    I have another laptop running an older version I can use in the meantime, but how easy would it be to back out of the software update I just executed if it were a feature of the App Store?
    Do you know how to make feature requests?
    As it stands, I will probably have to wait for a patch from postgresql in order to continue to use my new laptop as a programming environment.

  • Pro App update 4.0.1 - Macbook Pros and Motion 3 crash

    Anyone know if this Pro App update that came out today addresses the issue of Motion 3 crashing on the new Macbook Pros? Anyone know if it's safe now to run the Macbook Pro Software Update 1.0?
    There's no new information on the article page:
    http://docs.info.apple.com/article.html?artnum=306038
    And of course, the information on the Pro App Update page tells us NOTHING about what it actually fixes.
    After the major problems the MBP software update caused, I'm extremely hesitant to run any updates as I cannot afford to have to wipe my hard drive AGAIN due to a bad update. YUCK!
    I'd try it myself, but being in the middle of a couple of projects, I just can't afford to take the risk.

    OK, just got off the phone with tech support. This Pro Apps update does NOT address the Motion 3 crashing issue.
    MBP owners, still should NOT RUN THE MBP SOFTWARE UPDATE 1.0.
    Good news is that I was told that the issue (Motion crashing due to the new video cards and OpenGL) has been heavily escalated.

  • Ipad screen is white. Restored it on iTunes. Press home and on switch goes black then back to white with no logo at all. Can't get past the white screen. This happened after running app updates. 16GB OS 7.1.1

    The ipad screen is white. Holding buttons didn't work so I restored it on iTunes. When I press home and on switch, the screen is white,  goes black then back to white with no logo at all. Can't get past the white screen. This happened after running app updates. Is there any fix besides going to Apple store? In iTunes on computer can see what is on there. 16GB OS 7.1.1

    FORCE IPAD INTO RECOVERY MODE
    1. Turn off iPad
    2. Turn on computer and launch iTunes (make sure you have the latest version of iTune)
    3. Plug USB cable into computer's USB port
    4. Hold Home button down and plug the other end of cable into docking port.
    DO NOT RELEASE BUTTON until you see picture of iTunes and plug
    5. Release Home button.
    ON COMPUTER
    6. iTunes has detected iPad in recovery mode. You must restore this iPad before it can be used with iTunes.
    7. Select "Restore iPad"...
    Note:
    1. Data will be lost if you do not have backup
    2. You must follow step 1 to step 4 VERY CLOSELY.
    3. Repeat the process if necessary.

  • FYI Pro App update for Logic Studio

    The lastest Pro App update is available from Apple. This includes Final Cut apps and Logic Studio.
    Cheers,
    RealDave

    RealDave wrote:
    Yes, it may pertain only to the Final Cut suite , and since Compressor is part of both suites it might only involve Compressor. However, I'm in the technology field by trade and always find that even when something is not specifically mentioned in the "read me" file, that doesn't mean it won't apply to a broader spectrum.
    I suppose this is true.
    I just installed it on my machine and now my life is perfection.
    Any notable improvements you can report?
    -droo

  • 10.4.7 update fine - prompted for Pro Apps Update 2006-01 again

    I ran the 10.4.7 Update without a hitch. Everything works fine. However, when running SU again to see if 10.4.7 is a multiple update, SU now wants me to install the 2006-01 Pro Apps update again. I'm sure I installed it prior to 10.4.7. This makes me nervous. Any advice anyone?
    MacBook Pro

    Can you mount the drive from another computer via FireWire Target Disk Mode? then repair the drive; delete cache folders etc.
    From single user mode you could also try to rename
    ~/Library/Preferences to another name.
    MacFixit: Repairing Permissions
    General Troubleshooting permissions
    Troubleshooting Mac OS X
    Insufficient disk space or RAM
    Installing Software Update
    Advice on Archive & Install

  • HT1766 ipad no longer functions after accepting an updated version of "Hayday"

    ipad no longer functions after accepting an updated version of "Hayday"

    Unfortunately it was a blinding flash of the obvious that fixed my issue...
    Simply rebooting the iMac brought it back to life.
    Duh.
    I assumed that since Apple usually forces reboots after updates if they are required that this didn't require one, apparently it did.

  • Pro App Update Problems

    Has anyone else installed the latest Pro App Update and run into major slow downs? Ever since I installed the last update, Motion has slowed down to about 10% of it's normal speed. In fact when I do a ram preview (1 replicator 1200 points) I only get 2 frames a second playback. Any guesses?
    I sure hope this isn't what the upgrade has in store for me.

    Yeah I am serious. Here's a little personal history. I bought a G4 400 MHZ Dual processor Mac and I had 800 megs of ram installed (from the Apple Store). So two years later when I decided to buy FCP 3 I looked on the side of the box, it's system requirements stated a 500 MHZ G4 single or dual with 384 megs of ram for real time effects. So I thought "well heck, I've got a dual processor system with 800 megs of ram I should be able to get real time playback." I later found out that it wasn't so. Apple had included a processor check in the app that would NOT allow real time playback unless your system was 500 MHZ. Some guy in Denmark discovered this and posted a hack that would remove the processor check and allow people running slower G3 systems to get realtime effects. Apple promptly sued and shut him down. At lease that's what I read (at the time) on the internet. I never hacked my version (not smart enough) and I didn't want to destroy my copy of FCP.
    So yes I am serious. Apple is in the market to sell computers and if they can convince you that you need the latest greatest system to survive they've done their job.
    Also when Apple came out with the G5s they touted the fact that they were the first 64 bit processor on the market. Now I'm smart enough to know that a 64 bit processor means nothing without the apps being rewritten to support 64 bit. But I took a gamble because I thought the life of the G5 processor would be long enough to allow the software companies to catch up. One year later Apple announced they're moving to the Intel chips. Well what software company in their right mind is going to rewrite their software for an older processor. So my dreams of 64 bit speed were dashed.
    Don't get me wrong, Apple still has the best OS out there. But do I trust them to do the right thing anymore? No it's all about the money. And if I'm wrong about the dane hack I'd be happy to have someone set me straight about it.

  • Final Cut Studio Fail After Pro Application Update 2010-1

    Final Cut Pro crashes when loading project.
    Motion crashes when loading project.
    Compressor won't allow me to "submit" my batch from the 'name batch' stage.
    I didn't try DVD Studio or Color.
    Problems started as soon as I updated. Anyone else have similar problems? I tried dumping my system preferences but that didn't help. I haven't modified or customized FCS at all, I don't have any unusual plugins - I hardly even set up customized window configurations.
    Using latest Final Cut Studio (MB642Z/A)
    Final Cut Pro 7.0
    Compressor 3.5
    Motion 4
    Running OS X 10.6.2
    3.06 GHz Intel Core 2 Duo, 21.5" iMac
    8 GB 1067 MHz DDR3
    Thank you for any feedback. If others have similar problems, I can wait for next update (hopefully soon) otherwise I have no clue where to start.
    --Doug

    I should have known better, but new to the mac....dealt with death blows like this for a while....
    Process: Final Cut Pro [1209]
    Path: /Applications/Final Cut Studio/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
    Identifier: com.apple.FinalCutPro
    Version: 7.0.1 (7.0.1)
    Build Info: FCPApp-910141802~4
    Code Type: X86 (Native)
    Parent Process: launchd [124]
    Date/Time: 2010-03-25 01:06:44.195 -0500
    OS Version: Mac OS X 10.6.2 (10C540)
    Report Version: 6
    Interval Since Last Report: 3062 sec
    Crashes Since Last Report: 9
    Per-App Interval Since Last Report: 1939 sec
    Per-App Crashes Since Last Report: 8
    Anonymous UUID: 2739307A-393B-4135-A387-644DE9430D3D
    Exception Type: EXCBADACCESS (SIGSEGV)
    Exception Codes: KERNINVALIDADDRESS at 0x00000000390302fe
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread
    Thread 0 Crashed: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x90f1bb51 tinymalloc_from_freelist + 741
    1 libSystem.B.dylib 0x90f1ab03 szonemalloc_shouldclear + 297
    2 libSystem.B.dylib 0x90f1a988 malloczonemalloc + 81
    3 libSystem.B.dylib 0x90f18a58 malloc + 50
    4 libstdc++.6.dylib 0x91105617 operator new(unsigned long) + 36
    5 com.apple.motion.TextFramework 0x24c54dab TXTextObjectRender::getHelium(LiAgent&) + 667
    6 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
    7 com.apple.motion.TextFramework 0x24c13829 TXTextLayout::buildHGNodeForFace(PCPtr<TXTextObject>, OZRenderParams&, LiAgent&, TXHeliumGlyph*, unsigned int, bool, PCMatrix44Tmpl<double>&, PCMatrix44Tmpl<double>&, PCMatrix44Tmpl<double>&, PCMatrix44Tmpl<double>&) + 4985
    8 com.apple.motion.TextFramework 0x24c455ec TXCachedGlyphRender::getHelium(LiAgent&) + 940
    9 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
    10 com.apple.Lithium 0x248c4cda LiImageSoftClip::getHelium(LiAgent&) + 74
    11 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
    12 com.apple.Lithium 0x248c4cda LiImageSoftClip::getHelium(LiAgent&) + 74
    13 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
    14 com.apple.Lithium 0x248e0692 LiPolygonInstance::makeNode(LiClipSet const&) + 1682
    15 com.apple.Lithium 0x24911111 LiRenderInstance::collectGeode(LiGeode*, LiCollectState&) + 929
    16 com.apple.Lithium 0x24911f01 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 1521
    17 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
    18 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
    19 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
    20 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
    21 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
    22 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
    23 com.apple.Lithium 0x249123a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
    24 com.apple.Lithium 0x249123a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
    25 com.apple.Lithium 0x249123a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
    26 com.apple.Lithium 0x249144b5 LiRenderInstance::collectPolygons(LiSceneObject*, LiPtrArray<LiPolygonInstance>&) + 1509
    27 com.apple.Lithium 0x24914d35 LiRenderInstance::collect() + 949
    28 com.apple.Lithium 0x24914f91 LiRenderInstance::buildHeliumGraph(LiAgent&) + 529
    29 com.apple.Lithium 0x24915a3e LiRenderInstance::getHelium(LiAgent&) + 270
    30 com.apple.Lithium 0x2486bac3 LiRenderer::getHelium(LiAgent&) + 51
    31 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
    32 com.apple.ozone.framework 0x238c4ebe GLRenderer::getSceneHeNodeFromLiWorld(OZScene*, OZSceneSettings const&, OZRenderParams&, PCPtr<LiGroup>, HGRenderer*, int, int, double, double, long*) + 2254
    33 com.apple.ozone.framework 0x238c96e0 GLRenderer::getFrameNodeForSingleTime(OZScene*, OZRenderParams&, HGRenderer*, double, double, long*) + 880
    34 com.apple.ozone.framework 0x238ca2ae GLRenderer::getFrameNodeIncludingFields(OZScene*, OZRenderParams&, HGRenderer*, long*) + 990
    35 com.apple.ozone.framework 0x238ca894 GLRenderer::getFrameNode(OZScene*, OZRenderParams&, HGRenderer*, long*) + 164
    36 com.apple.ozone.framework 0x238ce817 GLRenderer::render(OZScene*, OZRenderParams&) + 2583
    37 com.apple.ozone.framework 0x2396fdd3 OZXGetFrame + 2755
    38 com.apple.ozone.framework 0x23972406 OZXGetFrameAsTexture + 86
    39 ...uartzComposer.QCMotionPatch 0x0d949c96 UserHasCancelled + 17982
    40 ...uartzComposer.QCMotionPatch 0x0d9467ca UserHasCancelled + 4466
    41 ...uartzComposer.QCMotionPatch 0x0d946428 UserHasCancelled + 3536
    42 com.apple.QuartzComposer 0x91730396 -[QCPatch(Private) _renderAtTime:arguments:] + 111
    43 com.apple.QuartzComposer 0x91739334 -[QCContext renderPatch:time:arguments:] + 809
    44 com.apple.QuartzComposer 0x91738f9c -[QCGraphicsContext renderPatch:time:arguments:] + 96
    45 com.apple.QuartzComposer 0x91737f53 -[QCOpenGLContext renderPatch:time:arguments:] + 565
    46 com.apple.QuartzComposer 0x91737d16 -[QCPatch(Runtime) render:arguments:] + 92
    47 com.apple.FinalCutPro 0x005196e9 RenderQCPatch + 1671
    48 com.apple.FinalCutPro 0x00515c63 FCPQCMainEntry(long, long, KGDictInt*, void*) + 10083
    49 com.apple.FinalCutPro 0x002ea236 pKGRunTransition(KGDictInt*) + 2182
    50 com.apple.FinalCutPro 0x0045b5dc EffectRender(XXGlobals*, EffectTree*, long, long, Output*) + 5894
    51 com.apple.FinalCutPro 0x0045e909 RenderFXTreeNode(XXGlobals*, EffectTree*, long, unsigned char, KGQTCanvasFormat, long, Output*) + 1497
    52 com.apple.FinalCutPro 0x004614fb DecodeEffectFrameN(XXGlobals*, EffectTree*, long, unsigned char, Output*, bool*) + 2933
    53 com.apple.FinalCutPro 0x004609ff DecodeEffectFrameN(XXGlobals*, EffectTree*, long, unsigned char, Output*, bool*) + 121
    54 com.apple.FinalCutPro 0x004609ff DecodeEffectFrameN(XXGlobals*, EffectTree*, long, unsigned char, Output*, bool*) + 121
    55 com.apple.FinalCutPro 0x00461893 DecodePipeTree(XXGlobals*, Output*) + 633
    56 com.apple.FinalCutPro 0x0042bb15 FCPMediaHandler::RenderFrames(long long, bool) + 3981
    57 com.apple.FinalCutPro 0x0042c17b FCPMediaHandler::Idle(long, long, long*, TimeRecord*) + 657
    58 com.apple.FinalCutPro 0x0042d245 FCPMHIdle(FCPMediaHandler*, long, long, long*, TimeRecord*) + 45
    59 ...ple.CoreServices.CarbonCore 0x92def72d callComponentStorage_44444 + 49
    60 ...ple.CoreServices.CarbonCore 0x92de4474 CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
    61 com.apple.FinalCutPro 0x00426009 FCPMHDispatch(ComponentParameters*, char**) + 59
    62 ...ple.CoreServices.CarbonCore 0x92ddcb06 CallComponentDispatch + 29
    63 ...ickTimeComponents.component 0x95ee4de7 MediaIdle + 61
    64 ...ickTimeComponents.component 0x957673b6 doGenericIdle + 2991
    65 ...ickTimeComponents.component 0x957691eb GenericMoviesTask + 357
    66 ...ple.CoreServices.CarbonCore 0x92def72d callComponentStorage_44444 + 49
    67 ...ple.CoreServices.CarbonCore 0x92de4474 CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
    68 ...ickTimeComponents.component 0x9576893e GenericComponentDispatch + 182
    69 com.apple.FinalCutPro 0x00426025 FCPMHDispatch(ComponentParameters*, char**) + 87
    70 ...ple.CoreServices.CarbonCore 0x92ddcb06 CallComponentDispatch + 29
    71 com.apple.QuickTime 0x912b4083 MediaMoviesTask + 61
    72 com.apple.QuickTime 0x912b2e33 TaskMovie_priv + 4783
    73 com.apple.QuickTime 0x912c5b68 MoviesTask_priv + 101
    74 com.apple.FinalCutPro 0x001bad50 DoMoviesTask(KGPlayerRec*) + 2388
    75 com.apple.FinalCutPro 0x001cda79 DisplayMovie(KGPlayerRec*) + 2201
    76 com.apple.FinalCutPro 0x001d1f70 pKGPlayerUpdate(KGPlayerRec*) + 196
    77 com.apple.FinalCutPro 0x001bb045 DelayTimer(long, long, KGDictInt*, void*) + 89
    78 com.apple.FinalCutPro 0x00150552 KGTimerInvoke(__EventLoopTimer*, void*) + 212
    79 com.apple.CoreFoundation 0x900c1edb __CFRunLoopRun + 8059
    80 com.apple.CoreFoundation 0x900bf864 CFRunLoopRunSpecific + 452
    81 com.apple.CoreFoundation 0x900bf691 CFRunLoopRunInMode + 97
    82 com.apple.HIToolbox 0x97feff0c RunCurrentEventLoopInMode + 392
    83 com.apple.HIToolbox 0x97fefcc3 ReceiveNextEventCommon + 354
    84 com.apple.HIToolbox 0x98177c02 _AcquireNextEvent + 54
    85 com.apple.HIToolbox 0x9816dd5b _RunAppModalLoop + 101
    86 com.apple.HIToolbox 0x9816e13b RunAppModalLoopForWindow + 86
    87 com.apple.FinalCutPro 0x002a86b3 pKGDialogRun(KGPanelRecord*, unsigned char, unsigned char, KGDictInt*) + 755
    88 com.apple.FinalCutPro 0x00285bf4 pKGNotifyFilesOffline(KGDictInt*, long) + 1990
    89 ...FinalCutPro.Plugins.Browser 0x0bd0c914 BrowserOpenFile(KGFileRec*, unsigned char, unsigned char, KGDictInt**) + 5718
    90 ...FinalCutPro.Plugins.Browser 0x0bd0f42d Browser(long, long, KGDictInt*, KGFileRec*) + 10299
    91 com.apple.FinalCutPro 0x0018c870 CheckForOpenFile(KGFileSpec*, char*, unsigned char, unsigned char, KGDictInt**) + 488

  • Software Update wants to install Pro Apps Update 2008-05...

    I've been running Final Cut Studio 3 on this machine for a long time.  Suddenly Software update wants to install the Pro Applications Update 2008-05. The only thing I can think of that might have caused that is that I dragged over a copy of LiveType from an older PPC G5 that was still running FCS2.  Not sure if I should allow it or not. If I allow it, will it be smart enough to see that I have more recent versions of all of the apps?  Any suggestions?
    Thanks,
    CJ

    Nothing newer will be replaced.

  • Final Cut Server 1.1.1 & Pro Apps Update

    Many of you have been experiencing various issues with the Compressor & Qmaster process crashing and needing to resort to the only resolution to fix this issue:
    - Stop FCSvr, reinstall the QMaster Node.pkg, start FCSvr, and stop FCSvr services to get the issue fixed.
    Many others have wished for Final Cut Server would recognize all the metadata for video clips capture via:
    - FCP Log and Transfer
    - Capturing from a Sony XDCAM HD source
    - P2
    without using the very time consuming approach of dynamic metadata mapping.
    Many other have yearned for Final Cut Server to recognize EXIF metadata from images
    Well wait not longer.
    Download, Install, and Test the updates released today via Apple Software Update or by manually downloading them from:
    http://www.apple.com/support/finalcutserver/
    I must personally say thanks to the Mac OS X team, Pro Apps Team, and Final Cut Server team for resolving these issues.
    The product is very great and will only be better with stability and reliability update like these.
    Shame to everyone that has posted on the Final Cut Server discssion list complaining about these issues. Software development is no easy task, bug take careful time to fix and test before being released into the wild. We need to thank Apple more often for creating careers and a market place for everyone that is creative professional, systems administators, or technology consultants like myself.
    Enough said.

    I have one thing to say. The team that writes and maintains FCSvr could probably fit around a dinner table. It's a complex app to say the least.
    http://bugreporter.apple.com/(Free ADC account needed) should be the place where we direct all bugs and feature requests. Don't assume they know about it. Also, if you do use this, please follow the guidelines in submitting a report.
    It's a bit of work, but the developers appreciate a well written feature request and/or bug report. If we as the "soldiers in the trenches" give our feedback this can only get better.
    http://developer.apple.com/bugreporter/bugbestpractices.html
    http://stevenf.com/archive/reporting-bugs-in-mac-os-x-apps.php
    All that said, all the latest updates seem to be fairing well so far (touch wood). Even QuickTime!
    Chris

  • Color shift between viewer and browser after pro kit update

    hi there,
    i thought i be one of the lucky guys since updating and running 3.0.1 was easy on my system. but after yesterdays pro kit update i experience a weird color shift between the look of pictures in the browser and viewer.
    there is a strong colorshift in orange parts of sundown pictures. they turn magenta in the viewer but stay orange in the browser. the difference can easily be seen in the split screen. even weirder if i export a picture from the vier/split screen the exported files show the magenta tint. if i export them from the browser, they have the "right" orange tint.
    this happens with raw-files from both d200 and d70. also exportet the raw and processed it with ps cs3 and everything was ok. anyone got a clue?
    thanx in advance

    just found the explanation. after my prokit update, all raw-files needed to be reprocessed and then i needed to select the standard apple camera module for the d200. that was quite tricky and i don't understand why something like this happens. why do all files need to be reprocessed and than afterwards you would have to manually select the apple standard converter and why did the viewer look different than the browser and why is there no warning module that tell you all files will have to be reprocessed?

  • Download/Update buttons non functional after iOS 6 update

    Updated iPad 2 to iOS 6 tonight, initially I had the problem when app updates don't start and just hung. Restarted iPad and the updates appeared to have stopped. Went to update all apps again and the button did nothing. This is the same with all new app downloads/iTunes song purchases/individual app updates. The button does change from the price to "get single" or whatever, but the button just does absolutely nothing when clicked upon.
    All occurring over wifi, I don't currently have the laptop the iPad is synced with me but will tomorrow.
    Can anyone help me with this very frustrating problem?
    I have tried restarting iPad, restarting all apps, signing in and out with my apple ID, nothing appears to work. I can't see any downloads hanging in iTunes.

    Basic troubleshooting from the User's Guide is reset, restart, restore (first from backup then as new).
    iOS devices can only be restored with the current iOS version.
    No one here has any way of knowing if a "fix" is in the works, but that would imply there is an iOS issue causing your problem, this is highly unlikely.  More likely, something from your backup is causing an issue or the device has a hardware failure.

Maybe you are looking for