Posts by nvdias

Tvheadend nightly builds for LibreELEC

Yes. it is the last tvheadend nightly version. It is working ok.

Just install as you would for any other addon. It will upgrade your current 4.2.X tvh version.

My two cents for the thread:

I have the following WORKING TV reception system:

I have a pi4 with an amazon powered hub, which as an independent 5V @4A PSU.

• Running LibreELEC 9.2.6
• The pi4 is powered by the hub trough the Header Pins.
• An external hdd and a tv receiver is connected to the hub, which in turn is connected to a pi4 usb port.

I've been using the following tv receptors (all with supported libreelec drivers) :

• tbs 5520se (DVB-S2 + DVB-C combo receiver) = awesome receiver (pity I've lost some money with the others);
• Hauppauge WINTV SOLO Hd -- works ok in DVB-C. But some small lost frames (reception / green artifacts errors);
• Geniatech / MyGica DVb-S2 (worst receiver I've ever used. works great for DVB-S, but very sensitive with S2 signals);

TV playback with TBS is very good.

I have no lost frames with the following configs:

• Whitelist 1920x1080 formats
• Adjust display refresh rate ON Start/Stop
• Sync playback to display OFF
• Allow hw acceleration MMAL ON
• During playback: Deinterlace method: AUTO

And the following configuration in:
/storage/.kodi/userdata/advancedsettings.xml

<advancedsettings>

<cache>
<buffermode>1</buffermode>
<memorysize>536870912</memorysize>
<readfactor>30</readfactor>
</cache>

<gui>
<algorithmdirtyregions>0</algorithmdirtyregions>
</gui>

</advancedsettings>

I hope this helps.

Quote from crazycat

Don't worry about legacy signal strength/quality in %. Usual this calculated in different way depend from developers

ok. thanks. But I'm not much worried with that.

But i am worried that with the new drivers, the device cannot tune any channels.

And that could mean it will stop working with libreelec in a near future...

Is it possible to confirm that the new drivers are still compatible with it ?

crazycat ,

After all, I was not compiling your last version, but one I had in my disk.

Now I've updated form your new gitsource GitHub - crazycat69/media_build

But now, the device cannot tune-in anymore !

The device which had the name in tvheadend as "Montage Technology DS3000/TS2020",

was now recognisable as "Montage Technology M88DS3103B", but incapable to tune in anything !

Reverting back to the old drivers, I was able to tune in, but with the old low signal issue.

Even with this low signal issue, is it possible to at least guarantee that the device is still supported (this, thinking in the future)?

Thanks.

I've downloaded you last media drivers and compiled them in osmc to test for different results.

But I'm getting the same low signal strength

Will it be a linux firmware issue for this device ?

thanks

Quote from crazycat

this old driver which use ds3k frontend driver.

Hi. thanks for your comment.

And there is no plans to update it ?

Any cheap usb receiver recommended for best results in Linux ?

I've just made as suggested, but no luck:

A new sdcard with LE for x86 booting in my PC.

Only Crazycats drivers recognise the device.

But the tuning is very bad.

A transponder that locks and plays perfectly when running within windows (with windows drivers, of course), cannot be locked when running in LE.

In an entire sat, only 2 transponders are locked by LE.

In the same sat, running in windows, there are tons of transponders and channels locked.

One could assume there is a linudvb driver issue (related to signal amplification ?).

At least for this device.

Please look at the dmesg above.

Bellow is the dmesg from LE in x86, with crazycats drivers:

Quote from Nicolas

Hello!

On windows your using x86 drivers and a PC or Laptop compared to LInux and Rpi4.

Have you tried x86 with Linux/LE?

Have you tried a powered USB Hub in the Pi to Power the Tuner?

Worth a Test to Tracks the Problem down.

Regards

Nicolas

Display More

Hi. Thank you for your suggestions.

Besides the receiver being self powered, I connect every USB devices to the Pi4 trough a powered USB HUB (which in turn has a 5V @ 4A PSU) in order to make sure that no issue comes from power issues.

I've also tried the same testing with a Pi 3 running OSMC without any other usb device connected, just to be sure.

All tests with a raspberry pi official PSU.

I've been using a Geniatech HDSTAR dvb-s2 usb receiver (self powered) in my Raspberry Pi 4 running LibreELEC.

recognised by dmesg as SU3000HD DVB-S USB2.0 //: Montage Technology DS3000/TS2020

firmware: dvb-fe-ds3103.fw

The reception has not been the best one on LibreELEC.

I've connected the same receiver to a Windows PC, and the signal and reception improved considerably !

My tests were with:

- raspberry pi4, libreelec: DVBLINK and TVHEADEND

- Windows 10: DVBLINK and SMARTDVB

using the same receiver.

Examples:

A transpoder with 10% signal in LibreELEC on the Pi has like 55% signal in windows.

A transpoder with 30% signal in LibreELEC (pi4) has 80% signal in windows.

In the end, I can watch channels in windows with top quality, that are impossible to lock in linux.

As if windows driver has some way of enable some sort of "amplifier" in the driver.

Is there way of adjusting the "power" in the linux dvb driver ?

Or an update to the linux driver that is not included in LibreELEC dvb drivers ?

This problem happens with all LibreELEC module drivers (crazycat, and "latest" included with 9.2.3. Standard drivers do not support this receiver)

I've attached a link to my dmesg in LibreELEC.

I have also a running dvb-c receiver from silicon labs. Please ignore it.

Only consider the dvb-s2 receiver.

That is true when running on a PC.

But having libreelec running in a RPi4 (as the case), and accessing it by ssh, parted and resizefs are already installed. No downloads, no installs, no other boots.

Or follow chewitt proposal above, for an even easier approach.

I use parted and resize2fs.

both included in libreelec and accessible via ssh.

Call parted and then use the following commands:

select (to select your disk /dev/sda ?)

print (show the size of the disks and partitions)

resizepart (to resize the partition to the new size)

quit

Then call resize2fs following the partition path (probably /dev/sda2, but you should validate-it yourself )

resize2fs /dev/sda2

reboot

Warning: You must be very careful using these tools, as you mich loose everything in your disk.

Post back your results

yes. of course.

it's kodi in top, that reports 30% CPU usage

Not other running services.

And yes: I've launched kodi with a clean /storage/.kodi/ just to make sure it is not a config issue

mine too !

and for thatm the temps are always around 60C

30% cpu in idle is too much.

Ricardo666 , were you able to configure the openvpn addon?

Quote from ChrisCwmbran

Around my house I use 3 Raspberry Pi 4s, each of which has an official DVB hat fitted.

Two of them are connected to Samsung 4k TVs and the other to a Samsung HD TV. All are patched up to date and run Librelec 9.2.3.

Generally things are working well - but in order for TV programs recorded with TVHeadend to have sound in sync with the program I have found I am forced to set "Adjust display refresh rate" to Always and "Sync playback to display" to fix it.

However I have a very odd problem when watching other content because the audio sounds like it recorded on 'elastic' which is currently having its tension altered so the pitch is always changing.

This seems to happen with 2160P 24 frames per second recordings and 1080P 24 frame per second recordings alike. The video playback is fine.

Can anyone point me in the right direction as to what is going wrong please?

Thanks in advance!

Chris.

ps - In case its relevant I'm in the UK and TVHeadend records at 50fps.

Display More

I use a hauppauge wintv, with similar symptoms.

I've been using different buffering setitngs as the ones reported above.

I also use:

Adjust display refresh rate" at start/stop only

"Sync playback to display" to off.

Whitelist 23.976, 50 and 60 fps to assure the correct frame rate per content.

About tvheadend settings, I've noticed better results with a dvr recording profile I've called "matroska", with the following settings in tvheadend:

configuraiton / recording / digital video recording profiles / matroska /usinng profile matroska

the maktroska profile is defined in configuration / stream / stream profiles as:

matroska

webm off

reorder dvbsub on

when watching tvheadend channels or recordings, if some sound is out of sync, usually a stop and start is enough to solve.

Not the ideal solution ...

- NOTE:

I've also tried realtime ffmpeg encoding.

Solves audio issues, but for he rpi4,I need to lower the bitrate a lot, and the final quality is not acceptable (for me). And ffmpeg will take a lot of cpu, and during transcoding you will not be able to do anything else.

Just try creating a new SPAWN profile and using the following command line (assuming you have the ffmpeg add-on installed):

ffmpeg -loglevel quiet -i pipe:0 -pix_fmt yuv420p  -vcodec mpeg2video -vb 1024k  -bufsize 1024k -g 100 -af "aresample=async=1:first_pts=0" -acodec mp2 -ab 128k -f mpegts pipe:1

Then create a dvr profile that uses this new stream profile.

Good luck.

An report your findings !

Same here.

1886 working great !

Thanks

You just have to install the add-on and have-it enable for the path to be searchable.

you can also try:

/storage/.kodi/addons/docker.openvpn.server/bin/openvpn-add-server

Quote from spontex

Hi,

I have been running TVH 4.2 for years, but I just reinstalled my computer from scratch and told myself that it would be nice to try TVH 4.3, since there is a feature I would like (better image cache management to avoid thousands of temporary files and slow startup).

So I took the latest LibreElec (9.2.3) and the latest TVH nightly (4.3-1885-08.06.2020) and installed it.

It worked a few hours, but now it does not anymore, due to a crash (log attached).

I have read on the forum that I might be due to a mismatch between the config file version and the TVH version.

It happened just after I set up my EPG by using the Kodi addon and pointing it to my XMLTV file location.

Many thanks

Display More

I'm also using tvheadend 4.3 betas for quite a while.

Version 1867 works great.

Yesterday I've tested version 1885 and had the same issues as you

It also happened some version ago.

I suggest you use 1867 until the next releases comes out.

Tvheadend nightly builds for LibreELEC

(As I always backup tvheadend add on settings before an upgrade, it was easy to restore the settings and resinstall previous version.

Settings are here:

/storage/.kodi/userdata/addon_data/service.tvheadend42/)