I've run into this problem also, though I've been lucky enough to not lose anything from my serious regulars. I did a quick screenshot of the error message:
http://img.photobucket.com/albums/v720/ ... serror.png
It's actually one of three - it pops up for each of the singer's playlists (Tonight, Favorites, History) in quick succession. I'm not sure of the cause, so I've not been able to reproduce it on demand.
Deleted Singer
Re: Deleted Singer
yes i have seen the error message, actually i wrote it 
but i have not been able to reproduce it on demand, that's why i can't fix it 
but i have not been able to reproduce it on demand, that's why i can't fix it Re: Deleted Singer
OK, I'll try to get the library to you when I get home from work. I can wait til Tuesday for office hours and let you see it in action if you can't recreate it.
From he to whom much liquor is given...much singing is expected.
Re: Deleted Singer
k thanks
Re: Deleted Singer
Haven't forgotten, Dave...I'm setting myself a reminder to get this to you when I get home. If need be I'll be available during your office hours tonight.
From he to whom much liquor is given...much singing is expected.
Re: Deleted Singer
my office hours are, umm, canceled this week, but i'm still handling bug reports and email tech support. just send me your library *BEFORE YOU RUN AGAIN*.
-dave
-dave
-
DeusExMachina
- Posts: 1293
- Joined: Sun Apr 20, 2008 9:57 am
- Location: Pittsburgh, PA
- Contact:
Re: Deleted Singer
Dave:
I think this is the bug I was tracking a few months ago. If you recall, we determined that the issue was that somehow kJams assigned the same Singer ID to two singers, and thus refused to open one of the two. The solution I found was to create a new singer, which created a new ID, and then find the singer file for the original singer, that kJams would not open, and open it with an XML editor, and copy over the relevant data, editing the Singer ID where appropriate.
Still not clear why this happens, but that is the temporary fix.
Mark
a.k.a.
DeusExMachina
a.k.a.
physicisgod
a.k.a.
U-Chun
I think this is the bug I was tracking a few months ago. If you recall, we determined that the issue was that somehow kJams assigned the same Singer ID to two singers, and thus refused to open one of the two. The solution I found was to create a new singer, which created a new ID, and then find the singer file for the original singer, that kJams would not open, and open it with an XML editor, and copy over the relevant data, editing the Singer ID where appropriate.
Still not clear why this happens, but that is the temporary fix.
Mark
a.k.a.
DeusExMachina
a.k.a.
physicisgod
a.k.a.
U-Chun
-
Scott Parr
- Posts: 25
- Joined: Wed May 05, 2010 2:03 pm
Re: Deleted Singer
This happens to me often.
Re: Deleted Singer
well, keep me posted 
-
DeusExMachina
- Posts: 1293
- Joined: Sun Apr 20, 2008 9:57 am
- Location: Pittsburgh, PA
- Contact:
Re: Deleted Singer
If you open the .xml files in an XML editor, like Smile, you will find that the playlist IDs are corrupted.
Normally, the Singer, Tonight, Favorites, and History lists have consecutive IDs, assigned at creation.
What appears to be happening is that for some reason, kJams gets confused, and changes one or more of the playlist IDs, such that they are not longer consecutive. If that is the only problem, kJams overwrites the offending list with a blank one, and gives you the dialogue as shown. If one of the playlist IDs conflicts not just with the others for that singer, but with another singer, one or the other singer gets deleted.
I suspect that in some dark corner of the code, kJams is getting its signals crossed, and assigning out the wrong ID.
The solution is manifold.
On the server-side, the subroutine that invokes that dialogue could to be rewritten such that instead of creating a new playlist, the offending Singers folder and all playlists are "quarantined" to another folder, and the user can fix it manually. (Alternately the new singer subroutine can be used, and the old playlists copied into the new singer, with the ID dict entries changed to match those of the newly generated singer.) A similar methodology could be applied to collisions.
On the client side, I have written a kJams launcher script that I posted in the code section of the wiki that saves certain system settings (like exposé state) backs up the "~/Music/kJams/kJams Library/Venues" folder to "~/Music/kJams/kJams Library/~Venues Backup", and then launches kJams safely. You are welcome to d/l and use it.
That said, some changes made in r64 to address some issues that popped up in my console logs may have also lead to the solution to this bug. So it MAY be fixed in versions after r64. I have been hammering it pretty hard with Server, and have not had these problems again. But it is a bit too early to declare victory.
Time will tell.
Normally, the Singer, Tonight, Favorites, and History lists have consecutive IDs, assigned at creation.
What appears to be happening is that for some reason, kJams gets confused, and changes one or more of the playlist IDs, such that they are not longer consecutive. If that is the only problem, kJams overwrites the offending list with a blank one, and gives you the dialogue as shown. If one of the playlist IDs conflicts not just with the others for that singer, but with another singer, one or the other singer gets deleted.
I suspect that in some dark corner of the code, kJams is getting its signals crossed, and assigning out the wrong ID.
The solution is manifold.
On the server-side, the subroutine that invokes that dialogue could to be rewritten such that instead of creating a new playlist, the offending Singers folder and all playlists are "quarantined" to another folder, and the user can fix it manually. (Alternately the new singer subroutine can be used, and the old playlists copied into the new singer, with the ID dict entries changed to match those of the newly generated singer.) A similar methodology could be applied to collisions.
On the client side, I have written a kJams launcher script that I posted in the code section of the wiki that saves certain system settings (like exposé state) backs up the "~/Music/kJams/kJams Library/Venues" folder to "~/Music/kJams/kJams Library/~Venues Backup", and then launches kJams safely. You are welcome to d/l and use it.
That said, some changes made in r64 to address some issues that popped up in my console logs may have also lead to the solution to this bug. So it MAY be fixed in versions after r64. I have been hammering it pretty hard with Server, and have not had these problems again. But it is a bit too early to declare victory.
Time will tell.
Re: Deleted Singer
mailing this to myself, to put in your "special" folder, so when i actually work on this bug, i'll have the reference
-
DeusExMachina
- Posts: 1293
- Joined: Sun Apr 20, 2008 9:57 am
- Location: Pittsburgh, PA
- Contact:
Re: Deleted Singer
Dave:
We've talked about this before, so you may already have it in my special folder!
Anyway, it is nice to be reminded that I as not suffering this alone!
Remember though, that latest fix we worked on last week (remember my 550MB log file?!?) MAY have addressed this.
Fingers crossed.
We've talked about this before, so you may already have it in my special folder!
Anyway, it is nice to be reminded that I as not suffering this alone!
Remember though, that latest fix we worked on last week (remember my 550MB log file?!?) MAY have addressed this.
Fingers crossed.
Re: Deleted Singer
you know... my brain... i need to tie a ribbon on my finger to remember something. then a ribbon on the other finger to remember the ribbon on the first finger
