User Activity

  • Posted a comment on ticket #9 on x264vfw

    No. The previous information should be enough if they really want to fix a bug in their product. I doubt that the place in the x264vfw code (codec.c:1881) where the memory access violation occurs will be useful to them.

  • Posted a comment on ticket #9 on x264vfw

    Hi. I tried to export using Adobe Media Encoder and it failed. This is Adobe's bug: they send a broken memory pointer (icf) in the ICM_COMPRESS_FRAMES_INFO message and therefore the codec crashes due to memory access violation. Ignoring this message is a bad idea because it signals the frame rate and therefore if you ignore it, all bitrates will be incorrect (as if it is always 25 fps). I also tried exporting to Xvid but it fails for the same reason.

  • Modified a comment on ticket #9 on x264vfw

    What do you mean no longer supported? I tested Adobe Premiere Pro 2023 (23.6) and Adobe Media Encoder 2023 (23.6), both still support x264vfw codec selection when using the AVI output format. Have you installed the full version of the codec, both 32-bit and 64-bit?

  • Posted a comment on ticket #9 on x264vfw

    What do you mean no longer supported? I tested Adobe Premiere Pro 2023 (23.6) and Adobe Media Encoder 2023 (23.6), both still support x264vfw codec selection when using the AVI output format.

  • Posted a comment on discussion Help on x264vfw

    x264vfw even says in its name that it is a VfW (Video for Windows) codec, not DirectShow. in GraphStudioNext it is visible in Video Compressors as ACM/ICM type with category "DMO Video Encoder" and category GUID={33D9A760-90C8-11D0-BD43-00A0C911CE86} make sure that your application has the same bit depth as the installed x264vfw, or install the full version (both 32-bit and 64-bit).

  • Posted a comment on ticket #25 on x264vfw

    If by "dropped" you mean that capture side starts capture in 5 fps instead of 30 fps because your CPU is not fast enough to capture and encode simultaneously than x264vfw can't do anything about this (it encodes every frame it gets but can't encode something it doesn't get because it wasn't captured) and all you can do is to choose faster preset which will need less CPU to encode.

  • Posted a comment on ticket #25 on x264vfw

    Sorry, but I don't under stand what you mean by "The problem is that the video is very dropped" or "the image is sharp but the movements are dropped." . Can you be specific (screenshots or sample) what exactly are your settings and what wrong with output? Preferably also post mediainfo text output for you encoded sample (like this https://pastebin.com/adD6qZRM).

  • Posted a comment on ticket #25 on x264vfw

    Are you sure that x264vfw codec was used at all? "10Gb per minute " sounds like it raw uncompressed video without any codec i.e. x264vfw wasn't used at all. Check your output video in mediainfo and if it is not H.264 video than something is wrong with how you used x264vfw in you app (i.e. it wasn't choosed).

View All

Personal Data

Username:
masternobody
Joined:
2007-12-27 21:22:09

Projects

This is a list of open source software projects that BugMaster is associated with:

  • Project Logo x264vfw   Last Updated:

Personal Tools