I've been a MP1 user for a very long time. I had been using Argus for OTA ATSC recording and viewing which has been flawless. However, with Argus development and support stopping some time ago and the product istelf dying on the vine, I decided to switch to TV-Server a couple of weeks ago.
I got things set up pretty easily. System is:
When I looked at the TV-Server log, it looks like the hang up is it has to try twice to delete the old timeshift TS files before it moves on and starts the new timeshift (deleting file > many seconds pass > deleting file > success). This is with full rights to the timeshift folder, and having tried locating the timeshift folder both on the server and on the machine where TV-Server is running (no difference). It seems like maybe the client isn't releasing it's lock on the timeshift file as fast as the TV-Server is trying to clean it up.
I will send up some logs shortly (it's in use at the moment).
I got things set up pretty easily. System is:
- Client (MP 1.24 on Win 7 x64 on an older dual core box) talking fine with the TV-Server (on another Win 7 x64 quad core VM in the basement).
- Recordings share and the MySQL database server is on a Windows Server (third machine), as was the timeshift share (initially).
- Network is giagbit ethernet. IP's are static.
- Shares are referred to by IP in UNC addresses on both client and server.
- Antivirus exclusions in place for the shares, client and server programs and data, and the MySQL database.
- No windows firewalls are enabled.
- Client has multi-seat UNC paths enabled and set in TV advanced settings.
- Tuners are two HDHomeRun HDHR4-2.
When I looked at the TV-Server log, it looks like the hang up is it has to try twice to delete the old timeshift TS files before it moves on and starts the new timeshift (deleting file > many seconds pass > deleting file > success). This is with full rights to the timeshift folder, and having tried locating the timeshift folder both on the server and on the machine where TV-Server is running (no difference). It seems like maybe the client isn't releasing it's lock on the timeshift file as fast as the TV-Server is trying to clean it up.
I will send up some logs shortly (it's in use at the moment).
Last edited: