Transfer rates will depend on a whole range of variables, however, I suspect the BDP-S490 Ethernet port is 100MB which would be faster than a WLAN card using the 802.11n standard which is pretty common. No built in option for WLAN on the BDP-S490 though
That's how I understand it, this era (2012-13) of Sony Blu-ray players have a Fast Ethernet NIC capable of 100MB/s, and while the WiFi on the U.S. variant of these machines actually works quite well, the U.K. specific models for whatever reason omitted WLAN as a feature, perhaps the only difference between an S490 and S590.
It is generally speaking preferable to connect these units via Ethernet. WiFi will work more or less well depending on the exact operating conditions and network variables, but will be a bit slower and somewhat prone to interference where Ethernet is not.
Good evening and Happy Thanksgiving weekend to those celebrating in America, and a Happy Belated Thanksgiving to all of our (now frozen?) friends up in Canada whose harvest was completed over a month ago!
Tonight it is my pleasure to welcome another new member from the other side of the pond, adding to a recent influx here of new members from Europe.
I am very pleased @Nexus3 has joined us here on HFH, he brings a wealth of knowledge on the All Things Digital side of the ledger, and has made a huge and generous contribution on another forum's SACD ripping thread with regard to compiling mindset's new sacd_extract 3.9 for Linux, Mac, and Windows.
He's also big into multichannel, an area where personally I'm of little to no help at all. Please welcome @Nexus3 to HiFi Haven!
Just a quick update...the front USB does work on the BDP-S490, it just seems to take a bit longer to recognise the USB stick than the rear port. Had insert/remove/insert
Thank you MikeyFresh for that royal introduction, not sure I deserve it though .
Now lets get down to business, here are my latest compilations of setmind's great SACD ripping tools:
Code:
SACDExtractGUI v0.1-7-g135cbd5d
sacd_extract version 0.3.9@setmind-13-g58db5f16fcf410ae4d6aeca226a067b37ade136a
For Linux and macOS users, there is one additional set-up step necessary, you must designate the sacd_extract file in the folder a Unix executable with a single line of code. Open Terminal and use the following command:
Code:
chmod +x
Followed by a single space after the above code. Now drag and drop the sacd_extract file onto the Terminal window, the file path/name will fill in/populate automatically. Press Enter.
Now close Terminal, sacd_extract will now appear as a Unix executable in the GUI's folder.
Should the need for DSD audio players arise, please drop a note for what platform / operating system they might be required for.
I will publish the SW links in this thread though, to keep this one solely for ripping topics.
I set up the tools on my Windows 7 system and ripped successfully, thanks ! In terms of speed then I didn’t see any major difference between 3.7 and 3.9. I was already getting good speed on 3.7. although 3.9 was very slightly
faster……..2.96mb/sec versus 2.97mb/sec using same disc (2ch).
I also tried ripping both the 2 channel and multi channel audio at the same time and that worked a treat with a speed of 3.18mb/sec (see screenshot)
BTW...what's the calculation refer to on the last line, 113.6MB?
I did notice that the file sizes were different between the 3.7 and 3.9 rips, the 3.9 rips being slightly smaller in some but not all cases. I assume this is because 3.9 defaults to “padding-less DSF” whereas 3.7 does not.
I did a second rip to confirm with padding enabled using 3.9 and the file sizes were identical to the 3.7 rips.
This did get my thinking a little more about rip validation and AccurateRip etc. I guess there’s no way to validate any of the rips other than rely on “sacd_extract” to report errors appropriately?
Mike....I did wonder that but the last file on the MCH rip is approx 283MB? Having said that in the 2CH rip the file size is 90MB as reported in the second screenshot.
Mike....I did wonder that but the last file on the MCH rip is approx 283MB? Having said that in the 2CH rip the file size is 90MB as reported in the second screenshot.
Hmm, I wonder if that's the size of the DST compressed track that was then unfolded to 283MB?
I'm pretty sure on stereo rips that the last line is reporting the size of the final track completed, but I'll test it out right now to double check.
EDIT: On a stereo rip its somewhat close but still not the exact number, Extract reporting on that final "Completed" line 216.4MB while the folder shows the final track to be 223.4MB in size.
EDIT #2: After further review this difference is attributable to 2 things: the first is my appending of album art and manipulation of the meta data in the .dsf files (which of course affects their size), and the second being my Mac reporting the file size in MB while sacd_extract reports in MiB.
Maybe you need some common ground to start your comparison?
Since you presumably both own the Moon album of Pink Floyd, why not do a basic comparison on the result types which should not differ at all, regardless what sacd_extract flavour is used.
1. Create a hash value (MD5 or SHA-256) of the full album file (ISO-rip)
2. Hash the individual tracks (rip to .DFF)
I'll rip all the tracks again (2CH & MCH) as DFF (DSDIFF) with DST decompression selected and then calculate the hash values. I'll also take note of that confusing number at the end of the rip to see if we get the same number!
Name: 05 - Pink Floyd - The Great Gig In The Sky.dff
Size: 200833332 bytes (191 MiB)
SHA256: 1428A65C0161F895369480326B63CDC7B00A658AABB09D45FF29B6BD746FE046
Name: 05 - Pink Floyd - The Great Gig In The Sky.dff
Size: 602498500 bytes (574 MiB)
SHA256: 12EC7424AFC5C731FC00F1AB766184F109F2D1B83FABD64B5AB7CC0A78910315
DSDIFF output: C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]
DSDIFF output: C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\01 - Pink Floyd - Speak To Me.dff] (1/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\02 - Pink Floyd - Breathe.dff] (2/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\03 - Pink Floyd - On The Run.dff] (3/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\04 - Pink Floyd - Time.dff] (4/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\05 - Pink Floyd - The Great Gig In The Sky.dff] (5/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\06 - Pink Floyd - Money.dff] (6/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\07 - Pink Floyd - Us And Them.dff] (7/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\08 - Pink Floyd - Any Colour You Like.dff] (8/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\09 - Pink Floyd - Brain Damage.dff] (9/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [stereo]\10 - Pink Floyd - Eclipse.dff] (10/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\01 - Pink Floyd - Speak To Me.dff] (11/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\02 - Pink Floyd - Breathe.dff] (12/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\03 - Pink Floyd - On The Run.dff] (13/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\04 - Pink Floyd - Time.dff] (14/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\05 - Pink Floyd - The Great Gig In The Sky.dff] (15/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\06 - Pink Floyd - Money.dff] (16/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\07 - Pink Floyd - Us And Them.dff] (17/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\08 - Pink Floyd - Any Colour You Like.dff] (18/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\09 - Pink Floyd - Brain Damage.dff] (19/20)..
Processing [C:\SACD1\Pink Floyd - Dark Side Of The Moon [multi]\10 - Pink Floyd - Eclipse.dff] (20/20).. Completed: 100% (113.6MB), Total: 100% (113.6MB) at 3.19MB/secWe are done..
OK, I'll re-rip this disc as DFF when I get home later.
In the meantime, I still don't know what that last line in Extract is referring to, but could the size discrepancy I noted yesterday between what Extract reported and what my Mac thinks the Stereo track file size is be due to the difference between MiB and MB, or their sometimes interchangeable use, when really they aren't the same thing at all?
Well it isn't advisable for this specific operation, since DSF supports tagging and afaik some older sacd_extract versions leave their "signature" as tag comment (can be checked e.g. foobar2000).
@mike
Since you used the -c switch to decompress DST to raw DSD, my assumption is as follow:
DSDIFF output: C:\DST\Pink Floyd - Dark Side Of The Moon [stereo]
DSDIFF output: C:\DST\Pink Floyd - Dark Side Of The Moon [multi]
Processing [C:\DST\Pink Floyd - Dark Side Of The Moon [stereo]\10 - Pink Floyd - Eclipse.dff] (1/2)..
Processing [C:\DST\Pink Floyd - Dark Side Of The Moon [multi]\10 - Pink Floyd - Eclipse.dff] (2/2)..
Completed: 100% (113.6MB), Total: 100% (113.6MB) at 3.28MB/secWe are done..
Why do you think it's displaying that message at the end of the extract when I requested that the DST be decompressed to raw DSD? Just the way the program works?
DSDIFF output: /Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]
DSDIFF output: /Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/01 - Pink Floyd - Speak To Me.dff] (1/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/02 - Pink Floyd - Breathe.dff] (2/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/03 - Pink Floyd - On The Run.dff] (3/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/04 - Pink Floyd - Time.dff] (4/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/05 - Pink Floyd - The Great Gig In The Sky.dff] (5/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/06 - Pink Floyd - Money.dff] (6/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/07 - Pink Floyd - Us And Them.dff] (7/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/08 - Pink Floyd - Any Colour You Like.dff] (8/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/09 - Pink Floyd - Brain Damage.dff] (9/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [stereo]/10 - Pink Floyd - Eclipse.dff] (10/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/01 - Pink Floyd - Speak To Me.dff] (11/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/02 - Pink Floyd - Breathe.dff] (12/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/03 - Pink Floyd - On The Run.dff] (13/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/04 - Pink Floyd - Time.dff] (14/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/05 - Pink Floyd - The Great Gig In The Sky.dff] (15/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/06 - Pink Floyd - Money.dff] (16/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/07 - Pink Floyd - Us And Them.dff] (17/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/08 - Pink Floyd - Any Colour You Like.dff] (18/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/09 - Pink Floyd - Brain Damage.dff] (19/20)..
Processing [/Volumes/PATRIOT/Pink Floyd - Dark Side Of The Moon [multi]/10 - Pink Floyd - Eclipse.dff] (20/20)..
Completed: 100% (113.6MB), Total: 100% (113.6MB) at 3.11MB/secWe are done..
There's that 113.6MB number again, only this time ripped on an S590 and MacBook Air over WiFi in NY, and running just a bit slower than @mike 's S490 on Windows over Ethernet in the U.K.
For comparison, the track 1 (stereo) file information from my rip:
So it yields the exact same file size as your U.K. disc does, but I'm having some difficulty on the CLI with the SHA256 hash value generation. I might abort that and search for a suitable Mac utility to use instead of the CLI.
I'd also like to take a moment to suggest that this particular aspect of ripping SACD might warrant it's own separate thread topic here at HFH. To date we've done a good job of keeping the thread clean and focused on the ripping task itself, and I'd very much like to keep it that way.
About 2+ years ago this subject was visited by the original PS3 ripping brigade when the Blu-ray player method was first spawned. At that time it was found that early rips (as early as 2011) done on the PS3 were bit perfect/identical to a newer Blu-ray player rip of the very same disc. That made perfect sense, given both the old and new rips were done using Mr. Wicked's fantastic SACD Extract.
While the above does not constitute any kind of AccurateRip database, it was good enough for me, as I primarily wish to just get the rips done with, and move on to the actual DSD file music listening.
So while this is an interesting topic and might warrant a new thread with a focus on creating a database of ripped disc file information, it is decidedly not a necessary requirement for newcomers (or anyone else) to consider in the overall context of ripping SACD, to date there is absolutely no indication the rips are not accurate or bit perfect.
Well we now know what the number at the end relates to although not sure why it's displaying that number when the rip set for the DST be decompressed to raw and only seems to do that on last track. Not a massive issue now we know what the number is
Good idea to move to another thread (maybe "general related issues"), point taken on getting the rips done and enjoying the music.
Why do you think it's displaying that message at the end of the extract when I requested that the DST be decompressed to raw DSD? Just the way the program works?
I must conclude that sacd_extract shows the source file size (e.g. DST for MCH) of tracks only.
Naturally you both expected that the target file size should be shown in the rip status section.
I'd also like to take a moment to suggest that this particular aspect of ripping SACD might warrant it's own separate topic here at HFH. To date we've done a good job of keeping the thread clean and focused on the ripping task itself, and I'd very much like to keep it that way.
Granted - may I suggest putting rip logs or other potential "visual obstructions" into QUOTE and / or CODE formatting, this should improve the reading ability and scrolling.
I really don't want to beat a dead horse longer than needed, but if that source file size (per track) got you that "confused", it might be merited to ask mindset whether he can retune the whole information / ripping status log section.
What do you think about a track line, showing which track is currently ripped and its source (processed) file size (value always equal to DST).
And secondly about a total data summary line, showing the overall target size ripped (written) so far (value depends on ripping option used).
Last but not least a total elapsed time info, would also be welcome from a user's standpoint IMHO.
So what do you think, shall we approach mindset about this pettiness of pure statistical nature?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
,
.
