Hello everybody!

I’m wondering what your workflows are to create and recall presets for MIDI for live situations.

I want to work with MIDI encoder and motorized faders.
When i call an instrument i want to set my encoder and fader to predefined values.
in which way can i set my presets?
i found out that ctrlprint can save values to a text file. but how can i use this text file for recalling a preset?
or is there an more friendly way?

Greetings
Philipp
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Philipp,
there are a few ways to solve this. The basic idea, I can see, is to
create a kind of SysEx vector, i.e. a list of your controllers, always
stored and sorted in the same way. Unused controllers would be set to
default values.

As for save and load: you can print values to text files, using your
method or fprints or possibly others. Text files can be loaded into a
table with GEN23. There is also ftsave and ftload.

You can create preset-number based filesnames with sprintf or the str*
functions like strcat and similar.

The actual mechanism: it might be best to have dedicated load/save
instruments. A load instrument would load the data and then go through
the whole list of controller values at i-time to set your motorised
faders.

Passing data around: at some point a table is involved. You only need
one active table for the currently loaded preset. You can use a global
table giTable, you can use a local table, created in a persistent way
(ftgen or ftload) and pass the table number around through a channel
(chn opcodes), through one global variable, through parameters (a bit
awkward perhaps) or ... You can copy the loaded values to a global array
and work on that. If there aren't too many controllers you can copy them
to channels (chn again). All this means that your preset data is
available anywhere inside your orchestra.

NOTE: for channels, be sure to use a good naming scheme (strcat/sprintf can work
wonders), perhaps with names like:
mysynth.filter
or
mysynth.cc0
or something even more structured.

I hope that some of that helps. Whether you use straight ftables,
channels, a global array or another system, depends on your personal
workflow and preference. They can all be quite ellegant and well
maintainable. A separate load and save instrument is advised! You can
build a save+load instrument with a bit of control flow (if statements)
and good parameters (p-fields). This instrument would most likely work
at i-time. You can use turnoff at the end of your instrument, so it will
only run as long as required. You may want to set a global flag (channel
or whatever) to indicate readiness. That might be set to 0 or off when
you begin to load and set to 1/on when everything is loaded. That's
optional though. It depends on your needs and preferences again.

Best wishes,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

Make all the clouds disappear
Put all your fears to rest <3
(Britney Spears)

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hey Jeanette,

thanks a lot for this precise description!

In the meanwhile i was working with some opcodes that were designed for this task. With a little research i got my head around this.
And i guess i have the solution for this

But now i get some „Segmentation fault“ error and it doesn’t work and i don’t know why.

Here is my code, maybe someone can help:




-m0d
-d -odac -W -3 -+rtmidi=portmidi -Ma -Q0


sr = 44100
ksmps = 32
nchnls = 2
0dbfs = 1.0

massign 0, 0

opcode getMidiNote, k, k
  kChannel xin

  kStatus, kChan, kData1, kData2 midiin
  kMidiNote init 0
  if kStatus == 144 && kChan == kChannel then
    kMidiNote = kData1
  endif
  
  xout kMidiNote 
endop

#define UPDATE_CC(Chn'CC)
#
i$CC chanctrl $Chn, $CC, 0, 127
outic $Chn, $CC, i$CC, 0, 127
#





instr prepare_preset
  gkMidiData[] ctrlsave 1, 10,11,12,13,14,15,16,17
  
  kPreset getMidiNote 1
  printks2 "Preset Number: %d\n", kPreset

  kChar sensekey
  // save preset == 's'
  if kChar == 115 then
    schedkwhen 1, 0, 1, "save_preset", 0, 1, kPreset
  endif
  // call preset == 'r'
  if kChar == 99 then
    schedkwhen 1, 0, 1, "update_cc", 0, 1, kPreset
  endif
endin

instr save_preset
  kPreset ctrlpreset p4, gkMidiData
  ctrlprintpresets "./presets.txt"
endin

instr update_cc
  ctrlselect p4
  $UPDATE_CC(1'10)
  $UPDATE_CC(1'11)
  $UPDATE_CC(1'12)
  $UPDATE_CC(1'13)
  $UPDATE_CC(1'14)
  $UPDATE_CC(1'15)
  $UPDATE_CC(1'16)
  $UPDATE_CC(1'17)
  turnoff 
endin


i "prepare_preset" 0 60




> Am 17.04.2024 um 13:48 schrieb Jeanette C. :
> 
> Hi Philipp,
> there are a few ways to solve this. The basic idea, I can see, is to
> create a kind of SysEx vector, i.e. a list of your controllers, always
> stored and sorted in the same way. Unused controllers would be set to
> default values.
> 
> As for save and load: you can print values to text files, using your
> method or fprints or possibly others. Text files can be loaded into a
> table with GEN23. There is also ftsave and ftload.
> 
> You can create preset-number based filesnames with sprintf or the str*
> functions like strcat and similar.
> 
> The actual mechanism: it might be best to have dedicated load/save
> instruments. A load instrument would load the data and then go through
> the whole list of controller values at i-time to set your motorised
> faders.
> 
> Passing data around: at some point a table is involved. You only need
> one active table for the currently loaded preset. You can use a global
> table giTable, you can use a local table, created in a persistent way
> (ftgen or ftload) and pass the table number around through a channel
> (chn opcodes), through one global variable, through parameters (a bit
> awkward perhaps) or ... You can copy the loaded values to a global array
> and work on that. If there aren't too many controllers you can copy them
> to channels (chn again). All this means that your preset data is
> available anywhere inside your orchestra.
> 
> NOTE: for channels, be sure to use a good naming scheme (strcat/sprintf can work
> wonders), perhaps with names like:
> mysynth.filter
> or
> mysynth.cc0
> or something even more structured.
> 
> I hope that some of that helps. Whether you use straight ftables,
> channels, a global array or another system, depends on your personal
> workflow and preference. They can all be quite ellegant and well
> maintainable. A separate load and save instrument is advised! You can
> build a save+load instrument with a bit of control flow (if statements)
> and good parameters (p-fields). This instrument would most likely work
> at i-time. You can use turnoff at the end of your instrument, so it will
> only run as long as required. You may want to set a global flag (channel
> or whatever) to indicate readiness. That might be set to 0 or off when
> you begin to load and set to 1/on when everything is loaded. That's
> optional though. It depends on your needs and preferences again.
> 
> Best wishes,
> 
> Jeanette
> 
> -- 
> * Website: http://juliencoder.de - for summer is a state of sound
> * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
> * Audiobombs: https://www.audiobombs.com/users/jeanette_c
> * GitHub: https://github.com/jeanette-c
> 
> Make all the clouds disappear
> Put all your fears to rest <3
> (Britney Spears)
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>       https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> 

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Philipp,
thanks for pointing out these opcodes. I never paid any attention to them, but 
they look really helpful.

I can see one possible issue, that is your call to ctrlpreset. The manual, 
even the online version gives the syntax as:
kpreset ctrlpreset ktag, kchnl, kctlno1, [kctlno2] [, kctlno3] ...
So there is no array version documented, which might just work, but the second 
input parameter is the channel, which I suppose is not saved in the data 
array, so you may try with at least 1 as the second parameter:
kPreset ctrlpreset p4, 1, gkMidiData

Otherwise a neat solution.

One point, which is pure curiosity: why did you chose a UDO to read the note 
values and a macro to update the MIDI CC values? Coincidence or design?

Best wishes,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

All you people look at me like I'm a little girl.
Well did you ever think it be okay for me to step into this world. <3
(Britney Spears)

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Sorry, a P.S. experimenting with ctrlprint and ctrlsave, I found that the 
array has the following structure:
number_of_ccs, channel(apparently), 11_number, cc_value, cc_number, cc_value
This might lead to issues. Try to substitute the array in your call with at 
least certain elements from your array:
ctrlpreset p4, 1, gkData[2], gkData[4], ...

Perhaps that helps.

Best wishes and aplogies again for the continued reply,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

All you people look at me like I'm a little girl.
Well did you ever think it be okay for me to step into this world. <3
(Britney Spears)

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I can see one possible issue, that is your call to ctrlpreset. The manual, even the online version gives the syntax as:
kpreset ctrlpreset ktag, kchnl, kctlno1, [kctlno2] [, kctlno3] ...

Hi Philipp!
Apr 18 2024, Philipp Neumann has written:
...
> How much time needs it to write to the file?
> I just wanted to call a designated instrument just for one k-cycle to write a new preset. Is this enough?
Why bother, you already use turnoff. This gives the instrument enough
time to complete. Who knows depending on certain circumstances, it might
take a little more or a little less. Give the instrument a p3 or .1 or
maybe even .01 and leave the rest to the real world in this instance.

That's the theory and practise has proved it so far, for me.
...

Best wishes,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

What's practical is logical. What the hell, who cares?
All I know is I'm so happy when you're dancing there. <3
(Britney Spears)

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here