Re: Cisco room devices 4.0 - module cannot find the related CLZ on program compile

#245608

Copying the module and related CLZ to local folder fixed this issue.?
Was hoping I could use the user module folders on this PC but it still does not work correctly.?

Would still like to know if others found a workaround for this.?

Tray

Cisco room devices 4.0 - module cannot find the related CLZ on program compile

#245607

Migrating to a new PC and cannot get the Cisco Room Devices 4.0 module to compile properly in my program.?
Opened the CiscoRoomDevicesWrapper v4.0 and cannot compile that module.?
Error: Statement outside of function scope (line 55).?
That line is the reference to S# library. Copied CLZ to both the usrmacro and usrsplus folders.?
Still no joy.?

Question: is there still a standalone installer for the Cisco room kit modules or is there something more basic that I am missing.?
Same project compiles fine on old PC.?
Will try putting all files in local program folder to see if that works around this issue. I know that user databases can be problematic.?

Thanks in advance,?

Tray

Re: Yamaha 3080 multiple connections

#245606

I am using Yamaha IP 3000 1.2. Also I opened the module in simpl to check for parameters about keep alive / connections and they are actually there.

But I wasn't able to figure out a way to stabilize the ip connection. Seems like even when connected flag is high, the driver sends 4-5 reconnects per second which returns as broken connections remotely (because it is already connected).

After I m done alexa integrating the house will try to change parameters on module to solve this (but I'm not keeping my hopes high)

Em sex., 1 de abr. de 2022 03:31, Thorsten K?hler <thorsten.koehler@...> escreveu:

Show quoted text

I agree with Steve, IR is pretty stable in general (especially via cable) and often totally sufficient, with RS232 next to the list.
However, for Yamaha, i?m using the YNCA protocol and found that to be very reliable and stable even over firmware updates.
It?s just a dead simple ASCII protocol.
To the OP: which control protocol are you using?
?
Cheers,
Thorsten
?
Von: [email protected] <[email protected]> Im Auftrag von Steve Kuehn
Gesendet: Freitag, 1. April 2022 04:02
An: [email protected]
Betreff: Re: [crestron] Yamaha 3080 multiple connections
?
I know this doesn't answer your question. But since no one appears to have an answer for your question, thought I share a little insight base on my personal past experience.? In general, I avoid doing IP control for any consumer product, at least for anything mission critical, because of reliability issues.? Virtually ever job I have done using IP control on TVs and receivers, I have had to eventually go back on convert it to some other method because IP control was intermittent or a firmware update broke it.? A commercial product is a different story -- IP control is generally robust.?

I just did a Yamaha RX-A3080 and what I did was control it will IR.? There is a 3.5mm jack on the back of the RX-A3080 so you don't have to put a flasher on the front of the unit.? IR will always work because the manufacturer is very careful not to break that interface during firmware updates.? If I need feedback, such as volume level in my case, I do an RS232 connection to the receiver.? The RX-A3080 has RS232 port on the back of it.? I only use RS232 for feedback as if that breaks, and I have seen that happen after a firmware update, at least the receiver will turn on, switch inputs, and the volume control will still work.? The only thing that happens is the volume level may not display on any two-way interfaces.? But at least the system is still usable.

If you want to use IP control, you will probably have to write your own module. At least that is what I have had to do in the past. If the issue is with the firmware in the receiver, even that won't work.

Re: Alexa -> Creston integration connection system problem

#245605

I have an update about this:

Removing \usr\alexaappdata files, re uploading the program, rebooting and re registering solved the problem.

You still get a not connected message on echoadmin but if you register the skill, alexa will find and control devices just fine.

Daniel?

Em sex., 1 de abr. de 2022 09:17, Daniel Arola via <daniel.arola=[email protected]> escreveu:

Show quoted text

Hello, Im losing my mind here.
We have 72 devices working in a alexa-creston integrated enviroment. During logic tests the devices suddenly stopped working.
After a lot of chase-tail we found a room name parameter without ", but even after correcting that, control system wont go on. We tried to re-register on??and we get to greens and one red, where Control System Connection is "not connected".
After a while I checked the error log to find this:
123. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:50 # 3/31/2022 9:03:50 PM ConnectionManager.Connect: Exception occurred during connection. Exception:System.Exception: Websocket client connect: Exception Thrown = (NullReferenceException)
at Crestron.SimplSharp.CrestronWebSocketClient.WebSocketClient.C124. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # onnect()
at Crestron.RemoteService.SessionManager.ConnectionManager.Connect()
at Crestron.RemoteService.SessionManager.ConnectionManager.Send(Byte[] messagebytes)
at Crestron.RemoteService.SessionManager.SessionManager.Send(Byte[] message)
125. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # at Crestron.RemoteService.MessageManagement.MessageManager.GenerateRequest(String requestedAction, Dictionary`2 parameters, ResponseCallback callback, Int64 transactionID)
at Crestron.RemoteService.SessionManager.SessionManager.SendRegister(String re126. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # gistrationCode, ResponseCallback callback, Object callbackCustomObject)
at Crestron.RemoteService.SessionManager.SessionManager.SendRegister(String registrationCode)
at Crestron.RemoteServiceSimpl.SessionManagerSimpl.SendRegister(String registrati127. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # onCode)
at CrestronModule_REMOTE_SERVICE_CONNECTION_MANAGER_V2_0_0.CrestronModuleClass_REMOTE_SERVICE_CONNECTION_MANAGER_V2_0_0.REGISTRATIONCODE_OnChange_3(Object __EventInfo__)
at Amib.Threading.Internal.WorkItem.o()
at Amib.Threading.Interna128. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # l.WorkItem.Execute()
at Amib.Threading.SmartThreadPool.e(WorkItem A_0)
at Amib.Threading.SmartThreadPool.p()
This error occurs when we try to delete the registration and re-enter registration code on the adminsite.
All alexa-related logic was reviewed, no extras ' or " on any parameter. We even tried to revert back to code without alexa integration, leaving only the registration module and that didnt have any effect.
The only thing i'm sure is that this null reference exception occurs on re-registering, no matter what. (Even tried to revert back to a full last year backup + voice control).
Also, i'm using version voice control 2.0 and again, we had 72 devices working great with alexa when they all suddenly stopped (probably because of the missing ")
update: I waited a whole night and retried registering now, still same "Registration: registered", "Control System Connection: not registered" problem. But errlog doesn't show anything for this particular try.
Please, if anyone has any advice, I would be forever grateful.

Alexa -> Creston integration connection system problem

#245604

Hello, Im losing my mind here.

We have 72 devices working in a alexa-creston integrated enviroment. During logic tests the devices suddenly stopped working.

After a lot of chase-tail we found a room name parameter without ", but even after correcting that, control system wont go on. We tried to re-register on??and we get to greens and one red, where Control System Connection is "not connected".

After a while I checked the error log to find this:

123. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:50 # 3/31/2022 9:03:50 PM ConnectionManager.Connect: Exception occurred during connection. Exception:System.Exception: Websocket client connect: Exception Thrown = (NullReferenceException)
at Crestron.SimplSharp.CrestronWebSocketClient.WebSocketClient.C124. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # onnect()
at Crestron.RemoteService.SessionManager.ConnectionManager.Connect()
at Crestron.RemoteService.SessionManager.ConnectionManager.Send(Byte[] messagebytes)
at Crestron.RemoteService.SessionManager.SessionManager.Send(Byte[] message)
125. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # at Crestron.RemoteService.MessageManagement.MessageManager.GenerateRequest(String requestedAction, Dictionary`2 parameters, ResponseCallback callback, Int64 transactionID)
at Crestron.RemoteService.SessionManager.SessionManager.SendRegister(String re126. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # gistrationCode, ResponseCallback callback, Object callbackCustomObject)
at Crestron.RemoteService.SessionManager.SessionManager.SendRegister(String registrationCode)
at Crestron.RemoteServiceSimpl.SessionManagerSimpl.SendRegister(String registrati127. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # onCode)
at CrestronModule_REMOTE_SERVICE_CONNECTION_MANAGER_V2_0_0.CrestronModuleClass_REMOTE_SERVICE_CONNECTION_MANAGER_V2_0_0.REGISTRATIONCODE_OnChange_3(Object __EventInfo__)
at Amib.Threading.Internal.WorkItem.o()
at Amib.Threading.Interna128. Error: splusmanagerapp.exe [App 1] # 2022-03-31 21:03:51 # l.WorkItem.Execute()
at Amib.Threading.SmartThreadPool.e(WorkItem A_0)
at Amib.Threading.SmartThreadPool.p()

This error occurs when we try to delete the registration and re-enter registration code on the adminsite.

All alexa-related logic was reviewed, no extras ' or " on any parameter. We even tried to revert back to code without alexa integration, leaving only the registration module and that didnt have any effect.

The only thing i'm sure is that this null reference exception occurs on re-registering, no matter what. (Even tried to revert back to a full last year backup + voice control).

Also, i'm using version voice control 2.0 and again, we had 72 devices working great with alexa when they all suddenly stopped (probably because of the missing ")

update: I waited a whole night and retried registering now, still same "Registration: registered", "Control System Connection: not registered" problem. But errlog doesn't show anything for this particular try.

Please, if anyone has any advice, I would be forever grateful.

Re: Yamaha 3080 multiple connections

#245603

Thanks everyone,

Seems like you are right about this, probably something wrong in the keep alive /reconnect logic that cant be easily fixed.

Em sex., 1 de abr. de 2022 às 03:31, Thorsten K?hler <thorsten.koehler@...> escreveu:

Show quoted text

I agree with Steve, IR is pretty stable in general (especially via cable) and often totally sufficient, with RS232 next to the list.
However, for Yamaha, i?m using the YNCA protocol and found that to be very reliable and stable even over firmware updates.
It?s just a dead simple ASCII protocol.
To the OP: which control protocol are you using?
?
Cheers,
Thorsten
?
Von: [email protected] <[email protected]> Im Auftrag von Steve Kuehn
Gesendet: Freitag, 1. April 2022 04:02
An: [email protected]
Betreff: Re: [crestron] Yamaha 3080 multiple connections
?
I know this doesn't answer your question. But since no one appears to have an answer for your question, thought I share a little insight base on my personal past experience.? In general, I avoid doing IP control for any consumer product, at least for anything mission critical, because of reliability issues.? Virtually ever job I have done using IP control on TVs and receivers, I have had to eventually go back on convert it to some other method because IP control was intermittent or a firmware update broke it.? A commercial product is a different story -- IP control is generally robust.?

I just did a Yamaha RX-A3080 and what I did was control it will IR.? There is a 3.5mm jack on the back of the RX-A3080 so you don't have to put a flasher on the front of the unit.? IR will always work because the manufacturer is very careful not to break that interface during firmware updates.? If I need feedback, such as volume level in my case, I do an RS232 connection to the receiver.? The RX-A3080 has RS232 port on the back of it.? I only use RS232 for feedback as if that breaks, and I have seen that happen after a firmware update, at least the receiver will turn on, switch inputs, and the volume control will still work.? The only thing that happens is the volume level may not display on any two-way interfaces.? But at least the system is still usable.

If you want to use IP control, you will probably have to write your own module. At least that is what I have had to do in the past. If the issue is with the firmware in the receiver, even that won't work.

Re: Cisco Room Os 10

#245602

Hi Walter, Thanks for your comments. I wanted to ask if you are using the webex calls from the Crestron touch panel, trying to create a direct call to webex but I can't.

Re: Yamaha 3080 multiple connections

#245601

开云体育

I agree with Steve, IR is pretty stable in general (especially via cable) and often totally sufficient, with RS232 next to the list.

However, for Yamaha, i?m using the YNCA protocol and found that to be very reliable and stable even over firmware updates.

It?s just a dead simple ASCII protocol.

To the OP: which control protocol are you using?

?

Cheers,

Thorsten

?

Von: [email protected] <[email protected]> Im Auftrag von Steve Kuehn
Gesendet: Freitag, 1. April 2022 04:02
An: [email protected]
Betreff: Re: [crestron] Yamaha 3080 multiple connections

?

I know this doesn't answer your question. But since no one appears to have an answer for your question, thought I share a little insight base on my personal past experience.? In general, I avoid doing IP control for any consumer product, at least for anything mission critical, because of reliability issues.? Virtually ever job I have done using IP control on TVs and receivers, I have had to eventually go back on convert it to some other method because IP control was intermittent or a firmware update broke it.? A commercial product is a different story -- IP control is generally robust.?

I just did a Yamaha RX-A3080 and what I did was control it will IR.? There is a 3.5mm jack on the back of the RX-A3080 so you don't have to put a flasher on the front of the unit.? IR will always work because the manufacturer is very careful not to break that interface during firmware updates.? If I need feedback, such as volume level in my case, I do an RS232 connection to the receiver.? The RX-A3080 has RS232 port on the back of it.? I only use RS232 for feedback as if that breaks, and I have seen that happen after a firmware update, at least the receiver will turn on, switch inputs, and the volume control will still work.? The only thing that happens is the volume level may not display on any two-way interfaces.? But at least the system is still usable.

If you want to use IP control, you will probably have to write your own module. At least that is what I have had to do in the past. If the issue is with the firmware in the receiver, even that won't work.

Re: Loading VT files to CP4

#245600

Yep, I seen this happen with several older projects.? System had been working fine for years.? I make an update to the system using newer Crestron software and all of a sudden all the iPhone/iPad interfaces stop working.? Remove the spaces from the VTP project, recompile, and download and everything starts working again.

Re: Yamaha 3080 multiple connections

#245599

I know this doesn't answer your question. But since no one appears to have an answer for your question, thought I share a little insight base on my personal past experience.? In general, I avoid doing IP control for any consumer product, at least for anything mission critical, because of reliability issues.? Virtually ever job I have done using IP control on TVs and receivers, I have had to eventually go back on convert it to some other method because IP control was intermittent or a firmware update broke it.? A commercial product is a different story -- IP control is generally robust.?

I just did a Yamaha RX-A3080 and what I did was control it will IR.? There is a 3.5mm jack on the back of the RX-A3080 so you don't have to put a flasher on the front of the unit.? IR will always work because the manufacturer is very careful not to break that interface during firmware updates.? If I need feedback, such as volume level in my case, I do an RS232 connection to the receiver.? The RX-A3080 has RS232 port on the back of it.? I only use RS232 for feedback as if that breaks, and I have seen that happen after a firmware update, at least the receiver will turn on, switch inputs, and the volume control will still work.? The only thing that happens is the volume level may not display on any two-way interfaces.? But at least the system is still usable.

If you want to use IP control, you will probably have to write your own module. At least that is what I have had to do in the past. If the issue is with the firmware in the receiver, even that won't work.

Re: NVX vs. SVSI

#245598

开云体育

Thanks for the insight, Ed – very interesting.

I also did some additional reading about the concept.

I guess I just have too much of an Corporate/Enterprise IT background to imagine such a technique being approved by any IT department. ?

?

Cheers,

Thorsten

?

Von: [email protected] <[email protected]> Im Auftrag von eoqualls
Gesendet: Donnerstag, 31. M?rz 2022 17:10
An: [email protected]
Betreff: Re: [crestron] NVX vs. SVSI

?

Jeff,? In 2010 we were focused on VLAN switching, as it was much faster (instant seamless switching vs slow multi-second switching on other products).? We produced control system drivers to make implementing VLAN switching very simple.? Thorsten, I know you find this hard to imagine, but many of our dealers continue to use VLAN switching for its unmatched performance.? We have VLAN based installations over 10 years old that continue to perform perfectly.

?

In 2016 we decided to add standard network routing via Multicast to our products.? The commercial installers made it clear they had customers that needed this.? Our current firmware supports both VLAN and Multicast switching.? This firmware update is backwards compatible with our devices in the field.? An installation that started as VLAN, can easily be converted to Multicast if standard network routing is desired.

?

One other thing that you might be interested in knowing is that we have plenty of inventory available.? We have always purchased our silicon far in advance, as our circuit board designs are very stable and don’t change frequently.? Our commitment to a stable, long term architecture allows us to confidently purchase our chips far in advance.? It’s the companies that do Just In Time manufacturing that are suffering from the chip problems.

?

Thank you for your consideration.? If anyone here is interested, please let me know if you want to get a demo kit for testing and evaluation.? We also offer online and classroom training for installers.

?

Ed Qualls

Chief Executive Officer

+1-727-475-7033

ed@...

Yamaha 3080 multiple connections

#245597

Hello,

I'm working on a residence with 3 yamaha receivers, RX V85, RX A2080 and RX 3080. They are all using Yamaha 3010 IP v1.2 to connect and they all work fine with the xpanel app.

The problem is that all of them area trying to force a reconnection even if the module is already connected, leading to dozens of processes running showing up in toolbox.

As you can see below, the module has an IP connection via socket but tries again to reconnect.?

Maybe because the residence has 3 of them?

Anyone has this issue? Any tips on fixing this?

Thanks,

Daniel Arola

Heres my toolbox output:

00:00:02.719 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_Gourmet
00:00:02.719 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_Gourmet
00:00:02.719 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_Mainroom
00:00:02.719 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_Mainroom
00:00:02.719 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_Mainroom
00:00:02.734 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_SuiteMaster
00:00:02.734 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_SuiteMaster
00:00:02.734 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_Gourmet
00:00:02.734 ? ?Connected ? ?//{{Connection_Status_Text}}_Gourmet
00:00:02.734 ? ?1 ? ?{{TCP/IP_Client_>>_Connect-F}}_Gourmet
00:00:02.750 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_SuiteMaster
00:00:02.750 ? ?Connected ? ?//{{Connection_Status_Text}}_SuiteMaster
00:00:02.766 ? ?1 ? ?{{TCP/IP_Client_>>_Connect-F}}_SuiteMaster
00:00:02.766 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_Mainroom
00:00:02.766 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_Mainroom
00:00:02.781 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_Mainroom
00:00:02.781 ? ?Connected ? ?//{{Connection_Status_Text}}_Mainroom
00:00:02.781 ? ?1 ? ?{{TCP/IP_Client_>>_Connect-F}}_Mainroom
00:00:02.891 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_SuiteMaster
00:00:02.891 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_SuiteMaster
00:00:02.891 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_Gourmet
00:00:02.891 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_Gourmet
00:00:02.891 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_Gourmet
00:00:02.906 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_SuiteMaster
00:00:02.906 ? ?4d ? ?{{TCP/IP_Client_>>_status}}_Mainroom
00:00:02.906 ? ?Connection Broken Remotely ? ?//{{Connection_Status_Text}}_Mainroom
00:00:02.906 ? ?0 ? ?{{TCP/IP_Client_>>_Connect-F}}_Mainroom
00:00:02.922 ? ?1d ? ?{{TCP/IP_Client_>>_status}}_Gourmet
00:00:02.922 ? ?Waiting For Connection ? ?//{{Connection_Status_Text}}_Gourmet
00:00:02.937 ? ?2d ? ?{{TCP/IP_Client_>>_status}}_Gourmet
00:00:02.937 ? ?Connected ? ?//{{Connection_Status_Text}}_Gourmet

Re: NVX vs. SVSI

#245596

Hi Ed,

Great information. Some followup questions:

Does the current VLAN switching software allow for control of multiple switches or just a "switch stack" or "virtual switch"?
I'm curious how switching via VLANs is faster than multicast switching for the same product? When we switch streams to a decoder, the majority of latency to "picture" is the decoder processing time for the new stream...shouldn't make a difference if it's a new stream due to switching VLANs or switching routing. In both cases it's a new stream being directed to the encoder. This is borne out by the fact that if we have an incorrectly assigned VLAN for a decoder (i.e. on our control VLAN vice the streaming video VLAN), when we correct the VLAN assignment the decoder still takes the same amount of time to process the new incoming signal to show on the display. I could see mulit-milli-second delay differences in VLAN vs multicast routing, but multi-second has more to do with the decoder than VLAN vs Multicast switching.

Thanks,
Jeff

-------------------------------------

Jeff Klein, DMC-E
Head Volunteer AV Geek
Faith Baptist Church
Glen Burnie, Maryland

(Website / Twitter)

?/ @FBC_TechTeam

/ @mixingforjesus

"Clothe yourselves, all of you, with humility toward one another, for God opposes the proud but gives grace to the humble." 1 Peter 5:5

Show quoted text

On Thu, Mar 31, 2022 at 11:10 AM eoqualls <ed@...> wrote:

Jeff,? In 2010 we were focused on VLAN switching, as it was much faster (instant seamless switching vs slow multi-second switching on other products).? We produced control system drivers to make implementing VLAN switching very simple.? Thorsten, I know you find this hard to imagine, but many of our dealers continue to use VLAN switching for its unmatched performance.? We have VLAN based installations over 10 years old that continue to perform perfectly.
?
In 2016 we decided to add standard network routing via Multicast to our products.? The commercial installers made it clear they had customers that needed this.? Our current firmware supports both VLAN and Multicast switching.? This firmware update is backwards compatible with our devices in the field.? An installation that started as VLAN, can easily be converted to Multicast if standard network routing is desired.
?
One other thing that you might be interested in knowing is that we have plenty of inventory available.? We have always purchased our silicon far in advance, as our circuit board designs are very stable and don’t change frequently.? Our commitment to a stable, long term architecture allows us to confidently purchase our chips far in advance.? It’s the companies that do Just In Time manufacturing that are suffering from the chip problems.
?
Thank you for your consideration.? If anyone here is interested, please let me know if you want to get a demo kit for testing and evaluation.? We also offer online and classroom training for installers.
?
Ed Qualls
Chief Executive Officer
+1-727-475-7033
ed@...

CONFIDENTIALITY NOTE:?The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.

Re: NVX vs. SVSI

#245595

开云体育

Jeff,? In 2010 we were focused on VLAN switching, as it was much faster (instant seamless switching vs slow multi-second switching on other products).? We produced control system drivers to make implementing VLAN switching very simple.? Thorsten, I know you find this hard to imagine, but many of our dealers continue to use VLAN switching for its unmatched performance.? We have VLAN based installations over 10 years old that continue to perform perfectly.

?

In 2016 we decided to add standard network routing via Multicast to our products.? The commercial installers made it clear they had customers that needed this.? Our current firmware supports both VLAN and Multicast switching.? This firmware update is backwards compatible with our devices in the field.? An installation that started as VLAN, can easily be converted to Multicast if standard network routing is desired.

?

One other thing that you might be interested in knowing is that we have plenty of inventory available.? We have always purchased our silicon far in advance, as our circuit board designs are very stable and don’t change frequently.? Our commitment to a stable, long term architecture allows us to confidently purchase our chips far in advance.? It’s the companies that do Just In Time manufacturing that are suffering from the chip problems.

?

Thank you for your consideration.? If anyone here is interested, please let me know if you want to get a demo kit for testing and evaluation.? We also offer online and classroom training for installers.

?

Ed Qualls

Chief Executive Officer

+1-727-475-7033

ed@...

Re: Managing/Processing volume

#245594

The issue for me is all about Feedback display.
Sending discrete volume levels work fine. our system uses the actual feedback of the unit to determine what the next value level will be
i.e. if I send 'x' and then receive 'x' my next increment is to send 'y', BUT if I still receive 'x' as feedback, or the unit is sluggish in returning 'y', I just send 'y' again, thinking that the unit is still at 'x' instead of 'y'
This problem results from one of two conditions
a. the unit is sluggish in returning its feedback - slower than my Inc/Dec ramping - I've seen this with a number of AVRs using RS232 and the Sony ZA series with IP control
b. The conversion from the serial text coming from the Yamaha (-80 to 16) to the Analog values are not always correct leading to weird display of the volume status

In Case A, the solution is to use a pair of analog buffers one fed with my direct ramping analog and the other with the parsed Analog from the AVR. the output of both are the FB signal going to the UI
Then I enable the first whenever I'm ramping so that the FB is just my ramping value - this provides very smooth display for the client
After 1 second of not ramping I disable Abuf 1 and enable Abuf 2, passing the ACTUAL volume level from the AVR to the UI display

This method has worked great for years with Sony ZA, Denon, Marantz, etc.
With the Yamaha units, the seeded value does not convert correctly part of the time.

The solution (So far): It seems that the Yamaha IP control delivers the volume level values fast enough that I can just use it directly as the FB without the switching, eliminating the need to have a change-over
Assuming that it continues to keep up, this will be my 'solution'...

Thanks All!

Re: Loading VT files to CP4

#245593

I haven't heard about no spaces yet...
And this issue was resolved leaving the spaces in (Consistency, anyone! haha) - I just had to remove the brackets

Didn't work:
MiddleAtlantic RackLink Select [ipad]

Did work:
MiddleAtlantic RackLink Select - ipad

Re: Samsung BET-H series IP Control

#245592

Was the magic packet transmitted via a Crestron processor? I have it working with Packet Sender, but my S# library for it as well as the UDP/IP symbol in Simpl are not doing the trick.

Re: Managing/Processing volume

#245591

开云体育

I just prefer to use the volume control modules available in the crestron database rather than AINC.? They already have memory for 4 volume presets built in.

?

The point was that raise and lower on the AVR modules kind of sucks and they do not have an analog volume level input, so I found a way to send the direct level to the AVR precisely because it allows the AVR to be controlled like a crestron device.

?

From: <[email protected]> on behalf of BruteForceIsUnderRated <crestronpro@...>
Reply-To: <[email protected]>
Date: Wednesday, March 30, 2022 at 10:00 AM
To: <[email protected]>
Subject: Re: [crestron] Managing/Processing volume

?

The outputs of the analog step could be connected to an EQU to and SIO to send the discrete steps. As an analog you can store it like any other signal.

As you stated, you could just use a raise/lower if the AVR has that feature and process?the feedback for user display and to store for preset/zone presets that are then decoded on recall. Lots of ways to do this.

The analog increment allows you to not deal with the rounding issues. You could always store the converted % amount and convert backed to your signed values on a preset recall.

?

Show quoted text

On Wed, Mar 30, 2022 at 9:50 AM MSTC <kol.mstc@...> wrote:

I send the discrete volume level to the AVR.? It is much easier to deal with it that way.? Use a volume control module to generate analog value then use a bit of logic to send it.? Plus is it is then able to be treated the same as a Crestron device (SWAMP, PAD-8 . . .) and you can do the memorize preset volumes thing, initialize to a start-up level, or whatever other joy-joy stuff you might do with a multi-zone system.? Even though most of the Crestron modules I have seen use raise and lower, virtually all AVRs or processors that allow third party control allow setting volume level directly.
?
For serial control of Aventage the volume direct format is @MAIN:VOL=11.0\n or @MAIN:VOL=-11.0\n.?
I ASCALEL the raw volume level.? 0%,100% scales to -80, 16 (or reduce the output range to something like -50, 0 to set the volume of the AVR to a barely audible minimum and limit the top end, similar to VolMin and VolMax inputs on the PAD8.)
I EQU the scaled level to get a signal for each level command.? The digitals out of EQU drive SIO.
I also use AOS (* output) on the TX$ for the AVR to do a 0.2 sec disable of the EQU to allow the AVR to process the command before sending the next during ramping.
?
From: <[email protected]> on behalf of ckangis <chris@...>
Reply-To: <[email protected]>
Date: Wednesday, March 30, 2022 at 8:41 AM
To: <[email protected]>
Subject: Re: [crestron] Managing/Processing volume
?
Re: dB display - our normal clients barely understand %, dB would confuse them even more!!? HaHa!!

Re: adding the two extreme values:
I'll look at that, but I think that the basic issue is analog values being slightly different when scaled vs. our level analogs.

The root problem is that we have a consumer piece that uses Pro Audio parameters...:(

Re: Loading VT files to CP4

#245590

It has been this way for a while- at least a year or so. Spaces are no longer allowed in mobile file names. Replace with underscore or other character.?

Re: NVX vs. SVSI

#245589

开云体育

Hi,

?

the VLAN ?rewriting“ method you describe below sounds insane to me and i?d never even think about using that in a production environment.

I can?t imagine that this is how it?s supposed to work…

?

Cheers,

Thorsten

?

Von: [email protected] <[email protected]> Im Auftrag von FBC Tech Team
Gesendet: Donnerstag, 31. M?rz 2022 03:17
An: [email protected]
Betreff: Re: [crestron] NVX vs. SVSI

?

On Wed, Mar 30, 2022 at 2:14 PM eoqualls <ed@...> wrote:

Jeff, I’m not sure how you reached the understanding that we are only point-to-point, but it is not right.? Just Add Power has always provided many-to-many functionality (our original CEDIA demo was a 5x9 many to many matrix).? This has been true since 2008.? All of our current offerings provide many-to-many support and have been successfully implemented in a wide range of settings.? This includes VLAN and Multicast implementations.? We have countless installations with 100+ devices.? For example, the Cincinnati Reds ballpark installation is a many to many with over 300 end points.

?

Hi Ed,?

I appreciate the reply. As I said, "they are (were?)". Can you clarify if the routing method has changed? Our issue in 2010(?) was that the routing of the units we purchased for testing onsite was accomplished by rewriting switch port VLANs rather than traditional multicast network routing/IGMP Snooping. I.e. to route a JAP unit on port 1 of a switch to port 20, 25, 33 and 46 you would use the JAP software to command the network switch to change the ports to be on the same VLAN via network switch commands and the receiving JAP units would display whatever streaming video came over that VLAN. If you wanted to route across switches in larger systems, we also would have to add those VLANs to the uplink ports and command the other switches to change the target port VLANs as well. If memory serves, you could only command one switch with the JAP control software, which could be a "real" or "virtual" switch. A "real" switch system would be limited to what you could physically stack together (1U switches with stacking cables) or how many cards you could fit in, say, a Cisco 6800 chassis or similar. All of our network cables would have to be home run to that physical switch, which would have been very problematic for us. A "virtual?switch" was also possible, and would allow you to have multiple switch groups to avoid having to home run everything, i.e. the Cisco Nexus line where the core and FEC expanders can all over a site but be seen as one single switch. We'd considered that idea, but found the FEC expanders to be way too loud to be located in conference and training rooms (think Cisco 3850 fans when it first starts up...but ALL the time...yuck).

?

SVSi, Electrosonic/Extron, Evertz, Crestron NVX (which actually wasn't available at the time of our install) and other network protocol streaming products are routed like any other network traffic. I can have all my control devices on VLAN10, streaming devices on VLAN11 and VTC camera/touch panel control on VLAN12, and those assignments never change. Rather than communicating with switches to route things around, we command the decoders directly from the Crestron control system to pull in this or that encoder stream .?

?

If JAP products are now using standard network routing like the SVSi and NVX systems are, rather than changing switch?VLANs, that's great as that would give us another product to consider. If it's still routed via commanding network switches to change VLANs for routing, that's not something that works well for our large systems (and our network departments weren't too keen on that either).

?

Interested in your thoughts,
Jeff

?

-------------------------------------

Jeff Klein, DMC-E
Head Volunteer AV Geek
Faith Baptist Church
Glen Burnie, Maryland

(Website / Twitter)

?/ @FBC_TechTeam

?/ @mixingforjesus

?

"Clothe yourselves, all of you, with humility toward one another, for God opposes the proud but gives grace to the humble." 1 Peter 5:5