Question... Besides all the new techincal features/advances in v3... Does the interface "look" any different? I'm just curious as to see if it's been changed at all. If it has, could I see some screenshots? Thanks..

No, it does not look any different. In fact, a lot of its code is from an earlier version of the 2.0 tree, back when there were still certain features not yet implemented, and certain bugs not fixed. The main advantages in the 3.0 portions of the code tree are related to the new 3.0 audio engine, the same one that's used on the Karma. Primarily what you get with 3.0 is: crossfade, pitch bend, OGG, and FLAC. Otherwise there are no new improvements in the user interface and in fact there are some features missing and some old bugs cropping up again.

is FLAC functional already? i thought that it wasn't implemented yet.

Please also note that there is no V3 Beta 5. You must be getting confused with V3 Alpha 5.

The main advantages in the 3.0 portions of the code tree are related to the new 3.0 audio engine, the same one that's used on the Karma. Primarily what you get with 3.0 is: crossfade, pitch bend, OGG, and FLAC.

How can I upload FLAC files?

I don't know, I never tried. It's possible I'm wrong about it. I was under the impression that the 3.0 codebase supported FLAC, but I never actually used a FLAC file on either the Karma or the Car player, so maybe I was wrong.

oops... damn, and i'm a software developer!

::slaps myself::

I don't know, I never tried. It's possible I'm wrong about it. I was under the impression that the 3.0 codebase supported FLAC, but I never actually used a FLAC file on either the Karma or the Car player, so maybe I was wrong.

get my hopes up for nothing why don't you oh well maybe some day

Uhm..

Also, isn't is "Alpha3"? and not "5"? At least, that's what my player says when it boots up.. If there IS a '5' out there, I'd like to start using it.

Me.

It's a bit late but Merry Christmas!

It's a bit late but Merry Christmas!

Okay, I feel REAL DUMB now.. I have no clue how I missed that in the first place.

Muhahaha! Mine is an evil laugh!

Sorry. Thanks!
Me.

well, with some inital experimentation, .flac files aren't imported by jemplode. but i wanna see if i encode with OGG encapsulation (i think its similar to the old .wav encapsulation of mp3 files; tho i forgot for what reason that was for). hopefully, it'll work. more updates when i experiment more.

well, with some inital experimentation, .flac files aren't imported by jemplode. but i wanna see if i encode with OGG encapsulation (i think its similar to the old .wav encapsulation of mp3 files; tho i forgot for what reason that was for). hopefully, it'll work. more updates when i experiment more.

Flac encapsulated in Ogg is not currently supported by the car-player (or, for that matter, by Karma). For now it's ".flac" files only.

Peter

is .flac importation enabled in emplode v2.1? also, even if we do get it on the empeg, is v3a3/5 going to play it?

is .flac importation enabled in emplode v2.1? also, even if we do get it on the empeg, is v3a3/5 going to play it?

To answer your questions in strictly reverse order, v3a5 plays flac, v3a3 doesn't, Emplode (I think) can't put them on and you have to use Jemplode. Unless, that is, someone fixed Emplode while I was off over Christmas, which is always possible.

Peter

Gah. Maybe I should try alpha 5 on one of my other players, because it still doesn't work with the database on the player with all the music.

well, jemplode doesn't import flac as of yet either. <peers at our favorite java guru>. just tempted to rename my flacs as ogg, and see what happens.

well, jemplode doesn't import flac as of yet either. <peers at our favorite java guru>. just tempted to rename my flacs as ogg, and see what happens.

The "codec" tag will get set incorrectly, and the vorbis decoder will fail to play it with extreme prejudice.

Peter

if i recall, we can manually set the codec tag in jemplode. what should it be, btw?

if i recall, we can manually set the codec tag in jemplode. what should it be, btw?

"flac" (or "mp3", "wma", "wave", "vorbis").

Peter

There is a new jEmplode at http://www.inzyme.com/rio/empeg ... The installers are still the old versions (they just take forever to upload), but the individual jar files, etc are new.

So the deal is that as long as you use the jar file of jEmplode, it is bundled with Rio Music Manager Lite's jar file which DOES have FLAC support. So it checks to see if you have rmmlite in your classpath and enables FLAC if you do. If anyone happens to know of an open source java flac parser, I will include it and provide source ... In the meantime, if you want to use FLAC, it will have to be binary only for the time being. If anyone's uncomfortable with that, you can use the non-binary version and it just won't get FLAC.

I haven't kept up with all the changes, but they're roughly:

Fast database rebuilds (turn it on in Options)

Tag syncing on duplicates (turn it on in Options)

Commandline full database rebuild ( java -classpath jemplode.jar org.jempeg.empeg.protocol.RebuildDatabase <ipaddress> ) -- This should rebuild an alpha5 db for you.

I haven't kept good notes on this release, but there are a bunch of misc fixes and tons of fixes inherited from Rio Music Manager Lite. There are still quite a few things people have reported, but it's been so long since I did a release, I just wanted to get this out there.

ms

The fast database rebuild works for me (didn't try flac).

But on my v3a5 player (the only one I've tried), after a fast rebuild, the player does not get restarted (should it?).

Cheers

Yeah it should be .. Actually it looks like it's not restarting after any rebuild except a rebuild-on-failure. Whoops.

Seems like it doesn't want to deal well with my "large" database (only 12k songs, actually); On the first try it died, probably out of memory. 46 and 47 are both fine. Should any of the changes cause increased memory usage?

Hm. Running it again shows it's only using 10% of the system memory, but panning in the top level of "Playlists" is taking 90% of the CPU. Curious.

Not sure what would have changed ... can you run it from a console and hit Ctrl-Break and send me the output?

I guess I need to figure out what key is "break" on a Mac

Well, just running in an xterm, just letting it open the database and doing nothing else, I see:

Unknown fid type for fid 272 titled ""
java.lang.NullPointerException
at com.inzyme.container.ContainerSortableContainer.getSize(ContainerSortableContainer.java:33)
at com.inzyme.sort.ContainerSortUtils.linearSearch(ContainerSortUtils.java:172)
at com.inzyme.container.ContainerUtils.getChildContainer(ContainerUtils.java:92)
at org.jempeg.nodestore.soup.AbstractTagSoupUpdater.getContainer(AbstractTagSoupUpdater.java:87)
at org.jempeg.nodestore.soup.AbstractTagSoupUpdater.getContainer(AbstractTagSoupUpdater.java:89)
at org.jempeg.nodestore.soup.AbstractTagSoupUpdater.initialize(AbstractTagSoupUpdater.java:127)
at org.jempeg.nodestore.soup.AbstractTagSoupUpdater.initialize(AbstractTagSoupUpdater.java:111)
at org.jempeg.nodestore.soup.SoupUtils$SoupInitializeRunnable.run(SoupUtils.java:324)
at java.lang.Thread.run(Thread.java:554)
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError

The right answer is that I should install eclipse again (the previous laptop had it and I didn't bring it with me to the Mac) but at the moment I'm taxiing files and so my disk is ~full. Blah.

Are you running the jemplode jar directly? if so, try running it:
java -Xmx128M -jar jemplode.jar

If you're running the app bundle, then I need to look, but in one of the properties files you should be able to specify the max memory that can be used by the VM ... Jack that up if you find it.

By default it will only get 64M of RAM max, which maybe (obviously) is not enough to handle a db of that size ... Surprising though. Do you have a lot of soups? Soups eat memory, I think (and processor at least initially)

ms