(05-Jan-2015, 10:10)Confused Wrote: @Mikeeo - Some (not all) of what describe is very similar to the issues that I had when trying to enable inputs on the companion. After a few email exchanges with Devialet they eventually admitted that there are known bugs with the Configurator and they stated that they are working on a robust solution. In the end I gave up trying to use companion inputs, deciding that I would simply live without them until Devialet confirm the Configurator is fixed.

(05-Jan-2015, 10:19)Mikeeo Wrote:

(05-Jan-2015, 10:10)Confused Wrote: @Mikeeo - Some (not all) of what describe is very similar to the issues that I had when trying to enable inputs on the companion. After a few email exchanges with Devialet they eventually admitted that there are known bugs with the Configurator and they stated that they are working on a robust solution. In the end I gave up trying to use companion inputs, deciding that I would simply live without them until Devialet confirm the Configurator is fixed.

Good to hear, sadly, that I am not the only one with problems. Couldn't the have a normal RS 232 instead to enable all communication between units?
For sure I would not mind if the units where slightly bigger in terms of tallness then so much more inputs etc could be configured including having real AES/EBU to AES/EBU. If it is now the expert line why not enabling his and why only go halfway with that by having us use the RCA to AES/EBU solution. Why AES/EBU at all when not possible to do it fully?
Sorry for the drift off in topic.

/Mike

(05-Jan-2015, 10:55)NickB Wrote:

(05-Jan-2015, 10:19)Mikeeo Wrote:

(05-Jan-2015, 10:10)Confused Wrote: @Mikeeo - Some (not all) of what describe is very similar to the issues that I had when trying to enable inputs on the companion. After a few email exchanges with Devialet they eventually admitted that there are known bugs with the Configurator and they stated that they are working on a robust solution. In the end I gave up trying to use companion inputs, deciding that I would simply live without them until Devialet confirm the Configurator is fixed.

Good to hear, sadly, that I am not the only one with problems. Couldn't the have a normal RS 232 instead to enable all communication between units?
For sure I would not mind if the units where slightly bigger in terms of tallness then so much more inputs etc could be configured including having real AES/EBU to AES/EBU. If it is now the expert line why not enabling his and why only go halfway with that by having us use the RCA to AES/EBU solution. Why AES/EBU at all when not possible to do it fully?
Sorry for the drift off in topic.

/Mike

Well I for one do NOT want the units any larger and am very happy that the are the best amps I have heard ! Good job they are not made by any other company or you would never get anything changed on them.

Nick

(10-Jan-2015, 13:36)Mikeeo Wrote: Hi,

Want to report another 'bug'. When I hibernate the units, the companion display black out but the master keep the display saying 400 etc as it supposed. Any clue to the dimmed out display of the companion?

/Mike

(10-Jan-2015, 16:27)Mikeeo Wrote: Thanks Confused,

I see my own answer BUT at that time I didn't go AES/EBU yet as well as not used the new configurator enabling SAM. First time I noticed this was plugging in AES/EBU and then when the trigger cable was connected the companion closed down when enabling the >AES/EBU input on the master!??? So I unhooked it and everything worked again with no shut down of the companion when choosing the AES/EBU input on the master BUT the when hibernate is chosen companion display go black.

/Mike

(10-Jan-2015, 18:13)amabrok Wrote:

(10-Jan-2015, 16:27)Mikeeo Wrote: Thanks Confused,

I see my own answer BUT at that time I didn't go AES/EBU yet as well as not used the new configurator enabling SAM. First time I noticed this was plugging in AES/EBU and then when the trigger cable was connected the companion closed down when enabling the >AES/EBU input on the master!??? So I unhooked it and everything worked again with no shut down of the companion when choosing the AES/EBU input on the master BUT the when hibernate is chosen companion display go black.

/Mike

I have the same thing. when i turn off my D400, the master display shows a dimmed "400" whereas the slave display totally shuts down, but i did not take that as a bug, i assumed that this was by design considering that Devialet intended to have dual mono systems stacked with master on top, so ideally one is not meant to see the slave display at all.

is this ideal or logical, i dont think so, but i still don,t perceive it as a bug.

(10-Jan-2015, 18:13)amabrok Wrote:

(10-Jan-2015, 16:27)Mikeeo Wrote: Thanks Confused,

I see my own answer BUT at that time I didn't go AES/EBU yet as well as not used the new configurator enabling SAM. First time I noticed this was plugging in AES/EBU and then when the trigger cable was connected the companion closed down when enabling the >AES/EBU input on the master!??? So I unhooked it and everything worked again with no shut down of the companion when choosing the AES/EBU input on the master BUT the when hibernate is chosen companion display go black.

/Mike

I have the same thing. when i turn off my D400, the master display shows a dimmed "400" whereas the slave display totally shuts down, but i did not take that as a bug, i assumed that this was by design considering that Devialet intended to have dual mono systems stacked with master on top, so ideally one is not meant to see the slave display at all.

is this ideal or logical, i dont think so, but i still don,t perceive it as a bug.