Comments (7)
Well, that's certainly a valid idea. The only thing is that I think that a hard-coded resolution is actually a feature rather than a bug.
The reason being that if you have a setup, you want to make sure you know what resolution you're running. Otherwise it would be difficult to produce content.
Now, if you bring up some content on the screen and the resolution is, let's say 1280x720 instead of 1920x1080, you might not immediately spot that if you have an auto-resizing setup. Sure, you could check the X11-logs, but chances are you won't and simply make an incorrect assumption.
Perhaps a better solution would be a hybrid of the two use a dynamic resolution, but displaying the resolution in the web interface.
from anthias.
Ok agree that it easier to spot the issue if you have a static resolution of the browser, but in the case of web pages I believe it is up to the page to detect, most of my setups uses javascripts on the client to correctly scale everything.
I have seen some issues with non matching size of the browser that was not directly visible (overscan enabled) and also if you change monitors or rotation it's a somewhat unnecessary step to manually change the configuration.
Would showing the resolution on the splash page possible the server status page be a acceptable solution?
from anthias.
The overlay issue is a separate issue altogether. I've struggled with that too, and I think the only way to fully solve that is to build a database of monitors and their required overlay (or even better, have that pushed up stream for auto detection). I have data from a few professional LG and Samsung monitors.
Showing it on the status-page might be a reasonable compromise, but we would still have to first retrieve the resolution (probably from parsing the X11-logs or some other X11 utility), and then put it in the database for permanent storage.
from anthias.
Or only use displays with full-pixel support to avoid the overscan issue. ;) (for me it was a bad display, that I since then have stopped using)
I was thinking that javascript that posts back to the server is the most portable.
A fallback could be to use the output from xrandr, on the other hand there must be python bindings available to do this in the viewer and "post" to the server.
If we want more information from x and recommended overscans etc then there is the XOrg logs, or maybe dumping monitor edid, but for me it is enough to just have auto resolution, and for the Raspberry Pi it is up to the user to configure possible overscan in /boot/config.txt
Will start work on a auto_resolution branch.
from anthias.
As I wrote in a comment to issue #7:
on a Raspberry Pi, with raspbian, we should be able to use the tvservice command to get resolution info.
pi@raspberrypi ~/screenly $ /opt/vc/bin/tvservice -s
state: HPD high|DVI mode|HDCP off|composite off (0x120016), 1920x1200 @ 60Hz, progressive
(sidenote: I noticed that on openelec tvservice is in /bin )
from anthias.
Good point @axel-b. That will definitely be easier than trying to parse it from the logs.
from anthias.
@vpetersson Thanks!
Would it be valid to remove the resolution parameter to uzbl as well as removing it from settings module and configuration file?
from anthias.
Related Issues (20)
- Add support for changing timezone settings via the Settings page.
- Migrate database to use Django ORM.
- video output is underscanned HOT 10
- Rename remaining Resin references to Balena.
- Replace existing auth code with Django-based auth.
- Convert `bin/upgrade_containers.sh` to a Python script.
- Shutdown and reboot is not working via web UI after a while.
- Replace `retry` with `tenacity`.
- Deprecate the use of CoffeeScript
- Anthias stuck on Screenly screen HOT 8
- Anthias is not working properly on local networks HOT 1
- Pi 3B Bullseye: Anthias update hangs at "TASK [system : Remove libc6-dev]" HOT 5
- Request: Make Anthias work without internet HOT 18
- Update Python 3.7 on Docker containers HOT 1
- Typing error in Upgrade-Instructions HOT 1
- Use Poetry (or similar tool) to manage dependencies in the Raspberry Pi host environment.
- Webpage asset contents are not refreshed when it's the only asset active HOT 3
- Publish API documentation on anthias.screenly.io
- Add support for x86 devices
- White screen flash at beginning of URL asset display
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 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.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
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.
from anthias.