[support] rix's Docker Repository


rix

Recommended Posts

Hi

 

I'm trying to rip a DVD using Ripper (fantastic container btw) and I'm having the same issue:

/mnt/user/appdata/ripper/Ripper.log:

MSG:1005,0,1,"MakeMKV v1.16.3 linux(x64-release) started","%1 started","MakeMKV v1.16.3 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,2,999,1,"BD-RE HL-DT-ST BD-RE  BH16NS40 1.00","STUDIO_ONE_PAL","/dev/sr0"
DRV:1,256,999,0,"","",""
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5021,131332,1,"This application version is too old.  Please download the latest version at http://www.makemkv.com/ or enter a registration key to continue using the current version.","This application version is too old.  Please download the latest version at %1 or enter a registration key to continue using the current version.","http://www.makemkv.com/"

Docker container log extract:

*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
Found settings.conf. Replacing beta key file.
27.07.2021 09:38:05 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
27.07.2021 09:38:09 : DVD detected: Saving MKV
renamed '/out/Ripper/DVD/STUDIO_ONE_PAL' -> '/out/Ripper/DVD/finished/'
27.07.2021 09:38:10 : Done! Ejecting Disk

 

I did buy a MakeMKV key and pasted in /mnt/user/appdata/ripper/settings.conf:

app_Key = "M-yXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_wpR2sl1"

 

I also restarted the docker container and checked inside the container that the settings.conf was grabbed by /etc/my_init.d/ripper.sh:

root@Tower:~# docker exec -i -t Ripper bash
root@Tower:/# ls -al /root/.MakeMKV/
total 12
drwxr-xr-x 1 root root   82 Jul 27 09:26 .
drwx------ 1 root root   92 Jul 27 09:09 ..
-rw-rw-rw- 1 root root 2048 Jul 27 09:17 _private_data.tar
-rw-r--r-- 1 root root   81 Jul 27 09:17 settings.conf
-rw-rw-rw- 1 root root  194 Jul 27 09:19 update.conf

 

I can't figure out why MakeMKV is still not working (it was working with this DVD a few weeks ago).

Any idea?

  • Like 1
Link to comment

@rix I am having the same issue as @Guillaurent above. I have a valid MakeMKV key entered in the settings.conf and the latest docker image and am still receiving the "application is too old" message from MakeMKV. Is this an issue with MakeMKV checking the keys validity, or with the mechanism that supplies the key to MakeMKV?

Link to comment

Hi,

I am fairly new to all of this so please bare with me :)

I am trying to rip a CD (and i have tried different ones...) and after some errors on the file structure (wrong directory) - i finally got ripper to do the following:

*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
27.07.2021 19:47:39 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
27.07.2021 19:47:39 : Disk tray open
27.07.2021 19:48:51 : CD detected: Saving MP3 and FLAC
27.07.2021 19:48:51 : CD detected: Saving MP3 and FLAC
27.07.2021 19:48:51 : Done! Ejecting Disk
27.07.2021 19:49:53 : Disk tray open

But when i access the folder in which it should be saved...there is nothing there...what am i doing wrong?

Edited by Zeze21
New developments
Link to comment
9 hours ago, metalchad said:

@rix I am having the same issue as @Guillaurent above. I have a valid MakeMKV key entered in the settings.conf and the latest docker image and am still receiving the "application is too old" message from MakeMKV. Is this an issue with MakeMKV checking the keys validity, or with the mechanism that supplies the key to MakeMKV?

I did some testing and I don't think it checks anyting online: I tried installing a brand new instance with Network set as none and I'm having the same issue (with or without the key entered).

Link to comment
Posted (edited)
1 hour ago, Guillaurent said:

I did some testing and I don't think it checks anyting online: I tried installing a brand new instance with Network set as none and I'm having the same issue (with or without the key entered).

 

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.

 

7 hours ago, Zeze21 said:

Hi,

I am fairly new to all of this so please bare with me :)

I am trying to rip a CD (and i have tried different ones...) and after some errors on the file structure (wrong directory) - i finally got ripper to do the following:



*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
27.07.2021 19:47:39 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
27.07.2021 19:47:39 : Disk tray open
27.07.2021 19:48:51 : CD detected: Saving MP3 and FLAC
27.07.2021 19:48:51 : CD detected: Saving MP3 and FLAC
27.07.2021 19:48:51 : Done! Ejecting Disk
27.07.2021 19:49:53 : Disk tray open

But when i access the folder in which it should be saved...there is nothing there...what am i doing wrong?

 

Ripping audio is not done by Makemkv.

Edited by rix
Link to comment
2 hours ago, rix said:

 

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.

 

Here is what I've just tested.

 

First, I removed everything related to ripper from my system (Docker containers, appdata folders and /out directory):

1503047377_00remove.jpg.2dfe94858d0713882d6c70854f7e6e84.jpg

 

Then, I reinstalled Ripper from CA:

1597311988_01search.jpg.ae2aaab670e27e38619bcb38d7b882de.jpg

 

For the first test, I've put the Network Type to None and changed the Output Dir:

215552901_02install.jpg.b17b0a2cbec0c901ccb822af6a811e4a.jpg

 

Install log:

662293870_03installlog.thumb.gif.2459c30566e1a1e4a4992d2093bd8415.gif

 

Start log:

1142632059_04startlog.gif.88d82c8d079d7277de444456d6199c40.gif

 

I inserted a DVD and:

251525371_05defaultriplog.gif.dd53fe907805023d5738a18e226a5fa9.gif

863717422_06defaultRipper_log.png.77425375dd121b7ce6c939d950608d8c.png

 

For the second test, I left the Network Type to None and added my MakeMKV key to settings.conf:

1233427430_07settings_conf.png.43138a1d34ce89f5ed40954b9220af4a.png

And restarted the container:

886920171_08restart.png.95a48debb76246de8cf96992d253e942.png

 

And re-inserted the DVD:

1138240731_09keylog.png.937fb830e39ea0d97531eecfb7cd395c.png

793677991_10keyRipper_log.png.a13d0fd370eb12cf141860a9a26c0a65.png

 

For the third and last test, I changed the Network Type to Host (as default):

865821418_11edit.png.3d22475e08f2d59159f9f44290c49961.png

 

1044250996_12networkhost.png.b22ce96aa4c4b51be7b79dd29d8b0097.png

 

25382998_13edited.thumb.png.68892be93e64d82cdf890387d451d611.png

 

And re-re-inserted the DVD:

1703333327_09keynetworklog.png.1b093b2bbce19f3ca6ab92d317178aee.png

1676596987_10keynetworkRipper_log.png.eff9191ad732aaa656f3588db68193ba.png

 

As you can see, I didn't do anything fancy. The last test should be the same as a default install with the MakeMKV key in settings.conf.

 

Hope this helps.

00 remove.jpg

01 search.jpg

02 install.jpg

03 install log.gif

04 start log.gif

09 key log.png

Link to comment

@rix @Guillaurent

 

I seem to have resolved my issue, it seems the docker isn't bringing in the settings.conf as expected, thus the key not being used.

 

I ran some commands on the container to check the contents of settings.conf files I had found there.

 

docker exec Ripper cat /ripper/settings.conf

 

The output showed an empty key string, then doing 

 

docker exec Ripper cat /config/settings.conf

 

Showed my key. The /config is what is mapped to /mnt/user/appdata/ripper

 

After simply overwriting the /ripper/settings.conf with /config/settings.conf manually, it worked. So either MakeMKV within the docker is looking at the wrong location or the mechanism for copying the values from the config/settings.conf to the ripper/settings.conf within the docker is at fault.

Link to comment
5 hours ago, rix said:

Ripping audio is not done by Makemkv.

Ok... I am not sure I can follow you. I mean I never said, that audio is ripped by Makemkv. I have in the ripper folder created the abcde.conf

# -----------------$HOME/.abcde.conf----------------- #
# 
# A sample configuration file to convert music cds to 
#  MP3 format using lame, eyeD3 and abcde version 2.9.3 
# 
#   https://andrews-corner.org/abcde/index.html
# -------------------------------------------------- #

# Encode tracks immediately after reading. Saves disk space, gives
# better reading of 'scratchy' disks and better troubleshooting of
# encoding process but slows the operation of abcde quite a bit:
LOWDISK=y

# Specify the method to use to retrieve the track information,
# the alternative is to specify 'musicbrainz':
CDDBMETHOD=cddb

# With the demise of freedb (thanks for the years of service!)
# we move to an alternative:
CDDBURL="http://gnudb.gnudb.org/~cddb/cddb.cgi"

# Make a local cache of cddb entries and then volunteer to use 
# these entries when and if they match the cd:
CDDBCOPYLOCAL="y"
CDDBLOCALDIR="$HOME/.cddb"
CDDBLOCALRECURSIVE="y"
CDDBUSELOCAL="y"

# Specify the encoder to use for MP3. In this case 'lame':
MP3ENCODERSYNTAX=lame 
FLACENCODERSYNTAX=flac                    # Specify encoder for FLAC


# Specify the path to the selected encoder. In most cases the encoder
# should be in your $PATH as I illustrate below, otherwise you will 
# need to specify the full path. For example: /usr/bin/lame
LAME=/usr/bin/lame
FLAC=/usr/bin/flac                                # Path to FLAC encoder

# Specify your required encoding options here. Multiple options can
# be selected as '--preset standard --another-option' etc.
# The '-V 2' option gives VBR encoding between 170-210 kbits/s.
LAMEOPTS='-V 1' 
FLACOPTS='-s -e -V -8'                    # Options for FLAC

# Output type for MP3.
OUTPUTTYPE="mp3,flac"

# The cd ripping program to use. There are a few choices here: cdda2wav,
# dagrab, cddafs (Mac OS X only) and flac. New to abcde 2.7 is 'libcdio'.
CDROMREADERSYNTAX=cdparanoia            
                                     
# Give the location of the ripping program and pass any extra options,
# if using libcdio set 'CD_PARANOIA=cd-paranoia'.
CDPARANOIA=cdparanoia  
CDPARANOIAOPTS="--never-skip=40"

# Give the location of the CD identification program:       
CDDISCID=cd-discid            
                               
# Give the base location here for the encoded music files.
OUTPUTDIR=/out/CD               

# The default actions that abcde will take.
ACTIONS=cddb,playlist,read,encode,tag,move,clean
              
# Decide here how you want the tracks labelled for a standard 'single-artist',
# multi-track encode and also for a multi-track, 'various-artist' encode:
OUTPUTFORMAT='${OUTPUT}/${ARTISTFILE}-${ALBUMFILE}/${TRACKNUM}.${TRACKFILE}'
VAOUTPUTFORMAT='${OUTPUT}/Various-${ALBUMFILE}/${TRACKNUM}.${ARTISTFILE}-${TRACKFILE}'

# Decide here how you want the tracks labelled for a standard 'single-artist',
# single-track encode and also for a single-track 'various-artist' encode.
# (Create a single-track encode with 'abcde -1' from the commandline.)
ONETRACKOUTPUTFORMAT='${OUTPUT}/${ARTISTFILE}-${ALBUMFILE}/${ALBUMFILE}'
VAONETRACKOUTPUTFORMAT='${OUTPUT}/Various-${ALBUMFILE}/${ALBUMFILE}'

# Create playlists for single and various-artist encodes. I would suggest
# commenting these out for single-track encoding.
PLAYLISTFORMAT='${OUTPUT}/${ARTISTFILE}-${ALBUMFILE}/${ALBUMFILE}.m3u'
VAPLAYLISTFORMAT='${OUTPUT}/Various-${ALBUMFILE}/${ALBUMFILE}.m3u'

# This function takes out dots preceding the album name, and removes a grab
# bag of illegal characters. It allows spaces, if you do not wish spaces add
# in -e 's/ /_/g' after the first sed command.
mungefilename ()
{
  echo "$@" | sed -e 's/^\.*//' | tr -d ":><|*/\"'?[:cntrl:]"
}

# What extra options?
MAXPROCS=2                              # Run a few encoders simultaneously
PADTRACKS=y                             # Makes tracks 01 02 not 1 2
EXTRAVERBOSE=2                          # Useful for debugging
COMMENT='abcde version 2.9.3'           # Place a comment...
EJECTCD=y                               # Please eject cd when finished :-)
INTERACTIVE=n

 

Am I missing something entirely? 

Link to comment
3 hours ago, metalchad said:

@rix @Guillaurent

 

I seem to have resolved my issue, it seems the docker isn't bringing in the settings.conf as expected, thus the key not being used.

 

I ran some commands on the container to check the contents of settings.conf files I had found there.

 


docker exec Ripper cat /ripper/settings.conf

 

The output showed an empty key string, then doing 

 


docker exec Ripper cat /config/settings.conf

 

Showed my key. The /config is what is mapped to /mnt/user/appdata/ripper

 

After simply overwriting the /ripper/settings.conf with /config/settings.conf manually, it worked. So either MakeMKV within the docker is looking at the wrong location or the mechanism for copying the values from the config/settings.conf to the ripper/settings.conf within the docker is at fault.

Are you able to rip DVDs and such after this?

I tried and I'm not.

From what I gathered, MakeMKV is actually looking at ~/.MakeMKV/settings.conf

Link to comment
3 hours ago, Guillaurent said:

Are you able to rip DVDs and such after this?

I tried and I'm not.

From what I gathered, MakeMKV is actually looking at ~/.MakeMKV/settings.conf

Well, it does seem to be applied there as well, not sure if it was previously, my guess is no. Perhaps ~/.MakeMKV/settings.conf is set up as an alias of /ripper/settings.conf? And yes, I have successfully ripped a couple DVDs now since making the change.

 

HOWEVER, and I'm sorry for this, I neglected to mention another change I did prior to the changes mentioned. Thinking that it was somehow getting a cached version of the docker image I decided to change the Repository field to rix1337/docker-ripper:1.16.4 to force it to get the 1.16.4 tag instead of latest and then did a force update of the container. This could have also contributed to the fix. After doing so I had to manually delete the 'latest' image version by running

 

docker image remove rix1337/docker-ripper:latest

 

Screen Shot 2021-07-28 at 4.24.24 PM.png

Link to comment
1 hour ago, Zeze21 said:

maybe i am completely off here, so please forgive me - is it at all possible to rip cds with this plugin/docker image or is that not possible?

Yes, it works out of the box for me. Once the docker is set up it will output your files to whatever you set your output directory to [output-directory]/Ripper/CD

 

Each time a disk is inserted into the designated drive, in my case /dev/sr0, it will execute the ripper.sh script in your designated config directory, you can make your own CDrip.sh for full customization, otherwise it will create both FLAC and MP3 files using abcde.

Edited by metalchad
Link to comment
41 minutes ago, metalchad said:

Yes, it works out of the box for me. Once the docker is set up it will output your files to whatever you set your output directory to [output-directory]/Ripper/CD

 

Each time a disk is inserted into the designated drive, in my case /dev/sr0, it will execute the ripper.sh script in your designated config directory, you can make your own CDrip.sh for full customization, otherwise it will create both FLAC and MP3 files using abcde.

Ok thank you...

so i removed the docker then reinstalled it

at first i got 

*** Running /etc/my_init.d/10_syslog-ng.init...
[2021-07-28T18:11:41.470728] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.25 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.13'

[2021-07-28T18:11:41.793025] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;

Jul 28 18:11:41 Server syslog-ng[14]: syslog-ng starting up; version='3.25.1'

Jul 28 18:11:41 Server syslog-ng[14]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().;

*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
28.07.2021 18:11:43 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
28.07.2021 18:11:44 : Disk tray open
28.07.2021 18:12:56 : CD detected: Saving MP3 and FLAC
28.07.2021 18:12:56 : CD detected: Saving MP3 and FLAC
28.07.2021 18:12:56 : Done! Ejecting Disk
chown: cannot access '/out/CD': No such file or directory

so i created a CD folder in the output folder and got this

28.07.2021 18:14:10 : CD detected: Saving MP3 and FLAC
28.07.2021 18:14:11 : Done! Ejecting Disk
28.07.2021 18:15:13 : Disk tray open

the outputfolder has nothing in it apart from the CD folder, which is unfortunately empty...

i am sorry to be so persistent on this but i have no means but to rip my cds on my server, and running adedicated vm for this sounds a bit overkill... so i was thrilled to find out about this docker and i would love to get it to work

Link to comment
21 minutes ago, Zeze21 said:

Ok thank you...

so i removed the docker then reinstalled it

at first i got 



*** Running /etc/my_init.d/10_syslog-ng.init...
[2021-07-28T18:11:41.470728] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.25 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.13'

[2021-07-28T18:11:41.793025] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;

Jul 28 18:11:41 Server syslog-ng[14]: syslog-ng starting up; version='3.25.1'

Jul 28 18:11:41 Server syslog-ng[14]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().;

*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
28.07.2021 18:11:43 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
28.07.2021 18:11:44 : Disk tray open
28.07.2021 18:12:56 : CD detected: Saving MP3 and FLAC
28.07.2021 18:12:56 : CD detected: Saving MP3 and FLAC
28.07.2021 18:12:56 : Done! Ejecting Disk
chown: cannot access '/out/CD': No such file or directory

so i created a CD folder in the output folder and got this



28.07.2021 18:14:10 : CD detected: Saving MP3 and FLAC
28.07.2021 18:14:11 : Done! Ejecting Disk
28.07.2021 18:15:13 : Disk tray open

the outputfolder has nothing in it apart from the CD folder, which is unfortunately empty...

i am sorry to be so persistent on this but i have no means but to rip my cds on my server, and running adedicated vm for this sounds a bit overkill... so i was thrilled to find out about this docker and i would love to get it to work

 

I'm not sure what you've set the value of 'Output Dir' to in the setting for the docker container, but in my case it is set to a user share and I don't believe I had to set any permissions on the share, but in your case it looks like you may be lacking some permissions for it to be able to write data; see the error in your output above

chown: cannot access '/out/CD': No such file or directory

 

If your output directory is a valid user share and you see the Ripper/CD folder in it, perhaps doing a chmod +rwx on the folder from the terminal will solve your problem.

 

 

Sorry, I misread initially.. You shouldn't have to create the CD folder yourself, I don't think, perhaps the Ripper folder I did have to create myself on my user share, cannot recall - but the ripper script should take care of creating CD/Bluray/DVD/etc.. folders, if it doesn't then I have to believe there is a permissions issue.

 

 

Screen Shot 2021-07-28 at 8.30.39 PM.png

Edited by metalchad
Link to comment
5 hours ago, Zeze21 said:

Ok thank you...

so i removed the docker then reinstalled it

at first i got 


*** Running /etc/my_init.d/10_syslog-ng.init...
[2021-07-28T18:11:41.470728] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.25 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.13'

[2021-07-28T18:11:41.793025] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;

Jul 28 18:11:41 Server syslog-ng[14]: syslog-ng starting up; version='3.25.1'

Jul 28 18:11:41 Server syslog-ng[14]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().;

*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
28.07.2021 18:11:43 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
28.07.2021 18:11:44 : Disk tray open
28.07.2021 18:12:56 : CD detected: Saving MP3 and FLAC
28.07.2021 18:12:56 : CD detected: Saving MP3 and FLAC
28.07.2021 18:12:56 : Done! Ejecting Disk
chown: cannot access '/out/CD': No such file or directory

so i created a CD folder in the output folder and got this


28.07.2021 18:14:10 : CD detected: Saving MP3 and FLAC
28.07.2021 18:14:11 : Done! Ejecting Disk
28.07.2021 18:15:13 : Disk tray open

the outputfolder has nothing in it apart from the CD folder, which is unfortunately empty...

i am sorry to be so persistent on this but i have no means but to rip my cds on my server, and running adedicated vm for this sounds a bit overkill... so i was thrilled to find out about this docker and i would love to get it to work

As said by metalchad, have you set the Outpur Dir parameter in the Unraid Docker Container to where you want rips to go?

Link to comment

Well i completely started from scratch after chmodding the hell out of the folders. So all I did was just a fresh new install with the standard parameters

image.thumb.png.fcc9ae02dcb5e3c5217c277677034df8.png

The Folder Downloads exists after the install (created by ripper)

But again when I insert the CD the log shows:

 


*** Running /etc/my_init.d/10_syslog-ng.init...
[2021-07-29T01:40:10.533504] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.25 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.13'

[2021-07-29T01:40:10.868478] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;

Jul 29 01:40:10 Server syslog-ng[14]: syslog-ng starting up; version='3.25.1'

Jul 29 01:40:10 Server syslog-ng[14]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().;

*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
29.07.2021 01:40:12 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
29.07.2021 01:40:13 : Disk tray open
29.07.2021 01:41:13 : Disk tray open
29.07.2021 01:42:25 : CD detected: Saving MP3 and FLAC
29.07.2021 01:42:25 : Done! Ejecting Disk
chown: cannot access '/out/CD': No such file or directory
29.07.2021 01:43:28 : Disk tray open
29.07.2021 01:44:28 : Disk tray open
29.07.2021 01:45:29 : Disk tray open

The thing is... shouldn't ripping take a while? Between CD deteced and Done the log shows no time difference. So i dug a little around. In the Appdata folder (appdata/ripper) there is a Ripper.txt file which has several lines and all read:

Executing customizable pre-read function... done.
Getting CD track info... [WARNING] something went wrong while querying the CD... Maybe a DATA CD or the CD is not loaded?
[WARNING] Error trying to calculate disc ids without lead-out information.

Then I used the console to take a look. I went to usr/bin/ and then just started abcde

[WARNING] something went wrong while querying the CD... Maybe a DATA CD or the CD is not loaded?
[WARNING] Error trying to calculate disc ids without lead-out information.

so i inserted the cd and tried again and got:

# xmcd CD database file
#
# Track frame offsets:
#       150
#       7054
#       19116
#       29496
#       39273
#       49230
#       57108
#       77241
#       89796
#       111405
#       113799
#       121320
#       126018
#       135243
#       141876
#       153045
#       162555
#       172185
#       176508
#       192639
#       213360
#       231390
#       243522
#       261675
#       273183
#       280776
#       294042
#       307077
#       323550
#       332739
#
# Disc length: 4465 seconds
#
# Submitted via: cddb-tool 0.4.7
#
#blues,classical,country,data,folk,jazz,newage,reggae,rock,soundtrack,misc
#CATEGORY=misc
DISCID=bd116d1e
DTITLE=Unknown Artist / Unknown Album
DYEAR=
DGENRE=
TTITLE0=Track 1
TTITLE1=Track 2
TTITLE2=Track 3
TTITLE3=Track 4
TTITLE4=Track 5
TTITLE5=Track 6
TTITLE6=Track 7
TTITLE7=Track 8
TTITLE8=Track 9
TTITLE9=Track 10
TTITLE10=Track 11
TTITLE11=Track 12
TTITLE12=Track 13
TTITLE13=Track 14
TTITLE14=Track 15
TTITLE15=Track 16
TTITLE16=Track 17
TTITLE17=Track 18
TTITLE18=Track 19
TTITLE19=Track 20
TTITLE20=Track 21
TTITLE21=Track 22
TTITLE22=Track 23
TTITLE23=Track 24
TTITLE24=Track 25
TTITLE25=Track 26
TTITLE26=Track 27
TTITLE27=Track 28
TTITLE28=Track 29
TTITLE29=Track 30
EXTD=
EXTT0=
EXTT1=
EXTT2=
EXTT3=
EXTT4=
EXTT5=
EXTT6=
EXTT7=
EXTT8=
EXTT9=
EXTT10=
EXTT11=
EXTT12=
EXTT13=
EXTT14=
EXTT15=
EXTT16=
EXTT17=
EXTT18=
EXTT19=
EXTT20=
EXTT21=
EXTT22=
EXTT23=
EXTT24=
EXTT25=
EXTT26=
EXTT27=
EXTT28=
EXTT29=
PLAYORDER=

then a while nothing happens and then the cd get's ejected

But i can not find any mp3 or flac files....

Link to comment
  • 4 weeks later...

Hi @rix,

 

Looks like Makemkv needs to be updated again.

 

Quote

"This application version is too old.  Please download the latest version at http://www.makemkv.com/ or enter a registration key to continue using the current version.","This application version is too old.  Please download the latest version at %1 or enter a registration key to continue using the current version.","http://www.makemkv.com/"

 

Link to comment
  • 3 weeks later...

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. 😄

  • Like 1
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.