VideoHelp.com forum archive
http://www.supermediastore.com/



Forum Archive Home -> Advanced Video Conversion -> Avisynth and m2ts files



Avisynth and m2ts files
Megahurts posted 2008 Sep 14 15:03
Avisynth script stopped loading m2ts files in VDub and MPC. Vdub gives a "No video stream fround" and MPC plays audio only. It works with all other file types including ts.

Did a system restore and re-installed Avisynth but no luck.

Any suggestions... TIA



45tripp posted 2008 Sep 14 15:08
what avisynth script?

codecs and splitters installed?



Soopafresh posted 2008 Sep 14 15:10
You need a directshow codec to play back AVCHD, like CoreAVC or ffdshow


Megahurts posted 2008 Sep 14 20:26
Thanks for the replies.

The avs script is a one line DirectShowSource(my-file.m2ts).

I have ffdshow & CoreAVC installed. Only AVC & VC-1 are effected. The m2ts files will play in MPC but not using an avs script.

Also I noticed that trying to open the original m2ts with Graphedit, I get an error message "Some of the streams in this movie are in an unsupported format" then will display the audio graph.

I have a dual boot (both) XP pro setup and using the 2nd boot everything works fine with Avisynth & Graphedit.

I did install Xvid4psp and Net Framework 3.0 yesterday and thinking that caused the problem I un-installed both but NO. Did a system restore to a week back and the same problem.



poisondeathray posted 2008 Sep 14 20:28
haali media splitter installed? did you turn "on" h264 in ffdshow to libavcodec? or set the merit of coreavc higher as the default decoder?


Megahurts posted 2008 Sep 14 23:33
Yes, haali media splitter is installed and h264 is turned on. Coreavc is set to preferred.

MPC will play the m2ts files using ffdshow or Coreavc if it is preferred.

What does Avisynth and Graphedit have in common to read m2ts (AVC & VC-1) files?



poisondeathray posted 2008 Sep 14 23:40
Graphedit is a tool used for directshow filters.

Since you are using DirectShowSource() in avisynth, it will use the same directshow filters you have installed on your system by default (unless you map something different in graphedit). If you used DGAVCdec and AVCSource() instead on a h264 .m2ts stream, for example, it would use it's own decoder (which is based on libavcodec).

The warning you get "Some of the streams in this movie are in an unsupported format" may refer to other types of unsupported audio like TrueHD, EAC3 or perhaps PGS or subtitle tracks. Or perhaps you didn't turn them on in the ffdshow audio configuration

Your script should be something like this, and the syntax is important. If you can play the file directly in mpc, you should be able to open the .avs in mpc as well: (assuming your fps is 23.976)

DirectShowSource("PATH\myfile.m2ts",fps=23.976)

If your .m2ts is a VC-1 stream, then you need to install Windows Media Format 11 SDK. Use mediainfo to determine what type of video stream you have.



Megahurts posted 2008 Sep 15 11:16
More strange info...

By changing the file extension from m2ts to ts, and creating a new avs file, it will play in MPC, VDUB, and display the graph in Graphedit. It works for AVC and VC-1 files.

What could have changed to cause this as it did work properly before 2 days ago?



jman98 posted 2008 Sep 15 12:54
Megahurts - I don't know if this is any help to you or not, but on my PC, I have no choice when working with AviSynth. I used to get the same error as you but all the time on all kinds of files. I accidentally stumbled on the fact that if I use MPC to open the *.avs script file and start the file playing, only after that will AviSynth work reliably for me and open the file. It's no problem because it hardly takes any time for me to do this extra step with MPC, but I learned that if I do this every time, AviSynth works for me without the error. I have noticed that once I open a file in MPC, that sometimes I can actually get AviSynth to work correctly with different scripts and different files that I have not played in MPC, even a few days later.


gadgetguy posted 2008 Sep 15 13:55
This sounds like codec conflict to me. You seem to have the right codecs and splitters, but you may have also not-right codecs and/or splitters that may get priority under certain circumstances (certain players, certain files, etc.) causing WCS (Windows Confusion Syndrome). It might be time to do a clean sweep of all codecs and splitters and reinstall just what you need.



Login/Register to our forum to be able to post here.








About   Advertise   Forum Archive   RSS Feeds   Statistics