2012-03-24foobar2000 v1.1.12 beta 1 has been released.
This is a maintenance update focusing on various bugs documented since the last release.
Fixed Musepack HTTP streaming bugs.
Fixed incorrect MP3 decoder behavior on certain rare files.
Fixed crash reporter dialog crash (duh).
Detection of proxy server settings from Internet Explorer.
Improved crash report generation for infinite recursions / stack overflows.
Fixed multi-channel FLAC encoding (channel mask now gets preserved).
Fixed multi-channel WavPack decoding (channel mask now gets preserved).
Now possible to use HDCD & DTS decoder components with ALAC.
Changed MP3 tag reading behaviors when multiple tags are present.
ID3v2 content now takes priority over APE and then ID3v1.
Various time-consuming operations such as conversion or ReplayGain-scanning now prevent the computer from automatically going to sleep (opt-out).
foobar2000.org (http://www.foobar2000.org/)
btw: is there any reason why someone won't find an official announcement here at the forums?
foobar2000 v1.1.12 beta 2 has been released.
This is a quick fix for apparent regressions in the beta 1.
Detection of proxy server settings from Internet Explorer.
Could you please add support for "Don't use a proxy"?
I'm a web developer and I constantly use debug-proxies (Charles, Fiddler) that change the default Windows proxy.
Without the option my Streams get interrupted while working/debugging. A possible solution could be to use no proxy when you un-check the box but leave the text-field for the address empty.
Thank you very much!
Please fix this:
http://www.hydrogenaudio.org/forums/index....showtopic=93431 (http://www.hydrogenaudio.org/forums/index.php?showtopic=93431)
Please fix this:
http://www.hydrogenaudio.org/forums/index....showtopic=93431 (http://www.hydrogenaudio.org/forums/index.php?showtopic=93431)
+1
foobar2000 v1.1.12 beta 3 has been released.
This update fixes an MP3 decoder regression causing glitches when decoding files that have been split from a longer original file.
beta4 is out.
Tuned ReplayGain scanner for fast multicore CPU / slow HDD scenarios (beta 4).
Fixed Converter misbehavior on files with misplaced “cuesheet” tags (beta 4).
Improved performance when playing MP3 files from internet HTTP sources (beta 4).
Improved compatibility with Apple's HFS driver (beta 4).
thanks Peter.
Hi Peter.
I apologize if this has been discussed elsewhere. If so, please point me towards the relevant thread.
The following item from the 1.1.12 beta 4 changelist caught my attention:
Fixed Converter misbehavior on files with misplaced “cuesheet” tags (beta 4).
Can you please elaborate upon what these 'misplaced' cuesheet tags are?
Also any pointers towards how I can fix these misplaced cuesheet tags will be immensely helpful.
Thanks and regards.
By misplaced cuesheet tags I meant apparent "cueshseet" tags on formats that do not support embedded cuesheets, or on each individual track of an album image that's already partitioned using an embedded cuesheet. Converter would fail to cope with such files before.
2012-05-04foobar2000 v1.1.12
beta 5 has been released.
This update addresses various ID3 tag handling issues and improves ID3 specification compliance:
- ID3v2 handling improvements (beta 5):[blockquote]-Fixed TXXX field name sometimes incorrectly written
-No longer possible to write multiple values per ID3v2.3 frame in various scenarios
-COMM frames with a description now show as “COMMENT <description>”
-Certain broken APIC (cover art) frames are now visible[/blockquote]- APEv2 tag writing: relaxed tracknumber/discnumber field content restrictions (beta 5)
Thanks for changing the handling of COMM-Tags with description!
-No longer possible to write multiple values per ID3v2.3 frame in various scenarios
Not sure how to understand that. Does it mean a fix and now it is possible to write multiple values, or is it now not possible anymore to write them in various scenarios? In the latter case: what exactly was changed?
Thanks for changing the handling of COMM-Tags with description!
-No longer possible to write multiple values per ID3v2.3 frame in various scenarios
Not sure how to understand that. Does it mean a fix and now it is possible to write multiple values, or is it now not possible anymore to write them in various scenarios? In the latter case: what exactly was changed?
There is no apparent specification-compliant way of including multiple values of most fields in ID3v2.3. We changed from storing multiple values per frame (against the 2.3 spec) to storing multiple frames (still against the spec but better odds of other software reading it).
Ah ok, i guess on tag rewrite frames with multiple values will be changed to new format?
2012-05-11foobar2000 v1.1.12
beta 6 has been released, including further incremental fixes
Improved ID3v2.3 specification compliance for TXXX and TCON (genre) frames (beta 6)
Fixed Converter having trouble locating oggenc.exe (beta 6)
complete changelog (http://www.foobar2000.org/changelog)