A dashboard for everything in your show.
A dashboard for everything in your show.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
The button should glow to indicate what arrangement is active. Arrangements will be increasingly useful as devices are added- pinning all the wireless to arrangement 2 while monitoring consoles on arrangement 1 would be sick
The Shure digital wireless ULX-D, QLX-D, SLX-D all support control over TCP/IP (looks to be quite similar across the series). Even supports viewing meter levels.
what are these line in view.js doing? just debug? I'm trying to go through and clean up debug logging/commented out code and things like that and ran across this.
Lines 23 to 25 in 5ccb3c0
There seems to be some issues I've run into when deleting devices in conjunction with the save slots. If the device being deleted is in the active save slot it doesn't get deleted from that save slot.
Hi, I'm really interested to use your software with eos, but I cannot make it work. View cue find eos but it has a red cross near it. I've followed the instructions you provided on the selected window but the red cross doesn't disappear and connection is not possible.
Is it a bug? I'm trying to communicate with eos on my own PC
Thank you
looks like all the devices get saved, but during loading, some are deemed duplicates and not added
It might be nice to have some sort of implementation score for each current plugin. Or maybe utilize the projects section of the Github Repo to track progress for each plugin, maybe have a project per plugin with a list of todo/doing/dones or something like that? Just a thought.
d3 is getting incredibly popular to run complex video and projection shows in theatre.
It is surrounded by a great community of tinkerers who love projects like Cue View!
I would personally love to see EOS cues next to d3 cues. It's something I always have to do when programming a show.
d3 has extensive documentation on its protocols. The timeline nature of the software will probably require the extraction of Cues, Tags, TC and other triggers from the d3 timelines.
I know it is possible over OSC, but also using the new disguise API which seems very powerful.
Link: https://disguise.one
OSC: https://help.disguise.one/en/Content/Configuring/Devices/Common-Devices/OSC.html
API: https://help.disguise.one/en/Content/Configuring/API/APIs.htm?Highlight=api
The d3 designer software also recently became free, without the need of a hardware dongle anymore. This should allow everyone to test and develop application with d3 for free! https://www.disguise.one/cloud/
Thank you for this amazing app!
Only unprotected workspaces are able to be connected to. It would be nice to be able to connect to workspaces that have a pin (maybe with the option to save the pin for future or always ask)
Looks like the ESLint and Prettier stuff hasn't been regularly run. Could enforce this on the main branch using GitHub Actions.
Could also do some automatic stuff using GitHub Actions like auto apply and commit formatting/linting (not all linting things can be auto fixed).
I would love to see support for SCS Show Cue Systems.
Got my test windows machine running artnet, SACN and EOS. For some reason it detects and adds a shure device for that IP. I will do some more digging into what the search is sending/receiving for that port.
If there are no workspace QLab device will just show "Incorrect Passcode or OSC Access Permissions". Should be fairly easy to detect that there are no workspaces loaded and display a message. No way to tell if a passcode is correct if a workspace isn't loaded.
Some initial ideas!
Currently on most plugins the last data is just displayed, after a certain timeout (heartbeatTimeout) the device should change status.
(I thought it worked that way but here we are)
Describe the bug
"playback progress" broken in 0.9.9. works in 0.9.6. I think just in QLab?
To Reproduce
https://twitter.com/rsmck/status/1663118833815617536
Just generically. I'll occasionally run into things that are laid out using tables that just don't seem "tabley"
Describe the bug
On upgrading EOS to V3.2 Cue-View stopped displaying cues.
To Reproduce
Steps to reproduce the behavior:
In all of the above circumstances, sACN can be viewed by Cue-View but not EOS cue lists.
Expected behavior
Expected Cue-View to display cues from EOS.
Desktop (please complete the following information):
Additional context
Have tried multiple machines and multiple network arrangements. This could be (probably is) an ETC third party OSC bug.
Similar to Shure, Sennheiser wireless has a pretty open UDP protocol for G3 and G4 series so should be fairly easy to add. It might be a while but I should be able to get my hands on a slew of receivers in both these series. At a quick glance the protocols look pretty much the same from G3/G4 so should be doable with one plugin.
Moving "future devices" to issues so that some discussion can take place if needed (look/feel ideas, libraries, control information, etc.).
Moving "future devices" to issues so that some discussion can take place if needed (look/feel ideas, libraries, control information, etc.).
When I launch Cue View 0.9.5-pre (Mac), the + icon is missing from the Add button, and the button is not functional (hovering or clicking produces no change). This is a brand new install.
I do have a console error during plugin file loading:
/Applications/Cue View.app/Contents/Resources/app.asar/preload.js:13 init!
/Applications/Cue View.app/Contents/Resources/app.asar/src/plugins.js:12 Loading plugin files... /Applications/Cue View.app/Contents/Resources/app.asar/src/../plugins
/Applications/Cue View.app/Contents/Resources/app.asar/src/plugins.js:19 artnet started
/Applications/Cue View.app/Contents/Resources/app.asar/src/plugins.js:19 eos started
node:internal/fs/utils:342 Uncaught Error: ENOENT: no such file or directory, open './plugins/eos/cue.ejs'
When a workspace has nested groups there seems to be a problem with the logic of when to display the bottom left corner (See attached image).
An example: https://github.com/philhartung/aes67-monitor/
If focus is on the document root and not on a specific text input field, Select All attempts to select all text in the app and makes graphical weirdness. I think Select All should be disabled when the :focused element isn't an input.
I believe most of the Yamaha digital consoles (TF/CL/QL/etc.) all speak a similar protocol. Still trying to find a decent document about the protocol.
Is your feature request related to a problem? Please describe.
We run Cue View on the DSM's desk on a very small screen in a fixed environment (Qlab and Eos only), every pixel of width matters, so it would be good to be able to hide the sidebar column on the left via a menu bar option or keyboard shortcut.
Describe the solution you'd like
Addition of a menu item "Hide Sidebar", the state of which is remembered when the app is closed/reopened.
Have you had any thought of adding a viewer for PosiStageNet Traffic.
https://posistage.net/
https://github.com/vyv
You would possibly have to specify which Tracker (Axis) you want to see, and maybe a scaling and Unit (mm, ft) etc.
Thanks
For example, changing a QLab device into an Eos device results in an Eos device with a Passcode field. Similarly, changing an Eos device into a QLab device doesn't add the Passcode field.
Same with port.
Is your feature request related to a problem? Please describe.
It takes a long time to get all the data from a big QLab workspace with thousands of cues. Could affect performance on the the device. Similarly for Eos, etc.
Describe the solution you'd like
Slow down or optimize how data is collected.
If you have auto update enabled and there is no update it will always pop up a dialog saying there is no update available. Every time you launch the app.
Moving "future devices" to issues so that some discussion can take place if needed (look/feel ideas, libraries, control information, etc.).
The SQ series has a MIDI over TCP/IP control scheme outlined here
Currently, only basic information for cues is loaded.
Moving "future devices" to issues so that some discussion can take place if needed (look/feel ideas, libraries, control information, etc.).
There are some inconsistencies across plugins of the format for the config object. So I think a once over of all of them should be done to make sure things are nested/named properly. I just noticed the mayChangePort didn't line up in a couple of the plugins so think it's best to run through the config on everything.
Hi, please add support to show cue system, it's the only real alternative to Qlab for windows.
https://www.showcuesystems.com/cms/
The developer of the application is really active!
Thank you
Problem: Lots of cue lists cause confusion
When an EOS feed has multiple cue lists, displaying all of them can make the UI busy and can make it less clear what the current state of the venue is. In complex show structures, lots of cues being triggered can make it hard to determine the primary state of the device/venue.
Proposal
I'd love the ability to filter or specify a cue list to display. For example, always show only Cue List 1/. Ideally, this would be persistent enough, so I can 'set and forget'.
I can imagine that there are circumstances where having multiple instances of the same device with different cue lists might be useful, but my common use case wouldn't need that.
Context
We use Cue-View to monitor multiple venues simultaneously in order to enable a Duty LX to understand the state of each venue. When shows have multiple cue lists within EOS, particularly if they are used during show running (rather than rig checks), this can cause a confusing UI.
hi,
When using Cue View for me (I might be doing something silly so if I am my apologies) Cue View doesn't appear to show the Pre Wait, Action or Post Wait progress on the cues.
However, this data is exposed via OSC which is I believe how Cue View communicates with QLab.
The OSC Commands available for this are:
/cue/{cue_number}/PreWaitElapsed
/cue/{cue_number}/ActionElapsed
/cue/{cue_number}/PostWaitElapsed
For these, the OSC Reply will look something like this:
{
"status":"ok",
"data":"90.1234",
"workspace_id":"7ABC...",
"address":"/cue/{cue_number}/ActionElapsed"
}
The data field contains the number of seconds into the PreWait, Action or PostWait
There is also a number of OSC commands where the data field contains the percentage though, rather than the number of seconds, these are:
/cue/{cue_number}/percentPreWaitElapsed
/cue/{cue_number}/percentActionElapsed
/cue/{cue_number}/percentPostWaitElapsed
I was wondering if this would allow for enhancement of Cue View at some point - unless the feature is already implemented and I am managing to be a fool somehow?
I do see that Cue View shows me the fact that a cue is active and I can't see any mention of these OSC commands in the plugin javascript file.
Sadly, I don't believe that I am competent enough to add this functionality myself.
Kindest Regards
Peter Hodgkinson
weird parsing in the template, probably!
Moving "future devices" to issues so that some discussion can take place if needed (look/feel ideas, libraries, control information, etc.).
I would love to see support for Light Factory.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.