FFmpegSource

[akupenguin]

Originally Posted by d'Oursse

ask the gstreamer developpers about the different versions of ffmpeg. For a developper it's a pain. Example : 3 or 4 days ago : they changed the options of configure. It's not 3 years at all.

That's the build system, not the api. It affects compiling ffmpeg, not compiling programs which use libav*, unless you imported a copy of ffmpeg into your source tree.
Incompatible api changes require incrementing the major version, which has happened twice in the last 3 years.

[Myrsloik]

My attempt at a sample accurate audio source. Not very tested yet. Only supports mpeg1 layer 2/3 audio in mkv so far. Should seek accurately in the same formats as the video source.

Usage: FFAudioSource(string source, int track = -1)

Experimental audio source

[ficofico]

I've tried to make a script including this line

(mvfpsflowscd(30,oversample=16,blurradius=4)

but when I open the file with FFMpegSource avisynth give me an error



Where I've to write "linear=false" ?

[IanB]

ChangeFPS(...., linear=False)

And it will be on line 10 of one of your *.AVSI files.

Also oversample=8 might probably avoid the issue as well.

[Mr_Odwin]

What there is of this so far is great. I used it today on an flv file and the video part seemed to work fine, even though flv isn't mentioned in the readme.

[Myrsloik]

A new version has been released with several improvements to seeking.

FLV files have now been confirmed to work perfectly
VOB files now appear to have frame accurate seeking (at least with the single test vob used) but no rff flags applied (won't ever happen)
Normal MPG files should seek without showing artifacts

Feel free to report the results with any other containers you use.

[Leak]

Originally Posted by Myrsloik

VOB files now appear to have frame accurate seeking (at least with the single test vob used) but no rff flags applied (won't ever happen)

Wouldn't applying rff flags be a must for proper IVTCing of badly flagged video? (Looking at that URL in your sig I'm rather surprised to read the above... )

np: Lusine - Flat (Cepia Remix) (Podgelism)

[Myrsloik]

Doing that using only libraries coming from ffmpeg you have to first decode the video to find out the flags. So in the end all you'd get is a very slow dgindex/dgdecode clone if you're lucky. I don't see a great demand for that.

If you find me a nice mpeg/vob/ts parsing library it would be a completely different thing though...

[infernix]

works on wine! tried only on demuxed .vc1 source so far:

FFmpegSource(source="FEATURE_1_FEATURE_2.VC-1.stream.0.vc1",track=-1,seekmode=0,timecodes="test.timecodes",cache=true,cachefile="test.ffcache")
AssumeFPS(23.976)

takes a minute or two to index for 18GB. And I can't seek, or it takes incredibly long (probably the latter).

Thanks so much i hate the VFW interface, I couldn't get it to read vc1

[Myrsloik]

Version 1.3 has been released (see first post) and some other items have been added to the possible improvements list.

[ficofico]

Myrsloik can you post the version 1.1? This version doesn't work in my batch script.

With the tool avs2avi, the avs file is like: ffmpegsource("temp.mp4) when temp.mp4 it's a x264 8000 bitrate .The conversion in xvid with avs2avi with the 1.1 release it's good, with this version doen't work, it give me error.

The dll in plugins directory it's still 1.1 (after I've seen that 1.3 doesn't work) but the dll in system32 are from 1.3 version.

thanks

[Myrsloik]

No, if you can't be bothered to actually tell me what the error is it can't be that important.

[ficofico]

the error it's



the script it's very simple



Before upgrade ffmpeg works well.

[Harukalover]

ficofico: Hint: Read the manual when upgrading to newer versions.

There is no function named ffmpegsource anymore.

/me points to ffvideosource

[ficofico]

ops..................sorry, but I've assume that the name was a constant.

[Myrsloik]

My guess is that you're using the ffmpeg dlls from a previous version/other program.

[ficofico]

no no, now I've upgrade the dll and change the script, now work. Thank you and sorry for the mistake.

[Myrsloik]

It's time to get some input from the silent masses...

What should I do about audio handling in general?

Is there any reason at all to keep FFAudioSource when FFAudioRefSource actually works (if you've got the space)?

Should FFAudioRefSource be merged with FFVideoSource (faster file opening the first time if you want both audio and video)?

Should I waste many more hours to try to get FFAudioSource to work (it's highly unlikely it'll ever be good for more than previews)?

...the next version will also have postprocessing.

[Mr_Odwin]

I personally would like FFVideo and FFAudio/FFAudioRef merged; perhaps like QTInput/Directshowsource where there is an audio=true/false option?

[IanB]

From a user perspective it is much more straight forward to them if you do the AudioDub of the audio and video internally for them.

From a programming perspective I know it sucks having function arguments left, right and centre to control need behaviour.