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

[cdeveza]

With my Pioneer 170, the USB stick does not have to be bootable.

 

Perhaps, maybe it needs to be bootable for the Oppo 105D, I dont know, just want to share my experience.

[Kal Rubinson]

Perhaps, maybe it needs to be bootable for the Oppo 105D, I dont know, just want to share my experience.

I does not need to be bootable with a 105 or a 102.

[greynolds]

I does not need to be bootable with a 105 or a 102.

Or a 103 even.

[cdeveza]

Or a 103 even.

 

Like I said, it did not work for me on a virgin USB stick, I had to make it bootable for it to work. I was just thinking out loud that the stick that people are using may have been bootable already in the first place. Just my observation. The stick may already have an MBR in it already. Those are hidden files I believe. Anyways, if it works for you, then no problem then.

[Kal Rubinson]

Or a 103 even.

 

Yeah. That, too. :-)

[cdeveza]

Yeah. That, too. :-)

 

I did a little test. I low level format my usb stick. This erases everything. Then I copy the Autoscript folder, then tried it. Nothing happens. So I went back and run rufus-2.11p.exe, this creates a partition with master boot record on the stick and place some boot files on the stick also. Then, I just manually delete all the files on the stick that I can see, and copy the Autoscript folder and tried it, and now it works. The MBR is a hidden partition on the the stick, and this allow the system to load whats on the Autoscript.

 

One can easily mistake a stick to be empty when it actually has an MBR partition in it already. Some new stick being sold with some files in it usually has the MBR partition in it already and one can delete all the files in it, but the MBR is still in it. If I am not mistaken, high level formatting will not delete the MBR partition. Low level formatting is the only way it can be deleted. So all I am saying is that if your stick would not work, then try this rufus-2.11p.exe and create an MBR partition on your stick and see if it works. If it still does not work, then I believe that the machine is probably not compatible. Try it, its not going to hurt.

[greynolds]

I did a little test. I low level format my usb stick. This erases everything. Then I copy the Autoscript folder, then tried it. Nothing happens. So I went back and run rufus-2.11p.exe, this creates a partition with master boot record on the stick and place some boot files on the stick also. Then, I just manually delete all the files on the stick that I can see, and copy the Autoscript folder and tried it, and now it works. The MBR is a hidden partition on the the stick, and this allow the system to load whats on the Autoscript.

 

One can easily mistake a stick to be empty when it actually has an MBR partition in it already. Some new stick being sold with some files in it usually has the MBR partition in it already and one can delete all the files in it, but the MBR is still in it. If I am not mistaken, high level formatting will not delete the MBR partition. Low level formatting is the only way it can be deleted. So all I am saying is that if your stick would not work, then try this rufus-2.11p.exe and create an MBR partition on your stick and see if it works. If it still does not work, then I believe that the machine is probably not compatible. Try it, its not going to hurt.

 

I just double checked the USB thumb drive I'm using for this. It is a 64GB drive and has a single exFAT partition using the MBR partition scheme.

 

What seems likely is that your stick may have initially been partitioned with the GPT partitioning scheme. It's likely that only MBR partition types will work for this. But you definitely shouldn't need to make the stick bootable for it to work.

 

And FYI, in case it wasn't clear, the exchange I was having with Kal was pointing out a typo of his; not poking fun at you.

[cdeveza]

I just double checked the USB thumb drive I'm using for this. It is a 64GB drive and has a single exFAT partition using the MBR partition scheme.

 

What seems likely is that your stick may have initially been partitioned with the GPT partitioning scheme. It's likely that only MBR partition types will work for this. But you definitely shouldn't need to make the stick bootable for it to work.

 

And FYI, in case it wasn't clear, the exchange I was having with Kal was pointing out a typo of his; not poking fun at you.

 

Like I said, my stick was low level formatted, meaning totally blanked out, nothing in it, no partitioning whatsoever. And I guess what I meant was, your stick has to have an MBR partition in it, in order to work. With MBR in it, that makes your stick bootable, that is why its called Master Boot Record. It may boot to a Dos operating system or whatever, and in our case, it boots to whatever is in that Autoscript folder and loads whatever it is in it. Well, as long as it works, I am happy.

[JediJoker]

It may boot to a Dos operating system or whatever, and in our case, it boots to whatever is in that Autoscript folder and loads whatever it is in it.

Except that the player clearly isn't booting from the stick. If it were, the player's OS wouldn't be running. The player is booting from its internal storage. The AutoScript is just a daemon, and it can only be loaded after booting the player, to my knowledge.

[CatManDo]

Here's the start-up sequence on my Pioneer 170, with the prepared USB stick connected:

- player is booting it's OS

- checks for the presence of an optical disc in the drive (displays "No disc" when the drawer is empty)

- then checks for the presence of USB storage (displays "USB disk" when a stick is connected)

- reads files on the USB stick (light on my USB stick flickers), which loads the autoscript program

- drawer opens

[cdeveza]

Except that the player clearly isn't booting from the stick. If it were, the player's OS wouldn't be running. The player is booting from its internal storage. The AutoScript is just a daemon, and it can only be loaded after booting the player, to my knowledge.

 

This is true, but it is also clear that it needs this MBR to find and load this Autoscript files. Booting does not seem to indicate just loading the operating system, but loading whats on the first sector of the inserted storage device.

[greynolds]

This is true, but it is also clear that it needs this MBR to find and load this Autoscript files. Booting does not seem to indicate just loading the operating system, but loading whats on the first sector of the inserted storage device.

The MBR partition in and of itself doesn't make the stick any more bootable (in the sense of loading an operating system from the stick) than a GPT partition would as GPT partitions can also be bootable; the boot drive on the Windows 10 system I'm typing this message on has a GPT partition. GPT is a newer partitioning scheme that has to be used if a partition is larger than 2TB and the Oppo apparently won't read the autoscript files from a GPT partition, which makes sense because the same thing applies to installing firmware updates via USB, as that also requires using a MBR partition. But again, this is just a matter of which partitioning scheme is supported for reading the autoscript files and has nothing to do with the stick being "bootable". Essentially, you're reading too much into the B in MBR standing for "boot".

 

So when using a USB drive for ripping on an Oppo BDP-10x player, it needs to be partitioned with the MBR scheme and formatted with the FAT, FAT32, or exFAT file system; I'm not sure if NTFS is supported.

[cdeveza]

Essentially, you're reading too much into the B in MBR standing for "boot".

 

So when using a USB drive for ripping on an Oppo BDP-10x player, it needs to be partitioned with the MBR scheme and formatted with the FAT, FAT32, or exFAT file system; I'm not sure if NTFS is supported.

 

This is funny as we are actually talking about the same thing. Its just the definition of the "boot" is what we differ, just as you said, the disk has to have an MBR in it in order for it to work, all I am saying is that it is actually is actually reading this first sector and giving the machine its first instruction from the moment the disk is inserted, and this is what I call booting from the drive. Its just terminology my friend. For me, the booting is its ability to read the first instructions as soon as whatever it is, is inserted and take extra control from then on. Whether it is called MBR or whatever, it does not matter, it is its ability to get the first instruction is what I call booting. Whatever you call this process, booting or whatever, it does not matter, we are talking about the same process, just different name.

[greynolds]

This is funny as we are actually talking about the same thing. Its just the definition of the "boot" is what we differ, just as you said, the disk has to have an MBR in it in order for it to work, all I am saying is that it is actually is actually reading this first sector and giving the machine its first instruction from the moment the disk is inserted, and this is what I call booting from the drive. Its just terminology my friend. For me, the booting is its ability to read the first instructions as soon as whatever it is, is inserted and take extra control from then on. Whether it is called MBR or whatever, it does not matter, it is its ability to get the first instruction is what I call booting. Whatever you call this process, booting or whatever, it does not matter, we are talking about the same process, just different name.

The distinction actually is important for two reasons.

 

1) The first is that it's important for people to realize that they can't partition the drive they use for this with GPT partitioning; it needs to be a MBR partition. This is simply because the OS running on the Oppo won't recognize scripts on GPT partitions. Note that the Oppo BDP-10x series will handle media files on drives with GPT partitions.

 

2) The second is that all this talk about booting from the stick simply isn't accurate and only serves to confuse people. The player boots on its own, with or without the stick plugged in. If a USB drive is present, is partitioned with the supported partitioning scheme (MBR), and formatted with a supported file system (FAT, FAT32, exFAT), the OS will finish its boot process and then check for the autoscript folder and run the script (if it's there). The USB stick can actually be inserted into the USB port before or AFTER the player has booted; when using it I've been booting the player up, disabling auto play, and then inserting the USB drive. For this SACD ripping process, you're simply running a script from the USB drive. Nothing more, nothing less.

 

So again, you were right that MBR is important; your reasoning for it just wasn't entirely accurate.

 

FWIW, I'm a beta tester for Oppo. That obviously doesn't mean I'm an expert at all things (Oppo or otherwise), but in this case I'm pretty confident about what I'm saying.

[paul3000h]

This is funny as we are actually talking about the same thing. Its just the definition of the "boot" is what we differ, just as you said, the disk has to have an MBR in it in order for it to work, all I am saying is that it is actually is actually reading this first sector and giving the machine its first instruction from the moment the disk is inserted, and this is what I call booting from the drive. Its just terminology my friend. For me, the booting is its ability to read the first instructions as soon as whatever it is, is inserted and take extra control from then on. Whether it is called MBR or whatever, it does not matter, it is its ability to get the first instruction is what I call booting. Whatever you call this process, booting or whatever, it does not matter, we are talking about the same process, just different name.

 

Can see where you are coming from and it is 'funny' in the nicest sense because you clearly mean well and funnily enough you are roughly right but at the same time not, bow to greynolds tech savvy he has put it as it truly is. And you have helped people who might find themselves in your situation. Well done to all. Good for all.

[paul3000h]

All you need to know to rip SACD's using Pioneer players BDP160 and BDP170. Other players could be similar. (only qualifying players, see post #1) I struggled a bit so hope this helps some others.

 

Start to finish instructions for PC users to extract the iso only. (Adapted from various posts, thanks to all concerned.)

 

1. Optional: Get latest version sacd extract file, sacd_extract.exe 0.3.8 here https://github.com/sacd-ripper/sacd-ripper/releases and replace the one in the folder with the latest one, see below.

1a. Optional:download the user manual, google for it. reset to factory settings and complete the first use wizard.

2. Optional: update the firmware. google for it. Instructions in manual and below.

Using the player's remote control:

Press the STANDBY/ON button to switch the unit on.

If the player starts to play a disc, press the STOP button and wait until the Pioneer logo is displayed on your TV.

Press the Home Menu button to display the HOME MENU.

Select Initial Setup and press the ENTER button.

Select Options and press the ENTER button.

Select System information and press the ENTER button.

Select Next Screen and press the ENTER button

The firmware version of your player will be displayed on the TV screen.

3. Must do. Turn 'disc auto play' off and 'Last Memory' (called resume on some players) off. In initial setup/options see manual.

You will find the only 2 needed folders here thanks to ted_b and Maldur:

4. AutoScript and sacd_extract, if these 2 folders are within other folders you must only use the folders named AutoScript and sacd_extract.

Place these 2 named folders directly where instructed below.

post 26

http://www.computeraudiophile.com/f11-software/sacd-ripping-using-oppo-or-pioneer-yes-its-true-29251/index2.html

or

post #48

http://www.computeraudiophile.com/f11-software/sacd-ripping-using-oppo-or-pioneer-yes-its-true-29251/index2.html

Unzip all downloaded folders.

5. Connect your pioneer player BDP160 LAN socket to your modem LAN socket. According to the player's manual.

Write down the IP address of your player. Find how to find it in the manual or find it in your modem's settings.

Check if you see your player is showing in Windows/Network/Media Devices of your PC (connected to the same LAN).

Disconnect from the player all USB devices.

6. Folder AutoScript contains the files to rip original SACD discs.

Copy only the (unzipped) AutoScript folder to the root of a USB stick formatted Fat32.

Safest to use an empty usb stick but you can leave your other files on your stick.

7. Folder sacd_extract contains the files to execute (start) the ripping. Files inside the folder are: sacd_extract.exe and a file sacd.cmd

You should put this folder on a drive or partition with enough space to create the .iso image.

Best to put it directly on the C drive then you are very unlikely to have problems with long filenames which originate from the iso.

The PC must be on the same network as the player

Edit the sacd.cmd file with Notepad or another editor to change the IP address which exists in the file to that IP address of your player you noted at step 5.

8. Restart the player with no discs in it.

9. Insert prepared USB stick into the player.

The tray will automatically open ie slide out.

10. Remove USB stick from your player or can leave it in to the end of ripping.

Put sacd disc in tray.

Press the close button.

Wait until the disc is recognized by the player. You will see SACD in the players window.

11. Inside the Folder sacd_extract on the Windows C drive (or wherever else you placed it) run/open the sacd.cmd file and the ripping process should start.

To rip another SACD make sure that the rip has finished, the CMD window on your computer will have auto closed when it is finished.

Eject the tray with previous disc and put in the next disc and repeat this step 11.

When finished First remove USB stick and turn off player and power ie reboot the player to return it to normal player use.

 

Ignore anything you may see in this thread to do with Telnet it is now an option not required.

 

Out of interest these are the commands that can used in the sacd.cmd file. Can be used to extracct DFF, DSF and DST but there are other methods given in this thread (must use the exact case as given, upper or lower.):

 

Usage: sacd_extract [options] [outfile]

-2, --2ch-tracks : Export two channel tracks (default)

-m, --mch-tracks : Export multi-channel tracks

-e, --output-dsdiff-em : output as Philips DSDIFF (Edit Master) file

-p, --output-dsdiff : output as Philips DSDIFF file

-s, --output-dsf : output as Sony DSF file

-I, --output-iso : output as RAW ISO

-c, --convert-dst : convert DST to DSD

-C, --export-cue : Export a CUE Sheet

-i, --input[=FILE] : set source and determine if "iso" image,

device or server (ex. -i192.168.1.10:2002)

-P, --print : display disc and track information

Help options:

-?, --help : Show this help message

--usage : Display brief usage message

 

Added this, thanks to greynolds.

 

...when using a USB drive for ripping it needs to be partitioned with the MBR scheme and formatted with the FAT, FAT32, or exFAT file system; I'm not sure if NTFS is supported.

[SpotOn]

So it looks like the Oppo 103 is now sold out at Amazon.com and Oppo direct.

I wonder if this is a temporary shortage, or if the drive is now out of production.

[One and a half]

So it looks like the Oppo 103 is now sold out at Amazon.com and Oppo direct.

I wonder if this is a temporary shortage, or if the drive is now out of production.

 

A lot of people who've read this thread may have contributed to the drought. Oppo would like to release their 203 later this year, but now have no product to sell

[StephanLJ]

Has any of the European users been successful with the EU models of the Oppo drives ripping SACDs.

[CatManDo]

The region doesn't matter. Most people posting here have US Oppo players, but there are also users of the european, australian and asian versions who are ripping SACDs successfully.

[StephanLJ]

Thank you CatManDo

[wolfram]

Yes, I have the 105 EU model and already ripped all of my SACDs. :-)

[mvilla]

Yes, I have the 105 EU model and already ripped all of my SACDs. :-)

 

+1 and I'm using 103 EU

[forester]

...when using a USB drive for ripping it needs to be partitioned with the MBR scheme and formatted with the FAT, FAT32, or exFAT file system; I'm not sure if NTFS is supported.

 

Just to clarify: this only applies to the AutoScript thumb drive inserted in the player. NTSF works fine for the destination drive receiving the rips.

[pl_svn]

...45 pages already? =:-0

 

took me three weeks of hunting but finally found a very good deal on a 105D and tomorrow we'll know if I get the thing or... if I have to open a PayPal claim (yes: the deal was *that* good )

fingers crossed

btw... used 103s are going, here, for €600 :-0 that's... :nutter: (and, in fact, they usually don't sell )

 

anyway... can someone, please, point me to the instructions for Mac OS and *no* Java (just using the Terminal), please?

 

thank you guys:)