You can measure this yourself if you want to.

Just wipe all of the music from your drives, and reboot with Hijack installed. Then surf to http://your.player/proc/meminfo and see how much is left over (MemFree+Buffers+Cached, I think).

This will be different between Mk1 and Mk2, as the software is different. And Mk2a should be exactly the same as Mk2, except 4MB more free.

-ml

In reply to:

---

It's been sort-of on the todo list for a while to separate the player's database (that it uses while running) from the one visible to Emptool/Emplode/JEmpeg.

---

That would be really cool! But I understand why other things are more pressing...

For anyone referring back to this thread, there was a bug in the 48-bit support of v274.. fixed now in newer hijack's (up to v290 today).

cheers

In reply to:

---

It's been sort-of on the todo list for a while to separate the player's database (that it uses while running) from the one visible to Emptool/Emplode/JEmpeg.

---

I will be implementing this in mp3tofid version 2. I will have to, as the database size is getting a lot bigger because of the extra tags I'm putting in (like original tune location).

I'm already able to build the database myself, so it will not be hard to leave out unnecessary tag fields.

Unfortunately I won't be able to release a new version until after I return from a short holiday.

Pim