Hi Rdl,
Thanks for the quick responses!
Well I did what you said and it worked like a gem (as usual) even on the files I was having issues with.
However, after further testing I noticed that you can replicate the error 100% of the time if you create a very long string (mixed characters) for the collection name. I can confirm that by shortening the collection name (even for the same files that were causing the errors) when added none of the errors were raised on the decode.
Not sure what dictates the actual length of characters in the collection name to trigger the decode process to hang tho (>256?), but I am 100% certain that the string length in the collection name is the culprit. Depending which folder structure where Altbinz decodes plus the additional long title added may push the path for the decode above the 256 limit?
I noticed that you try and break up the raw header string into meaningful sub strings in the drop down list box when adding files from a search engine and it just so happens that none of the them matched correctly; being lazy I selected the 1st option of the full\raw title which contained a shit load of chars... and hence the errors.
Anyway, thanks very much. Hope this helps others which have been caught out with this issue.