Marc
69 Posts
wrote on 05.06.15 at 22:01last edited by Marc on 07.06.15 at 02:34
Link to this post
Is there any chance to fix it? I do have a backup from last week but I added lots of radios/changes since then.
How it happened: I closed StreamWriter so it saved settings to the database file, but after opening it again it displays the error/message.
Thanks in advance.
Edit: Forgot about the bug report. Here it is http://www.mediafire.com/view/jfey0gl5jnfhwed/streamwriter_bugreport.txt
 
alex
2431 Posts
wrote on 07.06.15 at 02:35
Link to this post
Hi Marc,

can you send me the file "streamwriter_data.dat"? See here where it can be found. Have you been using the current version (at the time of your post) 5.2?
I'm not sure if I can help you restore anything lost, but the mentioned data file might show me where things went wrong.
LG/Best regards, Alex

"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell

D1734FA178BF7D5AE50CB1AD54442494
 
Marc
69 Posts
wrote on 07.06.15 at 16:14
Link to this post
Yes I was using 5.2 version. I sent the file via email. Can you confirm me that you received it?
 
alex
2431 Posts
wrote on 08.06.15 at 17:54
Link to this post
I received your mail, thanks. I hope I find the time to look at it this week.
LG/Best regards, Alex

"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell

D1734FA178BF7D5AE50CB1AD54442494
 
alex
2431 Posts
wrote on 14.06.15 at 07:32
Link to this post
The problem should be fixed now, there was an error when decompressing the data file (it is saved using zlib) - the file was saved correctly.
LG/Best regards, Alex

"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell

D1734FA178BF7D5AE50CB1AD54442494
 
Marc
69 Posts
wrote on 14.06.15 at 21:54
Link to this post
Hi Alex,
could that issue also cause the crash of StreamWrriter having to manually terminate the process.
It's the second time it happens. Maybe a transversal point, there could be a bigger number of database backups, so that for example there isn't a difference of one day or two of the last recovery data.
And maybe a routine for crashed profiles that recreates the ignorelists based on existing tracks.
The other option is to use a configuration not based on ignorelists, the drawnback is that files can't be moved and that if "only save whole songs" is not checked incomplete files of already saved songs are saved.
I apololgize for such a long post, I´m running the latest build so if it was related the two crashes with zlib compression I sould have no more crashes.

Kind Regards,
Marc
 
alex
2431 Posts
wrote on 21.06.15 at 01:19
Link to this post
Hi,

did streamWriter really crash, or did it just not react to user input? If it crashed there should be a file named streamwriter_bugreport.txt on your Desktop. If it seemed "to take forever to do something" (no reaction when clicking the window or items in the window) this is likely because of your profile (I observed it here myself). I won't include any "hacks" to restore broken data - if there is a crash the crash needs to be fixed.
LG/Best regards, Alex

"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell

D1734FA178BF7D5AE50CB1AD54442494