1342: AVs on attempted Video play (f_video.dll)[#7118]

[Mizery_Made]

I've installed 1342 along with the Codec trial pack. I have attempted to play four video files (of various file types; MKV, MP4 and AVI) and each is met with an AV about the f_video.dll. Unable to get any videos to play, including an AVI that previously played fine in 1333 (without the codec pack).

EDIT: Codec Pack 1.06

[Mizery_Made]

Here's an update on the issue: I uninstalled the codec pack, and then proceeded to reinstall build 1342. I still had the previously mentioned four videos in the Now Playing list and upon opening MM, I attempted to play one of the AVIs (which was the one that previously played find with an "out of the box" build 1333). It failed to play, as it just sat there for a few moments before graying out and moving onto the next video. That one was the MP4 and naturally MM threw a message about not finding the codec, so it moved onto the next video which was the MKV and received the same message. Then it moved onto the second AVI (which is a 720p) and it played. Given that it played, and the other AVI didn't, I got curious as to why and found myself trying to play the first one again... and it played too.

So, figuring the reinstall may have fixed the issue, I installed the codec pack again to try and play the MP4 and MKV files. Thing is... they don't play, nor does the two AVIs. The AV messages about f_video.dll is back!

EDIT 1: Uninstalled codec pack and restarted MM as prompted after uninstall. AV persists after starting it back up after codec pack uninstall.

EDIT 2: Another reinstall (without codec pack) and videos are playing fine again. Seems there is something up with the Codec pack that is damaging MM's ability to play videos (on my system at least)

EDIT 3: Bingo! I think I've narrowed it down to a very specific trigger. Install the Codec pack per user (default). Doing so results in the repeated error about f_video.dll. However, uncheck that option during install (thus installing "globally") and it works fine!

[Mizery_Made]

*Sighs* Well, I thought I had this bug cornered, but it just teleported back to square one on me. Had video working fine with a global install of the codecs earlier (as I reported). Put MM up for a while (closed it, that is) and then brought it up just a few minutes ago to test a different video file... and the AV is back! This is driving me nuts, help... anyone?

[Lowlander]

So far video playback is working for me. I have the latest MM/codec pack as well as the K-Lite codec pack installed.

[Mizery_Made]

Doh! Me again, I believe I may have found the actual trigger for this error. Looks as though if you run MM3 and MM4 simultaneously, then this AV is triggered. I just went in and uninstalled the codec pack (which was installed globally per my previous theory), and then re-installed it locally (per user) so that I could test it against my (already debunked) other theory. MM4 is playing nice with the videos now that I have MM3 closed out.

Lowlander, have you tried video in MM4 with MM3 also open?

[Lowlander]

No, I just have MM4 installed.

[Mizery_Made]

That's alright, Lowlander. I believe I have narrowed it down further. It seems that if you run MM3 before MM4, then this error will be thrown on attempts to play a video. However if you run MM3 after you open up MM4, videos seem to play just fine with both versions running.

[nohitter151]

That's alright, Lowlander. I believe I have narrowed it down further. It seems that if you run MM3 before MM4, then this error will be thrown on attempts to play a video. However if you run MM3 after you open up MM4, videos seem to play just fine with both versions running.

Just ran MM3, then opened MM4 and attempted to play a WMV video -- no AVs or errors. Win 7 64 bit with CCCP installed (not MM codecs).

[Mizery_Made]

I think I want to say about a hundred curse words right now! See that there, over on the floor? Yeah, that's my hair... I pulled it out.

I'm not really sure where to go next in my hunt for this little bugger. On this computer, I can consistently trigger the AV by running MM3 prior to MM4, having it running when MM4 starts (it doesn't matter if MM3 is left running or not, as it being there when MM4 starts seems to corrupt video playback for that MM4 session, even if you close MM3).

Just uninstalled the MM Codec Pack, and the AV still occurs as it did before so there goes that variable. I doubt that CCCP would be of relevance, since this issue occurs for me both with and without K-Lite. That leaves the OS as a possible variable, as it doesn't occur for you on 7, whereas it does for me on Vista. If that isn't the necessary variable, then it's looking like it's something with my system. Hm.

Certainly appreciate you taking the time to give it a test though, nohitter.

[Peke]

No AV here Win7 x64 MM4 and Codec 1.06

[MiPi]

I've reproduced it. Tracked as http://www.ventismedia.com/mantis/view.php?id=7118

[Mizery_Made]

I'm glad someone else was able to reproduce the issue, however your reproduction steps makes me wonder if you really have reproduced the same error I've got. You write: "4) play video file in MM4, for which no codec or splitter is present. E.g. I've tried to play MKV without any Matroska splitter installed." That's not exactly the case here, as playing any video file here will cause the AV. That includes AVIs, MKVs and MP4s, all of which play fine otherwise (suggesting there's a codec or splitter present somewhere on the computer). Even when the codec pack was installed giving MM a "local" codec/splitter(?), it still occurred whenever MM3 was ran before MM4.

[MiPi]

Mizery_Made: the reason could be the same, the wrong dll I mentioned could cause more problems. For sure - could you send us bugreport and add comment with issue# (7118) to it? Thanks.

[Mizery_Made]

Are you referring to sending on the AV that pops up with the bug number in the "what were you doing" section, or are you looking for a log from DebugView?

[MiPi]

Are you referring to sending on the AV that pops up with the bug number in the "what were you doing" section, or are you looking for a log from DebugView?

Both will be useful, thanks.