2nd on the "expensive" option of iZotrope. As we continue to be forced into doing things that go against best practices (like trying to record good audio in a space that isn't) these tools become necessary. Gotta pass it along to the client, or have them accept lower quality audio.
Didn't say it absolutely wouldn't work, I am saying that depending on the playout house, embedding the data in a QT file and washing hands might not be the QnD answer. Trust me, I spent a lot of time trying to get a workflow set up in my broadcast shop in the US.
Telestream also makes Switch which *does* allow a user to proof an MXF file with CC.
PremiereCC is buggy -- when "proofing" a file things looked fine, yet when played back, the captions had "residue" some times which was frustrating.
SCC files generally describe captioning in the 608 spec. Some players need 708, and some need both.
The suggestions for MacCaption will be the "cadillac" option giving users the most flexibility to meet any provider's spec. The Compressor option will work in *some* instances, and will most likely require another step at a provider to get a completely "transmission ready" file -- devices look for the caption data in different places -- even though it is still "embedded" into the file.
A quick and dirty application called MediaInfo will allow a user to see what tracks are present (video at what codec, audio -- number of tracks at what codec, caption data tracks, etc) -- if they have a known working file from the provider, this can provide a roadmap to see what works at a given location.