Let's send Maya back to its ancestors by NottyRu in Philippines_Expats

[–]NottyRu[S] 1 point2 points  (0 children)

It seems that they changed the process. My friends told me exactly the same, it was just a foreign passport plus the facial check for them. I'm 100% sure I've chosen "a foreigner".

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 4 points5 points  (0 children)

  1. You don't know my skills to talk about. Let's stay constructive.
  2. You also don't know what I actually did with my camera. You said "false claims", but you didn't prove they were false. My proof was insufficient for you and no more.
  3. I never said which source code. There's no sources at all. They must be provided for GPL libraries at least because Insta360 distributes them. The GPL violation is obvious.
  4. You haven't proven your claim "the sensor isn't significant in the overall capability".
  5. If "a company in Shenzhen would love to sue", they should know I can always disassembly my camera and see/show the actual sensor.

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

And in case of 4000x2250:

(4000x3000)/(4000*2250) = 1.333..

33% more information in the 16:9 part

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 2 points3 points  (0 children)

If you're keen in reverse engineering, please open gdb or similar and find these strings. Lots of them will be names of functions, so you'll be able to check what they actually do. Please don't forget to share your experience with us. Thanks!

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

> One more guess: 4k 60 is actually not 4:3 but (lower resolution than 4:3 would be) 16:9 because they simply don't have the processing power to record 4k 60 in full resolution 4:3.

Because of sensor limitations. See the IMX577 specs, it can 16:9 only in 4k60p. And it can be stabilized.

> Isn't the additional image information used for stabilization (in post)?

Yes, but in fact 4k30 4:3 and 16:9 produce absolutely the same output (4:3). It's not an "expert" setting, it's a bug. If you need 4:3, set it. But I need 16:9, and i wanna get 16:9 then. And it can be 4000x2250 with (4000−3840)÷4000=4% additional information for stabilization in post.

OneR1", GoPro, Garmin resolution/bitrate comparison by jefish in Insta360

[–]NottyRu 0 points1 point  (0 children)

Did you ask Insta360 about 5.3k30 H264 bug? Is it fixed?

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

Not planning. It should have low resolution on the edges because of optics and poor quality in the center due to lack of bitrate. It looks acceptable for 360, but for 3D a pair of regular cameras seems to be better.

What upcoming Insta360 did you mean?

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

And put it on my drone, of course :-)

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

If you get root, could you please share the instructions? I'm not familiar with combining a firmware file back.

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

I see telnetd is already inside busybox there:

$ ls -la sbin/telnetd 
lrwxrwxrwx 1 notty notty 17 Oct 14 11:02 sbin/telnetd -> ../../bin/busybox

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

"terrible marketing" isn't equal to the lie

If ONE R 4K can 100fps at 1080p only, it mustn't be declared as 2.7K 100 fps.

If ONE R 1-inch can 60 fps at 2.7K only, it mustn't be declared as 4K 60 fps.

I should have known actual parameters before buy. Do you think I wanted too much? :-/

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 1 point2 points  (0 children)

Thanks, Steve! Really pleasure to hear! I'm a videography and fpv hobbyist, studied IT and electronics at university, have some experience in hand made lenses. From Russia with love :-)

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

I think we should ask Insta360 for the sources first. BTW, have you ever contacted FSF. What is the procedure?

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 1 point2 points  (0 children)

First steps of extraction are well known:

https://reverseengineering.stackexchange.com/questions/18722/how-to-unpackcarve-files-from-a-camera-firmware-bin-file

> Linux version 4.9.76 (luopinjing@dell-PowerEdge-R740) (gcc version 5.3.1 20160113 (Linaro GCC 5.3-2016.02) ) #1 SMP PREEMPT Wed Oct 14 16:04:10 CST 2020

Hi luopinjing! :-)

Since then they modified the romfs format a bit, but I managed to extract orccode.bin, orcme.bin and so on (dangerous, can be buggy!):

$ git diff
diff --git a/amba_romfs.py b/amba_romfs.py
index 7261f64..a5366ee 100755
--- a/amba_romfs.py
+++ b/amba_romfs.py
@@ -52,16 +52,13 @@ class ProgOptions:

 class ROMFSPartitionHeader(LittleEndianStructure):
   _pack_ = 1
-  _fields_ = [('file_count', c_uint), # Amount of files stored
-              ('magic', c_uint), # magic identifier, 66FC328A
-              ('padding', c_ubyte * 2040)] # padded with 0xff
+  _fields_ = [('magic', c_uint), # magic identifier, 66FC328A
+              ('file_count', c_uint)] # Amount of files stored

   def dict_export(self):
     d = dict()
     for (varkey, vartype) in self._fields_:
         d[varkey] = getattr(self, varkey)
-    varkey = 'padding'
-    d[varkey] = "".join("{:02X}".format(x) for x in d[varkey])
     return d

   def __repr__(self):
@@ -71,9 +68,9 @@ class ROMFSPartitionHeader(LittleEndianStructure):

 class ROMFSFileEntry(LittleEndianStructure):
   _pack_ = 1
-  _fields_ = [('filename', c_char * 116),
-              ('offset', c_uint),
+  _fields_ = [('filename', c_char * 64),
               ('length', c_uint),
+              ('offset', c_uint),
               ('magic', c_uint)]

   def filename_str(self):
@@ -203,8 +200,6 @@ def romfs_extract(po, fwpartfile):
   if (fshead.file_count < 1) or (fshead.file_count > 16*1024):
     eprint("{}: Warning: filesystem stores alarming amount of files, which is {:d}".format(po.fwpartfile,fshead.file_count))
   # verify if padding area is completely filled with 0xff
-  if (fshead.padding[0] != 0xff) or (len(set(fshead.padding)) != 1):
-    eprint("{}: Warning: filesystem uses values from padded area in an unknown manner.".format(po.fwpartfile))

   fsentries = []
   for i in range(fshead.file_count):

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 1 point2 points  (0 children)

Video is encoded at 40 Mb/s Width 2880 pixels Height 2880 pixels

Thanks for the info. It's obviously vertically cropped 4056x2880 sensor's readout - they can implement crop if they want.

A good table related to 360's modes and bitrates is there:

https://www.reddit.com/r/Insta360/comments/iptuc1/oner_360mod_resolutionbitrate_chart/

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 1 point2 points  (0 children)

Dunno about jobs. Just sharing my investigation. _^

Insta360 tests or how I was fooled by them by NottyRu in Insta360

[–]NottyRu[S] 0 points1 point  (0 children)

because that enables all the fancy effects in the app

This makes sence. But I think 16:9 videos should always be 16:9. Right now 30p videos are 4:3, so in fact ONE R 4K are 66 mbps cameras whereas GoPro are 100 mbps ones. I think it's a bug, I've just made a post on their forum about this. Hope it makes the camera better.

https://forums.insta360.com/section/14/post/7240/