Author
Topic: Marantz SR over RS232 (Read 6985 times)

after the ruby hands on with ddamron (thanks again) I did a template for the Marantz SR series based on the work of bulek (http://wiki.linuxmce.org/index.php/Marantz_SR5600).I'm handling messages from the SR with the #350 process incoming data command:

...case avrcommand when 'SRC' case avrvalue when 'D' log('Input #420: CDR') input_param=420...cmd = Command.new(device_.devid_, -1001, 1, 2, 49);cmd.params_[41] = input_param.to_s()SendCommand(cmd);i see the message on the router but it has no handlers:

to implement the multi room feature i think we should create the multi rooms as related child devices (got inspired by the Yamaha template). We could assign every child to another EA. The parent would handle all commands with the "handle commands for child" cmd and send the multi room commands to the amp. The on/off cmds for the child would enable/disable the multi room.

to implement the multi room feature i think we should create the multi rooms as related child devices (got inspired by the Yamaha template). We could assign every child to another EA. The parent would handle all commands with the "handle commands for child" cmd and send the multi room commands to the amp. The on/off cmds for the child would enable/disable the multi room.

bulek, any ideas?

best regards,Hari

Hi,

generally speaking, you're thinking right... I already tried different things some year or so ago, but couldn't get to the proper solution. Basically I create one child device for FM Tuner, but the problem is that how to control/distribute commands. if you have separate commands (this is IMHO good enough solution till two separate output channels), then you can distinguish between them. if you have child device than it's probably impossible to assign volume controls to some other Orbiter screen... Also, don't forget that multiroom is only a feature, so you can easily swithc it off and use all channels for single source..

In my use, I usually declare new room called Audio Center and put all commands that relate to control of Marantz in Media scenarios (Vol+-, Vol+- multiroom, and basic switching/routing of audio sources and outputs - for instance I have "Separate" scenario, where I set up Marantz with two sources and two outputs..... I think this is not bad solution for a start...

I also hope that somewhere along the line, support for multichannel output devices will become part of LMCE and also ability to add 3rd party audio players (I also did a lot of work on "Audio only Xine player" idea, where you could use more separate stereo channels on Core as a source for whole house audio system for - either by putting in more sound cards, or using those cards that let you use multichannel outputs as separate stereo channels...)...

To be honest, for a start, good logging feature would help to enhance that template...

I'm still in some kind of passive state regarding template for Marantz. I talked to guys and the main advice was to wait for 710 release and rewrite template and check it in...

I'm also happy cause I see that Hari is contributing a lot of stuff for this template. I guess we all will merge efforts in one template.

But I have one question for more experienced GSD guys :

1. how to treat more parameters in gsd code ? :for instance I have volume up/down commands implemented with simple Ruby snippets : <$"@VOL:2\r"$>But DCE command includes also parameter for repeat and it seems like end device is responsible for handling it

Quote

/usr/pluto/bin/MessageSend localhost 0 SR5600_ID 1 90 72 ""

How to parse this incoming parameter in Ruby snippet for Vol up Command that is currently <$"@VOL:2\r"$> ?

Major questions regarding Marantz template remained unanswered are :- how to properly implement multiroom feature (option 1. separate commands for both zones, option2. having child device each for audio zone)- how to add child device properly to audio zone/room or whatever ?- can child devices mentioned above be in different rooms ?

I'm still in some kind of passive state regarding template for Marantz. I talked to guys and the main advice was to wait for 710 release and rewrite template and check it in...

I'm also happy cause I see that Hari is contributing a lot of stuff for this template. I guess we all will merge efforts in one template.

But I have one question for more experienced GSD guys :

1. how to treat more parameters in gsd code ? :for instance I have volume up/down commands implemented with simple Ruby snippets : <$"@VOL:2\r"$>But DCE command includes also parameter for repeat and it seems like end device is responsible for handling it

Quote

/usr/pluto/bin/MessageSend localhost 0 SR5600_ID 1 90 72 ""

How to parse this incoming parameter in Ruby snippet for Vol up Command that is currently <$"@VOL:2\r"$> ?

Major questions regarding Marantz template remained unanswered are :- how to properly implement multiroom feature (option 1. separate commands for both zones, option2. having child device each for audio zone)- how to add child device properly to audio zone/room or whatever ?- can child devices mentioned above be in different rooms ?

Hello fellow Marantz SR users,I've got an SR7500 that I've been tinkering with. I was wondering if the "SR Series RS232" device template that shipped with 0710RC1 is up-to-date. Here's what I have found about that template:

Some of the code in the Ruby rectangles is conspicuously less sophisticated than what is described in this thread. For example, volume control just the straightforward <$"@VOL:2\r"$> style.

the template doesn't have any av inputs.

something in that template causes video and music to stop playing immediately after it starts (you hear audio for about 1/4 second)

I have started to build my own SR Series template and have a simple implementation working so that the receiver turns on and off and the volume and inputs can be controlled. I suspect, however, that someone out there has a better template for the SR series. If so, can you share it with me somehow?