Welcome, Guest
Username: Password: Remember me
NOTE: This forum is community powered. Please be mindful that long time community members are here to help as part of a community effort. If you have a specific issue (e.g. hardware, failure), please use our tech support portal (Support menu - > Contact Us). Thanks a lot of your help in making a better community. :-)

TOPIC: DDRC-24 - Erratic behaviour with remote

DDRC-24 - Erratic behaviour with remote 3 months 3 weeks ago #40196

  • Tony_J
  • Tony_J's Avatar
  • Offline
  • Junior Boarder
  • Posts: 26
  • Thank you received: 5
  • Karma: 0
I'm finding that the remote sometimes works as it should, and sometimes not. For example, I can use it to enable/disable Dirac Live, and then if I press the Mute button, Dirac Live gets toggled instead. Sometimes the volume up/down works fine, and then pressing volume up reduces the volume.

Similarly, sometimes the DDRC-24 plugin sometimes updates to show changes made from the remote, and sometimes it doesn't.

Any clues please...?
The administrator has disabled public write access.

DDRC-24 - Erratic behaviour with remote 3 months 3 weeks ago #40259

  • EdHowarth
  • EdHowarth's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 5
  • Thank you received: 1
  • Karma: 0
Can I add to this? Exactly the same, sometimes the remote's volume changes the source input. Only very occasionally does the laptop screen update the master volume when it's been altered with the remote.
The administrator has disabled public write access.

DDRC-24 - Erratic behaviour with remote 3 months 2 weeks ago #40272

  • Tony_J
  • Tony_J's Avatar
  • Offline
  • Junior Boarder
  • Posts: 26
  • Thank you received: 5
  • Karma: 0
I'm a bit surprised that I haven't heard from @devteam on this one - the problem seems to be easily reproducible and not only on my system. Some more info: When the DDRC-24 plugin is disconnected from the DDRC-24, the remote works as it should; when I connect the plugin, the erratic behaviour described above occurs.
The administrator has disabled public write access.

DDRC-24 - Erratic behaviour with remote 3 months 2 weeks ago #40274

  • dreite
  • dreite's Avatar
  • Offline
  • Platinum Boarder
  • Posts: 1217
  • Thank you received: 608
  • Karma: 82
That sounds like normal operation to me.
When you have the USB cable connected there's a conflict on which device has priority operating the unit. The remote finishes in second place in that case.

Many of the miniDSP units exhibit this characteristic and it's been queried numerous times. They probably should make this more clear in the user manuals.

Unplug your computer and you should be fine with the remote operation.

Dave.
The administrator has disabled public write access.
The following user(s) said Thank You: Tony_J

DDRC-24 - Erratic behaviour with remote 3 months 2 weeks ago #40275

  • Tony_J
  • Tony_J's Avatar
  • Offline
  • Junior Boarder
  • Posts: 26
  • Thank you received: 5
  • Karma: 0
Thanks Dave - as you say, it would be helpful if this "feature" was documented.
The administrator has disabled public write access.

DDRC-24 - Erratic behaviour with remote 3 months 2 weeks ago #40294

  • Tony_J
  • Tony_J's Avatar
  • Offline
  • Junior Boarder
  • Posts: 26
  • Thank you received: 5
  • Karma: 0
OK - finally seem to have a handle on this. It seems that after lots of loading/reloading of configurations, the DDRC-24 can get itself into a strange state, and if you reset it to factory defaults & re-load all of your working configurations & Dirac filters all is well again. I now have a DDRC-24 that responds correctly to the remote with the plugin connected, and the plugin properly updates to show current state.
The administrator has disabled public write access.
The following user(s) said Thank You: devteam

DDRC-24 - Erratic behaviour with remote 3 months 2 weeks ago #40364

  • plus5volt
  • plus5volt's Avatar
  • Offline
  • Junior Boarder
  • Posts: 25
  • Thank you received: 4
  • Karma: 0
In my case when I had current state updates issue, just power off/on helped, I did not have to do reset.
The administrator has disabled public write access.
The following user(s) said Thank You: EdHowarth
Moderators: devteam