RNASound

Hi everyone, I am working on a RNBO patch that I would like to export to use in my daw. The idea is a patch that takes in text input and translates it to morse code. I've figured out the logic and how to build it in Max using gen, jit.cellblocks, textedit, but as RNBO seems to be far more limited in terms of text/string processing, I don't know where to begin. Ideally, the JUCE plugin that RNBO spits out would have a TextBox that could be utilized by the patch. 

One possible solution I came up with was to create @params that take in text, then to handle text input and param passing in JUCE after exporting the RNBO patch as C++ code. 

But that kind of defeats the purpose! Any ideas of how to get text into RNBO?

Hi everyone, I am working on a RNBO patch that I would like to export to use in my daw. The idea is a patch that takes in text input and translates it to morse code. I've figured out the logic and how to build it in Max using gen, jit.cellblocks, textedit, but as RNBO seems to be far more limited in terms of text/string processing, I don't know where to begin. Ideally, the JUCE plugin that RNBO spits out would have a TextBox that could be utilized by the patch. 


One possible solution I came up with was to create @params that take in text, then to handle text input and param passing in JUCE after exporting the RNBO patch as C++ code. 
But that kind of defeats the purpose! Any ideas of how to get text into RNBO? 

Hi everyone, I am working on a RNBO patch that I would like to export to use in my daw. 

text-input-to-rnbo

how do you input text from DAW into plugin in first place ?

if RNBO can take midi input you might think of sysex

how do you input text from DAW into plugin in first place ?

if RNBO can take midi input you might think of sysex
ascii code



the first thing you have to do - before realizing it in rainbow - is to make sure that the host program passes keyboard input to plug-ins, which is in some cases turned off by default.


the first thing you have to do - before realizing it in rainbow -  is to make sure that the host program passes keyboard input to plug-ins, which is in some cases turned off by default.

I think you are on a hiding to nothing trying to get text into rnbo... 

as, unlike Max, RNBO does not handle symbols

https://rnbo.cycling74.com/learn/key-differences

this is not entirely suprising as text processing is not really a DSP function , and RNBO is focused on DSP, 

so Id be quite surprised if C74 will add symbols. (but who knows )

what I would do is 're-frame' the problem a bit, and think about what needs to be in the UI vs DSP.

Im not sure what you are trying to do, so hard to be specific, 

but generally, Id do all the text processing within JUCE in the UI, passing the morse code (1/0, so numbers :)) to your DSP function/rnbo patch.

note: rnbo does support lists and also you can pass in 'data blocks' from C++ to your rnbo patch.

so this might be useful, if you cannot get the data 'nicely' thru the parameter/signal interface. 

I think you are on a hiding to nothing trying to get text into rnbo...  
as, unlike Max, RNBO does not handle symbols 

https://rnbo.cycling74.com/learn/key-differences 

this is not entirely suprising as text processing is not really a DSP function , and RNBO is focused on DSP, 
so Id be quite surprised if C74 will add symbols. (but who knows ) 


what I would do is 're-frame' the problem a bit, and think about what needs to be in the UI vs DSP.
Im not  sure what you are trying to do, so hard to be specific, 
but generally, Id do all the text processing within JUCE in the UI, passing the morse code (1/0, so numbers :))  to your DSP function/rnbo patch.


note: rnbo does support lists and also you can pass in 'data blocks' from C++ to your rnbo patch.
so this might be useful, if you cannot get the data 'nicely' thru the parameter/signal interface. 


Thank you @thetechnobear I see now RNBO is more of just a DSP sandbox and I'll have to use C++ to handle my text input at the UI level, and then hand it off to the DSP portion of the code.

I think this is what I'll have to do. I plan on using lists so I can pass the data in a "nicer" way. Thanks a bunch for the feedback, I'll let you know how it goes!

Thank you @thetechnobear I see now RNBO is more of just a DSP sandbox and I'll have to use C++ to handle my text input at the UI level, and then hand it off to the DSP portion of the code. 

but generally, Id do all the text processing within JUCE in the UI, passing the morse code (1/0, so numbers :))  to your DSP function/rnbo patch.

note: rnbo does support lists and also you can pass in 'data blocks' from C++ to your rnbo patch.
so this might be useful, if you cannot get the data 'nicely' thru the parameter/signal interface.

cool, good luck... will be interested to hear how you approach this.

RNBO is new, so we are all figuring it out together.... it's good to share experiences1

cool, good luck... will be interested to hear how you approach this.
RNBO is new, so we are all figuring it out together.... it's good to share experiences1

UPDATE: Though you can't pass symbols, I've found that you can easily pass lists of numbers to RNBO as a message. You were right @thetechnobear

I think in the weeks since RNBO's release I've seen more tutorials on the C74 github and RNBO reference docs. This one in particular was very helpful to me: 

https://rnbo.cycling74.com/learn/sending-and-receiving-messages-cpp

You just need to use a "RNBO::list" which functions like a normal c++ list.

UPDATE: Though you can't pass symbols, I've found that you can easily pass lists of numbers to RNBO as a message. You were right @thetechnobear 

I think in the weeks since RNBO's release I've seen more tutorials on the C74 github and RNBO reference docs. This one in particular was very helpful to me: 
 
https://rnbo.cycling74.com/learn/sending-and-receiving-messages-cpp

Text input to RNBO?