help with "Failed to Start Requested Stream"

[lbit]

Hi,
can anyone help me with the error in the subject?
I've just installed nextpvr on raspi4 with ubutnu 20.10 server 64bit using the nextpvr-helper.deb method.
From the web interface I see my DVB-T adapter, and scan channels all right (~500 found).
Then if I go to "Channels" and try to play one I just get that error.
Logs end with 

08:28:21:511 [DEBUG] got request:
POST /stream/start?slipseconds=1200&target=LIVE%26%2Fvar%2Frecordings%2Flive-Rai%201-1776-2.ts HTTP/1.1
Host: localhost:35575
Connection: Keep-Alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 191

<tuning>
  <type>DVB-T</type>
  <name>Rai 1</name>
  <locator>
    <conf>177500000OFF</conf>
  </locator>
  <service_id>3401</service_id>
  <service_type>27</service_type>
</tuning>

08:28:21:511 [DEBUG] starting stream: LIVE&/var/recordings/live-Rai 1-1776-2.ts
08:28:21:511 [DEBUG] slip seconds: 1200
08:28:21:511 [DEBUG]
Rai 1
08:28:21:521 [ERROR] Failed to get tuning params for (Rai 1) from /var/opt/nextpvr/adapter0/frontend0-DVB-T-channels.conf

but note that directory /var/opt/nextpvr/adapter0 doesn't even exist. Only /var/opt/nextpvr exists, with correct permissions I think:

drwxr-xr-x 7 nextpvr root 4096 Mar  5 09:46 nextpvr

[mvallevand]

This message is confusing for sure. The multiple frontend scanning implementation was hacked and scanning has some bugs. What adapter*.conf files do you have in that folder.

Martin

[lbit]

This message is confusing for sure. The multiple frontend scanning implementation was hacked and scanning has some bugs. What adapter*.conf files do you have in that folder.

Martin

Thanks Martin. Under /var/opt/nextpvr I have no "adapter*" folder at all. And there is no *.conf file at all under the whole /var/opt/nextpvr hirarchy or /opt/nextpvr hirarchy.

If I'm supposed to have a folder for the adapter (do I?), that's clearly missing in my installation - not sure what should have created it but evidently it didn't happen.
if I do " find / -name 'adapter*' ", that doesn't find anything related to nextpvr. It just finds /dev/dvb/adapter0 and some kernel and python related stuff, so there is no nextpvr's adapter0 folder anywhere.

[mvallevand]

That message is bogus since there is no adapter folder, it would be in /var/opt/nextpvr

I suggest doing a scan and let it finish and then upload the logs.

Martin

[lbit]

I did this:
- stop nextpvr-server
- delete old logs and db3 file
- restarted server
- started scan on adapter0
- waited for it to complete (hundreds channels found)
- click save
- click the button (don't remember the name) for epg update
- waited for it to complete (0 found)
- click on close
- click on "channels" main menu
- click on first channel
- got error
Collected logs - attached - and anyway, there is still no /var/opt/nextpvr/adapter0* folder.

[mvallevand]

I see know you are missing this update https://forums.nextpvr.com/showthread.ph...#pid552206

Martin

[lbit]

Great, that seems to have solved. I'll test it further but everything seems ok.
Now I can watch all SD channels fine, while for HD channels I get "Server is not fast enough for playback in a web browser. (0.691x)".
What is not fast enough? Network should be fast enough (1Gbit lan), cpu shouldn't be much involved (unless nextpvr tries to re-encode but I hope it doesn't), so is it disk IO? Can I eventually use a ramdisk? Does nextprv buffers the dvb stream through a file even when not recording it? How much space would I need in the ramdisk?
Thanks
lbit

[mvallevand]

The RPi 4 is still not fast enough for HD transcoding. Use Kodi for direct play.

Martin

[sub]

Just a bit more detail to Martin's reply above - basically the server isn't fast enough to transcode in real time for playback in the web browser. It shouldn't have any problems with a player that can play the native streams (ie, without transcoding), like Kodi, or nlite, or the iOS/Apple TV clients etc.

[lbit]

Just a bit more detail to Martin's reply above - basically the server isn't fast enough to transcode in real time for playback in the web browser.

Just a doubt: considering that 'hd' dvb-t stream should be in h.264 (and relatively lowres) and that most browsers support that video format, why is transcode necessary?