(01-03-2021, 06:52 PM)TheOldPresbyope Wrote: @lamode
So I count 4 issues:
- "missing" menu - I'll let Tim or others address this one.
- volume control defaulting to 100 percent when playing a DSD track through Audirvana to moOde. This is hard to assess. By its nature, DSD-encoded audio has to be passed to the DAC without any modification (including not any software volume control). You haven't said how you have configured volume control on any of the components you mention.
- loss of audio and of contact with moOde. I assume from other things you say that this occurs while using moOde as a UPnP renderer. I would not be surprised if this is a problem with your network and not your moOde player, but you don't mention how your moOde player is connected.
- an encryption key conflict in your SSH client on your MacBook. This is down to you and your use of SSH with various moOde installations and RPis. The brute-force solution is to delete the file /Users/abc/.ssh/known_hosts and let SSH rebuild it as you log into hosts anew. This also deletes keys you have stored for use with other systems so it may not be an acceptable solution to you. Alternatively, you could edit the known_hosts file to delete only the offending line 3.
For further discussion of issues 2 and 3, it would be helpful to include a copy of your system info output.
Regards,
Kent
Sorry, I realize that there wasn't much detail provided.
Issue 2: I have "software volume" DE-selected on Audirvana. That's the only relevant control I can find on the Audirvana side.
Issue 3: I was using Moode 6.x for 6 months or so and found it to be very stable as a UPnP renderer. Since upgrading, I have had frequent disconnects in the middle of playback, inability to even SSH the Pi for some periods, and Audirvana freezes as well (same version of Audirvana which was stable with 6.x). The Mac and network haven't changed at all.
Issue 4: I'm not sure that I understood your reply as I have only one RPi and one instance of Moode. I did brute force it and haven't had an issue since (although it was fixed only 24 hours ago) but I thought it was worth mentioning in case it crops up with other users too.
