Deliplayer 2 vs. Foobar
Reply #20 – 2004-11-16 00:01:59
I honestly wonder how anyone can call DeliPlayer a contender for foobar2000 (or even "hot on the heels") and keep a straight face.* Deliplayer2 supports more formats than fb2k - but the formats which are supported by fb2k are usually better implemented in fb2k. [a href="index.php?act=findpost&pid=253656"][{POST_SNAPBACK}][/a] And as far as I can tell pretty much every single format supported by DeliPlayer but not by fb2k is some obscure amiga/module/chiptune format. Still an advantage, but a lot less significant than you make it out to be.* Deliplayer has a much better UI than fb2k - its skinned yet still you can customize it by freely moving ui-elements around and enabling-disabling it - this allows you to create your own ui without being a skin or ui developer.[a href="index.php?act=findpost&pid=253656"][{POST_SNAPBACK}][/a] Well, since none of the skilled developers around here actually need something like that, it might indeed be a long while before anyone becomes bored enough to implement it. Anyway, while DeliPlayer's user interface might have some flexibility in control placement going for it, the usability of the window configuration itself is bad. Not intuitive at all, and resetting individual windows to (skin) defaults is not possible (unless you reset your entire window config). No much-needed "undo" for this either. True, you don't have to be a ui developer to get it right.. just lucky and extremely patient. On the whole the player can't even dream of touching the sheer usability of fb2k's default and columns UIs. No playlist tabs, no easy access to components (like the Components and Context menus in fb2k), no DSP queue, config is a mess, config accessibility is a mess (just how #@%$ many configs do you need?!) Oh yes, unless I really missed something, keyboard accessibility in DeliPlayer is virtually nonexistant.* Deliplayer comes with more visualizations than fb2k[a href="index.php?act=findpost&pid=253656"][{POST_SNAPBACK}][/a] moot. The per-track volume vis for modules is somewhat interesting, gotta give it that much. The rest would be rather trivial and boring to implement, not much more than a finger exercise for aspiring plugin developers. * both players support plugins, but fb2k probably has a more powerful architecture for it. Thus, deliplayer will probably continue to lack exotic plugins[a href="index.php?act=findpost&pid=253656"][{POST_SNAPBACK}][/a] At this point the documented part of DeliPlayer's API is limited to input plugins only , so don't expect to see output/dsp/ui/general purpose plugins for it anytime soon.The thing is that most users don't need these exotic plugins - which could someday lead to deliplayer taking the "poweruser"-crone while fb2k is left with linux-style geeks only.[a href="index.php?act=findpost&pid=253656"][{POST_SNAPBACK}][/a] crone n. An ugly, withered old woman; a hag. I wonder what you're trying to tell us? Anyway, here's a tiny list of plugins you consider "exotic": abx, albumlist, bitcompare, columns, convolve, crossfeed, dbsearch, dynamics, freedb, history, matroska, mpeg4u, oggpreview, playlistgen(_ex), pphsresample, quicktag, rgscan, shuffle, soundtouch, tradersfriend, utils, diskwriter (clienc etc) . None of these can be implemented as DeliPlayer plugins using the current SDK (and keep in mind that this list is very incomplete.) Of course this might change once devs add the necessary interfaces, documentation and example code to DeliPlayer SDK Other random annoyances: * extremely slow adding of files * very buggy Shorten seeking and playback (granted, it's a new input plugin) * and last but not least: shareware