NPAPI plugins are deprecated and not supported in Chrome since September 2015. This method requires some coding other than web-coding, meaning C/C++. Nethertheless, I'm mentioning this possibility here for completenees. Though I made NPAPI plugins, I never used this API, and I'm not sure it will work as expected. The plugin can be wrapped into a Chrome extension. I can imagine that you create a plugin registered for, again, audio/mpeg MIME-type, and receives the data via NPP_NewStream, NPP_WriteReady and NPP_Write methods. You may have a look at NPAPI plugins in general, and their streaming APIs in particular. If you need to further process such files, it can be a challenge to monitor them in the folder, and run additional analysis in a separate program. (I made such an extension, but I do not have requirements for further processing). It will land in default downloads folder and may have unfriendly name. Having the url you may force appropriate media download as a file.
#Chrome audio capture how to#
Just for a quick example of code you make look at the following SO question - How to change response header in Chrome. You can develop a Chrome extension, which intercepts HTTP-requests by means of webRequest API, analyses their headers and extracts media urls (such as containing audio/mpeg MIME-type, for example, in HTTP-headers). If you do not have a specific requirement to build your system on Chrome, you should possibly move to Firefox. They are already known to be used by similar extensions. To look at other browsers, for example Firefox, which provides low-level APIs for connections. You could try 3 ways, neither one does provide 100% guarantee to meet your needs.īefore going into more detailed descriptions, I must note that Chrome extensions do not provide convenient tools for working on per connection level - sufficiently low level, required for stream capturing.
0 kommentar(er)
