View Full Version : Opening M2TS files with avidemux proxy
Trademark
24th June 2017, 18:45
I am trying to use Avisynth and eventually proxy it to Avidemux so I can take advantage of a custom QTGMC script that was given to me years back that made my interlaced videos have really good quality.
Sadly, the computer I had the full script on has since died on me, and I'm trying to start from scratch and getting a script to load my videos, so I won't even be able to use the QTGMC script until I can figure out how to load the files in the first place.
The videos are encoded in H264 and are m2ts extensions.
I've been browsing through the Avisynth Wiki and and on the Doom9 forum for the past couple hours, but no luck. I've downloaded the FFMS2 v2.22 plugin I found in the FFmpegsource wiki page and put it into the Avisynth plugin folder, and here is my current script to try and load the video into VirtualDubMod:
FFmpegSource("C:\Users\Owen\Desktop\hdpvr.m2ts")
The error I get in return is 'there is no function named ffmpegsource'
manolito
24th June 2017, 19:03
The latest version on GitHub is v2.23.1, and instead of "FFMpegsource" you need to specify "ffmpegsource2" or "ffms2".
Cheers
manolito
stax76
24th June 2017, 19:38
The newest ffms2 is 2.2000 test6 I believe, that's used in staxrip for quite long so it should be reasonable stable, QTGMC is also included for both AviSynth and VapourSynth.
manolito
24th June 2017, 20:18
The newest ffms2 is 2.2000 test6 I believe, that's used in staxrip for quite long so it should be reasonable stable, QTGMC is also included for both AviSynth and VapourSynth.
I think you are mixing up a few things...
ffms2 is 2.2000 test6 is from the "Experimental" fork, it is not even Alpha, so it is far from stable. I have a hard time understanding why some folks are so much obsessed with always using the very latest versions, no matter how buggy they are.
Cheers
manolito
Trademark
24th June 2017, 20:32
Thanks guys, adding the 2 did the trick.
Now I get an error message saying it 'couldn't locate decompressor for format yv12 (unknown0. VirtualDub requires a video for windows (vfw) compatible codec to decompress video. DirectShow codecs, such those used by Windows Media Payer, are not suitable. Only 'Direct steam copy' is available for this video.'
VirtualDub crashes if I try to play the video after that warning.
Also, when I load this script into avidemux, it needs a demuxer, so I assume I'll have to use something like dgvacindex to separate the audio and video of the file? I vaguely remember having to do that from several years ago.
stax76
24th June 2017, 20:38
@manolito
It's in the stable staxrip release since a month without anybody reporting a issue so it's save to say that it's fairly stable.
@Trademark
I'm rather sure VD has a yv12 decoder built in, there is a filter suit fftryouts or something that was popular before lav filters, it includes all kind of vfw decoders.
manolito
24th June 2017, 21:20
@manolito
It's in the stable staxrip release since a month without anybody reporting a issue so it's save to say that it's fairly stable.
Including an EXPERIMENTAL source filter in a stable release of StaxRip looks a little bit irresponsible to me. I am glad that you are not working for a commercial software company...
Cheers
manolito
Trademark
24th June 2017, 21:27
@manolito
@Trademark
I'm rather sure VD has a yv12 decoder built in, there is a filter suit fftryouts or something that was popular before lav filters, it includes all kind of vfw decoders.
If it's a VD problem then I can skip that step, since ultimately I will be using avs proxy and avidemux. Using VD was just so I could make sure I got my load file script right.
Now then I will move on to trying to demux the m2ts file into audio and video and get it loaded up in avidemux so I can apply my qtgmc script.
Morku
24th June 2017, 21:52
ffms2 is 2.2000 test6 is from the "Experimental" fork, it is not even Alpha, so it is far from stable. I have a hard time understanding why some folks are so much obsessed with always using the very latest versions, no matter how buggy they are.
Never have any problem with FFMS2000 test6 with my videofiles and if so, I am aware about the state "test".
I am glad that you are not judging about how we have to use our software and related to your posts here, we would still use Windows XP.
manolito
24th June 2017, 22:14
we would still use Windows XP.
Which would probably be not such a bad thing IMO... :mad:
Trademark
25th June 2017, 14:28
Ok, I'm having issues getting the video file into avidemux through the proxy now. I've done what the wiki says about .TS files, and I first put it through TSREmux to give me an h264 stream, then put that stream in through DGAVCIndex to give me a .dga file which I put in my script. I also have DGAVCIndex.dll as one of my avisynth plugins.
The test.ts clip I can drag into avidemux without hassle, so there must be something lost along the way with avisynth here.
Here is my script so far:
LoadPlugin("C:\Program Files (x86)\Avisynth\Plugins\DGAVCDecode.dll")
AVCSource("C:\Users\Owen\Desktop\testremux.dga")
Avidemux just keeps saying it can't find a demuxer for avs proxy.
lansing
26th June 2017, 00:37
Have you actually open the avsproxy_gui in the avidemux folder and load the script in there?
Trademark
26th June 2017, 01:09
My avidemux didn't come with avsproxy in its folder, so I put the avsproxy that I downloaded separately first in the avidemux folder, then in the avidemux plugins folder, and I still get the same error message.
lansing
26th June 2017, 01:42
My avidemux didn't come with avsproxy in its folder, so I put the avsproxy that I downloaded separately first in the avidemux folder, then in the avidemux plugins folder, and I still get the same error message.
No no no.
Get the program from its official site, all files are included:
http://www.avidemux.org/nightly/
Trademark
26th June 2017, 01:57
No no no.
Get the program from its official site, all files are included:
http://www.avidemux.org/nightly/
Wow! Thank you very much. I had downloaded some version off fixounet, but this version works without a problem!
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.