ProSoundWeb Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: 1 2 [3]  All   Go Down

Author Topic: dbx driverack 260 vs venue 360  (Read 12936 times)

Jason Joseph

  • Full Member
  • ***
  • Offline Offline
  • Posts: 103
  • Vibrant Soundz
    • VibrantSoundz.net
Re: dbx driverack 260 vs venue 360
« Reply #20 on: May 17, 2016, 03:44:57 pm »

No simple crossover changes and the like are fine. But say if you move the GEQ from pre input to post output then there is a small reboot needed. Normal slope changes, eq changes, delay etc are not affected..

I do believe storing a setting has the name behavior (small mute of outputs) which is fundamentally different from how the 260 works..

This maybe changed in future updates however currently using the latest firmware this is what happens..
Logged

Bob Faulkner

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 998
  • Raleigh, NC
Re: dbx driverack 260 vs venue 360
« Reply #21 on: May 17, 2016, 07:57:54 pm »

No simple crossover changes and the like are fine. But say if you move the GEQ from pre input to post output then there is a small reboot needed. Normal slope changes, eq changes, delay etc are not affected..

I do believe storing a setting has the name behavior (small mute of outputs) which is fundamentally different from how the 260 works..

This maybe changed in future updates however currently using the latest firmware this is what happens..
Thanks for the follow up. 

The muting concerns me, though, a protocol change in how we use the driverack unit could possibly make it work.

What's the firmware version you are currently using?
Logged

Jason Joseph

  • Full Member
  • ***
  • Offline Offline
  • Posts: 103
  • Vibrant Soundz
    • VibrantSoundz.net
Re: dbx driverack 260 vs venue 360
« Reply #22 on: May 17, 2016, 10:34:06 pm »

v2.0.2.0
Logged

ProSoundWeb Community

Re: dbx driverack 260 vs venue 360
« Reply #22 on: May 17, 2016, 10:34:06 pm »


Pages: 1 2 [3]  All   Go Up
 



Page created in 0.05 seconds with 24 queries.