Lightroom 5 import failure

Hi all - I have just purchased Lightroom 5.3 as an upgrade from 3.6. On my first attempt to import any photos, nothing happens - either from a camera card, USB device, or trying to import from either of my hard drives, yet I can still import using my trusty old LR 3.6. I am running a HP i7 laptop with Windows 8. When I say nothing happens, no previews appear and so I cannot move forward. Any clues? This is my first time asking a question so hope someone is out there.
Cheers
Lothlarien

Hi Lothlarien,
lothlarien wrote:
no previews appear
So, the import dialog box comes up, but the thumbnails are all gray? (black? white? no "slots" for the thumbnails? not talking about thumbnails? import dialog box not coming up / talking about something else...).
If the import dialog box does come up, I think a screenshot would help us visualize the problem better.
Rob

Similar Messages

Premiere Elements 9 PC: Major Importer Failure

I think that I have gone down every troubleshooting road on trying to discover why "all of a sudden" Premiere Elements 9 PC will not import anything via Get Media/Files and Folders into its Organize interface as is its default behavior. The program fails at that point and shows the message "the program is not responding". Yet if you force the closure of that particular project and reopen a new one, you find that those media that failed to import into Organize in the first project now are live and well in the Organize of the new project. You can drag them from the Organize to the Timeline and use them in this new project. All other functions of Premiere Elements 9 PC appear unaffected by this import failure. AND, source media can be video (any format and size) and photos (any size). This happens even with import of the first and only file being a jpg (800 x 600 pixels).
My history of Premiere Elements 9 PC/baddrivers.txt file/ and "incompatible driver messages" is well documented in these forums. That involved Windows XP Professional SP3 32 bit and a NVIDIA display card. And, I have been moving along successfully with Premiere Elements 9 PC for several months. About two weeks ago, I upgraded my computer to Windows 7 Professional 64 bit Intel Graphics Card, and Premiere Elements has been performing great until yesterday when what I call "major importer failure" struck. The computer has about 800 GB free hard drive space and about 2.5 GB out of 4.0 GB of available RAM. All of this worked great for about two weeks and now suddenly this yesterday. Did I do anything different or unusual? I think not. I also have Premiere Elements 7 and 8 on this same new computer, and they continue to function perfectly in all respects, whereas Premiere Elements 9 does not. AND, yes I have had the Premiere Elements 9.0.1 Update installed and in use before and after the importer failure.
Troubleshooting has included
a. Uninstall/Reinstall from Premiere Elements 9 installation disc + uninstall/reinstall of QuickTime + Photoshop Elements 9 as well.
b. System Restore (as well as a restore of an earlier version of the installed Premiere Elements 9.
c. Removal of possible interferring program, such as, Nero InCD.
d. Removal of recent Windows Updates
e. Uninstall/reinstall of Intel driver since at one point in the failure the Edit Mode Monitor was displaying part of the Disc Menu Section while the program was in the Organize Mode.
f. Have looked at permissions, running as Administrator, etc.
One of the things that I will try this morning is installing Premiere Elements 9 PC on the previous system Windows XP Professional SP3 32 bit to see if there is any major importer failure there at this time.
If anyone has the time, I would appreciate any comments on a troubleshooting avenue that I may have overlooked. This appears to be another Deja Vu all over again. I hope not.
Thanks.
ATR

Neale
Thank you for your interest in this issue.
I still have not pin pointed why my Premiere Elements 9 works great EXCEPT it will not import media into the Organize with Get Media/Files and Folders and attempts to do that drive the program into unresponsiveness and extreme difficult closure, even with the Task Manager.
Yes, I have already looked at the workaround that you suggested for moving forward in my Premiere Elements 9 PC project, that is, entering all my source media into the Elements Organizer (can do from Photoshop Elements side) so that the source media thumbnail will be in the Premiere Elements Organize "ahead of time", and I will not have to depend upon Get Media/Files and Folders to get that job done.
But, until I hit the key to this, I think I have an almost perfect better way. My computer is now Windows 7 Professional 64 bit that comes with the Windows XP Mode. Essentially what you have in this mode is a virtual Windows XP Professional SP3 32 bit machine (best I can determine, Microsoft Generic Card). I can install Premiere Elements 9 (same serial number as on the Windows 7), and IT WORKS, no problem with the Get Media/Files and Folders. The one glitch in this perfect solution is setting up to burn to DVD. The Windows 7 Windows XP Mode Virtual Machine will not recognize installed internal DVD/CD drives when you go to write a DVD. The explanation is that the optical drive in XP Mode is a virtual device - read only. I have confirmed this. In order to use Premiere Elements 9 PC burn to disc in this Windows XP Mode , my answer here appears to be plugging in an external DVD burner USB and then using the USB Attach of the Windows XP Mode.
When Premiere Elements 9 PC was released, I was forced into much troubleshooting of the display issues which are very widely documented here. But then I was using "a real" Windows XP Professional SP3 32 bit" with a NVIDIA card. In the trial version, the BadDrivers.txt and VideoRenderer.dll got me through that episode. For me, the purchased version "essentially" was not afflicted with these same problems, and it has been running great. Now when I go to a new computer system for better performance/greater computer resources (by the way, Intel HD Graphics card), Premiere Elements 9 runs great for two weeks and then this no Get Media/Files and Folders matter sets in accompanied by program going completely knocked out by the event. In all of this, old or new, I have Premiere Elements 7, 8, and 9 installed on the same computer. While Premiere Elements 9 is being hit with these issues, Premiere Elements 7 and 8 are not , same computer environment, same source media, same project preset, et al. For me, the Premiere Elements 9.0.1 has not hit the mark.
I have done extensive troubleshooting of the this current matter, too long and involved to go into now. I am preparing a full detailed description of the issue and the troubleshooting that went into the search for a fix. I will be posting it at the forum that I frequent. When I post it there, I will supply a link to it for whomever is interested. I have filed a bug report with Adobe on this matter in abridged format as per the space provided in its bug report online form.
Thanks again for posting.
ATR

Solution Import Failure Message: Cannot add a Root Component 'GUID' of type 29 because it is not in the target system

Hi all,
Please refer to the error:
Root Components import: FAILURE
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Exception |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Error |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | CrmException..ctor
ilOffset = 0x30
at CrmException..ctor(String formattedErrorMessage, Int32 errorCode, Object[] arguments) ilOffset = 0x30
at ImportRootComponentsHandler.GetSolutionRootsCollection(Boolean throwIfMissing, Boolean skipRibbonCustomization) ilOffset = 0x209
at ImportRootComponentsHandler.ImportItem() ilOffset = 0x8
at ImportHandler.Import() ilOffset = 0x43
at RootImportHandler.ImportAndUpdateProgress(ImportHandler ih) ilOffset = 0x7
at RootImportHandler.HandleNonMetadataHandlers(String[] ImportEntities, ImportHandler& ihForCurrentPath) ilOffset = 0x33
at RootImportHandler.RunImport(String[] ImportEntities) ilOffset = 0x1D8
at ImportXml.RunImport(String[] ImportEntities) ilOffset = 0xE
at ImportXml.RunImport() ilOffset = 0x5BF
at ImportXmlService.ImportSolutionSkipCapable(Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Byte[] customizationFile, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies,
ExecutionContext context) ilOffset = 0x46
at RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) ilOffset = 0xFFFFFFFF
at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) ilOffset = 0x25
at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) ilOffset = 0xCF
at LogicalMethodInfo.Invoke(Object target, Object[] values) ilOffset = 0x4F
at InternalOperationPlugin.Execute(IServiceProvider serviceProvider) ilOffset = 0x57
at V5PluginProxyStep.ExecuteInternal(PipelineExecutionContext context) ilOffset = 0x200
at VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context) ilOffset = 0x65
at Pipeline.Execute(PipelineExecutionContext context) ilOffset = 0x65
at MessageProcessor.Execute(PipelineExecutionContext context) ilOffset = 0x1C5
at InternalMessageDispatcher.Execute(PipelineExecutionContext context) ilOffset = 0xE4
at ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode,
Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)
ilOffset = 0x16E
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, UserAuth userAuth, Guid targetUserId,
OrganizationContext context, Boolean returnResponse, Boolean checkAdminMode) ilOffset = 0x1F1
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset
= 0x2D
at OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset = 0x26
at InprocessServiceProxy.ExecuteCore(OrganizationRequest request) ilOffset = 0x34
at PlatformCommand.XrmExecuteInternal() ilOffset = 0xF6
at ImportSolutionCommand.Execute() ilOffset = 0x20
at DataSource.ImportSolution(Byte[] customizationFile, Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies, IOrganizationContext
context) ilOffset = 0x0
at SolutionImportProcessPage.ImportSolution() ilOffset = 0x123
at SolutionImportProcessPage.ProcessRequestData() ilOffset = 0x4A
at SolutionImportProcessPage.ProcessAction(String action) ilOffset = 0x92
at AppUIPage.OnPreRender(EventArgs e) ilOffset = 0xD
at Control.PreRenderRecursiveInternal() ilOffset = 0x54
at Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x6D3
at Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x3C
at Page.ProcessRequest() ilOffset = 0x14
at Page.ProcessRequest(HttpContext context) ilOffset = 0x33
at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() ilOffset = 0x18D
at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ilOffset = 0x15
at ApplicationStepManager.ResumeSteps(Exception error) ilOffset = 0x10A
at HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) ilOffset = 0x5C
at HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) ilOffset = 0x16A
at ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType) ilOffset = 0x4B
>Crm Exception: Message: Cannot add a Root Component 0ffbcde4-61c1-4355-aa89-aa1d7b2b8792 of type 29 because it is not in the target system., ErrorCode: -2147188705
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Platform.Sql |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Info |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | BusinessProcessObject.ExecuteNonQuery
ilOffset = 0x28
I am getting this coming up in the error log when I attempt to import an unmanaged solution.
After searching on google Type 29 refers to a workflow.
I go into the source system and query the database by the GUID and discover that it is actually a Business Process Flow called 'Phone to Case Process'.
I do not have this process in my target system as I deleted it.
Looks like this is one of the out of the box ones. I don't think we we have changed this one much.
What does this mean and what should I be looking for??
Anyway how do I remove this offending process from the unmanaged solution xml file and attempt to re-import it?
It doesn't look like I can generate the solution again without the offending workflow/process..

I managed to resolve this issue after looking at this thread:
https://social.microsoft.com/Forums/en-US/fddff17f-1cca-4d33-a666-60c08ad76b0c/crm-2011-import-failure?forum=crmdevelopment
Just modify both solution and customizations xml by searching for the guid and removing the root component

File Import Failure with Adobe Premiere Elements 11

I've just installed Adobe Premiere Elements 11 on my Windows computer. I have started a video project, saved it and when I tried to re-open it I got this File Import Failure message "This type of file is not supported or the required codec is not installed". What do I do? Thanks for your help!!

I've just installed Adobe Premiere Elements 11 on my Windows computer. I have started a video project, saved it and when I tried to re-open it I got this File Import Failure message "This type of file is not supported or the required codec is not installed". What do I do? Thanks for your help!!

My Images won't open in Photoshop CS5 when I click on Edit in Lightroom - even though this option has been selected? To edit in Photoshop I have to export image from Lightroom then import into Photoshop. I have other programmes such as NIK and if I wish

My Images won't open in Photoshop CS5 when I click on Edit in Lightroom - even though this option has been selected? To edit in Photoshop I have to export image from Lightroom then import into Photoshop. I have other programmes such as NIK and if I wish to edit in these everything works fine.

Same here. I've never had trouble with this function before.
It opens the Photoshop application with all the menus/windows, but it never opens the actual image I chose to work on.
I'm on a Mac, using OS X Yosemite, 10.10.1 Lightroom is version 5.7 Photoshop is CS5, version 12.0.4
FWIW, I also can't automate>Photomerge ... . Makes me think Photoshop, not Lightroom, is all wacky. I tried dumping PS preferences

Lightroom 4 importing causing program to crash.

Lightroom 4 will not import files. Windows 7 pop-up states; "there is a problem with this program that is preventing it from running correctly will check for solution". "Windows failed to find a solution must shut down program now".
This prevents the import page from loading or working and no images can be imported using usb or SATA connections. Was able to use computer's built-in card-reader to read from Sd and compact cards, those were able to run in the import window only because of preference setting. "when a Memory card is installed import files" (preference-setting). Any other means of importing files, the out-come is the program crashing and being shut down. All other functions outside the import menu seem to be working. Deleting all catalogs and then using the default catalog setting, failed to clear issue.
System info: Windows 7 64-bit, Intel i7 cpu, 16 gigs of ram, 4 one terabyte hard-drives.
Solutions tried. Removing Lightroom 4, all catalogs, then running defrag, registry cleaner, before attempting to re-installing lightroom 4. Removing lightroom 4 and installing lightroom 3.6 fails to fix issue. Removing all Lightroom products from hardrive,Including the windows program folder, windows programs data folder. Then rebooting re-running defrag, registry cleaner and re-installing lightroom 4 fails to fix importing issue. No way to contact support and links to user group fail to take me to correct user group. Question with the lead as lightroom 4 importing causes program to crash. Takes me to everything but lightroom solutions! Now this takes me to photoshop user group which has nothing to do with lightroom. With lightroom 4 in the question itself, I get everything but lightroom solutions!

Camera raw is built into Lightroom. It is the engine that makes the corrections within an image. You might not see as a seperate program, like earlier versions of Lightroom. Or having to launch it in a new window to work in camera raw. In version 4 of Lightroom it was made seamless and built into Lightroom.
Lightroom 4 was installed in the admin log-in window. I have all useage rights to any file lightroom creates or adjusts. I am thinking that the Photoshop CS6 beta created some working problem within Lightroom 4. Now that the beta-test program is over, I think the problem is a result of removing Photoshop's last build, before the public beta was released. I do hope, Adobe is working on a solution for people experiencing importing problems with Lightroom 4. I am just grabbing at straws here, trying to find something that will work. I think the problem will go away once computer has the new camera raw build 7.0 that ships in Photoshop CS6. With so many versions of camera raw installed on the computer, I think Lightroom is having issues as a result. Let's hope a patch is in the works, Lightroom 4 is useless if importing files doesn't work correctly.
B&H photo is taking pre-orders for the creative suites, right now. The only way to get support is by purchasing a subscription. Otherwise it is a $35.00 per issue fee. So, I am not sure of what upgrade path I will take. Not loving the cloud at all, with this year of Hackers, I seriously doubt that any cloud will prove to be safe to use. Why would, I want to post my hard work to a cloud where anyone can steal it? But that is a different topic.
For right now the only way to import is by creating an empty folder on the same hard-drive that Lightroom resides on. Setting up auto-import in Lightroom Pref. file to check that empty folder. Folder has to be empty to set up. Then dragging image files into that empty folder. I discovered that Lightroom 4 will not open or look in sub-folders for images. Which means you lose keeping a day's worth of shooting seperate from other folders. Where Lightroom version 3.6 you could.There was a second auto-import that worked, with my built-in memory-card reader. Where in the Lightroom pref.file you can tell Lightroom to auto-import, when a memory-card is detected. ( this is the least viable option, because more memory card become damaged removing and reinstalling them). These were the only two methods, I could get images into Lightroom 4 and prevent Lightroom from crashing. Might have to go back to using Nikon NX to import my images and using Bridge to catalog them.

"File Import Failure Unsupported format or damaged file" in CS6 but fine in CS5.5

Hello All.
Recording in Pal DV AVI from Sony Z5U with MRC1K compact flash recorder.
Imported files to computer using the Sony utility, and also tried dragging and dropping.
Some files import to Premiere Pro CS6.03, but others give "File Import Failure: Unsupported format or damaged file,".
The files that do import show up as 4:3 and I have to modify / interpret footage to get them to show as 16:9,
However, these same files play back just fine in Windows Media Player.
Intriguingly these files import just fine to Premiere Pro CS5.5, and also show up correctly as 16:9.
I can't figure out why some files import into CS6 and others don't....
Anyone else seen this kind of behavior?
(Normally I record in HDV and I've never had problems importing from MRC1K into Premiere, but the client specifically requested DV files for their ease of editing...)
Cheers
Mark
PS When I use the DV recoverer utility on these files they import just fine into CS6....

Hi Jim,
OK, here's the video that imports OK into CS6.03 but that Premiere CS6.03 sees as 4:3:
And here's the one that won't import into CS6.03 but is happily opened by CS5.5 and correctly seen as 16:9:
Can you spot the difference? Thanks for having a look at this.
Cheers
Mark

File import failure in premiere pro on specific files

I have installed the latest version of Premiere Pro CC 2014. I am trying to import several video files that i have recorded on a Canon 5D Mark III. The problem is that while some of the files gets successfully imported, many files cant import because of a error message, file import failure. Unsupported file format etc. I have tried to open this in many media players, and all work fine there. I have even imported these files on the same Premiere Pro-version on a different machine, and there they work perfectly. But on this machine some files just wont open. Does anybody have a clue or tips on how I can fix this? I guess its a problem within the software.

It just seems to pick certain files and reject them.
Which ones does it eject? eg do they have a different file extension from the video files.
Are they rgb?

Lightroom PSE6 Import

I wish to move from Photoshop Elements 6 to Lightroom (1.3.1) running on Windows Vista. However I can't get Lightroom to import the PSE6 catalog. From what I can make out PSE6 uses a different catalog format from PSE5 and LR doesn't seem to recognise this.
I find it hard to believe that that the latest version of LR can't import from the latest version of PSE. Does anyone know how to make this work (even if it involves exporting the PSE6 catalog first)
Note: I've 20,000+ photo's in PSE6 and make use of the Album's feature to sort them, hence the need to import the catalog rather than simply importing the files
Regards
Mike

i have a real problem with your advice .
i took it and when i opened LR all my images had gone !!!!
the good side of this is that my back up was up to date.
any other suggestions ?>????????

I have a subscription on Adobe cc and I am trying to instaal it on a second pc. Lightroom ok, but failure 47 on Photoshop. I also get the message that I downloaded a trial version, but as I said I am already a customer. What to do?

I have a subscription on Adobe cc and I am trying to instaal it on a second pc. Lightroom ok, but failure 47 on Photoshop. I also get the message that I downloaded a trial version, but as I said I am already a customer. What to do?

Han,
You should be able to install CC on a second computer, licensing rules allow you to install on two computers.
Please first try signing out and back in: https://helpx.adobe.com/creative-cloud/kb/sign-in-out-creative-cloud-desktop-app.html
If you open an application that's part your Creative Cloud membership and you see a message stating you're running a trial, see this link:
Creative Cloud applications unexpectedly revert to trial mode | CS6, CCM
Pattie

Quicktime file import failure in CS5 After Effects and PPro

Running a Dell PC with a fresh install of Win 7 Pro, Intel Quad Core 2 with 4GB. Ram.When I try to import quicktime files into AE or PPro, I get a file import failure or corrupted file message. I am using quicktime version 7.6.6. I have tried uninstalling and removing all preferences, then reloading older versions of quicktime (7.2) rebboting the machine, and still no luck. Any tips would be appreciated. I have not been able to get any help from Adobe. I have a laptop setup the same way and it works great. I even tried loading the exact same versions of qt. and tried to use the Importerquiktime.prm file from that machine.

I appreciate the feedback. I checked the processes upon AE start and found that the Adobe QT server32 starts then closes in the processes before AE actually loads up. If it is supposed to remain open, it does not. I can not find where to change its permissions. I looked the site you sent a link to, but do not see that section.

Media offline / file import failure

Hi,
I have my project created in Premiere CS6. Now i updated to CC.
In my project, i imported a really short AE file into my Pr timeline. The whole vidieo worked fine.
Now I just noticed that media (AE file) was reported media offline in Premiere CC.
OK, I tried to locate the media from the folder where i keep the file.
Can locate the file but hitting "ok" button won't let me select the file.
Ok, I treid to rename the AE file. Imported the file in Pr, but Pr says file import failure.
Anyone come across this problem.
Not sure if this's because of version CC. My AE file is there. Nothing has changed.
Just don't know why I can't relocate and import the file.

HI abhishah,
Thanks for posting on adobe forums;
Please provide me following details
Premiere pro CC or CS6
What is the OS and version ?
What is the Graphics Card installed on the system ?
How much Ram do you have ?
Do you use any external Hard Drive ?
and please try to copy the media file from the one location another without media, and make the media offline and save the project as a new project and try to open the new one, then try to link the media.
Thanks
Sandeep

Mxf File import failure

Dear All,
I have a problem to import files in CS4 from a Sony PDW-U1(MPEG2 HD 50CBR_1920_1080_422P@HL" formatFps="50i") on my new HP Quad Core 4600.
The error message: file import failure "Unsupported format or damaged file" but is not damaged.
The PC don't have a capture card and I don't need it, I just want to import the mxf and edit it on the timeline then encode in flv.
Someone have an idea?
Many thanks
Claudio

MainConcept sells a fairly expensive PP plugin that supposedly will read the Sony XDCAM HD 422 50 mbps MXF files. I downloaded the demo, but I could never get it to work right, because according the MainConcept, it won't install correctly if you have both CS3 and CS4 components installed. Maybe your luck will be better:
http://www.mainconcept.com/site/prosumer-products-4/xdcam-22351/information-22391.html

File Import Failure

I just tried to open a video I have been working on in Adobe Premiere Elements 11 editing software and I got an error message saying "File Import Failure. The type of file is not supported or the required codec is not installed." How do I fix this so I can get access to my file again? Thanks!!

Do you get the "Missing CODEC, or file not supported" error message upon Import?
If so, this FAQ Entry might be helpufl" http://forums.adobe.com/thread/1050730?tstart=0
Good luck,
Hunt

5.1 WAV Import Failure

If I try to import a 5.1 Wav file into Premiere CS6 which was exported by Audition CS6, I get an Import Failure Error:
The file will also not play in Windows Media Player. Does this work for anyone else?
Terry

Hey Bill,
It's a 5.1 .wav file and although I pasted a screenshot of the error in my post, apparently those don't get through. Premiere's message was that it has a header error. Nothing more useful than that.
Terry
Sent from my iPad

Lightroom 5 import failure

Similar Messages

Maybe you are looking for