Privacy policy. DirectShow provides a set of default filters in Windows. These filters support many data formats while providing a high degree of hardware independence. An application can also register and install custom filters on the target system. If a filter appears in GraphEdit but is not documented in this reference section, it means the filter has either been installed by a third party or is used internally by some other Microsoft technology.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. Audio Renderer WaveOut. However, I am still confused. However, now that I've installed the mentioned filter package it can play.
At the same time. On the other hand, Windows 10 out of the box so to speak can both play and rip to. Why would I need to add this kind of filter package to Windows 10 which seems to fully support. Are these the same files or same file type at least you tried yesterday when the initial error occurred?
Are you having problems with more than just M4A files? Have you tried installing any one of these? The Orban. Unfortunately Free-Codecs. I take it you mean Free-Codecs. When you talk about referenced package, do you mean the one referenced in the guide or the one you linked to in your first post? This is not a link you will find in the guide on what DirectShow filters to install for M4A file support. It may work equally well, perhaps even better, that I don't know.
Have you tried installing any one of these filters on your Windows 10 computer to see if it will make or break ImgBurn? It's understandable that it doesn't specifically say it's made to work with Windows I'm pretty sure that ImgBurn itself was never designed with Windows 10 in mind, yet by some software magic it's still alive and kicking. I think most users will only use it these days to archive their optical disc collection, not to burn new optical discs, and even less so to author Audio CD discs with it.
Any source on this? In what context? Then why is it throwing the same type of error you see in Windows 7? Mere presence of M4A file format support you see in Windows 10 is not a guarantee that you will not need DirectShow filters to enable MP4 encoding and decoding in a given software application. The term "support" goes deeper than that. Things have to be put in a context, because everything is relative. You may be able to play MP4 files on a Windows 10 computer without any additional software, but that may only be possible if you use the default media player that ships with Windows If you try using a different media player, especially an older one, let's say Then you may not be so lucky.
I'm pretty sure Winamp still installs on Windows 10 and plays what it was designed to play, but M4A files are not on the list of things it will play.
Unless of course someone comes along and hacks it to play things it's not supposed to. A similar thing has happened with Windows Media Player, per your description. I would call that a "beneficial bug". It's not supposed to let you play things it was not designed to play. But if it works, it works, be happy for what does work and not sad for what doesn't. For it to fully support M4A in all the ways you expect it would need to be reprogrammed. I know nothing about the implementation details of neither Windows Media Player nor the new "Groove Music" media player, but if I have to guess I would say that Microsoft has switched to using Media Foundation rather than DirectShow in its new media player.
It's something that ImgBurn isn't programmed to take advantage of. It's relying on the old technology called DirectShow, and there may not be any easy way to bridge the two for backwards compatibility with older software such as ImgBurn. M4a seems to have 2 codecs associated with it.
The one initially referenced was found by doing a web search duckduckgo that specifically asked for Win7. However, it was also from free-codecs. Statement is based on findings lots of information about how to use the API but nothing about the need to add anything to the Windows 10 base software. Yes this explanation fits with my experience as well as a few more trials I've undertaken which I'll post separately from this reply. At this point, I concluded that I did NOT have much of any reason to think that either package might work on either system, which led to the idea of trying the DSP-worx package on Win7.
This failed but with a different error message both screenshot and log file attached. It failed. I suppose even though still perplexed this means I am lucky to have gotten IMGburn to work properly on both Win7 and Win10 prior to free-codecs disappearing even if it means using different Directshow Filter packages on each system.
If free-codecs re-appears I may experiment with the codecs mentioned in the guide. Will post findings if that happens. You are the last person on Earth to have visited and checked out of Free-Codecs. None of those two domain names are responding anymore! Ask Question. Asked 8 years, 7 months ago. Active 8 years, 7 months ago.
Viewed times. Improve this question. Nelrum Nelrum 2 2 silver badges 9 9 bronze badges. Add a comment. Active Oldest Votes. Improve this answer. Roman R. Your belief is unlikely to be correct. You were right. It was a 3rd party demultiplexer which was installed on the test PC without me knowing.
0コメント