FFmpegSource

[Myrsloik]

Don't use ademuxedfile for actual demuxing (bad argument name). It's not meant to be used that way and is only written when actually needed for decoding.

No idea why vorbis would fail but as the manual says FFAudioSource is very experimental.

[Blue_MiSfit]

Well, I love the fact that ffmpegsource seems to be frame accurate, and doesn't rely on DirectShow!

However, building the indexes is very slow on (for example) a 15GB HD-DVD or BluRay -> MKV remux (I've been working on a lot of these). Is there any way to index ahead of time? i.e. before I actually fire up AVSp, write an FFMPEGSource(...) script and hit F5 - then wait while the app hangs for 10 minutes or so while it builds the index? Maybe someone could cobble together a DGIndex workalike - nothing complex - just a little GUI or even a CLI app to show you that yes in fact, indexing is happening.

I ask for too many things :) If I could code, I could give. I should do something about that.

~MiSfit

[Myrsloik]

So what you want is either a (command line?) program that starts the indexing process so it can run in the background OR that it shows a progress bar when opening files? Both should be fairly easy to do after I get around to making indexing a separate pass which I plan to anyway. Not that I will have time to make it happen until sometime in 2011 with my schedule though...

[asdfsauce]

I was going to ask for this too (command line), but didn't think anyone else would be interested in that. I'm working on an avisynth based encoder and things would be more seamless if files were indexed beforehand.

Another thing I had to say was when I merge one file with using one source and then merge it with a file using ffmpegsource, when playback reaches the ffmpegesource clip it becomes really laggy, whereas it would play fine by itself. Any ideas on what may be going on?

[Myrsloik]

The only reason I can think of would be audio (aligned/unaligned splice) doing something odd. If you don't have audio in the clips then I really have no idea why it happens.

[vlada]

Don't use ademuxedfile for actual demuxing (bad argument name). It's not meant to be used that way and is only written when actually needed for decoding.

So I guess I'd better use mkvextract, AVI-Mux GUI, DGIndex and MP4Box for demuxing, right?

Btw. I'd be interested in the CLI indexer with progress indicator too.

asdfsauce
What kind of application are you working on? Maybe we exchange some ideas and experiences because I'm working on an Avisynth based transcoder too. I'm using PyGTK and currrently my application is able to take any input (including DVD), automatically set the best possible parameters (size, resolution etc.) and convert it to AVI/MPEG-4 ASP.

Sorry for this OT.

[asdfsauce]

The only reason I can think of would be audio (aligned/unaligned splice) doing something odd. If you don't have audio in the clips then I really have no idea why it happens.

I figured it out, thanks. Had nothing to do with FFMPEGSource. :)


asdfsauce
What kind of application are you working on? Maybe we exchange some ideas and experiences because I'm working on an Avisynth based transcoder too. I'm using PyGTK and currrently my application is able to take any input (including DVD), automatically set the best possible parameters (size, resolution etc.) and convert it to AVI/MPEG-4 ASP.

Sorry for this OT.

Cool, I'll PM you about it.

[Myrsloik]

Version 1.19 released. It's only a an evolutionary update with a newer ffmpeg and a filter that allows swscale to be used for colorspace conversions/resizing separately. It also autodetects the number of threads to use for decoding and exports a few more values of questionable importance.

[rhester72]

Any hope for AC3-in-AVI? If your plugin supported that, I could ditch DirectShowSource entirely. :)

Rodney

[cweb]

Any hope for AC3-in-AVI? If your plugin supported that, I could ditch DirectShowSource entirely. :)

Rodney
There's nicac3source for that already...

[rhester72]

True enough, but that requires a manual demux and handlers for every container type, which rather defeats the purpose of having something like FFmpegSource to begin with.

Rodney

[Myrsloik]

Would you consider donating a sample file to the cause? I seem to have run out of ac3 in avi files recently.

[rhester72]

Certainly:

http://www.mediafire.com/?m1drsc2wjvn (10.64MB)

Rodney

[Atak_Snajpera]

I have a problem with FFmpegSource with mkv (avc). I use this script in my app in order to get some info from source. The problem is that I get incorrect framerate (24.07 instead of 23.976). If I use DirectShowSource everything is ok and I get correct 23.976 value.

LoadPlugin("C:\Users\Dawidos\Desktop\RipBot264v1.9.8\Tools\AviSynth plugins\FFmpegSource\FFmpegSource.dll")
video=FFmpegSource("C:\Users\Dawidos\Desktop\1.mkv",vcachefile="C:\Temp\RipBot264temp\job1\FFmpegSource.cache").ConvertToYV12()
LoadPlugin("C:\Users\Dawidos\Desktop\RipBot264v1.9.8\tools\AviSynth plugins\NicAudio\NicAudio.dll")
audio=NicAC3Source("C:\Temp\RipBot264temp\job1\audio.1.ac3")
AudioDub(video,audio)
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Framecount")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Framerate")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","AudioRate")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","AudioChannels")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","AudioLength")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Width")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Height ")
Trim(0,-1)

sample
http://www.mediafire.com/?egp0ldqwgxi

[martino]

Don't think there's anything wrong with it. The MKV probably has timecodes (I haven't checked myself) where not all timestamps are the same (implying it not being CFR) and it does some sort of averaging on the overall framerate, maybe?

[tebasuna51]

Don't think there's anything wrong with it. The MKV probably has timecodes (I haven't checked myself) where not all timestamps are the same (implying it not being CFR) and it does some sort of averaging on the overall framerate, maybe?

Checking the Atak_Snajpera sample I found this data from MediaInfo and TimeCode_Track2.txt (MKVextract):
MEDIAINFO:
General
Duration : 21s 696ms

Video
Duration : 21s 666ms
Frame rate : 23.976
FrameCount : 520

Audio
Duration : 21s 696ms
----------------------------------
Timecodes:
0.000000 # frame 0
42.000000
83.000000
...
21605.000000
21647.000000 # frame 519

With these data I can obtain different frame rate calculations:

Theoretic:
24000 / 1001 = 23.976024

Using FrameCount and Duration (General&Audio or Video)
520 / 21.696 = 23.967551 # error = 0.00847
520 / 21.666 = 24.000738 # error = -0.02471

Using Timecodes
(with 1 ms precision the FrameCount limit the fps precision)
519 / 21.646 = 23.976716 # error = -0.00069
519 / 21.647 = 23.975608 # error = 0.00041 best approach
519 / 21.648 = 23.974501 # error = 0.00152


But never something like 24.069126 # error = -0.093102
obtained with ffmpegSource.

Edit: Timecodes obtained with FFmpegSource identical to obtained with MKVextract

[Myrsloik]

Not a bug, documented behavior and MATROSKA DOES NOT HAVE A FRAMERATE. That last part should be repeated as often as possible since lots of people waste their time looking for it. What is returned is just (number of frames - 1)/(last dts - first dts) which FOR CFR FILES WILL BE FAIRLY CLOSE.

[tebasuna51]

...
What is returned is just (number of frames - 1)/(last dts - first dts)
...

Yes, this was expected, but in the sample:

(number of frames - 1)/(last dts - first dts)
519 / 21.647 = 23.975608 # error = 0.00041 best approach

and not 24.069126 # error = -0.093102
obtained with the Atak_Snajpera avs.

[Myrsloik]

Is it noticable? Is this even a meaningful discussion?

You take a rational value, round it to a fixed point number to store as a timestamp and then expect the actual rational number to be recoverable. Good luck with that.

If you know that much I can only recommend assumefps() from the start. Anything else will only disappoint you. And if you say "make a special case" I will say "write the function yourself to detect it".

[Atak_Snajpera]

if you know that much I can only recommend assumefps() from the start.

I've already done that

LoadPlugin("C:\Users\Dawidos\Desktop\RipBot264v1.9.8\Tools\AviSynth plugins\FFmpegSource\FFmpegSource.dll")
video=FFmpegSource("C:\Users\Dawidos\Desktop\1.mkv",vcachefile="C:\Temp\RipBot264temp\job1\FFmpegSource.cache").ConvertToYV12().Assume(value_taken_from_MediaInfo)
LoadPlugin("C:\Users\Dawidos\Desktop\RipBot264v1.9.8\tools\AviSynth plugins\NicAudio\NicAudio.dll")
audio=NicAC3Source("C:\Temp\RipBot264temp\job1\audio.1.ac3")
AudioDub(video,audio)
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Framecount")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Framerate")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","AudioRate")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","AudioChannels")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","AudioLength")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Width")
WriteFile("C:\Temp\RipBot264temp\job1\info.txt","Height ")
Trim(0,-1)

[vlada]

I have a problem with the latest FFmpegSource (version 1.19). I'm getting this error:

Avisynth error:

Script error: FFAudioSource does not have a named argument "ademuxedfile"

Was this parameter removed? I can use "acachefile", it just looks to me that demuxing audio file is much faster then decoding and caching the whole audio track.

[Myrsloik]

It was renamed to acachefile2 to obfuscate it. I also managed to omit it in the changelog.

And now for a general service announcement: I am a cheap bastard. What this means for you (forum readers, dvd collection backupers and all you people who get mkvs from the internet that I have to pretend don't exist) is that my webhosting will stop being free any day now. Since I'm extremely cheap I also won't bother to buy hosting elsewhere until it really stops working. (stops working is defined by not being available for a few weeks)

[vlada]

So is there a reason why I shouldn't use acachefile2? I'm not using it for real demuxing anymore, as you have suggested. But the decoding (caching) takes really long time and I can't even show a progress dialog for it.

Thinking about it, it might be faster to use a CLI demuxer (ffmpeg, mp4box, mkvextract etc.) and then use NicAudioSource to open the audio files. But will be a much more work (programming) for me. Is the audio caching really so important? Couldn't it be avoided (I know I've asked it before)? I understand it might be important for editing, but I'm only interested in transcoding so far.

[Myrsloik]

If you shouldn't be using it at all it wouldn't be there. You're also right that decoding to wav/piping with ffmpeg.exe will do exactly what you want since you only need to access the audio linearly.

[AnnaFan777]

Hi, I found some flvs cannot be opened with ffmpegsource
but can play it with winpyflv players..
would you take a look?
thanks..

http://www.cloudgate.org.tw/event/2007/spring_present/flv/
http://www.cloudgate.org.tw/event/2007/spring_present/flv/oculus_150s.flv

[Myrsloik]

WhileI can't look at the files right now or anytime soon my guess is that the video itself is encoded in a way that's not yet supported by ffmpeg. FLVs can contain a few different combinations (exactly which i can't remember right now). Try again later or try it with a recent compile of ffplay.exe and see if it works there.

[Malow]

how ffmpegsource handle the color matrix from mpeg2?

the output from a xdcam ex video (mpeg2) become Rec.601, i have to use colormatrix to convert to Rec.709 and make colors right.

edit: WOOOOPS, my bad. i was using a "experimental" import plugin for sony vegas, and it was not making the correct tranfer.

the problem was the plugin, not ffmpegsource.. ;)

[Malow]

im having another weird thing (but now is not my fault ;) )

opening xdcam ex mp4 file (mp4 with mpeg2+pcm) it lost 2 frames on video start and repeat twice the last frame, like the video was "slipped" to the right.

ffmpeg.exe doesnot cause this...

[Myrsloik]

Does it also happen when you use seekmode=-1? Unfortunately I'll still be away from my real computer for a few more weeks so I can't do any testing/debugging right now.

[Malow]

im doing alot of testing, this is what ive got so far:

carbon coder and vegas works perfect, get all frames, no cut/dupes. (with mp4 wrapped to mxf)

in one example, ffmpegsource cuts the 2 first frames, and duplicate the last one two times (making the framecount correct)

ffmpeg.exe cut the 2 first frames also, but instead of duplicate the last two it duplicate the first (after the 2-frame cut)

the same happens with the wrapped mxf.

so ive demuxed the mp4, and looks like the problem is in the mpeg-2 video. looks like the video does not start with a keyframe (its possible?) and dgmpeg/ffmpeg/virtualdub skip the start of video to the third frame. vdub show as being an i-frame.

looks like the video from these cameras are not so friendly. the mp4 looks "non-standard", as basicaly no splitter works with it (besides ffmpeg).

ive tried all options/combinations and the result are the same...

i believe theres nothing to do about it.. :(

[Blue_MiSfit]

I'm having a tricky time with 1080i VC1 and ffmpegsource!

See my thread here for more details:
http://forum.doom9.org/showthread.php?t=139340

Basically, the source is a BluRay disc, dumped to a video-only MKV. When I open with ffmpegsource the indexing takes ages (of course ;)), and before it finishes, the avsP error log starts spewing all kinds of nonsense, and the application totally hangs. I close and re-open, and indexing starts all over :(

Ideas?
~MiSfit

[vlada]

AFAIK libavcodec doesn't support interlaced VC-1 so it is no wonder it crashes.

[Blue_MiSfit]

Figured as much :(

~MiSfit

[CruNcher]

@Myrsloik

i converted .WMV entirely to .MKV now the problem is FFMPEGSource seems to have problems with those files :( every seekmode crashes after the encoding is finished and it only displays this

[matroska @ 01A66DC8]Unknown seekhead ID 0xbf
[matroska @ 01A66DC8]Ignoring seekhead entry for ID=0x1549a966
[matroska @ 01A66DC8]Ignoring seekhead entry for ID=0x1654ae6b
[matroska @ 01A66DC8]Unknown entry 0xbf in cues header
[matroska @ 01A66DC8]Unknown entry 0xbf in info header
[matroska @ 01A66DC8]Unknown entry 0x73a4 in info header
[matroska @ 01A66DC8]Unknown entry 0xbf in track header
avis [info]: 1280x528 @ 23.98 fps (3633 frames) <- 1 Frame got missing

http://s1.directupload.net/images/080712/44vs8enp.jpg

VLC,Mplayer and Gabest Source filter have no Problem with this file (Haalis own has Sync issues) :(

Converted (MKV):

General
Complete name : D:\x264test\vegas.mkv
Format : Matroska
File size : 36.0 MiB
Duration : 2mn 31s
Overal bit rate : 1986 Kbps
Encoded date : UTC 2008-07-12 09:04:02
Writing application : gdsmux
Writing library : Haali DirectShow Matroska Muxer 1.8.122.18

Video
Format : VC-1
Codec ID : WVC1
Codec ID/Hint : Microsoft
Width : 1280 pixels
Height : 528 pixels
Display aspect ratio : 2.424
Resolution : 24 bits
Language : English

Audio
Format : WMA2
Codec ID : 161
Codec ID/Info : Windows Media Audio 2
Duration : 2mn 31s
Bit rate : 128 Kbps
Channel(s) : 2 channels
Sampling rate : 44.1 KHz
Resolution : 16 bits
Language : English


Original (WMV):

General
Complete name : D:\x264test\Vegas_1280x528.wmv
Format : Windows Media
File size : 36.1 MiB
Duration : 2mn 31s
Overal bit rate mode : Variable
Overal bit rate : 1999 Kbps
Maximum overal bit rate : 2013 Kbps
Movie name : What Happens in Vegas
Encoded date : UTC 2008-03-13 23:08:59.613
Copyright : 2008 Fox

Video
Format : VC-1
Format profile : AP@L2
Codec ID : WVC1
Codec ID/Hint : Microsoft
Duration : 2mn 31s
Bit rate mode : Variable
Bit rate : 1863 Kbps
Width : 1280 pixels
Height : 528 pixels
Display aspect ratio : 2.424
Frame rate : 23.976 fps
Resolution : 24 bits
Bits/(Pixel*Frame) : 0.115

Audio
Format : WMA2
Format profile : L3
Codec ID : 161
Codec ID/Info : Windows Media Audio 2
Duration : 2mn 31s
Bit rate mode : Variable
Bit rate : 128 Kbps
Channel(s) : 2 channels
Sampling rate : 44.1 KHz

hope you can look into this (if you back) :)

maybe your used Libavformat is to old in 1.19 now ?

[Myrsloik]

Libavformat isn't used for matroska, haali's library is. Since you say haali's splitter also has problems with it you should probably show the file to haali and see what he says first.

[CruNcher]

@Myrsloik
are you sure you useing Haalis libraries from the output i get

[matroska @ 01A66DC8]Unknown seekhead ID 0xbf
[matroska @ 01A66DC8]Ignoring seekhead entry for ID=0x1549a966
[matroska @ 01A66DC8]Ignoring seekhead entry for ID=0x1654ae6b
[matroska @ 01A66DC8]Unknown entry 0xbf in cues header
[matroska @ 01A66DC8]Unknown entry 0xbf in info header
[matroska @ 01A66DC8]Unknown entry 0x73a4 in info header
[matroska @ 01A66DC8]Unknown entry 0xbf in track header

it looks like libavformat to me ? could it be that it falls back to it, i can't find any reason for it on my side (another loaded ffmpegsource) or something of that kind im useing your latest released FFMPEGSource 1.19 3,68 MB (3.862.528 Bytes)
i talked with Haali and he also confirmed his parser would never show these information that's ffmpeg typical debug output, so im suprised over here what's going on, maybe the combination libavcodec and haalis parser isn't compatible in this case ?

[TheFluff]

@Myrsloik
are you sure you useing Haalis libraries from the output i get

[matroska @ 01A66DC8]Unknown seekhead ID 0xbf
[matroska @ 01A66DC8]Ignoring seekhead entry for ID=0x1549a966
[matroska @ 01A66DC8]Ignoring seekhead entry for ID=0x1654ae6b
[matroska @ 01A66DC8]Unknown entry 0xbf in cues header
[matroska @ 01A66DC8]Unknown entry 0xbf in info header
[matroska @ 01A66DC8]Unknown entry 0x73a4 in info header
[matroska @ 01A66DC8]Unknown entry 0xbf in track header

it looks like libavformat to me ? could it be that it falls back to it, i can't find any reason for it on my side (another loaded ffmpegsource) or something of that kind im useing your latest released FFMPEGSource 1.19 3,68 MB (3.862.528 Bytes)
i talked with Haali and he also confirmed his parser would never show these information that's ffmpeg typical debug output, so im suprised over here what's going on, maybe the combination libavcodec and haalis parser isn't compatible in this case ?
I... what? No seriously, WTF?

Since you apparently love copypasting gigantic walls of text I'll just go ahead and do the same...
From ffshared.cpp, function CreateFFmpegSource():
if (av_open_input_file(&FormatContext, Source, NULL, 0, NULL) != 0)
Env->ThrowError("FFmpegSource: Couldn't open %s", Args[0].AsString());
bool IsMatroska = !strcmp(FormatContext->iformat->name, "matroska");
av_close_input_file(FormatContext);

if (IsMatroska) {
return new FFMatroskaSource(Source, VTrack, ATrack, Timecodes, VCache, VCacheFile, ACacheFile, PPString, PPQuality, Threads, Env);
} else {
// Do a separate indexing pass, enjoy the constructor sideeffects
if (SeekMode == -1)
delete new FFmpegSource(Source, VTrack, ATrack, Timecodes, VCache, VCacheFile, ACacheFile, PPString, PPQuality, Threads, -2, Env);
return new FFmpegSource(Source, VTrack, ATrack, Timecodes, VCache, VCacheFile, ACacheFile, PPString, PPQuality, Threads, SeekMode, Env);
}
As you may or may not have guessed, FFMatroskaSource() calls no libavformat functions whatsoever.

What I'm guessing happens is that you get those errors from libavformat when the file is first opened to check if it's a Matroska file or not, and Haali's parser then fails on it because the file is broken in one way or another. Go back and do your homework, do not pass GO and do not collect your $200 salary.

(Seriously why do I even have to explain this? You noted in your original post that Haali's splitter has issues with this file when used as standalone, what makes you think it won't have issues when used from ffmpegsource? Magic?)

[CruNcher]

@TheFluff

Yeah in that case it's clear where that debug output comes from i didn't suspect that the file is parsed first by libavformat to confirm that it is indeed Matroska, thought it's decided by the file extension, so yeah we have to wait for Haali checking this file on Monday and most probably fixing the libraries :(. Im useing FFMPEG as long as this isn't fixed in the meantime for these problematic files.


(Seriously why do I even have to explain this? You noted in your original post that Haali's splitter has issues with this file when used as standalone, what makes you think it won't have issues when used from ffmpegsource? Magic?)


Yeah no not Magic i mixed up the complexity levels here at least i hoped FFMPegSource wouldn't crash Avisynth in this particular case, like the Directshow Filter isn't crashing the Player.

[ajp_anton]

Would it be possible to add some kind of frame information into a corner, like frame type, size, number... ?

[Myrsloik]

What can be easily done is to set a variable in every getframe call so you can write it on the clip/use it in scripting. I haven't looked that closely yet but I think that should would very well for the frame type.

Frame size? dimensions? bytes? explain what and why you want it.

The frame number is already possible to add using one scriptclip line so that will never be added.

[Dragon4333]

i was using FFmpegSource on making a lossless with filters and the video went form 25:40 to 6 min. anyone got any ideas why this is happening

[TheFluff]

i was using FFmpegSource on making a lossless with filters and the video went form 25:40 to 6 min. anyone got any ideas why this is happening

Is the framecount the same? Is the file VFR? What container is it?

[Dragon4333]

yea the framecount is the same its 37280 for both. and yea its a vfr o yea and if it help the framerate is 95.923261 for the both of them and the raw is mp4 and then i made a lossless with filter so its in a avi now. and i have the timecode thing from FFmpegsource

[CruNcher]

@Myrsloik

The unsync problem seems to be found it's only happening with ffdshow, tough the crash with ffmpegsource is still a mistery to me :(
here is the file http://mirror05.x264.nl/CruNcher/force.php?file=.//vegas.mkv

funny thing is i now get another error message in the cmd [vc1 @ 0194CE30]Illegal DC VLC and a imediate player crash (closing down of mpc)
and i slowly get the impression it has something todo with the soundtrack as without it, it doesn't seem to crash ffmpegsource.

[Myrsloik]

Released 1.20 which is just a recompile with a newer FFmpeg but maybe some more stuff works now. Haven't had time to look at any of the problem files yet.

Asking for help in private messages WILL NOT WORK IF YOU END EVERY SENTENCE WITH LOL. (this is not necessarily because I won't answer the question but if you don't know what the dot thingy is you're very unlikely to understand the answer)

[Dragon4333]

ok i tried adding in the timecodes thinking that it would fix the prob but it did not so now i have a video that plays for 6min or so then audio that last for 25:40. so that did not work any other ideas

[martino]

What does "adding in the timecodes" mean? You want to say you muxed the encoded video that you got from ffmpegsource with timecodes and the audio, and the length came out different?

[CruNcher]

@Myrsloik
Thx for the new Compile, tough it still doesn't work (i guess it was no wise decission to abondon every container yet, before testing interoperability completely) i also tried atrack=-2 no response the new version doesnt show any messages anymore but just stops doing anything except getting the fps to X264 :(

[TheFluff]

Opening an AVI file now gives you an assertion failure in avidec.c.
file: libavformat/avidec.c; line: 1029; expression: st2->time_base.den == ast2->rate

The same thing happens with Aegisub when using the ffmpeg provider so I suspect some enterprising libavformat patcher broke something a few weeks ago.

[sh0dan]

@Zhelkus: You cannot get support for your illegally obtained material here. Read the rules.