-
Notifications
You must be signed in to change notification settings - Fork 33
Openni2 does not handle oni files #26
Comments
I'm guessing it is due to this commit: ros-drivers/openni2_camera@17c1072 -- in the past it would have probably fallen through and returned the string name, now it returns the empty string -- you could try adding an extra case before the matching attempt which checks if the file ends with .oni and if so, returns the device_id as-is. If that works, we can gladly accept a PR to fix this regression. |
It worked! Thanks.
|
Same issue here, does anyone has a fixed fork? |
If you add the above two lines to line 682, it fixes the problem. |
@rastaxe problem solved, thanks a lot 👍 |
Moved to the |
I am not able to load a oni file (OpenNI record file) with openni2 in Indigo. In Hydro I was able to load it simply with: roslaunch openni2_launch openni2.launch device_id:=/path/to/your/file.oni
but in Indigo openni2 still tries to open the real device. Do you have the same problem?
The text was updated successfully, but these errors were encountered: