small but urgent 2.0 wish

Hi.

This is related to my post and the subsequent thread in the programmer section:

I would really appreciate if emplode would allow the upload of a specific file type (let's say ".addon" files) to the empeg that are automatically stored in a special, FID-only "playlist". That "playlist" should be completely ignored by the player itself, other than during sync/up-/download using emptool/emplode.

Currently, addons would have to be named ".MP3", added to some playlist, uploaded to the empeg, then manually moved away from the .../fids directory...
What I propose is to

1. let emplode upload ".addon" files to a special addon-pseudo-playlist
2. let the player ignore this playlist when building its binary music database
3. allow custom init/installer scripts to remove those files from that special playlist after installation, without invalidating the music database that was built during sync.

This should be pretty easy to implement, and would help us 3rd party developers a lot when it comes to installation and update of custom software. The special playlist wouldn't even be necessary if the player would simply ignore the .addon files after upload, for example by assigning *2 fids to them.

cu,
sven

proud MkII owner (12GB blue/green/smoked, was #080000113 is #090001010)

I would really appreciate if emplode would allow the upload of a specific file type (let's say ".addon" files)

To generalize this a bit, emplode can allow the user to specify a list of additional extentions allowed for upload. This will be useful for addon files, the file taxi app, and something else I have in mind that I'm not letting out yet.

Borislav

Hi Borislav.

Well, I think adding the capability to upload one additional file type is much easier than to allow the upload of many, user defined types. Though I think this would be nice, I guess that it would certainly be a post 2.0 feature.
Also, this is going in the direction of a defined interface for 3rd party software anyway, and the guys@empeg promised such a thing long time ago (without any specific time line given though). I really hoped that a plugin-API for both emplode and the player would come up with 2.0, and I'm still hoping this will come up in the not too far future.

cu,
sven

proud MkII owner (12GB blue/green/smoked, was #080000113 is #090001010)

Essentially, v2.0 is ready. We need to forward-port the tuner stuff from v1.03, and chase down a bunch of bugs, but the plan is to knock this out as soon as possible -- you guys have been kept waiting for long enough.

Hence, it's in feature-freeze. Anything suggested here will be considered for inclusion, but if the implementation is non-trivial, it'll probably get bumped to v3.0.


Roger - not necessarily speaking for empeg

God no! What do you mean v3.0!!! don't go there, all versions of '3' have flopped. except maybe windows 3 but that was strictly 3.1 which really took off.

Run for the hills. don't do the v3.0 thing!!

10 9 8 7 6 5 4 3 2 1


sorry, i've calmed down now

Good to hear that it is more on the way.


Murray 06000047
Just increasing my post count

In fact, between 2.0 and 3.0 we will be releasing periodic public betas (just like the good old days) so if 3.0 dies horribly you can at least go back to 3.0-Beta87C

Rob

periodic public betas

Jipeee! Then I can really 'use' my empeg, instead of.... uh... only listening to MP3s

Edwin de Vaan
mk2 rev.7 # 080000263 (queue 1232) 6+20Gb blue/red