What this ? "DV Reader: file fomat invalid"

[vincej]

My first post to Procoder - hope you can help.

I have captured an analogue file using ADVC55 in dv.avi. It is PAL.

I have edited it in Pal and then made a whole new avi from the results.

I now want to convert the new avi into NTSC.

Procoder Express is giving me an error "DV Reader: file format invalid"

I have never had this error yet. What does the error mean ?

Could it be the consequence of the editing of the orginal PAl avi ?

Are there any work arounds ?

Many thanks Vincej

[GrassValley_KH]

Ok we're missing a vital piece of the puzzle here - the software used to edit.

EDIUS? Premiere Pro? Something else? What version number of the software?

[vincej]

Sorry - On a forum where so pros come I am embarrassed to say that it was edited using Ulead Visual Studio 11.


thanks Vince

[GrassValley_KH]

There we go. So I assume you used Ulead to capture the footage (as PAL) yes? Do you know what DV format Ulead was set to capture? If it's a funky, non-Microsoft DV format, then ProCoder Express may not be recognising the codec.

Are you able to capture (or render out) as Microsoft DV AVI? ProCoder shouldn't have any trouble with that format. (PAL or NTSC)

[vincej]

Ok - i have checked and I am capturing Microsft DV.avi open dml

when it goes to ntsc it also is Microsoft.

The curious thing is that I have been doing Pal > NTSC conversions very successfully on the native files.

Just this time it has gone boom hence my thinking that it might have something to do with the fact that I edited the Pal file before conversion.

What does the error message actually mean ?

Many thanks Vince

[GrassValley_BH]

The error means ProCoder can't read the DV file properly. Either it's not DV, or contains invalid data.

[THoff]

Can you open the file in question using Windows Media Player? You can also have GSpot (http://gspot.headbands.com/) check for codec problems (a possible consequence of installing so-called "codec packs") and scan the file for damage.

[vincej]

Yup it will play on Microsoft media player.

I have checked it on AVIcodec and I have the available codecs on my system to play it.

I will have to download Gspot and check it.

many thanks Vincej

[vincej]

Ok - I checked with Gspot and this is what it is telling me on the edited file wich caused the error message - I do not understand what this is saying.

Note: 10.1 GB unneeded bytes at end of file
DV Type 2 AVI
Multipart OpenDML AVI (5 parts)
(128658 frames in first part, -32 frames follow)


Additionally I tried converting the orginal *unedited* PAL dv.avi file and it converted fine into NTSC. The curious thing is that if I check this presumed "good" file it is giving me similar dodgey report:

Note: 14.6 GB unneeded bytes at end of file
DV Type 2 AVI
Multipart OpenDML AVI (5 parts)
(166582 frames in first part, -3 frames follow)


What is the moral of the story ? I like to understand so I fix it myself next time.

Many thanks Vince

[THoff]

Essentially, the size information in the header doesn't match the file's actual size.

Can you play the entire file in Windows Media Player? Have you tried moving the playhead position near the end of the file and playing the video?

[vincej]

Yup - I can play both files at the end of the file as well as the beginning. good meaning the one which converted without breaking Procoder Express and the bad being the edited one which caused Expressed to give the error " bad file format"

Remember I captured these off an old Hi8 analogue camera using an ADVC55 converting it straight into dv.avi - would it still have have header and file size info ?

Thanks Vincej

[THoff]

Yes, whatever software you use to capture the DV data coming from the ADVC writes the AVI (or in some cases some other container format) file and header.

[vincej]

Ok - I'm not too sure what I should do to be correct about things.

I have an unedited file although converted to NTSC. It will play through to the end using Sony Vegas Movie studio. I can try re-editing in vegas

should I just be happy and get on with it ? or should I do something so that Gspot is happy ?

If so what is that ?

Thanks Vince

[THoff]

You could try outputting the problematic file(s) to new DV AVI files using Vegas, and then test the new files using GSpot to see if that makes any difference.

Also, have you tried GSpot on any other files besides the one that started you on this journey? How about DV AVI files captured using Vegas?

[vincej]

Ok - I'll give it a try - however to reiterate, I converted a file this morning last night which Express was quite happy with .. that is to say I did not get the error message "bad file format"

BUT perhaps Gspot does not like that one either ?? Please advise:

details:

Note: 14.6 GB unneeded bytes at end of file
DV Type 2 AVI
Multipart OpenDML AVI (5 parts)
(166582 frames in first part, -3 frames follow)

I have noticed that hte last 3 frames of these files are garbage. does that matter ?


If I am going to try capturing in Vegas using my ADCV55 will I get revealing and accurate results with say only a 15 minute capture or must I do the whole 90 mins ?

Many Thanks Vince

[THoff]

From where I'm sitting, I can't tell you where the problem is or whether this affects all your files.

All I know is that GSpot V2.70a does not report problems with the DV AVI files on my system, but they are also all NTSC and not PAL. However, I'm not aware of any problems that GSpot may have with PAL DV AVI files, so I'm inclined to think that there is in fact something wrong.

Another thing you can try is DVDate (http://paul.glagla.free.fr/dvdate_en.htm). It's a free program to primarily overlay the timecode on video, but it also does PAL to NTSC conversions and some file repairs.

[GrassValley_KH]

If it's a particularly large file (i.e. long runtime), then it makes me want to know - how long has it been since you ran a full-level hard drive error scan?

[vincej]

thanks - U have downloaded DVDate and looked at it untill I have square eyes. I can see that it will change dates, formats Pal / NTSC etc but for the life of me I can not see how it fixes files > where and how does it do this ? any ideas ?

Many thanks Vincej