DSP Robotics Support

@ rj hollins

does it happen with all bitmapversions here?

and what version of fs are you using?

v: .oo6 loads and displays fine.

v: .008 loads but no keyboard displays. The internal BITMAPS do have the data, as I can force a view with a viewer from the toolbox.

FS 3.0.4 is what I'm using.

[i have 3.0.7, but I was having issues. Went back to 304

yeah its the problem that the ruby component changes with each version , what i meant was to connect the afterload with the bitmap inputs at the ruby module,

before 3.06 bitmaps were not stored at the ruby inputs..
but this should work in 3.08, really don't know whats the problem here, maybe you need to reconnect the bitmaps that they get stored once at the ruby component inputs!?

connect the afterload with the bitmap inputs at the ruby module,

That was it ... WORKS !

Wow ... nice work on those keys

Thanks NuBeat

oh good to hear!
btw. the images for the keys are from palls stock keyboard which is used ( i think it was ) at the multisampler..

Thats really good Newbeat7! what a difference it makes being done in ruby! i had some issues with a few of the older keyboards around, keys disappearing etc, but this works very smoothly! well done m8!

Regards

Hey Nubeat7 It seems the plug-in using the Bitmap version crashes on startup half of the time (FL&Reaper). While testing with the other one causes less crashes. And by removing it from the schematic completely the crash never happens. I'm on 3.0.5 and connecting after loads as needed.
I'm almost sure its the keyboard. Any ideas? Anyone else having the same problem?

if it crashes only on startup, i would try to delay some triggers which happen when its loading, i think on version 3.05 you need to trigger each bitmap with an afterload or? if so you could trigger them in with delays so taht not all need to be loaded at once.. or similar things, thats the only idea i have to identify the problem...

try also the versions without bitmaps, if it happens only with the bitmap version for sure it has something to do with the bitmaps..

hope this helps..

Nubeat7 wrote:if it crashes only on startup, i would try to delay some triggers which happen when its loading, i think on version 3.05 you need to trigger each bitmap with an afterload or? if so you could trigger them in with delays so taht not all need to be loaded at once.. or similar things, thats the only idea i have to identify the problem...
try also the versions without bitmaps, if it happens only with the bitmap version for sure it has something to do with the bitmaps..
hope this helps..

I thing it was the same without bitmaps. Anyways i designed something simpler without ruby so not worried about that anymore hehe.