Closed rcdailey closed 1 year ago
I removed them as they didn't really work and they just wrapped existing functions anyway. I updated the readme with my latest config https://github.com/iloveicedgreentea/jvc_homeassistant#useful-stuff
I would recommend using user modes instead of the automation because setting the low latency state is too unreliable with the way JVC implemented it
I was looking for documentation on exactly what you set, and the best I could find is here: https://github.com/iloveicedgreentea/jvc_projector_improved/blob/master/jvc_projector/optimal_settings.py
So you're saying I shouldn't use this anymore? I'll check out your guide updates.
Could you please also explain how you set up your user modes as well? Thank you again.
EDIT: I do see a tiny snippet of how they get set up on the jvc improved repo, but it needs to be more detailed IMHO.
Also: Why do you use installation modes? I've deliberately avoided those as it requires duplicating lens adjustment settings, and I do not want to have to make the same lens adjustments multiple times per mode.
EDIT: Dumb question. Looks like you have a mechanical projection screen and you can change your aspect ratios dynamically. Makes sense.
Yeah I need to remove that file eventually. I added my HA yml in the readme which replicates the remote with some shortcuts for installation modes
There are 3 things - content type, user mode, and installation mode
User modes are per content type so you have different user mode sets for SDR vs HDR
If SDR, set user1 to be whatever you want, including low latency settings, user2 for another thing, etc.
Personally for HDR I have frame adapt for film, and HDR10 for gaming which has low latency enabled. You can easily make a button to switch to those, or you can make all of them user1, user2, etc so you can have one button for film mode and one button for gaming mode (I think, haven't tested this out). User modes are why I removed the services because all they did was write configs which is not a good pattern. Much easier to switch between presets and since users had different presets it wouldn't make sense to have services for this.
Installation modes are independent of user modes. IM dictates focus, zoom, etc. I have buttons to switch between 1.78 and 2.4, etc on the PJ, not the screen.
None of the four services work:
I get an error when I push the buttons on the remote you have in your README. For example, this button: