I'll then make sure there are no other lines in the SCC file that are causing such problems. If they do look close, I will start to add frames to the offending line's timecode and saving, then testing in QuickTime Player until I get it to work. If I can't find any, I look at the timecode and count the characters to give me an idea of whether or not the timecodes may be too close. Once I identify the offending line, I will look it over for anomalies as above. I will keep splitting the file in this manner until I get it to work again and then not work again, so I will eventually home in on the line that's giving me the problem. If it does, I know that the error lies in the last half of the file. I'll drag the SCC file onto the QT icon and see if it opens properly. That way I can undo my cut and try again. I will leave the text editor open while I test the saved SCC file in QuickTime Pro. I will typically select and cut all the captions from the midpoint of the file till the end and save it. I do this by opening the SCC file in my text editor and using cut and paste, I test out sections of the file. Before you can do anything about this, however, you need to find the caption (or captions) that have timecode issues. If someone would verify what this is exactly, I'd love to know myself. This seems to vary, however, with different captions, so I've not found it to be a hard and fast rule. Subtracting 18 frames from its timecode should not run into the timecode of the previous caption. So the caption "I may be going now" might need 18 frames of buffer time to display. If you add all that up and subtract if from the timecode for that line, it should not be less than the timecode preceding it. In the SCC format, each caption needs about 1 frame of buffer time per every 2 letters of a caption. The other more difficult thing to find is what's known as a timecode overrun. The line should have ended with " 942f", but instead it is " 42f". This will throw an error when it goes to display in QuickTime. ![]() Note the last number sequence is only 3 characters long as a result. Instead of it being a 2 digit number to represent the character, it is only one digit, which throws off the rest of that line. In the example above, an unsupported character is showing up as a bullet. Sometimes this could be caused by a character in the captions that is not supported by the SCC format which can goof up the sequence of numbers. If you see anywhere where a line ends with a 3 digit number instead of 4, there's probably trouble there. ![]() MovieCaptioner always creates them in sets of four digits. Every set of alphanumeric digits should be in sets of four usually, although they can come in twos, I believe. All lines must have at least some formatting applied, even if there is no text in the caption.Īnother thing to look for is unpaired binary code. Here are a few types of things I might look for.Ī blank caption after the timecode. Here I'll do a quick scan to look for certain types of anomalies. To troubleshoot this, I'll open the SCC file in BBedit or the free version called Text Wrangler, available from. Sometimes, though, an SCC file can have a garbage character in it that may allow it to play in QuickTime properly, but will cause an error in other applications. If you see that, then you know you have troubles in River City. It will have a black background, it will display smaller than a working file, "Scenarist_SCC V1.0" will show at first, and the binary code will display instead of the transcribed captions if you scrub through it. ![]() A file that has errors will open like this. It should have a white background and if you scrub through the movie, you should see captions. So, as long as you have the plugin installed you should be able to see captions in an SCC file that you open in QuickTime Pro. It only costs $30 and it well worth it for the increased ability to work with QuickTime movie files. You can install QuickTime 7 from your Snow Leopard install disk, then upgrade it to QuickTime Pro via the Apple website. QuickTime X, the default QT Player that comes standard with Snow Leopard does not have all the functionality of QuickTime 7. Note that as of this writing, QuickTime 7 is necessary for all the features of QuickTime Pro to work. If you have QuickTime 7 open, you'll need to close it to make the plugin available when you re-open it. Once you download it, just drop the plugin into your QuickTime folder in your hard drive's Library folder. It can be downloaded (currently) from this link. To be able to do this, however, you need to download a free plugin from Apple for importing SCC files into QuickTime. Knowing that it is a bad file in the first place is simple. Here is a (hopefully) helpful strategy for zeroing in on the cause of the problem. From time to time you may get an error in your SCC caption files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |