Simply: I want lit buttons, which means I need to upgrade from 1.03 to 2.0. But since I still can't wrap my mind around the 2.0final menu implementation, I'd like to try out older 2.0betas. Maybe an older one has some features I want (old 1.03 style menus, non-visual-squashing Transient info, stripped down EQ, the old FunnelWeb viz ::sigh::).

So, among the lot of us, could I scrounge the complete set of old 2.0 betas?
Are there any that are fatal to my player, its database, its play counts, or its eq settings?
Are there release notes on the old betas, or should I just deep-search the BBS for the pros and cons of them all?

Thanks mucho! Clearly, I'll do whatever it takes to get HiJack so I can get lit buttons. Or just tweak the menu UI.

No released 2.0 beta had square menus, and if I remember my empeg meet history, 1.1 didn't have square menus either.

I'm also pretty sure all 2.0 betas squashed the visuals for transient, and in earlier builds, it did this to more visuals then 2.0 final.

Besides the fact that all 2.0 betas prior to b13 had bugs that I would not want to wish upon anyone...

At some point, some software simply overlaid the visuals for transient, rather than squashing them. Dunno if this was 1.03, or a v2beta. But I hardly ever used my player until the v2betas existed, so perhaps it was one of them.

Cheers

Here are the release notes (attached) for the earliest v2-beta that I know of. Read'em and weep -- tons of useful features in there that were not in 1.03.

Cheers

I like the squish on transient, but not on line...

shrug.

This is like your third post lamenting the 3.0 UI, so it's obviously something that's really bothering you. If you *really* want to try the 2.0 betas, go ahead.

However, if you're willing to be patient, I am putting finishing touches on software that will quite possibly address some of your concerns. It will (already does) at the very least, allow completely user-defined "non-squishing" transient info modes, and allows you to do some slick things with "full screen" style info modes that still lets you see your visuals. As for menus, I don't plan on the first version being able to replace the player's menus, but that's possible in the future. The way it works now, when you access the player menus, my app hides until you get out of them. But it would be possible to replace them with my own menu that just passes the selected actions on to the player. Much more of a task, though, and would need to be updated every time the player software changes.

As for Funnelweb (which I like the new version of, for what it's worth) and the EQ, I can't do anything about those, and I'm not sure those prayers are going to be answered by the empeg gods either. If those two nits are more valuable to you than the features of 3.0, maybe you're best served sticking with one of the 2.0 betas. I don' t remember offhand which ones had which bugs, but I ran with 2.0b13 for a long time and found it to be the most usable. YMMV.

non-visual-squashing Transient info

v3-alpha-7

Actually, my deal-breaker for 2.0 and above are the two menu system quirks.

Mark: Wow, thanks for showing me the light. I honestly didn't know there were THAT many features on 2.0 over 1.03.

yn0t: Thanks for the link! Oh, I most definately waiting for your software project! If you offered user customizable menus (with the "currently selected is first selected" beauty of 1.03) which fed data to the stock menus, that would be just brilliant.

Nah, I'm not bugged by Funnelweb or EQ or anything; just stating a preference. It's just the menu order and the current selection state (described in link above). Ok, I won't mention it again for 4 more months (my usual incubation period for this topic).

Thanks for the info all!

If you offered user customizable menus (with the "currently selected is first selected" beauty of 1.03) which fed data to the stock menus, that would be just brilliant.

Can't quite pull that kind of magic off, what I may be able to do at some point is create our own menus that pass the commands on to the player's menus. Duplicating all of the player menus would probably be a little too much though, especially deep ones like the playlist menu... But the source will be wide open so enterprising contributors can figure the hard stuff out

With the serial port commands we have.. I would think that replacing the playlist menu would be one of the less difficult things to implement. Not trivial, but not much harder than the web interface that's already in Hijack.

Cheers

Well I was more referring to the part where he said "feeding data to the stock menus." I can certainly imagine replacing the existing menus (and envision doing so someday), but not actually substituting what's displayed in the ones that are already there.

Well, I got the full stash of v2 betas (and every set of release notes since 0.11beta). Thanks for all your help everyone.

And yn0t, I can't wait to see your software.

And apparently ir_translate is much more powerfull than I originally wrote it off to be. Wow, my head's about to explode with all this user interface tweak potential!