TDA wants to re-encode my DVDflick Project

[marioval]

I use Tmpgenc DVD Author 3 when I want to add nice menus to my dvd that I create with either dvdflick, favc, or convertxtodvd. I use all 3 because they all heave their strengths and weaknesses so I use the right one based on my needs. If I import a VIDEO_TS that I created with favc or convertx then tda just adds a menu without re-encoding and the output process only takes a few minutes. But, if I import a VIDEO_TS folder created with dvdflick then TDA will attempt to re-encode the entire thing taking the usual 2 hours or so. Now it's my understanding that TDA will only re-encode if the source is not compliant. Can anyone shed some light on whats going on? Thanks. Here's a Gspot screenshot from one of the vob's that are in the dvdflick created video_ts folder if that helps.

[lowellriggsiam]

Based on true DVD compliance some programs will test the data and then judge for itself about it's compatibility. If the compression is seen as "non-compliant" programs frequently attempt correct this. This anomoly can be seen frequently after using tmpgenc to create an mpeg 1 or 2 file and then importing it into Nero which usually will find something wrong with the result of tmpgenc's conversion.

[MysticE]

Could it be in the final authoring? FAVC uses Muxman. Flick uses DVDAuthor.