Yea, I figured I didn't need the mpeg2 and h264 stuff. I left in that legacy part of his script for now. I'll likely refactor this to simplify it further. I didn't write these scripts and I don't get to control how they're called from the java code. So I'm working within the framework he's built, but, as you said, there are a few tricks I can play with. Honestly I feel the whole thing should be rewritten as a powershell script anyway, but, that's besides the point. That's nifty on the filename trick. In my case I'm trying to get it OUT of TiVo format and into a TS file. And because Xfinity sucks so bad, I HAVE to qsfix my files to prevent VideoRedo from hanging trying to output the edited files. Yes, they're THAT broken. In any case, I will likely take a look at simplifying these further for people. I just wanted to get them working first. Again, thanks so much for the support. I'm back in business just in time for season premieres with a total V6 solution. AWESOME!You don't need the specific MPEG2 or H264 parts of the profile. All profiles in v6 are match source so you can just use the "Transport Stream" profile and it'll pick MPEG-2 or H.264 automatically based on the source. The profile IDs have also changed. Although I'm not sure what he's using those for. I don't think we use profile IDs as input on any of the functions. Just the name or full XML of the profile.
There are also some tricks with the COM you could use. If you provide no profile at all it will attempt to pick a profile based on the extension of the output file. So if the output file is video.mp4 it'll pick the first profile that uses the .mp4 extension. There is also a hidden option where if you pass "sas" as the profile name it'll actually automatically find the profile that most closely matches the source file. This works for both codec and format. So if you pass in an H.264 .tivo file it will output an H.264 .tivo file.