[Bug] Question/Problem with Thumbs (1 Viewer)

[jameson_uk]

I think it would also be beneficial to see what happens when you try and create a thumb manually using mtn.exe in the MP folder and mtn.exe from the site. My experience (was only really looking at H264 material but looks like MPEG2 is also problematic now) was that no thumb would be created by MP version but one would with original version.

Would at least narrow it down to a problem with the changes MP has made to mtn.exe or whether it is a problem with mtn.exe code in both versions / an issue with the way TSWriter is creating files.

 

[tourettes]

Would at least narrow it down to a problem with the changes MP has made to mtn.exe or whether it is a problem with mtn.exe code in both versions / an issue with the way TSWriter is creating files.

I'm quite sure that the TsWriter can be ruled out since int mainly writes the stream that comes from DVB card (also playback would have issues if the file is not ok).

 

[infinite.loop]

Would at least narrow it down to a problem with the changes MP has made to mtn.exe

The last changes done by MrHipp fixed issues when creating thumbs for videos with some codecs (dont exactly remember which).
Now it seems that while it can create thumbs for those videos, it fails to create them for mpeg2 in many cases....
Fix one issue - get a new one.

 

[DreadFury]

Would at least narrow it down to a problem with the changes MP has made to mtn.exe or whether it is a problem with mtn.exe code in both versions / an issue with the way TSWriter is creating files.

I'm quite sure that the TsWriter can be ruled out since int mainly writes the stream that comes from DVB card (also playback would have issues if the file is not ok).

in one of the last svn versions, random ts files were not playable with certain codecs (video pin would not connect with arcsoft) while others from the same card were fine.

i think it is honestly the way tswriter creates the files, it seems to do something at random that some codecs don't like while others ignore.

since mtn.exe can create thumbs on some recordings and not others (same card, same channel, same show) i think there is some unseen issue going on here.

 

[infinite.loop]

Would at least narrow it down to a problem with the changes MP has made to mtn.exe or whether it is a problem with mtn.exe code in both versions / an issue with the way TSWriter is creating files.

I'm quite sure that the TsWriter can be ruled out since int mainly writes the stream that comes from DVB card (also playback would have issues if the file is not ok).

in one of the last svn versions, random ts files were not playable with certain codecs (video pin would not connect with arcsoft) while others from the same card were fine.

i think it is honestly the way tswriter creates the files, it seems to do something at random that some codecs don't like while others ignore.

since mtn.exe can create thumbs on some recordings and not others (same card, same channel, same show) i think there is some unseen issue going on here.

It is also possible that there was something wonky in the stream your tv-card received / created.
There are many possible reasons.

 

[DreadFury]

I'm quite sure that the TsWriter can be ruled out since int mainly writes the stream that comes from DVB card (also playback would have issues if the file is not ok).

in one of the last svn versions, random ts files were not playable with certain codecs (video pin would not connect with arcsoft) while others from the same card were fine.

i think it is honestly the way tswriter creates the files, it seems to do something at random that some codecs don't like while others ignore.

since mtn.exe can create thumbs on some recordings and not others (same card, same channel, same show) i think there is some unseen issue going on here.

It is also possible that there was something wonky in the stream your tv-card received / created.
There are many possible reasons.

I have this issue on 3 different cards, it is random on all three.
Most files are created just fine, but every once in awhile something goes wrong.

Also, these problems didn't exist before, they recently started happening in the last few SVN updates and carried over into RC1.

I have tried this on XP Pro and Vista Ultimate x64 with the exact same results.
I have tried every driver for every device under the sun with no change.

I find it highly unlikely that the same problem would reproduce itself on three separate cards on two OS systems (and even remote systems on the created files)

It is possible, but the chances of the same wonky behavior on three separate cards of different types all happening out of the blue at the same time are extremely remote...

 

[infinite.loop]

I find it highly unlikely that the same problem would reproduce itself on three separate cards on two OS systems (and even remote systems on the created files)

It is not highly unlikely.
It could be caused by bad/corrupted signal - or "broken" hardware from the TV-provider - or the tv-provider manipulates the stream in a "bad" way.

We have seen all that many times in the past.

But to be sure what happens in your case, we need a sample. Nothing else will help to find out what is going on.

 

[wjw]

I have to say I don't think it's Tswriter.

I have some HD TV recordings that were made using Windows Media Centre (Win7 edition). I have added the .wtv extension so that MP can see - and will play - these files as videos. The earlier version of mtn.exe created thumbs but the newer version will not.

 

[DreadFury]

I am actually referring to the original mtn.exe as it has had WAY better results that the one compiled for MePo. (for me)
The only reason I Think it could be tswriter is that I have had other issues with mepo creating ts files at random that for some reason wouldn't play with certain codecs. (the video pin wouldn't connect, some codecs seem to ignore this issue and play anyways, whatever it may be.). This problem seemed to crop up during the last couple of svn releases, before that I had no such issues with the same setup and hardware.

as for hardware problems, all 3 of my cards/devices have worked fine without this issue in previous versions, they are all hauppauge devices not TV-service devices and they all get their signal from different sources. (one direct analog signal, one STB, one digital ATSC/QAM. All have the same issues at random.)

Using the original mtn.exe, the only problems I have are with random ts files created using MePo. (so far)
90% of the files created by MePo work fine in all aspects, including thumbnail creation (using the original mtn)

I could be totally wrong, but the pieces fit for my situation as older versions of MePo did not have these issues for me.

I can send a sample if you like, but since I can not tell if the file has a problem until a recording is complete or timeshifting fails, the files will be quite large.
If this is not an issue, I will find somewhere to upload the large files.
I am afraid that if I cut the files down in size it may contaminate the results.

Thanks!

 

[Paranoid Delusion]

I can send a sample if you like, but since I can not tell if the file has a problem until a recording is complete or timeshifting fails, the files will be quite large.

Should not be necessary, I posted about this in the team forum straight after RC1 release, I had 9 recordings, 7 without thumbs being produced, had run files through tsdoctor (try it) with 0 errors found, installed mtn.exe from the developers website and thumbs then produced (I have only mpeg2 recordings).

After that it has been confirmed by other team members, so we can reproduce this happening.

So I would advise anyone with this problem to run recording in tsdoctor, because if there are errors, then that may be the culprit for that file, while we track down when this stopped working correctly.