ffdshow tryouts project: Discussion & Development

[Kado]

@thuan
thanks. "keep aspect ratio" enabled in mpc did the trick.

[sjchmura]

As a general question....

The fork is working VERY well with VistaMCE and the "plugin" that allows FFDShow to work.

However, how long with this "fork" continue? Will we always have the fork is is the plan, at some point, to merge back to a single repository?

Thanks for all the incredible work. FFDShow keeps me from using a MAC :)

[Leak]

However, how long with this "fork" continue? Will we always have the fork is is the plan, at some point, to merge back to a single repository?
Well, given that MPC proper is as good as dead and no-one that's still active has write access to it's SVN I doubt there's going to be a merger down the road...

Same goes for ffdshow...

np: Luke Vibert - Clikilik (Chicago, Detroit, Redruth)

[Wilbert]

The use of the [0,255]->[0,255] is justified because they say it's a more smooth conversion from YUV to RGB which could cause less banding. For me, I think the best should be the compromise solution.
Perhaps so. But when doing a [0,255]->[0,255] the black portions are too black and the bright ones are too bright. Imo, that's more annoying than any banding.

[Dark_Angel_PT]

Just a small question\request:

When using the translation mode of ffdshow, wouldn't it be a lot more useful to keep the original language showing in these dialogs, so we can compare what we entered and the original.

http://img521.imageshack.us/img521/7716/ffdshowyi5.jpg

I suggest the original string should always be kept above the text box, to help translating. Sometimes I forget what was there in the first place, i have to be changing the languages back and forth to check what i entered.

[FredThompson]

I've had very poor performance with MPEG2 4:2:2 and libmpeg2 decoder in the past few builds of ffdshow. If I open a file with MPC then move the position slider, the returned video is not playing. The position indicator will continue to move but the displayed video does not change, almost as if ffdshow's libmpeg2 decoder is returning blank frames. FWIW, the MPC and ffdshow configurations appear to be the same as in the past. Do other people have this problem with MPEG2 4:2:2 and ffdshow's libmpeg2 decoder?

[Leak]

Do other people have this problem with MPEG2 4:2:2 and ffdshow's libmpeg2 decoder?
Any idea where I could get hold of such an MPEG sample to test this? DVDs usually are 4:2:0 I think?

[chros]

I found the way.
* Enable "Uncompressed" and "Check for DTS in WAV" at the foot note of DTS.
* Raise the merit value.

Thanks, I'll try it !!!!

[Valeron]

@haruhiko:
Thanks for ur reat job! A much faster subtitle rendering engine compare to vsfilter! Though some advanced effects r still limited.
I can play some low bitrate 1080p AVC encode with subtitle flawless with my old Barton now.:thanks:

[Thunderbolt8]

how much cpu power does vsfilter take anyway on a c2d with 2.8ghz ?

[Valeron]

how much cpu power does vsfilter take anyway on a c2d with 2.8ghz ?

depend on what subtitle u r going to render, what final resolution to overlay on, whether advanced effects or not. all these factors will affect the rendering power need.

[Thunderbolt8]

hm its either an .srt or .ass subtitle on lets say 1080p resolution. using ffdshow with postprocessing for video decoding and ac3 filter for audio, haali splitter. for vsfilter picture size: original heigth, rest are standart settings I guess

[Valeron]

c2d at 2.8GHz can handle 1080p AVC decoding even with libavcodec(the one in ffdshow) without too much problem if the bitrate don't go too high(2x~30Mbps maybe). libavcodec is single thread nowadays unless the AVC encode u r going to play is multi-splice coded.
the subtitle rendering thread will be dispatched to another core imo, so there's no problem unless u've already got shutter in the decoding process.

yes, NO advanced effect here. i'm just talking about plain text subtitle. i achieved my goal just with an Barton@2Ghz(with vsfilter i got 10%~20% higher CPU load and then met sub-async). the subtitle rendering process will never become painful for c2d imo.

[haruhiko_yamagata]

Just a small question\request:

When using the translation mode of ffdshow, wouldn't it be a lot more useful to keep the original language showing in these dialogs, so we can compare what we entered and the original.

http://img521.imageshack.us/img521/7716/ffdshowyi5.jpg

I suggest the original string should always be kept above the text box, to help translating. Sometimes I forget what was there in the first place, i have to be changing the languages back and forth to check what i entered.Yes, maybe when we have time.

[TheShadowRunner]

hey guys, it seems Vobsub is completely broken in the latest builds (from september), is it a known issue?
By broken i mean it either crashes the player or displays nothing.
Later,

TSR

[Boardlord]

hey guys, it seems Vobsub is completely broken in the latest builds (from september), is it a known issue?
By broken i mean it either crashes the player or displays nothing.
Later,

TSR

I had that too, but also with older builds. Whenever I encounter such vobsub files, I run them through vobsub 2.23 (get it from Doom9 download library) and then they load fine with ffdshow. :)

[clsid]

If it only crashes with specific files, then please upload a sample file.

[SBeaver]

A fresh x64 build would be nice now, I'd like to try the new half-ass multithreaded h264 decoder and see how it works.

[Shakey_Jake33]

Strange, since I use 32 bit ffdshow along with Zoom Player and Media Player Classic and my S/PDIF Passthrough works perfectly. I do need to check the "Maximize S/PDIF Compatibily" checkbox though. That's on Vista 64 with a Sound Blaster X-Fi Platinum.

Well ever since vista was released I've been reading about people like you who say everything is ok, maybe creative has some workaround in their drivers but it doesn't work for anyone else.

Just so we are clear on this, I hope all of you actually have a way to tell what signal is going to the reciever.
From all information I have gathered there should be no way to passthrough ac3/dts using 32bit filters in vista x64.
I apologise if I'm talking about something completely different here, or if this has already been cleared up, but I have an X-Fi XtremeMusic and ffdshow's SPDIF passthrough works perfect for me, although as the above poster states, 'Maximize S/PDIF Compatibility' does need to be enabled, otherwise the DTS sound is garbled.
Vista Home Premium 64-bit here.

I do also have an onboard HD Audio codec if anyone would like that tested.

[SBeaver]

I apologise if I'm talking about something completely different here, or if this has already been cleared up, but I have an X-Fi XtremeMusic and ffdshow's SPDIF passthrough works perfect for me, although as the above poster states, 'Maximize S/PDIF Compatibility' does need to be enabled, otherwise the DTS sound is garbled.
Vista Home Premium 64-bit here.

I do also have an onboard HD Audio codec if anyone would like that tested.

Please do try it with the onboard audio, with 32bit version of ffdshow then of course.
I'm still very interested in understanding why creatives cards work and most others don't.

[Shakey_Jake33]

Please do try it with the onboard audio, with 32bit version of ffdshow then of course.
I'm still very interested in understanding why creatives cards work and most others don't.

I'll install the drivers for my onboard tomorrow and post the results.

I know for sure my speakers (Logitech Z-5500's) are recieving an untouched AC3/DTS passthrough because Dolby Digital/DTS are displayed on the reciever, and the audio is untouched because the various effects I have enabled in ffdshow (like normalisation) do not effect it.
Also, the AC3 transcoding functionality of ffdshow works perfectly too, with my video files with 5.1 AAC outputting as 5.1 AC3 fine.

The SPDIF also works using the MPC internal codec, as well as PowerDVD and WMP.

[cc979]

@haruhiko_yamagata
if you can remember the 'video decoder configuration' display problem i mentioned - i had more time to trace it, seems the my problem started at rev. 1444 as rev. 1443 works fine

cheers

[haruhiko_yamagata]

@haruhiko_yamagata
if you can remember the 'video decoder configuration' display problem i mentioned - i had more time to trace it, seems the my problem started at rev. 1444 as rev. 1443 works fine

cheersRev 1444 is a very small fix. I have no idea about it. Anyway thank you for your time...

[haruhiko_yamagata]

hey guys, it seems Vobsub is completely broken in the latest builds (from september), is it a known issue?
By broken i mean it either crashes the player or displays nothing.
Later,

TSRVobsub support in ffdshow has been very incomplete from the start. I have broken it recently and fixed it at rev 1485.
I can reproduce "displays nothing" but cannot reproduce "crash the player". Please send us the sample, if it is possible.

[_xxl]

New test build:
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2007-September/035877.html
http://rapidshare.com/files/58407533/ffdshow_rev1485_20070926_xxl.exe.html

[LigH]

Now that Theora 1.0 beta 1 was released - will you update the supported VfW encoder + the decoders?

[haruhiko_yamagata]

New test build:
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2007-September/035877.html
http://rapidshare.com/files/58407533/ffdshow_rev1485_20070926_xxl.exe.html
Sample file : [Eclipse-gg] Manabi Straight - 07 (1024x768 h264) [A7E82AE2].mkv
CPU : core2duo E6700
rev1487_20070926_clsid : User: 249s, kernel: 1s, total: 251s, real: 261s, fps: 138.8, dfps: 133.4
rev1485_20070926_xxl : User: 64s, kernel: 2s, total: 66s, real: 210s, fps: 523.3, dfps: 165.9

Great! The multithreaded version is 24% faster.

[Thunderbolt8]

hm, why does clsid's newer (svn) version not support this yet? wasnt this part of a general update or something like that?

btw. how does it come, when comparing a file using vc-1 codec ffdshow basically only uses 1 core , while when playing a .mkv or .ts h264 file the cpu usage seems to be distributed evenly to both cores, according to task manager with clsid's 1487 ?

[_xxl]

http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2007-September/035877.html
The attach patch gives ~20-30% speedup on single sliced CABAC content.
Basically, the code decodes up to 128 macroblocks in one
thread while doing prediction+idct+deblock of the previously decoded
128 blocks in another thread.

My build is based on latest h.264 multithreaded patch.

http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2007-September/035880.html
Well, as already discussed previously :
- slice based parallelism depends on the video, so will not be always
possible. Furthermore, it scales as much as the encoder was scaled, so
though it's an easy solution, it's not a pretty one

- cabac / reconstruction parallelism : relatively good speed up,
though it will depends on the bitrate of the video ( low bitrate -> bad
scaling, very high bitrates -> bad scaling too ), and no scaling over 2
CPUs. There again, not necessarily pretty, but effective. More effective
imho than slice based, and sufficient for decoding anything up to
1080i30 40 Mbit/sec on a C2D, I would say.

- frame based, which I think should be the "best" method : a priori
very scalable ( if x264's threading efficiency is achieved ), no
constraint on the video except for vertical downward motion vectors,
but, alas, not tested, so scalability is hypothetical.

All that to say I'm torned between a theorically clean ideal solution,
and a dirty but already working one. One thing is sure, I don't like
slice based parallelism :)

Libavcodec VC-1 is not multithreaded yet.

[Thunderbolt8]

My build is based on latest h.264 multithreaded patch.
yes, but I thought it was the same with clsid's version, since its even 'newer' according to the svn version? so I guess that patch wasnt included there and has to be implemented manually ?

[clsid]

The patch that xxl used is still experimental and not yet part of the official FFmpeg code base.

[Thunderbolt8]

allright then.
I tested boths versions, clsid' 1487 and xxl' patched 1485, with hs264 .ts and remuxed .mkv star wars broadcasts, but at least with a look on task manager cpu usage screens I almost couldnt make any difference out between them, in fact im even tempted to say the 1487 version was slightly faster (have a c2d 6300 running @2,8GHz). could this be possible?

[foxyshadis]

Multithreading the decoder is only important when you can't achieve a full framerate already. If you have a fast processor, that'll mostly be in HD encodes, like BD/HDvD. Most HD discs are encoded with several slices, I've seen reports of 3-8, so this will help a lot for playing them.

[Shakey_Jake33]

Seem to be facing a bug right now, where if I try to play a DVD with LPCM audio using ffdshow as the audio decoder, I get no sound.

Here's the funny thing though - when I set AC3 and DTS to decode using the internal MPC filters, it works fine. But when I set them to decode with ffdshow, all AC3/DTS content works fine, but LPCM does not! What has LPCM got to do with AC3/DTS? God knows.

Here's another wierd thing - the same DVD's work 100% fine when extracted to my DVD's as VOB files!

Now, if I enable MPC's internal LPCM decoder, the DVD's will still try and use ffdshow, as if the player is detecting the DVD's to be having AC3 sound or something (though MPC reports LPCM at the bottom). Is it a bug in ffdshow or MPC? I'm not sure.

Using SPDIF, but the same happens over analogue.

[chros]

I tested boths versions, clsid' 1487 and xxl' patched 1485, with hs264 .ts and remuxed .mkv star wars broadcasts, but at least with a look on task manager cpu usage screens I almost couldnt make any difference out between them, in fact im even tempted to say the 1487 version was slightly faster (have a c2d 6300 running @2,8GHz). could this be possible?
For me, it's the same: I can't tell the difference between them ...
So is this new patch good for only for multi-slice based encoding or for all (I tested both: new apple trailers (1080p) and mine (x264 720p)) ?

PS: _xxl: thanks for your build!

[haruhiko_yamagata]

For me, it's the same: I can't tell the difference between them ...
So is this new patch good for only for multi-slice based encoding or for all (I tested both: new apple trailers (1080p) and mine (x264 720p)) ?

PS: _xxl: thanks for your build!You could try beta3 vs rev 1487. If rev 1487 is faster, the sample is multi-slice based encoding. The new patch is good for both.

[yesgrey]

I think I have found a bug...
In ffdshow's avisynth tab, when you change some of the text in the avisynth commands box, the text only is keeped if you click OK while seeing the tab. If before clicking OK you change to another tab for setting another parameter, when you return to the avisynth tab your changes were lost.

[Delerue]

I think I have found a bug...
In ffdshow's avisynth tab, when you change some of the text in the avisynth commands box, the text only is keeped if you click OK while seeing the tab. If before clicking OK you change to another tab for setting another parameter, when you return to the avisynth tab your changes were lost.

Another thing: if you export FFDShow settings to a reg file, the text inside the avisynth tab won't be restored.

[Mc Onyx]

The new patch is good for both.

Sorry, but do you mean there is a finished patch that enables multithreading on all encodes, even those not encoded with slices?

[Leak]

Another thing: if you export FFDShow settings to a reg file, the text inside the avisynth tab couldn't be restored.
Okay, that definitely looks like a bug to me.

As for the other problem - the script is not stored in the configuration (and therefore not used) until you hit the "Apply" button, and it's always been that way: the edit box value is read from the current configuration every time the AviSynth page is (re-)loaded, which happens when you switch back and forth between config pages.

The difference in regard to most other controls is that their values are stored (and used) in the configuration immediately upon editing, but with an AviSynth script you'd both get script errors most of the time while you're typing and possibly a lot of lag since re-initializing AviSynth with a new script can take several seconds depending on the filters used. So it's contents are only stored when hitting "Apply" on purpose.

I'll take a look at the reg file problem.

EDIT: That's a problem with regedit, actually - the scripts are written to the file with their linebreaks intact, so regedit's parser will just skip what it thinks are broken lines.

But if you just export the whole ffdshow configuration from regedit, it'll produce the exact same problem... so I'd have to replace the newlines in the AviSynth script with something else when storing it to the registry and undo that when reading from it - that'll need a bit more investigation...

np: Supermayer - Two Of Us (Geiger Mix) (Kompakt Total 8 (Disc 1))

[haruhiko_yamagata]

Sorry, but do you mean there is a finished patch that enables multithreading on all encodes, even those not encoded with slices?The patch is not finished as you can read from the link above. The patch enables multithreading on all encodes (as far as I have tested).

[yesgrey]

Leak,
Thanks for clarifying my "bug". It makes sense.

[foxyshadis]

Can you hook onblur() from the filter menu or one of the other teardown messages, to pop up a 'save me?' box? I haven't worked with the side menu at all, I have no idea what's possible.

[Leak]

I haven't worked with the side menu at all, I have no idea what's possible.
Same here, but after a quick check I couldn't find anything that would get called specifically when the page is changed.

And TBH, if you're editing a bigger script you'll probably be happier with doing it in an external text editor anyway. Or just don't forget to hit "Apply" after changing or pasting in the script.

np: Burnt Friedman - Machine In The Ghost (ft. Barbara Panther) (First Night Forever)

[vinetu]

I'll take a look at the reg file problem.

EDIT: That's a problem with regedit, actually - the scripts are written to the file with their linebreaks intact, so regedit's parser will just skip what it thinks are broken lines.

But if you just export the whole ffdshow configuration from regedit, it'll produce the exact same problem...
I'm not sure about complex scripts,but the simple ones can be writen in one line and then there is no problem with exporting and importing.

Example:
ColorMatrix(mode="Rec.709->Rec.601").SeparateFields().fft3dfilter().LanczosResize(640,480).Weave()

[zambelli]

When is the next beta planned for?

[haruhiko_yamagata]

When is the next beta planned for?Not very near, I think. We have some issues to fix.
I'm implementing RGB<->YUV conversion options.

[_xxl]

Not before PAFF and h.264 multithreaded for all x264 encodes.
Maybe E-AC3 decoder should be added and dts issue fixed.

[ACrowley]

Not before PAFF and h.264 multithreaded for all x264 encodes.
Maybe E-AC3 decoder should be added and dts issue fixed.


These are exactly the Updates most people need !

What do you think, when will there be a EAC3 Decoder build ?

[yesgrey]

I'm implementing RGB<->YUV conversion options.

Just the PC vs rec levels option or also the custom matrix?