If you have a problem or need to report a bug please email : support@dsprobotics.com
There are 3 sections to this support area:
DOWNLOADS: access to product manuals, support files and drivers
HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects
USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here
NEW REGISTRATIONS - please contact us if you wish to register on the forum
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
USBLib Ruby - Using Libs with flowstone
2 posts
• Page 1 of 1
USBLib Ruby - Using Libs with flowstone
Hello!
I have an DMX Interface here that is NOT FTDI ^^ - It has also No MIDI or any HID - It just has a "Standart" USB-Driver
delivered by the vendor.
It i install a standart usbdriver by zadig -> Same result
So no i was asking me if i could read out ALL USB Data - and i found this one here:
https://github.com/larskanis/libusb
Would that be possible?
Regards
I have an DMX Interface here that is NOT FTDI ^^ - It has also No MIDI or any HID - It just has a "Standart" USB-Driver
delivered by the vendor.
It i install a standart usbdriver by zadig -> Same result
So no i was asking me if i could read out ALL USB Data - and i found this one here:
https://github.com/larskanis/libusb
Would that be possible?
Regards
100% accuracy is the guarantee to your success. The value alters if you combine it with musical creativity.
-
chackl - Posts: 233
- Joined: Tue Aug 17, 2010 8:46 pm
- Location: Austria / Salzburg
Re: USBLib Ruby - Using Libs with flowstone
I guess not, because you could not trigger the ruby module, at the same data rate of USB.
you must have loop-callback from external interaction.
you can not do, as it has been implemented in ruby FS, it runs only when required by a trigger,
it will occupy the thread and when executed will release the thread.
if you try to occupy the thread out of the set limit, it will turn off the ruby module by putting it in the OFF position.
I repeat, until there will be the opportunity to be able to read external dll
you can not implement anything that is not already implemented.
you must have loop-callback from external interaction.
you can not do, as it has been implemented in ruby FS, it runs only when required by a trigger,
it will occupy the thread and when executed will release the thread.
if you try to occupy the thread out of the set limit, it will turn off the ruby module by putting it in the OFF position.
I repeat, until there will be the opportunity to be able to read external dll
you can not implement anything that is not already implemented.
- Tronic
- Posts: 539
- Joined: Wed Dec 21, 2011 12:59 pm
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 97 guests