{"action":"created","issue":{"url":"https://api.github.com/repos/gleb812/pch2csd/issues/6","repository_url":"https://api.github.com/repos/gleb812/pch2csd","labels_url":"https://api.github.com/repos/gleb812/pch2csd/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/gleb812/pch2csd/issues/6/comments","events_url":"https://api.github.com/repos/gleb812/pch2csd/issues/6/events","html_url":"https://github.com/gleb812/pch2csd/issues/6","id":300068642,"number":6,"title":"Print human readable labels for the module parameters","user":{"login":"ech2","id":1007225,"avatar_url":"https://avatars0.githubusercontent.com/u/1007225?v=4","gravatar_id":"","url":"https://api.github.com/users/ech2","html_url":"https://github.com/ech2","followers_url":"https://api.github.com/users/ech2/followers","following_url":"https://api.github.com/users/ech2/following{/other_user}","gists_url":"https://api.github.com/users/ech2/gists{/gist_id}","starred_url":"https://api.github.com/users/ech2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ech2/subscriptions","organizations_url":"https://api.github.com/users/ech2/orgs","repos_url":"https://api.github.com/users/ech2/repos","events_url":"https://api.github.com/users/ech2/events{/privacy}","received_events_url":"https://api.github.com/users/ech2/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2018-02-25T22:38:00Z","updated_at":"2018-03-04T16:15:56Z","closed_at":null,"author_association":"COLLABORATOR","body":"Currently, the only way to see parameters of a module is by printing the contents of a patch using the `-p` argument, like this\r\n\r\n```\r\n$ pch2csd -p lfoA2OscA.pch2\r\nPatch file: lfoA2OscA.pch2\r\n\r\nModules\r\nName      ID    Type  Parameters                 Area\r\n------  ----  ------  -------------------------  ------\r\nLfoA       1      26  [0, 0, 0, 66, 2, 1, 4, 0]  VOICE\r\nOscA       4      97  [64, 64, 1, 127, 2, 0, 3]  VOICE\r\nOut2       2       4  [0, 1, 0]                  VOICE\r\nLfoC       3      24  [64, 0, 4, 2, 1]           VOICE\r\n\r\nCables\r\nFrom                   To                Color    Type    Area\r\n-----------------  --  ----------------  -------  ------  ------\r\nLfoA(id=1, out=0)  ->  OscA(id=4, in=1)  blue     out-in  VOICE\r\nOscA(id=4, out=0)  ->  Out2(id=2, in=0)  red      out-in  VOICE\r\nOscA(id=4, out=0)  ->  Out2(id=2, in=1)  red      out-in  VOICE\r\n```\r\n\r\nThis 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.\r\n\r\nThis 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."},"comment":{"url":"https://api.github.com/repos/gleb812/pch2csd/issues/comments/370241344","html_url":"https://github.com/gleb812/pch2csd/issues/6#issuecomment-370241344","issue_url":"https://api.github.com/repos/gleb812/pch2csd/issues/6","id":370241344,"user":{"login":"zappfinger","id":5838951,"avatar_url":"https://avatars1.githubusercontent.com/u/5838951?v=4","gravatar_id":"","url":"https://api.github.com/users/zappfinger","html_url":"https://github.com/zappfinger","followers_url":"https://api.github.com/users/zappfinger/followers","following_url":"https://api.github.com/users/zappfinger/following{/other_user}","gists_url":"https://api.github.com/users/zappfinger/gists{/gist_id}","starred_url":"https://api.github.com/users/zappfinger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zappfinger/subscriptions","organizations_url":"https://api.github.com/users/zappfinger/orgs","repos_url":"https://api.github.com/users/zappfinger/repos","events_url":"https://api.github.com/users/zappfinger/events{/privacy}","received_events_url":"https://api.github.com/users/zappfinger/received_events","type":"User","site_admin":false},"created_at":"2018-03-04T16:15:55Z","updated_at":"2018-03-04T16:15:55Z","author_association":"COLLABORATOR","body":"Thanks! It seems to work indeed...\n\nRichard\n\n\nOn 04/03/18 17:11, Eugene Cherny wrote:\n>\n> @zappfinger <https://github.com/zappfinger> I added you as a \n> collaborator for this repo. Now you shouldn’t have this issue.\n>\n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub \n> <https://github.com/gleb812/pch2csd/issues/6#issuecomment-370240987>, \n> or mute the thread \n> <https://github.com/notifications/unsubscribe-auth/AFkYZ-kPVgwANbMbqTG3GwBHzvg70-5Yks5tbBIvgaJpZM4SSfnQ>.\n>\n\n"}}
{"actor":{"display_login":"zappfinger"}}