Ruby & REAPER 64bit

[tulamide]

while it is only happening in the bridged version where the plugin is opened in an extra window while in the 32 bit version of reaper the plugin is inside the reaper plugin window which doesn't affect the usage when not playing..

i also recognised that (i'm testing it with the asio4all driver) in the 64 bit version of reaper there is always a little popup window in the lower right corner of the screen that asio4all is started or closed (in the default settings of reaper) which doesn't happen in the 32 bit version.. so its difficult to say for me where the problem is based

but for shure the 64 bit version of reaper handles this setting in a different way then the 32 bit version...

The releasing of the audio driver is also part of the background behaviour of a DAW, so it is related to what I said above. I have a feeling that it has to do with a feature of Flowstone's Ruby implementation. Remember, if ASIO (or in this case ASIO4All) is present, Ruby automatically syncs to ASIO. If the driver then is deactivated, chances are it doesn't have a fallback plan, but simply uses 0 ticks, with the result of not operating anymore.

EDIT: Of course, this would only be true, if we could observe that indeed the driver is not closed in the 32-bit version of Reaper.

[Nubeat7]

EDIT: Of course, this would only be true, if we could observe that indeed the driver is not closed in the 32-bit version of Reaper.

yes, that's what is irritating because the settings are there to set it on or off..

the second thing is that in the 64 bit version an own plugin window is open, also, it doesn't look like that ruby stops working becasue the actions get done after clicking outside of this window! so i think the issue lies maybe in the window handling of the bridged plugin!?

but i really don't know

[tulamide]

EDIT: Of course, this would only be true, if we could observe that indeed the driver is not closed in the 32-bit version of Reaper.

yes, that's what is irritating because the settings are there to set it on or off..

the second thing is that in the 64 bit version an own plugin window is open, also, it doesn't look like that ruby stops working becasue the actions get done after clicking outside of this window! so i think the issue lies maybe in the window handling of the bridged plugin!?

but i really don't know

Just a thought I had while reading that the actions get done after the bridge window loses the focus: Communication with the outside world is done through the windows api (for example mouse movement/clicks, edit boxes, dropdown menus, etc.) But, this is also true for the bridge window. DAWs just act like a midi through for those events, so the plugins get noticed of them (like mouse clicks), but maybe the bridge window doesn't fully support this behavior. It can then come to conflicts. For example, no windows control can be clicked without mouse capture, but only one instance is allowed to capture the mouse. If the bridge window captures the mouse, Ruby simply waits until getting the control over mouse capturing (via windows api). That was just a quick and dirty example, of course. But you get the point.

If some conflict of that kind occurs, there's not much Flowstone can do.

[RJHollins]

hmmm ... I need to go back and look through some of my projects ...

I have a NOISE generator that uses 'green' PRIMS that has momentarily stopped outputting while using Reaper-32. Nothing bridged obviously.

Maybe there's a setting in Reaper that affects this behavior ...

Nonetheless ... there was quite a long topic that I was part of, that dealt with some strange happenings. Those that participated might recall the issue I found putting a plugin on Reapers MASTER track only. I had a countdown display that would not start ...

The projects I made were having issues on 64-bit systems with MIDI data ... it seemed as if the plugin was in standby mode when it lost focus. It's been awhile ... and I really had to stop all my projects because I could not test properly for myself. I use my stuff fine on my 32-bit system [or if a problem, I at least have chance to fix] ... things with possible 'focus' issues that kill oscillators, or prevent MIDI data flow on 64-bit systems was more than I could handle professional [thus the plea for FS-64 .... I know, i know .... sorry].

But I will closely follow this and any thread dealing with this in hopes for a solution

[RJHollins]

ok, i found the problem, reaper per default closes the audio device when stopped playing!

if you unset this flag in the audio settings (under preferences) it works also when not playing!

i don't know why ruby doesn't work when audiodevice is there but not connected or closed - you also can see this when you save a project in FS with your soundcard activated - disconnect the soundcard and activate the project, then there is no audio device connected and all ruby components don't work! maybe this is an issue which could be solved by FS.

I also think that this behaviour was introduced in 3.06 or maybe earlier, but i'm not sure if it always was like this or not... i only know that i recognised this in version 3.06

i don't know if it could be stated as bug, but maybe it should be stated to malc!?

Oh NuBeat !!!

Once again, you are Saviour.

In another thread I recently started, I was forced to build a new computer and went 64-bit. All my VST plugins that used certain RUBY based components would not work UNTIL I hit PLAY. As soon as I STOP, things like the pull-down selectors would no longer open.

Strangely, the pull-downs based on GREEN worked just fine.

As to NuBeats finding, I un-tick the 'close audio device when stopped' option, now the GUI works !!!

More testing to do, but this is something of a possible solution.