Post
by Pauven » Mon Jan 19, 2026 5:33 pm
Hey Robert,
That was a lot to digest. I appreciate all the screenshots and the detailed write-up. There's quite a bit to discuss here, and you may be mixing up a couple aspects of what's going on, so I'll try to be careful in explaining what I believe has transpired.
First, for a brief moment let's ignore that one CCC error. Sometimes that happens, like a hiccup, but I think CCC has since recovered (mostly...).
My Movies has a lot of gremlins, and this is one of them. There are many updates/data changes you can make into My Movies that fails to mark a record as changed. This is extremely frustrating, and I've reported these issues long ago to Binnerup, but at this point I think it is safe to say fixes will never happen. So, to the outside world (aka CCC via the MM API), The Long Walk has NOT changed, since My Movies doesn't flag a change for Watched Status updates, and in turn CCC does not auto-export it with normal changes.
So, you watched The Long Walk in CMC, which in turn updated CCC, which in turn updated My Movies (as you can see in the MM GUI). But My Movies doesn't update the "Last Changed" date-stamp in response to this change, so when CCC checks for My Movies updates, The Long Walk doesn't make the cut.
Of course, I already know about this limitation, so I've programmed CCC to re-export any titles that it updates via the API, right after the update was performed. Basically, CCC forces My Movies to export the full The Long Walk metadata, so CCC should have the updated data back from My Movies, and this in turn should have made it into CMC.
Now, let's revisit that original CCC error - it's possible that this error also disrupted this re-export of updated data behavior in CCC that I programmed. So, while CCC updated My Movies, it had a 1-shot chance to re-export that record from My Movies, and due to the hiccup, that didn't happen. So now you are seeing this Out of Sync Titles notification. And because even My Movies doesn't seem to realize that there was a notable change, when you run CCC in changes-only auto-update mode, My Movies doesn't list The Long Walk as needing to be re-exported.
This is also one of the reasons I ship CCC with a default configuration that does a full export once a week. Unless you have turned this feature off or changed the schedule, this out of sync condition should fix itself within 7 days (and may have already done so yesterday, the default schedule is a Full Export on Sundays).
Of course, you don't have to wait for the scheduled full export. You can run one manually any time.
Alternatively, and for a much faster fix, you can type the title name into the text box at the top-right of CCC's main screen, then do a Full Export. This is a special feature, it will force the re-export of any titles matching the text (aka "The Long Walk"), but does so in an append mode, so it doesn't clear the CCC DB and rebuild it all from scratch, it simply merges in the data from whatever titles match the text you typed. In this way, it would only take a minute or two to fix this sync issue, versus potentially hours for a normal Full Export. Just be sure to clear out the text box once you're done, you don't want to run CCC in filtering mode all the time.
Hopefully all that made sense. But in your documentation, you included samples of the mymovies.xml and mmTitle.xml files. This is where you may have gotten a little mixed up. mmTitle.xml files are only produced by CME, not CCC. If you're using CCC, you may not have much or any need of CME, so looking at mm*.xml files have zero bearing on CCC or CMC (assuming CMC is in CCC mode).
You also listed the mymovies.xml file, which are created by My Movies itself. Here's where that gremlin strikes again. My Movies fails to flag the watched status as a change requiring export, and so in the API The Long Walk won't show as having any recent changes (affecting CCC, as discussed above). But guess what else uses that same logic? Yes, that's right, My Movies uses that logic to determine when to write new mymovies.xml files. Since My Movies doesn't see the Watched Status as a data change, it also doesn't create a new mymovies.xml file. But CCC and CMC (in CCC mode) do NOT look at these mymovies.xml files, so that doesn't matter one bit to CMC users. There are ways you can force My Movies to regen those files, but there's really no reason to worry about that, CMC never looks at those files even in Legacy mode (only the mmTitle.xml files created by CME, which are nearly identical but more reliable).
But wait, there's more. You also mentioned running in test mode. I can't think of any reason for you to be using test mode. More than anything, test mode is for me. It allows me to check if a change was detected, and simulate the export, but doesn't actually process the changes or flag the change as processed. Test mode allows me to evaluate program behavior repeatedly without forcing me to stage new test scenarios over and over. Running in test mode would prevent updates from My Movies as actually processing down into CCC and ultimately CMC. You really should not be using test mode, and doing so could also explain some of the problems you encountered.
Sorry, I know that was long. Hopefully you find all the answers you need above. Feel free to ask for more help if needed.
-Paul
President, Chameleon Consulting LLC
Author, Chameleon MediaCenter
