Beta 13 has really been released

Okay guys, the beta has been released for real this time...
http://www.empeg.com/cgi-bin/display.cgi?section=downloads&id=4

Wow. Yeah it has...

Edited to account for a wrinkle in the space-time continuum.

/afs/dementia.org/distributions/empeg

For those of you with AFS clients.

Yeah baby! This is great!

But after I'll install it, Hijack will be gone of course....

Hey, I wonder....can I just run the latest HiJack on it, or should I wait until Mark releases a "beta-13 certified" version of HiJack ?

Mine's running developer 2.0b13 and hijack v281, so I guess so.

Remember that Mark's been running Beta12 for a long time with the rest of the alpha team. And this release is not very much different from Beta12.

I just grabbed a copy of trevors version of hijack here. It beta 13 ready, v281 and it has FAT support thrown in for free!

Did Anyone notice this little comment in the Release Notes:
Not that anyone reads these things right before installing the software right?

In reply to:

---

The player now supports a partitioning scheme for the fids directory, which
should improve performance when rebuilding the database. The partitioning
works by e.g. FID 34da0 is placed in (e.g.) /driveN/fids/_00034/da0,
where N is 0 or 1, according to the player's normal rules. Essentially,
the number (in hex) is zero-padded to 8 characters (xxxxxyyy) and saved
as _xxxxx/yyy....

---

... Nothing new there you say, well you're right, but then the notes continue thusly...

In reply to:

---

Note that the player won't create directories of this form. A future version
of the player will.
This code was partially back-ported, in order to
allow v2.0 betas to work correctly on players which had music added by v2.1
player code.

---

The mention of version 2.1 of the Player software is interesting - I gather from that that the player software is being used for products other than EOL'ed Empegs - but the software is indeed able to run on the said EOL'ed empegs.

Hmm, interesting - if nothing else this as yet unknown (by me anyway) project may help keep us in newer software versions for a bit longer when and if the team find time to backport the code, package it up as a 'release' and put it out there.

So perhaps: "one day there will be lemon soaked paper napkins..."

Oops, I meant [apologies to Douglas Adams]

"One day there will be a Empeg replacement- until then, return to your Empegs".

Arse away on a course with only them mobile for net access


arse feck drink

arse

Rob said what the 2.1 player is for here

- Trevor

Fret not dear sir, when beta 11 came out, both of my empegs were away at Davids being fixed. I had to wait nearly a whole week before I got them back. Needless to say I had the upgrade files and emplode downloaded and ready to go.
I've got 13 on now, and honestly can't tell the difference! I've not seen any new features jump out at me yet! You never know 13 could hose your player (which I doubt very much) and you'll be the only one with your FIDs intact! (oo er!!!)

The mention of version 2.1 of the Player software is interesting - I gather from that that the player software is being used for products other than EOL'ed Empegs - but the software is indeed able to run on the said EOL'ed empegs.

Elsewhere on this BBS, Rob mentioned that their low-level playback engine has been undergoing more changes for other projects. A recent rewrite has allowed it to become more modular, in theory allowing just about any new codec to be added at a later date.

This version of the code is not in the released beta 13. It's running on an internal build that they seem to have named "2.1" based on reading the release notes.

My sincerest thanks to the Cambridge guys. I appreciate your efforts to continue to enhance this even after the EOL.
I love you guys *sniffle*.

What? NO crossfading? No OGG Vorbis support? What the hell???
.
.
.
.
.
Hehe i'm sorry ... I couldnt help it ... just kidding guys.

Thanks very much for the new release and all the bugfixes and enhancements.

There's no changes in the kernel of any significance if you've already been running the Hijack kernel The only difference between v2.00b11+v281 and v2.00b13+v281 is a time delay in the flash code is slightly longer in v2.00b13.

I took out the duplicated bugfixes from the Hijack patch and used the official version instead.

- Trevor

There's no changes in the kernel of any significance if you've already been running the Hijack kernel

I have this lingering hope that putting the player in "clock" mode will no longer crash the player software. If not, well, I guess I'll send a bug, since I don't remember if I did last time (but we did discuss it here )

The clock-crash thing is on the internal bug list, but has it been verified as a software bug? Has anyone else experienced it?

Does anyone else leave the clock up all the time?

How does one verify it as a software bug? It happens with more than one piece of hardware, running more than one version of the (stock, no hijack) software. As far as I'm concerned that's all I can do.

As far as I'm concerned that's all I can do.
Well, not really. Maybe I'll get some free time and actually try to debug it. But the point is that should be good enough to exhibit that it's the player app and not something else.

Yeah, but one person on the thread reported that it never happened to one of his boxes, yet it did happen to the other one.

arse feck drink

LOL, I wonder how many other people here understand this reference

Cool. The best MP3-Player ever build got even better.

Aww.. darn. Still has the plain vanilla vuback.raw file.

But the rest is nice.

In reply to:

---

arse feck drink

LOL, I wonder how many other people here understand this reference

---

Considering there is a large british contingent here, I would think quite a few. I am sure there are lots of us others aswell.

I guess the good question would be how many people outside the UK understand this. I just got done watching Season 1 and 2 DVDs a few weeks back, a coworker got me hooked. I'm now going to try and catch Season 3 on BBC America.

I work offshore and most of the crew is British. That is the only reason I have seen any of them. Not really an American network style show.

Yeah, but one person on the thread reported that it never happened to one of his boxes, yet it did happen to the other one.

Still, not a hardware problem with one box. I could and probably should spend some time on it, but I don't have much, and it's one of those things where even if I can guess what's wrong, there's a high probability of "now what"?

Thanks to the lads I've had my fun. (S2:E9)