Peter posted that he got the Empeg to hook into RMMAhem! Technically, Mike, I posted that on a private beta forum with all NDAs and stuff. It does kinda work, but there's some genuine engineering to do before it could even figure in a v3 alpha, so it's no good getting people "on the outside" all excited about it.
Note that you will likely be able to do wacky things that don't make sense to the karma (like the UI will let you do hierarchical playlists and the Karma will not). I've not actually tried to see what it does if I do thatI expect they'd work fine in the Playlists menu, but the Organise menu would behave oddly. Also, they'd get deliberately flattened (attached to the root) the next time you connected RMM to it.
Sorry about that -- I have riovolution and beta open together so often I was thinking you posted that on riovolution.No worries, it's an easy thing to do. There's no real need to be revisionist about it -- we'd already announced that we were planning to do this (although, looking back, that seems to have been you too...)
In reply to:that seems to have been you too...
I expect they'd work fine in the Playlists menu, but the Organise menu would behave oddly.Wait. So right now, we have hierarcial playlist capabilities on the Karma?
This is the big thing stopping me so far,Yeah... That and tweak order functions. If those two features ever make it to the Karma, I will probably have to buy one again.
Exception in thread "main" java.lang.NoClassDefFoundError: com/rio/protocol/PearlSynchronizeClient
at org.jempeg.empeg.manager.Main.main(Main.java:107)
I didn't get an error I just get the icon for the player saying loading forever.
In reply to:Did you upgrade to the latest firmware on the Karma?
In reply to:It's worth noting that while you can create a "smart playlist" on the device, it won't continue to update after your first sync
In reply to:Karma support within jEmplode is even more beta
In reply to:I would definitely make sure you have the latest Karma firmware if you're having problems with lockups.
In reply to:I just uploaded a new version of jEmplode to the site that has a workaround for supporting dynamic soups on the Karma.
I'm curious to know how the development team from empeg relates to the current group - is there still a group based in Cambridge? It seems as though some of the development carried over as the company/division/technology was sold - how much carried over? Who is who?Empeg has more or less stayed put while the tides of change washed over the Americans. Rio's firmware development team for the Karma, Cali/Chiba, Nitrus/Eigen, and S series is the Empeg development team. (There was another firmware development team at Rio Tigard in Oregon, who did the Riot and 600/800, but they're not around any more.)
I'm curious to know how the development team from empeg relates to the current group - is there still a group based in Cambridge? It seems as though some of the development carried over as the company/division/technology was sold - how much carried over? Who is who?In addition to what Peter just said, there are some other historical tidbits about the Car player and the team here and here.
In reply to:I'm curious to know how the development team from empeg relates to the current group
In reply to:What have I missed by never scraping together the cash for a car unit?
In reply to:Argh. Dang it, I was hoping that this fell into the "undocumented feature" category. "
In reply to:I'm curious as to what functionality is carried over to the Karma, and what functionality was there for the empeg in the first place
In reply to:Is there documentation beyond the faq?
In reply to:jEmplode seems to have a very different structure from RMM. (I haven't tried RMML - should I?)
In reply to:Can I specify via a soup what stays on my Karma?
In reply to:Is there a rating tag already? Does editing the advanced properties of a song
In reply to:In iTunes I had a playlist of my top rated songs which I hadn't listened to in two weeks, which is really nice for unattended listening.
In reply to:I'm guessing by the end of your post you realized that this is fixed and is now an undocumented feature But then just about everything in jEmplode is undocumented
In reply to:Sorry ... The best docs are searching for topics on the forum. There's never been a jEmplode documentation project, and it would bore me to death, so there probably never will be.
In reply to:I don't know that you should necessarily use RMML if you're happy with RMM, though in some ways it is more similar to jEmplode.
In reply to:The primary difference is that jEmplode/RMML don't maintain a local database of music. It's entire reason for being is managing the music on your player, not on your hard drive.
In reply to:Not really .. Soups aren't sync profiles, rather they are dynamic playlists.
In reply to:Note that soups are entirely done on the client, not on the Karma. So if you stop using jEmplode, they will no longer update ... It's just some magic that is done when you add tunes through jEmplode.
In reply to:I could technically extend my soup fix to support arbitrary additional tags, though without too much pain. I may do that, actually. Same deal though, it would only work in jEmplode, not in RMM (though it would in RMML since they share the same codebase).