Wondering if anyone else has ever seen this issue - searched the board but didn't find anything similar. TS source file run through PxxxxDxxxxxxx can output to project without re-encoding, but the same file "trimmed" with Smart Cutter must be fully encoded even though only minor edits were done with Smart Cutter to the source file. This is a problem because the complete re-encode takes quite a long time compared to the time it would take to output without a re-encode. I would think that the output from Smart Cutter would be fully TS compliant and not be seen by the Cxxxxxxxx app as "out of spec" (i.e., requiring re-encoding)....
Anyone have this experience or know of a possible way to "massage" the SC output file to be more in line with the native TS spec of the source (tried TSMuxer, but no dice)? Thanks!
Cxxxxxxxx PxxxxDxxxxxxx Problem w/ Smart Cutter...
-
- Posts: 1
- Joined: Sat Mar 09, 2013 5:21 pm