Selected file cannot be linked because its type (video) does not match the original file's type

I've been using Premiere Elements 9 for a couple of years now, and a few months ago I began having problems importing AVI files created from a BlackMagic Intensity Pro capture card. (These issues were not previously occurring, and since they surfaced, I have exhausted the various settings for the BlackMagic card, used various software such as BlackMagic's own Media Express as well as the freeware VirtualDub, and still have the following problems.)
In addition, these AVI files play just fine, in their entirety, using Windows Media Player and in Quicktime.
The problem (or possibly two, but I suspect they could be related) is that most of the AVI files I attempt to import will either (1) import all video and NO audio, or (2) import ONLY a short segment of audio and video, and the length that Elements imports varies. Usually only in the range of a minute or two. The rest of the file is not imported at all.
After much digging in forums, and testing various settings in trying to figure out the issue, I decided to back up all of my files and completely wipe all hard drives and start over with a fresh installation of Windows and Premiere Elements 9. I haven't installed much else yet, as I wanted to first find out if the reinstallation improved things with Elements.
For the first project I created in Elements after the reinstallation, Elements successfully imported an entire AVI that was nearly 2 hours long, audio and video. This was a file that previously would not import properly into Elements. This suggested that my earlier installation of Elements must have been corrupted somehow. At this point I was very hopeful that all was well.
I proceeded to edit the video as I had wanted, saved the project, and exported it to an MPEG format file. I had originally wanted to export it as an MOV, but I hadn't yet installed Quicktime, so Elements couldn't do that just yet. The MPEG export was successful and plays fine.
However, I then installed Quicktime, and once it was finished, I restarted the PC and reloaded the same project. This time, Elements claimed the media was offline. I double-clicked on a segment of the video, and directed Elements to the raw file, but then an error message popped up: "The selected file cannot be linked because its type (video) does not match the original file's type (audio and video)." This was the same file I had JUST edited and of which I created an MPEG.
I tried creating a new project and the "Get Media" function to import the AVI again, but this time only the video imported with NO audio. (This would explain why the error message said what it did, but not why the audio wasn't imported.)
What in the world is going on with Elements??? I am baffled since the ONLY task I have done on this machine after a complete reinstallation of both Windows and Elements is edit one AVI. I find it very hard to believe that just installing Quicktime caused this.
Some info on my system:
System: Asus P6T w/ Intel i7 920 and 12 GB memory
OS: Windows 7 Ultimate
Video Software: Premiere Elements 9
Capture Card: BlackMagic Intensity Pro (PCI-e)
Capture Software: AVIs recorded with either BlackMagic Media Express or VirtualDub (only prior to the reinstallation, as neither of these programs are currently installed)
I'm getting to the point with Elements that I might need to just abandon it and find something else that is more reliable. Anybody have suggestions to help with this, so I won't have to migrate?

mtnsports
We think that we need to start off with definiting the properties of these .avi files that you are importing into Premiere Elements 9.0/9.0.1 (assumed that you are working for the required 9.0.1 Update).
You say that the "avi" was created from a "BlackMagic Intensity Pro capture card". What are the properties of this .avi that you imported into Premiere Elements? Not all .avi are created equal. What is the video and audio compression, frame size, frame rate, interlaced or progressive, pixel aspect ratio, typical duration?
Based on the properties of the video what have you been setting as the project preset?
Let us start here.
More later.
ATR

Similar Messages

CS5 The selected file cannot be linked because its type (audio) does not match the original file's t

Greetings,
I have been working on a very large project using CS5 on my desktop computer. Now I am on the road and bought a laptop so that I can continue to work. I placed all of my assets on a back-up external 2tb drive (which I was able to open without incident on my desktop). I installed CS5 on my new laptop and now when I try to open the project I get the following message "The selected file cannot be linked because its type (audio) does not match the original file's type (audio and video)". This message appears before I indicate the path to any of the assets. Then, when I do indicate the path to each asset, I get the same message for individual files.
Any advice is appreciated.
Thanks,
Jeremy

I had this problem and have found a solution / workaround: my issue was when trying to open a cs5 project that had been collected on mac and then transfered to pc, my footage was all png image sequences but this will hopefully work in other situations...
Open the project and cancel the first dialogue box that pops up where you get the "file cannot be linked" error when trying to reconnect footage. The project will open and then in the project panel, right click on any footage that needs reconnected and choose "Replace footage..." this will open a dialog that will allow you to select the file that gave you the error in the first place without any issues. Any sequences with that footage will now work and everything show be all good.
You may experience "Offline material is present in this export and will be encoded using the offline media graphic" on first export but apparently you can just ingore that, but i guess it's woth testing a few short sections before commiting to a huge render...
This workaround isn't perfect as i had about 50 pieces of footage i had to relink via this method one by one but at least it saved redoing the edit which was critical for my project...
good luck!

CS6 The selected file cannot be linked because its type (audio) does not match the original file's t

I understand there is another posting in this forum with the same error happening on CS5 and their solution had something to do with Quicktime. Mine has nothing to do with this.
I ran into this exact same problem in CS6 and I found that the issue is because I renamed the root project folder. My folder structure is like this:
Drive C:\
-> [root project folder]
-> [folder containing videos]
-> MyProject.prproj
By renaming the root project folder, I was no longer able to open up the project successfully. It would get to certain clips and ask about where the clip was located. Trying to re-link it to the correct file would result in that error (which makes no sense if you think about it).
So my question is, is it intentional that the absolute folder paths are saved into the project file rather than relative paths? Does it not make more sense if paths were saved relative to the root project path? That way the root project folder could be renamed to whatever you want and it would have no effect on the project itself.

I had this problem and have found a solution / workaround: my issue was when trying to open a cs5 project that had been collected on mac and then transfered to pc, my footage was all png image sequences but this will hopefully work in other situations...
Open the project and cancel the first dialogue box that pops up where you get the "file cannot be linked" error when trying to reconnect footage. The project will open and then in the project panel, right click on any footage that needs reconnected and choose "Replace footage..." this will open a dialog that will allow you to select the file that gave you the error in the first place without any issues. Any sequences with that footage will now work and everything show be all good.
You may experience "Offline material is present in this export and will be encoded using the offline media graphic" on first export but apparently you can just ingore that, but i guess it's woth testing a few short sections before commiting to a huge render...
This workaround isn't perfect as i had about 50 pieces of footage i had to relink via this method one by one but at least it saved redoing the edit which was critical for my project...
good luck!

Need help urgently!! - "The selected file cannot be linked because its type (video) does not match t

Hey guys... I need your help!! I started a project using Premiere Pro 2 and was 80% when I formatted my computer (all my project files were always saved to a external hard drive). Anyways instead of installing Premiere Pro 2, I installed Premiere Pro Cs3. Problem is whenever I try starting up my project it asks me to link every file used. When I do this it says "The selected file cannot be linked because its type (video) does not match the original file's type (audio and video)." I took my external harddrive to friend's house who has Premiere Pro 2 and it says the same thing. Why did this happen? Is there anyway around it... Any help would be greatly appreciated, I put over 20 hours into editing this movie... I don't want it all to go to waste.

Frequently answered question
Cheers
Eddie
Forum FAQ
Premiere Pro Wiki
- Over 250 frequently answered questions
- Over 100 free tutorials
- Maintained by editors like
you

Error message 'the selected file cannot be linked because it has 2 audio channels and the clip was created with 1 audio channel'

Can anyone help with the error message I'm getting 'the selected file cannot be linked because it has 2 audio channels and the clip was created with 1 audio channel'. I had to move the footage to another folder and now am unable to link it - just getting this error message instead.... Has anyone had to deal with this before?
Thank you!

Relink to the correct media.

JNI generated header file does not match the class file

We have had a JNI project for many years and all has been fine. Within our libraries we have several classes that have inner enum classes.
Recently we have moved to JDK1.7. Up to now when JNI generated the methods where the signature used the inner enum class, and it was an oveloaded method, we would get something like the following as the signature:
Java_PackageName_ClassName_methodName_OuterClass_00024InnerEnum_2
And the class file result of the build would look like the following:
methodName(OuterClass$InnerEnum)
Since we have moved to JDK 1.7 the header file looks like the following:
Java_PackageName_ClassName_methodName_OuterClasss_InnerEnum_2
The class file is still the same, and because of that when we run the program we get an UnsatisfiedLinkError. I understand that this error is because the VM cannot find the implementation. So why JDK 1.7 generates a header file that does not match the class file?
Thank you in advance.

I don't have 1.6 to verify but your statements about what is generated for 1.7 for the header appear correct.
The 000024 represents the '$' and for 1.7 the inner class is still named using '$'. So for example after compiling in 1.7 the inner class file is named the following...
MyClass$InnerEnum.class
So a one to one conversion should have kept the 000024 (presuming it does in fact do it that way in 1.6.)
You might want to look at the release notes for 1.7.
If you need a solution you could add a post javah step that renames the file.

File sizes listed does not match the downloaded files

I am trying to download 92010NT from this page http://www.oracle.com/technology/software/products/oracle9i/htdocs/winsoft.html but the file sizes listed does not match the downloaded files. Is there any other page where I can download 92010NT.

I am trying to download 92010NT from this page http://www.oracle.com/technology/software/products/oracle9i/htdocs/winsoft.html but the file sizes listed does not match the downloaded files. Is there any other page where I can download 92010NT.

So I decided to try and 'Edge up' since I was practically at the mark. Seemed to go fine until I select my new device, then I get 'This device does not match the device ID on your original Edge Agreement.'. Odd because I've never switched phones, and i'm

So only a few bucks left for the edge upgrade, decided to edge up since it gave me the option to do so, I figure why not?
Process seems to go fine until i'm in the checkout for a new device.
Tosses 'This device does not match the device ID on your original Edge Agreement. ' at me, but it's really strange because I'm using the phone I got direct from Verizon, haven't switched phones or anything.
Has anyone had this issue before?

Toxicle,
I can understand how something like this can be concerning. Let's work to get to the bottom of this for you. What kind of phone were you Edging up from? Has the phone ever been replaced or removed temporarily? Just want to make sure we are getting all the facts to help with this issue.
CandiceH_VZW
Follow us on Twitter at @VZWSupport

Iphone 4 file size does not match the ACTUAL file size

My iphone 4 is reading 27 gigs of music as over 29 gigs of music. I don't understand why. Anyone else having an issue like this? My 3gs reads it as 27 gigs and so does my computer. I even set my 3gs to sync off a backup of my iphone 4 and it reads it as 2 less gigs. Why?

Don't know, though Apple has been known to play with the numbers a bit:
http://www.tuaw.com/2009/08/29/snow-leopard-the-new-one-gigabyte-now-slimmer-tha n-before/
Or you could have had a conversion box checked in iTunes when you loaded your IPh4
Phil

Error message: The selected file cannot be linked because it has 6 audio channel(s) and the clip was

I recently purchased/upgraded from Premiere Elements 5 to Premiere Elements 9 and I cannot open the projects in version 9 that were created with version 5. It shows it as offline. I get a message to open up a file and when I do i receive the error message: The selected file cannot be linked because it has 6 audio channel(s) and the clip was created with 2 audio channels. Can someone help me or tell what I am doing wrong? All of my projects that were completed in version 5 cannot be opened up in version 9.
Thank you.

Bill,
I ran G-Spot on one of the files and here it what I have:
DVD "VOB" format
MPEG-2 Program Stream << { 1 vid, 1 aud }
Sys Bitrate: 10080 kb/s VBR
I guess I am really confused. The project that I am trying to open PrE 9 was completed in PrE 3 w/templates , scenes, etc. The movie was burned to a DVD. I cannot understand why I cannot open it with a newer version of PrE. According to G-Spot (I am assuming this is what you mean above), it is already in 2 channels. To me this should be ok. I put many, many hours into these videos and now it seems all for not.
Here is what I did so far:
I uploaded the required media files to a new project in PrE9 and let them index and conform. I saved the project with the same name in a different location. Do I have to do this to the project files and/or the original media files? Confusion starts here.
The next step is where I am confused. I do not know if I am proceeding in the right direction from here. There is the share tab in the upper right hand corner. Is this what you are talking about? I am truly lost from here.
Thanks.

The selected file cannot be linked because it has 6 audio channel(s) and the clip was created with 2

I tryed to link MTS files to a project that I edited with AVI files. I got the message "The selected file cannot be linked because it has 6 audio channel(s) and the clip was created with 2 audio channel(s)". Does anybody know what I should do?

Relink to the correct media.

Does Muse optimize the original file because my images in a slideshow resize after I have used the image more than once.

iif I import a photo into my website and make it a small size then when I create a slideshow and add that photo from my computer it comes in too small every time. It's as though Muze is optimizing the original photo and that is very frustrating. I have to open that photo in Photoshop and save it again to fix it. Very annoying. Will this be fixed?

Muse does not touch the original image, but it does maintain an optimized copy of the original. You can verify by locking the original image file to prevent Muse from touching it.
Muse performs the optimization at export/publish time based on the largest instance of the image in the project. In this case, when you re-import the image, Muse is incorrectly assuming you want the new image at the same size as the first instance that you resized smaller. We'll look at fixing this behavior in the next release, but in the mean time there is a workaround.
Instead of opening the image in Photoshop and re-saving, which changes the modification date of the image and signals Muse to re-import the image, try double-clicking until the image is selected. The selection handles will be smaller and solid if you have the image selected. The handles will be larger and hollow if a container is selected. Then resize the image to the dimensions you want. Initially, the image will be pixelated because Muse is still using the previously optimized copy. However, if you choose File->Preview Page in Browser, the image will be re-optimized for the new dimensions and you should see a higher resolution version in both the browser and on your page within Muse.
You can more easily verify the optimization behavior as follows:
1. Place an image at 25% of its original size.
2. Select File->Preview Page in Browser, which will optimize the image at the 25% size.
3. Duplicate the placed image and resize the duplicate to be twice as big (i.e. 50% of the original). Initially, this duplicate will be blurry after the resize.
4. Select File->Preview Page in Browser, which will re-optimize the image and redraw at the higher resolution.

Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040

Please assist I am on a Windows 7 64 bit machine I have VS 2010 and have been fighting with this new program that I was brought on to help with - Issue is that I am unable to get rid of this issue. There is so many solutions but none have worked. If someone can give me some help with what has worked for you.
The error is Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
This is with CR installed on 64 bit.
Thank you very much for any assistance with this problem,
Kris

Hi Vittorio
Please enter the search string 'log4net crystal net' into the search box in the top right corner. When the results come up, click on the Support Notes link. That will filter for the KBAs that you want to have a look at.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

How can I convert my Open Source document files into Word document files? I cannot download Pages since my Macbook Air does not have the most recent software.

How can I convert my Open Source document files into Word document files? I cannot download Pages since my Macbook Air does not have the most recent software. I downloaded open office to my mac to try and save money. It worked well for a while. Now I get this pop-up message that asks me to "Reopen" and when I select the option, nothing happens. I cannot save my documents anymore and I cannot convert them to word. Help!

dwb wrote:
Does OpenOffice output Word documents by default or do you have to select it manually?
You have 17 options to save as in Open Office, one of which is .doc files, yes it needs to be saved manually.
You may be able to default to DOC, but have not tried same.
Since Open Office is 99% same as Word, I use it, or Word, either one. Open Office is a bit less buggy than Word 11'

Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
===========================================================
This is a SQL Server 2012 Developer Edition of SSRS.
I am getting this error when navigating to http://servername/Reports. The reports site was working fine, until I installed a SQL 2014 Developer instance (including SSRS) on the same server.
I can still get to the http://servername/ReportServer site.
Neither of these are using Sharepoint.
Any help resolving this issue would be greatly appreciated.
Below is the stack trace.
===========================================================
[FileLoadException: Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)] System.Reflection.Assembly._nLoad(AssemblyName
fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0 System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity,
StackCrawlMark& stackMark, Boolean forIntrospection) +416 System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +166 System.Reflection.Assembly.Load(String
assemblyString) +35 System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +190 [ConfigurationErrorsException: Could not load file or assembly 'Microsoft.ReportingServices.SharePoint.ObjectModel'
or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)] System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +1149
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +323 System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +116 System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +36 System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection
compConfig) +212 System.Web.Compilation.WebDirectoryBatchCompiler..ctor(VirtualDirectory vdir) +174 System.Web.Compilation.BuildManager.BatchCompileWebDirectoryInternal(VirtualDirectory vdir, Boolean ignoreErrors) +57 System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath
virtualPath) +295 System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +482 System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext
context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +108 System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean
noAssert) +171 System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +52 System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext
context, String requestType, VirtualPath virtualPath, String physicalPath) +53 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +519 System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
+176 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +274
===========================================================

Hi Glen，
"The located assembly's manifest definition does not match the assembly reference." is generally caused by the loaded assembly's version is different than the expected version application refers to.
In this case, it should be caused by:
While starting Report Manager, the backend process ReportingServiceService need to load assemblies it refers to
ReportingServiceService reads the compilation/assemblies element from web.config(under Report Manager virtual patch)
If the compilation/assemblies is not existing, ReportingServiceService loads all assemblies from Bin folder. It can be verified from call stack System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory(). ReportingServiceService
uses System.Reflection.Assembly.Load with the assemblies' name only to load assemblies.
The Assembly.Load tries to load from the specify assembly by name from GAC at first. If it is found from GAC, it won't be loaded from Bin folder any more.
Since Reporting Service SharePoint Integration mode is installed, a same assembly of 'Microsoft.ReportingServices.SharePoint.ObjectModel' with different version might be installed to the GAC. That causes the error "The located assembly's manifest definition
does not match the assembly reference."
For more information about the error message and the loading process, please see:
http://blogs.msdn.com/b/junfeng/archive/2004/03/25/95826.aspx
https://msdn.microsoft.com/en-us/library/yx7xezcf(v=vs.100).aspx
Thanks,
Jinchun Chen

Selected file cannot be linked because its type (video) does not match the original file's type

Similar Messages

Maybe you are looking for