File Format Mismatch X7 and X8

[lata]

Hi

File Format Mismatch has been mentioned a few times over the years until now I was unable to replicate the problem, nor explain the reason.

I think the error is relating to the files extension of a particular file.
Lets assume we re-name a MTS file to use a Wav extension, windows will complain and rightly so. Video Studio will treat this as a File Format Mismatch.
The extension of course may not be the problem and a corrupt file could fool VS in not recognising the format and could show File Format Mismatch.
Whatever the reason I have never been able to explain it.

Ok try this

1 / Add a video file to the timeline, choose one of the Mpeg4 / wmv samples.

2 / Share - Choose – Audio, I choose this to create an audio file of the timeline, I returned to edit to check the file, that worked ok. It does not really matter rendering, selecting Audio will suffice.

3 / Share – I immediately choose Same as Project or Clip from the top option, tick the box first.
The video render settings showing in the properties panel as ok.
4 / Choose a save location and a suitable / unique name.
5 / Start the render
6 / Render completes -- program returns a File Format Mismatch, normally we would see “The file has been successfully rendered”. Ok the panel
7 / Return to Edit and the file is not in the library.
8 / View the files location on the hard drive and you will find a sound file having your unique name, we would expect a video type extension—mp4, instead the file has an audio type extension.

The problem seems to the Share – Profile panel has an Audio type showing even though this is greyed out and should not be used, the selection being retained from the previous audio render, creating an audio file.

The panel is greyed out and should not be affecting the settings, clearly it does.

I have tested with both X8 and X7 with the same results.

Can you replicate these results? Thanks

[Ken Berry]

Sorry Trevor -- I couldn't replicate this fully, only partially. I only tried it with X8, though I followed your steps exactly, using FWIW SP-V21.wmv as the clip. Rendered the audio clip. Then went back to Share, assigned a new name, then selected Share > Same As Project Properties, and indeed got a message, when the render ended "File is invalid" (rather than the "file format mismatch" one). The Format line did indeed show Windows Media Audio .wma as the Project Properties, so that was fine and backed you up.

However, when I selected Same As First Clip, the render was successful and I got a message telling me so. The format line, however, still showed Windows Media Audio .wma as the output, and indeed the rendered file had the .wma extension. But very curiously, it also had the video in it which played fine.

So the mystery deepens...

You also said:

I think the error is relating to the files extension of a particular file.

That may be so, but it is not the only cause. You will recall we recently had a couple of people using "non-standard" (at least for VS) frame sizes in their GoPro Hero cameras, and I could replicate it. Rendering Same As produced the file format mismatch error message, though in all cases the file extensions were -- and remained -- .mp4. In these cases it was clearly not the extension causing the error but the frame size (in these cases 1920 x 1440 and 1280 x 960 instead of the more "standard" (for VS) 1920 x 1080 and 1280 x 720).

[Ken Berry]

The mystery does indeed deepen! Intrigued by all this, I decided to try the same thing in X7 using the same clip. I created the audio only file. Then went back and selected Same as Project Properties. In this case the Format line showed clearly Windows Media Audio .wma but the Properties box contained all the Properties of my previous project in X7 which coincidentally enough must have been one of my experiments with one of the problematic GoPro clips I just mentioned, in this case a 1280 x 960 one. So when I tried to share, I got this error message, which in reality was what I also got when trying to render one of those problem GoPro clips:

When I chose instead Share > Same As First Clip, the render was successful, though as with X8 it produced a file with the .wma extension, but which also contained the video. I noted that in the Same As First Clip option, the Format line was .wma though the Properties box showed the full properties of the clip, which of course included the video stream. I checked back in X8 and found that this was also the case there with the Same As First Clip choice.

In other words, this seems to show that it is the Properties box under Share which governs the result, be it successful or a format mismatch type of error. But it still doesn't explain why you can get a supposed audio .wma file which is also a full video file, though not using a video extension!

[lata]

Hi Ken

Thanks for the tests, I read through your reply but need to read again just to digest the content, a lot going on there.

When you choose Same as First Clip, what shows in the panel marked Format, it should show Windows Media Audio or Microsoft Wav, although greyed out.

Just to clarify
Share – select Audio – choose Wav as the format.
Now Choose Same as First Clip

Render the clip.

Are you able to add that new clip to the library?

I’ll be back tomorrow, have a good day….

[Ken Berry]

I thought I had tried to make it clear that the format line showed .wmv (though yes, it was greyed out) while the Properties box showed the Properties of whatever my last project in that version of VS was.

You also had not specified choosing .wav as the output format for the Audio. I just accepted the default .wma since it was originally a .wmv clip. However, I have now just tried this using .wav as the audio format. This was in X7. It quickly produced a .wav file. However, when I then chose Share > Same As First Clip, the Format remained a greyed out .wav, while the Properties box showed the original .wmv properties. And this time I actually got a "File format mismatch" error.

When I instead chose Same As Project Properties, the format line remained a greyed out .wav, but the Properties box changed to those of the 1280 x 960 project and I got the same error message as on the image posted above in my last post.

When I then repeated this in X8, I got a File Format Mismatch error message for both Same as First Clip and Same As Project Properties. In each case the Format line remained a greyed out Microsoft WAV Files (*.wav), but in Same As First Clip the Properties box showed the original .wmv properties, and in Same As Project Properties, the properties were those of my last project in X8 (in this case a standard def mpeg-4 project).

So it seems pretty clear (???) that the file format mismatch is between the format shown in the Format line, and the format reflect in the Properties box.

[lata]

Hi Ken

Just to add after receiving the File Format Mismatch error the rendered file is saved to the hard drive, but with the wrong file extension, we can re-name the file to use the correct one, if using the MP4 samples then re-name to MP4.

The library would normally hold the clip for the new rendered file, but not so, I think the Mismatch was generated when VS tried to add the rendered clip to the library. VS did not like the file type and extension combination.

Ken thanks for the tests and confirming the problem, I will send the details to Yvonne Bugzilla.

[asik1]

Trevor I did many tests, the problem is only when one render Audio first, "same as" second.
I had no problem with any other crazy "combo's"

[lata]

Hi

Thanks Asik for the testing, yep rendering video immediately after selecting audio is where the problem lies, I have passed the details to Yvonne just to keep her on her toes.

[lata]

Hi Guys

Good news this is the reply from Corel

"We can reproduce this problem and will include this into patch pool."

I guess that means a Service Pack will be provided.

[ents_2]

I have successfully used Video Studio for many years, using various versions. I've never had a problem with new versions being able to read old versions of the .VSP files. Until now. I just downloaded the trial version of Ultimate X8 and it will allow me to create a new .VSP file and it will read it with no problems. However, every time I try to open a .VSP file from previous versions - no matter what versions I try, I get a "File Format Mistmatch" and it won't open it.

So I guess I won't be buying Corel anymore if they're going to start doing this kind of crap. I use other Corel products but maybe I should start looking at other brands.

Does anyone have a clue as to what I can do here? My computer had to get reformatted due to viruses and I don't have Video Studio X7 anymore. And of course, I didn't have a copy of the program to re-install. And of course, even though I paid for the darn thing just last year, I can't re-download it. What is wrong with this picture???? Isn't that illegal???

Anyway, I am ranting. I really do need to know what to do with all my hundreds upon hundreds of .VSP files that Corel doesn't see fit to enable their new products to read.

GRRRRRRRRR

[BrianCee]

Your problem is simply that you are using the trial version

for the first time ever Corel have released a trial version which is not a full working version but has several important functions removed - the trial will allow you to create *some* video formats -but as you have found it will not import older .vsp files if they contain video formats not allowed in the trial

Crazy I know and most of us feel Corel have shot themselves in the foot - but that's the way it is.

I have had no problems importing .vsp's made in previous versions into a full copy of X8

[lata]

Hi

We are all as frustrated with this issue as you are with the trial limitations.

You could try ranting at Corel via their Facebook account, we are all volunteers trying to help users..

Otherwise pay for the full program, you have a 30day money back guarantee, so if you do not like???

Under the circumstances that’s the best we can suggest

Corel Video Studio X7
I assumed you have contacted Corel asking if they will give you the download link for the old program.
I always make copies of my programs and burn Data Discs as a second backup.
Your serial number should be on your Corel registered account

I guess hind sight is a good thing……………

[ents_2]

Thank you very much to both of you for your comments. I knew it said some features wouldn't work but didn't think it would be old .vsps. and yes I do indeed plan on buying it. I just wanted to make sure it would still access all of my old files. LOL

I do have backups normally. However for whatever reason I couldn't find video studio. I found corel paintshop pro, so 1 out of 2 ain't bad. Lol

And I ranted in hopes that people from corel may frequent this forum. I belong to a couple of forums where the company does have staff monitor the forums. I am new to this forum.
And yes I already sent them a mild rant.
Thanks again for the help!

[MIKEL]

You are fortunate people know how to help you. Yes - backups are mainly to forgo the pleasure of having to be embarressed trying to rebuild things and pleading for reloads.
If any of you have any knowledge of Canon 7D mkii cameras having intermittent problems rendering clips I would really, really appreciate a chat - I don't get an error message it just deletes the tempory files and buggers off.
As an after thought how in hell are you supposed to use a trial version if it is NOT like what you think you are testing.
mike

[lata]

Hi Mike

You should tell Corel about your concerns regarding the Trial version.
We all agree that the trial limitations have gone to far in affecting the programs functionality, but as I remember will edit Mov and MP4 in HD, it’s the DVD and AVCHD options that are missing

Canon 7D yes but not mkii.

I don’t use the camera that much for video, generally still images.
But I have not had any problems other than not being able to render same as video properties, although things have improved over the last two versions.

When you say the rendered files just disappear, the only reason I can thing of is using Fat32 filing system that limits to 4 Gb, when render reaches the limit it will simply terminate with on files saved.
If you are using Fat32 then update to NTFS