Creating the report seems to take just as long as it does to fix, tag, and save items.
Does it mess anything up if I were to hit ‘Cancel’ during the create reports process?
I don’t care too much about the report at the end unless I see errors, which I rarely do.
Or does this mess up the database by canceling during the create report process?
If not, maybe making it an option to create reports would be better? Or does the option already exist and I just missed seeing it?
Thanks
Even when you have matched thousands of songs the report creation should only take a few seconds so Im concerned if yours is taking an inordanate long time, could you give me some actual figures.
But cancelling a report doesn’t mess up the database or anything.
Not sure what it could be but none of my reports are generated in seconds. Usually 30 mins to and hour for about 2000 songs matched. It’s probably system related. Not running the fastest Phenom II x4 b870 with 4GB on WHS 2011. Logs are being written to a 120 SSD system drive.
What usually happens when it starts creating the report is that it immediately completes about 3/4 of the report (on the progress bar) then then last 1/4 trickles slowly across the screen. When done I am presented with the Summary log.
Now on two occasions (including my last one that just finished today (20k songs) it errored out before it completed the report. I had the summary on the right hand side, but the left hand side was trying to reference an html link it could not find. like this
No webpage was found for the web address: file:///C:/Users/Administrator/AppData/Roaming/SongKong/Logs/FixSongsReport_00002_2013-02-20-18-01-18_index.html
Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found.
Also ‘almost’ every creation report I always get this:
Found xxx songs, xxxx have been checked before cancellation. And it’s like just a few songs shy of finishing though I think it does.
One the prior occasion it just completely hosed up and the DB was no longer accessible (maybe corrupt) and I just deleted the DB and started over.
I still have logs if you need them.
Could you email support@jthink.net your support files, then I can see what part of the reports are being created and what parts are missing
I have similar issues with the non-completion of the report, overnight. It needs to be optional.
W7ULTx64-4gbRAM/2.66DuoCPU
It is optional in that you can cancel it no problem, I see no reason to make it optional whether or not to create the report, you might not think you need the report until later on.
The issue is why is the report not being created in a timely manner, there were alot of improvements put into SongKong 1.3 to reduce the time it takes to create a report.
Thankyou for the logs
So I found an OutOfMemoryException that occurred when reading a jpeg file for the purposes of report creation. What I’m unclear about is whether SongKong just happened to run out of memory at this point because it is using too much memory to create reports, or because something in this jpeg caused SongKong to use massive amount of memory to read this file, but at least I have a sensible line of investigation
I’ve raised http://jthink.net:8081/browse/SONGKONG-228 to track this.
This exception which should be displayed to user (but isn’t) is preventing creation of the rest of the report including the index page which is created last which is the reason why you get the error about the missing webpage.
Report creation is much quicker in SongKong 1.4.0 released today, hopefully you should no longer have issues with report creation, please let me know.
[quote=nickeaston]I have similar issues with the non-completion of the report, overnight. It needs to be optional.
W7ULTx64-4gbRAM/2.66DuoCPU
[/quote]
Same old same old regarding report generation–but not an issue for me. Now using a different clean (W8) platform and processing files over my LAN, now 10% thru 330,000 tunes.
I notice that in the beginning I got no Discogs hits but lately now a significant number.
==================
Clarification: My reports result promptly upon completion; the Progress/Creating Report timeline popup never finishes…