lossf
4th May 2004, 15:16
I'm an MPEG4 / DV newb and I've basically been using AutoGK as my only tool-- it's worked great. However, I'm running into big problems with a couple of recent convert attempts.
Both films are in a language other than my own, and so I'd really like to "burn in" the subtitles (as is the AGK default). They preview / encode just fine w/o subs, but something is massively screwed up with field order or something when I try to turn the subs on. I'd happily post a screenshot, but I can't seem to get one out of WMP / preview and have deleted all of the several screwed-up encodes I've already acquired. Synopsis: I get scrambled-looking green and purple "negatives" of the film scattered across the screen, with the subtitles displaying just beautifully in the midst of the chaos.
Eventually I got the first such film to work-- turns out I was choosing the wrong subtitle mode (letterbox versus wide). However, much to my surprise, neither mode works for this newest film (the two films are remastered and expensively packaged together by a very reputable source...)
I've just updated AutoGK from 1.0 to 1.19 and the problem persists.
Apologies for my obvious ignorance.
Both films are in a language other than my own, and so I'd really like to "burn in" the subtitles (as is the AGK default). They preview / encode just fine w/o subs, but something is massively screwed up with field order or something when I try to turn the subs on. I'd happily post a screenshot, but I can't seem to get one out of WMP / preview and have deleted all of the several screwed-up encodes I've already acquired. Synopsis: I get scrambled-looking green and purple "negatives" of the film scattered across the screen, with the subtitles displaying just beautifully in the midst of the chaos.
Eventually I got the first such film to work-- turns out I was choosing the wrong subtitle mode (letterbox versus wide). However, much to my surprise, neither mode works for this newest film (the two films are remastered and expensively packaged together by a very reputable source...)
I've just updated AutoGK from 1.0 to 1.19 and the problem persists.
Apologies for my obvious ignorance.