-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Setting to stretch the image from the analog module from 4:3 to 16:9 #145
Comments
Caddx Baby Turtle (Larva X HD) supports 16:9 and 4:3 however it's native 16:9 (i.e. 4:3 is cropped). Also it has onboard DVR and footage in 16:9 is way better. The only issue is that HDZero Goggle doesn't support stretching the image to 16:9. Flying with the wrong aspect ratio is just awful (and I don't mean rendering a 4:3 feed in 4:3 but stretching 16:9 into 4:3). I do see that there is a difficulty to switch between 4:3 and 16:9 depending on the model possibly especially for people flying with both aspect ratios (rare). |
Larwa is not a tinywhoop, for such sizes it is possible to adjust the aspect ratio, but I see no reason to use an analog if there is hdzero. The analog is relevant only for 65-75mm, because hdzero is heavy. |
To be clear I'm using an analog module on the HDZero Goggle. Yes I can change the aspect ratio that the camera sends and lose what I could see on the side to gain a bit on the horizontal resolution. |
@wernight change aspect ratio in goggle or camera? |
@a-di-ez In the goggle so that if I set the analog camera to send 16:9 (received via TBS Fusion module) the HDZero Goggle would also render that in 16:9. For now I've change the aspect ratio that the camera sends (i.e. I get a cropped view but a bit higher horizontal resolution). Noticed that the DVR recorded video is always 16:9 which is good. |
@wernight great, but in your case it's better to switch to hdzero to get a high-quality picture |
You mean change the VTX to something like a HDZero Whoop / Race? Sure that'd improve quality if it actually fits and works with the camera and onboard-DVR (which I doubt). In any case I have digital VTX on 5" but I got the analog module for smaller quads and cheaper builds. Keeping analog either options (HDZero Goggle stretch the received analog feed to 16:9 vs cropping the analog VTX to 4:3) would have the same picture quality just "distributed" differently. I think the HDZero Goggles are also very popular with many analog users as I also noticed around me. |
Yes, analog support was a decisive factor for me to get rid of hdo2 |
I would also like the ability to display a 16:9 analogue image at the full 46 degree FOV of the goggles. There are cameras like the Caddx Ant Lite (not the FPV Cycle edition that is 4:3 native) that I can't currently use due to stretching, but would love to on lighter 65mm builds. I really like the way the goggles handle the HDzero 16:9 vs 4:3 image where the goggles are always 16:9, but the image from the camera either fills up the screen (16:9) or is displayed with black columns either side (4:3). This means I don't have to set my goggles to a particular mode and can mix cameras at will. If the analogue module behaved in the same way, that would be awesome, though if I had to choose a screen format for the analogue module to force full screen 16:9, that would also work. |
16:9 mode for the analog module would be awesome. I do fly a lot of analog whoops still, one reason I bought the HDZero Goggles. Many of my whoops do have 16:9 which gets squished in the goggles unfortunately. So I'd be really happy for this mode. |
I have gotten used to flying all my analog whoops on 16:9 (Skyzone 02s). Even the 4:3 cameras, when stretched to 16:9 look great. Its much easier to get used to than the other way around (4:3 stretched to 16:9). So I would be very grateful for this fix. |
I know there is a lot of work going on with the analogue interface at the moment and this is just one issue amongst many that probably have higher priority. Does anyone know if these wishlist (but still important for those of us who want them) items are also being included in these works? Thank you in advance. |
How it's going? |
I would like this as well. |
I'd really like to have 16:9 for the analog input. This could make them my main goggles. A lot of people fly 16:9 on analogue. |
I would also love to have 16:9 output as an option with the Analog output. |
I also primarily use 16:9 cameras on analog even on whoops. Telling people to switch to a different VTX is not a fix. There are lots of reasons to use analog even outside of whoops still and lots of people got the HDZ goggles because they also are supposed to include full analog support. I still feel like to date they still have a fairly limited implementation for analog however. |
Option to switch between 4:3 and 16:9 Analog. |
This is what it would possibly look like if you had the option of 16:9 wide but a 4:3 feed. example.mp4I feel the 16:9 is needed as some analog cameras are 16:9 and they get compressed to 4:3 If you want to convert your current HDZero footage from 4:3 to 16:9 for now you can;
|
Ok, this is ridiculous that we don't have it yet. |
My old analog camera (foxeer T Rex) has sensor 16:9 and gives really nice image. It would be great to have the feature |
Just purchased HDZero goggles for the ability to do both HD and Analog, and with 16/9 signal having it squeezed to 4/3 is awful, it gives horrible motion sickness when doing barrel rolls. |
How do we get this fix implemented? I wouldn't even consider analog supported with out the ability to support the higher end analog cameras. Is this something we should bug Divimath about? Do we just get enough people to comment here? Discord? |
I'm also surprised this still hasn't been implemented after all this time.
Or there to have at least been an explanation of not currently possible to
do/hard to do because of XYZ.
…On Wed, 6 Nov 2024, 6:58 am thespova, ***@***.***> wrote:
How do we get this fix implemented? I wouldn't even consider analog
supported with out the ability to support the higher end analog cameras.
Is this something we should bug Divimath about? Do we just get enough
people to comment here? Discord?
—
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ66KIF5JDXSW7J2RUXRZDZ7EWQ3AVCNFSM6AAAAABJ563ROSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGEZTQOJWGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I agree. Let’s see this happen
Sent from Yahoo Mail for iPhone
On Tuesday, November 5, 2024, 2:08 PM, Peter Feerick ***@***.***> wrote:
I'm also surprised this still hasn't been implemented after all this time.<br>Or there to have at least been an explanation of not currently possible to<br>do/hard to do because of XYZ.<br><br>On Wed, 6 Nov 2024, 6:58 am thespova, ***@***.***> wrote:<br><br>> How do we get this fix implemented? I wouldn't even consider analog<br>> supported with out the ability to support the higher end analog cameras.<br>><br>> Is this something we should bug Divimath about? Do we just get enough<br>> people to comment here? Discord?<br>><br>> —<br>> Reply to this email directly, view it on GitHub<br>> <#145 (comment)>,<br>> or unsubscribe<br>> <https://github.com/notifications/unsubscribe-auth/ABJ66KIF5JDXSW7J2RUXRZDZ7EWQ3AVCNFSM6AAAAABJ563ROSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGEZTQOJWGE><br>> .<br>> You are receiving this because you are subscribed to this thread.Message<br>> ID: ***@***.***><br>><br>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
At least add this to your 10.0 to-do list. |
+1 to this feature request from me.. Was really surprised in a bad way that this is not supported. |
With all the interest and comments this seems to get it would be nice to get some comment from devs about the possibility of this happening. I know everyone was saying analog is dead there for a bit but that's clearly not true. Analog still has a lot of use and interest. HDZ are supposed to be "the best you can do with analog" but not having common screen ratio that many of the best analog cameras are offered with is an issue. |
PR #472 now stretches analog to 16:9, but seemingly without option for 4:3 :( binary here: https://github.com/hd-zero/hdzero-goggle/actions/runs/12760401014 |
Was that specifically supposed to add an option or change the aspect ratio of analog? It doesn't look like either was intended as far as I can tell. |
same conclusion here. i don't how it's happening, only that it is. |
I gave this a few test flights with my whoops and didnt notice any issues. Can confirm its full screen with the aircraft I tested and all of these where set to wide screen on the cam side (or just have not adjustable wide screen cams). Maybe they are just changing to wide screen being default for analog? IDK how many cams are sold default wide vs 4:3 but maybe this makes more sense as a default? Personally, id be ok with just having 2 versions of each official firmware release. One for people that want wide screen analog and one for people that want 4:3. I imagine there are far fewer people that use both mode across different aircraft as most probably always go one way or the other. |
i just did some testing, i used the right-button input = toggle-source, and once i go from Analog to HD then back to Analog, the screen is 4:3 again. so i'm a little confused at the result/function. i have not tested how to achieve 16:9 again. 😆 🤕 as far as two firmwares, i think such would be messy in the dev-ops arena. one firmware makes more sense. |
Ok, so at least even if it’s bugged or stuck in 16:9, the hypothesis that
it’s impossible for hardware reasons can be dismissed now. That’s good!
Le lun. 20 janv. 2025 à 19:45, nerdCopter ***@***.***> a
écrit :
… i just did some testing, i used the right-button input = toggle-source,
and once i go from Analog to HD then back to Analog, the screen is 4:3
again. so i'm a little confused at the result/function.
i have not tested how to achieve 16:9 again. 😆 🤕
as far as two firmwares, i think such would be messy in the dev-ops arena.
one firmware makes more sense.
—
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACXIPYK7R5KTL66HTNEGHD32LU73DAVCNFSM6AAAAABJ563ROSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBTGA3DEMZSGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I would add 16:9 / 4:3 options |
option was merged: #473 latest |
I’ll give it a whirl first chance Cold weather has changed my lifestyle somewhat 😟
Sent from Yahoo Mail for iPhone
On Wednesday, January 22, 2025, 8:42 AM, nerdCopter ***@***.***> wrote:
option was merged: #473
latest main build(s) found here: https://github.com/hd-zero/hdzero-goggle/actions?query=branch%3Amain+event%3Apush
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
I tried to install the artifact from here: https://github.com/hd-zero/hdzero-goggle/actions/runs/12948041847, but I don't know if it was a coincidence or it has an issue, but after repower, my goggles won't boot. I made a recovery SD and, after a few attempts, was able to restore the system to try to install the 16:9 new feature once again, but this time from the latest artifact that I took here: Just curious if it's possible and if it makes sense to auto-adjust the aspect ratio for analog and add a 4:3/16:9/auto option. |
i've had similar before, ; i was told simply to put one of the |
Yep. All those beeps say nothing and a part where .bin files should be automatically removed on success is also not true. But I was able to install everything in an hour or so. It's not ideal, but it is also a part of the hobby. |
The tinywhoop cameras does not have settings to change it there, and the glasses do not have such an opportunity, so not the whole screen is used
The text was updated successfully, but these errors were encountered: