Jump to content

Phoenix Down

Members
  • Content Count

    83
  • Joined

  • Last visited

Community Reputation

12 Good

About Phoenix Down

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Check out this guide: https://hub.shinobi.video/articles/view/DmWIID78VtvEfnf
  2. Sounds like you might be transcoding the video stream, which always requires a ton of CPU power and is just not worth it IMHO. Find out what format video stream your IP cam produces, and then set the video format in Shinobi to match. For me, it's H.264. During active recording, my 8 core CPU uses less than 1% utilization for 2 cameras. In this case, Shinobi is just taking the video streams from the cameras and saving them to disk, which takes very little CPU power.
  3. Right, but it doesn't appear to be working as advertised. Hence taking matters into your own hands
  4. What if you crawl the process tree and kill each child process individually? It's a bit heavy handed, but should take care of any orphaned child processes.
  5. Mount button is grayed out and "Pass Thru" column (and most every column) is just "-". I suppose I need to have a MicroSD card inserted to activate the Pass Thru option?
  6. Good info, thank you! How do you go about marking an unassigned device as pass through? I poked around the UD settings but I'm not seeing anything.
  7. Hi all. I have a SD/MicroSD card reader, and the MicroSD port shows up as its own device under UD, but I never use it. I'd like to hide it in UD. Is this possible?
  8. Good info, thanks I don't think I ever looked at the "-i" switch.
  9. You could write a small Perl script to do it. Maybe something like this: #!/usr/bin/env perl use strict; use warnings; use Carp; use English; # Read the file my $file = "/mnt/user/text/mytestfile.txt"; my $fh; open $fh, "<", $file or croak("\nERROR: Cannot open '$file' for reading: $OS_ERROR\n\n"); my @rawdata = <$fh>; close $fh; # Update each line my @newdata; foreach my $line (@rawdata) { $line =~ s/#FF8C2F/#42ADFA/g; push @newdata, $line; } # Update the file with the updated data open $fh, ">", $file or croak("\nERROR: Cannot open '$file' for writing: $OS_ERROR\n\n"); foreach my $line (@newdata) { print $fh $line; } close $fh;
  10. It's a bit more heavyweight solution, but you can always write your own wrapper that does logging, timeouts, interlocking, and notifications. Then you can run all of your crons using this wrapper.
  11. I seem to recall reading about this particular error and something to do with the "use camera timestamp" settings or something like that. It's been a while.
  12. I hear you, orphaned processes are a pain in the rear. After you send the SIGTERM, do you wait at all before sending SIGKILL?
  13. I had a similar problem, but with scheduled recordings not starting after a day or two. Still no true resolution, but found an accidental workaround. I use the CA Appdata Backup/Restore v2 to back up all of my Docker data. The default behavior is that it turns off the docker while backing up the data then turns them back on. It only takes a few seconds, but effectively restarts the Shinobi docker daily. The schedule recordings have been working fine every day since.
  14. First of all, as I've learned the hard way, support and development for this rclone container is basically dead. Most people have moved on to the rclone plugin, which is actively developed and supported, and its support thread is pretty active. Also, one side effect I found is that doesn't matter what I do, the container writes to the docker image somewhere everytime rclone runs, which wakes up my SSDs (cache pool). With that said, to answer your question: you run it from the container's console. When it gets to this part: Use auto config? * Say Y if not sure * Say N if you are working on a remote or headless machine or Y didn't work y) Yes n) No DO NOT choose "yes". Choose "no" instead, and it will give you a link to Google website to get the access code.