gumby

Thanks for the explanation!

Just out of curiosity, I tried ripping a disk without using the USB drive. That is, I just powered up the OPPO 105 and loaded a SACD in the normal fashion, executed the SACD.cmd file and the disk was ripped to an ISO file. Has anybody else tried this? So it appears the information on the USB drive is stored in the OPPO. I am wondering if is stored in permanent memory or some sort of temporary memory? What would happen after a true power outage?

I discovered this thread yesterday. I copied the information on Grill's post #29 to a word file and proceeded to successfully rip a disc on my OPPO 105 without using Telnet. The whole process, from the time I discovered Grill's post until I had an ISO file took less than an hour. I did not even bother reading the rest of the posts until I was done. A pdf copy of Grill's instruction is attached. Thank you. OPPO 105 Ripping Instructions_29 July 2016.pdf

Hi Bogi, Thanks for the response. It is a great tool. Thanks for sharing it.

I couple suggestions, or possibly questions. 1) It appear you can batch extract files from more than one ISO by highlighting several files and right clicking to execute the "SACD ISO to DSF per track" command. The conversions run in parallel. It seems that it might be better to execute these in series. It probably takes about the same amount of time, but doing more than 3 or 4 at once is quite a computational chore, at least for MCH extractions and particularly for the conversion step to DSF. Generally, if I run a batch using the Mr. Wicked original tool, I start them and leave and come back later anyway. Running them in series is going to allow (I think) a larger batch to get done. 2) Is it possible to set up (edit) the config file to extract both the stereo and MCH files with one command (possibly in series) and dump the extracted files in two separate folders. I tried removing the # from in front of both channel commands and it did the stereo and quit. So, currently, it appears the config file needs to be edited every time in order to switch back and forth between the Stereo and MCH conversion.

Pedro, Well this is a real head scratcher. This latest information does not explain the photos you provided in an earlier post showing the very large files. After mulling this over for a while, I think there are so many things that could be wrong. This is a very long post, but is difficult to ask “follow up” questions in this manner, so I decided to just put down some observations/questions that might help you sort this out. My apologies if you already know some of this. 1) I need to make sure we are saying the same thing when we say “library.” There is your physical library (the actual files themselves) and the virtual/logical libraries you can create with JRiver by telling it which of the files in your physical library you want to JRiver to use for playback. Unless noted otherwise, I am going to assume that “library” means your physical library, not a logical library you have defined using JRiver. 2) If you are just starting out and not that familiar with JRiver,you really should keep the physical library entirely on one device, organized in directories if necessary to manage the information. You can then tell JRiver which directories to include in your “JRiver” library as you have referred to it. For example, as described in item No. 6 below you may want to separate the DSD files from the PCM files. 3) You said you have "3 libraries." I am not sure what you meant by this. I am concerned that you have your physical library spread over 3 devices and as you have tried to convert these DSF files (DSD) to PCM,you have created other copies. I just did a test and “converted” a stereo DSF file to a 5.1 (6 channel) DSF file using JRiver. The resulting file was 3 times larger than the original stereo file. This can happen if you have your DSP options set to source 5.1 channels instead of “no of channels” or 2 channels, and the encoder is set to DSD instead of FLAC. If you are new to JRiver, it would be easy to have done this. It took a couple minutes to convert one 5 minute track. So, if you remember the conversion of the whole album taking a long time, this may be what has happened. 4) Without knowing how you have connected everything, where you are keeping you physical library, and how you are controlling playback, it is hard to say if this is what happened. If you are using JRiver to control playback and pointed it at all of your physical libraries, and there are copies of the same music in different file types, there could be issues depending on how you have instructed JRiver to playback the files. 5) I obtained a copy of the user manual for the N50a. The N50a does not appear to playback DSD files. So, the files you are showing in your latest post are not going to work because they are clearly stereo DSD. Can you confirm this is a PCM only DAC? 6) Assuming you are using JRiver to control playback you can instruct it to convert to DSD to PCM at the time of playback. Unless I misread the manual, I assume this is what you are doing. Alternately, you can convert them “offline” and keep two copies of the music. The DSD files would be an archive and the PCM copy would be used for playback. See item No. 2 above. As a novice, I would highly recommend converting offline and omitting the DSD copies from your logical“JRiver” library. 6) It appears there are four ways to feed the N50a digital files. Over a network (it is DLNA compliant), optical, SPDIF or USB. Sending a sketch of how your network is configured and how the WD MyCloud dives are connected and being used would be helpful in ruling out potential problems. 7) You say you are ripping to 64 DSD. I assume you mean ripping redbook CD’s? As noted above, the N50a appears to be strictly 24bit/192 PCM DAC. There is likely no benefit to ripping your redbook CD’s to DSD 64. All you are doing is creating much larger files and adding noise. The musical information contained in thefiles is unchanged. Further, these DSD files need to get converted back to PCM (in one of the ways described above) inorder to played on the N50a. So, you have two conversions that can alter the original information and it is hard to imagine how this would improve things. Some may disagree, but I think it best to just rip your redbook CD’s to 16 bit, 44.1 kHz PCM. That is all the information that is there anyway. 9) It appears the N50a can upsample to 192khz, so you canexperiment with upsampling these CD quality files and determine if you can hear a difference. 10) The MyCloud Mirror is a RAID device. This actually has a greater probability of failure than a single drive because the RAID controller can fail, as well as one of the drives. I am not sure you will be able to get to the information on either of the drives if the RAID controller fails. The advantage of this device is that you can continue to listen to music if one drive fails. It gives you time to fix the other drive, although in this case I am not sure you can swap out the drives in this unit. If so, this would be a good drive to put the working copy of your physical library on, but the second "mirrored" drive is not really a backup unless you can remove it and use it. I would use the other WD drive to store a backup copy of your physical library.

Pedro, Although it is unlikely, I should point out that you may have two multichannel tracks (1 & 3) and one stereo track (track 2). Track 2 was not highlighted in your previous screenshot so I could not rule that out.

Pedro, These files do not appear to be same as the ones you showed us previously. They are smaller. Based on bit rate and file size (1.0 GB) for Track 2, these are stereo DSF files. My 5 channel Track 2 is 2.59 GB. Divide that by 2.5 and you get 1.0 GB for the same track in stereo, which is what you have here. The files you were showing us in your previous screenshots must be in a different location than these and must be different. If the others are 6 channels the file sizes for each track will different by a factor of 3. Yes, I have no problem playing my files through a multichannel DAC connected to computer running JRiver. My files are on a NAS located in another part of the house. JRiver retrieves the files from the NAS and pushes them to the DAC. To see more metadata for your file, click on the little squarish icon to the left of the word "Tag" on the upper left side of your screen. A menu will drop down. Select "show all tags." A long list of file properties will appear. Most will have no information associated with them....that is no tag. If you scroll through the list you should find "Channels" with a number showing to the right of "Channels"

pedroboe, I have this album in multichannel (5 channels) DSF. I downloaded it from Native DSD. Attached is a screenshot of the file size for Track 3. It is 1.44 GB. I think you have a 6 channel version. 6/5 = 1.2 and 1.2 X 1.44 = 1.728, or 1.73 as showing on your system. I obtained a similar result for Track 1 (also attached.) The other thing that is confusing to me is how dbPoweramp is seeing information on a DSD file? It really can't so it is probably "guessing" that it is a stereo file and therefore 24/96? You say you are using JRiver on your PC. Look at the metadata for the tracks in JRiver. It should indicate the number of channels and the bit rate would more 16,000 not 4,500

I have had this problem. Not sure I remember how I fixed it, but try deleting all entries in the "album artist" field. You can have different artists for different tracks in the "artist" field for each track. Then make sure "album artist (auto)" says multiple artists, or something like that, for all tracks. I think the program is set up to recognize two different albums that have the same name but are by different artists. This creates more problems than it is worth. An album is an album and the album artist's name can be added to the album title if necessary to distinguish Beethoven's Symphony No. 2 from Brahm's.

I now realize we were not talking about the same thing. I don't save "playlists." I was referring to "Playing Now" list. I have now encountered another issue deleting tracks from "Playing Now" using JRemote. I can only delete one, or sometimes two, tracks without crashing the program. Has anybody else had this problem? I am running JRemote 3.09 on iPad mini, latest JRiver 19 on CAPS Zuma, and files are on a remote NAS over a wired network.

Yes!

It takes a while to load the files, but it is working for me. I miss the paper clip but I cannot remember if it loaded faster.

Yes, but deleting song by song is the part that should not be required. If all the songs are listed together, it should be possible to delete the whole album by deleting the first track. LINN's Kinsky control point does this by providing an option to "Group playlist tracks." When set this way album art shows for first track only and deleting that track deletes all other tracks from the album listed directly below it. Other tracks from the album that are located elsewhere in the playlist are unaffected. Turn off "Group playlist tracks" and the application shows album art for each track, which must be deleted individually as is currently the case with JRemote.

It is good to get the album art size corrected but now it appears the alphabet paging feature on the right side of the window has been replaced with about 24 microscopic dots. I think I much prefer the legible letters. They did not take up that much screen space. Also, there is still no way to delete an album from a playlist. This is a feature that would be nice to have.