v0.56a: OpenCV Error: Bad argument (Input array is not a valid matrix) in cvPointSeqFromMat, file c:\builds\2_4_PackSlave-win32-vc12-shared\opencv\modules\imgproc\src\utils.cpp, line 54 #8
Comments
|
v0.56b : This time updating software did work automatically. But still the same issue of win_cursor_plus_fallback.exe crashing with 4 instances of win_cursor_plus.exe launched by deamon_plus.exe. This version is worse because i even can't get the two little windows named "image_foreground0" and "image_foreground1" and don't get to keyboard step. |
|
Getting on it. On Thu, Jul 30, 2015 at 7:29 PM, touchhope notifications@github.com
|
|
Thank you ! |
|
I'm getting 4 instances of menu_plus.exe |
|
The menu is running in Node WebKit, the runtime automatically creates 4 instances. Please check back in 24 hours, I've done a lot of work lately that lead the current commit to become a lot less reliable. Working to get it smoothed out. On Thu, Jul 30, 2015 at 7:55 PM, bogdi1988 notifications@github.com
|
|
Thank you! Looking forward to compiling and testing out the next build (now that VS is set up right and compiles all code ok) |
|
v56c: See http://gharbi.me/ractiv/ I'm a buyer from China,here is a link of touch+ software http://pan.baidu.com/s/1pJ0zNfl Then when deamon_plus.exe is running, right click one the little icon on you task bar and choose "Update software" to migrate to version 0.56c. In this current version 0.56c again for me it seems worse than v0.56a. In v0.56c, i get to keyboard step but when i push 8 key, it does nothing (oops ! qwerty and azerty automatic detection added ?), no when i switch to azerty again, it detects my 8 key but block on = key ! I don't obtain the two little windows and before keyboard step, i have had a lot of win_cursor_fallback.exe crash again and have had often to replug device ! After pushing 8 key, in the console i have "message sent: menu_plus show calibration next step 0 complete" and then 5 to 5 numbers and nothing (blocked on = key, no matter if azerty or qwerty). When showing in console "pose estmator initialized, message sent: win_cursor_plus open udp channel", and also first with "menu_plus created, message_received get toggles deamon_plus1, message sent: menu_plus get toggles 1011005" to go on out of the blocking you have to replug device ! Then you go to taskmgr, to kill some of the 4 instances of win_cursor_plus.exe in memory, just to get the control panel to come again. The console runs again and says menu_plus created but nothing appear ! @lai Schwe: |
|
Hi,
It seems like many folks are trying to run the software in Windows 7. The
cursor code for Windows 7 and 8&above are different because 7 does not
natively support touchscreens and touch-injection. I haven't updated the
Win7 cursor for a while already, and as a result it is extremely bugged up.
I'm downloading Win7 at the moment, and will start working on it once I
have the OS installed in a virtual machine.
Thanks
|
|
Will give you a heads up once I've gotten it smoothed out. On Fri, Jul 31, 2015 at 4:45 PM, Lai Xue sheley1998@gmail.com wrote:
|
|
Thanks. |
|
Is it important to install and run as administrator or not, because we see a little icon on the program icon which suggest administrator privileges needed, no ? |
|
current v[e]sion v0.57a (Do you mean current ve[r]sion in the bubble ?) |
|
In order to lauch a new initialization after updating software, you sometimes need to delete userdata folder and ipc too i'm not sure ? |
|
And sometimes, you go and search in the first patch.zip the database folder because it seems it's more recent and fonctional ? |
|
lol ! :) super excited ! |
|
Could you tell me what's the problem with these two dll files msvcr110.dll and msvcp110.dll that touch+ software doesn't find to run under win 10 x32 ? |
|
When you and Darren will be billionaires with touch+ device, would you invite us all to eat at La Tour d'Argent or Chez Maxime if you prefer in Paris to celebrate that ? |
|
lol ! :) |
|
@alexandru |
|
@touchhope - i used this on Windows 10 64bit. I did NOT have to put those DLLs in the system. I just installed the app and it just worked. |
|
@alexandru & @lai Schwe |
|
After a bad night, dreaming of a working touch+, new try this morning with the idea of taking care of caps lock enabling : keyboard step ok but make sure you wait until 95 for each key in the console. I get the 2 little windows but still no pointing circle but again a big crash with error message from vs debugger "An unhandled win32 exception occurred in track_plus.exe". |
|
I don't know why on one of my 2 pc (the ex win 8.1 x64) under win 10 x64 when i click on "Update software" it does nothing but on the other, which was previously under win 7 x64, where i have had to install vs_isoshell.exe to get the 2 dll, asking for update still work. |
|
Yeah I've started experiencing issues myself after updating my laptop. Still installing latest visual studio, will start debugging in a bit. On Sat, Aug 1, 2015 at 12:52 PM, touchhope notifications@github.com
|
|
Got now the 2 little windows running and no crash for now (few minutes) but after deleting userdata folder and ipc for new initialization, but still no pointing circle ! |
|
Deamon_plus.exe console says "step 3 complete, message sent: menu_plus show stage, calibration finished". Still no crash : a kind of stability ! lol :) |
|
Gimme half a day to get things sorted. BTW what model is your laptop? On Sat, Aug 1, 2015 at 1:00 PM, touchhope notifications@github.com
|
|
ACER ASPIRE R7 WITH EZEL HINGE |
|
Thank you and good afternoon, is that right ? Here, it's the morning in France. |
|
Well restarting after clicking on "Exit", then again blocked after "pose estimator initialized, message sent: win_cursor_plus open udp channel" and this time replug don't make anything on a eventually loss of device detection. |
|
In fact device detection was completely broken and i had to click on Exit, then replug and hearing windows sound that tell it detects something on usb. |
|
How long should we wiggle normally ? Because the two next step of gestures after are so fast that we don't have time to move properly i think. |
|
Normally, around 2 seconds. Here try the latest build from this link https://www.dropbox.com/sh/41v0qwqysth6dfl/AABNSRVG6rEdHrvDUgd7z6wga?dl=0 On Sat, Aug 1, 2015 at 1:36 PM, touchhope notifications@github.com
|
|
Try terminating all running executables from the old build if you run into any issues On Sat, Aug 1, 2015 at 1:36 PM, touchhope notifications@github.com
|
|
Thank you for that new build. |
|
Alight just needed to verify that the proble exists across different builds. Thanks for reporting these issues, I'm getting on it. On Sat, Aug 1, 2015 at 2:13 PM, touchhope notifications@github.com
|
|
Tried this build you just posted on dropbox. |
|
I take it back. I deleted all the folders, re-copied the ones from the new build. Started the app again, let it download the calibration data and I was able to pass the wiggle part. Took about 30 seconds on the wiggle part until it finally kicked the camera process. Finger pointer movement is choppy and still only works in a really tiny area. Screenshot attached. |
|
OK! Got the pointer stabilized! Seems like the cameras are really sensitive to distance and that I need at least 6 inches from camera to keyboard. Also, took the track_plus.exe app and disabled scaling on high DPI settings. I now have pointer going on the entire screen! |
|
Yeah clicks have been disabled during debug. I'll try to borrow a high DPI display so that I can see what the problem is on 4K displays. Can you open up a new issue on GitHub regarding this issue? Thanks so much! On Sat, Aug 1, 2015 at 2:51 PM, bogdi1988 notifications@github.com
|
|
@touchhope try to move the camera back a bit and the app will pass the wiggle screen easier. also, disable the high DPI support! |
|
@sheley1998 issue opened. Please take a look at it. I found another issue with the pointer not being the highest 'layer' in the display. Separate issue opened for it. |
|
Yes the debug pointer executable hasn't been code-signed. Pointer can only be displayed above all UI elements after the executable is signed with a special permit purchased from Microsoft. I'll post a download link for the code signed pointer here in a bit. On Sat, Aug 1, 2015 at 3:05 PM, bogdi1988 notifications@github.com
|
|
Hmm... weird. I have had it sometimes over the UI elements. Let me try and get a screenshot. |
|
I think it works sometimes over regular UI elements. The code-signed executable always works, and even stays above microsofts full screen Modern apps in Win8 On Sat, Aug 1, 2015 at 3:48 PM, bogdi1988 notifications@github.com
|
|
Gotcha. Ok :) Looking forward for next item to test. |
|
Microsoft created a level of permission called UIAccess for WPF applications. This permission is only granted to "safe apps", which basically means we've had to pay them. On Sat, Aug 1, 2015 at 3:48 PM, bogdi1988 notifications@github.com
|
|
Have you posted a link to the code-signed executable yet? |
Hello Lai Schwe,
The hungry of hope frog has catch a bug for you on v0.56a : "OpenCV Error: Bad argument (Input array is not a valid matrix) in cvPointSeqFromMat, file c:\builds\2_4_PackSlave-win32-vc12-shared\opencv\modules\imgproc\src\utils.cpp, line 54".
See http://gharbi.me/ractiv/ for details on error context.
Thank you for publishing your code and congratulations for hard work.
If Darren is Ractiv's webmaster, please tell him to take the time to publish a little update on the blog.
For windows installer, it's unlogical that it refuse to install under win 7 x64.
Please clearly define dependancies for msvcr110.dll and msvcp110.dll on win 10 x32.
To fix : loss of device detection just before keyboard step that get you to replug to go on.
4 instances of win_cursor_plus.exe launched by deamon_plus.exe that make win_cursor_plus_fallback.exe crashing.
To fix : updater that download patch but fail to install update
To add : a new menu on deamon to allow user to ask for a new initialization (instead of manually deleting folders).
Glad to see this marvellous project is still active (for Ractiv it's normal, no ?)
Best regards,
The frog (known as touchhope on Wassim's website)
The text was updated successfully, but these errors were encountered: