Set date through rnbo.remote or OSC
Hi,
I managed to set a new reference to a soundfile I've replaced through rnbo.remote but I couldn't set a new date (cf. imgcaps) to launch that file. Any hint ? Through OSC maybe ? How can I tweak the old date ? Thanks
Max 8.5.7 runs with rnbo 1.3.0. Unfortunately I can't upgrade to the newest version.
Best,
N.
Hey, can you share a patch that has this date parameter? I'm not sure how you got the formatting you have. I also don't know what you mean by cf. imgcaps.
Hi Alex OR XNOR :-)
Thanks for your reply.
Sorry ! cf. imgcaps : Cf. (from latin "report to") See the attached image capture.
how you got the formatting you have :
param date @enum 07:59:22 08:29:23 08:59:37 09:29:02 09:59:26 10:28:49... etc.
It's just a convenient way to set enumerated value for these symbols
Actually the rpi loads a python script at boot to retrieve the clock (NTP activated) and send it through osc to the max program to launch audio files exactly at these dates
Attached the <rpi-ip:5678> json file. I checked that the date param has access 3 (sorry I can't access my external hard drive and the patch for the moment)
Here's a diagram :
param date @enum 07:59:22 08:29:23 08:59:37 09:29:02 09:59:26 10:28:49 10:59:19 11:29:22 11:59:22 12:29:38 12:59:11 13:29:24 13:59:24 14:29:35 14:59:28 15:29:35 15:59:28 16:29:27 16:59:21 17:29:33 17:59:10 18:29:25 18:59:21 19:29:37 19:59:24
⬇︎
param ltdc_bell @max 25 @steps 25
⬇︎
num float object
⬇︎
t b f (object)
⬇︎ param ltdc_stop
set stop
⬇︎
| setparam buffer
groove~ ltdc 2 @buffername b_01_StBrice_Carillon_8_00AM_wav b_02_StBrice_Carillon_8_30AM__wav b_03_StBrice_Carillon_9_00AM_wav b_04_StBrice_Carillon_9_30AM_wav b_05_StBrice_Carillon_10_00AM_wav b_06_StBrice_Carillon_10_30AM_wav...etc. @loop 0
⬇︎
param ltdc_amp @value 0. @min 0. @max 3.
line~ 0 100
*~ x 2
out~ 1 out~ 2
Instances of :
bell1
bell2
bell3
...
bell n
Best,
okay, I see that your date param has these possible values:
["07:59:22","08:29:23","08:59:37","09:29:02","09:59:26","10:28:49","10:59:19","11:29:22","11:59:22","12:29:38","12:59:11","13:29:24","13:59:24","14:29:35","14:59:28","15:29:35","15:59:28","16:29:27","16:59:21","17:29:33","17:59:10","18:29:25","18:59:21","19:29:37","19:59:24"]when you say that you "can't set a new date" do you mean you cannot select and set your param to one of those values or, how are you trying to set your "date" ?
In fact, I calculated these dates : soundfile duration - clock right time i.e. "08:00", "08:30"... etc. in order to prepend a bell sound to tell the exact time right after playing the file. I've replaced one of the soundfiles so I have to set the according date because of the new file's duration.
I would like to use sflist~ or some object available in the rnbo~ environment to retrieve a snd duration and implement this operation in the program in order to replace a date on the fly ! Does it sound possible ? Thanks
Both buffer and multibuffer give you the length of the audio file, in samples, they also give you the sample rate, from those to values you can calculate the length in seconds. BUT, rnbo doesn't have string representations so you cannot format something like 09:02:95 arbitrarily and set it to a param.
One thing you might think about doing is using multiple param objects to represent each segment:
[param s @min 0 @max 59]
[param m @min 0 @max 59]
[param h @min 0 @max 23]
then you could map those to the second, minute and hour values you compute.
Thanks Alex.
How about the first question ? How to access and tweak the date param through rnbo.remote or OSC ? What syntax after /rnbo/inst/0/params/date ?
Congrats for the Rnbo 1.4.0 version !
if you're intent on using enum with your params, via OSC, you'll have to send a string from the list you specified in advance /rnbo/inst/0/params/date "09:29:02"
if you move to a numeric value, you can just supply that numeric value.
via rnbo remote, it is the same except your message doesn't need to have the whole path, just "date 09:29:02"
Thanks Alex.
Sweet Summer,
N.