Page 1 of 3
Ruby & REAPER 64bit
Posted: Wed Jan 28, 2015 6:25 pm
by Drnkhobo
So I want to know if anyone else has had any issues when using your plugins in REAPER 64bit..?
As far as I have gathered, there are issues with background triggers/processing within Ruby when under the REAPER 32bit bridge which causes Rubymade editboxes to become un-clickable.
Ive checked the forums and found info about other users having similar issues and wanted to check if there was a resolution to this?
Re: Ruby & REAPER 64bit
Posted: Wed Jan 28, 2015 8:41 pm
by kortezzzz
Yes, ruby has problems with some daws. Most problematic is probably Abelton; All of my plug-ins ruby features are out of order there. Didn't had issues with reaper yet, but I won't be surprised if I'll find any. Many daws don't like ruby
Re: Ruby & REAPER 64bit
Posted: Wed Jan 28, 2015 11:30 pm
by Nubeat7
as nearly always, i cannot agree when its about "its an ruby issue" all of my plugins have pure ruby GUI controls and lots other ruby stuff inside and they are running well in ableton live, cubase, renoise, FL, and reaper (while i din't tested it with the bridge to be honest) i also didn't ever get any issue messages from any user and i have about 12000 downloads only on my page (the free stuff is hosted on other highly frequented sites too)... so are you sure it is an ruby issue?
anyway if you know that it is an ruby issue it would be great to let the community know what the exact issue is, so we could maybe find some solution or workaround
Drnkhobo wrote:As far as I have gathered, there are issues with background triggers/processing within Ruby when under the REAPER 32bit bridge which causes Rubymade editboxes to become un-clickable.
would be fine to extract the problematic modules and find the concrete bug
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 12:51 pm
by Ricciardo
This post explaines a lot...
i am having issues with Ruby also in x64 daws...
(and i only tested it in x64 daws)
I am using this mudulation system ->
viewtopic.php?f=2&t=3271but the modulation only works when the plugin is opened in the DAW, if its minimized, or closed in background
it stops, it doesnt work...
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 1:38 pm
by Drnkhobo
@Nubeat, I have tested it in 32bit and there is no issue I can find. It is indeed an issue with Ruby and 64bit.... you really need to try it on a 64bit machine to see its the bridge. Also, I will attach an example schm file for you to export as vst and try for yourself. Like I said, its only in 64bit bridge. Take a gander at the 2 editboxes inside the schm.... testing it as a vst in Reaper64 I found that the stock editbox (no Ruby) works....but not my version....so I think there is something right there...
@Ricciardo, I know that this has been a topic of discussion before (with RJHollins I think) and I had to change my Ruby modules that worked in the background. Unfortunatey I never found a way around it. Perhaps he will see this topic and comment for us. I feel for you though as some things are easier done in Ruby
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 2:26 pm
by Ricciardo
How did you changed the modules to work in background? did you make it??
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 2:35 pm
by tulamide
I don't have a 64-bit-system, so can't really test this. But assuming it is as stated there is a clue for me.
It works without issues in a 32 bit environment, but fails when used bridged? Chances are the bridge is causing it. Maybe it is a good idea to inform Reaper's developers of this as well? They are working hard each day to improve their DAW, so they might be interested in finding out if the bridge can be improved.
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 2:40 pm
by Drnkhobo
Will def send a message to the Reaper guys. And no fix for this yet Ricciardo
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 2:44 pm
by Ricciardo
tulamide wrote:I don't have a 64-bit-system, so can't really test this. But assuming it is as stated there is a clue for me.
It works without issues in a 32 bit environment, but fails when used bridged? Chances are the bridge is causing it. Maybe it is a good idea to inform Reaper's developers of this as well? They are working hard each day to improve their DAW, so they might be interested in finding out if the bridge can be improved.
No actually i just installed an old x86 ableton live i had to check if it 32 bit plugin worked without being bridged
it doesnt...
Ruby time doesnt work in background... it apears that ruby is attached with "display" if the plugins is not open, it doesnt make calculations or anything...
Re: Ruby & REAPER 64bit
Posted: Thu Jan 29, 2015 2:58 pm
by Nubeat7
thx drnkhobo for extracting the issue, i'm at work atm, so i can test it later in the evening...
but what i could see is that you don't use the edit index in the editFinished methode, i don't know if this could be the reason, i normally use it, i also use the ruby editbox in all of my presetmanagers so if there would be troubles i think i should got some messages about it...
maybe try to define the index when finishing the edit
Code: Select all
def editFinished id,text
val = text.to_f if id == 1
outval = case val
when 0..99
output val
else
output @ins[3]
end
end