Tunespan stuck
Known
Hi. I purchased Tunespan last night so that I could separate my music from my movies and TV shows. All of the media was on an external USB drive and I transferred the music back to my user accounts music folder. I am now going on 18 hours and Tunespan still says "Verifying 26,821 Tracks, Quitting iTunes to save updated Library". But it has sitting like that for ten hours and it won't let me quit the program. I have confirmed that the music was transferred to my user folder. Please help.
The same problem
I'm so sorry your experiencing issues.
TuneSpan is stuck waiting for iTunes to quit. But, iTunes hasn't quit for some reason. To kick TuneSpan back into gear you need to manually quit iTunes and TuneSpan should notice the change and finish the span.
It will still need to finish the verification process which could take some time for your nearly 27,000 tracks. So, please be patient after iTunes is quit and TuneSpan continues the process.
But, it shouldn't have taken this long. Did you have any iPhone or iPod or anything plugged in? Sometimes that can stop iTunes from quitting. Also, if you have Wi-Fi sync enabled, I have noticed that can cause iTunes to take longer to quit, but not 18 hours.
Also, if iTunes prompted a warning before quitting when TuneSpan asked it to quit, that would interrupt TuneSpan from quitting iTunes.
So, you should be able to just quit iTunes and it will allow TuneSpan to continue the process.
If that does not kick TuneSpan back into gear, or if iTunes is already not running. Please get back to me.
Sorry again for this issue and thank you for getting in touch, please let me know how it works out.
I'm so sorry your experiencing issues.
TuneSpan is stuck waiting for iTunes to quit. But, iTunes hasn't quit for some reason. To kick TuneSpan back into gear you need to manually quit iTunes and TuneSpan should notice the change and finish the span.
It will still need to finish the verification process which could take some time for your nearly 27,000 tracks. So, please be patient after iTunes is quit and TuneSpan continues the process.
But, it shouldn't have taken this long. Did you have any iPhone or iPod or anything plugged in? Sometimes that can stop iTunes from quitting. Also, if you have Wi-Fi sync enabled, I have noticed that can cause iTunes to take longer to quit, but not 18 hours.
Also, if iTunes prompted a warning before quitting when TuneSpan asked it to quit, that would interrupt TuneSpan from quitting iTunes.
So, you should be able to just quit iTunes and it will allow TuneSpan to continue the process.
If that does not kick TuneSpan back into gear, or if iTunes is already not running. Please get back to me.
Sorry again for this issue and thank you for getting in touch, please let me know how it works out.
I had already quit iTunes manually. And no, my iPhone was not plugged in and I do not have wi-fi sync enabled. I finally forced quit Tunespan, restarted my computer, moved all the newly transferred music to the trash and started over. I had Tunespan find the missing tracks and now I am re-running it. It is more than halfway through. Hopefully this time will do the trick.
I had already quit iTunes manually. And no, my iPhone was not plugged in and I do not have wi-fi sync enabled. I finally forced quit Tunespan, restarted my computer, moved all the newly transferred music to the trash and started over. I had Tunespan find the missing tracks and now I am re-running it. It is more than halfway through. Hopefully this time will do the trick.
Alright. I should have given more instruction in case that were the situation.
Had you tried relaunching iTunes?
And just so you know. TuneSpan has a Crash Recovery Mode built in. Next time (but, hopefully there is not a next time), you do not need to remove the copied files. TuneSpan would detect that they are there and not need to copy them again. If a file was partially copied, TuneSpan will detect that, trash the partial file, and recopy it. Then, it would have finished the verification as normal.
But, what you've done should be fine, it will just take a while to re-copy all those files.
I'm sorry again that this has happened, I would like to try to figure out why TuneSpan didn't detect that iTunes had quit. I am nearly certain that a relaunch and re-quit of iTunes should have triggered TuneSpan.
Alright. I should have given more instruction in case that were the situation.
Had you tried relaunching iTunes?
And just so you know. TuneSpan has a Crash Recovery Mode built in. Next time (but, hopefully there is not a next time), you do not need to remove the copied files. TuneSpan would detect that they are there and not need to copy them again. If a file was partially copied, TuneSpan will detect that, trash the partial file, and recopy it. Then, it would have finished the verification as normal.
But, what you've done should be fine, it will just take a while to re-copy all those files.
I'm sorry again that this has happened, I would like to try to figure out why TuneSpan didn't detect that iTunes had quit. I am nearly certain that a relaunch and re-quit of iTunes should have triggered TuneSpan.
Hey again, just checking back in to see how the span went.
Did it finish properly this time?
Hey again, just checking back in to see how the span went.
Did it finish properly this time?
The span went good the second time. Although there were about 1500 songs that didn't transfer, so I had to go back and redo those songs. Thanks for checking up on it. Your application is amazing and a lifesaver for those of us with large libraries. I will most definitely recommend it.
The span went good the second time. Although there were about 1500 songs that didn't transfer, so I had to go back and redo those songs. Thanks for checking up on it. Your application is amazing and a lifesaver for those of us with large libraries. I will most definitely recommend it.
So glad to hear that! Thanks for getting back to me.
I am still concerned about why this happened, I would like to be sure this does not normally occur. I know there are some situations where there may be an issue, but I would like to to know and if there is more I can do to deal with it within TuneSpan.
But also, did TuneSpan give a reason why the 1500 tracks failed? There should have been some reason for each track listed in the Span Results.
So glad to hear that! Thanks for getting back to me.
I am still concerned about why this happened, I would like to be sure this does not normally occur. I know there are some situations where there may be an issue, but I would like to to know and if there is more I can do to deal with it within TuneSpan.
But also, did TuneSpan give a reason why the 1500 tracks failed? There should have been some reason for each track listed in the Span Results.
Replies have been locked on this page!