There seems to be some sort of conflict between RecCopy and MyStuff. Once decoded by RecCopy, MyStuff deletes the MEI cache for that recording, meaning it's correct title and description is no longer available in MyStuff, not for the decoded copy nor for the original recording. Instead, MyStuff reads the title from the filename, and since MyStuff strips non-English characters during recording, the title can easily become wrong, and with Automove adding a datestamp into the filename things get even more complicated (and MyStuff only reads year and month from the filename, not the date). The description is then read from the header but since MyStuff doesn't support non-TF5800 headers, things get ugly there as well, and in this process as well MyStuff drops non-English characters (while it doesn't if the description is read from a cached MEI file).
Thing is, as far as I've been told the decoded copy retains all properties of the original file right down to the datestamp in the filesystem, and since the original file is also still present, I see no reason why the MEI cache file should be deleted, but nevertheless it is.
Here's what BobD said about the problem:
BobD hat geschrieben:If you do something to change the timestamp of a rec file, and then load MS then MS will delete the mei files that no longer match a rec file. So even if you then reset the datestamp on the rec file, the mei file will no longer be there. Could that be what is happening?
Link to the discussion:
here.
SRP-2410M
...man muss ihn einfach gern haben; bin doch kein Murmeltier... 
SetEdit
