It looks like at line 959 the quote and the parenthesis needs to be closed

In finsta360.py its a line called:

print('finsta360.py : to finalize incomplete MP4 of Insta360 ONE-X

To make the script work I had to add ') after X to make it consistent like this:

print('finsta360.py : to finalize incomplete MP4 of Insta360 ONE-X')
print('https://github.com/kichiki/finsta360')
print('USAGE: finsta360.py [options]')

Got the script to run but running into the following issue:
`mcwiggin@Kubuntu50:~/Downloads/finsta360-master$ sudo ./finsta360.py -s ../VID_20200513_174448_00_004.insv -r ../ref.insv -o ../out.insv
[sudo] password for mcwiggin:

########################################

1) extracting reference moov from

    ../ref.insv

########################################

2) regenerate sample tables from mdat in

    ../VID_20200513_174448_00_004.insv

Traceback (most recent call last):
File "./finsta360.py", line 1015, in
finsta360(
File "./finsta360.py", line 891, in finsta360
mov_table, aac_table = recover_sample_tables_from_mdat_fast(
File "./finsta360.py", line 463, in recover_sample_tables_from_mdat_fast
frame_length = struct.unpack('>I', buf)[0] + 4
struct.error: unpack requires a buffer of 4 bytes
`

Hey great work on this software.
I'm trying to recover a 3.6Gb pair of files and the non-corrupt video I'm using is only 9s long. The output is still 3.6Gb but is also only 9 seconds long (but there is about 10 minutes of footage) is this a bug?

Hi there,
I tried to repair a corrupted Insta350 ONE R file. I thought it should be possible to repair it with your tool. The following error was thrown:
# 3) rebuilding moov from the sample tables Traceback (most recent call last): File "D:/anypath/FixInsta360/finsta360.py", line 680, in recover_moov_from_sample_tables copy_atom_box('uuid', None, f_moov, f_dst, only_header=False) File "D:/anypath/FixInsta360/finsta360.py", line 494, in copy_atom_box if atom_type != target_type: raise ValueError(f'{target_type} not found but {atom_type}') ValueError: uuid not found but trak
Do you have any idee how to fix it or what the problem is? It could be possible that the tool is not compatible with the H.265 codec from the ONE R.

Hi! I have corrupted insta 360videofiles, unfortanly I don't know who to use your code. I have never used pyton and don't know if I should launch a file or open the terminal. So please add a step by step example where you show the steps from scratch with some screenshots, or by a detailed script.
That would be really helpful.
Thanks

The duration could exceed 4 bytes, and causing error during struct.pack in file write. Maybe use ">Q" or try to limit the duration size?

Originally I reported that I was unable to stich the files. However, the reasons for my issue was that I was not consistent using different reference files for the different files. If the file has the 00 in it, then you have to use a reference file like 00_033.insv If it instead has the 10 in it, you have to use a reference file like 10_033.insv to make both files combine in the software.

F:\Videos\TEMP>python finsta360.py -s .\VID_090732_00_006.insv -r .\VID_Referenz_00_009.insv -o .\output.insv

########################################

1) extracting reference moov from

    .\VID_Referenz_00_009.insv

########################################

2) regenerate sample tables from mdat in

    .\VID_090732_00_006.insv

########################################

3) rebuilding moov from the sample tables

Traceback (most recent call last):
File "F:\Videos\TEMP\finsta360.py", line 1015, in
finsta360(
File "F:\Videos\TEMP\finsta360.py", line 926, in finsta360
recover_moov_from_sample_tables(
File "F:\Videos\TEMP\finsta360.py", line 680, in recover_moov_from_sample_tables
copy_atom_box('uuid', None, f_moov, f_dst, only_header=False)
File "F:\Videos\TEMP\finsta360.py", line 494, in copy_atom_box
if atom_type != target_type: raise ValueError(f'{target_type} not found but {atom_type}')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: uuid not found but trak