On Wednesday 26 November 2008 06:25:57 Da Rock wrote: > On Mon, 2008-11-24 at 10:23 +0100, Nico Sabbi wrote: > > On Monday 24 November 2008 10:15:19 Da Rock wrote: > > > On Tue, 2008-11-18 at 08:30 +0100, Nico Sabbi wrote: > > > > Il giorno mar, 18/11/2008 alle 15.57 +1000, Da Rock ha scritto: > > > > > Sorry guys - I solved this myself. > > > > > > > > > > I don't know why I didn't think of this before, or perhaps > > > > > I was waiting for a reminder... anyway I ended up using > > > > > -tsprobe and -forceidx. -forceidx didn't do much, but I had > > > > > to set the -tsprobe too some stupid amount (8192000) and > > > > > hey! it suddenly found an audio stream. > > > > > > > > > > The MV and AC errors have disappeared so far too (probably > > > > > thanks to the -forceidx). > > > > > > > > > > Thanks for your patience guys. > > > > > > > > -tsprobe has effect only on mpeg-ts streams, not on avi or > > > > any other kind of file > > > > > > The avi is simply a container for the ts. Ergo -tsprobe is > > > useful in this case. Thanks for the pointer though. > > > > total nonsense > > To be honest I don't really care- it worked for me and fixed the > problem. If anyone else has a similar problem (if they choose to do > the job the same strange way I do) then this will more than likely > help them too. > > I did initially respond in a civil manner, but comments such as > this are neither warranted, nor useful. Something more constructive > might have been more qualified here, such as why the statement is > nonsense... > the AVI demuxer doesn't insert in the demuxing and decoding chain the TS demuxer (which is the only component of mplayer that uses the -tsprobe parameter), for this reason I wrote that your statement was nonsense. In my opinion my assertion doesn't have anything incivil or offensive: doesn't it sometimes happen to anyone saying some nonsense? And in case you wonder with what authority I say something about -tsprobe: I wrote the TS demuxer
