rix
-
Posts
423 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by rix
-
-
3 minutes ago, bar1 said:
can the google photos sync support more then 1 account?
if there is an official way, it should be mentioned on the project page: https://github.com/gilesknap/gphotos-sync
if not, you need to run two separate instances of this container with different names and config folders. this should essentially result in two different containers where you can log into each of your accounts seperately.
-
On 5/15/2020 at 7:20 AM, Flatfire said:
Hey, is there any chance now that freedb is no longer an active service that the CDDB provider be switched to MusicBrainz in ripit? I've tried to figure out how to do it myself but I can't find concrete documentation on ripit either now that the author has left it for dead.
Afaik this is something only ripit can fix. If there is another tool that can be included instead of ripit I will consider migrating over.
What I'd need is the tools name and how it needs to be called.
-
2 minutes ago, CSeK said:
That cmd works for me within user scripts. Just had an update yesterday to user scripts though. Didn't test before.
For me too, have just tested it. Enjoy the container!
-
18 hours ago, rguinn said:
@rixwould you be able to share you users script for GooglePhoto Sync mine is not working I sure I doing it wrong new to user scripts
Sure:
#!/bin/bash docker exec GooglePhotosSync gphotos-sync /storage
but it does not seem to work (running the command outside user scripts does!).
I will try to add a cron entry through container variables, so everyone can set this up by themselves.
-
On 4/14/2020 at 5:42 PM, codebone said:
Hey rix, thanks for developing all the containers and continuing to support them, and helping manage the COVID-19 crisis wherever you are.
I am using the ripper container, and I get very mixed results with it. I have run probably 300 DVDs/Blurays through the jlesage/makemkv container in the past few weeks, since I am now sitting at my home desk all day. Many of the same discs I have attempted through Ripper, but the type is not detected correctly, or the rip is unsuccessful. For example, a bluray disc is detected, but immediately ejected with a finished in the log, but no data is created.
*** Running /etc/my_init.d/ripper.sh... Using MakeMKV beta key: T-UWwbYn781f1gjZcH5NOsJkGgWHnUkQsr2IduoSJ8sssNXOqclsWhowNWTclkBjHIMH 12.04.2020 04:42:25 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds. 12.04.2020 04:45:38 : Data-Disk detected: Saving ISO 12.04.2020 04:45:51 : Done! Ejecting Disk 12.04.2020 04:46:58 : Disk tray open 12.04.2020 04:48:00 : Disk tray open 12.04.2020 04:49:02 : Disk tray open 12.04.2020 04:50:05 : Disk tray open 12.04.2020 04:51:07 : Disk tray open 12.04.2020 04:52:09 : Disk tray open 12.04.2020 04:53:11 : Disk tray open 12.04.2020 04:54:13 : Disk tray open 12.04.2020 04:55:15 : Disk tray open 12.04.2020 04:56:17 : Disk tray open 12.04.2020 04:57:20 : Disk tray open 12.04.2020 04:58:23 : Disk tray open 12.04.2020 04:59:25 : Disc still loading 12.04.2020 05:00:33 : BluRay detected: Saving MKV '/out/Ripper/BluRay/BRAVE' -> '/out/Ripper/BluRay/finished/' 12.04.2020 05:00:37 : Done! Ejecting Disk 12.04.2020 05:01:42 : Disk tray open
A small datadisk I did want, did rip successfully. It seems to have no issues making an .iso of discs from SeattleFilmWorks (defunct photo processing company, that my inlaws have dozens of discs from that they want to backup the pictures from).
Audio disks generally have been detected as data, and fail to rip.
Is there extra debug information I could find somewhere, either to present here, or to attempt digging in myself? I appreciate any support you might be able to offer.
Run
makemkvcon -r --cache=1 info disc:9999 | grep DRV:0inside the container. This will help you modify ripper.sh accordingly.
-
On 4/25/2020 at 12:06 AM, EmilionDK said:
On 4/21/2020 at 8:58 PM, constellation said:Any advice on this? Not able to make the automation work even with the official docker. Keep getting bad gateway if I enable autojoin.
Due to inactivity on my side and no further time to support this I have now removed Synclounge from my repos.
-
On 5/3/2020 at 6:32 AM, administrator said:
Are the extra parameters correct? Did you try swapping the sr1 and sr0?
Have you tried just passing through /dev/sr1 as /dev/sr1 and modifying the ripper.sh for your second container to point to /dev/sr1 ? That should work. Have just one optical drive, hence I cannot test this.
-
Hey guys. I am doing fine and am hereby back again.
The last few weeks have made me aware of what matters most. I will stop supporting tools that I do not use my own and have since removed the following repos, images and their respective templates.
From this day forth I will only be able to help you with
- RSScrawler
- Ripper
- GoogleMusicManager
- MyJDApi
-
On 4/5/2020 at 5:42 AM, zachrybaker said:
Sounds like you have the exact same questions I do. The lack of response here should tell us something, I guess. Either @rix is busy, doesn't know, doesn't care. Bummer.
Nice attitude. Apart from that, I was abroad and now am managing the COVID-19 thing at work. Lack of responsiveness for another few weeks included.
I will take a look at your questions, if there is time.
-
On 1/8/2020 at 6:02 PM, Squazz said:
Just to be sure, did you try setting up a new instance from scratch, or did you log into an existing? Logging into an existing instance works for me, but new ones can't be created
Havent tried that, but if you can reproduce this issue, it sounds like its on googles end
-
On 12/31/2019 at 6:09 PM, CyberFunk said:
Hi,
Is there a way to change the port for DNSCrypt? I have Pi-Hole installed and listening on port 53 and need DNSCrypt on another port. However, when I go into DNSCrypt and add in Host Port 1 (5300 / TCP) and Host Port 2 (5300/UDP) it doesn't seem to take into effect and sticks to port 53.
Any idea how I can get DNSCrypt to pick up port 5300?
Have you edited the toml file?
-
On 12/27/2019 at 12:20 PM, Squazz said:
I'm trying to get the Google Play Music Manager docker working.
Installing the image and logging in the first time works like a charm.
But after logging in, I get the following message:
When looking in the log, I see the following:
Looking in the log it says: 2019-12-27 11:43:03,245 +0100 ERROR TId 0x14b62f5df740 Error: Domain (1) code (400) label (Bad Request) url (https://accounts.google.com/o/oauth2/[email protected]) [ExtendedWebPage.cpp:48 ExtendedWebPage::extension()]
If I navigate to the URL, I get the following message.
Can somebody else verify that the docker image is still functioning?
Am I doing something wrong?
Its working completely fine on my part.
-
3 minutes ago, Arndroid said:
Thanks a ton @rix for your support! Also to Squid of course!
-e USER=USERNAME \ -e PASS=PASSWORD \ -e DEVICE=DEVICENAME \
Adding these variables to my docker template made it work. (Instead of using the Credentials variable that is coming with it by default.)
Works wonders now with Organizr v2.
Dang, I forgot updating the template when removing the Credentials variable. This is fixed now.
-
1
-
-
12 minutes ago, Arndroid said:
No just upper and lower case and some numbers, no special characters.
Something like:
[email protected] and AsD1345QWio8Hm, that would have been my first question also. Thanks Squid!
When passing through Variables to docker those quotes should be optional.
Please try setting this up as specified on github:
docker run -d \ --name="MyJD-API" \ -p port:8080 \ -v /path/to/config/:/config:rw \ -e USER=USERNAME \ -e PASS=PASSWORD \ -e DEVICE=DEVICENAME \ rix1337/docker-myjd-api
The backslashes are optional, if you use just one line for the command. Also DEVICE is optional if you only run one JDownloader.
Please do the following:
- Run JDownloader
- Ensure the JDownloader is actively conencted to my JDownloader (verify in the settings)
-
Run the container using this command:
docker run -d --name="MyJD-API" -p port:8080 -v /path/to/config/:/config:rw -e USER=Arndroid@domain.ltd -e PASS=AsD1345QWio8 rix1337/docker-myjd-api
This should work. If it does not, please post the output of you container's log (there might be something wrong with my code after all).
-
1
-
Just now, shidraconis said:
I updated the ripper.sh file, restarted the docker, and waited a few minutes to see if tmp files started to be created. Only 1 did, so I waited a little longer to see if any more appeared. Still the 1 there. I think that modification worked.
Thanks for helping me debug this - I pushed these changes:
https://github.com/rix1337/docker-ripper/commit/a3470835533b126c305e4765edb879b2669aec7d -
9 minutes ago, shidraconis said:
I ran the command you provided and it doesn't delete anything. I personally to clear the tmp files out ran a "rm -r *.tmp" but I don't know if this is applicable here.
That explains why the files are still there.
Please replace the line seen above with these lines in your ripper.sh then report back:
# delete MakeMKV temp files cwd=$(pwd) cd /tmp rm -r *.tmp cd $ -
3 minutes ago, shidraconis said:
Thanks for trying, I'll see if I can get a script to run in the userscripts plugin to delete them. Either way here's the output of an ls in the tmp folder.
This looks expected..
I have added this command, that should delete all the .tmp files in the folder:
find /tmp/ -name "*.tmp" -type f -delete
Could you please enter that one in the container shell and post the results.. might be an error displayed or it working perfectly.. either would help me get to the core of this
-
Just now, shidraconis said:
I deleted the ripper.sh and rebooted the docker afterwards which did create the new ripper.sh file like you said, and .tmp files are being created still and not deleting.
Then there is not much I can do about this without further info.
Could you please send me the output of a ls command in the /tmp folder?
-
I just started having issues with Quicksync on 6.8 (it worked smoothely on 6.7.2):
Any help would be appreciated
-
9 hours ago, shidraconis said:
I did update and it doesn't appear to be deleting the files, the temp files are being created even when the system isn't ripping anything just sitting idle.
Yes, because once you started the image it places the ripper.sh on your disk and will not overwrite it. Delete your ripper.sh then check again.
-
This requires you to remove your custom ripper.sh
Or just add these lines to the file: https://github.com/rix1337/docker-ripper/commit/92cf8f62bb6d430ca07358ea21743b98022d8e68
-
On 10/23/2019 at 6:34 AM, shidraconis said:
I know it was mentioned before that the docker size for Ripper was growing large without doing anything. Mine is consistently filling the /tmp directory with a bunch of "MakeMKV-0x78a1-2.tmp, MakeMKV-0x78a2-2.tmp, and so on every minute or so, could be less. Each one is 532kb in size, I have to almost every day go in and run a "rm -r *.tmp" to clear them out otherwise the docker image fills up which it has already done to me once. I have implemented the --log-opt max-size=50m but I don't think that is what this is about.
Thanks for investigating. I have updated the included ripper.sh which will now delete all .tmp files located at /tmp minutely.
Docker Image should update within the next hour.
-
Has anyone else had issues with Intel Quicksync hardware transcoding running the 6.8 rc series?
Streams have stopped working for my users and if they start at all, they are extremely blocky and unwatchable. -
On 10/17/2019 at 1:19 AM, txpenguin said:
Thank you. Yes - this fixed the issue.
I'm curious though - why was it trying to upgrade to a -beta version? Is there a way to restrict to only stable releases?
Not currently, The script always looks for the latest release on github.
This probably could be solved - but not actively by me. I will however integrate a Pull Request that does this, if one appears.
[support] rix's Docker Repository
in Docker Containers
Posted
Ensure you do the initial setup exactly as described here. https://github.com/rix1337/docker-gphotos-sync
Your error messages indicate you either did not pass through the config dir as described or did not provide the secrets as required. Also ensure you run the command with the correct options.