ffmpegsource

[StarMasayume]

Could I jump into this thread as I am having difficulty figuring out the ffmpegsource myself? I don't easily understand these things but I have managed to grasp avisynth just enough for my purposes.

I would like to either open mkv files directly in Premiere Pro or at least in Vdubmod. I found that I could use directshowsource but the lag is horrible and it seems ffmpegsource is recommended so I hoped to try that. I have downloaded the files as doom9 directed in this post. I couldn't find a readme file or clear installation guide without seeing a book of technical stuff so I've been gleaming what I could find out from forum posts. I'm growing quite frustrated having wasted most of my evening on this with no luck.

I'm not quite sure what all of the files downloaded are for. I paid more attention to the ffms2-r292 download and went to drop the ffms2.dll, FFMS2.avsi, and just in case the ffmsindex.exe in my avisynth plugins folder. Don't know what the .exe file was for as nothing opens if I click on it. Low and behold it I already had ffms2.dll files in my plugins folder... but they seemed a bit different so I moved the existing ones out of the way to replace with the ones just downloaded.

Anything else I can do to get it to work? I'm using the following code.

Code: Select all

FFVideoSource("E:/Anime/Kurei-nai/Kurenai - 01.mkv")

I basically get, in either Vdub or premiere....

Avisynth error:
FFVideoSource: Can't open "E:/Anime/Kurei-nai/Kurenai - 01.mkv"

Code: Select all

DirectShowSource("E:/Anime/Kure-nai/Kurenai - 01.mkv")

works so I know the problem must lie withe ffmpegsource

[Scintilla]

Avisynth error:
FFVideoSource: Can't open "E:/Anime/Kurei-nai/Kurenai - 01.mkv"

First thing to try: change all those slashes to backslashes.

[StarMasayume]

XD Weird it still seemed to work with the slashes for directshow.

Edited the slashes... still says no function named ffmpegsource. I'm thinking it's not installed or the right files aren't where they need to be.

Maybe I'm having avisynth problems in general. I tried to use MPEG2Source to open a d2v file in premiere (just trying it out, I normally cut out the clips I want as avi files) but it told me something was inconsistent with the dgdencode.dll files... which I don't see what's wrong. Maybe I've been downloading codecs and plugins from too many places trying to get stuff to work XD

[Mister Hatt]

There are multiple formats for d2v, each version of mpeg2source can only use the compatible d2v file. The d2v file must be made with the indexer packaged with your mpeg2source.
Slashes can be in either direction, avisynth handles converting to Windows paths for you.
You don't have FFMS2 installed properly or you are not loading it properly.

GUYS DON'T USE VIRTUALDUBMOD IT MAKES YOU LOOK STUPID.

[Kariudo]

GUYS DON'T USE VIRTUALDUBMOD IT MAKES YOU LOOK STUPID.

And telling people not to use something without giving an explanation makes you look stupid.
Once again, it gets the job done, and it is good enough.

Vdubmod has been the standard recommendation in the site's most referenced guide since 2005, and the newest update to that guide was completed less than a year ago. Change doesn't happen so quickly.

Perhaps you would like to enlighten the rest of us on the advantages of vdub over vdubmod keeping in mind that mkv support is a non-issue as the standard advice here (besides buying the dvds instead) is to use DSS/FFMPEGSource

[Mister Hatt]

Should use avisynth for everything anyway, so no need to use crappy VFW demuxers. DSS should never be used either, same goes for FFMS. The only plugins worth using are select mpeg2dec versions (mpeg2dec3, mpeg2dec3db, and dgindex) along with FFMS2 and very occasionally, DSS2. I guess DGNVDec is also acceptable. As far as VDub vs VDubMod, the mod version is years out of date, lacks speed optimisations, outright does some audio things wrong, fucks with your colourimetry, and includes the ability to open ogm files (but not ogv or ogg) internally. It also does some strange things with aspect and avisynth but I don't think anyone here does anything that would be impacted by that. The point is that it's outdated. VDub and avisynth development is somewhat done hand in hand, the latest vdub always supports the latest avisynth with internal optimisations for various things and vice versa. Using a current avs with an old vdub, especially one as flawed as vdubmod is just stupid.

[Qyot27]

Don't know what the .exe file was for as nothing opens if I click on it.

It's a CLI program, it doesn't have a GUI (and typically when one double-clicks a CLI app, the Prompt appears for a split second before disappearing again). You use it from the Command Prompt/Terminal. It simply indexes the files externally so they don't have to be indexed when you open the script for the first time in WMP, VDub, or so on.

[StarMasayume]

Hmn okay so that's normal. Am I right that all I was supposed to do was copy those files to the plugins folder for avisynth 2.5? Is there something else I'm missing to get it to work properly? The code is right as far as I am aware of.

I'm at work so can't try anything till I get back home, but would still like to gain some ideas of what else I can actually try doing.

[Qyot27]

Various things to try:

Reducing the path down to just the filename, thus eliminating any errors that might be in the rest of the line. Make sure if you do this to keep the script in the same folder as the file you're trying to open.

Alternately, you can install Ninotech Path Copy or use the 'Copy Name as Text' or 'Copy Full Path Name as Text' options in ExplorerXP. Then you can paste it into the script without needing to type it all out yourself. ExplorerXP has at least one advantage over Ninotech, which is the ability to properly copy foreign characters such as Japanese kana, which Ninotech chokes on; on the flip side, though, it's a little cumbersome, whereas Ninotech integrates into regular Windows Explorer. I have both installed and simply use whichever one I need at the moment.

Vista and Win7 users can forgo the above and use the Copy as Path option. Just hold down Shift while right-clicking to bring up the alternate context menu. Copy as Path (and even Open Command Window Here) are both options on it. You can move those onto the regular right-click menu by modifying entries in the Registry, but as I don't use Vista or Win7 I can't vouch for how to do that.

Updating FFMS2. I'm fairly sure v2.13 is newer than revision 292, but I'm not altogether sure of that. The changelog mentions a v2.14, but I've not seen any builds of that one floating around unless it's just an alias for a newer revision (which is currently at r309).

Yes, C:\Program Files\AviSynth 2.5\plugins is the correct place to put all those things.

[Kariudo: Fix't bbcode]

[Qyot27]

Alternately, you can install Ninotech Path Copy[/code] or use the 'Copy Name as Text' or 'Copy Full Path Name as Text' options in [url=http://www.explorerxp.com/]ExplorerXP.

Gah, I wasn't paying attention to my BBcode tags. Here's the fixed links:

Ninotech Path Copy

ExplorerXP