Weird Behavior after Driver Update

bitzerjd's Avatar Topic Author
User User
  • Posts: 375
  • Thanks: 3

Weird Behavior after Driver Update

1 year 11 months ago - 1 year 11 months ago
#3421
Hi,

I'm issuing this command in a macro...

Control|3~SendIR~HD Fury-4K Vertex 2~TURNOFFSOUND!

It is not working when executing from the macro, but works fine from the command builder.  The macros have not changed and it has worked fine for months.  It stopped working after the GenericIR update.

FYI (Update) - I have three "Vertex 2" commands in a row, adding a "Pause|1!" after each one allowed them to fire properly.  Without the pause only one would fire.

Looking in the logs, it appears that single commands work fine.  When multiple ones are firing in a row, they don't work.
Last edit: 1 year 11 months ago by bitzerjd.

Please Log in or Create an account to join the conversation.

Nillaz's Avatar
User User
  • Posts: 444
  • Thanks: 36

Re: Weird Behavior after Driver Update

1 year 11 months ago
#3423
Hi,

I'm issuing this command in a macro...

Control|3~SendIR~HD Fury-4K Vertex 2~TURNOFFSOUND!

It is not working when executing from the macro, but works fine from the command builder.  The macros have not changed and it has worked fine for months.  It stopped working after the GenericIR update.

FYI (Update) - I have three "Vertex 2" commands in a row, adding a "Pause|1!" after each one allowed them to fire properly.  Without the pause only one would fire.

Looking in the logs, it appears that single commands work fine.  When multiple ones are firing in a row, they don't work.
 
I'll check tonight to see if I can corroborate this.

Please Log in or Create an account to join the conversation.

Nillaz's Avatar
User User
  • Posts: 444
  • Thanks: 36

Re: Weird Behavior after Driver Update

1 year 11 months ago
#3425
I was able to test this and I'm seeing the same thing. As far as I can tell all of my other devices being controlled via IR are working as intended.

Thanks for the heads up that adding a Pause mitigates the issue!

Please Log in or Create an account to join the conversation.

Nillaz's Avatar
User User
  • Posts: 444
  • Thanks: 36

Re: Weird Behavior after Driver Update

1 year 11 months ago
#3426
Saw that there was an update to the Generic IR driver today and just tested it. The HDFury still fails to recognize commands in a macro without adding a pause. Actually, I need to add a pause before and after the command in order for it to respond correctly.

It's not a significant problem for me, but I would imagine that this can be tedious and time consuming if you have a chain of commands being sent to the HDFury within the same macro.

@bitzerjd out of curiosity which HDFury IR commands do you actually use? In general the only command I need to send to my VRROOM's is a basic inputsel in order to switch device inputs or maybe the occasional hotplug if the VRROOM is acting wonky.

Please Log in or Create an account to join the conversation.

bitzerjd's Avatar Topic Author
User User
  • Posts: 375
  • Thanks: 3

Re: Weird Behavior after Driver Update

1 year 11 months ago
#3427
I issue a mutetx1 and mutetx0 followed by a command to switch the Vrroom from manual eARC to manual HDMI. This is a workaround for the Vrroom not having a command to Mute the eARC (Arcana) port. If you set it to eARC it kills the output...Manual HDMI restores the audio.

The mute commands are to make sure that the output to the TV contains no audio... I've had the TV outputting sound and the Sonos ARC.

I don't use eARC out of the TV because my Sony has some issues where it will drop the audio.

It seems my HT is a series of workarounds...

Please Log in or Create an account to join the conversation.

Nillaz's Avatar
User User
  • Posts: 444
  • Thanks: 36

Re: Weird Behavior after Driver Update

1 year 11 months ago - 1 year 11 months ago
#3430
It seems my HT is a series of workarounds...

 
I hear ya. Sometimes I feel like my entire life is a series or workarounds lol

I wonder if a dedicated driver could be created for HDFury devices. I know that Control4 has one and the command documentation is readily available.

I'd also like to know if this affects any other IR devices. I haven't run across any issues with any of my other equipment but I haven't exhaustively tested everything yet.
Last edit: 1 year 11 months ago by Nillaz.

Please Log in or Create an account to join the conversation.

Time to create page: 0.300 seconds