Reply to thread

Message

<blockquote data-quote="da-anda" data-source="post: 371184" data-attributes="member: 86409">Hi there,I'm interested in some technical insight of TVserver. I'm no coder, but I'd like to know how stuff is handled in the background to better understand why things are as they are, and to give qualified feedback and improvement suggestions.On reason why I'm asking is, that I'm interested in disabling default timeshift for TV-server. I know (read several times) that it's not possible in TV-server &quot;due to it's architecture&quot;, but why in detail, what part of the architecture? I can't imagine that it's due to multicast, because you can also provide a multicast stream over the network without timeshift buffer, can't you? Is it for multiple TV-card support to easier keep track of the different streams?The reason why I'd like to disable it is to get a far better zapping experience without using RAM-discs that slow down hibernation etc.. I'd also like to know how the zapping process itself is working - is the current stream killed and MP connects to a new stream, or is it one continuous stream only switching the data source on TV-servers side?How are multicasts handled? Is every client getting it's own version of the stream (as I read that reconnecting to a RTSP-stream will show the stream right from the beginning of timeshift and not from current live state)? If so, what is the reason for that? Technical limitations or something?Thanks.</blockquote>

[QUOTE="da-anda, post: 371184, member: 86409"] Hi there, I'm interested in some technical insight of TVserver. I'm no coder, but I'd like to know how stuff is handled in the background to better understand why things are as they are, and to give qualified feedback and improvement suggestions. On reason why I'm asking is, that I'm interested in disabling default timeshift for TV-server. I know (read several times) that it's not possible in TV-server "due to it's architecture", but why in detail, what part of the architecture? I can't imagine that it's due to multicast, because you can also provide a multicast stream over the network without timeshift buffer, can't you? Is it for multiple TV-card support to easier keep track of the different streams? The reason why I'd like to disable it is to get a far better zapping experience without using RAM-discs that slow down hibernation etc.. I'd also like to know how the zapping process itself is working - is the current stream killed and MP connects to a new stream, or is it one continuous stream only switching the data source on TV-servers side? How are multicasts handled? Is every client getting it's own version of the stream (as I read that reconnecting to a RTSP-stream will show the stream right from the beginning of timeshift and not from current live state)? If so, what is the reason for that? Technical limitations or something? Thanks. [/QUOTE]

Verification