Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
Hard to know without knowing precisely what the hardware is. Can you get a product id from windows?
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 21
Joined: Apr 2008
Reputation:
0
It DOES work how you ask, as nickr mentions, the issue will be wether TVH will see the actual device, and this is down to the chip-set in the tuner.
But technically it will work, and should only take an hour or so to test out, so well worth a punt. The most frustrating thing is setting up the TVH backend, takes a bit of getting used to.
One thing to be aware of is recording, you would have to rig up some kind of external storage as the pi3 will not have enough local, or indeed power.
Also consider Libreelec as the OS as it suggest it support the latest version of TVH better and more devices.
But if you just want to watch TV then it should be fine. Although the supplied aerial is not a good source.
Posts: 611
Joined: Aug 2014
Reputation:
76
My understanding of Kill Kodi within the context of that discussion refers to use of OpenELEC/LibreELEC (installed on rpi3) in order to get just enough operating system with a tvheadened backend available for enabling if you have a DVB-T usb stick that is recognized by LibreELEC (Then use rpi3 as simple home network TV PVR for devices around house that are not directly connected to an Ariel etc)
Killing kodi is essentially just stopping kodi running (via ssh) in situations where you do not intend to be using kodi front end connected to a TV on device that is running the tvheadend server.
i.e. ssh into rpi3 and "systemctl stop kodi" = stops Kodi and "systemctl start kodi" = starts kodi
Yes should work just fine..
RPi4, (LibreELEC 11.0) hdmi0 -> Philips 55PUS7304 4K TV, hdmi1 -> Onkyo TX-SR608 AV Receiver
Posts: 21
Joined: Apr 2008
Reputation:
0
It does record, but I wanted to be brief in response, there are a number of lets say concerns.
1. Small storage (local), some recordings will eat that up quickly
2. The more R/W you do to these cards can create more chance of corruption if the card isn't 100%
3. Unless you have a VERY good psu, this too will cause some potential issue.
But having said that, your setup could run 100% for you with no issues, and I love the idea of the kill kodi, not seen that one, and it makes good sense.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
In relation to an SD card for recording, bear in mind that my system shows about 4.5G per hour for recordings. These are HD h264 recordings. MPEG2 will be bigger.
Its about 1G per hour for SD h264 recordings. Again MPEG2 files will be bigger.
YMMV as different broadcasters use different compression rates, but those figures should be some sort of guide.
So you ain't gonna get much even on a 64G card. It will, of course, deliver proof of concept, but if you are going to seriously start using a PVR, 64G will quickly become full.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 806
Joined: Nov 2015
Reputation:
33
All of my streams are MPEG2, and consume about 9-10GiB/hr. An external USB drive or network mount is really best if you're going to do any recording.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
2016-06-22, 14:48
(This post was last modified: 2016-06-22, 14:50 by nickr.)
What exactly did you type? Please copy and paste your input and output
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 594
Joined: Jun 2007
Reputation:
4
Input:
"systemctl stop kodi"
Output:
"Failed to stop Kodi.service: Unit Kodi.service not loaded".
That's everything I swear!
