• 1
  • 2
  • 3(current)
  • 4
  • 5
  • 20
VNSI4 alpha
#31
I added a vdr setup option to configure directory for file buffer. Accessible via vdr UI or setup.conf
Reply
#32
Would it be possible to limit vnsi connection only to serve recordings and not live TV/epg? Let's say VDR is used natively for watching TV on another machine, so it's undesired xbmc can "steal" live TV, yet I would like to be able to play recordings, because it doesn't interfere with anything.
Reply
#33
Why don't you set priority to -1 on the machine you don't desire to watch live tv. Then it won't interrupt any other clients.
Reply
#34
Is it in vnsi settings?
Reply
#35
Not sure what you call vnsi settings. It's the addon settings dialog where you also specify ip and port of the vdr server.
Reply
#36
Ok I see it, thank you.
Reply
#37
Hi FernetMenta, really nice new features with this release. Thank you!
I'm tempted to switch from XVDR but I'm wondering how does VNSI addon handle channels with multiple audiotracks? Is there a way to have preferred langauge audio stream played on every channel (I'd like to have Czech audiotrack by default, but I use xbmc with English UK region/strings - is that a problem?)
Or do you have to set correct language audio track manually each time for each channel.
Or when you select an audio track in client, this track will be used next time I watch this channel?

Thanks for answer.
Reply
#38
You set preferred audio language in settings - appearance - international. If your desired language is available in the input stream, it will be chosen.
Reply
#39
nice, thanks Smile I will try this version over weekend.
Reply
#40
(2013-03-13, 18:57)FernetMenta Wrote: - recordings in progress are seekable now, requires an update of XBMC
It works, can skip forward and backward, no problem. But, if I stop watching and start watching again on this channel, it always starts at the beginning. It would be cool continuing at the last position Wink
Quote:
- vnsi addon settings have a new open "timeshift" which allows the client to request it. If the clients requests timeshift and this is not enabled on the server, it has no effect.
It is a good idea if client can decide if he wants timeshift buffer or not. What do you think about this:
  1. Let client decide if he wants timeshift or not (that is what you implemented in your last release)
  2. Let client decide if he wants buffer in ram or in file (mechanism are already there, see 1.)
    0 == No timeshift, 1 = Buffer in RAM, 2 = Buffer in file
  3. Let client decide how big the buffer should be
    0 = Take server configuration, 1-20 Size in 100MB(Ram) or 1GB(File)
So, every client can make his own decision which kind of timeshift buffer he wants

Quote:- optimized file buffer method. It works well with an external HDD connected to a USB 2 port. (at least on the machine I tested with)
yes, it works now much better. Watching a HD-LiveTV with timeshift buffer is located on an external 2.5" USB2 HD is no problem now
Kodi 18.6 @ openSUSE 13.1 x86_64 - Asus E35M1-I DELUXE | 8GB Ram | 240G 2.5" SSD
Kodi 20.2 on 1st Raspberry Pi B @ XBian | Kodi 20.2 on Raspberry Pi 3B+ @ XBian | Kodi 21a2 on Raspberry Pi4B @ XBian | Kodi 19.0 on SolidRun i.MX6 @ XBian
VDR 2.4.5 & Tvheadend4.3-1917 (for recording) on Cubieboard2 @ Debian Buster
Reply
#41
Quote:It would be cool continuing at the last position

This would require to store position for every possible client. Maybe in the next iteration.

Regarding configuration.
Ideally the entire account management is on the server. It does provide the resources and knows its limits. Another example is allowed_hosts where client access is defined. But this requires a UI and storage area for the data.
Reply
#42
Hi FernetMenta,
Do you know if XBMC 12.1 will be compatible with VDR UI (with GLES) of VNSI4 ?
Reply
#43
Compatible yes, but the vdr UI won't show. The required gui lib won't be backported to Frodo branch because it's more a feature than a fix. VNSI4 checks the version of the lib and if version is less than required, vdr UI won't be available.
Reply
#44
I did

git clone https://github.com/FernetMenta/xbmc.git xbmc-$dat_ext
cd xbmc-$dat_ext
git clone --branch vnsi4 git://github.com/FernetMenta/xbmc-pvr-addons.git pvr-addons

and get this
...
src/VNSIAdmin.cpp:373:12: error: type '<type error>' argument given to 'delete', expected pointer
src/VNSIAdmin.cpp: In member function 'virtual bool cOSDRenderGL::Init()':
src/VNSIAdmin.cpp:382:3: error: 'vis_shader' was not declared in this scope
src/VNSIAdmin.cpp:382:20: error: expected type-specifier before 'CVisGUIShader'
src/VNSIAdmin.cpp:382:20: error: expected ';' before 'CVisGUIShader'
...
Server OpenSuSE 12.3 - vdr-2.2.0 - 2xSatelco EasyWatch-C - streamdev-server git-19.02.15
Client OpenSuSE 12.3 - vdr-2.2.0 - SoftHDDevice git-19.02.15 - XBMC - Nvidia GT 610 / 331.79
Client Zbox ID84 OpenSuse 12.3 - vdr-2.2.0 - SoftHDDevice git-19.02.15 - Nvidia 331.79
Reply
#45
What is you host system? This code is in the block of
#if defined(HAVE_GLES2)

Please post config.log of pvr-addons.
Reply
  • 1
  • 2
  • 3(current)
  • 4
  • 5
  • 20

Logout Mark Read Team Forum Stats Members Help
VNSI4 alpha3