Print human readable labels for the module parameters

Currently, the only way to see parameters of a module is by printing the contents of a patch using the -p argument, like this

$ pch2csd -p lfoA2OscA.pch2
Patch file: lfoA2OscA.pch2

Modules
Name      ID    Type  Parameters                 Area
------  ----  ------  -------------------------  ------
LfoA       1      26  [0, 0, 0, 66, 2, 1, 4, 0]  VOICE
OscA       4      97  [64, 64, 1, 127, 2, 0, 3]  VOICE
Out2       2       4  [0, 1, 0]                  VOICE
LfoC       3      24  [64, 0, 4, 2, 1]           VOICE

Cables
From                   To                Color    Type    Area
-----------------  --  ----------------  -------  ------  ------
LfoA(id=1, out=0)  ->  OscA(id=4, in=1)  blue     out-in  VOICE
OscA(id=4, out=0)  ->  Out2(id=2, in=0)  red      out-in  VOICE
OscA(id=4, out=0)  ->  Out2(id=2, in=1)  red      out-in  VOICE

This represents parameters as an array of number ordered as they appear in the patch. To figure out to what UI element each parameter corresponds to, one would need to twiddle something in the NM editor, save the patch, print its contents again and compare the changes.

This is a bit tedious and error prone when creating special annotations for UDOs. To improve this we can print human-readable names of the parameters in the order they appear in a patch. There is an XML file flying around on the internets, supposedly with module parameters listed together with human-readable labels. @gleb812 knows about it. We need to find it, parse, add as metadata to the converter, and add some command-line parameter that would allow to access it.

[gleb812]

OK then. We can just exclude the file… )

[zappfinger]

Maybe it is also nice to add an option to show the parameter values /after/ conversion as well:

; VOICE AREA instr 1 ; Module    Parameters               Inlets    Outlets LfoA        0.26,0,0,0.516,2,1,4,2,  1,        7 Out2        0,1,0,                   7,7 LfoC        0.64,0,4,2,1,            1,        0 OscA        1.0,0.0,1,1.0,2,0,3,     1,7,      7

That way it can be checked if the right conversions are used… On 25/02/18 23:38, Eugene Cherny wrote:

Currently, the only way to see parameters of a module is by printing the contents of a patch using the |-p| argument, like this

|$ pch2csd -p lfoA2OscA.pch2 Patch file: lfoA2OscA.pch2 Modules Name ID Type Parameters Area ------ ---- ------ ------------------------- ------ LfoA 1 26 [0, 0, 0, 66, 2, 1, 4, 0] VOICE OscA 4 97 [64, 64, 1, 127, 2, 0, 3] VOICE Out2 2 4 [0, 1, 0] VOICE LfoC 3 24 [64, 0, 4, 2, 1] VOICE Cables From To Color Type Area ----------------- – ---------------- ------- ------ ------ LfoA(id=1, out=0) -> OscA(id=4, in=1) blue out-in VOICE OscA(id=4, out=0) -> Out2(id=2, in=0) red out-in VOICE OscA(id=4, out=0) -> Out2(id=2, in=1) red out-in VOICE |

This represents parameters as an array of number ordered as they appear in the patch. To figure out to what UI element each parameter corresponds to, one would need to twiddle something in the NM editor, save the patch, print its contents again and compare the changes.

This is a bit tedious and error prone when creating special annotations for UDOs. To improve this we can print human-readable names of the parameters in the order they appear in a patch. There is an XML file flying around on the internets, supposedly with module parameters listed together with human-readable labels. @gleb812 https://github.com/gleb812 knows about it. We need to find it, parse, add as metadata to the converter, and add some command-line parameter that would allow to access it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gleb812/pch2csd/issues/6, or mute the thread https://github.com/notifications/unsubscribe-auth/AFkYZzQ3i6wCgX0kcL85V5GaFUecMPgAks5tYeDIgaJpZM4SSfnQ.