Develop Bugs

FOV2GO: $5 motion tracked 3D HMD

Hi, has anybody tried this awesome 3d viewer on a Galaxy Note?
Looks like an amazing DIY 3D viewer on the cheap and its a project by Palmer Luckey (Oculus Rift anyone? :cyclops
EDIT: Sorry, my user can't post links yet (not enough posting ), you just look for fov2go on youtube,
Best, Pablo

relevance
lovly..

Pretty cool.
Just need proper APIs to enter the AOSP/Git/SDK.
Maybe watch Stereoscopic 3D movies (a la Avatar) in 3D on the NOTE itself. However the resolution would be reduced to (per eye) 620 x [email protected]
Honestly the resolution isn't a problem. The problem is pixel density.
You need to squeeze all those pixels closer and closer together, so that the eye doesn't see the little "black pixel" (the gap between one pixel to the other). I think a display with 260ppi or more should be sufficient to prevent this effect.
Obviously, because PenTile has pixels "sharing" some sub-pixels, the "black pixel" issue is reduced, but it creates a different problem, and that is "jaggedness". And the "jagedness" or blur undoes the effects, making it much worse than a standard square subpixel structure.
-The innovation is possible on the iPhone 4/4S but it is a lackluster experience of (per eye) 455 x [email protected]
-Or maybe this year with the iPhone 6, 3.99inches with 1152 x 640 resolution. The effect would be (per eye) 555 x [email protected] Still nothing to write home.
-The best example (available today) is from fov2go on the iPad3. Achieving (per eye) 750 x [email protected], as demonstrated by them on YouTube.
Additionally, the most relevant 3D you'd find for comparison are Passive types. Now the ppi doesn't really matter here because that can be controlled by the user (sit closer/further from TV, get larger/smaller 3DTV). However, 3D content is delivered as 1080p and divided into two. Each eye gets to see 1920 x 540. If you convert that to a 16:9 aspect, then per eye, sees 960 x 540 resolution. Not too shabby.
This innovation however is viable with a setup like this:
+RGB, 5.5inch, 334ppi, 1600 x 900 = 780 x 439 (per eye).
+RGB, 5.5inch, 340ppi, 1640 x 900 = 800 x 450 (per eye).
+RGB, 7inch, 287ppi, 1750 x 980 = 854 x 480 (per eye).
Or Passive 3D TV's with "Checkered Spatial Sterescopics" with a total 4X (aka QFHD) resolution (3480x2160) for 2D, and would deliver 1920 x 1080 (per eye) in 3D.
Overall, I think with sharper displays (RGB + PPI), higher resolutions, and more 3D content... this is the future. It is like what headphones do (mimic a Big Stereo Sound, miniturize it, localize its delivery, becomes portable)... except like 3DTVs for your eyes. In fact, Steve Jobs joked about this issue before I can't find the YouTube video but its there.

Possible TRUE 4K Recording

I believe it's possible to mod the Note 3 camera.apk or use Focal to record at 4096x2160 which is 4k, what they advertise is Quad HD but they say it's 4k but It's not the case.

tichs said:
I believe it's possible to mod the Note 3 camera.apk or use Focal to record at 4096x2160 which is 4k, what they advertise is Quad HD but they say it's 4k but It's not the case.
Click to expand...
Click to collapse
Ultra HD 4K is defined as 3840 × 2160, which is what the Note 3 records at. You're referring to Digital Cinema 4K, which is what's shown at movie theaters. 3840 x 2160 is still 4x the pixels of 1080p, which is what 4k means anyway.

Huge size videos in htc 10

It gives about 4mb for 1second record of an hd video
And totaly about 9gb for 1.5 hours
Pls help

Keyvevanab said:
It gives about 4mb for 1second record of an hd video
And totaly about 9gb for 1.5 hours
Pls help
Click to expand...
Click to collapse
I don't understand what you're asking. If the vids are too big just lower the quality. The higher the quality the larger the files, the lower the quality the smaller the files. Just play around with the settings it til you find a happy balance between size & quality.

Use 1080 or even 720p

PunishedSnake said:
Use 1080 or even 720p
Click to expand...
Click to collapse
There is no video quality options in settings i can just set the
Video quality to mms ,qvga,hd,full hd and 4k
And videos are 30fps but when i compare it with
Galaxy S7 the videos are bigger

Keyvevanab said:
There is no video quality options in settings i can just set the
Video quality to mms ,qvga,hd,full hd and 4k
And videos are 30fps but when i compare it with
Galaxy S7 the videos are bigger
Click to expand...
Click to collapse
Full HD = 1080
HD = 720

PunishedSnake said:
Full HD = 1080
HD = 720
Click to expand...
Click to collapse
I know that but 1080 in my phone gets more space than 1080 in S7
Any suggestions?

If the S7 is using less space for the same resolution that it's compressing the video more. Most would view this as a good thing (the HTC 10 higher quality that is).
How strapped for cash are you? Maybe invest in a larger MicroSD card if space is a major concern?

Video recording problem

1080p 60FPS why not 12mp?

1920 × 1920 = ~3.7 million, hence the 3.7 megapixel
Sent from my Pixel XL

Video recording 1080p 60fps not really working

Today I was trying Redmi Note 8 Pro (Global Edition) in the electronic shop, and since I'm planning to shot a lot of video with the device so I tried recording video at different resolutions and frame rates to look at the file size. Following is what I found out:
1. 4K 30fps h.264: 380MB / Minute
2. 4K 30fps h.265: 290MB / Minute
3. 1080p 60fps h.264: 152MB / Minute
4. 1080p 60fps h.265: 117MB / Minute
5. 1080p 30fps h.264: 153MB / Minute
6. 1080p 30fps h.265: 117MB / Minute
Results 1 & 2 seems fine and within the expected. result 3 came way less than I expected for 60fps video, but the shock was when results 5 & 6 came! how come both are the exact same size even the first is double number of frames! I'm used to the size of 150MB / Minute when record with my older Android phone at 1080p 30fps h.264 so that make results 5 & 6 acceptable. But what is wrong with 3 & 4!? there is something fundamentally wrong here. By the way how come iPhone can record 1080p 60fps and produce only 90MB / Minute, and on the other hand my future phone record same video using the same codec 2.265 for 117 MB /minute!? is Apple able rely more on it's powerful cpu to produce compress the video at real-time. Also I've noticed that 1080p 60fps recorded bt Redmi Note 8 Pro isn't as smooth as iPhone or Galaxy during play back!!!!

Its a budget phone. 60fps is working fine for me.
This phone is far cheaper compared to iPhone

Indeed it must not be compared to iPhone as a complete package, but 60fps still 60fps regardless which device record it. 1080p 60fps from galaxy 10 is as smooth as iPhone but both still far smoother than Redmi Note 8 Pro! I'm really suspicious about how Xiaomi is handling these files, if feel it's more or less 30fps with some tweaks. I'll get my hands on my phone in few days and I'll analyze 1080p 60fps more carefully even if it's required to go frame by frame.

I've just checked the following mobiles for 1080p 60fps and 30fps h.265:
Honor 9X
1080p 60fps H. 265: 160MB
1080p 30fps H. 265: 90MB
Samsung A70
1080p 60fps H. 265: 116MB
1080p 30fps H. 265: 74MB
iPhone XR
1080p 60fps H. 265: 90MB
1080p 30fps H. 265: 60MB
Mi 8
1080p 60fps H. 265: 119MB
1080p 30fps H. 265: 118MB
Mi 9T
1080p 60fps H. 265: 118MB
1080p 30fps H. 265: 102MB
It's clear now that 60fps in Note 8 pro is ok comparing to other phones, but seems the compression isn't working right in 30fps since 30fps and 60fps are the same size. 30fps must be around 80MB not 117MB. Anyone have explanation for this phenomena?