FFmpegSource

[vlada]

Originally Posted by Myrsloik

A possibly fixed version of the cli index app is now available from http://ivtc.org/new/beta/ffmsindex-progressfix.7z

Try it and report the results.

Thanks for the updated version. Unfortunately it still doesn't work for me unless I'm doing something wrong. The CLI output is still a single line. I get no output during indexing, after it finishes, I get 33% and 67% progress messages. Any idea what might be wrong?

[CruNcher]

@Myrsloik
Any progress on the GPU Decoding support ?

[Myrsloik]

When I say 2011 I MEAN 2011. If anyone in Sweden wants to buy a new very lightly used GF8400 GS send me a message. The only thing I've worked on is the other link and there's a serious bug somewhere in that project. But look forward to 2011, it will be a year to remember.

[vlada]

During the Christmas I spent quite a lot of time on finishing my transcoding application. I discovered some bugs and problems in FFmpegSource which I would like to report.

1) The first and most serious bug is related to index reading and creating. I found out that files with accented character in path can't be opened. There is a problem with codepage conversion somewhere. Let's say my file is C:\ěščřž\video.avi. Simply using FFVideoSource would fail. But if I specify the location of index to C:\temp\index.tmp, then it opens. The standalone FFMSIndex has the same problem. I use cp1250 for AviSynth script encoding.

2) Another problem is that some errors and warnings are probably output to STDOUT and then it is sent to encoders STDIN and the output is corrupted. It might be a mistake on my side too, because it only happens if I run it from my program. If I run the same command separately the created video is correct, but the encoder's output is mixed with error/warning messages from FFmpegSource. Would it be possible to disable all such messages, maybe by an option/switch?

3) Then I found some FLV (VP6F/MP3) files, which produce a silent audio track. The files work correctly in ffmpeg.

If you are interested into samples showing the #3 issue, let me know. If you need any further details to the first 2 problems, I can provide that too.

Thanks a lot for looking into these problems. I can't release my program without having a fix or workaround for the first 2 points.

[Myrsloik]

1. Does it work with avisource or directshowsource or any other source?
2. Call FFNoLog() first in the script in the next version
3. It's always good to have more test clips

Could you also make a small program that shows your problem with the indexing app? that way it's much easier to get TheFluff to fix it.

If you want to test what will be the next version find me in #darkhold on rizon and I'll send it to you (or anyone else who wants to test stuff).

[Myrsloik]

New beta released, mostly because FFmpeg was getting a bit old. The big news is greatly improved and slightly broken TS parsing. It now uses Haali's splitter (needs to be installed or TS files won't work) to provide almost frame accurate seeking. Almost meaning that if you access the first 200 frames or so it won't work right but if you only access later frames it has in my testing always worked perfectly. (yes, very weird)

So if you use it you might want to do something like

FFVideoSource(...).Trim(200,0)

for now.

[SAPikachu]

Hi,
First of all, thanks for your great filter, it helped me a lot.

I'm using FFMpegSource in my program, it can get key frame list from index file and seek by key frames. With beta 3, seeking to a key frame is very fast. But it is significantly slower in beta 4. For mp4 container, it is ~5x slower with beta4 than with beta3. MKV is faster than mp4, but still slower than with beta3.
Could you look into this problem? If you need some video samples, please let me know. Thanks in advance.

[Myrsloik]

I forgot some debug code when seeking that made it decode many more frames. Redownload beta 4 and it will be fixed.

[SAPikachu]

The problem is solved, thanks a lot!

[vlada]

Originally Posted by Myrsloik

1. Does it work with avisource or directshowsource or any other source?
2. Call FFNoLog() first in the script in the next version
3. It's always good to have more test clips

Could you also make a small program that shows your problem with the indexing app? that way it's much easier to get TheFluff to fix it.

1) The problem is only in index location, not in the file location. So there are no problems with the file using AviSource or DirectShow source.

2) Thanks for the improvement!

3) For the not working Flash Video see this file (4,5 MB).


As for my problems with getting progress from ffmsindex.exe, here is a sample code: http://rapidshare.com/files/179395825/test.zip.html (4 kB).

To run it you would need PyGTK (= Python, PyGTK, PyGobject, PyCairo), GTK+ and Python Win32 Extensions. All installers can be easily found and downloaded. If you (or TheFluff) prefer, I could provide a compiled version including all libraries, but this way you can look into the source code and modify it.

[loliconxd]

one question.

the ffmpeg.. 2.0 support vfr?

[TheFluff]

Originally Posted by loliconxd

one question.

the ffmpeg.. 2.0 support vfr?

What do you mean by "support"? It can read timecodes from the loaded file and write them to a timecodes file, but since Avisynth doesn't support VFR, it will set the framerate to some arbitrarily chosen bogus value (for mkv's it's based on the average frame duration, for everything else it's based on the duration of the first frame) and let you decide what you want to do with it. If you mean convert VFR to CFR, that is supported too, just read the manual.

vlada: I will look at your problem sometime after next weekend.

[guest0815]

Where did the timecodes' decimal places go with ffmpeg2?

Originally Posted by ffmpegsource("23,976 cfr.mp4",timecodes="ff1.txt")

#timecode format v2
0.000000
41.708333
83.416667
...

#timecode format v1
Assume 23.976000

Originally Posted by ffvideosource("23,976 cfr.mp4",timecodes="ff2.txt")

#timecode format v2
0
41
83
...

#timecode format v1
Assume 23.976000
0,0,24.390244
1,2,23.809524
3,3,24.390244
4,5,23.809524
...

thank you

[Myrsloik]

They will return in the next version. (if I remember to fix it)

[TheFluff]

@vlada: I've been looking at your problem with ffmsindex.exe and can't reproduce it with any code I've written myself. For example, this perl script:

#!/usr/bin/perl
my $res = `ffmsindex -f "blah.mkv"`;
$res =~ s/\r/\r\n/g;
print $res;

prints this, as expected:

Indexing, please wait... 0%
Indexing, please wait... 1%
Indexing, please wait... 2%
Indexing, please wait... 3%
Indexing, please wait... 4%
Indexing, please wait... 5%
Indexing, please wait... 6%
Indexing, please wait... 7%
(etcetera)
Indexing, please wait... 100%

Writing index... done.

I can't see how this is a problem on my side. I'm doing things pretty much exactly like every other CLI app, including x264, except I'm using the C++ iostream instead of x264's plain c stdio. I don't know what you're doing wrong but it's probably something trivial (such as forgetting to convert \r to \r\n or something).

[MadRat]

Thanks for the update, I'm eager to use the release version.

[lubczyk]

So what do I use to convert from vfr to cfr in the syntax? Do I set one and or both fpsnum and/or fpsden and what values are expected? I know the framerate of my video BTW.

[TheFluff]

Originally Posted by the fucking manual

FFVideoSource(string source, int track, bool cache = true, string cachefile = source + ".ffindex", int fpsnum = -1, int fpsden = 1, string pp, int threads = -1, string timecodes, int seekmode = 1)
(...)
fpsnum & fpsden:
For VFR -> CFR conversion. Setting fpsnum <= 0 means a 1:1 relation with the encoded frames.

Other hints:

• num stands for "numerator" and den stands for "denominator"; as in a fractional number.
• Both parameters are integers.
• fpsnum defaults to -1; fpsden defaults to 1.
• Standard NTSC framerate is not 29.97fps, it's 30000/1001fps exactly.
• If you are completely lost, check out the Avisynth documentation for AssumeFPS/ChangeFPS/ConvertFPS.

I'm sure you can figure it out from there.

[lubczyk]

Originally Posted by TheFluff

Other hints:

• num stands for "numerator" and den stands for "denominator"; as in a fractional number.
• Both parameters are integers.
• fpsnum defaults to -1; fpsden defaults to 1.
• Standard NTSC framerate is not 29.97fps, it's 30000/1001fps exactly.
• If you are completely lost, check out the Avisynth documentation for AssumeFPS/ChangeFPS/ConvertFPS.

I'm sure you can figure it out from there.

Thank you!!! That helped alot.

[lubczyk]

Any plans for subtitle support? It would be great if FFmpegSource eventually evolved into a total DirectShowSource (Video, Audio, Subtitles) replacement.