rix

Community Developer
  • Posts

    391
  • Joined

1 Follower

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

2862 profile views

rix's Achievements

Contributor

Contributor (5/14)

24

Reputation

  1. Hi all, after some struggles I have migrated from dockerhub automated builds (now deprecated) to github actions. Regarding Ripper you will now find ppa builds under the latest tag. These are the official way to go, the image is slim and the build streamlined. Alternatively you will find selfmade builds under versioned tags (currently 1.16.4). These are built from source, so they should appear quicker than the ppa builds. The image however is almost double the size and takes much longer to build. This should satisfy both types of users: those who are ready to pay for MakeMKV and bring some patience and those wo do not and have more free space on their docker host. 😄
  2. The latest build avaiable is 5 weeks old. Please check https://launchpad.net/~heyarje/+archive/ubuntu/makemkv-beta I will update, once a new version is available at the ppa. Use a valid license key in the meantime.
  3. You should lay out in detail every step you have taken to set your container up. Please include screenshots of your Docker run, and the volumes you have set up. Ripping audio is not done by Makemkv.
  4. This has been answered https://github.com/rix1337/docker-ripper/issues/75 Buy a license key or wait.
  5. Also with the ppa setup you have reduced the image to 1/3 the original size. Thanks
  6. That has always been the case if ripper.sh was changed.
  7. Thanks, that PR was indeed helpful. Using ppa to install makemkv will shorten the build time of this image. I have done a minor edit, removing the setup through the install.sh entirely and made a minor edit to the readme. Thanks
  8. Go ahead with a pull request I initially set this project up using abcd but it broke a short while after. Ripit has been a headache to support, so I'll gladly replace it.
  9. Thats a bug - Version 10.0.2 will be out shortly fixing the underlying issue. Please open a github issue next time, since the process there is much more streamlined than a forum post.
  10. Please discuss here https://github.com/rix1337/docker-ripper/issues/64
  11. Hi, this lovely plugin is central to my build not overheating, but it just did. My parity check was not paused, so my parity drive heated up to 66°C... According to the logs and web UI there is a syntax error in the current version: Also this option always reverts to "No" ("Nein" as translated) - no notifications can be enabled.. Please fix
  12. I have found out why my second fan never ramps up. Turning off fans is a really bad Idea since the second one will not be able to start again. How do I disable the "turn of fans" behaviour from the script so my fans will always run at their lowest value?
  13. Hi bonienl, I have switched to a modded DS380 case which fixed the airflow mostly. One issue remains. When moving a lot of files or during parity checks drive temp goes way above 40°C. Most of the time running my fans at 600rpm keeps cpu and drives below 35°C and is super silent, but i need to automatically turn up fan speed when drive temps are rising. Sadly the autofan plugin works not as I would want it to: - my mainboard has 2x 3-pin fan headers available (one cpu, one case fan) - the 2x array fans are connected to the secondary fan header - when setting up autofan, my cpu fan completely stops and will not ramp up again - until I remove the plugin and restart - the array fans never drop to 600rpm but instead stay at around 690 when the plugin is set up Please advise how to set this up properly. I have found no way to create settings for both fan headers simultaneosly - which should ensure the cpu fan keeps running. Currently my only workaround is to bind the array fan speed to the cpu temp in the BIOS. This will work only if file temps are related to heavy CPU load (which is not always the case). Using the plugin is my much prefered method.
  14. Thanks for the Info, I have updated the Readme accordingly so others dont have to struggle.
  15. Then you should add the line pointing it to /usr/local/bin/ccextractor. I have also updated the Readme to reflect this. I have since fixed the template. sr0 should now be passed through as a device by default. Thanks for the heads up. Also please consider donating at https://github.com/sponsors/rix1337 if you are a regular user of this image.