[support] MakeMKV-RDP container Deprecated


Recommended Posts

  • 4 weeks later...

Couldn't find anything in the thread on this but maybe I missed it. Been using makemkv for a week or so now with zero issues using a single usb blu ray drive. I finally got an external enclosure for my old 5.25" blu ray drive, my intent being to rip 2 disks simultaneously. I had read on the makemkv forum that if you set up single drive mode, you can run multiple instances of the software, however all this does in unraid is select a single drive, and any additional windows bring up that same instance of the program. Is there a way to enable multiple instances of makemkv to run at once?

Link to comment
  • 1 month later...

Anyone get this error when updating? I haven't updated in probably a few years, until now.

 

started connecting
[20200528-11:17:41] [INFO ] lib_mod_log_peer: xrdp_pid=144 connected to X11rdp_pid=50 X11rdp_uid=99 X11rdp_gid=100 client_ip=127.0.0.1 client_port=35522
connected ok
[20200528-11:17:41] [DEBUG] xrdp_mm_connect_chansrv: chansrvconnect successful
[20200528-11:17:41] [DEBUG] returnvalue from xrdp_mm_connect 0
lib_mod_process_message: type 2 len 0
lib_send_client_info:
xrdp_wm_login_mode_changed: login_mode is 3
[20200528-11:17:41] [INFO ] The following channel is allowed: cliprdr (0)
[20200528-11:17:41] [INFO ] The following channel is allowed: rdpsnd (1)
[20200528-11:17:41] [INFO ] The following channel is allowed: rdpdr (2)
[20200528-11:17:41] [DEBUG] The allow channel list now initialized for this session
[20200528-11:17:47] [INFO ] An established connection closed to endpoint: 127.0.0.1:35522 - socket: 8
xrdp_mcs_disconnect - socket closed
[20200528-11:17:47] [DEBUG] xrdp_mm_module_cleanup
[20200528-11:17:47] [INFO ] An established connection closed to endpoint: 109.112.47.46:12148 - socket: 11
[20200528-11:17:47] [INFO ] An established connection closed to endpoint: 109.112.47.46:12148 - socket: 12
xrdp:xrdp_encoder [1551967640]: xrdp_encoder_delete:
[20200528-11:17:47] [ERROR] Listening socket is in wrong state we terminate listener

 

Link to comment

Is there a way I can setup automatic ripping to just a file instead of individual folders with the disk name to make it automatically work with filebot to transfer over the files after renaming? I'm having problems with it reading the folder name and the just reading "title1.mkv" and names it the movie title (1978). Just wondering.

Link to comment
6 hours ago, Nlandis said:

Is there a way I can setup automatic ripping to just a file instead of individual folders with the disk name to make it automatically work with filebot to transfer over the files after renaming? I'm having problems with it reading the folder name and the just reading "title1.mkv" and names it the movie title (1978). Just wondering.

I'm not aware of any automatic ripping in this container. Are you maybe using djoss's container? That one has automatic ripping.

Link to comment
  • 1 month later...

Thanks @saarg, I used your MKV containter for a long time. Thanks for the reference to jlesage's container. I'm using his container now and it's great. There is even a setting to autopull the Beta key on launch. I tried binhex's but could never get it to read my optical drive.

Link to comment
  • 1 month later...
On 3/17/2018 at 8:43 PM, saarg said:

 

Did you also upgrade to 6.5?

There is a permission issue in the latest version and the host permissions doesn't apply in the container. You could try to do a chmod 777 /dev/sr0 and chmod 777 /dev/sg0 and see if that helps. 

Restart the container after. 

this little gem buried deep down in this thread saved me on my r720. thanks @saarg

 

for anyone else doing this, to persist after reboot, i added these quick lines to my go file (in my case it's sr0 and sg3, adjust accordingly)

# Make Optical Disc Drive Accessible
chmod 777 /dev/sr0
chmod 777 /dev/sg3

 

  • Like 1
Link to comment
  • 3 years later...
On 8/15/2020 at 8:22 PM, Cpt. Chaz said:

this little gem buried deep down in this thread saved me on my r720. thanks @saarg

 

for anyone else doing this, to persist after reboot, i added these quick lines to my go file (in my case it's sr0 and sg3, adjust accordingly)

# Make Optical Disc Drive Accessible
chmod 777 /dev/sr0
chmod 777 /dev/sg3

 

Thanks, this is still required in 6.12 and does work. What is/where is "go file" ?

EDIT:
Found it. For the inexperienced user:
Terminal to server
change directory to boot / config ('cd /boot/config')

send 'ls' command to confirm 'go' is listed

then edit the file, for example 'nano go'

Add comment (begins with #) and then parameters as listed above.
Exit and save with Ctrl+X

Reboot server to test.

Edited by OrdinaryButt
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.