Re: Macros and timing reliability

Sunday, January 29, 2012
I think your problem is the time that is needed to execute the ir code
by the Global Caché device.

Joep

Op 27 jan. 2012 om 23:33 heeft Jarrod Bell <jarrod@guilink.com> het
volgende geschreven:

> Of course discrete vol is the real answer, but I have not heard of anyone having issues with macro timing.
> 1 second should be plenty of delay, but then again IR is very hardware dependent. I don't think its a network issue.
>
> Waiting 10-20 seconds for vol adjustment sounds like a very bad situation. Why not use an amp that has RS232 control?
>
> Jarrod
>
> On 28/01/12 1:29 AM, MarkusKl wrote:
>> Hi,
>>
>> I have a few questions regarding macros, command timings within macros
>> etc.
>>
>> We have a couple of projects done now each of them having the same
>> hardware amps controlled by global caches IP bus devices via IR
>> commands.
>> I do know about IR code problematics etc. but I can for sure say that
>> all codes are working fine because we developed them on our own with
>> the manufacturer.
>> To clarify the situation a little bit more we are having audio scenes
>> within a multiroom environment and we are controlling the amps and the
>> audio zones by setting the volume levels on the amps differently (via
>> the mentioned IR/GC combos).
>>
>> Now as you might expect the macros are quite extensive because each of
>> the amps have 102 (!!) volume steps.
>> Besides this there are also a few other things to do in the macros.
>> Of course, not always 102 steps/commands are send per amp, we have
>> some improvements and used some tricks so we are talking about 10-20
>> steps per amp.
>>
>> Knowing that each vol up/vol down command needs ~500ms for execution
>> within the amp we have a delay of 1000ms in our macros (which are real
>> CF macros, no JS code) to ensure the commands are send adequately.
>>
>> I am wondering if I can rely on the 1000ms within the macro
>> execution ?
>> And also, is it ensured that the macros are executed serially (which
>> is what I am expecting, of course)?
>> Would it make sense to program the macros within JS ? Would that bring
>> any benefits/more reliability? Also, how to code the delays and ensure
>> the serial execution ? (The UI is blocked for the user in any case to
>> ensure correct execution and finalization of the macros)!
>>
>> I am asking this because even when I further delay the commands for
>> vol up/down sometimes (I would say in 1-3% of the cases) not all the
>> commands are received by the amps which results in differences in the
>> audio scenes...it's not something the user probably hears, but I can
>> track it in our devlopement/debuging software of the amps...and
>> because it's a question of professionality i would like to have this
>> 100% solved !
>>
>> It could be that the network has some delay in theory, although it is
>> a multimedia network used and installed ONLY for audio (!), no other
>> pc or NAS devices etc., also it's a gigabit network...
>>
>> I am just curious what other guys/installers say about this behavior,
>> and also would appreciate any idea to solve the issue.
>>
>> I know that the best way is to have discrete volume level commands
>> which in fact is something we are working at with the manufacturer but
>> it's not guaranteed that we will get them...
>>
>> So, any ideas ?
>>
>> Markus
>>
>
> --
> You received this message because you are subscribed to the Google Groups "CommandFusion" group.
> To post to this group, send email to commandfusion@googlegroups.com.
> To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to commandfusion@googlegroups.com.
To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.

0 comments:

Post a Comment