YouTube-On-TV
# **YouTube TV**
[](https://www.youtube.com/tv)
[](https://www.youtube.com/tv#)
Simple YouTube TV Client for desktop based on [electron](https://www.electronjs.org/). You can connect a compatible device such as a phone or computer with Google Chrome and send videos to the app for viewing, just like on ChromeCast or smart TVs with YouTube.
🌎 Languages
This readme is available in the following languages:
- 🇺🇸 English
- 🇪🇸 Spanish
It implements a DIAL server (based in SSDP) to allow connection from devices that use this same protocol (limited to YouTube in this application).
Use the userAgent allowed by YouTube TV:
Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Large Screen Safari/534.24 GoogleTV/092754
It can use npm start or else npx electron . .
If you already have electron installed globally, you can start the app with electron .
📦 Builds
The project can be downloaded already built and ready to use. Available for Linux, macOS and Windows. On x86, x84 and ARM architectures.
| Platform | Architecture | Link | |—————|:—————-:|:——:| (https://www.youtube.com/tv#) All builds
⌨️ Key shortcuts
- Max. resolution config panel: Ctrl + S
- Fullscreen: Ctrl + F.
- Developer Tools: Ctrl + D.
- Change cursor visibility: Ctrl + A.
Not tested on Windows and macOS for ARM platforms, except for ARM Linux for Raspberry (armv7l).
⚡️ Last changes [2.4.0/2.4.1]
2.4.1
- Fixed bug where the YouTube TV process would not close completely on platforms other than macOS.
- The title bar is transparent (macOS only).
- The title bar of the window did not load the Spanish title.
2.4.0
- YouTube TV persistently stores parameters of the main window state, such as position, size, full screen and cursor visibility.
🔧 Configuration
YouTube TV now includes a window for configuring the maximum playback resolution.
This window can be opened by pressing the keys Ctrl + S.
Resolution has been limited from the developing environment for the following reason:
Nowadays the mayority of computers are provided with integrated graphics, i.e. they share memory with the rest of the system, different to discrete graphic cards, which include their own memory modules where they have an isolated storage space without external load.
This implies more workload for the processor, and there are cases where resolutions above 2K/4K begin to affect performance at exagereted level.
Obviously the final user can establish the resolution they prefer; nevertheless, YouTube is able to measure bandwith and automatically establish the best resolution available in relation with bandwith, which can be bothering, since frequently hardware capacities aren’t enough to reproduce those resolutions that high.