Jump to content
ted_b

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

Rate this topic

Recommended Posts

2 hours ago, Chiefbrodie said:

Hi there again so tonight I've tried all of your above suggestions and feedback but yet still nothing! This is driving me nuts... Maybe I nerd to re download all the relevant autoscript files (can't remember where I got them now) tonight set a static ip for the bluray player I inserted the usb stick with the 3 autoscript files on powered on the bluray waited until the tray opens pop in the sacd disc wait for tge front panel to read sacd then on my pc I opened a command prompt window and it read C:\users\daniel>

After this I typed S. \sacd_extract - I 192.168.0.20:2002 - P - I

Then enter and I get this message when using the command prompt way and when I try with sonore I get this 

20180807_210505.jpg

20180807_211219.jpg

 

@Chiefbrodie

 

After you have opened the prompt enter the following

 

cd S:\

 

this should change the directory and prompt to

 

S:\>

 

now enter the sacd_extract command, which I believe from earlier posts is

 

sacd_extract -i 192.168.0.17:2002 -P -I

Share this post


Link to post
Share on other sites

@Chiefbrodie

I don't use the Sonore software (I have an Oppo BDP-103 for ripping) but that error message  'Failed to connect... ' would cause me to do 2 things; from the CMD prompt type:

 

ip config <return>

 

and make sure your computer is on the same subnet as the disc player you're trying to connect to, ie 192.168.0.x where x is the final triplet in your computer's IP address. If that shows you're on the same subnet, from the cmd prompt type:

 

ping 192.168.0.17

and see if you get successful packet confirmations- should look something like this:

 

Pinging 192.168.0.17 with 32 bytes of data:

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

 

Ping statistics for 192.168.0.17:

      Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>,

Approximate round trip times in milli-seconds:

      Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

If your results are like above, then your computer and disc player hardwares are communicating properly, and you can focus your efforts on your command line syntax,  disc player settings and Sonore software settings. Divide and conquer.

 

If you get timeout errors they are not communicating and that must be fixed before you proceed.

 

Lack of communication might be due to a bad cable, if your cable runs directly from the computer to the disc player without going through a switch you might need a crossover cable (most relatively new computers network interface should do this automatically with a non-crossover cable); other sources of problems could be the computer's firewall (possible but less likely), anti-virus software, faulty network connector, lint in the connector (don't laugh, this actually happens more often than you'd think, especially with old equipment).

 

Share this post


Link to post
Share on other sites
10 hours ago, Chiefbrodie said:

Hi there again so tonight I've tried all of your above suggestions and feedback but yet still nothing! This is driving me nuts... Maybe I nerd to re download all the relevant autoscript files (can't remember where I got them now) tonight set a static ip for the bluray player I inserted the usb stick with the 3 autoscript files on powered on the bluray waited until the tray opens pop in the sacd disc wait for tge front panel to read sacd then on my pc I opened a command prompt window and it read C:\users\daniel>

After this I typed S. \sacd_extract - I 192.168.0.20:2002 - P - I

Then enter and I get this message when using the command prompt way and when I try with sonore I get this 

20180807_210505.jpg

20180807_211219.jpg

The  I typed in the thread should be i as you can see in the image must be a auto correction my bad. 

Share this post


Link to post
Share on other sites
7 hours ago, alandbush said:

 

@Chiefbrodie

 

After you have opened the prompt enter the following

 

cd S:\

 

this should change the directory and prompt to

 

S:\>

 

now enter the sacd_extract command, which I believe from earlier posts is

 

sacd_extract -i 192.168.0.17:2002 -P -I

Thanks for this info alandbush I think this is part of my problem as I didn't know how to change the directory so if I type cd S:\ this then changes the directory to the folder "S" where the file is on my pc to extract? I will try this once home this evening, cheers. 

Share this post


Link to post
Share on other sites
6 hours ago, BluRay444 said:

@Chiefbrodie

I don't use the Sonore software (I have an Oppo BDP-103 for ripping) but that error message  'Failed to connect... ' would cause me to do 2 things; from the CMD prompt type:

 

ip config <return>

 

and make sure your computer is on the same subnet as the disc player you're trying to connect to, ie 192.168.0.x where x is the final triplet in your computer's IP address. If that shows you're on the same subnet, from the cmd prompt type:

 

ping 192.168.0.17

and see if you get successful packet confirmations- should look something like this:

 

Pinging 192.168.0.17 with 32 bytes of data:

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

Reply from 192.168.0.17: bytes=32 time<1ms TTL=128

 

Ping statistics for 192.168.0.17:

      Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>,

Approximate round trip times in milli-seconds:

      Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

If your results are like above, then your computer and disc player hardwares are communicating properly, and you can focus your efforts on your command line syntax,  disc player settings and Sonore software settings. Divide and conquer.

 

If you get timeout errors they are not communicating and that must be fixed before you proceed.

 

Lack of communication might be due to a bad cable, if your cable runs directly from the computer to the disc player without going through a switch you might need a crossover cable (most relatively new computers network interface should do this automatically with a non-crossover cable); other sources of problems could be the computer's firewall (possible but less likely), anti-virus software, faulty network connector, lint in the connector (don't laugh, this actually happens more often than you'd think, especially with old equipment).

 

Hi there bluray444 thanks for this info I'll try pining from the command prompt tonight to test if both computer and bluray are communicating properly, the cable I'm using is brand new so I'm guessing that's not the problem but will try swapping it out with a different one to see. Thanks again 

Share this post


Link to post
Share on other sites
8 hours ago, greynolds said:

What the heck is the "S.\" part at the beginning of your command?  You need to change your current directory to where sacd_extract.exe is located then type the command without the "S.\".  I also notice that you continue to mix up upper and lowercase i letters in your posts - what you show in the actual screenshot looks OK in that regard, but it's important to proofread your posts if you're going to get useful help as the difference between an uppercase I and lowercase i can make all the difference in the world for things like this; it's no different than when entering a password where "password" is considered completely different than "PaSSworD".

Hi greynolds the I was a auto correct it was actually i and the S was me thinking I was changing the directory but I've just learned from alandbush the way to do this so I'll try that this evening to see if that works. Thank you again. 

Share this post


Link to post
Share on other sites
8 hours ago, Dick Darlington said:

 

Tech/computer problems often have multiple underlying causes that must be sorted out to get things working. In my experience anyway. In your case I suspect you’re being thwarted by at least to separate issues (not including the biggest of all: troubleshooting avoidance). What I mean by that is that you seem to be banging your head on the final step instead of stepping back and working methodically to verify that each prerequisite in the chain has been satisfied. More on that in a moment but first ...

 

Potential problem 1: The error displayed in your Windows command console seems to be saying that it cannot find the executable program at the location you specified. Is it in fact in your current folder “c:\users\daniel”?  If it is you don’t need the “.\” prefix because that just says “this folder” although that shouldn’t hurt. If it is not, then you’re explicitly telling Windows to run a program in your home folder that is actually somewhere else. 

 

What happens if if you just type sacd_extract and hit return? Does it display usage info or a different error? Or is the result unchanged? If there is a difference; indicating the sacd_extract program did actually launch, that suggests  there is a problem with the arguments or somewhere else yet to be determined. But if it still says path not found or whatever... your talking to Elvis in the next room when in fact he’s left the building. 

 

Potential problem 2: Your Sonore GUI error would probably be different if it can’t find the sacd_extract executable (I *think*) so assuming it is able to launch your local sacd_extract then either it can’t talk to the player over the network OR it can but the remote sacd_extract is not running and listening on port 2002. If so what problem would cause this? Well any one of many from our current vantage point. That is looking back from the end of the flow chart with no knowledge of the decision branches along the way; who the hell knows?

 

FWIW I use the server method exclusively. Just a personal workflow preference, but nevertheless I include a Telnet launch line  in my scripts so it’s there for troubleshooting if I need it . When all is well with the server method, no worries. But as @Phthalocyanine has said many times (arguably more eloquently than me) and I strongly agree with: when stuff ISN’T working, you’re mostly blind without Telnet. 

 

So so that last digression was for anyone new that might happen along to this post and is such the glutton for punishment that they read this far into it. 

 

Moving along. In my little brain I think of several preliminary items that need to be satisfied and checked off if you’re not one of the lucky few finds ripping nirvana on the first try. Presented roughly in order but the order isn’t absolute and there are subset items not listed relevant to problems along the way:

 

1. Is there solid and verified network connectivity between the computer and the player? “I know I’m using the correct IP address” doesn’t count. 

 

2. Does the AutoScript file on the USB launch when inserted in the player? The tray opening is a strong positive indicator. The lack of the tray opening is not necessarily a counter indicator. 

 

3. Does the AutoScript file that launches find the the USB folder structure at its expected location, e.g. /mnt/sda1?

 

4. Does the AutoScript file succeed in launching 

   A) sacd_extract?

or

   B) Telnet?

or 

    C) both?

 

5. Can the connection from the computer to Telnet port 23 and/or port 2002 be established and verified? (actually this is just item 4 restated)

 

6. etc. etc. 

 

So yes inevitably someone will come along and say “all I did was this and stick that there and whoomp there it was and I’ve ripped 80000 SACDs except for the Tag Team sacd that was never released”, and that is awesome. For them. Some people win the lottery. But this SACD ripping thing is easy peazy and fraught with pitfalls at the same time. 

 

So with all that said I humbly suggest you turn your efforts towards verifying the items listed above. For item one there is ping. For item 2, use a script that opens the drawer and confirm that it does open. The approach to item 3 depends on whether or not Telnet is being employed or not. The murkiness of successive steps clears as the results of previous steps are known. 

 

And then then we pay taxes. 

 

And then then we die ...

 

Share this post


Link to post
Share on other sites
8 hours ago, Dick Darlington said:

 

Tech/computer problems often have multiple underlying causes that must be sorted out to get things working. In my experience anyway. In your case I suspect you’re being thwarted by at least to separate issues (not including the biggest of all: troubleshooting avoidance). What I mean by that is that you seem to be banging your head on the final step instead of stepping back and working methodically to verify that each prerequisite in the chain has been satisfied. More on that in a moment but first ...

 

Potential problem 1: The error displayed in your Windows command console seems to be saying that it cannot find the executable program at the location you specified. Is it in fact in your current folder “c:\users\daniel”?  If it is you don’t need the “.\” prefix because that just says “this folder” although that shouldn’t hurt. If it is not, then you’re explicitly telling Windows to run a program in your home folder that is actually somewhere else. 

 

What happens if if you just type sacd_extract and hit return? Does it display usage info or a different error? Or is the result unchanged? If there is a difference; indicating the sacd_extract program did actually launch, that suggests  there is a problem with the arguments or somewhere else yet to be determined. But if it still says path not found or whatever... your talking to Elvis in the next room when in fact he’s left the building. 

 

Potential problem 2: Your Sonore GUI error would probably be different if it can’t find the sacd_extract executable (I *think*) so assuming it is able to launch your local sacd_extract then either it can’t talk to the player over the network OR it can but the remote sacd_extract is not running and listening on port 2002. If so what problem would cause this? Well any one of many from our current vantage point. That is looking back from the end of the flow chart with no knowledge of the decision branches along the way; who the hell knows?

 

FWIW I use the server method exclusively. Just a personal workflow preference, but nevertheless I include a Telnet launch line  in my scripts so it’s there for troubleshooting if I need it . When all is well with the server method, no worries. But as @Phthalocyanine has said many times (arguably more eloquently than me) and I strongly agree with: when stuff ISN’T working, you’re mostly blind without Telnet. 

 

So so that last digression was for anyone new that might happen along to this post and is such the glutton for punishment that they read this far into it. 

 

Moving along. In my little brain I think of several preliminary items that need to be satisfied and checked off if you’re not one of the lucky few finds ripping nirvana on the first try. Presented roughly in order but the order isn’t absolute and there are subset items not listed relevant to problems along the way:

 

1. Is there solid and verified network connectivity between the computer and the player? “I know I’m using the correct IP address” doesn’t count. 

 

2. Does the AutoScript file on the USB launch when inserted in the player? The tray opening is a strong positive indicator. The lack of the tray opening is not necessarily a counter indicator. 

 

3. Does the AutoScript file that launches find the the USB folder structure at its expected location, e.g. /mnt/sda1?

 

4. Does the AutoScript file succeed in launching 

   A) sacd_extract?

or

   B) Telnet?

or 

    C) both?

 

5. Can the connection from the computer to Telnet port 23 and/or port 2002 be established and verified? (actually this is just item 4 restated)

 

6. etc. etc. 

 

So yes inevitably someone will come along and say “all I did was this and stick that there and whoomp there it was and I’ve ripped 80000 SACDs except for the Tag Team sacd that was never released”, and that is awesome. For them. Some people win the lottery. But this SACD ripping thing is easy peazy and fraught with pitfalls at the same time. 

 

So with all that said I humbly suggest you turn your efforts towards verifying the items listed above. For item one there is ping. For item 2, use a script that opens the drawer and confirm that it does open. The approach to item 3 depends on whether or not Telnet is being employed or not. The murkiness of successive steps clears as the results of previous steps are known. 

 

And then then we pay taxes. 

 

And then then we die ...

Hi Dick thank you for your very detailed post I'll trace me steps and try to rectify, your elvis quote had me in stitches 

Share this post


Link to post
Share on other sites

Hi to all who are kind enough to spare their thought time and knowledge helping me out, I did say in my first post my knowledge and experience with command prompts and changing directories was very limited so thanks for baring with me, so I have set a static ip address on the bluray tonight I will double check all the relevant autoscript files are in the correct place and on the root of the usb and my pc (am I correct in think root is as not in any other folder?) I will ping the bluray to double check that both pc and bluray are communicating with the each other I will change the directory in the command prompt window (didn't know how to do this) until a recent reply then will try again and feed back to you all, thank you again for your time and thoughts and huge help it's amazing what can be learned from good people like yourselves. 

Share this post


Link to post
Share on other sites
3 hours ago, Chiefbrodie said:

Hi to all who are kind enough to spare their thought time and knowledge helping me out, I did say in my first post my knowledge and experience with command prompts and changing directories was very limited so thanks for baring with me, so I have set a static ip address on the bluray tonight I will double check all the relevant autoscript files are in the correct place and on the root of the usb and my pc (am I correct in think root is as not in any other folder?) I will ping the bluray to double check that both pc and bluray are communicating with the each other I will change the directory in the command prompt window (didn't know how to do this) until a recent reply then will try again and feed back to you all, thank you again for your time and thoughts and huge help it's amazing what can be learned from good people like yourselves. 

 

+1 kudos to all those that willingly and helpfully provide information that is not always common knowledge as one would think.

 

@Chiefbrodie

 

Further to my earlier post, it subsequently occurred to me that the process you are following appears manually intensive and prone to typos, especially if you have to repeat it for each SACD rip.

 

The process I follow, surely gleaned from this thread or others, should greatly simplify the process for each subsequent SACD rip, once the initial setup is completed.

 

Let me explain, hopefully, in clear concise steps (oh and this is for Windows)

 

1) open the folder containing the sacd_extract.exe

2) create a new text document file named for eg. SACD_rip

3) open the new text document and type in the sacd_extract command with the appropriate IP address

sacd_extract -i 192.168.0.17:2002 -P -I

(nb - you could copy and paste the above command to prevent any typos)

4) save this text document

5) open this text document again and save as a new command script file

ie.

5a) select 'File -> Save As...' to open the 'Save As window' 

5b) change the 'Save As type' from Text documents to All Files

5c) change the 'File name' as appropriate BUT append the file type extension (.cmd)

eg. SACD_rip.cmd

5d) select the 'SAVE' button

 

Thats it!

 

To rip a SACD, you now simply open this command script file and it will execute.  Viola! (fingers crossed)

 

Should the IP address change, you simply need to repeat from step 3).

 

Good luck.

Share this post


Link to post
Share on other sites
9 minutes ago, alandbush said:

 

+1 kudos to all those that willingly and helpfully provide information that is not always common knowledge as one would think.

 

@Chiefbrodie

 

Further to my earlier post, it subsequently occurred to me that the process you are following appears manually intensive and prone to typos, especially if you have to repeat it for each SACD rip.

 

The process I follow, surely gleaned from this thread or others, should greatly simplify the process for each subsequent SACD rip, once the initial setup is completed.

 

Let me explain, hopefully, in clear concise steps (oh and this is for Windows)

 

1) open the folder containing the sacd_extract.exe

2) create a new text document file named for eg. SACD_rip

3) open the new text document and type in the sacd_extract command with the appropriate IP address

sacd_extract -i 192.168.0.17:2002 -P -I

(nb - you could copy and paste the above command to prevent any typos)

4) save this text document

5) open this text document again and save as a new command script file

ie.

5a) select 'File -> Save As...' to open the 'Save As window' 

5b) change the 'Save As type' from Text documents to All Files

5c) change the 'File name' as appropriate BUT append the file type extension (.cmd)

eg. SACD_rip.cmd

5d) select the 'SAVE' button

 

Thats it!

 

To rip a SACD, you now simply open this command script file and it will execute.  Viola! (fingers crossed)

 

Should the IP address change, you simply need to repeat from step 3).

 

Good luck.

 

Exactly what I do- I create 3 scripts, one to extract ISOs, one to extract 2-track files, and one to extract multi-track files.

Share this post


Link to post
Share on other sites
39 minutes ago, alandbush said:

 

+1 kudos to all those that willingly and helpfully provide information that is not always common knowledge as one would think.

 

@Chiefbrodie

 

Further to my earlier post, it subsequently occurred to me that the process you are following appears manually intensive and prone to typos, especially if you have to repeat it for each SACD rip.

 

The process I follow, surely gleaned from this thread or others, should greatly simplify the process for each subsequent SACD rip, once the initial setup is completed.

 

Let me explain, hopefully, in clear concise steps (oh and this is for Windows)

 

1) open the folder containing the sacd_extract.exe

2) create a new text document file named for eg. SACD_rip

3) open the new text document and type in the sacd_extract command with the appropriate IP address

sacd_extract -i 192.168.0.17:2002 -P -I

(nb - you could copy and paste the above command to prevent any typos)

4) save this text document

5) open this text document again and save as a new command script file

ie.

5a) select 'File -> Save As...' to open the 'Save As window' 

5b) change the 'Save As type' from Text documents to All Files

5c) change the 'File name' as appropriate BUT append the file type extension (.cmd)

eg. SACD_rip.cmd

5d) select the 'SAVE' button

 

Thats it!

 

To rip a SACD, you now simply open this command script file and it will execute.  Viola! (fingers crossed)

 

Should the IP address change, you simply need to repeat from step 3).

 

Good luck.

Wow thank you for that info once again I'll first try this evening changing the directory and see if that's where I've fallen down but reading what you just listed that sounds on paper relatively simple although creating text doc files etc is very alien to as I've never needed to do anything like that I restore furniture for a living so only ever use my pc for leisure but just googled it and it seems straight forward so once again a big thank you. Will feed back later 

Share this post


Link to post
Share on other sites
31 minutes ago, BluRay444 said:

 

Exactly what I do- I create 3 scripts, one to extract ISOs, one to extract 2-track files, and one to extract multi-track files.

Thanks again for this and your help but as above creating scripts /text document etc is alien to me but I'll certainly give it a go as I've got quite a few sacds to rip. 

Share this post


Link to post
Share on other sites
5 hours ago, Chiefbrodie said:

Wow thank you for that info once again I'll first try this evening changing the directory and see if that's where I've fallen down but reading what you just listed that sounds on paper relatively simple although creating text doc files etc is very alien to as I've never needed to do anything like that I restore furniture for a living so only ever use my pc for leisure but just googled it and it seems straight forward so once again a big thank you. Will feed back later 

When you CD to your S drive root folder, S:\ *and* if that is in fact where your copy of sacd_extract.exe is, then that should put to bed your *final* issue. That is you and Elvis ? will be strolling down the aisle in K-Mart reminiscing about all those great times in Vegas you never had. 

 

But alas the blue light special will not be there for you unless and until you go back to square one and work on identifying and fixing the one or two or more problems with the prerequisite steps along the way. 

 

I think you you really need to forget about ? for the time being and focus on being able to answer three questions in the affirmative:

 

1. Are you able to successfully ping your player using the IP address your player is reporting in its settings?

 

2. Have you verified that the AutoScript file is launching? (for example by using a script with a tray opening line and noting that the tray in fact opens.)

 

3. Are you able to launch your player’s Telnet daemon via an AutoScript file designed to do so?

 

Until you work through these things, everything you’re doing on your computer with sacd_extract and Windows command scripts is as pointless as trying to convince Elvis ? that if he lets you wear his fancy jacket, the Blue Light Special will magically appear. This is not to say it wouldn’t be really cool to take a ?? with ? while you’re wearing his jacket ?. It’s just that it’s a futile exercise at this point.  

Share this post


Link to post
Share on other sites
16 hours ago, BluRay444 said:

 

Exactly what I do- I create 3 scripts, one to extract ISOs, one to extract 2-track files, and one to extract multi-track files.

Thanks again for this and your help but as above creating scripts /text document etc is alien to me but I'll certainly give it a go as I've got quite a few sacds to rip. 

Share this post


Link to post
Share on other sites

Morning to all trying to help me, last night I only had limited time so I pinged the ip address and it came back looking good, when I power up the bluray with the usb attached it does open the disc tray so all good there.... Now this is where something isn't working when I try to change the directories to folder S on my C drive it still sends back the same response so I'm at a complete loss again am I placing the sacd extract exe in the correct place on my pc? Here are shots of last night... I couldn't even change directory. Any thoughts? 

20180808_224012.jpg

20180807_210505.jpg

20180808_225837.jpg

Share this post


Link to post
Share on other sites
1 hour ago, Chiefbrodie said:

Morning to all trying to help me, last night I only had limited time so I pinged the ip address and it came back looking good, when I power up the bluray with the usb attached it does open the disc tray so all good there.... Now this is where something isn't working when I try to change the directories to folder S on my C drive it still sends back the same response so I'm at a complete loss again am I placing the sacd extract exe in the correct place on my pc? Here are shots of last night... I couldn't even change directory. Any thoughts? 

20180808_224012.jpg

20180807_210505.jpg

20180808_225837.jpg

 

Computers don’t lie, apparently, so the photos suggest that your pc does not have an S: drive.

 

To clarify, can you open the folder containing the sacd_extract file and attach of photo of the screen.

Share this post


Link to post
Share on other sites
1 hour ago, alandbush said:

 

Computers don’t lie, apparently, so the photos suggest that your pc does not have an S: drive.

 

To clarify, can you open the folder containing the sacd_extract file and attach of photo of the screen.

Hi again I will take a screen shot once home this evening, but I can already confirm that my computer doesn't have a S drive, the S is the the name of the folder where I put the sacd_extract exe file, I followed what the instruction said and named a folder as short as possible so S came to mind for super audio. 

Is this the issue, where should I place the folder? Thanks again. 

Share this post


Link to post
Share on other sites

macOS, Pioneer BDP-170 and using Terminal to rip

created a "SACD_rips" (doh! ? ) folder in my "Music" folder, placed a copy of "sacd_extract" inside it and this is the command line I'm using:

 

cd /Users/paolo/Music/SACD_rips

 

then, to rip SACDs as DSF:

 

./sacd_extract -i 10.0.1.42:2002 -2 -s


Qnap HS-251+ NAS (powered by an HD-Plex 100w LPS) > Cirrus7 Nimbini v2.5 Media Edition i7-8559U/32/512 running Roon ROCK (powered by a ZeroZone 19v/5A LPS) > Lumin U1 Mini (powered by a Vinnie Rossi Mini Pure-DC-4EVR LPS) >  UpTone Audio ISO Regen (powered by an Uptone Audio UltraCap LPS-1.2) > Metrum Acoustics Adagio NOS digital preamplifier + First Watt SIT 3  power amplifier (or Don Garber Fi "Y" 6922 tube preamplifier + Don Garber Fi "X" 2A3 SET power amplifier, both powered from an Alpha-Core BP-30 Isolated Symmetrical Power Transformer) > Klipsch Cornwall III

 

headphones system:

Cirrus 7 > Lumin U1 Mini > Metrum Adagio > Pathos Aurium amplifier (powered by an UpTone Audio JS-2 LPS) > Focal Clear headphones

Share this post


Link to post
Share on other sites
11 minutes ago, Chiefbrodie said:

Hi again I will take a screen shot once home this evening, but I can already confirm that my computer doesn't have a S drive, the S is the the name of the folder where I put the sacd_extract exe file, I followed what the instruction said and named a folder as short as possible so S came to mind for super audio. 

Is this the issue, where should I place the folder? Thanks again. 

Anywhere but you need to know the full path.

Share this post


Link to post
Share on other sites
14 minutes ago, Chiefbrodie said:

Hi again I will take a screen shot once home this evening, but I can already confirm that my computer doesn't have a S drive, the S is the the name of the folder where I put the sacd_extract exe file, I followed what the instruction said and named a folder as short as possible so S came to mind for super audio. 

Is this the issue, where should I place the folder? Thanks again. 

 

@Chiefbrodie

 

My apologies to you because I must have misunderstood an earlier post.

A folder named S makes much more sense than a drive called S.

 

Lets keep this simple and ignore the command prompt process.

 

Instead, follow the process I described to create a command script.

That does not require prior knowledge of drives, folders, paths.

 

Share this post


Link to post
Share on other sites
35 minutes ago, alandbush said:

 

@Chiefbrodie

 

My apologies to you because I must have misunderstood an earlier post.

A folder named S makes much more sense than a drive called S.

 

Lets keep this simple and ignore the command prompt process.

 

Instead, follow the process I described to create a command script.

That does not require prior knowledge of drives, folders, paths.

 

No worries, I do like the idea of keeping it simpler as it's proving to be quite a headache compared to ripping my blurays and cds, I do understand that drives and paths exist as all my media is stored on various hard drives on my network and there has to be a path to access it from certain devices but I will have a stab at what you suggested once home and see if I can create a command script to simplify the process, it's frustrating as I seem to be at the last step. Will feed back later 

Share this post


Link to post
Share on other sites
44 minutes ago, alandbush said:

 

@Chiefbrodie

 

My apologies to you because I must have misunderstood an earlier post.

A folder named S makes much more sense than a drive called S.

 

Lets keep this simple and ignore the command prompt process.

 

Instead, follow the process I described to create a command script.

That does not require prior knowledge of drives, folders, paths.

 

No worries, I do like the idea of keeping it simpler as it's proving to be quite a headache compared to ripping my blurays and cds, I do understand that drives and paths exist as all my media is stored on various hard drives on my network and there has to be a path to access it from certain devices but I will have a stab at what you suggested once home and see if I can create a command script to simplify the process, it's frustrating as I seem to be at the last step. Will feed back later 

Share this post


Link to post
Share on other sites

I set out to rip my sacds to have them sit on my network in my music library so I can access when needed I have a few 2 channel sacds and quite a few multichannel sacds and only want to rip so needed to rip 2 channel from 2 channel and the multichannel layer from the multi.... This is certainly a learning curve I really appreciate all help that's being offered thanks again 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...