Problem With jEmplode and Soup Views

OK ... Next weekend (not this weekend, the next one), I'm going to make soups work properly. The Empeg mini-meet sparked my interest again

Any new updates on the status of the fix?

Thanks,
JeffreyB

This weekend came and went...

Any news???

Thanks,
JeffreyB

Sorry, but Next weekend is still a weekend away

Mike had mentioned that he was going to try to get to this last weekend. Did something come up? Was this put on the back burner?

Any info is appreciated...

JeffreyB

Is there a working version of JEmplode ?

The current version corrupts my databases anytime I try to use it.. (appears to lose a bit from some playlist fids, eg. saves a playlist containing a fid value of 0x6bf0 instead of the correct 0x6ac0). Ugh. Ugly.

Is there a version that works without corrupting things?

Thanks

I've been having the same corruption problems w/ jemplode 69.000001 as well. Problems started around versions 66-67. I'm no expert on the workings of this app. However, if I force myself to close and re-load jemplode b/w every sync, database corruptions have disappeared. I even do this for small stuff, like mods to config.ini. It's a pain, but it works.

I've become addicted to the soup playlists and have developed some similar procedures for making sure that they (and my personal playlists) don't get hosed by jemplode.

Assuming only regular playlists and no soups:
1. Enable Soup updating in jemplode. Add soups and sync. Close and re-start jemplode.
2. Disable soup updating. Check all personal and soup playlists look good. Enjoy soups!

As music tracks accumulate on my PC in the future, I batch them together, add to personal playlists and erase/rebuild soups. Soup updating of existing soup playlists has trashed by database many times in the past, so enabling/disabling of soup updating and erasing/rebuilding of soup playlists has been the only way to keep jemplode from destroying the db.

On next music upload:
1. Add tracks to personal playlists, keeping soup updating disabled. Sync player. Enable soup updating. Close and re-start jemplode.
2. Erase soups and sync. Close and re-start jemplode.
3. Rebuild soups from stratch. Sync player. Disable soup updating. Close and re-start jemplode. Enjoy more soups!

How time consuming! Hopefully, the multiple sync in one session and soup updating will get fixed down the road.

Does Mike even check these boards anymore??

JeffreyB

Basically the day after I posted that I was going to work on it that weekend, I got slammed with a new project at work. I'm still on it until August 15th (assuming it launches successfully), so I don't think I'll be able to work on anything until at least then. Sorry guys -- I know it sucks that I just disappeared from existence and left you hanging. If people can find whatever the last stable builds were, I can at least upload them to the site so everyone can grab them.

OK. I'm setting a closer goal to see if it will be harder to have cancelled ... I have an OS X users' group meeting tonight, so I can't tonight -- but tomorrow evening I'm going to see if I can reproduce these problems and figure out wtf is going on.

edit: It's scheduled on my iCal now -- I can't dodge my iCal

Thanks Mike!

Glad to see you back on here... I understand the real job is priority #1. We really appreciate the time and effort you put in here.

JeffreyB

... I DID start working on it It's going to take some time to find the exact test case that is causing problems though. But I'm working on it.

Here is how I could always cause this.

Add two albums
Sync
Add another album
Set the sorting to be in the correct order for three albums
Sync


Once this is done it always kills the playlists to have each of the alums at the top most level.

Genre -> Artist -> Album -> Songs