-
Notifications
You must be signed in to change notification settings - Fork 0
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
RangeError : Invalid typed array length #1
Comments
I'm sorry but I don't have GoPro 4 anymore. Only GoPro 3 Black here and it didn't support HiLight tag. Thank you. |
I can send you a link to one but its 3.5GB is that ok? I could try different lengths to find a smaller file with the problem if it is too big. Really nice of you to try and help by the way! I am a programmer but you'll find the issue must faster than I since it is your libraries :) |
That file ok for me. I start download it but I'm not sure when I will have time to check it out. |
No worries thanks again! Let me know if I can help in any way. |
@Alex-TRS Sorry for this late response. As you can see I open issue in codem-isoboxer. The thing was this has a big problem than I think. I will try to figure out what I can do with it. But this should take a long time with my time. |
No problem I have an alternative workflow for the time being. Its nice of you to try and fix it! Would be extremely time saving once the script works. Will keep following this issue. Thanks again |
WIth a long GoPro video (3.5gb) the script fails on any of the parts with the following error :
buffer.js:11
super(arg1, arg2, arg3);
^
RangeError: Invalid typed array length
at Buffer.Uint8Array (native)
at FastBuffer (buffer.js:11:5)
at createUnsafeBuffer (buffer.js:38:12)
at allocate (buffer.js:181:12)
at Function.Buffer.allocUnsafe (buffer.js:141:10)
at tryCreateBuffer (fs.js:474:21)
at Object.fs.readFileSync (fs.js:519:14)
at C:\Program Files\nodejs\node_modules\npm\node_modules\gopro-tagging\gopro-tagging.js:5:74
at FSReqWrap.oncomplete (fs.js:123:15)
The text was updated successfully, but these errors were encountered: