Activity for rensg
-
rensg modified a comment on discussion Open Discussion
yes, absolutely: i turn midi out OFF, when editing patches. by the way : there is a "THIN DATA" setting, which discards most of the pitch bend events. unless one needs them, I suggest turning that on... it saves a lot of messaging that will not end up in the notation anyway. note: using a hub is not a good idea.... I use USB socket directly connected to motherboard..
-
yes, absolutely: i turn midi out OFF, when editing patches. by the way : there is a "THIN DATA" setting, which discards most of the pitch bend events. unless one needs them, I suggest turning that on... it saves a lot of messaging that will not end up in the notation anyway.
-
just to finish up this item : noticing that GR55 device apparently has an issue with MIDI over USB... I bought an extra 5pin-MIDI I/O <=> USB interface Bus 005 Device 004: ID 7104:1400 CME (Central Music Co.) U2MIDI Pro for 26 Euro which seems to work just fine. I can now record midi out and control patches with Floorboard without issues and no cable plugging / unplugging needed. response is quick, smooth. MIDI recording is accurate.
-
tried a bunch of scenario's on same hardware ( 8 core, 16GB, ssd disks, absolute realtime prio, unlim pinned memory ) with midi data sending out turned on: via USB : windows works, linux does not; have to turn off midi sending, only then it works fine. via DIN, into a USB audio interface box: both work normally on windows and linux windows floorboard on wine : works, but initial load of all user patches is very slow compared to windows or linux on hardware. in a midi monitor, I can see that GR55...
-
same source code is not a guarantee for identical behaviour. as soon as I/O is involved, it is definitely not guaranteed to work the same way. multiplatform dev tools like Lazarus might go a long way, but not the whole way. Floorboard example: e.g: on windows, I can still select patch by using the GK controller on the guitar (up/down buttons). Floorboard Windows does not notice. On linux, this will not work. patch selection can only be done through Floorboard linux, while floorboard is active. The...
-
while testing I disabled (shut down) ardour. thats the only midi aware software I have. I do not use Jack or similar, too much complexity. Alsa / Pulse, thats all. Anyway, it sounds like that could be it anyway, I will check and let know thanks for the suggestion.
-
I will check and let know thanks for the suggestion.
-
I found out what the "problem" is ... on the GR55, I changed the USB MIDI setting "switch" to ON. this is necessary if you want to record the midi OUT stream that apparently upsets the GR55 Floorboard software: on Linux things work normally on Windows 10 ( same hardware ) it is NOT the USB stack in linux : If I run a windows 10 virtual on top of same linux, things work as they do on Windows running natively on same hardware. My conclusion is, that something is different in GR55 Floorboard for linux...
-
patches dont sound like they should, as soon as floorboard finishes loading. both 2021 and 2022 version have this issue. tried on different laptops / my PC (diff versions of linux , but reasonably up to date code ) all same result. ==> on windows 10, same laptop, it works with no issues.... ==> on a windows inside KVM virtualization on linux, .... it works with no issues.. strange, because the virtual machine uses USB from the linux host.... It seems to be an issue like not being able to communicate...
-
Hi I found the helpfile(s) on github thx Rens
-
Hi I found the helpfile(s0 on github thx Rens
-
maybe this is helpful for the problems people run into with this tool. the trouble sits mostly in the axis. the buttons are mapping straight forward. example: I am mapping two sticks into 1. (joystick and pedals) this requires the rudder from stick 1 to be replaced by the rudder (pedals) of stick 2. normal joystick is laid out like this: 0 X 1 Y 2 Rudder 3 throtle 4 hatX 5 hatY In the virtual Joystick axis: 0 = x, no problem 1 = y, no problem 2 becomes 5. 3 becomes 6. the hatx and haty becomes 16...
-
maybe this is helpful for the problems people run into with this tool. the trouble sits mostly in the axis. the buttons are mapping straight forward. example: I am mapping two sticks into 1. (joystick and pedals) this requires the rudder from stick 1 to be replaced by the rudder (pedals) of stick 2. normal joystick is laid out like this: 0 X 1 Y 2 Rudder 3 throtle 4 hatX 5 hatY In the virtual Joystick axis: 0 = x, no problem 1 = y, no problem 2 becomes 5. 3 becomes 6. the hatx and haty becomes 16...
-
maybe this is helpful for the problems people run into with this tool. the trouble sits mostly in the axis. the buttons are mapping straight forward. example: I am mapping two sticks into 1. (joystick and pedals) this requires the rudder from stick 1 to be replaced by the rudder (pedals) of stick 2. normal joystick is laid out like this: 0 X 1 Y 2 Rudder 3 throtle 4 hatX 5 hatY In the virtual Joystick axis: 0 = x, no problem 1 = y, no problem 2 becomes 5. 3 becomes 6. the hatx and haty becomes 16...
-
maybe this is helpful for the problems people run into with this tool. the trouble sits mostly in the axis. the buttons are mapping straight forward. example: I am mapping two sticks into 1. (joystick and pedals) this requires the rudder from stick 1 to be replaced by the rudder (pedals) of stick 2. normal joystick is laid out like this: 0 X 1 Y 2 Rudder 3 throtle 4 hatX 5 hatY In the virtual Joystick axis: 0 = x, no problem 1 = y, no problem 2 becomes 5. 3 becomes 6. the hatx and haty becomes 16...
-
maybe this is helpful for the problems people run into with this tool. the trouble sits mostly in the axis. the buttons are mapping straight forward. example: I am mapping two sticks into 1. (joystick and pedals) this requires the rudder from stick 1 to be replaced by the rudder (pedals) of stick 2. normal joystick is laid out like this: 0 X 1 Y 2 Rudder 3 throtle 4 hatX 5 hatY In the virtual Joystick axis: 0 = x, no problem 1 = y, no problem 2 becomes 5. 3 becomes 6. the hatx and haty becomes 16...
-
check my post. 2 = #5 (rudder) 3 = #6 (throttle) 4 = #16 (hatX) 5 = #17 (hatY) **
-
ok. here is some answers to what one can find in the previous 4 pages :-) what I am doing: combine a joystick and a rudder pedal. that means eliminating the rudder from the joystick, and use the rudder pedal instead. the mapping is broken: axis 0 and 1 map to 0 and 1 ( x and Y) axis 2 is axis 5, and you map it to 2 ( z or rudder ) axis 2 is axis 6, and you map it to 3 ( throttle, ussually ) hat X is 16 and you map it to 4 hat Y is 17 and you map it to 5 these numbers (map it to # ) correspond to...
-
hello, I have been using nmon on suse linux. (I built it freshly and packaged it...
-
hello, I have been using nmon on suse linux. (I built it freshly and packaged it...
-
hello, I have been using nmon on suse linux. (I built it freshly and packaged it...
1