bitfocus/companion-module-analogway-livecore

Companion module for Analog Way Livecore series

companion-module-analogway-livecore's Issues

Screen Selection and Global Take

On my system Screen Selection with Global Take is not working. I use two linked Ascender 3204, a two Output Widescreen, five Singlescreen Destinations and a Confidence Output.
All other Commands are working fine!
Can't figure out where the Problem is...
I'm doing the Selection and then the Global Take on one Button.

Companion fails loading mastermemories for discrete screens

Companion fails loading Mastermemories, if Mastermemory does not not contain presets for every screen at once.

For Example: build mastermemory #1 for screen1 and screen3. Build an other mastermemory (#2) for just screen2.
Recall Mastermemory #1 in AW-Browser. Companion is now only able to recall Mastermemories which contain presets for screen1 and screen3. Recalling mastermemory #2 in companion will fail - in AW browser it works fine.

After recalling mastermemory #2 in AWbrowser companion will be able to load mastermemory #2 again - but now companion will not load mastermemory #1.

Reboot of Ascender solves the issue - but after saving or recalling a mastermemory in AWbrowser, companion is again limited to load only those mastermemories which where configured for the screens recalled in AWbrowser before.

found with:
Ascender 48 4k build 04.02.77
AWbrowser 1.0.19
Companion 2.4.0

Feedbacks for "Memory active" seem not to work

I recently tried to use the feedback abilities of this module and noticed peculiar behaviour. Sometimes buttons would not light up at all or only when buttons are pressed twice. I took a look at the code and noticed that there might be a bug as I understand it. I'm fairly inexperienced with github so I'm sorry if do not follow a proper form with this issue.

In analogway_livecore.js in the "on data" callback function defined in "init_tcp()" there might be a confusion with a deprecated function at line 274. Upon receiving a data chunk the code reads the data line by line by taking substrings of the chunk. The way "substring()" is used here suggests the first parameter sets the starting index for the string whereas the second parameter declares how long the string should be. However the second parameter of "substring()" refers to the ending index sould therefore be "i" if I understand correctly. Changing this lead to buttons lighting up correctly on my system - at fist.

Now comes a really confusing part and because I'm really new to this I'm not sure I understand correctly. After fixing the substring the buttons light up correctly but whenever I would trigger a take the PIpid-messages send by the livecore device would flip the preview/program-state so the memories selected for preview afterwards are highlighted as if in program - but only visually. The memories still load to preview. So for example when I load memory 5 into the preview of screen 3 the following is received: "PIpid2,1,4". When I now perform a take with something arbitrary and select Memory 5 again to be loaded into the preview for screen 3 I receive: "PIpid2,0,4" - changing the 1 for preview to 0 for program. While this happens everything is displayed normally in the AW Browser. But since this flip comes from the debug messages of the livecore device I just decided to build a toggle triggered by "take" that flips how the value for the preview/program-state is interpreted - not really elegant but it worked.

One last thing I noticed: Whenever I preform a take the feedback on the buttons highlighted would not change so you would not be able to see which memory is in program currently - since it never lights up. This switch could also be performed whenever a take occurs - by switching the values in this.memoriesPGM and this.memoriesPVW for the corresponding screen and calling this.checkFeedbacks("memory_active") afterwards.

I hope it helps :)

I used:
Companion 3.0.0
AW Browser 1.0.19
Ascender 16 - 4K v04.02.Build 77

Fade to Black

Hi

Thanks for this module. This is more of a query/feature request.

Is there a custom command for Fade to Black?

Regards
EM

analogway livecore: open a sequence file and start stop sequencer

for Analog Way livecore and similar systems it would be great to have the function to load a sequence file and start/stop the sequencer. Also the possibility to loop or unloop the sequence would be good.

Problems to connect companion to Livecore Nextstage 0802-4k

Hi
I am having some problems to connect companion to Livecore Nextstage 0802-4k
I am entering the right ip address and the right port 10600 for third party control, but nothing
the error in the log is:
16. 15:02:11 instance(livecore): Network error: connect ETIMEDOUT 168.254.43.60:10600
16. 15:01:48 instance(livecore): Network error: connect ETIMEDOUT 168.254.43.60:10600

and before:
16. 14:26:13 instance(livecore): Network error: connect EADDRNOTAVAIL 168.254.43.60 - Local (0.0.0.0:55938)

if someone can help me it should great!

No Livecore Presets in Companion

Ascender 32 4k triggers

Ascender 32 4k triggers only do take no matter what master memory is set to load...
Only when i restart the companion its starts to work properly again

Nextage 08 error

Describe the bug
A Javascript error uncaught exception. This occurs when attempting to make a master memory recall to the preview bus on the nextage module. I've included pictures of the error and the button settings. I have tested this master memory and it works fine in the RCS

To Reproduce

Expected behavior
I expected the master memory to load into the preview bus, which it doesn when I click ok on the error, there doesnt seem to be an error suppression option and having it pop up and not load my cue is a show stopper. thanks guys!

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: win 10
• Browser chrome
• Version 71.0.3578.98 (Official Build) (64-bit)

Unnecessary? Select variant

https://github.com/bitfocus/companion-module-livecore/blob/6c948feee1235aa888c71f8adec53e20ff8cfb45/analogway_livecore.js#L159

Why do people have to choose the variant? The module does not seem to use this data for anything?

Analog Way NeXtage 08 - 4K Variant

Can you please add support to the Analog Way livecore Module for the NeXtage 08 - 4k Variant.

The Variant value is 117.

Please let me know if you need any additional information.

Thank you.