Black Hole
May contain traces of nut
Just a suggestion, not being a user, but it might be nice to allow the user to allocate tuners manually.
Yeah, that would be me while watching late at night.if someone comes along and watches one of the recordings then deletes it
But if it's not doing anything then why not put it to some use, instead of leaving it idle?Although the guide update uses up a tuner to update the guide and can take around 10 or 15 minutes,
So there is no problem with doing the above, as the only niggle is already solved.if recordings are taking place and there aren't enough tuners available the guide update is automatically terminated to let the recording take place.
@mike, welcome on board. I should be on commission with Silicondust The frequency to use for the guide data should default to one of the HD Muxes, but the option is available to change to a different frequency, for example if you are on the margins of reception and can't get the HD muxes too well you might want to go for a different frequency. All muxes carry the same guide data. Enjoy.
@Black Cloud @tonylon
I've been playing about with the network share, and have been successfully able to get it working for me, so hopefully this will help.
So give this a try:
* you could use any existing user of course, but maybe best to set a new one with a password not to expire.
- Stop the DvrOnTime service
- Change the permissions for the database to allow users to access it. Go to C:\Program Files\DvrOnTime, right click DvrOnTime.mdf and click Properties, then Security, then Edit… give the Users group Full Control, OK to save and repeat for DvrOnTime_log.ldf
- Now set up a new user* in Windows (e.g. a user called DvrOnTime), set a password, make sure the password is set not to expire and also not to need changing at log-in, add the Administrators and User groups to the new user Members Of.
- Now log in as this new User, navigate to the shared drive, i.e. \\NasBox\DvrOnTime, if a password is required, enter a password and make sure to tick the Remember option. This new user should now be able to access the shared folder, if they can't, then this problem needs to be fixed first.
- Log back in as your normal Administrator user, find the DvrOnTime service, right click it and go to the Log On tab, set to Log on as: This account and enter the new DvrOnTime user name and password, click OK.
- Start the DvrOnTime service, it should start normally but now using this special user. In the DvrOnTime settings, set the shared drive and click Save, this should hopefully succeed and the text file is written to confirm read and write access. Test a recording out.
Let me know how your get on.
The .ts file will be about 2% smaller than the .m2ts file.Both file formats .ts & .m2ts seem to end up about the same size
The HDR-FOX will only play M2TS labelled as .TS, and any software utilities written for the HDR-FOX expect M2TS.The m2ts format was a request from someone as the files were, I think from memory, being processed later in something else which only wanted m2ts files.
Results are in...
I added 5 minutes of padding to the end of 3 back to back shows recorded on E4.
First recording included 5 minutes of second show
Second recording started 5 minutes into second show, and included 5 minutes of third show
Third recording started 5 minutes into third show, and included 5 irrelevant minutes at the end.
I guess that means only one tuner was used.
Yeah, but that doesn't fix the problem where the end of the first show only exists at the beginning of the second recording. Just as it gets exciting, the player stops and you need to access your media files to get the second recording (that's if the recording weren't so long ago that you can still remember that it was back to back with something). Back to back recordings aren't always from the same series - maybe the second recording was an unrelated film. Maybe I watch the film first, then delete it, and there goes the end of the first show. And, I do like to remove the ad breaks automatically, so the end of the first show could be gone before I know it.In your test scenario my preference for single tuner behaviour would be for the 1st and 2nd recordings to start and end at their broadcast times and only the final recording to get the extra 5mins padding time
This is undoubtedly the correct strategy if you are tuner constrained which was the case with VHS recorders and when the humax was being developed 15 years or so ago but the world has moved on and now quad tuners are common and with dvrontime now supporting multiple hdhomeruns it is a chance to do padding properly for back to back programmes.In your test scenario my preference for single tuner behaviour would be for the 1st and 2nd recordings to start and end at their broadcast times and only the final recording to get the extra 5mins padding time. If each recording was requested with different padding times then add whatever the max padding time was to the last recording.
Yes agreed when you have free tuners available. Hopefully dvrontime will allocate recordings across its free tuners and only resort to dropping any padding if it runs out of tuners. I will have 8 tuners to play with if multiple HDHomeruns are supported so I'm not expecting that to ever happen.For the purposes of tuner scheduling each programme should be considered including its start and end padding and if there is any overlap with the preceding programme then another tuner should be allocated, only if there are no free tuners available would you need to consider removing padding
I'm definitely not holding my breath on that one! Unfortunately whatever systems they implement fall apart when they can't get the data right consistently...The lesson to learn is, don't record ITV until they get it fixed. But don't hold your breath, it's been 10 years already.
Something along the lines of schedchk by @MymsMan Monitoring the recording schedule for a variety of issues and attempting to fix them (if not resolved by a human first) using some built in algorithms. Idealy with the addition of an option to send an email with a link in it which then links back into the dvrontime web interface to present the options for the user to make the ultimate decision.If anyone has any suggestions for things they want to see added or changed let me know.
Yes still contact me here or send a message here, I'll check out GitHub as that is a good way to track issues.Thanks for this - I'd just come back to trying it out last week but will update and continue - so far so good.
P.s. is this still the main point of contact for you or are you using github etc?
Using Github will help other Homerun users find you - A Humax forum is not the natural home for Homerun softwareYes still contact me here or send a message here, I'll check out GitHub as that is a good way to track issues.
16:30:57.252 Debug : HdHomeRun command executed: 1250E143 key 3077587.0 set /tuner0/target none
16:30:57.321 Debug : HdHomeRun command executed: 1250E143 key 3077587.0 set /tuner0/channel none
16:30:57.367 Debug : HdHomeRun command executed: 1250E143 key 3077587.0 set /tuner0/lockkey none
16:30:57.427 Debug : HdHomeRun streaming started on new thread
16:30:57.427 Debug : HdHomeRun command executed: discover
16:30:57.502 Information: Streaming stopped on device 1250E143 tuner 0
16:30:57.893 Debug : HdHomeRun command executed: 1250E143 get /sys/features
16:30:57.941 Information: Device found at IP address 192.168.1.33 with ID 1250E143, set to priority 1
16:31:03.984 Error : Could not connect to a tuner on device 1250E143, status code returned , response was HTTP/1.1 503 Service Unavailable
Server: HDHomeRun/1.0
Connection: close
Content-Length: 0
Cache-Control: no-cache
X-HDHomeRun-Error: 807 No Video Data
16:31:03.986 Information: No device was found or no tuners available
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at HdHomeRun.TunerDevice.StopStreaming()
at DvrOnTime.ServicesByFrequency.StopTuner()
at DvrOnTime.Tuning.RetrieveServiceInformationFromFrequencies()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
C:\Program Files\DvrOnTime>