LR4 bugs & crashes

hi Adobe,
Could you please address the following issues:
LR4 crashes:
1.) First and foremost, I would suggest to implement an (optional) automated crash report function.
You will learn a lot about the instability issues that LR4 has.
PS: Suggested reading for the dev team: "Joel On Software" - contains an inspiring chapter on automated crash reporting
2.) LR4 is less stable than LR3.6 when I'm using it for processing Nikon raw files from my D700 with relatively modest resolutions.
Where a LR3.6 session would typically last 2 hours before becoming unworkable, LR4 usually gives up after like 30minutes.
This happens regularly on both an older Windows Vista PC and a more recent Windows 7 machine (both machines have sufficient specs)
This is my biggest disappointment with LR4, when I want to get some work done, I have to switch to LR3.6
If there were a way to provide more details about these crashes, I would do so (see point 1).
3. LR4 is also significantly slower than LR3.6. This may be related to the previous point?
LR4 bugs - faithfully carried over from LR3.x
4.) Rename folder
This still doesn't work properly in LR4, tried both Windows Vista & Windows 7
There are a couple of - relatively easy to reproduce - cases where LR apparantly keeps a handle to a folder(search) or file, which prevents LR from renaming the folder.
This usually happens when you have a file selected in LR in the folder that you're trying to rename, which is not uncommon ;-)
You can "avoid" the problem by quickly selecting another folder in LR, while LR is trying to rename the folder.
This does make for a nice mini-game, but it gets old after a while  ;-)
(yes, I'm sure I am not running any other software - including Windows Explorer - that references the folder or a file in the folder)
5.) Move file(s)
Suffers from more or less the same problem als "Rename folder"
It's usually the last file that can't be moved, forcing you to remember what you were doing and then move the remaining file again. Quicker to train a monkey ;-)

This is a user-user forum. If you want your concerns to be better heard by Adobe you might consider posting them at the proper site: http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om
If you want more bang for you buck, consider breaking your items up into individual posts instead of lumping them into a catch all post.  Also, be certain to research and make certain your bug/performance issues are not already in discussion. If they are, add your voice to the thread-don't create a new thread. If you create additional reports for things that already exist, the admins over there will likely merge your requests into existing threads.
Separate your feature requests into individual requests. Make certain they are not already requested and if they are, find them, and click [+1] on the existing request. Add your individual comments as necessary.
I can give you a hint and tell you that each of your five points already exists over there.

Similar Messages

  • Endless "Stream Overlap" Error Loop Bug Crashes Encore

    Endless "Stream Overlap" Error Loop Bug Crashes Encore.
    This is the 4 th time I have reproduced the bug.
    I burn a Disk image .. and upon completion the "Disk Info" resets to zero bytes under the Build Menu and when checking the Timelines Window the Dialog Box pops up with the "Stream Overlap" Error.
    Has anyone else had this issue?
    I have read other forum post .. and there is nothing relevant.
    I had to rebuild the project twice from scratch.
    I'm waiting for my Master Collection 5.5 .. maybe it is fixed in it.

    NOTE: There is a issue with Premiere Pro Dynamically Linking with After Effects with file corrupting I am experiencing as well.
    Someone offered a solution to rename my files to just words. ( No numbers or other characters )
    It still crashes .. and there is still file corruption ... but a "Linked Composition" can be found by "Edit Original" .. whereas it was not found before I changed the filename.
    This is a beginning to find the source of the nested bugs.
    I am wondering if this filesystem problem is core to the "Stream Overlap" problem noted here.
    I have have not reached tech support on the Encore side of this problems as of yet.
    This type of file system also has a terrible result for dated files:
    On the Mac ( Standard Finder ) :
    2011.1.1
    2011.1.2
    2011.1.9
    2011.1.10
    2011.1.11
    is treated in Adobe Encore as well as other Adobe Suite Master Collection Apps ( On the Mac Platform ) as:
    2011.1.1
    2011.1.10
    2011.1.11
    2011.1.2
    2011.1.9
    This make NO logical sense at all .. and must be some old DOS filesystem?
    Timecode
    Datestamp
    Numbered Outlines
    Are all very important ways to organize files / video.
    I am surprised that Adobe did not address this years ago.
    I have had two Adobe users mention a file system problem that has been known.
    Maybe it is the cause of my issues? ... Adobe is mixing two incompatible filesystems on a root level on the Mac platform only. ( Doesn't work with the Mac Finder? )

  • LR4 Beta crashes when accessing DNG files

    I am experiencing problems using 64 bit Win 7 and LR4. LR4 seems to crash every time I try to "DEVELOP" a dng format image that was created (imported from Raw)  with LR3.  I am not having the problem with the CR2 or JPG images although my processing speed seems extremely slow. The images were originally created with a Canon 7D or a Canon G12.

    Bill,
    It is my understanding that there is a known bug opening DNG files that have previously been developed under PV2010.  The bug seems to cause a crash when they are first accessed in the Develop Module. Try fresh images from the camera for testing purposes and see if you get the same crash. You shouldn't, and this will allow you to test the new features and provide feedback.
    Jeff

  • AIR 3.7.0.166 Sound Bug Crash APP without error

    Hello guys,
    The last Adobe Air Mobile update gaves me a lot of head ake!
    Im developing a multimidia APP, and since AIR was updated in my device, no more sounds is playing in the application.
    It just crashes withou any error in Debug mode, and restarts. When i call Sound.play media function in any ocasion, it happens.
    It seams that there is a REALLY BIG CONFLICT with the new AIR and Sound.play.
    My references:
    Im developing in Flash Builder 4.6, running Adobe AIR 3.7.0.166
    on a Motorola Atrix MB860
    with Android 2.2.2
    To reproduce the bug just install any AIR APP with music controls, like this: http://coenraets.org/blog/air-for-android-samples/voice-notes-for-android/
    APK: http://coenraets.org/android/VoiceNotes/VoiceNotes.apk   with the 3.7.0.166 version of AIR, and try to reproduce the sound.
    That application was running ok until the update. There is an textflow bug too, witch import only underline <u> and link <a> tag (no more bold <b> and italic <i>) from HTML, but compared to the sound crash this is nothing.
    I insist that all this was running OK since the last update (i even run an backup version cause i think i was making any script error).
    I´m looking hopelessly the LAST version before that last one so i can continue developing my application. With this error i canot do anything!!!!
    If someone can help me where i can find it, id appreciate a lot!
    Thanks

    05-29 19:59:00.896: I/DEBUG(3857): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    05-29 19:59:00.896: I/DEBUG(3857): Build fingerprint: 'sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P-17_20130107.155157:eng/test-ke ys'
    05-29 19:59:00.896: I/DEBUG(3857): pid: 4130, tid: 4154  >>> air.com.baijie.learnhanzi <<<
    05-29 19:59:00.896: I/DEBUG(3857): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
    05-29 19:59:00.896: I/DEBUG(3857):  r0 00000000  r1 afd46608  r2 00000000  r3 00000001
    05-29 19:59:00.896: I/DEBUG(3857):  r4 83195a94  r5 00006d00  r6 00000000  r7 00000017
    05-29 19:59:00.896: I/DEBUG(3857):  r8 2f8df18f  r9 00003120  10 00323dd0  fp 00008ae0
    05-29 19:59:00.896: I/DEBUG(3857):  ip 00000000  sp 49995cc8  lr afd10e74  pc 8214b238  cpsr 60800030
    05-29 19:59:00.896: I/DEBUG(3857):  d0  454545656372756f  d1  2e2e2e276a634b50
    05-29 19:59:00.896: I/DEBUG(3857):  d2  203334312020203a  d3  6c20746f6e6e6163
    05-29 19:59:00.896: I/DEBUG(3857):  d4  5f2720657461636f  d5  6f72646e61374e5a
    05-29 19:59:00.896: I/DEBUG(3857):  d6  6f43584d4f386469  d7  6165724336636564
    05-29 19:59:00.896: I/DEBUG(3857):  d8  0000000000000000  d9  3ff0000000000000
    05-29 19:59:00.896: I/DEBUG(3857):  d10 0000000000000000  d11 0000000000000000
    05-29 19:59:00.896: I/DEBUG(3857):  d12 0000000000000000  d13 0000000000000000
    05-29 19:59:00.896: I/DEBUG(3857):  d14 0000000000000000  d15 0000000000000000
    05-29 19:59:00.896: I/DEBUG(3857):  d16 5f534e4b52456574  d17 345f534e49707332
    05-29 19:59:00.906: I/DEBUG(3857):  d18 52454545584d4f49  d19 534e495f31534e4b
    05-29 19:59:00.906: I/DEBUG(3857):  d20 61446174654d385f  d21 4b52624545456174
    05-29 19:59:00.906: I/DEBUG(3857):  d22 5f534e495f31534e  d23 53616964654d3131
    05-29 19:59:00.906: I/DEBUG(3857):  d24 0000000000000000  d25 0000000000000000
    05-29 19:59:00.906: I/DEBUG(3857):  d26 0000000000000000  d27 0000000000000000
    05-29 19:59:00.906: I/DEBUG(3857):  d28 0000000000000000  d29 0000000000000000
    05-29 19:59:00.906: I/DEBUG(3857):  d30 0000000000000000  d31 0000000000000000
    05-29 19:59:00.906: I/DEBUG(3857):  scr 60000013
    05-29 19:59:01.026: I/DEBUG(3857):          #00  pc 0014b238  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.046: I/DEBUG(3857):          #01  lr afd10e74  /system/lib/libc.so
    05-29 19:59:01.046: I/DEBUG(3857): code around pc:
    05-29 19:59:01.056: I/DEBUG(3857): 8214b218 4810bd10 68004478 490fe7fa 68094479
    05-29 19:59:01.056: I/DEBUG(3857): 8214b228 b1604788 23014a0d 447a7023 47906812
    05-29 19:59:01.056: I/DEBUG(3857): 8214b238 6b4b6801 4a0a4798 6010447a 4809e7e8
    05-29 19:59:01.056: I/DEBUG(3857): 8214b248 68004478 bf00e7e4 0102ef30 0104a884
    05-29 19:59:01.056: I/DEBUG(3857): 8214b258 0104a880 0104a878 01023cc8 01028ece
    05-29 19:59:01.056: I/DEBUG(3857): code around lr:
    05-29 19:59:01.056: I/DEBUG(3857): afd10e54 02800016 08bd87f0 e5964000 e5967000
    05-29 19:59:01.056: I/DEBUG(3857): afd10e64 e2144903 1a00000e e5965000 ebffee45
    05-29 19:59:01.056: I/DEBUG(3857): afd10e74 e2055a02 e3853001 e1500003 0a000006
    05-29 19:59:01.056: I/DEBUG(3857): afd10e84 e5865000 e1a00006 e1a01005 e3a02001
    05-29 19:59:01.056: I/DEBUG(3857): afd10e94 ebfffea8 e1a00004 e8bd87f0 e3a00000
    05-29 19:59:01.056: I/DEBUG(3857): stack:
    05-29 19:59:01.056: I/DEBUG(3857):     49995c88  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995c8c  826efaaf  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995c90  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995c94  8276c953  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995c98  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995c9c  82145e97  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995ca0  8316e000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995ca4  831a5e28 
    05-29 19:59:01.056: I/DEBUG(3857):     49995ca8  0000000a 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cac  821d0869  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995cb0  83195a94 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cb4  00006d00 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cb8  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cbc  00000017 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cc0  df002777 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cc4  e3a070ad 
    05-29 19:59:01.056: I/DEBUG(3857): #00 49995cc8  00001000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995ccc  821d5cdd  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995cd0  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cd4  8316e000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cd8  00323dd0 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cdc  002b6b98 
    05-29 19:59:01.056: I/DEBUG(3857):     49995ce0  82ded2d4  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995ce4  82ded320  /mnt/asec/air.com.baijie.learnhanzi-1/lib/libCore.so
    05-29 19:59:01.056: I/DEBUG(3857):     49995ce8  00325ba0 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cec  00009b98  /system/bin/app_process
    05-29 19:59:01.056: I/DEBUG(3857):     49995cf0  00008124  /system/bin/app_process
    05-29 19:59:01.056: I/DEBUG(3857):     49995cf4  00001074 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cf8  4278f500 
    05-29 19:59:01.056: I/DEBUG(3857):     49995cfc  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995d00  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995d04  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995d08  00000000 
    05-29 19:59:01.056: I/DEBUG(3857):     49995d0c  3ff00000 
    SC8810, Android 2.3.5

  • ACR 4.5 Did Not Fix Photoshop Bug Crashing

    I posted this in June
    Bug: Multiple Files Open ACR Crashes Photoshop...
    Buko, "Bug: Multiple Files Open ACR Crashes Photoshop..." #1, 10 Jun 2008 2:57 pm
    I just went back to my normal workflow with ACR 4.5 (after leaving it because of the problem) and got the new Photoshop crash report after working on about six files.
    The workflow: .nef> Bridge> ACR> 16-bit aRGB (moving sliders Black/Mids/Exposure usually generates the crash)> resizing to 500 pixels and Save AS .psd (leaving the .psd files open seems to be the switch that causes the problem)
    I can repeat the problem consistently:
    Drag folder containing D200/D300 .nef files into Bridge, and going to work as described...if I don't leave my .psd files open I don't have a problem, if I leave them open as I work, I usually get the crash after 5-10 files.
    I emailed crash reports to CC back in June,

    UPDATE:<br /><br />I pulled the 12gb of macramdirect ram and tested with only 2gb OEM Apple ram (to rule out the 3rd-party ram per Jeff Schewe's theory  I duplicated the crash within 15 minutes.<br /><br />My money remains on the BUG theory, but will swap out the OEM ram and continue...if that doesn't work I will install ACR 4.6 and retest...<br /><br />Today's CRASH REPORT:<br /><br /><?xml version="1.0" encoding="UTF-8"?><br /><!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"><br /><crashreport version="1.1" crVersion="2.5.0.02272007" applicationName="Photoshop" applicationVersion="10.0.1" build="10.0.1 &#40;10.0.1x20071012 [20071012.r.1644 2007/10/12&#58;09&#58;30&#58;00 cutoff; r branch]&#41;,  ©1990-2007 Adobe Systems Incorporated"><br />     <time year="2008" month="10" day="2" hour="15" minute="50" second="29" /><br />     <user guid="5F46434A-15D5-4A63-A652-31682CE59DD0" /><br />     <system platform="macintosh" osversion="10.5.5" applicationlanguage="en" userlanguage="en" oslanguage="en_US" ram="2048MB" machine="i386" model="MacPro3,1" cpuCount="8" cpuFreq="2800MHz" busFreq="1600MHz" /><br />     <crash exception="Unmapped Memory Exception" instruction="c683068b"><br />          <backtrace crashedThread="0"><br />               <thread index="0"><br />                    <stackStatement index="0" address="0xffff07c2" symbolname="unknown"/><br />                    <stackStatement index="1" address="0x9327efd9" symbolname="__ZN18CTextensionIOSuite17SearchIOSuiteTypeEmP11TDataHeaderh"/><br />                    <stackStatement index="2" address="0x9327ef17" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEm"/><br />                    <stackStatement index="3" address="0x9327eee6" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEv"/><br />                    <stackStatement index="4" address="0x9328c9af" symbolname="__ZN18CTextensionIOSuite4FreeEv"/><br />                    <stackStatement index="5" address="0x93248cd7" symbolname="__ZN22CTextensionEditCommand4FreeEv"/><br />                    <stackStatement index="6" address="0x9328c7ed" symbolname="__ZN15OpaqueTXNObject4FreeEv"/><br />                    <stackStatement index="7" address="0x9328c71e" symbolname="_TXNDeleteObject"/><br />                    <stackStatement index="8" address="0x2fcc4a6f" symbolname="_EntryFM"/><br />                    <stackStatement index="9" address="0x2fc9286e" symbolname="_EntryFM"/><br />                    <stackStatement index="10" address="0x2fc58104" symbolname="_EntryFM"/><br />                    <stackStatement index="11" address="0x2fc53c7e" symbolname="_EntryFM"/><br />                    <stackStatement index="12" address="0x2fc94c2e" symbolname="_EntryFM"/><br />                    <stackStatement index="13" address="0x2fc58104" symbolname="_EntryFM"/><br />                    <stackStatement index="14" address="0x2fc53c7e" symbolname="_EntryFM"/><br />                    <stackStatement index="15" address="0x2fc74047" symbolname="_EntryFM"/><br />                    <stackStatemen

  • Yet another iMovie 6 bug-Crashing!

    Why did I have to upgrade on both my drives? Buggy, buggy, buggy. Transitions don't work properly, neither do video effects and it has a tendency to crash. But, hey, great-looking box!
    I wish instead of coming out with all these fancy new features, they'd concentrate on making the software stable.
    But, hey, that's just me.

    These are projects started in iMovie 6. Yes, I'm having some issues with 3rd party plugins. But they worked fine with the previous version. And, anyway, so few transitions and effects come standard with iMovie—what else are we supposed to do? I'm finding the new preview irritating. It decides for itself when it loops and when it doesn't—so I have to keep turning it off. Sometimes the update feature doen't work. Sometimes I get white frames at the end of pictures placed in the timeline so I have to go back in and clip them off. Updating clips sometimes causes transitions to re-render funny and the whole block has to be removed and recreated. And, in general, the new interface seems fancier but is more cumbersome to work with and takes longer to do projects. I've also had issues exporting finished movies.
    In general, it feels like a beta version and I didn't have the sense to wait until the bugs got worked out. My bad. Each first effort seems a little buggy, but this one is the least stable yet. It's almost like the marketing people are telling the programmers when the product is ready rather than the other way around.

  • Seasonal Time Change Bug crashes Dreamweaver 9 (CS3)- still no fix?

    The fact that Adobe has produced a new version of CS3 does not in my opinion give them a reason not to fix the CS3 bug that causes Dreamweaver to crash when any attempt is made to edit the ASP or  PHP components of a file.
    This bug is caused by daylight time adjustments.
    The podge that is recommended by Adobe is to delete the WinFileCache-AD76BB20
    While this works, as it happens only every 6 months, it is easy to spend time working out why your existing files all crash the system, but newly created ones do not.
    You can find the solution at http://kb2.adobe.com/cps/402/kb402776.html
    Bookmark this as it may save you the 4 hours or so that I spent trying to find a solution.
    It would cost Adobe nothing to send out an e-mail to all existing owners of CS3 containing this bug fix, and would certainly improve their reputation in many quarters.

    well.
    it feels bad, after paying money.
    not being able to use a software full.
    and ADOBE must be ashamed to give such service
    (by not updating these softwares which has still lots of unknonw! bugs and also must be ashamed to put a page for unknown bugs. and trying to make customers be their own software engineers instead of the company's hundreths of engineers)
    and this, which they do not fix their program is not important or the issue.
    it is a sad subject that, they think the people will give money to fix their unusable programs which they already bought.
    and to customers who has paid about 1000$ to a software suit are having a bad vision that ADOBE started to work for money instead of customer happiness.
    when they understand their
    1000$ program has no support at all. no update or fixes at all.
    which can not do a simple action
    which the simplest editor WORDPAD editor does.

  • CFP LV RT 2009 (ETS) Bug - Crashing on bad INI file

    Hello,
    This problem was actually touched upon in this thread:
    http://forums.ni.com/ni/board/message?board.id=170&message.id=466392&jump=true#M466392
    I have found, that if the ni-rt.ini file contains any "unexpected"  or wrong parameters (like the thread above describes), my cFP 2210 with LV RT 2009 crashes. After the crash, the following is the situation:
    - The ni-rt.ini file is garbled with strange charcters.
    -  I have format the "disk"  and reinstall all software again to make it work correctly!
    This is bad, since I have never encoutnered such a problem with LV 8.2 on a cFP 2120: 
    We have two of these running in a Concrete Production Plant here in Norway.
    They have been stable for 2 years.
    I could send updates via email: Just the .rtexe and the .alias file.
    The electrical engineer at the plant used FTP to replace the existing .rtxex and .alias file,
    Then he edited the .ini file with the name of the new .rtexe.
    If any errors where entered into the .ini file, the cFP simply would report the error to one of the logs, and NOT CRASH!
    I recon this is a bug, and it may easily be reproduced by trying to enter the entries I have listed in the thread linked to above.
    Geir Ove

    Hello,
    I have updated information on this problem:
    First a little background on "how it used to be"  when running LV 8.2 RT on a cFP 2120:
    To update the cFP with a new program, I did the following over a wireless network while the cFP was running but the machine it controlled was sitting stationary:
    1) On the cFP: renamed the .rtexe to .rt (to allow the file to be deleted)
    2) Deleted booth the .alias and .rt file
    3) downloaded new .rtexe and .alias files
    4) uploaded to my PC the ni-rt.ini file. Edit the name of the startup program
    5) downloaded the new ni-rt.ini file to the cFp
    6) From my PC rebooted the cFP
    THis may seem like a wild thing to do, but it works like a charm.
    It turns out, it also works well on the cFP 2120  with LV RT 2009.
    However, on the cFP 2210  the ni-rt.ini file becomes corrupted if the file is downloaded again to the cFP while it is running.
    If, however, the cFP is rebooted into Safe Mode first, I can still do all the steps above to update the cFP.
    WHy I do not use LV to do the update? Well,  in this manner the customer can do the update with no special tools or LV knowledge.
    Also, it is valuable to be able to update the cFP without accessing it physically, because it is not easily accessible (A conveyor running under the roof of the factory !)
    I do not understand why there should be a difference between the cFP 2120 and cFP 2210 in this respect !
    But since it is, it should be documented. We use LV to save development time, but this has costed extra time in this project.
    Geir Ove

  • LR4 Regularly Crashes When In Slideshow

    Hi, I've used LR3 for a long time and recently upgraded to LR4.
    I'm finding that it regularly crashes when I'm in Slideshow.
    I have an iMac with 8GB ram and even with no other applications running, I have this problem.
    The only 'cure', albeit temporary, seems to be to turn off and restart my computer.
    Any ideas?

    Try removing the Preferences File/s. Look here for instructions: http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-41.html
    If that does not help next try removing the .lrdata file from your catalog folder and rebuilding previews.

  • LR4 Beta Crash on Exit

    LR4 for Windows 64-bit crashes on exit and fails to close.  I have to manually kill the program in Task Manager.  This has occurred each time I exit by clicking on "close window."  It does not happen if I close from the menu.
    AMD Phenom II X6
    16 Gig Ram
    Radeon 5570 Video Card
    Windows 7 Professional

    known issue, Uncheck "remove chromatic abberation"  in your LR settings

  • BUG/CRASH when exporting 1080p project containing DSLR footage. 720p works fine.  Please fix or respond

    Hello,
    I would like to report an application crash for iMovie mobile.  After the recent update (1.2.2), adding the functionality to import footage from cameras other than iOS devices.  (DSLR, HDV, HD, MP4 etc.)  I recently created a 12min project in iMovie which contained all clips shot on a Canon DSLR.  I was able to export a 720p movie to my Camera roll when the project was completed.  However when trying to export a 1080p movie it always crashes around  20 seconds after starting the export process.  This leads me to believe that there is a bug.  I also tried this on 2 other devices  (iphone 4s and friends iPad 2) all of them are having the same crashing problem.  
    I made sure that there was enough space as I'm aware the 12min 720p movie alone was 800mb.   Meaning the 1080p file could not exceed more than 2gb.  I had 16GB of free space and no other applications running in the background and they would all crash around the same 20 second mark.  
    Please Advise if this is a known issue already in the works.
    Thx,

    Welcome,
    This is a user forum, so no Apple staff here sorry.
    If you have a problem or error to report to Apple then you can do so here:
    http://www.apple.com/feedback/imovie_ios.html

  • Premiere CC - Merge Clips repeatable bug crash!

    I have been editing a feature film since the start of this week and have found a huge bug and proble with Premiere CC. This has been repeatable for me every time.
    I am working on a brand new install of windows 8, all updated, and 64GB of RAM.
    I am working with Epic footage shot 5k 2.4:1
    Sound was recorded as separate WAV files each video clip has either 1, 2 or 3 mono WAV files (Merged) to them.
    Here is the problem:
    When working with all merged files, everything works fine, but if I try and bring in any clip that is not a merged file things get crazy. I can work fine unless I select or try to move a merged clip and a non merged clip at the same time. So if I select all on the timeline and only have merged clips, no problem. If there is even one non merged clip on the timeline and I select all, I get an instant Premiere Pro CC has encountered an error, and closes out premiere.
    My temporary workaround:
    If I merge an audio file, like a music file/ ADR or sound effect with a color slug, and just select the audio file to bring into the timeline, everything is fine.
    Same goes with video clips. If I have an MOS clip, I can simply merge it to any random audio file, then just bring in the video file and everything works fine. I can select the whole timeline and nothing crashes. But if I forget even once, Boom Premiere shuts down. . . very frustrating.
    Thanks for any insight that may be provided in this situation
    Stefan

    Hi Kevin,
    Unfortunately, no audio syncing occurred with multi-cam on 2 different formats (MPG and MP4). I did find out how to view the multi-cam sequence though.... You need to have the track with the multi-cam sequence selected.  If it's not selected, the preview window is blank.
    But Premiere still can't sync audio with all formats I've tried.
    Message was edited by: vanlazarus2013

  • IOS 5.0.1 MMS Bug - Crash

    I have been able to recreate this bug multiple times after upgrading to IOS 5.0.1. Here is how to test it:
    1) Pick a picture to MMS.
    2) Pick a "to" address
    3) Use the microphone button and speak your text to convert
    4) Send
    It crashes every time. If you manually type your text, it sends the MMS just fine. Anyone else run into this?
    Iphone 4s Verizon on IOS 5.0.1

    Mine is worst.
    When i try to slide to unlock, it crashes,
    but when im able to get in and when i try to run an app, it crashes,
    and sometimes when i try to type a character to reply to a message or something, it crashes.
    The pain!!! XD
    iPhone 3GS with iOS 5.0.1

  • Logic 8 Bugs/Crashing when importing audio

    Hi,
    Been running Logic 8 for a few months - some good things but lots of niggly bugs which we're trying to iron out.
    We're getting a problem with Logic crashing everytime we import an audio file - however when Logic reloads the file is in the project and plays fine. Anyone come across something similar?
    Also, for some reason audio files are playing randomly in a Logic sequence - for example the backing vocals will play at the start of the track even though they are not placed anywhere near there.
    Hoping someone can help, we've installed the latest updates and everything - currently running a HD 192 TDM system on 10.4.11.
    Thanks
    Jack

    I have had similar bugs like this even on 7. I think it might be a DAE/Logic issue that has been carried into the next generation. Just the wrong playback of an audio file in respect of the arrangement placement is new. I am having it too when i am in cycle mode. Only randomly though.

  • [LVC bug] Crash when changing the position of a wire terminal in the icon tab

    Hi,
    in the attached VI, if I go to the icon tab and try to move the terminal "xa2" up, the GUI crashes.
    LVC version 1.0.0.50009
    Nicola
    Attachments:
    do_generate_waveform.gvi ‏112 KB

    Welcome to the forum.
    It's always best to put different questions in different threads. Sometimes people have the answer to one question and not the other.
    There is an article on my site about creating help for left to right languages. You may be able to extract something from that to deal with the tabs.
    To get larger images when a smaller one is clicked, there are various options.
    You could use a javascript method, there are many that you can find by Googling.
    You could put it in another HTML page that just has the image. You could then create an ordinary link or a popup link.
    You could create a link from the small image to the large image. (Select the image and then click the link icon. Choose the Link to File option.
    Each will work in a different way so you have to decide which you prefer for your users.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

Maybe you are looking for

  • Visual Studio Error in UNIX FTP for AIX

    I am using a VS2010 Web Site Project to access files on our AIX server (Unix). (Pre-compiled website). Using Add > Existing Web Site, I have established an FTP session within my project which shows all of the Unix files and folders. We just found out

  • Illustrator CC 2014 slow opening networked files on some PC's

    Have 6 PC's running CC 2014. 5 Win 7 Pro 64, one Home 32. Two weeks ago two of the pro 64 PC's are pausing for 20 seconds opening or saving illustrator files of any size on the network (Server 2008 R2). No issues with any other programs or any of the

  • With Photoshop 7 how can I get text in a layer that is in effect the colours of the layer behindd

    Have tried several Google searches but not quite found what I think I'm looking for My PS7 Bible is also a little lacking on an obvious explanation of what I'm trying to achieve thanks Richard

  • Write diadem search results to text file

    Is there a solution within DIAdem for exporting specific information from a search result into a text file? For example: I perform a search which returns all of the files, groups, and/or channels which I want to work with; now I would like to have, s

  • Missing Business Partner

    Classic Scenario; SRM 5.0; R/3 46C Hi everyone, I am a true novice when it comes to troubleshooting issues related to Business Partners.  My updated SRM Org Structure shows that there is a node w/ a business partner number 0000005409 under the Extend