• 1
  • 2
  • 3(current)
  • 4
  • 5
  • 30
Live TV doesn't work on Openelec [tvheadend server]
#31
Is this the issue where people start a channel and it shows play pause play pause then nothing... xbmc doesnt crash just stays on a black screen.. Im currently getting this after updating to xbmc rc3 through raspbmc... There was a nightly build that didn't have this issue I think it was 22 dec...
Reply
#32
@cavej03 Yes this is the problem.
Reply
#33
Same issues here. Really frustrating. I've tried every build of both RaspBMC and Openelec. Any update on this?
Reply
#34
My question as well. Is this reported?

//Edit: ah, yes Tongue http://trac.xbmc.org/ticket/13783
Reply
#35
Hi,
any news about the issue ?
Thanks
The only winning move is not to play.
Reply
#36
I'd like to know too. What I find weird is that two popular distributions (OpenELEC and Raspbmc) are now in release candidate status and neither have solved this issue despite many bug reports and threads indicating that LiveTV with TvHeadend as backend is not working.

I have yet to find a conclusive answer as to what is causing it to fail. I verified that my Pi can play recorded DVB transport streams, yet streaming from TvHeadend remains problematic for some reason. It has been said that the issue is with the omx player component but since recorded DVB transports work, it remains unclear why this is not fixed. Surely this is a must to fix before the final release can be made?

Not just asking though. I am willing to help out. I looked into the code for the TvHeadend add-om from OpDenKamp's GIT repo, but failed to find any reference to the fabled omx player. The actual playback implementation is probably abstracted somewhere but couldn't find any reference to Pi-specific stuff. Does anyone know where the Pi-specific TvHeadend add-on stuff is?
Reply
#37
I would also appreciate it, if this issue could be fixed soon!

I don't think, that there is anything Pi-specific in the Tvheadend add-on.

The Pi-specific stuff is here:
xbmc/cores/omxplayer/OMXPlayer.cpp

The combination of how the Tvheadend PVR addon uses/fills the demuxer is perhaps somehow other than the other PVR addons. This in combination with the omxplayer leads to the issues.

Could it have something to do with i-frames and b-frames? At the beginning of the Tvheadend addon development there was an option to skip b-frames until the first i-frame arrives (IIRC). Perhaps the omxplayer needs an i-frame first?!?
Reply
#38
Last I heard, the issue was in the R-Pi firmware, and there's nothing XBMC can do on our level. I don't really know how all that works or why that is, but I do trust the people who said it.
Reply
#39
(2013-01-15, 17:19)Ned Scott Wrote: Last I heard, the issue was in the R-Pi firmware, and there's nothing XBMC can do on our level. I don't really know how all that works or why that is, but I do trust the people who said it.

I investigated this. Manages to reproduce problem and got this log file:
https://dl.dropbox.com/u/3669512/temp/xbmc_headend.log

Lars said:

"This doesn't seem right to me.

23:49:32 T:2805740608 DEBUG: COMXPlayer::SetCaching - caching state 2
23:49:32 T:2805740608 DEBUG: OMXClock::OMXSetSpeed 0 buffering 0
23:49:32 T:2805740608 DEBUG: OMXClock::OMXSetSpeed 1 buffering 0
23:49:32 T:2778264640 DEBUG: COMXPlayerAudio - CDVDMsg:TongueLAYER_SETSPEED
23:49:32 T:2805740608 DEBUG: Previous line repeats 1 times.
23:49:32 T:2805740608 DEBUG: COMXPlayer - CDVDMsg:TongueLAYER_SETSPEED speed : 1000

caching state 2 = CACHESTATE_PVR
This means that player must be paused until the video and audio buffers
are filled up enough before starting to play the stream.
Last line from this paste indicates that playback is starting, before
caching state is set to CACHESTATE_DONE, and even before stream
descriptions are requested from demux.
So my best guess is that this is causing the problem."

which looks like an omxplayer problem.
Reply
#40
If this is a raspberry pi firmware problem, why is there no issue?

I searched this repo:
https://github.com/raspberrypi/firmware/...state=open
Reply
#41
Is anyone able to report a log of this issue on raspberryPi github ?
this would be helpful,
thank you.
The only winning move is not to play.
Reply
#42
I reported this issue:
https://github.com/raspberrypi/firmware/issues/137

Please add information if you have any and post your configs so that this bug get fixed .
Reply
#43
(2013-01-17, 15:35)regnets Wrote: I reported this issue:
https://github.com/raspberrypi/firmware/issues/137

Please add information if you have any and post your configs so that this bug get fixed .

Good, that you have reported it, I hope this will help to get it fixed!
Reply
#44
(2013-01-17, 15:35)regnets Wrote: I reported this issue:
https://github.com/raspberrypi/firmware/issues/137

Please add information if you have any and post your configs so that this bug get fixed .

Its not a firmware problem as popcornmix pointed out, this issue happens in omxplayer.

All our hopes are on adamsutton and gimli, no need to create bugs anywhere else imho.
Reply
#45
okay, submitted the same ticket also to omxplayer:

https://github.com/huceke/omxplayer/issues/98
Reply
  • 1
  • 2
  • 3(current)
  • 4
  • 5
  • 30

Logout Mark Read Team Forum Stats Members Help
Live TV doesn't work on Openelec [tvheadend server]5