MAD (MPEG Audio Decoder) Activity
Brought to you by:
verement
Activity for MAD (MPEG Audio Decoder)
-
thedigitalworld010 modified a comment on discussion General Discussion
When encountering build problems with MadPlay on Windows, here are a few steps you can take to troubleshoot: Check Dependencies: Ensure you have all the necessary dependencies installed on your system. This may include libraries, headers, or other tools required for compiling MadPlay. Check the project documentation or README file for a list of dependencies. Compiler Compatibility: Verify that your compiler is compatible with the version of MadPlay you are trying to build. Some versions of MadPlay...
-
When encountering build problems with MadPlay on Windows, here are a few steps you can take to troubleshoot: Check Dependencies: Ensure you have all the necessary dependencies installed on your system. This may include libraries, headers, or other tools required for compiling MadPlay. Check the project documentation or README file for a list of dependencies. Compiler Compatibility: Verify that your compiler is compatible with the version of MadPlay you are trying to build. Some versions of MadPlay...
-
Martin Guy posted a comment on ticket #16
That's a hard thing to do because decoding the current frame can require data left over from decoding the previous two. libmpg123 manages even sample-accurate seeking very well - maybe you could try that.
-
Wolfgang Stöggl created ticket #16
libid3tag: Fix conflicting types for 'id3_frametype_lookup'
-
Yang Zhang created ticket #15
The gcc option -fforce-mem not supported after version gcc-4.3, add version check in the Makefile
-
MAD (MPEG Audio Decoder) released /OldFiles/mad-0.14.1b.tar.gz
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Ross Burton posted a comment on ticket #39
Also, change AM_INIT_AUTOMAKE to AM_INIT_AUTOMAKE([foreign]), as libid3tag doesn't...
-
František Dvořák posted a comment on ticket #40
Plus there are other obsolete macros and libtool warnings. Attaching a patch.
1