-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Illegal instruction error from example code. #39
Comments
@Lorune I upgraded recently the entire project to recent dependencies. You can try with the v2: https://github.com/TypedProject/ts-gphoto2-driver/tree/v2.4.3 It's a stable released. I'm sorry about the errors related to the v3. I'll try to fix this version ASAP! |
Version 2.4.3 works fine. Thanks a lot for the swift reply, onwards to integrate it further :) |
Ok, so capturing a image with the following code works :
However the example that contains :
It still produces :
It is now running the 2.4.3 version. |
Erf… i haven’t idea… |
I'll try to fix the project ASAP. |
Would be much appreciated, otherwise i have to resort to a native c++ implementation. None of the available library wrappers seem to deal very well with 2 camera's. If you need more info or help with testing just give me a message or ping me here. |
2 camera's connected ? ts-gphotodriver2 is inspired from node-gphoto2 so It's probably the same issue. |
And I haven't two camera XD |
If there is anything i can do to debug this myself i don't mind helping out, but i have never worked on node modules myself that use c++ libraries, only ever interacted with those directly. And yes it also has issues with it. |
@Lorune Sure. The library use NAPI to wrap native C++ module with nodejs. For the cameraList, you have class that call the native wrapped method: GPhoto2Driver.gp_camera_autodetect(this.pointer, Context.get().pointer); This function is wrapped here: This line for example, configure the gp_camera_autodetect signature:
The first index
How I have determined this types ^^' ? By reading the official API documentation here: int gp_camera_autodetect ( CameraList * list, GPContext * context) The error is in the load method which calls different native method. You can edit the CameraList in the node_modules and add logs to determine where come from the problems :) Tell me if you have any question. Also, you can join us on the Slack here: https://api.tsed.io/rest/slack/tsedio/tsed See you |
I will be busy today with some other stuff but i will see if i can dedicate some time to it in the next few days. |
Sure ;) |
@Lorune I fixed the v3 version. But the napi-ref isn't fully compatible with Node.js v14 I'll try to understand the reason! See you |
Not sure what error you are facing but both v2.4.3 and v3.0.3 are crashing on node v14.x. I found the following item related to my problem: |
Yes the code crash with v14, but not with v12 when the scripts try to get camera list. And yes the error is the same. |
Indeed it works on v12, I can confirm. The linked issue contains a reference for a more robust implementation of ref-napi... currently I have no time for that but later I will try to wire them into the driver and see wheter it will resolve our problem or not. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I am trying to use this library to operate one of our Sony Alpha-A7R III, i tried to use node-gphoto2 before, but ran into some issues with the capturing of multiple images after each other.
So i was trying out this library, however i am not even getting the simplest of examples running without getting Node.JS to throw me illegal instructions errors. I am running v14.16.1 of Node.JS at the moment.
I hope you have any points as to which direction i should take this. If you need more information please let me know and ill provide it.
My current code (one of your examples)
I have the package installed along with gphoto2 and the gphoto lib version
Brew package installed info
The text was updated successfully, but these errors were encountered: