Skip to main content
Topic: foobar2000 v1.1.8 beta (Read 17368 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000 v1.1.8 beta

Reply #26
changelog?


foobar2000 v1.1.8 beta

Reply #28
"Support for iTunes gapless information in MP3 files"

Sounds promising, but can't figure out what this means.  Clarification appreciated.

foobar2000 v1.1.8 beta

Reply #29
iTunes encoded MP3 files contain gapless information in the ID3v2 tags, rather than having a LAME header.

foobar2000 v1.1.8 beta

Reply #30
Beta 6 out, thanks to the approximately 70 people who reported the beta 5 preferences crash.

foobar2000 v1.1.8 beta

Reply #31
Is it possible to have an option to write a string on the genre tag instead of the id3 genre number on MP4 tags?

Certain genres such as Thrash Metal, Heavy Metal, Synth Pop and Winamp id3 genres does not appear on iTunes and Mp3tag, after the tags are being written under foobar2000.
"I never thought I'd see this much candy in one mission!"

foobar2000 v1.1.8 beta

Reply #32
Beta 6 seems to be having problems with auto refreshing the albums list, whether detecting tag changes from an external prog, or doing the edits within FB?
I'm doing some housekeeping with album dates, and get very inconsistent results. Sometimes the change appears instantly, sometimes a few of the edited tracks are updated, sometimes none. No pattern visible, and the edits have been made, even if FB's own properties panel refuses to show them.

foobar2000 v1.1.8 beta

Reply #33
I don't know if it's beta related, since I just noticed it, but images in album art viewer that are 256 grayscale looks dithered, almost like Floyd–Steinberg dithering. But the image appears to look fine (no dithering) in other image viewing software.
I am using foobar 1.1.8 b6 on W7 x64

Does anyone else experience this?

foobar2000 v1.1.8 beta

Reply #34
I use the Media Library's function "Rescan now" once in a blue moon. With beta 6, I notice for the first time that the progress window that popped up in former versions to indicate the rescanning process has gone. The rescan itself works flawlessly.

Have I missed solely its removal? I hope this is the right place for my question.
This is HA. Not the Jerry Springer Show.

foobar2000 v1.1.8 beta

Reply #35
Just downloaded the 1.1.8b6 - maybe it's just me but I notice more CPU usage in latest versions. I downloaded 1.1.8 to replace 1.1.6 in which I saw the problem first.
On an i7 processor @2.8GHz, Win7 the CPU usage is at 2% (listening a standard MP3) and it goes to 5% when the spectrum widget is shown.
Ok, I'm using the 160 bands view... but it was not like that before. Removing the spectrum widget it goes to 2%.
I mean,previous versions were under 1%, also on a 8 years old Centrino 1.6GHz machine.
Maybe some graphics regressions?

foobar2000 v1.1.8 beta

Reply #36
reporting bug found in 1.1.8b6 (I translated and reporting here what someone has found)

The gapless play is not working properly at 1.1.8b6 when
1. the LAME gapless info is written on CBR encoded mp3 file
2. iTunes gapless info is written on VBR encoded mp3 file

Easy way to check #1 is to prepare a wav file, divide into several files and then convert them to mp3 using LAME with CBR.
it should play without gap before 1.1.7, but short silence appears at 1.1.8b6 (or b5 later)

Same result is predicted for the VBR mp3, encoded by iTunes with gapless infomation.

For more detail, (what the original person said;) it looks like the length of the unwanted gap is
one frame of mp3 file (1152 samples) and there's somekind of mistake around skipping headers

Hope the explanation is understandable and will be fixed.

 

foobar2000 v1.1.8 beta

Reply #37
I can confirm the gapless playback problems.

I tested two four-track sets of short gapless test samples: an iTunes 10.2.1.1 "128 kbps VBR" set and a LAME 3.98.4 "-b 192" set.


iTunes VBR MP3: foobar2000 1.1.8b6 output is far from gapless. It is clearly and audibly incorrect. For comparison I tried the latest Winamp. It appears to play the files correctly. Here is how Winamp displays the encoder delay and padding values:

Code: [Select]
Track 1:

COMMENT ITUNSMPB
 00000000 00000210 00000714 000000000004B5DC 00000000 00023679 00000000 00000000 00000000 00000000 00000000 00000000

Payload Size: 149296 bytes
Header found at: 2345 bytes
Enc Delay: 528, Zero Padding: 1812
Length: 7 seconds
MPEG-1 layer 3
169 kbps (VBR), 271 frames
44100 Hz Joint Stereo


Track 2:

COMMENT ITUNSMPB
 00000000 00000210 0000090C 0000000000060E64 00000000 0002F4DF 00000000 00000000 00000000 00000000 00000000 00000000

Payload Size: 199813 bytes
Header found at: 2345 bytes
Enc Delay: 528, Zero Padding: 2316
MPEG-1 layer 3
Length: 9 seconds
176 kbps (VBR), 348 frames
44100 Hz Joint Stereo


Track 3:

COMMENT ITUNSMPB
 00000000 00000210 00000858 0000000000040998 00000000 00022448 00000000 00000000 00000000 00000000 00000000 00000000

Payload Size: 144743 bytes
Header found at: 2347 bytes
Enc Delay: 528, Zero Padding: 2136
MPEG-1 layer 3
Length: 6 seconds
191 kbps (VBR), 233 frames
44100 Hz Joint Stereo


Track 4:

COMMENT ITUNSMPB
 00000000 00000210 00000A50 0000000000056220 00000000 00032A80 00000000 00000000 00000000 00000000 00000000 00000000

Payload Size: 212499 bytes
Header found at: 2346 bytes
Enc Delay: 528, Zero Padding: 2640
MPEG-1 layer 3
Length: 8 seconds
210 kbps (VBR), 310 frames
44100 Hz Joint Stereo

LAME CBR MP3: I converted the files to wav with Foobar2000 1.1.8b6 and 1.1.5 (didn't have 1.17 installed). The decoded file durations are identical, but the output of 1.1.8 b6 is delayed by 1152 samples.


EDIT

I uploaded the samples: http://www.hydrogenaudio.org/forums/index....st&p=768989

foobar2000 v1.1.8 beta

Reply #38
Known, already fixed for the next update.

foobar2000 v1.1.8 beta

Reply #39
I don't know if it's beta related, but %filesize_natural% seems to be broken, it does not display a difference between KB and MB.
Can anyone else confirm this? Just make a column with %filesize_natural% and then click the column and see...

foobar2000 v1.1.8 beta

Reply #40
Is it possible to have an option to write a string on the genre tag instead of the id3 genre number on MP4 tags?

Certain genres such as Thrash Metal, Heavy Metal, Synth Pop and Winamp id3 genres does not appear on iTunes and Mp3tag, after the tags are being written under foobar2000.


I agree with /mnt, it would be a plus and has been asked for years now if I remember well. dBpoweramp does not read these tags too, when they have been written under foobar2000. Foobar2000 has issues writing such genres from cuesheets as well.

Thanks.

foobar2000 v1.1.8 beta

Reply #41
1.1.8 final is out now.

 
SimplePortal 1.0.0 RC1 © 2008-2019