• VLAN. At a minimum, your switch will need to support VLAN. A traditional switch is like a big hall, when there's a lot of people pack in the hall, and everybody tries to speak/listen, things get busy. A switch with VLAN is like a big hall with multiple sound proofed private room - it makes things more managable.
  
• IGMP v2/v3. I'm still not entirely sure if you'd need IGMP v2/v3 support or not. There are two types of network traffic. Unicast (1 to 1), and multicast (1 to many). If the network audio out of this Merging audio device is multicast, then yes you'd need IGMP. Otherwise this works the same way as other unicast network audio.
  
  Logitech Media Server and Squeezelite are unicast in nature. This just means point to point (one source, one destination) If I have ten sqeezelites and I want them all to receive the same music at the same time. Unicasting will create ten data and ten control streams on the network, all with the exact same data.
  
  Multicasting works differently. It creates just a single data stream and send it to all the ports on the network. Any device on the network can work on this single stream of data. There is no data duplication.
  
  Both distribution methods are limited by network bandwidth. Assume we have a ceiling of 1000 mbps, this means network traffic going up or down a network port cannot exceed this magic 1000 number). As an example, if the unicast stream is 100 mbps, the maxium number of devices that'd work will be 9 (9 x 100 = 900 + overheads).
  
  For the same multicast stream of 100 mbps, there is no device limit. However, every port on your network is now left with 900 Mbps for everything else. This "one-to-many" do not scale well. What if you want to multicast 10 streams at 100 mbps to all the devices (many-to-many)? On a dumb switch, the network will fail.
  
  This is where IGMP comes in. Multicast traffic on a dumb switch will be broadcasted to all network ports. But the same traffic on a IGMP capable switch will only be sent to ports that are specifically asking for this traffic. An analogy, a dumb switch is like tuning to a radio station that is broadcasting 10 songs all playing all at once; you do not get to choose, the songs are force fed down to you. On a smart switch (one that supports IGMP Querier), you tell the switch you want song 1, 3 and 5, and it'll only broadcast that 3 songs (still all playing all at once. But you're now getting only the songs you want, instead of everything).
  
• CoS/QoS: Class Of Service or Quality of Service. This is a configuration setting that priorities one type of network over another. Think of this as queue jumping. In traditional networks, packets in and out follow the order as they come in. This is orderly but can slow things down. CoS allows you to jump the queue. An analogy will be airline boarding. Economy class has a long line and you have to wait patiently to board. First class passengers on the other hand, have a much shorter queue and they board the plane immediately.
  
• Network cabling. While you don't have to get expensive cables. You have to make sure the cable is 100% fault free - no CRC errors.
  

1. 0000276: [web-app] Show a notice if ALSA device no longer matches what is found in the system
   
2. 0000280: [players] MPD: Add albumartist id3tag to metadata_to_use (v0.20 and v0.21 only)
   
3. 0000281: [players] Improved HQPlayer installation script
   
4. 0000283: [web-app] Update NAA for AMD64 to 3.5.5-39 (There is no i386 update)
   
5. 0000284: [web-app] Fixed activation sequence when names or emails have accents/punctuation
   
6. 0000285: [web-app] Do not show kernel tweaks in Raspberry Pi, as there's no tweak to do
   
7. 0000286: [players] Fixed problem where you cannot install/uninstall HQPlayer NAA in i386 and Raspberry Pi platforms
   
8. 0000287: [web-app] Fixed incorrect Thread count in CPU panel in dashboard
   
9. 0000288: [web-app] Free Edition: Can now mount multiple drives/paths in library
   
10. 0000289: [web-service] Free Edition: Can now modify MTU in networks
    
11. 0000290: [web-app] Change streaming mode from "PCM" to native PCM/DSD
    
12. 0000291: [web-service] Introduce initial Ravenna support
    
13. 0000292: [players] Update MPD v0.20.x series to 0.21.5
    

(03-Mar-2019, 03:29 PM)Bromf Wrote: RPI3

Decrypting File: snakeoil-1.1.3-armv7l.fw

Cannot decompress file.
Uploaded file appears to be an invalid firmware.


Not for ARM...?

(03-Mar-2019, 05:51 PM)Bromf Wrote: Third try worked....though a couple of reboots via ssh needed...
Rest reloaded 54 times then 32 times then final reboot brought up the webpage and all seems to work..

(03-Mar-2019, 10:01 AM)agent_kith Wrote: 0000285: [web-app] Do not show kernel tweaks in Raspberry Pi, as there's no tweak to do

(07-Mar-2019, 05:11 AM)Evach Wrote: Hi Agent Kith, thanks again for your work ;-)
I try to find the file MPD.CONF for updating tidal account, but without any success with SSH session, could help me to find this configuration file? Where is the correct path for Snakeoil, because the common path etc/mpd.conf is not available

The only mpd.conf i found is "/var/www/scratch/mpd.conf"

(07-Mar-2019, 09:46 AM)agent_kith Wrote: The file is /var/www/players/mpd-v21/mpd.conf.template

Modify the file above. Everytime you start the player, the scripts will use that template to generate /var/www/scratch/mpd.conf. Another way is to use the advanced audio configuration option.

Right now everytime you apply a new firmware update, your changes will disappear if you use the first method.

I'm working on improving the GUI in Gear Isolation to make this better. Stay tuned.  

• Install Fiddler and start it.
  
• In Fiddler, click Tools > Options > Decrypt HTTPS Traffic
  
• Install TIDAL for Windows and start it
  
• In Fiddler, look for requests to
  Code:

  api.tidal.com or similar
  Click a request, then on the right, click Inspectors > Headers. Underneath Miscellaneous you'll see
  
  Code:

  X-Tidal-Token
  This is a TIDAL Token you can use.