When I hooked up the Oppo machine yesterday, that seemed to be the source of my connectivity problems. They are re-occurring today, with the internet signal being fine but internal wifi very variable from normal to nothing. Connecting the Oppo is the only thing I have changed in the last 2 days.
Rip SACD with a Blu-ray player
- Thread starter MikeyFresh
- Start date
I'm not really sure what to say except this process does not require the internet at all, but the internal WLAN (WiFi) issues can definitely cause problems, however I'm thinking that too should be a non-issue if you had moved the machine close to the router and wired it via Ethernet.
Can you post screenshots of your flash drive's folder structure, and also your GUI settings.
Lastly, please confirm you had circled back on previous posts, it was not the .cfg file in the SACDExtractGUI folder that you needed to make executable, only the one called sacd_extract.
Looks like sacd_extract needs to me made executable.
hifihaven.org
Rip SACD with a Blu-ray player
Are the failed rips in question perhaps SACDs that contain special (non-English) characters in the meta data? If so that is likely the issue, and using the network server method will solve it. Thanks for your replies.. Nope its “Steve Strauss - a very thin string”.. 2020 stockfisch label.. now...
hifihaven.org
Exactly, per the previous posts about that in which initially the .cfg file was mistaken for the file called sacd_extract, which is the one that actually needs to be executable. Once that is completed, the path to that executable needs to be established in the Program field using the Browse button (overwrite what is currently in that field).Looks like sacd_extract needs to me made executable.
Rip SACD with a Blu-ray player
Are the failed rips in question perhaps SACDs that contain special (non-English) characters in the meta data? If so that is likely the issue, and using the network server method will solve it. Thanks for your replies.. Nope its “Steve Strauss - a very thin string”.. 2020 stockfisch label.. now...
The AutoScript folder on the flash drive looks good to go.
Now just circle back to the posts about making sacd_extract executable, you had mentioned the .cfg file at that time and that isn't the one needing the Terminal command, run that command on the file in the SACDExtractGUI folder called sacd_extract, it was the one you downloaded from EuFlo's GitHub.
Once it's been made a Unix executable, then just specify the path to it in the Program field of the GUI, using the Browse button (overwrite what is in that field currently). Then you should be all set.
Thanks Mikey for starting this thread and maintaining it for all these years.
I'm using a Sony BDP-S390 and SACDExtractGUI. The only pitfall I had was not paying attention to having a folder named "AutoScript" on the root of my USB. A couple hours later, I was able to use a 128MB USB drive (pre USB 2?) that was configured using the Windows "diskpart" command to install the script. I have been able to rip a handful of SACDs to DSF no problem.
However, one disk will only rip to an ISO file. The ISO file will not rip to DSF using SACDExtractGUI. It starts the process, but then it stops it and says it's done. Any idea why? Same thing happens when I try to rip the disk directly to DSF.
Thanks!
I'm using a Sony BDP-S390 and SACDExtractGUI. The only pitfall I had was not paying attention to having a folder named "AutoScript" on the root of my USB. A couple hours later, I was able to use a 128MB USB drive (pre USB 2?) that was configured using the Windows "diskpart" command to install the script. I have been able to rip a handful of SACDs to DSF no problem.
However, one disk will only rip to an ISO file. The ISO file will not rip to DSF using SACDExtractGUI. It starts the process, but then it stops it and says it's done. Any idea why? Same thing happens when I try to rip the disk directly to DSF.
Thanks!
My pleasure, welcome to HFH.
No that doesn't make any sense, however I'm curious what behavior and/or error message in the GUI lead you to this conclusion.
I'd also ask which disc title is in question, and if you are using Windows, macOS, or Linux? Finally, which version of sacd_extract is in use (the GUI will list that information).
Hello to everyone!!
I`m using Sony BDP S490 to rip my SACD`s.
Yesterday I`ve noticed odd thing: my rips contains strange, something like elecrostatic noise from vinyl in silent fragments. Everytime when fadeout starts at the end of track this sound starts and stays until next track. 4-5 seconds of these sounds in the background.
Daphile is my main player. I checked it with Foobar on Windows but it`s the same. I`ve checked usb wire with no change.
I`ve download some DSD files from Nativedsd and random rips and these are clear in silence so I guess that for some reason ripping process adds these sounds.
Do you have any idea what might went wrong? Do I need to change settings in BDP? There is nothing to set in sonore software so I believe it`s not the case. All SACD`s were ripped to DSF.
I`d appreciate an suggestions
I`m using Sony BDP S490 to rip my SACD`s.
Yesterday I`ve noticed odd thing: my rips contains strange, something like elecrostatic noise from vinyl in silent fragments. Everytime when fadeout starts at the end of track this sound starts and stays until next track. 4-5 seconds of these sounds in the background.
Daphile is my main player. I checked it with Foobar on Windows but it`s the same. I`ve checked usb wire with no change.
I`ve download some DSD files from Nativedsd and random rips and these are clear in silence so I guess that for some reason ripping process adds these sounds.
Do you have any idea what might went wrong? Do I need to change settings in BDP? There is nothing to set in sonore software so I believe it`s not the case. All SACD`s were ripped to DSF.
I`d appreciate an suggestions
baward
Can you try this, I have posted about this fixing my issue where I would ping fine but still wouldn't rip.Not sure if this is your problem or not but worth a try
open SACDExtractGUI
At the top where it says Program, click Browse and redirect it to the actual location of that sacd_extract executable file
Then try again
I simply run the app from a folder on my desktop
What you have there should work, though there is absolutely no need for that subfolder called sacd_extract-0, I don't have that, everything is in one folder on my Mac, however I see no reason why a subfolder should interfere with anything once you've specified the path, and you have.
I suggest a full power cycle of the 103, with flash drive removed, and after replacing the AC cord allow the machine a few moments to complete its initial boot sequence, then try again.
Greetings and welcome to HFH!Hello to everyone!!
I`m using Sony BDP S490 to rip my SACD`s.
Yesterday I`ve noticed odd thing: my rips contains strange, something like elecrostatic noise from vinyl in silent fragments. Everytime when fadeout starts at the end of track this sound starts and stays until next track. 4-5 seconds of these sounds in the background.
Daphile is my main player. I checked it with Foobar on Windows but it`s the same. I`ve checked usb wire with no change.
I`ve download some DSD files from Nativedsd and random rips and these are clear in silence so I guess that for some reason ripping process adds these sounds.
Do you have any idea what might went wrong? Do I need to change settings in BDP? There is nothing to set in sonore software so I believe it`s not the case. All SACD`s were ripped to DSF.
I`d appreciate an suggestions
Unfortunately there is no easy one size fits all answer, and what you are describing is actually the complex interaction of playback software (and it's settings), along with DAC firmware.
Many DACs don't have this problem at all, because their firmware very briefly mutes the output on track changes. That however can sometimes cause the beginning of the new track to be slightly truncated or "fade in", which is particularly problematic with pieces that are supposed to be gapless playback.
Other DACs provide that mute for too short a period, and so still a very small tick or pop can sometimes be heard on some track changes because the DAC lifted its mute too quickly to fully suppress the noise.
Then there are DACs with no such muting in their firmware, and often those will exhibit the loudest or most pronounced pop or click on track changes.
Sometimes the playback software settings can be altered to limit/reduce, or eliminate this problem, it really is a complex interaction between the way the track is served and how the DAC receives it.
A few questions for you:
1. What DAC are you using and do you have more than one DAC, if so, do they both behave the same?
2. Which playback software are you using?
3. Is the DAC connected directly to a computer, or are the tracks streamed over a network connection?
4. Have you tried to rip the same disc both with and also without the Padding-less DSF option ticked, to see if one produces a better result than the other?
Regards,
Mike
Thank you for your answer!
1. I have one DAC unfortunately, it`s Gustard X16. DAC is fine, I`ve tried demo files from 2L store.
I`ve downloaded DSD64 files and these sounds ok: no strange noises in silence.
2. Daphile and foobar for Windows.
3. Yes, DAC is connected directly to computer via usb. Hard drive which contains all music files is in that computer so no streaming in chain.
4. This one I didn`t try. Is it option in Iso2Dsd? I couldn`t find it.
Those files are different in that they aren't produced from an SACD rip.
No that option only exists in SACDExtractGUI. Download the zip file and unzip (you don't need the source files), launch the program with the .jar file, then point the Program field to sacd_extract.exe using the Browse button.
Close any running instance of ISO2DSD to avoid the potential for a conflict when testing SACDExtractGUI.
Ok, I`ve tried ripping with Padding-less ticked but unfortunately it`s no better.
I don`t get it: track that I`m testing on comes from album Istambul by Jordi Savall. There is 5 seconds of silence after last note decays, and then echo decays. Here this sparkling/noises start but.. it`s not that there is nothing at the background: except microphone hiss, there is humming hearable from studio, so it`s not artificialy added 5 seconds of silence but 5 extra seconds where musicians froze after last note.
So it happens when music stops, it is also noticeable in silent breaks in the middle of tracks (those noises).
I understand that dome tracks are not SACD rips but on those tracks, where volume levels are very low , there are no extra sounds in silence so I guess DAC itself is ok.
Similar threads
