-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Ross Carbonite Black Solo nolonger works after update #620
Comments
Hello there dustenharward 👋 Welcome to TallyArbiter! Thank you for opening your first issue for the Tally Arbiter project. Tally Arbiter fosters an open and welcoming environment for all our contributors. Please adhere to our Code Of Conduct. If you have more to contribute to this issue, please comment down below! We will try to get back to you as soon as we can. |
Did it crash after editing a device source? It looks in the attached log that you edited the source |
In a sense yes it crashes after editing a device source. To explain what i mean. It lets me add the Source and in our case its the Carbonite Black Solo. When i go to edit the device source it will let me add it then then it does not keep it. I then have to shut down the application and restart it and have to attempt it a few times to get the device source to take it. Once it takes one it will take it on all of the other devices. from there i am getting the error or the bug report when i switch to the first source. In previous versions of TA the Ross Carbonite Black Solo source did not work and I had to use a generic TLS device option but i have found when setting it up that way there is no option to select the bus and i get a bus not selected error. I just performed an update to 3.0.7 and its still giving me an error. Here is the stacktrace from the error. I am happy to do a remote session of some kind if its easier for you to diagnose whats happening on the device and specific configuration. I know its hard to reproduce a specific error without the known hardware. |
One thing that has always bothered me and i can never remember in the device source it asks for an address. Is this supposed to be the TLS address or is this supposed to be the IP address of the source? I have tired both and i think i am getting more information from the TLS address. |
It’s always supposed to be the tsl address or the physical input number depending on your device type. Never IP address in this area because you’ve already associated the IP at the source level. |
Thanks for the the note on the intention for the Address field. There is one place that the Device Edit info I see a field labled TLS address so that one is very clear what its intended for. under the device source there is an Address field that is just listed as Address. IF this is supposed to also be a TSL address then maybe its best for that field to have a label of TSL address instead of just Address. For the Ross Carbonite Black solo device and the i don't enter an IP address its just a port number. there is not anywhere that I can enter an IP address. I am associating the IP address of the computer running the software from our video switcher. So i think the data is still coming across from that direction. With my current configuration setup as the Source as Ross Carbonite Black Solo Port 4459 using TCP here are the issues i am seeing:
Again if its easier to have access to this computer for diagnosis I am Happy to work with you to make that happen. If its a configuration issues on my end please let me know what I need to change. |
If TA is acting as a client, that source type will have an IP. If it is the server, it’s just listening on a port. In your case with a Carbonite, it is the client sending data to TA. I have 3 carbonites. Just no free time to fix this. |
Ok. I will roll back to the working version that I have (2.0.16 if anyone else needs to know). From my understanding I think my use case has TA as the server and its distributing the tally to the M5sticks that I have and its coming from Carbonite. I will look for an update here some time later on. Thanks for your hard work on this! Its a great project that helps me out a lot and I know it does others. If there is any way that I can assist with this feel free to ask, I am happy to help in any way. |
Hello just following up to see if this was addressed in the last update or if this issue is still present before I try an attempt at 3.0.8 |
Still present |
just checking in to see if this issue has been addresed in 3.0.10? |
You can view the commit history here at any time to know if the change was addressed and I will generally try to follow up on issues as they are fixed or related: https://github.com/josephdadams/TallyArbiter/commits/master/ |
What happened?
A bug happened!
I am getting the following error now:
There was an unexpected error. Please open a bug report on the project's Github page or contact one of the developers.
Stacktrace:
TypeError: Cannot read properties of undefined (reading 'find')
at _loop_2 (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:340:84)
at _loop_1 (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:353:21)
at RossCarboniteSource.updateRossCarboniteTallyData (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:367:13)
at RossCarboniteSource.addRossCarboniteTally (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:296:26)
at RossCarboniteSource.processRossCarboniteTally (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:263:18)
at Parser. (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:245:31)
at Parser.parse (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\node_modules\packet\index.js:446:25)
at Socket. (C:\Users\LFCH\AppData\Local\Programs\tallyarbiter\resources\app.asar\dist\sources\RossCarbonite.js:247:30)
at Socket.emit (node:events:517:28)
at addChunk (node:internal/streams/readable:335:12)
Error datetime
2024-01-08 09:00:36
Logs:
[2024-01-08 08:59:20] info: Starting OSC Setup.
[2024-01-08 08:59:20] info: Loading the stored Tally Arbiter configuration file.
[2024-01-08 08:59:20] info: Tally Arbiter Sources loaded.
[2024-01-08 08:59:20] info: 1 Sources configured.
[2024-01-08 08:59:20] info: Tally Arbiter Devices loaded.
[2024-01-08 08:59:20] info: 8 Devices configured.
[2024-01-08 08:59:20] info: Tally Arbiter Device Sources loaded.
[2024-01-08 08:59:20] info: 0 Device Sources configured.
[2024-01-08 08:59:20] info: Tally Arbiter Device Actions loaded.
[2024-01-08 08:59:20] info: 0 Device Sources configured.
[2024-01-08 08:59:20] info: TSL Clients 1 Second Updates are turned off.
[2024-01-08 08:59:20] info: Tally Arbiter Cloud Destinations loaded.
[2024-01-08 08:59:20] info: Tally Arbiter Cloud Keys loaded.
[2024-01-08 08:59:20] info: Initiating Setup for Source: Carbonite
[2024-01-08 08:59:20] info: Source: Carbonite Creating Ross Carbonite Black Solo connection.
[2024-01-08 08:59:20] info: Source: Carbonite Creating connection.
[2024-01-08 08:59:20] info: Source: Carbonite Reconnect attempts 5.
[2024-01-08 08:59:20] info: Source: Carbonite Default reconnect timeout: 5000.
[2024-01-08 08:59:20] info: Source: Carbonite Connect triggered at startup.
[2024-01-08 08:59:20] info: Source: Carbonite Closed Ross Carbonite Black Solo connection.
[2024-01-08 08:59:20] info: Source Setup Complete.
[2024-01-08 08:59:20] info: Setting up the Main HTTP Server.
[2024-01-08 08:59:20] info: Main HTTP Server Complete.
[2024-01-08 08:59:20] info: TallyArbiter advertised over MDNS.
[2024-01-08 08:59:20] info: Starting socket.IO Setup.
[2024-01-08 08:59:20] info: Socket.IO Setup Complete.
[2024-01-08 08:59:20] info: Starting Listener Providers.
[2024-01-08 08:59:20] info: Starting VMix Emulation Service.
[2024-01-08 08:59:20] info: Starting TSL Listener Service.
[2024-01-08 08:59:20] info: Initiating 0 TSL Client Connections.
[2024-01-08 08:59:20] info: Finished TSL Client Connections.
[2024-01-08 08:59:20] info: Starting HTTP Server.
[2024-01-08 08:59:20] info: OSC Sending Port Ready. Broadcasting on Port: 5958
[2024-01-08 08:59:20] info: Source: Carbonite Connected.
[2024-01-08 08:59:20] info: Source: Carbonite Ross Carbonite Black Solo Connection Opened.
[2024-01-08 08:59:20] info: Finished VMix Emulation Setup. Listening for VMix Tally Connections on TCP Port 8099.
[2024-01-08 08:59:20] info: Tally Arbiter running on port 4455
[2024-01-08 08:59:39] info: Device Source Added: CAM1 - Carbonite
[2024-01-08 08:59:39] info: Config file saved to disk.
[2024-01-08 09:00:00] info: Device Source Edited: CAM1 - Carbonite
[2024-01-08 09:00:00] info: Config file saved to disk.
[2024-01-08 09:00:11] error: Caught exception: TypeError: Cannot read properties of undefined (reading 'find')
[2024-01-08 09:00:11] error: Caught exception: TypeError: Cannot read properties of undefined (reading 'find')
[2024-01-08 09:00:26] info: Device Source Edited: CAM1 - Carbonite
[2024-01-08 09:00:26] info: Config file saved to disk.
[2024-01-08 09:00:36] error: Caught exception: TypeError: Cannot read properties of undefined (reading 'find')
Config file:
{
"security": {
"jwt_private_key": ""
},
"users": [],
"device_actions": [],
"device_sources": [
{
"deviceId": "ebe3664f",
"sourceIdx": "0",
"address": "1",
"bus": "me1",
"sourceId": "6b0985f4",
"id": "c67cbcbe"
}
],
"devices": [
{
"name": "CAM1",
"description": "Camera 1",
"tslAddress": 1,
"enabled": true,
"id": "ebe3664f",
"linkedPreview": false,
"linkedProgram": false
},
{
"name": "CAM2",
"description": "Camera 2",
"tslAddress": 8,
"enabled": true,
"id": "5855afca",
"linkedPreview": false,
"linkedProgram": false
},
{
"name": "CAM3",
"description": "Camera 3",
"tslAddress": 3,
"enabled": true,
"id": "a559df42",
"linkedProgram": false,
"linkedPreview": false
},
{
"name": "CAM4",
"description": "Camera 4",
"tslAddress": 2,
"enabled": true,
"id": "5987c046",
"linkedPreview": false,
"linkedProgram": false
},
{
"name": "CAM5",
"description": "Camera 5",
"tslAddress": 5,
"enabled": true,
"id": "b78a84b2",
"linkedPreview": false,
"linkedProgram": false
},
{
"name": "CAM6",
"description": "Camera 6",
"tslAddress": 4,
"enabled": true,
"id": "dc963603",
"linkedPreview": false,
"linkedProgram": false
},
{
"name": "CAM7",
"description": "Camera 7",
"tslAddress": 6,
"enabled": true,
"id": "b9bc17a5",
"linkedPreview": false,
"linkedProgram": false
},
{
"name": "CG",
"description": "CG",
"tslAddress": 7,
"enabled": true,
"id": "69c13eab",
"linkedPreview": false,
"linkedProgram": false
}
],
"sources": [
{
"data": {
"port": 4459,
"transport_type": "tcp"
},
"name": "Carbonite",
"sourceTypeId": "e1c46de9",
"reconnect": true,
"enabled": true,
"id": "6b0985f4",
"max_reconnects": 5,
"connected": true
}
],
"bus_options": [
{
"id": "e393251c",
"label": "Preview",
"type": "preview",
"color": "#3fe481",
"priority": 50
},
{
"id": "334e4eda",
"label": "Program",
"type": "program",
"color": "#e43f5a",
"priority": 200
},
{
"id": "12c8d699",
"label": "Aux 1",
"type": "aux",
"color": "#0000FF",
"priority": 100
},
{
"id": "12c8d689",
"label": "Aux 2",
"type": "aux",
"color": "#0000FF",
"priority": 100
}
],
"externalAddress": "http://0.0.0.0:4455/#/tally",
"remoteErrorReporting": false,
"uuid": ""
}
Version
3.0.6
Distribution
Source
OS
Windows
What browsers are you seeing the problem on?
Chrome
If applicable, What Listener Clients are You Using?
M5 Stick
TallyArbiter configuration
Relevant log output
Error stacktrace (if applicable)
No response
The text was updated successfully, but these errors were encountered: