Broken dependent links aren't really broken - can't be fixed
Solved
If you link a song database entry to another song file (like a re-ripped version at a higher bit rate) the song file is stored in "iTunes media" as per the iTunes prefs.
TuneSpan can then span the file but at the same time it thinks it has lost a dependency and prompts me to use iTunes to re-link - even though iTunes *and* TuneSpan both know the location of the song file. I can even click on the red warning heptagon to play the song!
How can I remove this unnecessary dependency or reset the TuneSpan database so I don't get these errors?
The same problem
I am not sure I fully understand your situation...
Are these tracks that were dependently spanned with a previous version of TuneSpan or are you spanning them for the first time with the latest version of TuneSpan that was just released (version 0.9.5 beta)?
If you are getting the red warning sign that means the span failed, which means that the file is still in its original location and TuneSpan did not update the location in iTunes, so the track will still be playable. A dependently spanned track is indicated by a blue rounded square and should no longer happen in 0.9.5 beta as the spanning process is all new. The only time a track will not be playable when using TuneSpan is if the tracks file is on an external drive that is not mounted (plugged in).
It sounds like you are saying there are some specific tracks that TuneSpan is not able to span. But again, it will help me to understand if these are tracks you are spanning for the first time, or some other situation.
It may help me to get some screenshots of what you are seeing in TuneSpan. If you do not want to post them here, feel free to email me directly at pico (at) randomapplications.com
I am not sure I fully understand your situation...
Are these tracks that were dependently spanned with a previous version of TuneSpan or are you spanning them for the first time with the latest version of TuneSpan that was just released (version 0.9.5 beta)?
If you are getting the red warning sign that means the span failed, which means that the file is still in its original location and TuneSpan did not update the location in iTunes, so the track will still be playable. A dependently spanned track is indicated by a blue rounded square and should no longer happen in 0.9.5 beta as the spanning process is all new. The only time a track will not be playable when using TuneSpan is if the tracks file is on an external drive that is not mounted (plugged in).
It sounds like you are saying there are some specific tracks that TuneSpan is not able to span. But again, it will help me to understand if these are tracks you are spanning for the first time, or some other situation.
It may help me to get some screenshots of what you are seeing in TuneSpan. If you do not want to post them here, feel free to email me directly at pico (at) randomapplications.com
Hi Pico
I'll try and explain here but my workflow is probably a bit unusual and we may have to go to email.
1. An album that was previously partly dependently spanned was converted as part of the upgrade. Therefore some tracks were still in place inside the iTunes Media directory and some had been spanned using the new method. No errors and iTunes helper hadn't been seen since the upgrade.
2. To upgrade those tracks to ALAC I re-rip the original CD. Because I have re-tagged the tracks in this case the automatic "replace" function doesn't work and I have to re-rip the compilation, then delete the original files and then link the iTunes database entry to the new files. (When you get the exclamation mark in the circle you get the option to find the "original" - in my case I find the ALAC version).
3. iTunes is set to consolidate and therefore moves the file to an album directory inside the artist directory inside iTunes Media - even if the original file had been spanned. So TuneSpan thinks the file is spanned, iTunes thinks it is local.
4. To try and get rid of the error messages (for some reason TuneSpan now thinks that these files were dependently spanned) I re-span, TuneSpan moves the new file (TuneSpan shows it as spanned) but still has the error record for the old. And doesn't delete the spanned file and iTunes points at that non-spanned version.
I appreciate that this is complicated and that I may not have explained myself very well.
DS
Hi Pico
I'll try and explain here but my workflow is probably a bit unusual and we may have to go to email.
1. An album that was previously partly dependently spanned was converted as part of the upgrade. Therefore some tracks were still in place inside the iTunes Media directory and some had been spanned using the new method. No errors and iTunes helper hadn't been seen since the upgrade.
2. To upgrade those tracks to ALAC I re-rip the original CD. Because I have re-tagged the tracks in this case the automatic "replace" function doesn't work and I have to re-rip the compilation, then delete the original files and then link the iTunes database entry to the new files. (When you get the exclamation mark in the circle you get the option to find the "original" - in my case I find the ALAC version).
3. iTunes is set to consolidate and therefore moves the file to an album directory inside the artist directory inside iTunes Media - even if the original file had been spanned. So TuneSpan thinks the file is spanned, iTunes thinks it is local.
4. To try and get rid of the error messages (for some reason TuneSpan now thinks that these files were dependently spanned) I re-span, TuneSpan moves the new file (TuneSpan shows it as spanned) but still has the error record for the old. And doesn't delete the spanned file and iTunes points at that non-spanned version.
I appreciate that this is complicated and that I may not have explained myself very well.
DS
This is an interesting situation, something I want to try to replicate on my system. But I may not have time to do this right away.
In the mean time, would you mind posting a screenshot of your span results to see exactly what the failed span message says for each track?
This is an interesting situation, something I want to try to replicate on my system. But I may not have time to do this right away.
In the mean time, would you mind posting a screenshot of your span results to see exactly what the failed span message says for each track?
Hi
I'll send a screenshot and more details by email.
Cheers,
DS
Hi
I'll send a screenshot and more details by email.
Cheers,
DS
After Dan and I talked more directly through email, we found the root of this issue had to do with having tracks consolidated through iTunes.
TuneSpan should have been able to handle this situation properly, but Dan had actually encountered an overlooked bug in TuneSpan 0.9.5 beta.
I have just released 0.9.5.1 beta which fixes this issue. TuneSpan can now properly follow any track location changed done by iTunes.
Thanks so much Dan for helping resolve this issue and for making TuneSpan even better!
The latest version of TuneSpan is available on http://tunespan.com or through auto-update.
After Dan and I talked more directly through email, we found the root of this issue had to do with having tracks consolidated through iTunes.
TuneSpan should have been able to handle this situation properly, but Dan had actually encountered an overlooked bug in TuneSpan 0.9.5 beta.
I have just released 0.9.5.1 beta which fixes this issue. TuneSpan can now properly follow any track location changed done by iTunes.
Thanks so much Dan for helping resolve this issue and for making TuneSpan even better!
The latest version of TuneSpan is available on http://tunespan.com or through auto-update.
Marking this issue as solved.
Marking this issue as solved.
Replies have been locked on this page!