SACD Ripping using an Oppo or Pioneer? Yes, it's true!

[joehirez]

@Nexus3

 

Thank you for the reply. 

 

I downloaded Foobar2000 and opened the ISO and played the problematic track.  At 7:38 into the track (13:12 total time) it just stops, same spot as converted DSF file.  Seems like the ISO did not get all the sectors from the disc or is somehow corrupted.  If it was just this one disc I would conclude maybe just some issue with the disc, but running into this problem on around half the discs I've ripped so far.

 

I used two different USB sticks with AutoRip.  One was 8GB the other 32GB.  Both formatted with FAT32.  Same issue with either one.

 

It would be interesting to rip the SACD over the network to see how that would behave vs. ripping directly to the USB stick, but I can't get a connection to the player.

 

Any other ideas most apprecaited!

[Dick Darlington]

8 minutes ago, joehirez said:

Both formatted with FAT32.

It’s been a while. And a few brain surgeries for removal of cannabis pearls later, which BTW rarely occur but often appear in clusters when they do ... anyway I have to wonder if the iso image may be larger than the 4Gb per file FAT32 limit. 

[Nexus3]

OK thanks for confirming that the ISO has indeed a problem (maybe premature cut-off).

 

Since you were saying that the problematic ISOs were having all a STEREO + MCH area could you check their filesizes please.

 

As you may know FAT32 has a file size limit of 4GByte and a single DVD layer (12cm) (=used by most SACDs) can fit up to 4.38 GByte. 

[MikeyFresh]

52 minutes ago, Nexus3 said:

As you may know FAT32 has a file size limit of 4GByte and a single DVD layer (12cm) (=used by most SACDs) can fit up to 4.38 GByte. 

 

One good reason to use NTFS formatting with AutoRip, it eliminates the potential for that problem. OPPO players can also use exFAT formatting in similar fashion.

 

1 hour ago, joehirez said:

It would be interesting to rip the SACD over the network to see how that would behave vs. ripping directly to the USB stick, but I can't get a connection to the player.

 

Can you pst a screenshot of the GUI settings? While I think the above posts have likely identified the issue you are having with AutoRip, there is no good reason why you shouldn't be able to get the server method working too.

 

[obscuredXclouds]

Hi, maybe someone here can help. I am using the latest versions of SACDExtractGUI and sacd_extract and cannot get the ISO+DSF rip option to work. The ISO extraction or DSF extraction works fine as a separate run. I have tried all three OS's I have. Here is an example of what the GUI outputs:   [SUCCESS] Port 2002 of 192.168.1.22 is accessible.   [RUNNING][/home/obx/Music/SACD/sacd_extract/sacd_extract, -i, 192.168.1.22:2002, -w, -I, -s, -2, -m, -C, -P, -o, /home/obx/Music, -y, /home/obx/Music/DSFs].

[MikeyFresh]

1 hour ago, obscuredXclouds said:

Hi, maybe someone here can help. I am using the latest versions of SACDExtractGUI and sacd_extract and cannot get the ISO+DSF rip option to work. The ISO extraction or DSF extraction works fine as a separate run. I have tried all three OS's I have. Here is an example of what the GUI outputs:   [SUCCESS] Port 2002 of 192.168.1.22 is accessible.   [RUNNING][/home/obx/Music/SACD/sacd_extract/sacd_extract, -i, 192.168.1.22:2002, -w, -I, -s, -2, -m, -C, -P, -o, /home/obx/Music, -y, /home/obx/Music/DSFs].

 

I have ISO+DSF running on the macOS compile, no strange behavior there I can see.

[mindset]

After some weekends of deciphering disassembled codes, I have managed to create a working patch for sacd_extract_160 to work with BDP-S6700 and BDP-S6500.  Outputs are bit perfect compared with those from BDP-S390.

 

Still working on some minor issue, but hopefully I will be able to share it soon.

 

[Nexus3]

5 hours ago, mindset said:

I have managed to create a working patch for sacd_extract_160 to work with BDP-S6700 and BDP-S6500.

 

 

Wow 😵, what a bombshell 💥 return & announcement - truly a welcome back @mindset !

As both players make use of version 3.10.26 in their linux kernel, are those still armv6l based?

[joehirez]

@MikeyFresh @Nexus3 @Dick Darlington

 

Thank you again for the help gents!

 

Sure enough, the issue is that the FAT32 file size limit was truncating the ISO file for discs with fuller content.

 

For the truncated ISOs ripped to the FAT32 file system, Windows shows the file size as 4,194,304 KB.  So, anytime you see an ISO with this file size, it has almost certainly been truncated.  

 

I re-formatted my USB stick with NTFS and now am able to get all the sectors in the ISO.

 

Much obliged for all the help!

 

I'm still not able to rip via the network server method to try and extract an ISO from discs that won't rip with the AutoRip process on the USB.  I saw some posts that the connectivity issue to the player over port 2002 is fixed with an updated AutoScript, AutoScript.TSS and sacd_extract_160 files for the Pioneer BDP-80FD.  If anyone can point me to these latest and greatest files, I would be most grateful.

 

This is a great community and thanks again!

 

 

 

[MikeyFresh]

31 minutes ago, joehirez said:

I'm still not able to rip via the network server method to try and extract an ISO from discs that won't rip with the AutoRip process on the USB.  I saw some posts that the connectivity issue to the player over port 2002 is fixed with an updated AutoScript, AutoScript.TSS and sacd_extract_160 files for the Pioneer BDP-80FD.  If anyone can point me to these latest and greatest files, I would be most grateful.

 

You can find a known working AutoScript version for the Pioneer BDP-80FD here.

 

Be sure to retain the enclosing folder called AutoScript:

 

[joehirez]

@MikeyFresh

 

The three files should go in an AutoScript subfolder directly under the root on the USB stick correct?

 

I downloaded again from the link you sent.  Pioneer reads the USB stick and ejects the tray, but still cannot connect to it on port 2002.

 

>>

 

sacd_extract 0.3.9.3 enhanced by euflo ....starting! 
 
Found configuration 'sacd_extract.cfg' file... 
    Artist will be added in folder name (artist=0) no 
    Performer will be added in filename of track (performer=0) no 
    Padding-less (nopad=0) no 
    Pauses included (pauses=0) no 
    Concatenate (concatenate=0) no 
    ID3tagV2.4 (id3tag = 4) yes 
 
Program terminates! 
 
Failed to connect 
libsacdread: Can't open 10.0.1.20:2002 for reading 

 

>>

 

Microsoft Windows [Version 10.0.19041.329]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\Joe>ping 10.0.1.20

Pinging 10.0.1.20 with 32 bytes of data:
Reply from 10.0.1.20: bytes=32 time=16ms TTL=64
Reply from 10.0.1.20: bytes=32 time=2ms TTL=64
Reply from 10.0.1.20: bytes=32 time=1ms TTL=64
Reply from 10.0.1.20: bytes=32 time=2ms TTL=64

Ping statistics for 10.0.1.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 16ms, Average = 5ms

C:\Users\Joe>telnet 10.0.1.20 2002
Connecting To 10.0.1.20...Could not open connection to the host, on port 2002: Connect failed

C:\Users\Joe>

 

>>

 

I disabled Windows Firewall to make sure there is not port blocking.  

 

Any other thoughts on what's happening?

 

Appreciate the help!

 

[MikeyFresh]

51 minutes ago, joehirez said:

@MikeyFresh

 

The three files should go in an AutoScript subfolder directly under the root on the USB stick correct?

 

I downloaded again from the link you sent.  Pioneer reads the USB stick and ejects the tray, but still cannot connect to it on port 2002.

 

>>

 

sacd_extract 0.3.9.3 enhanced by euflo ....starting! 
 
Found configuration 'sacd_extract.cfg' file... 
    Artist will be added in folder name (artist=0) no 
    Performer will be added in filename of track (performer=0) no 
    Padding-less (nopad=0) no 
    Pauses included (pauses=0) no 
    Concatenate (concatenate=0) no 
    ID3tagV2.4 (id3tag = 4) yes 
 
Program terminates! 
 
Failed to connect 
libsacdread: Can't open 10.0.1.20:2002 for reading 

 

>>

 

Microsoft Windows [Version 10.0.19041.329]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\Joe>ping 10.0.1.20

Pinging 10.0.1.20 with 32 bytes of data:
Reply from 10.0.1.20: bytes=32 time=16ms TTL=64
Reply from 10.0.1.20: bytes=32 time=2ms TTL=64
Reply from 10.0.1.20: bytes=32 time=1ms TTL=64
Reply from 10.0.1.20: bytes=32 time=2ms TTL=64

Ping statistics for 10.0.1.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 16ms, Average = 5ms

C:\Users\Joe>telnet 10.0.1.20 2002
Connecting To 10.0.1.20...Could not open connection to the host, on port 2002: Connect failed

C:\Users\Joe>

 

>>

 

I disabled Windows Firewall to make sure there is not port blocking.  

 

Any other thoughts on what's happening?

 

Appreciate the help!

 

 

Everything looks good on the USB flash drive, can you post a screenshot of the GUI settings?

[Dick Darlington]

55 minutes ago, joehirez said:

C:\Users\Joe>telnet 10.0.1.20 2002

The telnet connection must be made via the default telnet port, i.e. port 23, not 2002, which is the port sacd_extract listens on. 

[mindset]

20 hours ago, Nexus3 said:

 

Wow 😵, what a bombshell 💥 return & announcement - truly a welcome back @mindset !

As both players make use of version 3.10.26 in their linux kernel, are those still armv6l based?

Thanks.  Both run Linux 3.10.26 on MTK8580DJAG (armv7l).

[Mike6f]

Whenever I see Win10 mentioned in a network issue, I think AHA!

 

I don't know why but Win10, especially recent patches seems to hate all older or non MS network devices. Most recent I was looking at was something about turning off SMB, whatever that is.

[mindset]

Here is the patch for S6500/S6700:

 

Please respect copyrights. 

 

This patch can only be used for legal purposes at your own risk.

1. You can use this patch only for processing discs you legally own.
2. Any output obtained with this patch cannot be shared with anyone.
3. Before any disc leaves your possession, all outputs obtained from the disc must be permanently destroyed.

 

To apply the patch, overwrite the file "a" in the zip file over sacd_extract_160 at the 192476-byte offset using the method of your preference.  For reference (using dd):

 

The sacd_extract_160 program must be started while the player is OFF.  This means that the quick start mode has to be enabled,

 

By the way, I am not the author of sacd_extract_160.

[Phthalocyanine]

12 hours ago, mindset said:

Here is the patch for S6500/S6700:

Kudos to @mindset for his pioneering work in expanding the range of SACD ripping devices!

 

Now I just have to find a Sony BDP-S6700 or BDP-S6500.

 

Hard to do with all my Thrift Stores closed at the moment.

 

Something to look forward to in the future . . . .

 

[MikeyFresh]

30 minutes ago, Phthalocyanine said:

Now I just have to find a Sony BDP-S6700 or BDP-S6500.

 

For a bit more scratch than the typical used piece, you can still find the S6700 new-in-box at Best Buy, Target, Crutchfield, and B&H.

 

I picked up an open-box special for $65.

 

Welcome back BTW - it's nice to hear from all of the old gang!

[Phthalocyanine]

6 minutes ago, MikeyFresh said:

I picked up an open-box special for $65.

Wow, you are tempting me!

 

7 minutes ago, MikeyFresh said:

it's nice to hear from all of the old gang!

Yes it is.  I am keeping an eye on the thread but haven't had the need or opportunity recently to contribute much.

 

@MikeyFresh

You're doing such an excellent job of helping new-comers with their problems.

[Nexus3]

13 hours ago, mindset said:

Here is the patch for S6500/S6700:

 

 

 

Hooray, grazie mille @mindset, can you confirm that my fiddling has nailed it?

 

FileName			MD5 HashValue			FileSize
sacd_extract_6700	83548AD29B9787B8CE067C100D379064	342,61 KiB
sacd_extract_160	49107E9625E8CD27232E395787C46FE2	342,61 KiB
README			E6A41E8A6CD30BAEAFA40660587C383B	342 bytes
a			CFCAEDE40075FB4A24093E46913AE360	11,64 KiB

 

 

59 minutes ago, Phthalocyanine said:

Now I just have to find a Sony BDP-S6700 or BDP-S6500.

 

Well the next best players in line (candidates with kernel v3.10.26), would be the Pioneer BDP-180 & the Sony UHP-H1.

 

33 minutes ago, MikeyFresh said:

Welcome back @Phthalocyanine - it's nice to hear from all of the old gang!

 

👏

 

23 minutes ago, Phthalocyanine said:

@MikeyFresh

You're doing such an excellent job of helping new-comers with their problems.

 

No museum would find a better curator, regardless what the exhibition stuff would be about.

 

[mindset]

4 hours ago, Nexus3 said:

Hooray, grazie mille @mindset, can you confirm that my fiddling has nailed it?

You did it right.

 

4 hours ago, Nexus3 said:

Well the next best players in line (candidates with kernel v3.10.26), would be the Pioneer BDP-180 & the Sony UHP-H1.

There are SONY UBP's as well.  They are too expensive to play with at this point.

[Nexus3]

On 6/26/2020 at 1:13 AM, mindset said:

There are SONY UBP's as well.  They are too expensive to play with at this point.

 

Sadly, the UBP-X800M2 (and likely all Sony UHD players with a current FW) simply ignores any kind of AutoScript (regular, telnet, AutoRip, ARMinfo). 

[Nexus3]

Evening folks,

 

here is a status update on the new 6700 script and its AutoRip A6 derivative:

 

It IS working BUT not on all Sony BDP-S6700's!

 

What we know for SURE (thanks to the comprehensive testing by @MikeyFresh, @mindset & @EugenF) :

 

• The disruption is NOT caused by a mere firmware release, which simply turns OFF the AutoScript functionality.
• If your player was manufactured before 2017 (FW version M32.R.0380 or older) the AutoScripts will work, you can EVEN UPGRADE to the current FW release - without loosing the SACD ripping ability.
• If your player was built 2019+ (comes with FW version M32.R.0527), you are out of luck for now.
• The predecessor model (BDP-S6500) is almost certainly not affected.

 

What we can SPECULATE about:

 

• The demarcation line could be in the year 2018 - the more S6700 owners report in their firmware factory level and the device manufacturing dates, the better we could narrow down the point of change.
• The cause of the incompatibility could be a HW revision change (different board / SoC) or a factory SW setting which is not affected by regular FW updates.
• Firmware downgrades will likely not fix the problem.

[Nexus3]

To better but slightly off-topic news:

 

On 4/18/2020 at 11:41 PM, ted_b said:

I would be VERY surprised if any ediitor can edit DSD files without going to DXD, best case.  DSD is not an editable beast.

 

 

With the addition of WavPack v5 handling, 

MKVToolNix v48 has become the first basic Direct Stream Digital editor in the world

and it's absolutely free of charge.

 

 

You can now cut & merge compressed DSD audio streams in such a manner that you will NOT lose a single sample!

 

Basic TO-DOs:

Quote

 

1. Losslessly compress your DSD files (.dsf or .dff) with wavpack (.wv)
2. Repackage the WavPack file into the Matroska container with mkvmerge / MKVToolNix GUI (.mka)
3. Choose the desired cutting method (manual via time indexes or automatic by filesize or duration)
4. Extract the WavPack-DSD stream (.mka->.wv) via mkvextract (or GUI)
5. Decompress the .wv back to .dsf or .dff via wvunpack

 

 

 

 

Who cares or could benefit from this?

 

Quote

 

• "Music lovers" 💿 who want their favourite SW audio players to support DSD files, can now cut and transmit sample files instead of full tracks to the developers (also gives certain legal advantages)
• "Hardcore audiophiles" 🤓 who want to manually cut their MASTER-DIFF SACD rips, with the aim to mirror the track lenghts of the Red Book layer / cover duration print - down to the very last millisecond
• "DSD online shops" 🛒 who can offer their potentional customers audio/track previews, in original DSD instead of PCM

 

 

 

Happy DSD editing ✂️! 

[klassikmann]

15 hours ago, Nexus3 said:

To better but slightly off-topic news:

 

 

 

With the addition of WavPack v5 handling, 

MKVToolNix v48 has become the first basic Direct Stream Digital editor in the world

and it's absolutely free of charge.

 

 

You can now cut & merge compressed DSD audio streams in such a manner that you will NOT lose a single sample!

 

Basic TO-DOs:

 

 

 

Who cares or could benefit from this?

 

 

 

Happy DSD editing ✂️! 

@Nexus3Very very cool.

What I did according to the Nexus3's Basic TO-DOs :

1. I took the ISO of a hybrid SACD and generated a "DSDIFF edit master" (DFF, 56 min), 2CH with DST decompression using sacd_extract.
2. The .dff has been packed to a .wv with wavpack 5.3.0 .
3. I inserted the .wv into MKVToolNix GUI (v48) as input source file.
4. To test particularly the gapless cut of the input DFF I configured a split after every 10 minutes. Multiplexing in MKVToolNix generated six .mka files (Matroshka Audio).
5. mkvextract delivered six .wv files.
6. A single run of wvunpack with the six .wv files as input generated the final six DSD files; use --dff or --dsf to control the requested DSD format. Playback is gapless!

No "one-stop-shopping" - you need the combination of various open source products - but it works.

Marvelous!