balonmanovetusta / handball-liveshow-spain Goto Github PK

Create a scenes set and register sets and scenes with the backend.

TODO

• Set of scenes collections.

Build binaries to use it as standalone application in Windows/Linux and macOS

If you set a limit time of 30 minutes sometimes stops before 30:00 at 29:59. Probably because to determine stop is checking tickTime and not checking that currentTime >= limit and currentTime < (limit + tickTime)

Extra time is not supported currently.

Would be great the usage of pm2 to restart on crash.

Other possibility is to run it on VPS by using Docker that can do the same task. This would avoid the need of using local instance but to use api keys would be great to add jwt or similar and authentication.

The most awesome thing to do would be enable only when there is a match based on rfebm data.

Suspensions can be optimized to render more atomic and granular which could improves performance.

Probably also a good approach to improve the performance could be more usage of React.memo.

Another good idea its to wrap all suspensions in a Lazy component that only loads when any suspension is on the actions.

Docker was added at the same time of some stuff was removed because there were some issues with include-nodecg.

Currently you can watch always for changes to build but you must restart manually docker container.

Watch for changes

pnpm run pm:dev

Restart podman

After build is done:

pnpm dev:rs

Problem

This is slow for developing but currently is the best option to avoid errors of using include-nodecg.

Ideally, would be use include-nodecg with pm2 as it was before and use Docker builded image for production.

Show the current classification when match is timed out or in a banner slideshow.

Description

Integrate million to make web faster.

Tasks

• Install million
• Replace all .map to use the <For /> component.
• Add million in top level page which makes easier to integrate it. If fail go more atomic and so on until it works.
• Check performance before and after to know if it really improves the performance.

Reference

• https://million.dev/docs

Refactor and improve all related code to the stopwatch.

TODO

• Review the backend code and update methods to use post/get/put instead of having all in get.
• Refactor the hooks
• Usage of workers to update the timer instead of doing all in same process.

This is a low priority because currently the most important thing is have working graphics for the matches.

Add an api rest to add result, control stopwatch

Control ATEM Mini to show live graphics.

Autodiscover

For autodiscover we can use mdns package and there is example in companion module for atem on how to implement so it is basically a copy&paste and adaptation work.

Idea

The main idea is to generate faders and macros when live and execute them dinamically. Probable these macros should be preconfigured manually by a developer.

Motivation

The idea of automate transitions and scenes based on current game status to make it easier to stream for any no known technical person.

Other related improvements

Automate transitions and scenes of OBS. But the idea of this project is to full replace obs with the only main idea of being focus in handball events. Whatever there are things that are technically more complicated like Instant Replay which can be easier to handle with OBS because there is already a plugin that does that. Whatever the idea of Instant replay should be explored because is technically possible with the usage of MediaStream & MediaRecording apis by using a capture card. Probably a Raspberry Pi will be short for an usage like this but there are some affordable mini pcs that probably can do this work.

Other idea can be a different Graphics for each scene and switch them into the ATEM... All possibilities should be explored.

References

• https://www.npmjs.com/package/multicast-dns
• https://www.npmjs.com/package/atem-connection
• https://github.com/bitfocus/companion-module-bmd-atem

• Is not showing the score in the panel which makes difficult to follow the current result
• Reset button for the scores is enabled by default which can introduce undesired reset

Adds authentication to deploy in a public server for display the graphics in live streamings.

Use remotion to generate independant video with live scoreboard to add it fixed in a post match video edit.

Also can be good generate images to edit in post match with any video editor.

Usage of team names in scoreboard is not working.

Currently you can configure the names but they won't be showed on graphics page.

There is also a problem when you try to hide shields or shield is not a working url.

Customization of the appearance of the scoreboard.

This can be done manually with css/html but the idea is to use overlays to do it and moving the items by dragging.

The colors can be modified with css variables. Currently is not active and working but it can be done.

Use custom rfebm parser to get live match details.

If call start stopwatch rest api resets the stopwatch.

• Start scene for introducing the match with:
  • Local players list
  • Visitor players list
  • Match Date, place, week and referees.
• Presentation slideshow to show player 1 by 1 or list.

Stowatch is running well and stops well when introduces only 1 period and limit time but more periods to stop automatically is not working at all.

Refactor of all code is absolutely necessary. Currently has no architecture or minimal order all the code.

• There are components too complex
• Ideally all graphics component that have administrative part (dashboard) should be in same component folder under src/components/<component_name>/[graphics/dashboard].
• Not common libraries should be in the component folder.
• Replicants name should be avoided and create a custom hook use<Schema>Replicant for each schema to avoid errors.
• Routes should not be all using get method.

Necessary features

• Customize css vars, currently is already possible and shields configuration do that right now. Would be nice personalize almost, at least, all colors.
• Save current advert banner and do not restart all banners when hide/show. If you hide the banners and show it will always start from same banner which means not equality of advertising for every sponsor.
• Create banners from sponsor logos.

Description

Customize banner time, animation and Height individually.

This would be useful to show some temporary data like classification or auto promos with less time than sponsor times or rotation components instead of images.

TODO

• Advertising must be in its own NodeCG workspace.
• A select of banners to show only selected banners.
• Customize the seconds that it will be showed (optionally). TODO this, time that a banner is showed before transition must be calculated like in the stopwatch.

Not in match scene title is currently change messages based on hardcoded time. Would be very good to look for the stopwatch limits to put those messages and let the user customize those messages. Detecting if it is a break based on the number of periods and limit.