https://sourceforge.net/p/ffdshow/bugs/2015-01-28T14:55:42.667000ZRecent changes to bugs2015-01-28T14:55:42.667000Z2015-01-28T14:55:42.667000ZMarco Aurelio Lopes Filhohttps://sourceforge.net/u/mlopesf/https://sourceforge.netc700348a3500bfd9e693ae5a0aef98207e531d55

<div class="markdown_content"><p>We've noticed a graphics card mempory leak on ffdshow for H264 Videos. <br /> This is how we've tested:</p> <p>We have a program that uses directshow under Windows 7 64 bit. The frames are delivered to an opengl texture and displayed inside a opengl program. After looping a 15 seconds Videos on a intel i5/HD4600 machine with the latest drivers OpenGL returs a out of memory error. We've recoded the video into a divx mp4 and still using ffdshow to decode, no problem after 48 hours loop. The problems occurs after around 8 hours playing a Quad-HD Video of 15 seconds coded using After Effects H264.</p> <p>We've also tried a xvid video in avi container and it plays fine as well.</p> <p>It looks for me - although I don't know the internals of libav - that it's using graphics memory and GPU to decode and either libav or intel did a mistake and memory is not freed up.</p> <p>Please feel free to contact me for further information.</p> <ul> <li>Marco</li> </ul></div>

2013-08-20T08:45:07.234000Z2013-08-20T08:45:07.234000Zgeonhttps://sourceforge.net/u/userid-1428705/https://sourceforge.net9b9f36966ef8e2790a3706c69a3cfa2b8276c43b

<div class="markdown_content"><p>EDIT: its in not admin rights account. When in admin user, all works fine.</p></div>

2013-08-20T08:41:59.467000Z2013-08-20T08:41:59.467000Zgeonhttps://sourceforge.net/u/userid-1428705/https://sourceforge.net2ba34770840b227b5141c5a8b6ca1be4d1a52a58

<div class="markdown_content"><p>xpsp3, picasa 3.9, k-lite 9.8.0 basic</p> <p>when creating movie <em>with mp3</em> in picasa it doesnt work. Seems to me that its due to ffdshow audio decoder. Picasa show 0.0% done all the time. When disable ffdshow audio decoder, picasa works again.</p></div>

2013-03-27T08:32:10Z2013-03-27T08:32:10ZYORhttps://sourceforge.net/u/yor33/https://sourceforge.netc964af673ac2d2214dfe63b180f7e420bea24614

<div class="markdown_content"><p>ffdshow Do not play full HD-DTS <br /> <a href="http://img221.imageshack.us/img221/121/16956440.png" rel="nofollow">http://img221.imageshack.us/img221/121/16956440.png</a><br /> All Blu-ray movies HD-DTS is played to 1536 kbps with ffdshow !</p> <p>POWER DVD only plays the full DTS-HD See photo<br /> <a href="http://img14.imageshack.us/img14/6233/62407089.png" rel="nofollow">http://img14.imageshack.us/img14/6233/62407089.png</a></p> <p>Can this be fixed?</p></div>

2013-03-20T09:07:23Z2013-03-20T09:07:23ZIrina Arkhipetshttps://sourceforge.net/u/iarkh/https://sourceforge.net76f61e8be7d3cf0f5994151eb327c2e5fa0ac30c

<div class="markdown_content"><p>Probably, this is a duplicate of 2774167.</p> <p>My flash application uses video cam and crashes if there are two browser tabs with it currently.</p> <p>I've updated my FFDShow to the recent version a couple of days ago (1.3.4500).</p> <p>It uses video cam, and Mozilla crash report shows that crash happens because of some problems in FFDShow.</p> <p>Please let me know if stack trace from the report is not enough for you and some additional info from my side is necessary.</p> <p>Thank you in advance!</p> <p>Here is the report:<br /> Signature EMPTY: no crashing thread identified <br /> UUID 00f75f0c-2c0f-45de-9308-6a2af2130320<br /> Date Processed 2013-03-20 06:18:20<br /> Uptime 0<br /> Install Age 6.9 days since version was first installed.<br /> Install Time 2013-03-13 07:31:30<br /> Product Firefox<br /> Version 19.0.2<br /> Build ID 20130307023931<br /> Release Channel release<br /> OS Windows NT<br /> OS Version 5.1.2600 Service Pack 3<br /> Build Architecture x86<br /> Build Architecture Info GenuineIntel family 6 model 15 stepping 6<br /> Crash Reason EXCEPTION_ACCESS_VIOLATION_WRITE<br /> Crash Address 0x3f2025b8<br /> User Comments <br /> App Notes Cisco VPN</p> <p>AdapterVendorID: 0x0000, AdapterDeviceID: 0x0000, AdapterSubsysID: 00000000, AdapterDriverVersion: </p> <p>Processor Notes sp-processor04.phx1.mozilla.com_789:2008; Priority Job; MDSW did not identify the crashing thread; CSignatureTool: No signature could be created because we do not know which thread crashed<br /> EMCheckCompatibility True<br /> Winsock LSP MSAFD Tcpip [TCP/IP] : 2 : 1 :<br /> MSAFD Tcpip [UDP/IP] : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll <br /> RSVP UDP Service Provider : 6 : 2 : %SystemRoot%\system32\rsvpsp.dll <br /> RSVP TCP Service Provider : 6 : 1 : %SystemRoot%\system32\rsvpsp.dll <br /> VMCI sockets DGRAM : 0 : 2 :<br /> VMCI sockets STREAM : 0 : 1 : C:\Program Files\VMware\VMware Player\vsocklib.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{7B1151A2-BFAD-4E7E-BD53-7228C9E32614}] SEQPACKET 7 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{7B1151A2-BFAD-4E7E-BD53-7228C9E32614}] DATAGRAM 7 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{999E9BD5-F517-45C2-835E-97F626EA5B87}] SEQPACKET 4 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{999E9BD5-F517-45C2-835E-97F626EA5B87}] DATAGRAM 4 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{BE3C14EC-30BB-479A-B9E9-BBABA2E8A9E0}] SEQPACKET 3 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{BE3C14EC-30BB-479A-B9E9-BBABA2E8A9E0}] DATAGRAM 3 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{ED1A4FAB-05AD-4A2B-BD2C-ADDBAE9E4971}] SEQPACKET 0 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{ED1A4FAB-05AD-4A2B-BD2C-ADDBAE9E4971}] DATAGRAM 0 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{CDB238BA-F60D-4B99-B652-93872845E0E6}] SEQPACKET 1 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{CDB238BA-F60D-4B99-B652-93872845E0E6}] DATAGRAM 1 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{B6231C89-4845-45AB-B711-3B3C45031DE3}] SEQPACKET 2 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{B6231C89-4845-45AB-B711-3B3C45031DE3}] DATAGRAM 2 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{9D36F5B2-1B5E-4FDD-B7A5-77F5B02EDE6D}] SEQPACKET 5 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{9D36F5B2-1B5E-4FDD-B7A5-77F5B02EDE6D}] DATAGRAM 5 : 2 : 2 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{C597B604-18D8-4552-ABA6-FD6D2EDABFEE}] SEQPACKET 6 : 2 : 5 : %SystemRoot%\system32\mswsock.dll <br /> MSAFD NetBIOS [\Device\NetBT_Tcpip_{C597B604-18D8-4552-ABA6-FD6D2EDABFEE}] DATAGRAM 6 : 2 : 2 : %SystemRoot%\system32\mswsock.dll<br /> Adapter Vendor ID 0x0000<br /> Adapter Device ID 0x0000</p></div>

2013-03-03T21:47:52Z2013-03-03T21:47:52ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.netd475f6ce1090bd5b3422c938c2ea3a7056674135

<div class="markdown_content"><p>When I updated ffdshow from ffdshow_rev3914_20110629_clsid (from 2012) to ffdshow_rev4500_20130106 (Jan 2013), loading of MOVs into virtualdub put green/replicate frames at starts of vids with QuickTime.vdplugin/QuickTime64.vdplugin dated 8/20/2011. </p> <p>I uninstalled ffdshow_rev4500_20130106 and installed the older one ffdshow_rev3914_20110629_clsid from 2012 and the green frame drops disappeared, as were before 4500 update</p> <p>Verified in both 32 and 64 bit cases of ffdshow, vdub, and the QuickTime.vdplugin (incl QuickTime64.vdplugin) in Win7x64</p></div>

2013-01-19T13:24:12Z2013-01-19T13:24:12Zdanmhttps://sourceforge.net/u/dan3m/https://sourceforge.net20cb3aa45d6d3abca3046a02e6b494f841d3d7ac

<div class="markdown_content"><p>How to direct it?</p> <p>How does it work?<br /> i have Receiver +5 Speakers<br /> I tried to run it without success <br /> <a href="http://i50.tinypic.com/14japmu.png" rel="nofollow">http://i50.tinypic.com/14japmu.png</a><br /> [IMG]http://i50.tinypic.com/14japmu.png[/IMG]</p></div>

2012-11-05T09:55:04Z2012-11-05T09:55:04Zdisplayhttps://sourceforge.net/u/display1/https://sourceforge.netf287dfad197d05ef3a862e2b90862312ecdf1c99

<div class="markdown_content"><p>K-LITE 9.4 with win 7 64 <br /> <a href="http://img823.imageshack.us/img823/1111/1111hi.png" rel="nofollow">http://img823.imageshack.us/img823/1111/1111hi.png</a> ( ffdshow video decoder ) <br /> "Use ffdshow only in " All software Not updated at all ( Left blank ) Whatever happened to the software ???<br /> Direct "MARIT VERY HIGH" After I close the encoder is returns it to default from Merit : very high WHY ??</p> <p>When you will solve this problem?</p> <p>Same problem as well with sound<br /> <a href="http://img696.imageshack.us/img696/4598/2222xj.png" rel="nofollow">http://img696.imageshack.us/img696/4598/2222xj.png</a></p> <p>With these problems " VP7 decoder " <br /> <a href="http://img826.imageshack.us/img826/6399/3333j.png" rel="nofollow">http://img826.imageshack.us/img826/6399/3333j.png</a><br /> Can not adjust it </p></div>

2012-10-31T13:23:07Z2012-10-31T13:23:07Zdisplayhttps://sourceforge.net/u/display1/https://sourceforge.net0f1768f30619e99905f00a3fef69e85d58a1cff2

<div class="markdown_content"><p>1. Sound over AMD not as good as with Intel with FFDSHOW ,Does not make it sharp</p> <p>2. <a href="http://img521.imageshack.us/img521/2037/26872054.png" rel="nofollow">http://img521.imageshack.us/img521/2037/26872054.png</a> ( ffdshow audio decoder )<br /> In the picture with AMD 1055T Every time that I moves to - "MARIT VERY HIGH" After I close the encoder is returns it to HIGH<br /> Only with AMD processors.</p> <p>3.http://img41.imageshack.us/img41/8097/13180652.png ( ffdshow video decoder )<br /> In the picture with AMD 1055T Every time that I moves to - "MARIT VERY HIGH" After I close the encoder is returns it to HIGH<br /> Only with AMD processors.</p> <p>You can fix?</p></div>

2012-09-27T10:59:57Z2012-09-27T10:59:57Zdex Otakuhttps://sourceforge.net/u/dexotaku/https://sourceforge.netd89ee247a6add98c5649f2c9f203a7f3e5823711

<div class="markdown_content"><p>I'll hope this gets the point across clearly enough, and forgive me if I mess up the math:</p> <p>The integrated Dolby decoder evidently is doing does its math in quite literal a fashion, <br /> i.e. centre = 0.707R + .0707L [I know that's simplified, it's sqrt (0.5L) + sqrt (0.5R) if I have things correct] <br /> .. which works fine in an analogue system that has the headroom to do this without clipping, or with digital sources that "follow the rules" [i.e. where sqrt (0.5L) + sqrt (0.5R) never exceeds 0dBfs] but constantly causes clipping in the centre channel when done in the digital domain with material where the encoding party has maximised the volume.</p> <p>This can be remedied by using the volume filter and attenuating levels at least 7dB before the signal reaches the Dolby decoder, but this shouldn't be necessary as it is not transparent or obvious to most end users, who just hear distortion, don't understand why, and never use the filter again under the assumption that it's broken [when the real problem is the source material being processed].</p> <p>It could be more easily remedied and eliminate the need for manually-specified level pre-processing by taking the expectation of clipping by volume-maximised material into account beforehand by<br /> * attenuating the L and R signals before the decoder, eg. (0.5L), (0.5R) into the decoder, eliminating the possibility of clipping or <br /> * not merely processing and truncating the signal at decoder output [where the result exceeds 0dBfs but mathematically may have originally yielded valid unclipped signal outside of the valid range of the output quantisation depth] but attenuating it after processing and before requantising to the desired output format, again eliminating the possibility of clipping</p> <p>Additionally, to avoid unnecessary attenuation with program material that "follows the rules", a check could be added to the filter that enables "maximised mode" and applies the pre- or post- attenuation only if the summed level of sqrt(0.5L) + sqrtn(05.R) input exceeds 0dBfs. This would cause a "duck" in volume after the first loud channel-simultaneous peak but this would seem a better compromise than simply attenuating everything and users then finding that movies which "follow the rules" are wayyyyyy too quiet, while volume-maximised material sounds "normal".</p> <p>Hope that made sense.</p> <p>I like using the built-in decoder because I don't need to switch my outboard processor to do so and can still do things like run games with 5.1 audio at the same time as watching video. Because I use it this way frequently, I'm made quite aware of the problem in the decoder's design which, with unmaximised audio, would give perfectly good output - but thanks to poor encoding practices [i.e. bitpushing] is rendered effectively-faulty.</p></div>