Log in

View Full Version : ".mpv is not supported file format." in Scenarist ?


Grover
18th May 2003, 10:30
Warning D:\HFROCT_working_folder\VTS__01_P01.16~9_1.MPV is not supported file format. Imported as place holder
Warning D:\HFROCT_working_folder\VTS__02_P01.4~3_1.MPV is not supported file format. Imported as place holder

Any suggestions as to the cause / solution are greatly appreciated.

This error is what Scenarist is telling me when I import my script file from ReAuthorist. (full listing below) I've checked the ReAuthorist generated script for Scenarist and these are the correct file names and locations for my encoded VIDEO. Everything is where it's supposed to be. For some reason Scenarist doesn't like either the name or the format (note - I can mux these VTS's using IFOEdit with no problems which suggest that the video file format is OK ???).

I have tried going to the place holder in the Scenarist project and re-selecting the encoded video but no difference when I try to mux the project (ie - it complains there is no video to mux, just a place holder).

This example is Hunt For Red October (PAL), just movie (VTS_01) and trailer (VTS_02). This movie is one example. I get the EXACT SAME error when importing into Scenarist (ie - XXXX.mpv is not supported file format. etc...) on the two other DVD's I have tried so far, Minority Report and SW-AoTC.

I'm using DIF4U then DoCCE4 then ReAuthorist 0.6.2 and then Scenarist.

*********************************
Info -----------------------------------------
Info Start Importing
Info ------ Reading script ------
Info Importing MODIFIER VERSION
Info Importing Data
Info Importing VTS__01_P01.16~9_1
Warning D:\HFROCT_working_folder\VTS__01_P01.16~9_1.MPV is not supported file format. Imported as place holder
Info Importing VTS__01_P01-80-384K-[-80]MS(FIXED)-CH6ENGLISH
Info Importing VTS__02_P01.4~3_1
Warning D:\HFROCT_working_folder\VTS__02_P01.4~3_1.MPV is not supported file format. Imported as place holder
Info Importing VTS__02_P01-80-448K-[-80]MS(FIXED)-CH6ENGLISH
Info Importing Tracks
Info Importing VTS_01_PGC_01
Info Importing VTS01_vobid01_cellid01
Info Importing VTS01_vobid01_cellid02
Info Importing VTS01_vobid01_cellid03
Info Importing VTS01_vobid01_cellid04
Info Importing VTS01_vobid01_cellid05
Info Importing VTS01_vobid01_cellid06
Info Importing VTS01_vobid01_cellid07
Info Importing VTS01_vobid01_cellid08
Info Importing VTS01_vobid01_cellid09
Info Importing VTS01_vobid01_cellid10
Info Importing VTS01_vobid01_cellid11
Info Importing VTS01_vobid01_cellid12
Info Importing VTS01_vobid01_cellid13
Info Importing VTS01_vobid01_cellid14
Info Importing VTS_02_PGC_01
Info Importing VTS02_vobid01_cellid01
Info Importing Scenario
Info Importing First PGC
Info Importing First PGC_cmd_1
Info Importing VideoManager
Info Importing VTS_01
Info Importing VTS01_Title01
Info Importing VTS_01_PGC_01pgc
Info Importing VTS_01_PGC_01_pg001
Info Importing VTS_01_PGC_01_cell001
Info Importing VTS_01_PGC_01_pg002
Info Importing VTS_01_PGC_01_cell002
Info Importing VTS_01_PGC_01_pg003
Info Importing VTS_01_PGC_01_cell003
Info Importing VTS_01_PGC_01_pg004
Info Importing VTS_01_PGC_01_cell004
Info Importing VTS_01_PGC_01_pg005
Info Importing VTS_01_PGC_01_cell005
Info Importing VTS_01_PGC_01_pg006
Info Importing VTS_01_PGC_01_cell006
Info Importing VTS_01_PGC_01_pg007
Info Importing VTS_01_PGC_01_cell007
Info Importing VTS_01_PGC_01_pg008
Info Importing VTS_01_PGC_01_cell008
Info Importing VTS_01_PGC_01_cell009
Info Importing VTS_01_PGC_01_pg009
Info Importing VTS_01_PGC_01_cell010
Info Importing VTS_01_PGC_01_pg010
Info Importing VTS_01_PGC_01_cell011
Info Importing VTS_01_PGC_01_pg011
Info Importing VTS_01_PGC_01_cell012
Info Importing VTS_01_PGC_01_pg012
Info Importing VTS_01_PGC_01_cell013
Info Importing VTS_01_PGC_01_pg013
Info Importing VTS_01_PGC_01_cell014
Info Importing VTS_02
Info Importing VTS02_Title01
Info Importing VTS_02_PGC_01pgc
Info Importing VTS_02_PGC_01_pg001
Info Importing VTS_02_PGC_01_cell001
Info Importing DefaultPalette
Info Restoring Link VTS01_vobid01_cellid01 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid02 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid03 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid04 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid05 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid06 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid07 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid08 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid09 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid10 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid11 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid12 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid13 -> DefaultPalette
Info Restoring Link VTS01_vobid01_cellid14 -> DefaultPalette
Info Restoring Link VTS02_vobid01_cellid01 -> DefaultPalette
Info Restoring Link First PGC_cmd_1 -> Title101
Warning Referenced Data(Title101) not found.
Info Restoring Link VTS_01 -> VTS_01_PGC_01
Info Restoring Link VTS_01_PGC_01_cell001 -> VTS01_vobid01_cellid01
Info Restoring Link VTS_01_PGC_01_cell002 -> VTS01_vobid01_cellid02
Info Restoring Link VTS_01_PGC_01_cell003 -> VTS01_vobid01_cellid03
Info Restoring Link VTS_01_PGC_01_cell004 -> VTS01_vobid01_cellid04
Info Restoring Link VTS_01_PGC_01_cell005 -> VTS01_vobid01_cellid05
Info Restoring Link VTS_01_PGC_01_cell006 -> VTS01_vobid01_cellid06
Info Restoring Link VTS_01_PGC_01_cell007 -> VTS01_vobid01_cellid07
Info Restoring Link VTS_01_PGC_01_cell008 -> VTS01_vobid01_cellid08
Info Restoring Link VTS_01_PGC_01_cell009 -> VTS01_vobid01_cellid09
Info Restoring Link VTS_01_PGC_01_cell010 -> VTS01_vobid01_cellid10
Info Restoring Link VTS_01_PGC_01_cell011 -> VTS01_vobid01_cellid11
Info Restoring Link VTS_01_PGC_01_cell012 -> VTS01_vobid01_cellid12
Info Restoring Link VTS_01_PGC_01_cell013 -> VTS01_vobid01_cellid13
Info Restoring Link VTS_01_PGC_01_cell014 -> VTS01_vobid01_cellid14
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg001
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg002
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg003
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg004
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg005
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg006
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg007
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg008
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg009
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg010
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg011
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg012
Info Restoring Link VTS01_Title01 -> VTS_01_PGC_01_pg013
Info Restoring Link VTS_02 -> VTS_02_PGC_01
Info Restoring Link VTS_02_PGC_01_cell001 -> VTS02_vobid01_cellid01
Info Restoring Link VTS02_Title01 -> VTS_02_PGC_01_pg001
Info Validateing Video (VTS__01_P01.16~9_1)
Info Validateing Video (VTS__02_P01.4~3_1)
Info Validateing Track (VTS_01_PGC_01)
Info Validateing Track (VTS_02_PGC_01)
Info Finish Importing
*************************************

Apologise for the long post...

oddyseus
18th May 2003, 11:09
Did u accidentally performed a pulldown on the video?

I know its a silly remark and pal videos don't need to pulldown, but silly things have a tedency to occur.

Doom9
18th May 2003, 12:19
just rename those two files to .m2v.
You are using the latest DC4U, correct? I've had similar issues with PAL titles.. the naming scheme of dc4u has changed so RA won't pick up those files anymore.

69Mws
18th May 2003, 12:41
Checkout the RA Script. For PAL it normally points to *.mpv, so just rename the *.mpv.m2v to mpv.

I had the same issue right know, 'cause I forgot to change the file ending.

Greetz
69Mws

Grover
18th May 2003, 13:31
Thanks for the replies guys. I've read them both a few times and it could just be that I am in serious need of caffiene, but I'm sure that one is contradicting the other in terms of what .m** file extension I should be renaming to .
just rename those two files to .m2v.
For PAL it normally points to *.mpv, so just rename the *.mpv.m2v to mpv.
My current encoded files have the .mpv extension so I will first try renaming them to .m2v and see what happens. Fingers crossed.

oddyseus: No pulldown unfortunately. (I wish it WAS just my own stupidity. hmmmm.... :D) I checked for pulldown after reading about NTSC users having isues with renaming of files for Scenarist from RA. Thanks.

69Mws
18th May 2003, 13:41
I'm also dealing with PAL Titles and the RA Script points always to *.mpv for me.

You need no "fingercrossing", just open your RA Script with any texteditor and there you'll see to which File it points.

Greetz
69Mws

Grover
18th May 2003, 16:39
You are using the latest DC4U, correct? I've had similar issues with PAL titles.. the naming scheme of dc4u has changed so RA won't pick up those files anymore.
I did use 1.0.1.3 of DoCCE4U but am now using 1.0.1.2 due to having the problems discussed here -

http://forum.doom9.org/showthread.php?s=&threadid=53478

It's gotta be something to do with this change right ? (ie - I'm using an "old" version of DC4U but the latest RA is looking for the new naming scheme ? )I'm also dealing with PAL Titles and the RA Script points always to *.mpv for me. It's pointing to *.mpv for me too. And the encoded video files have the .mpv extension when they spit out from DoCCE4U. But for some reason Scenarist will not SEE these encoded files no matter what extension I give them. What would cause this ?

The only time I have got Scenarist to import actual video into the project was when I changed the text in the RA script file from *.MPV to *.M2V (no renaming of the files) Then it DID import video in the project fine. The only problem was that it imported my ORIGINAL uncoded video stream. (I know this because it warned of oversize when re-muxing and after re-muxing using Scenarist (which worked perfectly by the way) the /0 VIDEO_TS folder was the exact same size as the original DVD (5.97GB).

Determined to nut this one out, I then systematicaly went thru the process of trying all the combinations of re-naming the files from .MPV to .M2V combined with changing the RA text file to look for either .MPV or .M2V Will not import video. Still haunted by "place holders" and "not-supported file types" Arrrrggghhhh !!!

I even deleted the original video streams so there could be NO confusion for Scenarist. Still will not SEE my encoded video files.

Thanks (again)

69Mws
18th May 2003, 17:38
My dear PAL(Encoding) guys, dear fellow Perfectionists :)

just name your encoded files as they are in the RA Script, 'til there's a final fix for that and you will have no troubles with those mentioned "placeholder-issues".

I can't mention it enough, check the Script from RA and don't try any guessing like "uh, maybe I name the files manually so or so and then it maybe works"....

And by the way, it doesn't matter if I press the "Authorbutton" in RA before encoding or afterwards, it ALWAYS points to *.mpv (at least for me) --> in case an "NTSC-Guy" reads this, this doesn't affect you, it's only for PAL Sources, can't point that out enough! ;)

Amen :D
69Mws

waldok
19th May 2003, 09:51
In Scenarist, just go to the Data window (assets part lower right corner), double-click your "mpv" (or m2v) file (the one that shoudl correspond to the video stream), then in the middle lower window (assets properties), locate the file path, click the browse button (the one with 3 dots), point to the file on your hard disk you really want to use as video stream. Then in the data window, right-click the "mpv" file, and select Data->placeholder, let Scenarist do its stuff (takes time) and you're all set. No need to change anything in the script so no need to re-import it.

Waldok:cool:

Grover
19th May 2003, 10:41
As you can read above I've been grapling with this issue for a while now (sure seems like a while).

I KNEW it had to be somthing simple. AND IT WAS !!!!

(I post this only in the hope maybe someone else is having, this same problem and they can read this and know how to fix it) (It was so simple I'm almost embarrased to admit it)

Yes, you do have to re-name the encoded video files to *.mpv (or whatever your RA Scenarist script is asking for. (at least for now).

My problem was that Window XP Explorer was telling me they ALREADY WERE named with .mpv extensions. It was only when I did a dump of the filenames in that directory using a directory printer did I discover they were ACTUALLY named with *.mpv.m2v as below.

VTS__02_P03.4~3_1.M2V 472,214,078
VTS__02_P03.4~3_1.mpv.m2v 247,416,176

This lead me to check the -

TOOLS --> FOLDER_OPTIONS --> VIEW tab in Windows Explorer.

It was TICKED for "Hide extensions for known file types"

I un-ticked it and whallaaah !!! There were my all my *.mpv.m2v file extensions. I was now able to rename these to the PROPER .mpv that Scenarist is being told to look for. (up to this point, no amount of renaming of the files had made any difference. it was only after changing the switch in Windows explorer options that it let me change them)

Fired up Scenarist, imported script, NO PLACE HOLDERS !!!! Yaaaayyyhhh!!!!! Just big fat video files. It's re-muxing away now but I don't expect any problems from here on in.