reencoded M2V: problems with video length

[XAWE]

Hi ye guru-guys,

I need help with the follwing problem..
Got an M2V ripped from a DVD.
ran this:
pulldown src.m2v dst.m2v -norff -framerate 23.976 -prog_frames p -aspect_ratio 16:9
on it; Got a video that has pure progressive frames @ 23.79, 16:9 AR.
Feed it to Canopus Procoder, which detects that this video is 2:26, which is correct.
Set the settings as usual (Progr_frames, 4:3, 23.79), reducing bitrate to 5000Max.
On output got another M2V, which also has progr_frames, 23.976, 4:3 BUT the reported mov length is 1:26!!!! Procoder screwed it up somehow. Attempts to run TMPEGEnc/Merge & Cut result in having another padding stream added into M2V, and Pulldown.exe could not be applied to a file with 2 streams in it.. Not other tools work on this file, like for example ReStream or MPEG Sequence Maker...
Did I do something wrong? Could It be that the ripped M2V is not quite progressive video pulled down? How could I fix the time on the resulting movie ?

[XAWE]

Hi ye guru-guys,

I need help with the follwing problem..
Got an M2V ripped from a DVD.
ran this:
pulldown src.m2v dst.m2v -norff -framerate 23.976 -prog_frames p -aspect_ratio 16:9
on it; Got a video that has pure progressive frames @ 23.79, 16:9 AR.
Feed it to Canopus Procoder, which detects that this video is 2:26, which is correct.
Set the settings as usual (Progr_frames, 4:3, 23.79), reducing bitrate to 5000Max.
On output got another M2V, which also has progr_frames, 23.976, 4:3 BUT the reported mov length is 1:26!!!! Procoder screwed it up somehow. Attempts to run TMPEGEnc/Merge & Cut result in having another padding stream added into M2V, and Pulldown.exe could not be applied to a file with 2 streams in it.. Not other tools work on this file, like for example ReStream or MPEG Sequence Maker...
Did I do something wrong? Could It be that the ripped M2V is not quite progressive video pulled down? How could I fix the time on the resulting movie ?

Update: bbdmux tools shows that this is a transport stream?!?!?
How could Procoder make something like that??? Since when MPEG2 Elementary Stream setting produces a TS?