timeshift buffer location.

[ashley]

Hi, if I use kodi frontends where is the timeshift buffer defined as I want to take the writes off my ssd boot drive.
Ideally the default should be the same drive as an specified for recorded tv rather than the boot drive.
If I want to set this up in ram how much space needs to be allocated. - would I need a ram disk or can the product be configured to use ram natively?
Thanks.

[the_man]

By default timeshift path is dvblink/share/temp directory. You can change it by addin timeshift_path key to the root of dvblink_configuration.xml file with new path. Beware that all files inside this temp folder will be automatically deleted by DVBLink.
To make any changing available at dvblink_configuration.xml file, stop dvblink server and then, for example add this string:

Code: Select all

<timeshift_path>D:\TestTimeshift</timeshift_path>

[ashley]

Thanks. Great I can see through resource manager that the new location is being used.
If I want to make this go to a ram drive is it 4gb in total required or 4gb per client required? Is there a way of specifying buffer time?

[the_man]

As i know 4 GB for each of the Live TV streams.

[ashley]

Thanks. And what happens when a live stream is torn down? Are the files relating to that stream deleted?
Is there any way of reducing the size of the buffer? Reason why is that I'd like to push the buffer to a ram disk to avoid disk writes and smooth performance.

[BartZorn]

I have been away for a while, but now I have restarted using DVBlink.

I have a dedicated SSD for timeshifting, but I am unable to get DVBlink to use it.

I have added the following line to dvblink_configuration.xml:

<timeshift_path>F:\Timeshift</timeshift_path>

I save the xml file to my desktop. I verified the line is still in the file. I copied the xml file to the installation folder and gave the required permission. Finally, I verified that the line is still in the xml file.

Next I restart the dvblink_server service. The result is that my SSD is not used, and that the timeshift_path line has been removed from the xml file.

What the f**k is going on?

Bart

[BartZorn]

I have been away for a while, but now I have restarted using DVBlink.

I have a dedicated SSD for timeshifting, but I am unable to get DVBlink to use it.

I have added the following line to dvblink_configuration.xml:

<timeshift_path>F:\Timeshift</timeshift_path>

I save the xml file to my desktop. I verified the line is still in the file. I copied the xml file to the installation folder and gave the required permission. Finally, I verified that the line is still in the xml file.

Next I restart the dvblink_server service. The result is that my SSD is not used, and that the timeshift_path line has been removed from the xml file.

What the f**k is going on?

Bart

Because the DVBlogic team saw no reason to respond here, I send them an email. The response was that you have to stop the dvblink_server service *before* you make the edit to the configuration file. I have no idea how they do it, but it seems that the configuration file is a dynamic configuration store of some sort, rather than a text file which is read at startup of the service.

Anyway, it now works as I want it.

Regards,

Bart

[btaroli]

... you have to stop the dvblink_server service *before* you make the edit to the configuration file. I have no idea how they do it, but it seems that the configuration file is a dynamic configuration store of some sort ..

Not really, and this is a fairly common requirement for applications. Thunderbird is another good example. The issue is that the file is READ at startup and WRITTEN during execution (or sometimes just at shutdown). So what’s in the file only matters at start time. And it often gets overwritten at shutdown.

[BartZorn]

... you have to stop the dvblink_server service *before* you make the edit to the configuration file. I have no idea how they do it, but it seems that the configuration file is a dynamic configuration store of some sort ..

Not really, and this is a fairly common requirement for applications. Thunderbird is another good example. The issue is that the file is READ at startup and WRITTEN during execution (or sometimes just at shutdown). So what’s in the file only matters at start time. And it often gets overwritten at shutdown.

Sorry, but to me that is the same thing. Be it fairly common or not, I was very surprised that my configuration file got changed, without any warning or error message whatsoever.

Bart