I am writing to report an issue with my ROSE RS130 streamer. I believe this may be a firmware or software bug related to output settings. According to the documentation, the output groups should be configurable independently. However, in my case the settings are synchronized across groups. When I change output parameters for one output group, the same settings are applied synchronously to all output groups.
The affected settings are:
- PCM Resampling
- DSD Mode
- MQA
The groups do not appear to keep independent values, although the documentation suggests they should be configurable separately. I have tried changing the settings both on the RS130 itself and through the ROSE Connect app, but the behavior is the same in both cases. The issue remains the same: whenever I modify the settings for one output group, the same parameters are mirrored to the other groups. I am unable to keep separate values for each group, even though the documentation suggests they should be independent.
What I have already tried:
- Changed settings from the RS130 screen
- Changed settings from ROSE Connect
- Rechecked after saving the configuration
- Verified that the behavior is identical in both interfaces
- Factory reset and repeat the previous points
This is very inconvenient, since my setup uses two DACs. And they have different settings:
- The DAC is built into the preamplifier-processor Integra DRC-R1 (hi-end version Onkyo PR-RZ5100), connect via Coaxial Cable and HDMI
- The DAC is an external Hegel D-50, connect via USB
Device information:
- Model: ROSE RS130
- Firmware version: 5.9.09
- Control method used: RS130 screen and ROSE Connect app
Connected output type: USB / Coaxial / HDMI
Expected behavior:
- Each output group should retain its own independent settings.
Actual behavior:
Settings are synchronized across all output groups.
If this is a known limitation, I would appreciate clarification. Could you please confirm:
- Whether independent settings for each output group are supported on the RS130.
- Whether this is a known issue in the current firmware.
- Whether a firmware update or workaround exists.
- Could a repeat firmware update solve this problem? If true, where can I find the firmware for installation via USB?
- Can an XMOS/Audio MCU update solve this problem? If true, where can I find the XMOS/MCU Update option file for installation via USB?