..is fixed internally (also affected internal Karma releases you'll be pleased to know - you get the Karma's feartures and the bugs!).

At this stage I'm going to consult with the empeg gurus here and work out what is needed to turn this into a public beta. Apart from database issues I suspect emplode may be a little finickity so don't hold your breath, but it's getting there.

Rob

Make us live with jEmplode!

You da man, Rob!

Awesome!! I wonder if seeing this bug in alpha5 helped at all with the Karma efforts?

Cheers

you get the Karma's feartures and the bugs!

Cool! It's almost like actually having a karma, but not!

I really REALLY need to get one, I think.

Again, Rob, thanks for all your efforts. The upgrades are always much appreciated!

Thank you Rob! You rock!

Top Geezer! I'm always too scared to play with the alphas (as I never have enough time to redo major fsck-ups), but betas are just fine territory to play in.

Thanks a lot for your effort

bye

database issues

F, if I may say so, ITNR.

Peter

Woohoo!!!

F, if I may say so, ITNR

Now, that sounded extremely certain, final and complete! It sounds like that bug was well stomped.

hehe, It is pretty powerful how he seperated the F like that isn't it?

So Paul, you going to take the plunge if this comes out as a beta in the near future? I'm following your lead on this on.

Greetings!

I will load beta one onto the player that goes into the office with me. If it proves stable for standard play, I will install it on all of the others.

Is thinfourth2 back yet though? If so can somebody ship him off again so we can get another release?

I will load beta one onto the player that goes into the office with me. If it proves stable for standard play, I will install it on all of the others.

The big issue with these alphas is binary size / memory use, especially with big databases. (All Karmas have 16Mb, and for only 20Gb of disk.) As soon as it works for you, it ought to work for pretty much everyone.

Peter

Well, I bump into problems every now and then with 2.0. Usually during special case items (fscking drives). My syncs are somewhat of a challenge because of the number of FIDs I have. Emplode 2.0 really hates that, and has stopped trying... But I see no problems at all with day to day use. Sure, I cannot save a down-down-down playlist, but how often do your really want to randomize that much audio?

If anyone in empeg towers would like to have a few 80GB drives to test with, or borrow one of my players for experimental use, please send me a PM or email.

Paul, are you using a Mk2 or a Mk2a? I have an 80GB and a 60GB in the same player and I've never had problems fsck'ing... I only have 3GB free on the player, but I have far fewer tracks than you.

Peter, thanks! (Out of curiousity, how many of the staff have empegs/RioCars?)

If anyone in empeg towers would like to have a few 80GB drives to test with, or borrow one of my players for experimental use, please send me a PM or email

There shouldn't be any need for that. The issues, after all, are all to do with database size, not total amount of audio, so at the worst we'd only need a similar collection of *1 files -- which needn't have genuine *0 files behind them. We could lash that up easily on the 20s and 30s which Empeg Towers' biggest players have.

Peter

On a stuffed 80, I do occasionally - if I do not turn on swap. Emplode does fine with this, based on recent tests.

Rob, it's so good to hear you say this! THANK YOU!

Another little one I noticed on a feature I regularly used:

Down, Down.L to get to the previously selected playlist seems to repeat the previous insert/enqueue/append without actually taking you to the previously selected playlist.

binary size / memory use, especially with big databases.

IANAP, but how much of a performance hit will you incur if you just a compressed database in memory, and have routines in the player to read it natively when needed? i can only think of a longer boot time, longer Down-Down-Down wait time, and a longer search time, which i think all of us will not mind, if it means that it gets around the memory limitations that we're fast approaching.

surely you mean 3.00a10