I'm running 2.00 developer, jEmplode 69.000000000000000001, and Hijack 4.24. For months now I've had a problem with Soups stored on the Empeg. I've got soups with sorting like, artists a-z/abums, and all songs a-z, etc... It seems that when making the views and storing them on the Empeg, jEmplode is not picking up all of the songs. All tags are good, I'm just missing 100's of songs in these views. Any ideas? I thought I read on here the storing soups on the Empeg section of jEmplode might be broken. Anyone else having similar problems?

Thanks,

JeffreyB

From the reports, the newer jEmplodes definitely seem to have some problems w/ soup views, which is not terribly surprising given that they went through a major rewrite in those last couple versions. Unfortunately I have zero freetime these days, so I just don't have time to fix the problems

Am I better off going back to some previous version?? If so, are they still available?

Thanks,
Jeff

I tried going back to v44 (a very solid version), a few months ago, and then realised it was totally incompatible with modern soups, and RIDs etc. so gave up on the idea. Maybe if I recreated the database I'd be OK...

Mike, is the code in such a state it could be made available for some open development? I'm not offering to help as yet, but I'm sure a lot jEmplode fans would like to help out with the bug fixing if at all possible.

Also, to add to the jEmplode bug list... I have a really weird problem right now where whenever I add a new playlist to the database the synchronisation appears to work OK. But then upon reloading the database (or looking on the empeg) I discover a random soup playlist has been added as a child of my new playlist! I can't delete the soup directly as there is no option to delete that playlist without completely deleting the music it contains. Deleting the parent gives me the option to delete the playlist without deleting completely, but then on the next synchronisation the soup playlist mysteriously reappears at some new totally random location! It's bizarre. It's like a virus soup playlist!

Ross

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

Quote:
"It's very good jam," said the Queen.
"Well, I don't want any to-day, at any rate."
"You couldn't have it if you did want it," the Queen said. "The rule is jam tomorrow and jam yesterday but never jam to-day."
"It must come sometimes to "jam to-day,""Alice objected.
"No it can't," said the Queen. "It's jam every other day; to-day isn't any other day, you know."
"I don't understand you," said Alice. "It's dreadfully confusing."

-Through the Looking Glass, Lewis Carroll

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

To clarify, you're setting sort order on a soup playlist? I think that's a recipe for disaster ... It's been a while now since I've used any of this, but isn't there a sort order setting in the soup creation dialog? Sort order is key to jEmplode being able to find tunes in the soup, so if you set sort order on it, I suspect it's going to freak out adding and removing things it's not supposed to if you change it after the fact with set sort order ...... Just a guess though -- like I said, it's been a while.

I am not using soups.

Oh that's VERY interesting ... That should greatly simplify things for me.

Wow. That sh*t was just plain broken. I have no idea how my test cases missed this bug!

Hey Mark -- I haven't looked into the problem you're seeing yet, but I would be curious to have you try the latest one just in case it was related. What are the circumstances that the corrupted FID occurs for you?

Sorry I missed the second question. I'm not using Soups either. Thanks for version 70, though. Cool.

Arrgh.. "Operation failure exceeded maximum retry count", and the empeg still says 'Synchronizing' on it.
..after rebooting and rebuilding the database, it said "There is no file with FID 2 on this device."

What I did:
Added four Yngwie Malmsteen albums in FLAC format to a new playlist under 'Metal'. Sorted them to taste, hit 'Set Playlist Order', and then synchronized.

Is this reproducible? That sounds like something completely different than the previous problems -- Not sure exactly what offhand, but it sounds like there was some root failure that's not being shown that resulted in the sync aborting.