klassikmann Posted February 10, 2018 Share Posted February 10, 2018 6 hours ago, GT in OZ said: Haggis999, I didn't overlook your link - in fact I have a print out in front of me. In effect version 3 above is your suggested method (and I tried that first). My multi player is a Pioneer BDP-170 (the european equivalent to the US BDP-80FD). I only succeed if I use a bootable USB stick. I'm not sure whether this is a strong requirement (for the DBP-170 at least), it's my experience only. Link to comment
Popular Post klassikmann Posted March 9, 2018 Popular Post Share Posted March 9, 2018 Experiences with Sony BDP-S490 I recently bought a used Sony DBP-S490 (same as S590 but without Wifi) as a backup for my Pioneer BDP-170). The firmware version was M12R0320 from March 2012. My first try to get a telnet access was unsuccesful. I decided not to bother myself with this firmware, instead to update the player to the actual firmware (M12.R.0510), after that I downgraded the firmware to M12R0430 (last firmware to support SACD-R) using advice and tools of http://www.malcolmstagg.com/bdp-s390-downgrade.html. My goal was to use the player stand-alone, i.e. without a network connection which implies storage of the final ISO on the USB stick. To achieve that goal I started with LAN access and telnet. During my tests I noticed that the contents of the USB stick could be optimized. In particular, there is no need for a second directory (AutoScript.TSS), the directory AutoScript is sufficient containing two or three files: - AutoScript - mysh.sh (only necessary for scenario 2) - sacd_extract_160 Scenario 1: network connection + telnet + manual rip to the thumb driveContents of AutoScript: #MTKAT 0.xx script CLI(CLI_exec echo root::0:0:root,,,:/root:/bin/sh >/etc/passwd) CLI(CLI_exec /usr/sbin/telnetd &) SLEEPMS(3000) CLI(CLI_app.vfdmg.b clear_msg) CLI(CLI_app.vfdmg.b scroll_msg start) SLEEPMS(5000) CLI(CLI_drv.ir.rx.sq 0xaf000) CLI(CLI_exec cp /mnt/sda1/AutoScript/sacd_extract_160 /) CLI(CLI_exec /sacd_extract_160 -S &) Explanation: - got root access - wait for 3 seconds - scroll message ("0000") - wait for 5 seconds, - open drawer (now you insert the SACD to be ripped) - copy sacd_extract_160 to "/" - start ripper process as background job, waiting for client Sometimes you find an additional line CLI(CLI_exec insmod /lib/modules/2.6.35/BDP/splitter.ko) before the last line. If in doubt or problems arise, insert the insmod. After you insert the SACD, you have to change the music settings to toggle the channels from multi to 2ch or vice versa, see (https://www.computeraudiophile.com/forums/topic/28569-sacd-ripping-using-an-oppo-or-pioneer-yes-its-true/?page=110&tab=comments#comment-779908). Now you log-in via telnet (e.g. using putty) as root to the player and give two commands: cd /mnt/sda1/AutoScript ./sacd_extract_160 -I -i 127.0.0.1:2002 After two error messages from mknod and insmod which can be neglected, ripping starts and the ISO will be stored in the AutoScript directory. That's it. Your USB thumb device should be 8GB or bigger to contain the ISO. By the way, I use a NTFS formatted USB stick, so you don't have to worry about the 4GB limit of FAT32. Scenario 2: No network connection i.e. no telnetContents of AutoScript: #MTKAT 0.xx script CLI(CLI_exec echo root::0:0:root,,,:/root:/bin/sh >/etc/passwd) SLEEPMS(3000) CLI(CLI_app.vfdmg.b clear_msg) CLI(CLI_app.vfdmg.b scroll_msg start) SLEEPMS(5000) CLI(CLI_exec cp /mnt/sda1/AutoScript/sacd_extract_160 /) CLI(CLI_exec insmod /lib/modules/2.6.35/BDP/splitter.ko) CLI(CLI_exec /sacd_extract_160 -S &) CLI(CLI_drv.ir.rx.sq 0xaf000) CLI(CLI_exec /bin/sh /mnt/sda1/AutoScript/mysh.sh) CLI(CLI_drv.ir.rx.sq 0xaf000) Explanation: This script is very similar to the first. At the end the drawer opens, you insert the SACD, a shell-script (mysh.sh) to rip the SACD will be executed, and finally the drawer opens. The resulting ISO can be found in the AutoScript directory. Contents of mysh.sh: sleep 50 cd /mnt/sda1/AutoScript ./sacd_extract_160 -I -i 127.0.0.1:2002 Explanation: Wait for 50 seconds, time enough to change the music settings (If anybody is aware about a solution to change the music settings inside AutoScript, please let me know) as described already. Then the client will be executed. 127.0.0.1 is the IP address of the localhost, which is a valid IP address even no network connection is available. Beware: mysh.sh has to be UNIX-style textfile, i.e. end-of-line has to be coded by a single line-feed (\n); DOS-style textfiles are encoding end-of line as a two-character carriage-return + line-feed (\r\n). To avoid trouble I enclosed the mysh.sh to be copied as-is to the thumb device: mysh.sh I assume that the reason for my problems in the beginning with the old firmware was the wrong encoded mysh.sh. Btw. AutoScript can be either style. Now we have my requested stand-alone scenario. Scenario 3: Rip via network For completeness: If you want to rip via the network your AutoScript is as follows: Contents of AutoScript: #MTKAT 0.xx script CLI(CLI_exec cp /mnt/sda1/AutoScript/sacd_extract_160 /) CLI(CLI_exec /sacd_extract_160 -S &) CLI(CLI_drv.ir.rx.sq 0xaf000) Again, don’t forget to change the music settings before you issue on your client machine a command like sacd_extract -i <ip-address of the BD-player>:2002 -I mysh.sh Les Habitants and Nexus3 2 Link to comment
klassikmann Posted March 9, 2018 Share Posted March 9, 2018 18 minutes ago, Phthalocyanine said: @klassikmann The mysh.sh script is a script of your own devising? mysh.sh looks so trivial, but it requested some trial and error to find a way the ISO will be stored on the thumb device instead of "/" crashing the player because of a full root filesystem. 22 minutes ago, Phthalocyanine said: Scenario 2 is a clever innovation. But do you have to re-insert the flashdrive for each new SACD to be ripped? I will test it soon. Link to comment
klassikmann Posted March 9, 2018 Share Posted March 9, 2018 1 hour ago, dtblair said: What are the error messages you get? mknod: /dev/sacd_read: File exists insmod: can't insert '/tmp/fileO8kvHH': File exists Link to comment
klassikmann Posted March 9, 2018 Share Posted March 9, 2018 1 hour ago, Phthalocyanine said: I don’t understand why one needs the -i 127.0.0.1:2002 for local ripping. I simply use ./sacd_extract_160 –I and get the same result. That's true. Thank you for the tip. 1 hour ago, Phthalocyanine said: I never get any such error messages. A typical rip looks like the following on the command line. (Perhaps you are getting those error messages because you are not including CLI(CLI_exec insmod /lib/modules/2.6.35/BDP/splitter.ko).) I got these "File exists" messages with and without the insmod in the AutoScript. Link to comment
klassikmann Posted March 10, 2018 Share Posted March 10, 2018 9 hours ago, Phthalocyanine said: I wonder if you will get those 2 error messages with my shorter command version. I used your shorter commands. Nexus3 1 Link to comment
klassikmann Posted March 10, 2018 Share Posted March 10, 2018 31 minutes ago, Phthalocyanine said: And did you still get those error messages? Yes. Two observations: 1. The error messages mknod: /dev/sacd_read: File exists insmod: can't insert '/tmp/filerFFmzY': File exists are refering to non-existing files neither the device-file nor the temp-file are present. 2. If I start the second "./sacd_extract_160 -I" there are no more such messages. But I do not longer brood over the messages. Nexus3 1 Link to comment
klassikmann Posted October 8, 2018 Share Posted October 8, 2018 @mindset First, a big thank you for releasing sacd_extract 0.3.9. In particular I found you incorporate the fix for issue #94 ("ID3 size coding") first seen in dbry's (David Bryant) fork of sacd_ripper. Second, in the SACDExtractGUI for processing "DSDIFF edit master" the checkbox "DST decompression" is greyed-out. This seems not to be correct. Link to comment
klassikmann Posted October 9, 2018 Share Posted October 9, 2018 4 hours ago, mindset said: Fixed. Current version: v0.1-3-g0d9165b0 Checked. Thank you. Link to comment
klassikmann Posted October 28, 2018 Share Posted October 28, 2018 3 hours ago, Malkana said: Btw the firmware links in the above post (malcolmstagg) are ‘broken’ and result in an error page. Perhaps http://www.mmnt.net/db/0/0/216.151.177.79/PUB/HAV/BDV/FW helps. "no responsibility is taken for the correctness of this information". I only did one check regarding the firmware of my S490. klassikmann Link to comment
klassikmann Posted October 29, 2018 Share Posted October 29, 2018 2 hours ago, Malkana said: Hi Klassikmann Thanks for the link..do you have a workable link for the M11.R.0422 firmware by any chance? Unfortunately not. btw.: M11.R.0422 is a firmware for the S390? Sometimes it is meaningful to look for an even older firmware. According to https://www.avforums.com/threads/cinavia-on-sony-bdp-s390.1732497/#post-18366108 starting with M11.R.0147 the S390 contains the Cinavia protection. technology. Link to comment
klassikmann Posted October 29, 2018 Share Posted October 29, 2018 20 minutes ago, Malkana said: Do you know why the M11 s390 firmware in this link http://www.malcolmstagg.com/bdp-s390-downgrade.html that Phthalocyanine posted is broken? If you have a look at http://www.mmnt.net/db/0/1/ftp.vaio-link.com/PUB/HAV/BDP/FW/ the firmware entries point to ftp://ftp.vaio-link.com/PUB/HAV/BDP/FW/ and ftp.vaio-link.com is no longer online. Link to comment
Popular Post klassikmann Posted June 29, 2020 Popular Post Share Posted June 29, 2020 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 : I took the ISO of a hybrid SACD and generated a "DSDIFF edit master" (DFF, 56 min), 2CH with DST decompression using sacd_extract. The .dff has been packed to a .wv with wavpack 5.3.0 . I inserted the .wv into MKVToolNix GUI (v48) as input source file. 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). mkvextract delivered six .wv files. 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! MikeyFresh and Nexus3 1 1 Link to comment
klassikmann Posted June 30, 2020 Share Posted June 30, 2020 @Nexus3 Thank you for the additional informations. This discovery will be a valuable part of my audio software toolbox. But today I have no urgent need anymore to cut and merge DSD files. An explanation would be more than slightly off-topic. Nexus3 1 Link to comment
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now