Mostly success! Sorry to need to go to the well once again.

I had a bit of a problem with the Output directory and the path. The Browse button did not give any access to my dedicated external hard drive appearing on the desktop and simply typing in Music Drive/Patricia Barber got me the error message [ERROR] Output directory "Music Drive" doesn't exist or is not writable. I ripped to the desktop then copied to the Music Drive, so I think the DSF files will play on my main system. Can this extra step be avoided?

Thanks, Mark
That shouldn't be necessary, but I can't say why the external drive wouldn't be recognized. If the drive is mounted and visible on your desktop, then you definitely should be able to Browse to it.
 
For purposes of closure, I still could not/can not explain why the Browse Botton would not locate the connected external drive which appears on the desktop. I mystery for another time. I can highly recommend the disk I ripped--Patricia Barber-Cafe Blue--Unmastered. I understand that Gus Skinnas used the raw data from the 2011 recording. I have the original as well-interesting differences and worth the effort to rip the SACD layer of the disc.

Thanks, again for your help. Mark.
 
I still could not/can not explain why the Browse Botton would not locate the connected external drive which appears on the desktop.
I can only guess that it could be a disk permissions issue, if you right-click and Get Info for that disk and view the permissions at the bottom, perhaps it's permissions when used on that particular computer are read only, or something to that effect.

I can highly recommend the disk I ripped--Patricia Barber-Cafe Blue--Unmastered.
Great SACD.

Thanks, again for your help. Mark.
My pleasure Mark, cheers!
 
Successfully ripped a SACD using Ubuntu linux. However, I was not successful in compiling sacd_extract for Windows? Who has a step by step instruction to compile sacd-ripper for Windows using Ubuntu?
 
Last edited:
Successfully ripped a SACD using Ubuntu linux. However, I was not successful in compiling sacd_extract for Windows? Who has a step by step instruction to compile sacd-ripper for Windows using Ubuntu?
I don't even know what "sacd-ripper" is.
 
I don't know what sacd-ripper is.

This:
GitHub - setmind/sacd-ripper: Improved sacd_extract

The based C++ code that does the ripping that SACDExtractGUI runs on top of. I was able to compile it for Linux, but not for Windows.

The instructions to compile for Windows is this:
$ tar -xzf libiconv-1.15.tar.gz
$ cd libiconv-1.15
$ ./configure --host=x86_64-w64-mingw32 --prefix=/usr/x86_64-w64-mingw32 --enable-static
$ make
$ sudo make install

$ cd tools/sacd_extract
$ cmake -DMINGW64=YES
$ make
 
I see the instructions are posted there.
Followed those instructions, stuck on the first make. See error below, looks like I need mingw-w64, but would appreciate step by step if anyone has.

user@ubuntu:~/Downloads/libiconv-1.15$ make
builddir="`pwd`"; cd libcharset && make all && make install-lib libdir="$builddir/lib" includedir="$builddir/lib"
make[1]: Entering directory '/home/dk/Downloads/libiconv-1.15/libcharset'
if [ ! -d include ] ; then mkdir include ; fi
cp ./include/libcharset.h.in include/libcharset.h
cd lib && make all
make[2]: Entering directory '/home/dk/Downloads/libiconv-1.15/libcharset/lib'
/bin/bash ../libtool --mode=compile x86_64-w64-mingw32-gcc -I. -I. -I.. -I./.. -I../include -g -O2 -fvisibility=hidden -DLIBDIR=\"/usr/x86_64-w64-mingw32/lib\" -DBUILDING_LIBCHARSET -DBUILDING_DLL -DENABLE_RELOCATABLE=1 -DIN_LIBRARY -DINSTALLDIR=\"/usr/x86_64-w64-mingw32/lib\" -DNO_XMALLOC -Dset_relocation_prefix=libcharset_set_relocation_prefix -Drelocate=libcharset_relocate -DHAVE_CONFIG_H -c ./localcharset.c
libtool: compile: x86_64-w64-mingw32-gcc -I. -I. -I.. -I./.. -I../include -g -O2 -fvisibility=hidden -DLIBDIR=\"/usr/x86_64-w64-mingw32/lib\" -DBUILDING_LIBCHARSET -DBUILDING_DLL -DENABLE_RELOCATABLE=1 -DIN_LIBRARY -DINSTALLDIR=\"/usr/x86_64-w64-mingw32/lib\" -DNO_XMALLOC -Dset_relocation_prefix=libcharset_set_relocation_prefix -Drelocate=libcharset_relocate -DHAVE_CONFIG_H -c ./localcharset.c -DDLL_EXPORT -DPIC -o .libs/localcharset.o
In file included from ./localcharset.c:27:
/usr/share/mingw-w64/include/stdio.h:9:10: fatal error: corecrt_stdio_config.h: No such file or directory
9 | #include <corecrt_stdio_config.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:62: localcharset.lo] Error 1
make[2]: Leaving directory '/home/?/Downloads/libiconv-1.15/libcharset/lib'
make[1]: *** [Makefile:34: all] Error 2
make[1]: Leaving directory '/home/dk/Downloads/libiconv-1.15/libcharset'
make: *** [Makefile:42: lib/localcharset.h] Error 2
 
OK, you meant compiling sacd_extract.


According to the build instructions, you do.
Looks like I have a "fatal error" with a header file for mingw-w64, see below:

/usr/share/mingw-w64/include/stdio.h:9:10: fatal error: corecrt_stdio_config.h: No such file or directory
9 | #include <corecrt_stdio_config.h>
 
Actually, let me ask this: do everyone here use sacd-ripper (my understanding is that it's a fork of sacd_extract) or does everyone here use sacd_extract?
It's the latter, and that's true in all cases, setmind's GitHub uses "sacd-ripper" not as the name of the actual program, that is and has always been sacd_extract. If you compile it using those instructions on setmind's GitHub, the resulting Windows .exe will be called sacd_extract.exe.

If you'd like to use the latest version, visit EuFlo's Github and try the -99 version for Windows.
 
It's the latter, and that's true in all cases, setmind's GitHub uses "sacd-ripper" not as the name of the actual program, that is and has always been sacd_extract. If you compile it using those instructions on setmind's GitHub, the resulting Windows .exe will be called sacd_extract.exe.

If you'd like to use the latest version, visit EuFlo's Github and try the -99 version for Windows.
Will try later tonight. Thanks.

Quick question though, this saids it's code for PS3, I assume it works just fine for my Sony S590?
 
Will try later tonight. Thanks.

Quick question though, this saids it's code for PS3, I assume it works just fine for my Sony S590?
You are reading very old GitHub copy that was cut/pasted more than once across more than one fork. Yes it works with the S590, I would not have posted it here for you to consider if it did not.

Scroll to the bottom of that page to reveal the Assets, download the most recent version of the .exe, and replace the one you currently have with it. All set to go assuming the file path is specified in the GUI.
 
You are reading very old GitHub copy that was cut/pasted more than once across more than one fork. Yes it works with the S590, I would not have posted it here for you to consider if it did not.

Scroll to the bottom of that page to reveal the Assets, download the most recent version of the .exe, and replace the one you currently have with it. All set to go assuming the file path is specified in the GUI.
You're right, stupid question, of course it works.
 
Dear friends. I have player Sony BDP-S495. Ripping is OK? It's player same as s490?
And if YES - what is maximum firmware can ripping SACD? My player firmware M13.R.0430.
Thank you.
 

Attachments

  • 1.jpg
    1.jpg
    154.5 KB · Views: 8
Last edited:
Dear friends. I have player Sony BDP-S495. Ripping is OK? It's player same as s490?
And if YES - what is maximum firmware can ripping SACD? My player firmware M13.R.0430.
Thank you.
Good afternoon and welcome to HFH.

Yes the S495 was reported working by one other member, as you said it is essentially the same machine as the S490, with the addition of the Karaoke feature.

We don't have any information about specific firmware versions for that player, however the only firmware that is reported not working with the S390/490/590 is actually the oldest and original firmware version, all subsequent updates are working as best we can tell.
 
Good afternoon and welcome to HFH.

Yes the S495 was reported working by one other member, as you said it is essentially the same machine as the S490, with the addition of the Karaoke feature.

We don't have any information about specific firmware versions for that player, however the only firmware that is reported not working with the S390/490/590 is actually the oldest and original firmware version, all subsequent updates are working as best we can tell.
ТHANK YOU for fast answer. Today i check your method. Can you give me links to instrustions and correct Autorip files.
Best regards.
 
ТHANK YOU for fast answer. Today i check your method. Can you give me links to instrustions and correct Autorip files.
Best regards.
Sure thing, but let's clarify exactly what you mean by AutoRip, as that is a specific method in which an ISO is written directly to the USB flash drive that you insert into the Blu-ray player.

While AutoRip does work well with the S390/490/590, certain SACDs with special non-English characters in authored in the metadata will refuse AutoRip. For those discs you must use the sleep-server method, as AutoRip will not work.

For that reason we recommend the sleep-server method as a better choice, however that special non-English characters issue typically only affects classical music titles, it's pretty rare with most other kinds of music.

Do you have a bunch of classical discs?
 
Sure thing, but let's clarify exactly what you mean by AutoRip, as that is a specific method in which an ISO is written directly to the USB flash drive that you insert into the Blu-ray player.

While AutoRip does work well with the S390/490/590, certain SACDs with special non-English characters in authored in the metadata will refuse AutoRip. For those discs you must use the sleep-server method, as AutoRip will not work.

For that reason we recommend the sleep-server method as a better choice, however that special non-English characters issue typically only affects classical music titles, it's pretty rare with most other kinds of music.

Do you have a bunch of classical discs?
I have japanese rock/pop SACD. Can you send me links with instructions for sleep-server method?
Best.
 
Back
Top