Affichage hiérarchique

Le dom · Il y a 6 heures

D'accord, il n'y a donc qu'une carte Ethernet.
Et où est connectée cette carte Ethernet?

Facel

C'est le port ethernet du RPI4, ilest connecté directement sur mon switch
Je comptais utiliser mon adaptateur USB/Ethernet dans un 2eme temps après validation du bon fonctionnement.
Avec un Host Windows Asio la target connectée via switch fonctionne

Le dom · Il y a 2 heures

OK, peux-tu me montrer le contenu du fichier diretta-renderer.conf qui se trouve dans /opt/diretta-renderer-upnp/ ?

Ainsi que le log debug en activant l’option verbose.

Facel · Il y a 49 minutes

Log debug

Code :
Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: ════════════════════════════════════════════════════════

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]:  Starting Diretta UPnP Renderer

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: ════════════════════════════════════════════════════════

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: Configuration:

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]:  Target:          1

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]:  Network Interface: auto-detect

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: Command:

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]:  /opt/diretta-renderer-upnp/DirettaRendererUPnP --target 1 --port 4005

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: ════════════════════════════════════════════════════════

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.312] [DirettaRenderer] No Diretta Target found!

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.312] [DirettaRenderer] Run: ./bin/DirettaRendererUPnP --list-targets

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.312] Failed to start renderer

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219] ═══════════════════════════════════════════════════════

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219]  Diretta UPnP Renderer v2.0.3

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219] ═══════════════════════════════════════════════════════

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219] Configuration:

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219]  Name:    Diretta Renderer

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219]  Port:    4005

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.219]  Gapless:  enabled

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.220]  UUID:    diretta-renderer-45f2ec469457c66b

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.220] Starting renderer...

Feb 17 18:38:58 RPI-DirettaUPnP diretta-renderer[8063]: [18:38:58.220] [DirettaRenderer] Checking Diretta Target...

Feb 17 18:38:58 RPI-DirettaUPnP systemd[1]: diretta-renderer.service: Main process exited, code=exited, status=1/FAILURE

Feb 17 18:38:58 RPI-DirettaUPnP systemd[1]: diretta-renderer.service: Failed with result 'exit-code'.

Feb 17 18:39:03 RPI-DirettaUPnP systemd[1]: diretta-renderer.service: Scheduled restart job, restart counter is at 3001.

Feb 17 18:39:03 RPI-DirettaUPnP systemd[1]: Started diretta-renderer.service - Diretta UPnP Renderer.

fichier diretta-renderer.conf

Code :
# Diretta UPnP Renderer Configuration

#

# This file is sourced by the systemd service unit.

# Modify these values to change renderer behavior.

#

# After changing values, reload:

#  sudo systemctl daemon-reload

#  sudo systemctl restart diretta-renderer

# ============================================================================

# BASIC SETTINGS

# ============================================================================

# Target Diretta device number (1 = first found)

TARGET=1

#TARGET_IP=192.168.1.25

# UPnP port (default: 4005)

PORT=4005

# Gapless playback

# Add "--no-gapless" to disable, leave empty to enable

GAPLESS=""

# Verbose logging

# Add "--verbose" to enable debug logs, leave empty for normal output

VERBOSE=""

# ============================================================================

# NETWORK INTERFACE SETTINGS (for multi-homed systems)

# ============================================================================

#

# For systems with multiple network interfaces (e.g., 3-tier architecture),

# specify which interface to use for UPnP discovery and SSDP broadcasts.

#

# This is essential for proper operation when you have:

#  - Multiple network cards (eth0, eth1, eno1, eno2, etc.)

#  - VPN connections

#  - Bridged networks

#  - Separate control and audio networks

#

# IMPORTANT: Choose the interface connected to your UPnP control points

#            (e.g., JPlay, Roon, BubbleUPnP), NOT the Diretta audio network!

#

# Examples:

#  NETWORK_INTERFACE="eth0"          # Use interface name (recommended)

#  NETWORK_INTERFACE="192.168.1.10"  # Use specific IP address

#  NETWORK_INTERFACE=""              # Auto-detect (default)

#

# Common scenarios:

#

#  Single network (default):

#    NETWORK_INTERFACE=""

#

#  3-tier architecture (recommended by dsnyder):

#    Control Points: 192.168.1.x on eth0

#    Host:          192.168.1.10 (eth0) + 192.168.2.10 (eth1)

#    Diretta DAC:  192.168.2.100 on eth1

#

#    Use: NETWORK_INTERFACE="eth0"

#          TARGET should point to 192.168.2.100

#

#  VPN + Local network:

#    Local:  192.168.1.x on eth0

#    VPN:    10.0.0.x on tun0

#

#    Use: NETWORK_INTERFACE="eth0" (for local control points)

#

# To list your network interfaces:

#  ip link show

#  ip addr show

#

# Modification Copilot = indiquer le nom de l'interface :eth0

NETWORK_INTERFACE=""

#NETWORK_INTERFACE="eth0"

# ============================================================================

# ADVANCED DIRETTA SDK SETTINGS

# ============================================================================

# Leave commented to use defaults. Uncomment and modify to override.

# Thread Mode (bitmask - add values together)

# Default: 1 (Critical only)

#

# Available flags:

#  1    = Critical (REALTIME priority)

#  2    = NoShortSleep

#  4    = NoSleep4Core

#  8    = SocketNoBlock

#  16    = OccupiedCPU

#  32    = FEEDBACK (moving average)

#  64    = FEEDBACK (moving average)

#  128  = FEEDBACK (moving average)

#  256  = NOFASTFEEDBACK

#  512  = IDLEONE

#  1024  = IDLEALL

#  2048  = NOSLEEPFORCE

#  4096  = LIMITRESEND

#  8192  = NOJUMBOFRAME

#  16384 = NOFIREWALL

#  32768 = NORAWSOCKET

#

# Examples:

#  1    = Default (Critical only)

#  17    = Critical + OccupiedCPU (1+16)

#  33    = Critical + FEEDBACK32 (1+32)

#

#THREAD_MODE=1

# Transfer Packet Cycle Maximum Time (microseconds)

# Default: 10000 (10ms)

# Range: 333-10000

#CYCLE_TIME=10000

# Transfer Packet Cycle Minimum Time (microseconds)

# Only used in random mode

# Default: 333

#CYCLE_MIN_TIME=333

# Information Packet Cycle Time (microseconds)

# Default: 5000 (5ms)

#INFO_CYCLE=5000

# MTU Override (bytes)

# Default: auto-detect

# Common values: 1500 (standard), 9000 (jumbo), 16128 (max jumbo)

#MTU_OVERRIDE=""

# ============================================================================

# TROUBLESHOOTING

# ============================================================================

#

#

# Problem: Renderer not discovered by control points in 3-tier setup

# Solution: Set NETWORK_INTERFACE to the interface with control points

#          Example: NETWORK_INTERFACE="eth0"

#

# Problem: How to find which interface to use?

# Solution: Run: ip addr show

#          Look for the IP on the same subnet as your control points

#

# Problem: Renderer discovered but no audio

# Solution: Check TARGET points to correct Diretta DAC IP on audio network

#

# For more help: https://github.com/cometdom/DirettaRendererUPnP/issues