Jump to content

André Gosselin

Members
  • Content Count

    112
  • Joined

  • Last visited

About André Gosselin

  • Rank
    Freshman Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Jesus, Thats's exactly what I am doing now. My NUC server (Win10) is set to100 Mbps Full Duplex, and streaming is performing OK, no stuttering. I looked at the Flow Control in the Win10 Control Panel, and it is set at "Rx & Tx Enabled" . In fact, I never touched that setting since I got my Nuc i5. Cheers, André
  2. Could you or any other user (by chance!) try to stream through a 2.8 urendu a very high rate DSD file (DSD256 or DSD512) to a USB dac accepting native DSD (not DOP) like the iFi Pro iDSD ? In my case, 2.7 plays fine in this setup. However, 2.8 streams erratically with an unbearable stuttering. Regards to all who may hep here
  3. Thanks @barrowsfor your advice.Very nice of you. I was able to get the 2.8 card to boot, and gave another try to the software update in SO.com. Unfortunately it did not complete. Here is the output : My orendu had shut down, as it did before I will pm Jesus for further advice. Thanks again.
  4. I did what @vortecjrsuggested.I went to SonicOrbiter.com > Apps .Software Manager, clicked update, and unfortunately the update did not complete. Looking at the back of my opticalrendu, I saw it had shut off. Repeated a few times the sequence "Disconnect/reconnect/ wait a long time" had no success, as the red led went on permanently and the unit eventually shuts off at the end. The only way I found to bring the orendu 2.8 back to life was to take a detour through the previous SD 2.7 card, eg: 1- disconnect the orendu 2- remove the SD 2.8 card 3- put back the previous SD 2.7 card 4- verify settings in Sonicorbiter.com 5- Play my DSD 128 album both through Roon and MPD/DLNA to make sure that the orendu 2.7 was correctly functionning 6- disconnect, eject SD 2.7 card, reinstall SD 2.8 card, reconnect. Only then was I able to get SD 2.8 card to boot. I tried an update a second time, but with the same sad results. Repeated above procedure to get a booting SD 2,8 card. I then went to SonicOrbiter.com to make sure to resave (for the nth time!) the MPD/DLNA and RoonReady settings. The orendu shut off again during the process. I repeated he laborious process above to get orendu 2,8 to boot again, went to the RoonReady settings to check they were OK (no save this time!), went to the Audio App Switcher to make sure RoonReady was on. I then tried to play theDSD64 version of my album through Roon. Everything was OK. (Remember that yesterday I did not have time to try streaming the DSD64 version). I next tried to experiment with MPD/DLNA. Went to SonicOrbiter.com to check DLNA settings (no save!) and Audio App switcher to activate MPD/DLNA. I streamed the DSD64 version of the album with no issue. I next tried to stream the DSD128 version. My orendu played for about 2 minutes, then it shut off as it did yesterday when playing the same DSD128 version through Roon. My feeling is that RoonReady has nothing to do here, IMHO As a final step, I reinstalled the SD 2.7 card, and rebooted my orendu with no issue. Everything now plays correcly as it was the case since I received my orendu during the Black Friday pre-sale. I love my orendu, please be sure. I will leave it like that for the time being. @barrows Thanks for your advice, but I think I have honestly tried everything you suggested, without success. Yes it is odd, but that is the way it is, believe me. Reinstall the 2,7 card, and everything steams perfectly, PCM & DSD. Install the 2,8 card,and problems start to accumulate: difficulties booting the card, failure to update the software and maneuver through SonicOrbiter.com, unit shutting off, DSD64 playing but not DSD128, etc. If the orendu with SD 2.7 card works perfectly, this seems to indicate the hardware is OK. If simply installing SD 2.8 generate all those problems on my system, may I humbly suggest that the 2.8 update is somewhat responsible for that ? I think your system is much more elaborate than mine with the top of the line Rendu model Are you running the exact same SO version that I have, or is it a special version ? Could someone advise on what to do next ? Could Sonore remotely logging in on my system help, running diagnstics, etc ? I am ready to provide any help . Regards
  5. I received today a new opticalrendu SD 2.8 card, as a replacement for a previous bad card which did not boot. The new card boots, and was carefully set up using the exact same settings as used on my previous SD2.7 card, and making sure all setings were properly saved. The new card is correctly seen in SonicOrbiter.com . The orendu is powered by a SGC 7V/50W LPS, and connected by USB to a SimAudio Moon 780D dac. I am however running into a new set of problems. With SD 2.8 installed and streaming a local DSD 128 track through Roon .the track plays for about 2-3 minutes, then the orendu simply shuts off. After disconnecting the orendu and powering it on again, the red led at the back stays on constantly, and the orendu eventually shuts off. If I reinstall the SD 2.7 card, the same track plays without any problems. If I remove the SD 2.7 card and reinstall the SD 2.8 card, I note that I have no problem playing (through Roon) a 176/24 version of the track. Trying again to play the DSD128 version produces the same problem as before: the orendu shuts off after a couple of minutes and refuses to boot anymore after a disconnect/reconnect sequence. I have attached screenshots of my RoonReady settings in SonicOrbiter, and in Roon Device setup. In summary: - The issue occurs only with SD 2.8 card - The issue occurs only with DSD 128 tracks. I did not try with DSD 64 tracks. I could not try with DSD256 and DSD 512, because my DAC limits me to DSD 128/DOP. - This issue can be replicated at will on my system Any help would be greatly appreciated. I will be glad to contribute any needed information.
  6. This would not work anyway as the ER B side is 100 Mbits only and the optical module is 1 GBit only.
  7. Do you mean OpticalRendu connected to the fiber port of EtherRegen? Or are you using an opticalModule between the ER fiber port and the ultraRendu ? Please clarify
  8. @lxgreen Please see my post on Nov.10 about a very similar interrogation to the one you have. The answer by @JohnSwenson was unequivocal: Posted November 10 What you are describing is probably the best way to go. In this case most of the packets are going to the endpoints, hence crossing the moat, thus there should be little interaction between endpoints. That is certainly how I would connect things. John S. It appears crystal clear to me that you can connect more than one audio equipment to the A side, if everything goes through the moat from the router on the B side, and the NAS/music server is connected to the router (and, I guess, provided that PS are not shared between endpoints on the A side.). "That is the way I would connect things", to quote John.
  9. My question was not about whether Linux can support streaming in Native DSD vs DoP. My question was about the future SonicOrbiter 2.8 linux kernel support for native DSD on USB DACs equipped with the ESS ES90186 Sabre 32 chip,like my SimAudio 780Dv2. Currently, in SonicOrbiter 2.7, native DSD is not supported for this DAC, and SonicOrbiter must be parametrized to stream DSD using DoP, which means streaming at most DSD128 given that this DAC cannot go above 386 kHz. I hope my concern is clearer now, and that native DSD will be supported on my SimAudio 780Dv2 DAC in SonicOrbiter 2.8. Regards, André
  10. Do you know if the linux kernel modernization will include support for native DSD through usb on the ESS ES90186 Sabre 32 chip ? Up to now on SonicOrbiter, DSD must be streamed in DOP on usb, which limits DSD streams to dsd128. Native dsd256 streaming on usb is possible on Windows, but with the use of a special ASIO driver. Being able have the same for linux would be nice. Regards André
  11. In my current network setup, a NAS is connected to my router upstairs. An ethernet cable goes downstairs to an unmanaged switch in my music room. To the switch are connected two different renderers. 1- sonore optical module/optical rendu combo, and 2- Simaudio 780Dv2 with an internal Mind2 ethernet module . No other equipment connects to the switch. Reading the ER documentation, I see that the ER can be operated in "backward" mode with the connection to a router on the B side, and the SFP module on the A side connected by optical cable to the OpticalRendu. The manual suggests than nothing else be connected to the A side, but I think I saw a post by @JohnSwenson where he limited this restraint to non-audio equipment. So it would not be harmful to connect also the Simaudio 780Dv2 to the A side, but no additional non-audio equipment In short, I am hoping that using an ER, I could simplify my current setup by : - getting rid of my unmanaged switch and replacing it by the ER - removing the optical module and connecting to the OpticalRendu from the SFP on the A side - connecting the Simaudio 780Dv2 to a second port of the A side - having only those 2 audio connections to the A side, and nothing else - running a cable from my router to the ER B side - having all non-audio equipment (NAS, PC's, etc) connected to the router and not to the ER Could you comment on the above setup ? Is it a sound one ? In particular, would the 2nd audio equipment (Simaudio 780Dv2) connected to the A side benefit from the ER upstream isolation, or would it harm the SQ of the OpticalRendu ? Any advice would be greatly appreciated.
  12. I had the same issues on a Win10 platform. To solve them, I had to first uninstall the previous version, then execute a fresh install. After that, everything went smoothly.
×
×
  • Create New...