Reply to thread

Message

<blockquote data-quote="SciDoctor" data-source="post: 285213" data-attributes="member: 11346">1...The way tv server works is the most efficient use of network bandwidth. Only required data is available in the buffer on the server to be pulled by single network clients.2..No and not efficent, realy defeats a server configuration and centralised file/data. Also NEBULA used the method you describe with their software and it was inefficient, poorly managed,bug ridden and bandwidth hogging and as such simply wouldn't work with wifi as overheads were imense and caused havoc on every connected wired client throughout the whole network.3..A server side buffer is in essence what tvserver uses but it strips the transport stream to specific channel+data, you can set the tvserver to buffer the whole single MUX (try a search) but this is impracticle as disk space usage is absolutly HUGE.4..Each client is assigned its own buffer by the tvserver but buffers (of same requested channels) aren't shared at the moment, this is the only drawback and inefficiency.5.. I don't experience this at all and is probably down to your hard drive subsystem, I have tested up to twelve concurrant recordings across six MUX and three buffered network clients.6..This is&nbsp; by design and is a limitation as buffer and recording are seperate, a discussion has been requesting an EPG driven buffer which would alllow for this 'record now' function to include historical buffer data with respect to EPG data.Maybe when feature freeze and RC status has concluded.</blockquote>

[QUOTE="SciDoctor, post: 285213, member: 11346"] 1...The way tv server works is the most efficient use of network bandwidth. Only required data is available in the buffer on the server to be pulled by single network clients. 2..No and not efficent, realy defeats a server configuration and centralised file/data. Also NEBULA used the method you describe with their software and it was inefficient, poorly managed,bug ridden and bandwidth hogging and as such simply wouldn't work with wifi as overheads were imense and caused havoc on every connected wired client throughout the whole network. 3..A server side buffer is in essence what tvserver uses but it strips the transport stream to specific channel+data, you can set the tvserver to buffer the whole single MUX (try a search) but this is impracticle as disk space usage is absolutly HUGE. 4..Each client is assigned its own buffer by the tvserver but buffers (of same requested channels) aren't shared at the moment, this is the only drawback and inefficiency. 5.. I don't experience this at all and is probably down to your hard drive subsystem, I have tested up to twelve concurrant recordings across six MUX and three buffered network clients. 6..This is by design and is a limitation as buffer and recording are seperate, a discussion has been requesting an EPG driven buffer which would alllow for this 'record now' function to include historical buffer data with respect to EPG data. Maybe when feature freeze and RC status has concluded. [/QUOTE]

Verification