50%
As for identifying a corrupt file, all you have to do is move candidate files out of My Video. That's easy on the command line (webshell): "mv" (and will be very quick so long as you don't move files outside their own file system).
cd into /mnt/hd2/My\ Video
Identify your recordings (ls)...
...and installed the fan package I hope!
Is this regardless of the population of recordings you have?
It seems to me there is a corrupt file in your media library.
The point is we're not looking over your shoulder and can't see what you're seeing but not noticing. The screen grabs in Luke's post should give you the idea. You are not disclosing details such as programme names either. It all matters (or might matter). Please post the information...
...but I can't find it.
Try something very simple: make a short recording, decrypt it, set a couple of bookmarks, crop it. Document and report every stage so we can see the details – things you might not consider relevant. Even an unusual character in the name of a recording can trigger a bug.
I'm not sure what the common usage is – the tools were created by the various enthusiasts on the back of the CF framework and released on a take-it-or-leave-it basis. Playback of cropped files is sometimes problematic, so I know a fair number of users gave up with cropping and just use the...
What we're actually doing is running ad-detection on-the-fly, during recording and not as a separate process, and then just setting a post-advert bookmark for manual skip.
WebIF >> Settings >> Setttings for detectads package
I think you should be warned: I realise you're toying with these facilities for the first time, but "crop" (for example) is a blunt instrument. Sure, it cuts&splices the video file at strategic points (i-frames), but it does not patch up the .nts sidecar file – which contains time index...
Is that after a reasonable time for processing, or immediately?
Assuming the latter, I have seen processing errors like this (other situations) and IIRC it's the result of some bug, but trying to find the relevant report might be tricky...
It can, with tunefix.
Agreed it's not always reliable, don't know why. auto-schedule-restore should detect an empty schedule post-reboot and use that to trigger restoration of the most recent backup (and reboot itself in the process). It is vital never to have an empty schedule deliberately...
192.0.2.100 is the factory default IP address for Ethernet (192.0.2.200 for WiFi). It will also default if a DHCP request times out. It sounds to me like you are not setting the manual IP address correctly (either that or the hardware is faulty).
The easy way to configure Ethernet is to apply...
Unusual propagation conditions.
Some reason you're doing all this manually instead of fixing it with a reboot? Restoring User Settings after Restore Factory Defaults
50%
As for identifying a corrupt file, all you have to do is move candidate files out of My Video. That's easy on the command line (webshell): "mv" (and will be very quick so long as you don't move files outside their own file system).
cd into /mnt/hd2/My\ Video
Identify your recordings (ls)...
...and installed the fan package I hope!
Is this regardless of the population of recordings you have?
It seems to me there is a corrupt file in your media library.
The point is we're not looking over your shoulder and can't see what you're seeing but not noticing. The screen grabs in Luke's post should give you the idea. You are not disclosing details such as programme names either. It all matters (or might matter). Please post the information...
...but I can't find it.
Try something very simple: make a short recording, decrypt it, set a couple of bookmarks, crop it. Document and report every stage so we can see the details – things you might not consider relevant. Even an unusual character in the name of a recording can trigger a bug.
I'm not sure what the common usage is – the tools were created by the various enthusiasts on the back of the CF framework and released on a take-it-or-leave-it basis. Playback of cropped files is sometimes problematic, so I know a fair number of users gave up with cropping and just use the...
What we're actually doing is running ad-detection on-the-fly, during recording and not as a separate process, and then just setting a post-advert bookmark for manual skip.
WebIF >> Settings >> Setttings for detectads package
I think you should be warned: I realise you're toying with these facilities for the first time, but "crop" (for example) is a blunt instrument. Sure, it cuts&splices the video file at strategic points (i-frames), but it does not patch up the .nts sidecar file – which contains time index...
Is that after a reasonable time for processing, or immediately?
Assuming the latter, I have seen processing errors like this (other situations) and IIRC it's the result of some bug, but trying to find the relevant report might be tricky...
It can, with tunefix.
Agreed it's not always reliable, don't know why. auto-schedule-restore should detect an empty schedule post-reboot and use that to trigger restoration of the most recent backup (and reboot itself in the process). It is vital never to have an empty schedule deliberately...
192.0.2.100 is the factory default IP address for Ethernet (192.0.2.200 for WiFi). It will also default if a DHCP request times out. It sounds to me like you are not setting the manual IP address correctly (either that or the hardware is faulty).
The easy way to configure Ethernet is to apply...
Unusual propagation conditions.
Some reason you're doing all this manually instead of fixing it with a reboot? Restoring User Settings after Restore Factory Defaults
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.