Log in

View Full Version : ffdshow tryouts project: Discussion & Development


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 [111] 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308

tal.aloni
6th December 2008, 09:02
Haruhiko,
1. the tabs are ordered by the order of execution,
so "Decoder options" should be on top, (right above "processing")
I would say that the "Decoder options" in the video decoder should be moved upward, and not the other way around.

2. I'm feeling much more comfortable with "Decoder options",
I'm assuming in the future it may be used for other settings.
(Dialog normalization for example)

Thanks for the feedback,
Tal

haruhiko_yamagata
6th December 2008, 10:40
Haruhiko,
1. the tabs are ordered by the order of execution,
so "Decoder options" should be on top, (right above "processing")
I would say that the "Decoder options" in the video decoder should be moved upward, and not the other way around.

2. I'm feeling much more comfortable with "Decoder options",
I'm assuming in the future it may be used for other settings.
(Dialog normalization for example)

Thanks for the feedback,
Tal
OK, but let's finalize beta6 before adding new features.
Please commit after beta6.

Leak
6th December 2008, 10:42
I said below "Processing", but excuse me...
If it is called "Decoder options" it should be consistent with video, above "Output".
Shouldn't "Decoder options" be up there anyway? After all those options are all applied before any filtering is done while the "Output" options all apply after filtering...

EDIT: *reads rest of thread* Yeah, what Tal.Aloni said... :)

np: Boy Robot - My Heart's Still Beating (Glamorizing Corporate Lifestyle)

haruhiko_yamagata
6th December 2008, 11:18
Shouldn't "Decoder options" be up there anyway? After all those options are all applied before any filtering is done while the "Output" options all apply after filtering...

EDIT: *reads rest of thread* Yeah, what Tal.Aloni said... :)

np: Boy Robot - My Heart's Still Beating (Glamorizing Corporate Lifestyle)
Yes, but still below OSD?
OSD is not in the preset settings.

tal.aloni
6th December 2008, 11:20
OK, but let's finalize beta6 before adding new features.
Please commit after beta6.

OK, I'll commit after beta 6.

Here is the latest design:
http://iknowu.net/files/public/ffdshow/drc/Processing-DRC-RC5.png

Tal

p.s.
IMO, OSD should be in the preset settings,
but I can see that it will take much work to implement that.

haruhiko_yamagata
6th December 2008, 11:26
In r2314, if DTS is set to libavcodec and DTS is checked under Output -> pass-through, files with DTS don't play. Works fine with libdts though.Please update to the latest and if the problem is still there, please send us a sample.
Also information about your system and settings may be required.

haruhiko_yamagata
6th December 2008, 11:27
I have cleaned most bugs.
Anything that should be fixed before beta6?

haruhiko_yamagata
6th December 2008, 11:29
OK, I'll commit after beta 6.

Here is the latest design:
http://iknowu.net/files/public/ffdshow/drc/Processing-DRC-RC5.png

Tal

p.s.
IMO, OSD should be in the preset settings,
but I can see that it will take much work to implement that.Looks nice.
Moving OSD to preset settings isn't worth while IMO.

fastplayer
6th December 2008, 12:08
I can confirm when I visit OSD page, it turns to enabled.
Thanks for the fix!
Visiting DirectShow control - both in audio and video configuration - still triggers the "Apply" button state to switch. That is right after a fresh install with default settings and without any setting changed whatsoever. This has got to be reproducible... :confused:

tal.aloni
6th December 2008, 12:52
it seems that DRC is not implemented for libdts,
I looked upon the code, the dynamic range values are being read from the stream, but are not being used.

(with my latest patch, it is now easy to test DRC effects)

Tal

p.s. the tracks have DRC support when using AC3Filter.

Edit:
from the libdca project page: (http://www.videolan.org/developers/libdca.html)

some of the missing things are: Joint channels coding, Dynamic range, etc... - see the TODO file

haruhiko_yamagata
6th December 2008, 14:20
Thanks for the fix!
Visiting DirectShow control - both in audio and video configuration - still triggers the "Apply" button state to switch. That is right after a fresh install with default settings and without any setting changed whatsoever. This has got to be reproducible... :confused:
Reproduced, but only at the first time after clean installation.
If it is the case, I know why. It's not worthy of fix.

fastplayer
6th December 2008, 14:40
OK, then let's leave it like that. It's not a showstopper but a bit confusing nonetheless :)

STaRGaZeR
6th December 2008, 16:48
I have cleaned most bugs.
Anything that should be fixed before beta6?

ffdshow doesn't detect H.264 pulldown, present in NTSC HDDVD streams. But not that important since HDDVD is dead.

Sample in a moment.

EDIT: http://www.megaupload.com/?d=QNO25KDZ (50MB)

LoRd_MuldeR
6th December 2008, 17:05
It seems http://www.xvidvideo.ru/ is down. Is there another source for recent ffdshow-MT builds?

Yong
6th December 2008, 19:21
http://y0ngc6.googlepages.com/ffdshow_rev2346_20081204-mt.exe ;)

BatKnight
6th December 2008, 19:40
http://y0ngc6.googlepages.com/ffdshow_rev2346_20081204-mt.exe ;)
That one is old, I already have 2407 from xvidvideo.ru but now that it's down I don't know where to get the latest MT build.

Thanks

Bat

tal.aloni
6th December 2008, 19:41
Here is ffdshow-MT rev. 2407: (originated from xvidvideo.ru)

http://iknowu.net/files/public/ffdshow/ffdshow_rev2407_20081201-mt.exe

anyway, I'm sure xvidvideo.ru will be back soon, it's not the first time.

LoRd_MuldeR
6th December 2008, 19:42
http://y0ngc6.googlepages.com/ffdshow_rev2346_20081204-mt.exe ;)

This seems to be a pretty old build. The latest build I downloaded from xvidvideo.ru before it went down was rev2407 :confused:

khagaroth
6th December 2008, 19:52
ffdshow crashes if the language file is bigger than 103 704 bytes. After the switch to unicode, my language file is much bigger.

And considering the translation, would it be possible to get language template file (English) with all the translatable strings. The translation mode, apart from not working correctly (doesn't allow to enter long strings, randomly deletes some already translated strings, it isn't possible to translate some dialogs etc.), is not very suitable for tracking changes between releases, and tracking the changes in the rc script and crosschecking with resource.h to get the id's is a PITA.

Yong
6th December 2008, 20:20
This seems to be a pretty old build. The latest build I downloaded from xvidvideo.ru before it went down was rev2407 :confused:

its r2433 btw :p
i forgot to change to rev number on iss script :D
and btw the file "version.ver" does not up to date,
#define VERSION_MAJOR 1
#define VERSION_MINOR 0
#define VERSION_BUILD 5
#define VERSION_QFE 2353
#define VERSION_BUILD_DATE "02/12/2008"
#define VERSION_BUILD_TIME "16:10:41UTC"
i always get the latest code from svn repository before compiling them, it just the rev number is old doesnt mean its old build, dont worry :p
edit: wait, r2413 is mt build, r2433 is normal build :P
edit2: 2413 just contain some 64bit fixes for xvid codes, nothing major update to ffmpeg-mt.

LoRd_MuldeR
6th December 2008, 20:29
its r2433 btw :p
i forgot to change to rev number on iss script :D

Sorry, didn't notice. The configure dialog says r2346 too ;)

Eragon4ever
6th December 2008, 21:21
And considering the translation, would it be possible to get language template file (English) with all the translatable strings. The translation mode, apart from not working correctly (doesn't allow to enter long strings, randomly deletes some already translated strings, it isn't possible to translate some dialogs etc.), is not very suitable for tracking changes between releases, and tracking the changes in the rc script and crosschecking with resource.h to get the id's is a PITA.
True, maybe using something like TortoiseSVN would be better.

The TortoiseSVN project uses gettext PO (portable object) files for its translation. PO files are plain text, so you can even translate using a normal text editor. The only thing you have to take care of is that the editor can handle the UTF-8 charset.

Thunderbolt8
6th December 2008, 21:33
would it be possible to implement multi core support for mpeg2 in ffdshow(-mt) as well? sounds a bit stupid, but I got problem with most interlaced 1080i mpeg2 caps with my C2Q @2,75
with delinterlacing activated (ffmpeg, yadif etc.) im slightly over the verge to delay, meaning the delay slowly increases and the movie gets out of sync :S
(not even need to speak of additional sharpening, then its way too slow). using haali, I tried libav and libmpeg, ffmpeg deinterlacer, yadif and others, but speed remains a little too slow for fluent playback :/

clsid
6th December 2008, 21:39
You would need to ask that question to the ffmpeg-mt devs, not to us. But afaik, the MT API of ffmpeg-mt is very generic and will eventually be used for several video formats, at least all of the MPEG based ones (MPEG-2, MPEG-4, H.264, etc.).

haruhiko_yamagata
7th December 2008, 11:00
ffdshow crashes if the language file is bigger than 103 704 bytes. After the switch to unicode, my language file is much bigger.
Thank your for report. fixed at rev 2438.

And considering the translation, would it be possible to get language template file (English) with all the translatable strings. The translation mode, apart from not working correctly (doesn't allow to enter long strings, randomly deletes some already translated strings, it isn't possible to translate some dialogs etc.), is not very suitable for tracking changes between releases, and tracking the changes in the rc script and crosschecking with resource.h to get the id's is a PITA.I would like to improve translation support code, just don't have time to...

fastplayer
7th December 2008, 12:53
What is the limit now for language files?
I want to add this info to the changelog.

haruhiko_yamagata
7th December 2008, 13:06
ffdshow doesn't detect H.264 pulldown, present in NTSC HDDVD streams. But not that important since HDDVD is dead.

Sample in a moment.

EDIT: http://www.megaupload.com/?d=QNO25KDZ (50MB)Thank you for the sample.
I'll implement after beta6.

haruhiko_yamagata
7th December 2008, 13:12
What is the limit now for language files?
I want to add this info to the changelog.Practically no limitation as far as we edit using text editor.
256KB for the [-1] section.
32KB for one page of the dialog.
It must be UTF-16 with BOM, little endian.

Strings that are longer than 260 cannot be translated from GUI.
The translate mode may have some other bugs.

fastplayer
7th December 2008, 13:16
OK, since there's no actual limit in file size, I think it's enough to say that a bug was fixed that limited the translation file size.

Leak
7th December 2008, 14:43
Practically no limitation as far as we edit using text editor.
256KB for the [-1] section.
32KB for one page of the dialog.
It must be UTF-16 with BOM, little endian.
Well, as far as I can see you've made the limit 4 times larger, but wouldn't allocating memory based on the size of the file on disk instead of a fixed constant make more sense?

np: Boy Robot - Loving You Makes Me Nervous (Glamorizing Corporate Lifestyle)

MatMaul
7th December 2008, 15:13
Excellent. Hope FLAC (not like anyone uses libavcodec for it anyway, buggy) and LPCM come next if they don't already do that.
done for flac, patch sent to ffmpeg.
EDIT : can I have some samples for LPCM ?

haruhiko_yamagata
7th December 2008, 15:28
Well, as far as I can see you've made the limit 4 times larger, but wouldn't allocating memory based on the size of the file on disk instead of a fixed constant make more sense?

np: Boy Robot - Loving You Makes Me Nervous (Glamorizing Corporate Lifestyle)
Yes, but it won't over 256KB. Even if it does, it won't crash.

fastplayer
7th December 2008, 16:21
How complete is RV40 support? Complete enough to make it into the changelog?

Snowknight26
7th December 2008, 18:48
can I have some samples for LPCM ?

32-bit LPCM samples? Only thing I can find is 16/24-bit.

Inventive Software
7th December 2008, 18:53
How complete is RV40 support? Complete enough to make it into the changelog?

RV40 in ffmpeg is still not 100% though, so anything in ffdshow will be incomplete.

clsid
7th December 2008, 19:57
I have just tested a 32-bit build of ffdshow on Vista x64 and libfaad2 fails to load. Video decoding is working fine. Can anyone confirm this issue?

MatMaul
7th December 2008, 19:57
32-bit LPCM samples? Only thing I can find is 16/24-bit.
nevermind, I just read the code ans this is already supported so I don't need any samples.
thanks anyway.

STaRGaZeR
7th December 2008, 20:06
I have just tested a 32-bit build of ffdshow on Vista x64 and libfaad2 fails to load. Video decoding is working fine. Can anyone confirm this issue?

Works fine here. Never had a problem with libfaad2.

Snowknight26
7th December 2008, 23:59
Another r2314 issue (yea, I know, old build). With DTS passthrough set and no cable connected to S/PDIF or HDMI for audio, another instance of ffdshow opens up and plays 8000Hz, 16-bit, mono PCM static.

flanger216
8th December 2008, 01:01
I have just tested a 32-bit build of ffdshow on Vista x64 and libfaad2 fails to load. Video decoding is working fine. Can anyone confirm this issue?

Confirmed, using the latest mt build.

haruhiko_yamagata
8th December 2008, 11:03
I have just tested a 32-bit build of ffdshow on Vista x64 and libfaad2 fails to load. Video decoding is working fine. Can anyone confirm this issue?
I can't reproduce. I don't have Vista64. I'm on Xp64.
Which revision does the problem start?

clsid
8th December 2008, 12:19
It is a brand new laptop, so I haven't tried any older builds. I will do some more testing later.

Mercury_22
8th December 2008, 12:38
I have just tested a 32-bit build of ffdshow on Vista x64 and libfaad2 fails to load. Video decoding is working fine. Can anyone confirm this issue?
Working here with ffdshow_rev2443_20081207_xxl_mt and MPC-HC 1.2.918.0 (32-bit :) )

tetsuo55
8th December 2008, 14:33
I have a feature request.

FFdshow currently supports several settings for RGB level conversion.

I would like to have a similar option as the resize window.

Use REC601 for resolutions Equal to or Under Y*X for everything else use REC709

Default settings for Y*X could be 800*600
Also some cases are quite tricky like 1920*586, which should obviously be decoded with REC709

clsid
8th December 2008, 14:59
I have just tested a 32-bit build of ffdshow on Vista x64 and libfaad2 fails to load. Video decoding is working fine. Can anyone confirm this issue?
Must have been a bad build. I have made a fresh build and it is working again.

MatMaul
8th December 2008, 15:13
Use REC601 for resolutions Equal to or Under Y*X for everything else use REC709
Use presets.

Snowknight26
8th December 2008, 18:41
With r2447, the High quality YV12 to RGB conversion checkbox is under both Output and RGB conversion.

Also, theres is a volume difference with AC3 decoding between libavcodec and liba52. The latter seems to be a bit more quiet.

whurlston
8th December 2008, 19:09
r2447 fixed my channel mapping issue with TrueHD. Thanks guys (MatMaul in particular I think).

leeperry
8th December 2008, 19:14
cool, Haruhiko fixed some blurring problem with small fonts.
but is there a way you could let us choose how blurry we want the subs post-processing to be ? I guess it's about 2X/3X AA/GDI or sumthing ?

ppl with projectors like very sharp subs...

:thanks:

LoRd_MuldeR
8th December 2008, 21:38
With ffdshow-MT r2452 I get "slow motion" playback in DVBViewer, even when no filter is enabled!

The strange thing is: As soon as I enable the "KernelBob" deinerlacer it will run smooth again. Yadif doesn't work :confused:

(Happens on both of my screens and with both, RGB and YUV output)

Any ideas? :thanks: