New build doesn't work at all?

[Jinx-IT]

I've installed the newest build and I get warning triangles when pushing the buttons on the stream deck. If I revert to the other version I'm back where I started.

[Zayik]

Hey there. Not sure why that would give you issues since the change was relatively small. Ill do some additional testing to see if I can find anything wrong.

Per chance can you give me an example string that you are using for your command pressed/command released. That would help in the debugging.

On Sun, Sep 4, 2022, 7:23 AM Jinx-IT @.***> wrote:

I've installed the newest build and I get warning triangles when pushing the buttons on the stream deck. If I revert to the other version I'm back where I started.

— Reply to this email directly, view it on GitHub https://github.com/Zayik/CommandSender/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEELKT7XSAIXKAR32RYIDTV4SWGJANCNFSM6AAAAAAQELFAMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Jinx-IT]

Still working with the same strings…per your msg…here’s the strings.

Packet Sender uses regular string: CC 8023 1 780 \r

Command Sender uses literal string and then uses html decoding for special characters: CC 8023 1 780

A note for you though…the string you showed me in command sender (before upgrading to the latest release) doesn’t work either. Let me clarify that the spaces between CC, 8023, 1, and 780 all matter. The string calls for a controller change (CC) of parameter 8023 to increase (1 is increase, 0 is decrease) an amount of 780 (which equates to 1dB). See page 8 of this doc: Composer-Control-Protocol-v7.0-080918.pdf (symetrix.co)https://www.symetrix.co/wp-content/uploads/2018/08/Composer-Control-Protocol-v7.0-080918.pdf

And to clarify again, once upgraded to the new release, the actual stream deck press fails with the warning triangle.

Sincerely,

Destry Jinks Sr. @.**@.> 407.574.6978 [jinxITsignature1]

From: David Anderson @.> Sent: Sunday, September 4, 2022 15:37 To: Zayik/CommandSender @.> Cc: Support @.>; Author @.> Subject: Re: [Zayik/CommandSender] New build doesn't work at all? (Issue #13)

Hey there. Not sure why that would give you issues since the change was relatively small. Ill do some additional testing to see if I can find anything wrong.

Per chance can you give me an example string that you are using for your command pressed/command released. That would help in the debugging.

On Sun, Sep 4, 2022, 7:23 AM Jinx-IT @.<mailto:@.>> wrote:

I've installed the newest build and I get warning triangles when pushing the buttons on the stream deck. If I revert to the other version I'm back where I started.

— Reply to this email directly, view it on GitHub https://github.com/Zayik/CommandSender/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEELKT7XSAIXKAR32RYIDTV4SWGJANCNFSM6AAAAAAQELFAMQ . You are receiving this because you are subscribed to this thread.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/Zayik/CommandSender/issues/13#issuecomment-1236402243, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGLZTY3LVR3BAMLS53G2E3V4T25ZANCNFSM6AAAAAAQELFAMQ. You are receiving this because you authored the thread.Message ID: @.**@.>>

[Zayik]

Thanks for that detailed explanation.

Given I am abandoning the concept of dealing with html encoding/decoding in favor of unifying the tool to match what others do such as Packet Sender, I am not going to worry about diving into that aspect.

That being said, I have identified two issues and have fixed them.

1. The package I had was unfortunately a development version which has debugging requirements in order to work. This is what caused the yellow square to appear on the stream deck. I have corrected this and successfully sent a message to a tcp server via internet using the latest package.

2. I resolved a bug in that if the connection was lost to the server (Server restarts), the very first message sent would fail. (This would result in the command pressed failing to send while the command release would succeed.

I hope this fix fairs much better and thanks for your patience!

[Jinx-IT]

So I should upgrade again, and go back to my packet sender style of commands?

Sincerely,

Destry Jinks Sr. @.**@.> 407.574.6978 [jinxITsignature1]

From: David Anderson @.> Sent: Sunday, September 4, 2022 17:43 To: Zayik/CommandSender @.> Cc: Support @.>; Author @.> Subject: Re: [Zayik/CommandSender] New build doesn't work at all? (Issue #13)

Thanks for that detailed explanation.

Given I am abandoning the concept of dealing with html encoding/decoding in favor of unifying the tool to match what others do such as Packet Sender, I am not going to worry about diving into that aspect.

That being said, I have identified two issues and have fixed them.

1. The package I had was unfortunately a development version which has debugging requirements in order to work. This is what caused the yellow square to appear on the stream deck. I have corrected this and successfully sent a message to a tcp server via internet using the latest package.
2. I resolved a bug in that if the connection was lost to the server (Server restarts), the very first message sent would fail. (This would result in the command pressed failing to send while the command release would succeed.

I hope this fix fairs much better and thanks for your patience!

— Reply to this email directly, view it on GitHubhttps://github.com/Zayik/CommandSender/issues/13#issuecomment-1236420405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGLZT2E6DS6KOB5GAQTKPLV4UJXBANCNFSM6AAAAAAQELFAMQ. You are receiving this because you authored the thread.Message ID: @.**@.>>

[Zayik]

Yes, please upgrade again and go back to the packet sender style of commands.

[Jinx-IT]

We have full control! Even on a couple of double commands (muting two channels at once, with a release). You’re awesome!

Example of double command:

Pressed: CS 8034 65535 \r\nCS 8042 65535 \r

Released: CS 8034 0 \r\nCS 8042 0 \r

Sincerely,

Destry Jinks Sr. @.**@.> 407.574.6978 [jinxITsignature1]

From: David Anderson @.> Sent: Sunday, September 4, 2022 17:59 To: Zayik/CommandSender @.> Cc: Support @.>; Author @.> Subject: Re: [Zayik/CommandSender] New build doesn't work at all? (Issue #13)

Yes, please upgrade again and go back to the packet sender style of commands.

— Reply to this email directly, view it on GitHubhttps://github.com/Zayik/CommandSender/issues/13#issuecomment-1236422407, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGLZT6BV6DYZVA2AQU5DRTV4ULS7ANCNFSM6AAAAAAQELFAMQ. You are receiving this because you authored the thread.Message ID: @.**@.>>