CoreAVC 2.5 (for Windows) Released


Recommended Posts

MSL3L.png

CoreCodec CoreAVC 2.5 for Windows is a complete solution for playing high quality HD H.264 videos on your Windows based computer. CoreAVC comes (in part) from the creators of the Matroska MKV Container (.mkv), So you know it's gotta be good! CoreAVC fully supports GPU hardware acceleration with NVIDIA CUDA Technology, and works with other compatible NVIDIA Platforms like ION running on Windows XP, Vista, or 7. If you have a slow computer that is having problems with H.264 playback, you can try using it.

CoreAVC is known in the industry as being the standard for playback of high quality H.264 video. The new CoreAVC Decoder allows you to offload video decoding to any accelerated decoder that works with either NVIDIA CUDA or ATI with Microsoft's DirectX Video Acceleration (DXVA) interface for any Windows XP, Vista, or Windows 7 PC.

iK6lu.jpg

CoreCodec CoreAVC features

  • Supports Windows 7
  • 32/64 bit Support
  • DXVA 1/2 Compatible
  • NVIDIA CUDA GPU support
  • ATI GPU support (DXVA)
  • Multicore ready (16 CPU Cores)
  • 8100x8100 Resolution Support
  • Full Interlaced support
  • Uses Directshow for MKV
  • Haali Media Splitter Included

CoreAVC H.264 Video Codec - Version 2.5.0.0 (20110326)

  • ADD: DXVA1 support (with red tray icon)
  • ADD: DXVA2 support (with red tray icon)
  • ADD: new x64 blit asm code (unified with x86)
  • FIX: SPS memory leaks
  • FIX: Properly support SPS resolution changes (soft/cuda decoding)
  • FIX: Bug in YUV->YUV blit code
  • CHG: Unify x86 and x64 CUDA asm code
  • CHG: Unify x86 and x64 AVC asm code, enabling SSE2/SSE3/SSSE3/SSE4 for x64
  • CHG: Increase max supported resolution (approx 8100x8100)
  • CHG: Refactor directshow frontend code
  • CHG: Modify CUDA locking method
  • CHG: Rearrange/enlarge settings dialog
  • OEM: YASM padding bug for OSX target
  • OEM: Android support added to SDK

Haali Media Splitter (20110303)

  • ADD: AC3 in MP4 support
  • ADD: WebM support
  • ADD: More H264 aspect ratio options
  • FIX: Show error code in GDSMux when muxing is aborted
  • FIX: Accept more AAC media types in the muxer
  • FIX: Use correct timescales when processing MP4 edit lists
  • FIX: Scan the folder for more segments only if the file references external segments
  • FIX: Fixed a lot of issues with the mp4 muxer
  • FIX: Better support for VC1 in MPEG Transport Streams
  • FIX: Aspect ratio processing in certain Matroska files
  • FIX: Bug in uninstaller that prevented it from properly unregistering all filters
  • FIX: Unrecognized video track in some transport streams
  • FIX: Occasional excessive disk I/O when paused

H0Acs.png

Notes: CoreAVC is not free. It's a commercial program and you have to buy it to use it. There are no free versions available. If you want to use CoreAVC, you will have to buy it from CoreCodec.

CoreAVC Professional 2.5 (for Windows)

cuda.png

Link to comment
https://www.neowin.net/forum/topic/985432-coreavc-25-for-windows-released/
Share on other sites

Recommended Hardware Configurations for proper CoreAVC? Playback

The CoreAVC? H.264 Video decoder for windows directshow has the following 'recommended' hardware configurations below: Noting that the recommendations listed are measured for full screen video playback and a more powerful system will deliver the best playback experience. But because of how efficient CoreAVC is, you may find that what it takes to perform at these levels can be achieved just as well on a slower PC too.

CoreAVC? for Windows

CPU - 800 MHz or faster Intel Pentium class or equivalent AMD processor

RAM - At least 256MB of RAM

OS - Windows 98, 2000, XP, Vista, 7

480p video at 24 frames per second

CPU - 1.4 GHz or faster Intel Pentium 4 or equivalent AMD processor

RAM - At least 256MB of RAM- 64MB or greater video card

OS - Windows 98, 2000, XP, Vista, 7

720p video at 24-30 frames per second

CPU - 2.2 GHz or faster Intel Pentium 4 or equivalent AMD processor

RAM - At least 512MB of RAM

GPU - 128MB or greater video card

OS - Windows 98, 2000, XP, Vista, 7

1080p video at 24-30 frames per second

CPU - 2.8 GHz or faster Intel Pentium 4 or equivalent AMD processor

RAM - At least 1GB of RAM

GPU - 256MB or greater video card

OS - Windows 98, 2000, XP, Vista, 7

GPU Requirements for NVIDIA CUDA:*

NVIDIA GeForce GTX 260/280/290/295, 9800, 9600, 9500, 8800 GT, 8800 GTS 512, 8700, 8600, 8500, 8400, Tesla S1070/C1060, Quadro FX 3700, Quadro FX 3600M, Quadro FX 1700/FX 570/ NVS 320M/FX 1600M/FX 570M/FX 370/NVS 290/NVS 140M/NVS 135M/FX 360M/NVS 130M and higher.

* You will also need drivers 191.07 or higher from NVIDIA

DivX Plus HD was the fastest h.264 decoder and adds mkv support for windows media player.

Plus its free! (install DivX Plus Codec Pack)

I think Divx still wears the performance h.264 performance crown.

So there is very little reason to use corecodec as far i am concerned.

DivX Plus HD was the fastest h.264 decoder and adds mkv support for windows media player.

Plus its free! (install DivX Plus Codec Pack)

I think Divx still wears the performance h.264 performance crown.

So there is very little reason to use corecodec as far i am concerned.

That's why I'm curious about performance, DivX being free (and quite good) makes CoreAVC a hard sale.

I wish someone would make a comparison between this and the lastest DivX plus. There's only really outdated ones around.

H.264 CPU/DXVA codec comparison

UPDATE 31/3/2011: CoreAVC 2.5.1 (CPU & DXVA results added)

http://forum.doom9.org/showthread.php?t=159486

H.264 CPU/DXVA codec comparison

UPDATE 31/3/2011: CoreAVC 2.5.1 (CPU & DXVA results added)

http://forum.doom9.org/showthread.php?t=159486

Interesting, thanks. So wait, it's faster to use the cpu? or am I missing something?

DivX Plus HD was the fastest h.264 decoder and adds mkv support for windows media player.

Plus its free! (install DivX Plus Codec Pack)

I think Divx still wears the performance h.264 performance crown.

So there is very little reason to use corecodec as far i am concerned.

Better be trolling,

- DivX is really slow compared to CoreAVC.

- DivX is buggy compared to CoreAVC.

- Everything adds MKV support for WMP.

- I would avoid WMP and use MPC:HC for empirically higher quality and more performance friendly Haali Renderer as well as more performance friendly subtitles.

maybe i am mistaken, but what's the point of this software?

free video players like PotPlayer already supports hardware accelerated h264 video playback on my Radeon 5670 fine through dxva.

CPU use with dxva on is around 5percent on my AMD Athlon 3600+ dual core (2.0ghz overclocked to 2.4ghz). 720p/1080p x264 (h264). without it... 1080p gets out of sync and 720p plays fine but CPU use is 30-40percent area.

maybe i am mistaken, but what's the point of this software?

free video players like PotPlayer already supports hardware accelerated h264 video playback on my Radeon 5670 fine through dxva.

CPU use with dxva on is around 5percent on my AMD Athlon 3600+ dual core (2.0ghz overclocked to 2.4ghz). 720p/1080p x264 (h264). without it... 1080p gets out of sync and 720p plays fine but CPU use is 30-40percent area.

Not all renderers support DXVA.

If you want a quality presentation, you will use MadVR which doesn't support DXVA.

With CoreAVC, you can use CUDA with MadVR for fast and great quality video.

Not all renderers support DXVA.

If you want a quality presentation, you will use MadVR which doesn't support DXVA.

With CoreAVC, you can use CUDA with MadVR for fast and great quality video.

Well a standard x264 720p (7GB) file seems to be a negligible difference in image quality with a big CPU hit when using MadVR. (since DXVA is disabled)

i.e. it's not worth losing DXVA for the slight (to negligible) image quality increase.

note: i tested it on PotPlayer with madVR enabled and then it's default mode which uses dxva. (and like i say i can notice it did change the image some but it seemed to mostly introduce jaggies in the image where as standard dxva is more smoother.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!