So, I used both a Macbook Pro and a full size PC running Windows XP. This report is neccesarily a little lengthy and possibly even confusing but I’ll try and make this matter as clear and understandable as possible. Not only did I compare Mac to PC but also many different playback applications on either platform as well as a two sound enhancement add-ons for iTunes named Amarra and Pure Music. The above picture looks very cozy but this really was one majorly exhausing test. However, as the latest Winamp is starting to support APEv2 tags I am starting to wonder about its usefulness other than for legacy Winamp versions.Mac compared to PC, two iTunes sound enhancements and a range of DA-converters and USB interfaces This new plug-in, is pretty much "new" in terms of the same basic GUI but a re-written C++ backend, giving more chance to support Unicode and making it easily expandable. It was more an exercise for me to practise GUI programming, and learn a mp3 decoder - but I added ID3v2 support, APEv2 support, a more advanced tag editor etc. Updated in_mad Winamp MAD MP3 input plugin. The improved code, plug-in and it's details can be found in the thread titled It started off as an improvement of the original in_mad project code ( found here) which hadn't been touched since 2001, and lacked some, now basic, functions. This plug-in is an alternative mp3 decoder plug-in for Winamp, using libmad and libid3tag. The input buffer field accepts 5 characters, but only seems to save the first four.Īlso, would it be possible to unlock the file once it's fully buffered (I usually have a buffer large enough for this to always happen straight away) as I'm often cleaning tags on a new batch of MP3s while listening to them and it's a pain having to stop Winamp every time I apply changes. I've not found any bugs elsewhere yet, keep up the good (and very much appreciated) work. It's important to not that under ATF mode Winamp will use the media library info in preference to the plugin, which is why the problem may not have been noticed yet, and why I created these tests to remove the media library from the equation. Winamp should use the tag, but instead displays the filename. ID3v2.4 Only - In case the problem was in the ID3v2.3 support. ID3v2.3 Only - Winamp should use the tag, but instead displays the filename. ID3v1 & ID3v2 - Winamp should (under the plugin defaults) use the ID3v2 tag, but the ID3v1 tag is used instead. ID3v1 Only - Winamp should use the ID3v1 tag, and does. No Tag - Control, Winamp should display the filename, and does. In these files I've set the artist, album, and track title fields to the name of the tag format used in addition the track number on ID3v2 tags is padded with a 0 which the ID3v1 tags won't have. I've created a few test files (15KiB) so this can either be confirmed or I can be told where I'm going wrong. It does not make any difference which order the tags are listed The tags are displayed fine in the info dialog however. The new version of this plugin never uses ID3v2 tags for title formatting, it does not matter whether you're using Advanced or Basic. The playback and EQ backend is mostly the same except ported through to C++ and into a class structure. * Re-designed APE tag support including Unicode * Multi-lingual dialogs (once someone translates!) * Non-Unicode backward compatible for WA2 (not fully tested) * Advanced-style Basic formatting for WA2 * 32 bit output uses full internal 28 bit representation * Re-written/ported to C++ to 'enable' better WA5 compatibility The notable new features/fixes (that I can remember from notes) include, Hi, this is a long awaited (although not fully finished) conversion and improvement of my previous updated in_mad plug-in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |