The recording database design must be fixed!

Post your questions about DVBLink products running on Windows platform here!

The recording database design must be fixed!

Postby politby » Mon Dec 19, 2016 9:12 pm

So all it takes for my recordings to disappear from the index is one restart of the dvblink server before the network share my recordings are saved to becomes available. For example after a power failure when Windows boots faster than my NAS.

The recording location is reset to the default on C: and the index is empty. The server should never change this on its own initiative. If the recording location is unavailable, it's most likely a temporary issue the user is already working on, and dumbly resetting the location is creating another even more serious problem. And the repair function does nothing at all, at least not for me.

Using an SQL database for this seems to be completely unnecessary - would not a simple xml file stored with the recordings do?

Please fix this. Many thanks in advance!
politby
 
Posts: 122
Joined: Tue May 05, 2009 1:29 pm
Location: N59.45817 E18.39345


Re: The recording database design must be fixed!

Postby the_man » Tue Dec 20, 2016 10:43 am

Usage of the network paths for recordings are really not trivial. And in case if that path are not reachable server takes a default path for next recordings.
PS. I may check your current database, may be i will be able to restore current recordings. If you need so (?)
NETGEAR RNDU2000; Synology DS112j, DS 212j, DS213+, DS 712+; Western Digital WD ex2; Asustor AS3, RPI2 ...
PCTV 460,461e,292e; TT 4400, 4650CI;DVBSKy S960; DD octopus net; Inverto sat2ip multibox; TBS DVB-C ...
the_man
 
Posts: 4664
Joined: Mon Dec 02, 2013 1:11 pm

Re: The recording database design must be fixed!

Postby politby » Wed Dec 21, 2016 4:39 pm

the_man wrote:Usage of the network paths for recordings are really not trivial. And in case if that path are not reachable server takes a default path for next recordings.
PS. I may check your current database, may be i will be able to restore current recordings. If you need so (?)


I have already restored - sort of - using the dvblinkrecordingsimporter tool.

I agree recording to a network path may be iffy but the exact same thing happens if I record to a local hard drive and simulate a disk failure by pulling the hotswap drive out. The recording database is instantly borked and there is no way to restore it other than perhaps from a backup.

Am I the only one suffering from this problem - i.e. am I ignoring something obvious?
politby
 
Posts: 122
Joined: Tue May 05, 2009 1:29 pm
Location: N59.45817 E18.39345

Re: The recording database design must be fixed!

Postby Montoya » Mon Jan 02, 2017 8:34 pm

politby wrote:Am I the only one suffering from this problem - i.e. am I ignoring something obvious?


No, I also had a f*cked up database, when I temporarily removed my external drive where DVB recordings where stored and days later I noticed that all my scheduled recordings where on the default path........

A warning notice from the DVB software when it reverted back to the default path should have been issued :!:
Not doing so screwed my database which I only noticed after a couple of days.....

It should be easy to built in some options into the DVBLink server software, to send a message to the Win10 notification center, when installed on Win10, if some error occurs within DVBLink.....
DVBLink server 6.0.0 build14499, DVBLink TVSource 6.0.0 build14061, DVBLink for IPTV build 13107
Kodi 18.0-ALPHA1 Git:20171024-2f0fd5c, Win10 Pro x64 1709 build16299.19
Montoya
 
Posts: 111
Joined: Fri Apr 29, 2016 6:06 pm

Re: The recording database design must be fixed!

Postby politby » Tue Jan 10, 2017 10:13 am

Okay, it happened again. What is the solution to this? The "repair database" function is useless.

I have no problem with recording to a local drive but I need to keep the recording library on my network storage for space reasons. I could easily set up an automove from the local drive to the NAS but DVBlink is not able to separate recording and storage of recordings.

We really need an option to store recording metadata with the recordings like WMC does. Oberon, can you please comment on this?
politby
 
Posts: 122
Joined: Tue May 05, 2009 1:29 pm
Location: N59.45817 E18.39345

Re: The recording database design must be fixed!

Postby Videonisse » Wed Jan 11, 2017 7:29 pm

+1 (or the recording database solution must be much more reliable)
Win 7 64-bit SP1, Intel i5-3570K 3,4GHz HD 4000 Graphics, 6GB, TBS 6984 S2 Quad,TBS 6280 T2 Dual
DVBLink 5.5.0 Connect & TVSource (mc_recorder), CD S Thor 0.8W,FTA Aastra 19.2E, S FTA T2, ACAMD 0.6.2
Clients iPhone 4S 5S 6S, iPad2 iOS 9,Win 7 PCs
Videonisse
 
Posts: 572
Joined: Mon Nov 21, 2011 10:29 pm
Location: Stocholm, sweden

Re: The recording database design must be fixed!

Postby Muppets4 » Sun May 21, 2017 10:06 pm

I just encountered this today too. This is very bad. It makes the software far from reliable. Any updates?
HDHomerun 4 channel tuner
Muppets4
 
Posts: 109
Joined: Sun Feb 05, 2012 11:15 am

Re: The recording database design must be fixed!

Postby knekkert » Mon May 22, 2017 10:48 am

+1

Sent fra min SM-G900F via Tapatalk
knekkert
 
Posts: 46
Joined: Thu Dec 29, 2011 8:21 am


Return to DVBLink Server on Windows platform

Who is online

Users browsing this forum: No registered users and 1 guest