Hello and thank you for the quick responses.
I apologize for the vague post without links, but I didn't want to come across as a "spammer."
@Greenman, @jean-emmanuel has already replied to you, and you've also figured it out, but if you still need the file, I'll post it.
Ontime is an excellent open-source tool, whether used just as a timer or as a whole event manager.
The ability to display different HTML pages with customizable informations on different addresses makes it a very valuable tool.
Unfortunately, to fully utilize it, the event organization also needs to be at a certain level of "seriousness" (and if you've ever worked in a conference, you know it's far from be that level =( ).
@jean-emmanuel, looking at the Ontime's documentation, the feedback it sends can be received using OSC and web-socket, in my case /ontime/timer, pointing to port 9000.
As a noob, I don't understand why the log shows the feedback is received on port 51331 with path /ontime/update/xxxxxxx .
Basically, I can only use Open Stage Control to send commands. Without reading the status of a button, value, or response, it's only usable for private/amateur projects, and that's a shame.
I've studied the Reaper's Template, which is wonderful and has shown me all the potential of your software, but Reaper allows for a very detailed level of feedbacks via OSC, that (probably ?) lacks in Ontime.
But OSC protocol is a standard, so a feedback must be received without problems if (as is stated in ontime documentation) i point to the right path... am i wrong ?
Digression:
@jean-emmanuel, I've been involved in live and studio events as a performer, technician, supervisor/organizer for over 20 years, and having a customized interface that allows me to have the flexibility to manage what I need how I want has always been a concern.
I am able to interconnect different hardware/software using MIDI, DMX, TCP ...
over the years, there have been several software solutions that have helped manage events, but all with custom interfaces that couldn't be easily integrated with each other, until the advent of Companion (the de facto standard).
The problem with Companion is that it's StreamDeck-centric, so its interface is button-oriented, and even though they've introduced the ability to use rotation, it lacks features like sliders, pads, and overall customization...
But as inputs and outputs server, with feedbacks and expressions, is very powerful.
The potential of your software is very high, but unfortunately, the target users are also "high":
if you don't know how to program or aren't very familiar with code/protocols, you'll quickly hit a wall trying do basic things.
For example, the code that you've posted, i know (because i've read the documentation) that must be saved in a file.js and loaded as custom module.
But i don't know how to really use it (i'll spend time to understand, i saw something about referring widgets in documentation), because i'm not a developer or coder, i can argue and try and error it, but at the end, i'll probably get frustrated and leave it as is, keeping the frame solution.
(and it's my fault, not your ^,^ )
I've read the documentation and tutos, but it seems to take for granted some previous background.
It would be helpful to have at least a collection of links to start from to understand the basics, or somewhat more practical documentation, like that of Chataigne, with pratical pieces of working code to start with (this is absolutely not a criticism, but a suggestion to be more noob-friendly, as i am).
Here I found working templates for Pure Data, Reaper, Cubase, etc., but little or nothing for what I think is the real field of use of Open Stage Control: professional audio-video.
I came to your software because I use many software/hardware that communicate via OSC/Websocket/DMX/MIDI, have Companion modules, but not being able to customize its interface, I was looking for a way to "design it", communicating directly with them via OSC.
Companion's Generic OSC module only receives, it doesn't give feedbacks (despite being strongly requested by the community), while modules created for specific hardware and software (including Ontime, which displays the timer easily in different formats) do so without problems.
Maybe you could consider creating an Open Stage Control module for Companion, so that you can use feedback directly from the modules already made for other software/hardware and expand the possibilities of your software.
For now thanks for your time and your work.
eMMe