44 replies to this topic

[Pr2]

The current timeshift cannot shift streams (as far I know) don’t worry (if the as far I know is correct)

 

The current implementation can timeshift stream.

The only problem with stream is when you want to record it since most stream servers allow only 1 connection, recording automatically creates 2 connections so recording always failed.

[nietgiftig]

...

I would say just write the already received data also to a file. And that’s what the current implementation does. So is it really so bad??

 

Not really, It just works.

 

The use of permanent timeshift is to have a choice to preserve an already made or running timeshift recording that is necessary to have when you use timeshift., inclusive the current running one.

 

The problems come when people are using the timeshift portion of enigma, the rewind and skipping in the current running recording, or are making one or more regular recordings.

The last one can be neutralized with the option to auto stop timeshift when recording in the traditional way.

 

Has little to do with the purpose of the plugin "permanent timeshift" or better named "save current running or earlier made timeshift recording"

(I know, to long for a button  )

[littlesat]

The current implementation can timeshift stream.

The only problem with stream is when you want to record it since most stream servers allow only 1 connection, recording automatically creates 2 connections so recording always failed.

For streams a work-a-round might be... stop the stream... start the recording... play the recording....

For live streams this might be fine (with side effect you miss a small part of the transmission or a small part of the transmission recorded you just saw before)... But for 'file' streams you record it from the beginning)

[littlesat]

A new feature we also might need is put some kind of bookmark in the recordings list that point to a recording a 'play-point' where the program starts based on EPG...

Edited by littlesat, 20 December 2018 - 11:35.

[betacentauri]

During recording the marks are collected if now/next show a program start/end. Using these marks while the recording is running is not very easy as playback and recording use 2 different threads. I already thought about that.
Either store the marks immediately after receiving in the cuts file or send a “signal” from the recording thread to the playback thread. Don’t really know if that works.