Stuttering on LiveTV (5 Viewers)

[Rudi99]

How about giving the user the ability, to choose between dropping or pixeling or giving the user the ability to adjust the sensitivity of the tsreader?

 

[tourettes]

How about giving the user the ability, to choose between dropping or pixeling or giving the user the ability to adjust the sensitivity of the tsreader?

Currently there are zero settings that user can configure about TsReader / TsWriter. It would require adding either .xml parsing into directshow filters (big no) or extending the interface for TsReader to allow MP to configure the filter proporties.

The later one is not such bad from the design point of view, but it will create more MediaPortal has crashed nagging when users are experimenting with such settings and then completely forgotting that they had such setting turned on/off.

The best sollution is to fix the signal

Ambass coud you check that we arent too agressively dropping data after the discontinuity in the stream happens?

 

[charli181]

How about giving the user the ability, to choose between dropping or pixeling or giving the user the ability to adjust the sensitivity of the tsreader?

+1

I'm with Rudi99 with this as I have never had MP crash on me due to this issue and feel like this change is a big step backwards in TV Functionality. The sensitivity of bad packets seems very high as I have more skips now then I had pixelations before.

I think education on this setting would be the best solution if MP Crashes are of big concern. It should be marked in config with maybe a warning (message box maybe), that turning on/off may cause crashes....please please please - reconsider the options...

 

[druid9]

Thats because

#1 those errors arent yet logged in the TsReader.log when the stream has those)
#2 Pixelation is seen as the larger amount of data is not dropped

Mainly the stuttering / dropped frames is happening on the recent builds as TsReader is more strict when it comes to corrupted stream data. This is done to help badly written codecs (almost every single one) to cope with those streams that have errors. It much smaller usability issue to have small stuttering on corrupted stream than having MediaPortal crashing directly to the desktop when some coded decides to cause a crash.

I understand that, but we are not talking small stuttering here, on my system with RC2 stuttering is continuous. With RC1, a pixelation maybe every 10 minutes. The sensitivity of Ts reader is obviously much heightened with this release. Functionality of RC1 is fine for me, and like others I have never had a codec cause a crash to desktop. Not that I don't want to, but I simply can't upgrade to RC2 while it is like this.

 

[Shazell]

I live some 25 Km away from the nearest DVB-T transmitter but it is very high up and I can actually see it, my antenna is correctly aligned and I also use a booster. I have around a 60% strength signal with 100% quality.

I also cannot upgrade to RC2 and I am not sure there is much more I can do to get a better signal, I would only be guessing but I reckon there is probably a larger number of people with this stuttering problem than the ones who had the CTD's. I have no problems at all with my DVB-S reception.

There must be some solution that can cater for both camps as weak DVB-T is fairly common.

 

[romadd64]

Currently there are zero settings that user can configure about TsReader / TsWriter. It would require adding either .xml parsing into directshow filters (big no) or extending the interface for TsReader to allow MP to configure the filter proporties.

The later one is not such bad from the design point of view, but it will create more MediaPortal has crashed nagging when users are experimenting with such settings and then completely forgotting that they had such setting turned on/off.

I also prefer the later solution, I know that it's not possible to change the interface until 1.0 final will be released.
In the meantime a quick and dirty solution like looking in the registry for a key ?

How about giving the user the ability, to choose between The best sollution is to fix the signal

It's not always possible to fix the signal, especially with terrestrial broadcasting that are more subject to disturbs. All set-top boxes favor pixelation over stuttering. I think it’s the best solution for user experience


romadd

 

[natopotato]

IV SOLVED THIS PROBLEM!!!! YAY FOR EVERYONE!!!!!!!!!!!



OK, Its more like maby i might have almost got a workaround.... <that just sounds less glamors

Heres the deal after some extensive testing here is what iv discovered. (please forgive me i am a MP noob 1 week YAY)

WMP11 (maby 10 also?) is the default player engine for MP, WMP11 CANNOT playback a TS stream without STUTTERING... It wont show pixilation just freezes for half a second.

BUT VLC on the other hand shows pixilation. and plays back TS streams perfectly!!
In THIS VLC PLAYBACK ENGINE PLUGIN Can be used to replace WMP11 as the default playback engine for TS files (and many others)

So the only problem is i cannot get this plugin to work. If it works as its supposed to (i think) it will playback .TS streams that Live TV generates and eliminate the problem. Showing pixilation instead of STUTTERING

Can somebody test if this will work, iv tried many times but i cant get the plugin to work on my system.

 

[bobbyd87]

How about giving the user the ability, to choose between The best sollution is to fix the signal

It's not always possible to fix the signal, especially with terrestrial broadcasting that are more subject to disturbs. All set-top boxes favor pixelation over stuttering. I think it’s the best solution for user experience


romadd

Bingo! It's impossible to assume that the user can fix the signal for this exact reason. I live far enough away from my broadcasters where I get a lousy signal, enough to get a good picture but not enough for Mediaportal anymore. OTA broadcasts are all now impossible to watch using Mediaportal because of the constant stuttering every second or two.

 

[jkwnz]

Stuttering resolved for me anyway

I've had the same stuttering issue since upgrading to RC2. The liveTV stutters every 5 seconds or so and the TSwriter log shows lots of continuity errors which as people have mentioned is a signal issue.
I have direct line of sight to the tower only 7km away.

Reading another thread someone has suggested signal noise (EMI) from the video card. The Avermedia Super 007 PCI digital tuner was installed next to the MSI 8500GT video PCI-E card (in a Dell 531s).

At a loss to solve the problem I swapped the wifi card for the tuner. Placing the wifi card (with its emi shield) between the tuner and the video card. And... in the last 3 hours or watching... seamless video...

 

[druid9]

Glad it worked for you, my tuner is a USB variety, nearly 5m away from the computer box, so sadly no go for me