Transition Corruption Upon File Export

Hi everyone, I have been trying to export some videos and everything plays perfectly fine in the timeline. However, when I export to a QuickTime file, every transition appears to be "corrupted." Tiled blocks and ugly green patches all over, but only during the transition. It happens with every transition, from cross dissolve to alpha transitions. Any ideas would be greatly appreciated.
Thanks!

I'm having the same problem. If I make sure that the transition isn't rendered then it comes out fine, but when it is rendered and makes the self contained quicktime the transitions are corrupted. However, when it is played in the timeline it is just fine.
what codec is the footage, - HDV 720p60
what codec is is the timeline, - HDV 720p60
what codev are you exporting to? - HDV 720p60
what version of FCP? 7.0.3
OS X? 10.6.4
Quicktime? (player) 10.0 (114)
I was thinking about trashing preferences, but wanted to ask first.

Similar Messages

Premiere CS4 crashes/freezes upon File Export Media click

My system:
CS4 master collection. I have some remnants of CS3 on my computer.
4 Gig RAM
Quad Core processor
Vista
My problem:
Problem started yesterday and I've tried a lot of things but can't figure this out. When I click File>Export>Media, premiere greys out most panels and nothing can be clicked. It gives a beep of death on every click. I need to use task manager to close premiere. The only thing I've found I am able to do is click escape, which returns me to my project as if nothing has happened.
I've tried a range of different projects, including a brand new one with nothing in it except a 10 second DV avi file. Same problem across the board.
I've reinstalled CS4 Master collection but didn't uninstall it first. No change. Would it help to uninstall everything and start from scratch?
Never had this problem before.
It also does the same thing on file>export>clipnotes but I CAN export an EDL.
The only change to my PC between this not happening and it happening was I installed the new music streaming software 'Spotify'. I have since uninstalled this but it hasn't fixed it.
If anyone has any ideas, I'd be hugely grateful.
Ed

Hey Ed, I had replied earlier in the other thread you posted in and just noticed you started a new topic here, so, copied from the other thread:
I had something similar happen to me a few times... if the escape key is taking you back to premiere and returning everything to normal, then your computer is not really hanging or crashing. What most likely is happening is that Premiere is opening a dialog box OFF SCREEN, so you just can't see it or click on it to attend to what it's asking. Hitting escape is like hitting cancel, which returns you to your project.
To fix: just mess around with your monitor setups in your display panel, ie.: if you have a dual monitor setup, temporarily disable one monitor - forcing everything to open on one screen. And/Or set your screen resolution to the maximum your video card allows so that you may uncover the off screen space the dialog opens on. OR... you're video card may have a control panel with the option of forcing all windows onto one screen or preventing off screen display. Basically do whatever it takes to get a view of off your screen.
Once you discover that missing window, make sure you move it onto your primary display, somewhere in the center, and the next time you try to encode it should be right where it should be.
Good luck.

Corrupt .hh files in RH 7

Since upgrading to RH 7 I am having extensive problems with
the .hh file corrupting any time I try to update a map ID. I have
resorted to manually editing the .hh in notepad and then replacing
the corrupt file. When adding or modifying an existing Map ID, one
entry will start with invalid characters which I could only see
when exporting the file to Excel. I then get a warning message on
compile: "The Topic ID contains invalid characters." I am compiling
in WinHelp 2000 format.
Is this a bug in RH7? I'm not sure how I'm going to create
new Help topics in Word and assign them Map IDs with this current
problem. This particular file was originally on a co-worker's
machine and I have taken over the file. Is there something in the
.dot file or project file that could be set wrong?
Also, I just opened a project that compiles perfectly in
WinHelp 4.0 but has multiple warning and problems when compiled as
a WinHelp 2000 help file. I was using RH 6, so there isn't a large
gap in the versions. Upon further investigation, even WinHelp 2000
files that compile perfectly, end up with corrupted .hh files when
a new topic is added and assigned a Help ID.

A caution on cindep's response.
If the .hh or .h file has only ANSI data then this will work
but if any UTF-8 data is present in the file then it will not work.
For example, if the files has only English characters then it will
work, if the file has English and Japanese characters then it will
not work.

File - Export from Preview, iPhoto etc does not work

Lately, normal operations from OSX-programs are not working as expected on my MacBook Air mid-2013 running OSX 10.8.5. I can reproduce in PreView and iPhoto that operations like File, Export and File, Duplicate do not work - there is just no response.
Upon opening console, I see the following error messages:
10/11/13 3:23:50.170 PM com.apple.security.pboxd[487]: CGSGetWindowTags: Invalid window 0xc8
10/11/13 3:23:50.170 PM com.apple.security.pboxd[487]: kCGErrorFailure: CGSSetHideOnDeact: error getting window tags
10/11/13 3:23:58.950 PM com.apple.launchd[1]: (com.crashplan.engine[735]) Exited with code: 1
10/11/13 3:23:58.950 PM com.apple.launchd[1]: (com.crashplan.engine) Throttling respawn: Will start in 10 seconds
10/11/13 3:24:00.167 PM Preview[456]: RVS:__54-[NSRemoteSavePanel _runOrderingOperationWithContext:]_block_invoke_0319 : Timeout occured while waiting for the window
10/11/13 3:24:00.171 PM librariand[459]: [ERROR] [913.272s] com.apple. SRMessageTransport.c:498 SRConnectionCreateClient() timed out waiting for the server to post the started notification
10/11/13 3:24:00.171 PM librariand[459]: [ERROR] [913.272s] com.apple. framework_client.c:810 IPCEnableSyncing() failed to run server: -1
10/11/13 3:24:00.172 PM librariand[459]: [ERROR] [913.272s] com.apple. UBService.c:598 UBServiceEnableMobileDocuments() IPCEnableSyncing failed with error: The operation couldn’t be completed. (UBErrorDomain error 2.)
10/11/13 3:24:08.972 PM com.apple.launchd[1]: (com.crashplan.engine[736]) Exited with code: 1
10/11/13 3:24:08.972 PM com.apple.launchd[1]: (com.crashplan.engine) Throttling respawn: Will start in 10 seconds
10/11/13 3:24:18.996 PM com.apple.launchd[1]: (com.crashplan.engine[737]) Exited with code: 1
10/11/13 3:24:18.996 PM com.apple.launchd[1]: (com.crashplan.engine) Throttling respawn: Will start in 10 seconds
10/11/13 3:24:20.174 PM librariand[459]: [ERROR] [933.275s] com.apple. SRMessageTransport.c:498 SRConnectionCreateClient() timed out waiting for the server to post the started notification
10/11/13 3:24:20.175 PM librariand[459]: unable to enable mobile documents
10/11/13 3:24:20.175 PM librariand[459]: error in _handle_client_request: LibrarianErrorDomain/10/Unable to configure the collection.
Please help...

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

How to fix a corrupt .avi file (from capture in CS3)?

So I was recording a VERY long meeting at work and recorded it to my PC via Premiere. Since the recording was unattended, the file size is 275GB! I didn't really think anything would go wrong since I have recorded large .avi files in the past.
Well when I try to import the .avi or play it in media player, it is saying it is corrupt/wrong file format. I tried a few avi repair utilities and none of them fixed it. I'm guessing the avi headers are missing, but I thought Premiere wrote progressive .avi files (at least their export is progressive and valid while its writing).
Any help to repair salvage the avi? I only need about 50% of the actual content.

>wonder why you can view a video that is currently being exported
Seeing what the computer is
DOING while it is doing it is really not the same as trying to open a file after the fact
I have an inexpensive standalone DVD recorder to be able to move a movie from a DirecTv Tivo box in one part of the house to a DVD player in another part of the house
I can watch the video on the TV while it is playing from the DTivo box to the DVD recorder
If I do not properly CLOSE the disc when the recording is done, the DVD will not play
An improperly closed file is, as you found, not going to work
As I said, my best GUESS is that hitting the full point on the drive caused needed information to not be written to the header (or file end) and now any software you use to try and play or edit that file doesn't know what the file
IS because the identity is lost
I will guess that is also why the AVI repair programs you've tried won't work... they need to have some starting information to work, otherwise the contents of the file are just so much random "noise"

Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620 with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
to .mov Prores 422HQ 1080P                         22 Minutes
to .mov H.264 1080P                    22 Minutes
to .m2v Mpeg 2 1080P                                                22 Minutes
From a 1080P timeline Prores footage at 100% (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format                         13 Minutes
to .mov Prores 422HQ 1080P                             13 Minutes
to .mov H.264 1080P                                                             14 Minutes
to .m2v Mpeg 2 1080P                                                            14 Minutes
Since I am going to DVD, I chose the fastest option Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
      Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Illustrator CS4 - frequently generates corrupt EPS files that will not parse

I have used many versions of Illustrator prior to and including the CS lines. I am currently running CS4 and this is the first time I have experienced this issue. Approximately half of my EPS formatted illustrator files will not parse. I use Quark Xpress 7 for my layout (never liked any of the Indesign programs). If I try to generate a PDF with my CS4 generated EPS files placed at least 60% of the time the placed file will corrupt the PDF export resulting in no PDF being generated.
Further to this PDF export issue, if I attempt to parse the same EPS file into Photoshop, Photoshop will give me the error message "Could not complete your request because Photoshop was unable to parse the PostScript" and it will abort the attempt to open the file.
Anyone else having Illustrator EPS file issues?
Background info (if needed) Dual 2.0 Ghz, PowerMac G5, 8 gb RAM, running Tiger 10.4.11
I have attached a sample Illustrator file that will not Parse. It will open in Illustrator but not parse into Photoshop or if placed in Quark will not parse and allow for a PDF to be exported.

Thanks for taking the time to write Steve.
I understand that I can drag and drop between programs. Ultimately, when attempting to parse an EPS in photoshop I am merely doing it to confirm that the EPS is indeed corrupt.
As mentioned previously, I predominately use Quark Xpress for my page layout program and until I installed CS4 I have had zero complications with using EPS files. Now I quite commonly can not export PDFs due to corrupt EPS files.
My question to the public is I am alone in this glitch or do others experience the same issue. My first thoughts are that CS4 has a glitch and I should be expecting an update in the near future. But, if I am the only person suffering from this issue than maybe I should be looking at my own software.

Can't visualise text on PDF files exported from PS

PDF files exported from PS (levels included as we need them to be selectable) have corrupted text. When opening the saved pdf file, a part of text doesn't appear. It is usually starting from the second chapter of text. Any idea of how to solve this problem?

Hi Marco,
For now we have only fixed this in CC, but we are aware this problem also affects CS6 users and is a significant problem for many people. At this time, I don't know of any workaround in CS6 for this bug other than to break text up into smaller blocks or use another more text-oriented application like InDesign. While I can't comment on future releases, your feedback on this issue is important to us, and I can say, "there's always hope"...
If you'd like to discuss this further, or send us a file that exhibits the problem, please contact me directly. My email address is my last name @ adobe.com.
Paul

Missing WYSIWYG File Export option

Hello,
I'm running a trial version of Photoshop CS6 Extended and can't find the WYSIWYG plug-in for my Matrox device which I think I should be able to access via File>Export.
I've reinstalled the drivers for my device so it shouldn't be that.
Could it be that this feature isn't supported in trial versions?
Any help appreciated

I understand that it is difficult to determine which forum to post in since there are so many. This particular forum (sharing and storage) was created to help those transitioning from Photoshop.com to Adobe Revel. I am moving your post to the correct forum so that it can get proper attention.
I'll put this posting in the photoshop community so the experts there can help you.
We also have many other forums relating to other Adobe products
http://forums.adobe.com/community/
http://forums.adobe.com

How to repair corrupted PDF-File ?

Hi there !
I am having problems with a couple of PDF-files which got damaged due to a hard drive break down / file recovery action.
Neither can i open them ("...not supported") nor have several attempts in repairing them (by using Pdf-repair software) been successful.
Interesting point about it is, that in terms of file characteristics everything seems to be OK (file size, file type etc. are recognized by the computer).
Does anyone have an idea what could be done to get my PDF's back to a readable status ?
Thanks     timrelo
Ps: In case you got an idea about how to fix a corrupted pdf-file, i am willing to send you one of my files.
      To do so, please send an email to    [email protected]    and i will email you a file.

Hi Bernd,
unfortunately i don't have the root-file (indesign etc.) to re-create/export a new pdf.
all i got is a couple of restored (from the crashed hard drive) pdf files which are indicated as being "corrupt/damaged".
greets   tim

File Export is grayed out when Photo Book selected - worked yesterday

I have been assembling a Photo book from various scanned photos. In order to share a preview before send it of to be printed, I used the File>Export option to produce a Quicktime movie. It worked very well but today I wanted to change some of the movie settings.
When I tried to repeat the exercise, I found that the File>Export option is now grayed out and I cannot access it. The options to Share to web and iDVD are still available and I can print to PDF.
I cannot think of anything that has changed since yesterday. I tried a reboot but it made no difference.
Any suggestions appreciated.
Dave

David:
Try deleting the iPhoto preference file, com.apple.iPhoto.plist. What are you trying to export, the book? That option is not available from the book mode. Only from albums, slideshows or the main library. Did you do the export from a slideshow you made of the photos used in the book?
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Lightroom corrupting RAW files? Hardware issue?

I've started having some issues with RAW files being corrupted when I open them in Lightroom. I've done a lot to troubleshoot and narrow down the symptoms, and here is what I can tell you. If anyone has any ideas for how to solve this, I'd really appreciate it!
Equipment
Canon 7D, 1 32GB CF card, 1 4GB CF card
Lenovo Laptop, Win 8; Lightroom 4
Dell PC, Win7, Lightroom 5
Here's what the corruption looks like in my Library view. Note that all of the photos are the same. I just rapid-fired a bunch of shots down the hallway to test this out.
I first noticed the corruption on the PC, pulling photos from the 32GB card. I bought a new hard drive (SSD hybrid), installed a clean version of Windows 7, and upgraded to Lightroom 5, then the 5.3 update. I re-downloaded some photos from the 32GB card, and they still show up corrupted. So here is my further testing:
I shot a series of photos like shown above on the 32GB card, downloaded them on the laptop with a new USB cable. The photos look good.
I shot a series of photos on the 4GB card, downloaded them to the laptop with the same cord, they look good.
I imported the same photos photos from the 4GB card and from the 32GB card on the PC with my existing Lighrtoom Catalog and they are corrupted.
I created a new Lightroom Catalog on the PC and downloaded the same photos from the 4GB card and from the 32GB card on the PC and they are corrupted.
So what gives? I think we can rule out corruption or issues on the hard drive, the OS, the USB cable, and both of the CF cards. It baffles me that a new HD, clean OS install, new catalog, new USB cable, and upgraded Lightroom haven't solved the problem. Is it possible that there is some other part of the hardware on my PC which is corrupting the files?
I'd love some insight if folks have any ideas!
Thanks,
Adam

Was this ever figured out AdamCohn? I have a very similar issue. I have actually watched two photos over the last two days become corrupt while viewing them in Lightroom. I am not suggesting LR is the cause (as I know this is almost always hardware related) but it has happened right in front of my eyes while LR is interacting with the images (I believe).
Scenario:
Images were
* Imported into LR on different days (about a week apart)
* Imported to different hard drives during import (one an SSD, another to a typical HDD)
* Behaving normally in LR until corruption (i.e. previews were built without issue, was able to develop and export images. Showed fine in Finder).
After viewing the images in Loupe view and watching them flip instantly to a visual mis-mash similar to what you showed the images were permanently screwed. The appear the same way in Finder and in Photoshop
I have not noticed any other issues in any other app or area of the system. Everying seems to be running smoothly.
Troubleshooting:
* Memory tests:
- Built-in Apple memory test (normal + extended).
- MemTest (as described here: MemTest for Mac OS X Tests your RAM). Ran it twice, all tests passed.
* I am running some HDD checks now, but with the two images being on two different drives I suspect the likelihood of this being a drive issue is extremely small.
Suggestions?

Settings Get Zeroed out after File Export

I just noticed that out of a group of about 110 JPGs I was editing tonight, about 5 of them had their Develop Settings zeroed out after I exported the files.
Examples:
1. One file's Fill Light went from 14 to 0 after File Export.
2. Another file's Fill Light went from 17 to 0 after File Export.
3. Still another file's Black went from 3 to 0; its Brightness went from +5 to 0; it's Contrast went from -1 to 0....all 3 things on the same file zeroed out.
4. Still another file's Black went from 1 to 0, and its Contrast went from -3 to 0.
5. Another file was rotated by .28. After exporting, the rotation in the history went from .28 to 0.
One other problem I saw with at least 2 of these files (different than the 5 above), I had created virtual pictures for these 2 and exported them as TIFFs to Photoshop CS3. After the TIFF file was updated with CS3, it automatically was reimported to LR. There is no "Import" listed in the history, nor is there any "Created Virtual Copy" in the history.
I don't think I'm doing anything wrong; again, there have only been 5 out of about 110 JPGs for which as happened.

I think I have that box checked, but I'm not sure where to find it. I seem to recall having checked something like this before, but, again, I just can't
seem to find where it is. I've checked in Preferences and do not see it, as well as other places.
Anyway, I do not export files to CS3 very often, but I know that every time I do, the edited file gets added back into the LR Catalog when I close out the file in Photoshop CS3. I typically export these files to CS3 keeping the LR adjustments.
I originally had this set of images sorted by File Name. I did that because within this set are pictures taken from 2 different cameras, with two completely different types of file names. I wanted only to work on the images from one camera at a time. While sorted by File Name, the edited file does get added to the Catalog, stacked upon the original file....so, yes, they are side by side.
I did try sorting by Capture Time, but that didn't make any difference.
Because my other problem of settings being zeroed out appeared to be "fixed," I was hoping this problem also would be fixed. But when I tried the same procedure as last night (only with the files sorted by Capture Time instead of by File Name), the same thing happens...there is no "Import" listed in the History panel.
What has been "fixed," however, is that for those few files that I made a Virtual Copy of, the History panel now shows "Create Virtual Copy." I did not do anything to these files. Perhaps the reboot of my computer fixed this. I really don't know.
As mentioned, I do not export files very often to CS3, so this problem may have always existed (not showing "Import").
Thanks for your reply....I'll watch for more in the future, but because the problem happened again this morning, I think it is perhaps a software bug.

Corrupted image files in Lightroom?

I opened up Lightroom this morning and noticed that some of my files from a recent shoot look like this:
Are they corrupted?
If so, how does that happen? I've never seen this before and I have thousands of images in LR.

Thanks. I read through a few of the other threads. I found one comment that might be applicable to my situation:
Good - most often this tell-tale/signature-looking corruption is due to hardware - transfer hardware if corrupt upon first rendering (true raw rendering, not initial preview display), hard disk if corrupt after first rendering. And sometimes ram.
I think this may have had something to do with how I got these files onto my computer. I shot the pictures while visiting family. I had my Macbook Pro with me, which is not my main image editing machine. I imported the files into LR4 on the MPB from the 5D3 using the USB cable.
When I returned home, I moved the files from their location on the MBP to a USB flash drive, and then imported them from the flash drive to LR4 on my Mac Pro (which is my main image editing machine).
The corrupted images are only from this group. So I'm hoping that it was the transfer to and from the flash drive that caused this, especially since I've never experienced it before and don't see it in any of my other images.
Fingers crossed!

Corrupt audio file prevents me from opening Logic project file

Hello,
I've been running Logic 8 for a couple years off my MacBook and have never encountered any significant problems of file corruption until recently.
The issue I encountered is this:
I've been producing a lengthy track in an on-going Logic project file for some time and after completing a recording session I saved and started deleting excess track copies to clean up my arrange window. Upon doing so Logic unexpectedly crashed.
After attempting to reopen the project file, it started its normal process of loading its respective audio files, but now it hangs on one particular audio file indefinitely (I'll refer to it as 'audio file x' for ease of reference), freezing and crashing Logic as a result. All of this project file's auto backup files are also incapable of being opened without giving me the same result and crashing Logic.
I have no way of opening this project file and getting at my most recent saved sequence!
I've tried removing this corrupt 'audio file x' from the project's audio folder and dragging it to the desktop, but this had no effect and I still can't open any recent version of the project file.
Older saved copies of the current project file do still open though (most likely because they were saved prior to the corruption caused by this suspect 'audio file x.') When opening an earlier iteration of the project, I get a message '1 invalid audio region found' (I assume referring to the corrupt suspect 'audio file x' that I removed to the desktop) but the project file is still able to open.
I realize I could import the audio files from the most recent version of the crashed file to an older project version and reconstruct things back to the way they were, but it would take me a lot of time and I'm hoping there may be some way to recover the un-openable project file by getting it to stop looking for this corrupted 'audio file x' on startup.
When I click 'show package contents' of the Logic Project file, I notice two items labeled 'displayState' and 'documentData.' From my troubleshooting I've come to the basic understanding that the 'documentData' file contains all the sequence data and settings for its respective Logic Project file.
I think the 'document data' of the unopenable project file in question may be corrupt because whenever I replace it with the 'document data' from an earlier Project file version, the file is able to open. This doesn't do me much good though, because it's document data from an earlier iteration of the project and I need to be able to get at the current sequence I had right before my file crashed.
Is there anyway to open a project file without letting it load its audio files? Or is there anyway I could get inside the 'document data' file to delete the reference/pathway in its audio bin to the corrupt 'audio file x' its hanging on?
Any insights would be greatly appreciated. I'm hoping there's some way I won't have to repeat a couple days worth of work. Thanks for your help!

stooby3535 wrote:
After further troubleshooting I've realized that the suspicious audio file that prevents the project file from opening is actually not corrupted itself. I can still play the audio file in other media software like Quicktime, etc. with no problem.
This leads me to believe the problem opening the project file lies solely with the corrupted 'documentData' file.
Does anyone have any ideas about how I could somehow open this project file and delete the reference of the troublesome audio file from the project's audio bin?
Well... it really sounds like the project itself is corrupted, that's one of the reasons all project files won't load from a certain point on.
Try this.
Reboot the Mac.
Open the Applications folder and boot Logic from it's icon.
As soon as the Logic Logo/graphic window appears on the screen hold down the control key. You will see a message pop up that says something like "Launch the Core Audio Driver" there will be yes/no choice available... select NO.
Go to the File menu and selct "open" go find your project file and see if it will open. If it does.. delete the audio file in question... however.. I would also look at any plugins you recently installed and are possibly using in this project...this sounds more like a plugin problem rather than an audio file problem, but that's just a gut feeling.
Anyway, if it opens delete whatever you suspect and save under a different name.
Reboot Logic and see if it can load the project.
pancenter-

Transition Corruption Upon File Export

Similar Messages

Maybe you are looking for