Also, I think, playlist.fpl - the playlist file, should be kept too. This is especially useful when you have put hundreds of songs to foobar.

A problem about ABX comparator with 0.7beta28
It crashes whenever the playback position reached the last second of the file,says foobar has encountered an error then closes.

clean install,DS output,Win2000

Older version of ABX plugin doesn't have this problem in 0.667

WinNT4 SP5; fb2k v0.7 beta 28
Possible MPC file info minor bug.

Tracy Chapman\Tracy Chapman\10 - Tracy Chapman - If Not Now....mpc
Track ripped from CD in EAC secure mode with mppenc --standard --xlevel
File Info reports 7994326 samples @ 44100Hz
Convertor produces 16-bit PCM WAV (no DSP) of 13595 frames (7993860 samples @ 44100Hz).

The WAV is a multiple of 588 samples (CD frames of 1/75 s), but the MPC's reported length isn't, even though the output audio will be.

I presume the gapless part of Musepack SV7 isn't being taken account of in the reporting of the number of samples. It's not a multiple of 1152 or 576 either, so I'm not sure why it's that number. (I know this technical info is mostly useful for calculating the excellent MP3 gapless header tag fix, but it's still incorrect for MPC)

Edit: This happens to other tracks too, not just this one, but that's where I noticed it first.

Getting exact length from SV7 MPC would be too slow, getting exact number of samples in last frame requires decoding that part and due to slow seeking it's not practical. For length reporting size of last frame is assumed to be 576 samples but apparently rounding errors cause some changes to the value.

There's a problem (or maybe just a behavior) that I've found in both v.6x and the current v.7 betas... I'm using a GameTheaterXP under Win2k, and when I use Kernel Streaming, I use the resampler DSP to upsample from 44.1kHz to 48kHz so I get proper playback.

The problem is that the resampler doesn't appear to work with very low-bitrate streams or files. For example, the 16k and 32k MP3 streams at http://www.radioparadise.com/?content=listen end up being played much too fast if I use KS+resmple; they play back fine if I use DirectSound. Another set of files with this problem can be found here at the Yoko Kanno Project: http://ykp.hindsightproject.com/cdinfo.php...p?cd=standalone

Is this a limitation of the resampler DSP, or is there something I am missing?

If resampler doesn't support some conversion it simply does nothing. The problem you have is a driver bug, it apparently treats mono as stereo. Enabling "Convert mono to stereo" DSP should help your drivers.

I guess this could be considered a FR, but it took me 30 mins to findout what the problem was so please hear me out.
I've stumbled upon a cpl of "scene" releases with cuesheets, where the cuesheet wouldn't open either with 0.667 or 0.7 b27
After much investigation, I foundout the problem.
These lines are faulty :
TRACK 01
INDEX 01 00:00:00

and these are correct:
TRACK 01 AUDIO
INDEX 01 00:00:00

Difference between the 2 is that the correct line has AUDIO after the tracknumber.
I don't think that accepting cuesheets where this is omitted would cause any serious harm? Please let me know if you think I'm wrong (I'm sure you will, hehe)

/pike

I think that it is absolutely normal for Foobar2000 to reject such a cue sheet, it is completely incorrect cue sheet syntaxis!

Each track entry in a cue sheet must specify what kind of information it is supposed to have. The cue sheet you got is not-compliant of the norm and I don't think it was meant to ever open in FB2K (of course, I could be mistaken)

That is not the issue at hand here. I agree that the syntax is not correct.
But since we've already decided to open this .cue file with Foobar, imho it's rather safe to assume it's Audio..

Let's blame the release groups (in this case it's RNS) for not following the standards.

sorry, my IE is acting up. lost my first post and had to make a new one, then... fuck IE...

I think it's always a bad idea to promote improper formats.

I agree completely. But since this cuesheet obviously has passed some sort of control and it's not the first time I encounter it, something out there must support them.
If foobar supported it, it could popup a nasty requester saying something in the lines of "this is an invalid cuesheet".

One other option, perhaps the PP preferred way, would be if foobar could say that the cuesheet is invalid because it misses the AUDIO declaration.

The only other option is that I must edit all cuesheets with this fault.

I like the second idea, because it tells you what part you need to edit on your cue files instead of just not accepting it at all leaving you wondering wtf is wrong

I'm fine with it popping up to tell you what's wrong, but I don't think it should then play the cue sheet. But then, I also don't think foobar should play ogg files with ID3 tags, and I didn't get my way with that, either.

Interesting. The "Convert Mono to Stereo" DSP fixed the problem, although I have to use both it and the Resampler. If I have the "Convert Mono to Stereo" DSP enabled, and I play a stereo source file, will it do anything to screw up the stream? It would be nice to not have to switch my DSP settings back and forth.

It only affects mono streams.

Not sure if this is Windows or foobar...
Playing music.
Close foobar and leave.
Come back and open foobar again.
Start playing music then I notice that I have two foobar icons on the little taskbar box by the clock [lower right, you know what I mean I hope]. The rightmost foobar icon is the recent one. It's active and can be clicked on. When I move the cursor over it it displays the current track playing as it should. When I move the cursor over the left icon it just displays "foobar2000 v0.7 beta 28" and clicking on it does nothing. Ctrl-Alt-Del to open the Close Program dialog box and only one instance of foobar is shown, and it's the active one currently playing. So I am assuming that extra icon will be around until I reboot. Any other way to get rid of it?

WinME, recently installed and updated with all the latest drivers as far as I could find.

Remember something similar happen on my system (XP SP1) a few times. Can't remember what triggered the second icon though and it always vanished all by itself after a few seconds. Also did not notice it influencing anything else on my system. So it never really was that of an issue for me.

As far as I remember this also happened on pre 0.7 releases. Does not seem to happen with other programs on my computer.

"second icon" simply means that last instance crashed rather than exited properly. Check third-party components you have installed, one of them might be preventing proper shutdown.

Regarding other reported bugs:

- crash when searching empty playlist - fixed, thanks

- ABX comparator crash - should be fixed in b29 (not sure which exe Case uploaded, it wasn't fixed in "first" b29, but it's fixed on my side).

- "memory leak" when unable to create DirectSound object on win98se - eat this:
I don't see what could possibly be leaking here. This code is in SDK, you can debug it yourself. Or get a real OS instead of that piece of junk win98se is.

- other DirectSound issues with win9x - I *strongly* recommend that you stay with waveOut if you use win9x OS, those are all OS-side or driver-side issues which blew up after I workedaround "pause glitch". Not sure if I even feel like doing anything about them. (ahem, waveOut should be default on win9x)

Now here's something new:
http://foobar2000.org/foo_ui_std_ex.dll
(no it will not replace default UI in the setup)
Constructive feedback is welcome.

hrm, first time i've tried to use a third party plug and i get an error ..



I have the latest beta 28... can anyone help me please? thanks.

You'll need beta 29. Just out. : )

Bah... Case didn't manage to post new links before ha.org's firewall decided to blackhole us today. See freshly edited links in first post (I hope they work, still checking).

hrm, i got beta 29 now, and i'm still getting the error

I like it.

ok, nevermind ... that is a different error sorry

ah, i rather like this also ... nice looking, although i like the regular better

No Replay Gain Scanner in the "Lite" version anymore?

Have fixed in b29
thx

I like this extended UI quite alot. Still simple and functional like the default one but just looks a touch cleaner and more professional.

Only suggestion I have is probably the ability to change the color of the bars in the Visualisation.

The original is nice but new UI is great!
The button are much smaller and won't wrapping anymore when resize the window.

Anyone consider to make auto resizing for foobar2000?

foobar just crashed theres a first time for everything, have no idea why it crashed.. song ended and loading hte next song it crashed. oh well


the extra gui is pretty slick

One "problem" doubt if its one really... the little vis bars in the bottom left.... if you turn the vol down they get smaller. So when my speakers are turned up real loud and i have foobar at -30db or so u barely see anything in the little window. Turn speakers down and foobar to -5db or so they look pretty.

Dunno why my speakers were turned up so much it was at -30 to have a normal listening level, however it'd make more sense to be indepent of volume level. I guess the vis plugin support just uses the same data send to the wavout or whatever? Seems weird for visuals to be depended on volume level. I dont think any otehr player is like that, or maybe i just never noticed it / used windows kmixer to control volume.

oh yea one other thing that kinda bugs me cause it looks wrong. The buttons and the seek bar arn't centered vertically. All are up too high, at least on my computer. I played with windows display crap .. display-apperance-advanced that crap so its probably centered on teh default size only.

No you're not..
If u read the error descriptions you posted, you will find that they are NOT the same.

*I think it's very good and I like your way of adding things in a clean and functional way.

*I like the fact that the buttons don't wrap (the window can be so small before that is needed, and if they wrap they use alot of space) and that the drop down box makes it easy to see the playback order.

*I you want as many people as possible to use foobar2000 I think this should be the default UI, and that the default formatting string should highlight the track currently playing (don't know if it does that now, but that was confusing before I got into formatting).

*I like the "doubleclick in vis" to enter preferences. The older doubleclick in status bar to find current track, is very good too.

*I'm not sure about the length of the seek bar though. It gets very long in fullscreen and that is a great thing for video, but IMHO not needed for audio. It makes in disappear in a way.

*Maybe add checkboxes for these new components to make it optional to remove some of them. But all on by default.

Btw: Graphical problem at the bottom of the seek bar when resizing to decrease height.

Beta30 uploaded.

Seems like an issue with windows common controls.

Have to agree with upNorth on the length of the seekbar. It becomes kind of inconvinient as soon as th Foobar window gets above a certain size. Maybe you could make it in such a way that it will only resize up to to a certain length.

Am also not sure wether I like the fact that it jumps around as soon as you click the seekbar in front or behind the slider. The slider is quite small and sometimes you simply miss it and the song skips around. Maybe it would be better to include buttons or areas for that in front and behind the seekbar.

Colors for the vis would be really cool. Especially if you could make them user definable gradients ie.: $transition(xxxxxx,yyyyyy)

Otherwise I think it's a really nice and simple extension to the standard interface. Am sure a lot of people will be happy about the fact that foobar finally has a seekbar and the vis is kind of a cute added bonus.

what about volume control in the ex ui..
i like it a lot the only thing i need is a volumebar
or 2 buttons

I happen to use the ability to just click anywhere in the seekbar quite alot. But then it should jump to the spot i clicked, not somewhere else.

I like picmixer's idea of adding formatting options, my favourite part of foobar2000
It would be even better if it worked for the seebar too. A functional version of the visual one so many use in the status bar.

If you add a volume bar, I hope you also add the option to remove it in preferences as already mentioned in my last post. Optional view just like in Media Player Classic's view menu is IMHO a good thing.

I am afraid that most of stupid behaviors of seekbar are simply caused by the way windows common controls work. And I don't feel like implementing custom seekbar right now.

Perfectly understandable. Do you think you caould maybe make the seekbar button a bit wider though? Does not have to be much, two or three times as wide would do the job.

Can't just make the button wider, it will change size of entire seekbar (looks ugly).

I like the extended UI, I think it's clean and more friendly than the standard one. But searching the perfection you could implement the option of add/remove elements to the toolbars, and make them moveable and resizable, so we could set the two toolbars in a "single line" from left to right.

Not bad, but I prefer the original.

P.S. The play, next, and prev buttons seems to be a bit "jagged" on the edges. They might benefit from a bit more anti-aliasing. (That'd probably require alpha shading, though.)

Also, this may have been mentioned before, but all the vis data seems to be concentrated on the left. Seems kind of odd.

Also, if you're going to go the toolbar route, it seems like it might be worthwhile to use a ReBar.

Just noticed that the SDK link in the FAQ is a local link. So it's pointing to a spot on my D drive.

yeah, and if you read all my posts you will see that i figured that out and said never mind, sorry .. thanks

Beta31 posted.