• 1
  • 2(current)
  • 3
  • 4
  • 5
  • 20
VNSI4 alpha
#16
Recordings in progress is a special case of timeshift where the buffer is the growing file. Opening the recording channel opens the recording and the user is positioned at the beginning of the buffer. You can navigate to the end and you are almost viewing live.

Recordings in progress work with my external USB HDD and 1080i but the file buffer method only with SD content. I think I can make the file buffer method also work for HD on this box.
Reply
#17
>> Recordings in progress is a special case of timeshift ...
That means, timeshift must be enabled if I want to watch Recordings in Progress ?? I didn't enable for now, because I can't decide where to write to. I can't find an Option for the FilePath (want to write to NFS)

>> where the buffer is the growing file
But the growing File is on the VDR Server and is streamed through vnsi-server (or whatever) to the Client. If I start Recording at the Server and switch on my clientbox (normaly turned off) one hour later, there is no chance for the client to write the file (and me to watch it)
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
#18
Timeshift does not have to be enabled for watching recordings in progress. Note that there is no buffering on the client machine. All this is done on the vdr server. The file buffer is placed into vdr's video directory for the time needed.
Reply
#19
>> Timeshift does not have to be enabled for watching recordings in progress ...
Ah, yes. Thats what I ment to understood

But then, pausing and spooling does not work

I started recording on the server. Choose this channel in xbmc. Recording starts correctly from the beginning, but then, pressing pause, nothing happens. Movie still keeps playing
Same with FF and FR
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
#20
Thanks, I'll fix this.
Reply
#21
>> Thanks, I'll fix this.
That would be great. Thanks in advance for that

Another Question to "normal" timeshift (the Ringbuffer)
I decided to use my SSD Disk for timeshift.
The File is located on the Client Filesystem ? And, if yes, where, or do I have a choice for its path ?
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
#22
Quote:Note that there is no buffering on the client machine. All this is done on the vdr server. The file buffer is placed into vdr's video directory for the time needed.
Reply
#23
Aha, thanks for Reply
But what happens with more than one Client
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
#24
The server would create a buffer for each client. The buffer can't be on the client because the demuxer is on the server.
Reply
#25
OK, thanks
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
#26
(2013-03-12, 09:09)FernetMenta Wrote: The server would create a buffer for each client. The buffer can't be on the client because the demuxer is on the server.

Is it possible to have a single buffer shared among multiple clients watching the same channel? I afraid the hard disk may be overloaded with multiple buffers, especially on HD channels.
Besides, in case of in-memory buffers, it would save a lot of memory.
Reply
#27
(2013-03-10, 22:05)FernetMenta Wrote: Timeshift does not have to be enabled for watching recordings in progress. Note that there is no buffering on the client machine. All this is done on the vdr server. The file buffer is placed into vdr's video directory for the time needed.

Would it be possible to set the timeshift path? I'm recording on a rather slow usb2 disk and I would guess performance would be better if I could timeshift to the ssd.
Reply
#28
Quote:Is it possible to have a single buffer shared among multiple clients watching the same channel? I afraid the hard disk may be overloaded with multiple buffers, especially on HD channels.

A ringbuffer won't work with more than one reader. But I can add an option to limit the number of clients requesting timeshift.

Quote:Would it be possible to set the timeshift path?

Yes, will do.
Reply
#29
- recordings in progress are seekable now, requires an update of XBMC
- 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.
- 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)

EDIT: external HDD formatted with ntfs don't work well.
Reply
#30
Ahh, nice, thank you

I'll look for it end of the week
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
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 20

Logout Mark Read Team Forum Stats Members Help
VNSI4 alpha3