Metadata info opcodes #29
Replies: 0 comments 7 replies
-
I think since it already had "info" prefix, we can take out the "label"
? |
Beta Was this translation helpful? Give feedback.
-
It could also end up in its own Practical considerations: It is quite likely that some of these values may contain spaces. Let's not repeat the messy backtracking required for parsing sample filenames here. I can imagine several solutions:
|
Beta Was this translation helpful? Give feedback.
-
for this specific case I would vote the comment block option, something like Doxygen comments (using c or c++ styles)
|
Beta Was this translation helpful? Give feedback.
-
Doxygen style could work. However I think strings in SFZ need to be revisited regardless, and @sagamusix has some good points. Also, using doxygen for data that will be presented to the end user (Player Plugin, in info tab) feels wrong. |
Beta Was this translation helpful? Give feedback.
-
It may seem odd yes, but I think for this context could be the a good solution also to avoid to add compatibility issues as sagamusix said. OTOH Doxygen was made to be parsed just for extracting data, so I don't think will be particular issues for that purpose, otherwise this solution would be pointless other than looking strange. |
Beta Was this translation helpful? Give feedback.
-
Not doc comments preferably, SFZ parsing is already very vaguely specified, and doc comments are not helping. |
Beta Was this translation helpful? Give feedback.
-
I'm one against ui in sfz, and at some extent also ui related labels (and so the Recently output_labelN has been implemented in Calfbox, which also goes under Note that UI unrelated opcodes comes from extensions only:
plus As side note it's not clear what to do with #define, which seems to be used outside headers (like it should being something coming from C language) but this is how was meant in sfz2. So I think all of these should not go in sfz 3 under the control header but using a new one, which would be something like So the above should follow the same logic and naming convention, e.g.: |
Beta Was this translation helpful? Give feedback.
-
Currently library creators enter info about SFZ files as comment blocks.
For this data to be useful, for database, or display, a group of opcodes would be needed. Such as:
Beta Was this translation helpful? Give feedback.
All reactions