sota

Members
  • Posts

    661
  • Joined

Everything posted by sota

  1. probably going to start version/revision updates in the next couple of days. that should be fun.
  2. still at the 2XCH, and a monster amount of some of the sh!tcoins. farms haven't dropped any more drives lately. I'm not worried about them in the garage and the cold. in fact, they might keep the entire garage warmer this winter.
  3. Let me start with, I am changing disks out frequently without powering down, and this "issue" has cropped up before, with no solution presented. I currently have a share that appears for a disk that's no longer connected to the system. Further, if I attempt to reconnect the disk, the logs will show something about duplicate UUID being present, and refuse to even show the drive in UD. I need to find out where UD stores attached disk info, in the hopes that I can edit something that'll make the phantom share/drive disappear, so it can be reattached, without having to reboot the box. Thanks!
  4. *sigh* looks like 2 more disks on farm1 and 1 disk on farm2 might be in trouble.
  5. and since i'm not planning on doing any more plotting, guess I'm just going to have to live with 830 instead of 866. at least for the time being.
  6. well, shit. just lost a drive in farm1. 36 plots, poof.
  7. aye the issue is the decoding/extracting frames takes a brutally long time. each storage drive is: 4 cameras (currently. more to come hopefully) 13 days (roughly) 24/7 recording means I need to extract 60*60*24*13*4=4,492,800 frames total. then recombine them back into an MP4 @ 30fps. I'm fine with leaving the encoding part as CPU based, as that's usually running about 15fps, and once I have all the extracted frames I can easily batch process that to run. That'd take 83.2 hours, or just about 3.5 days continuous, to process. I'm fine with that part. it's the extracting that takes over a week to do. Yea I know shinobi does timelapse, but it sucks at 6 seconds per frame, so it's easy to miss things going by the cameras. And I want the 1fps files so I can delete the "useless" footage, as I go through and tag only the time stamps that have interesting things going on in front of the cameras, but still have a useful continuity file if I ever needed this stuff as evidence.
  8. did you notice the quality issues when encoding to a video stream? or when decoding to still images? I need to post-process a buttload of security footage, and yank 1 frame per second, to then later re-encode that back as a video file for quick scanning and archival processes. I can live with the slower encode times via CPU, but the decode times for each file is pathetic, and that's a problem. I can run up to 4 in parallel right now but that doesn't help the fact it's still days to extract frames from all the footage.
  9. Got some pretty intensive video decode/encode processes I want to do here. thinking about installing this AMD FirePro graphics card, with the hopes of passing it through to a VM to run these FFMPEG tasks quicker.
  10. I'm happily running along on my pair of E5-1230 processor based machines, and 866 plots spread across them. you're reminding me I need to take a backup of the machines soon.
  11. https://chiaforksblockchain.com/ that'll help. also chiadoge is now cryptodoge, with a hard fork of the blockchain.
  12. hang on, I'll have something for you...
  13. looks like shamrock has shit the bed.
  14. and it looks like the 3rd one works. trying now to get everything into their final positions.
  15. another board is on its way. hopefully this one works.
  16. and, I think they sent me another bad board. this one throws an immediate memory error (1 repeating beep) no matter what chips I toss in it.
  17. don't ask how, but i'm farming all 27 on a single machine right now, and it's not overloaded, and it's winning on various forks. Had to move FARM2 to FARM1 for a bit, as I have repair work to do on the former, and it'll be down for a couple hours at least.
  18. Ok. while I think that forkfarmer thing is really cool, I'm going to now recommend holding off using it for a bit. It's got an issue where if you have enough forks running and it viewing them it'll crush the CPU every 60 seconds. writer is working on the problem.
  19. right-click on each one that's not running, and select start. it doesn't start them automatically, although we were working on that a bit.
  20. but that's just a title field being blank. interesting. also, I changed my one image above.
  21. I think it's getting there. I'd suggested the following... we'll see how interested he is in doing it. problem will be the statistics will require a 3D table to be effective (coin * entry * values. 27 * 8640 * 4... if i'm right).
  22. how are you starting your forks? GUI? command line? if the latter, how are you solving the problem of, any started fork process will be under the cmd process, and if you kill CMD, you kill everything?
  23. probably not. he's about to post 0.8 to git in a bit. I've been chatting with him on discord, working on some of the forks.