Baseline:
the following basic script which has been converted to a template:
log(event.props)
log(event.props.parameter1.name)
the template, where a custom type has been added:
for this template, a preset (named "empty") has been made:
when the preset is executed, the following log appears:
13.10.2024 13:43:28.04 <info> [Backend]: >> Command: empty [user:clb6ghfya00003a106z2gkgs9:cm27gf6630005gn10w0ehx819#cm27i87ro0002b9106rarghvq]
[LOG] {
"parameter1": {}
}
13.10.2024 13:43:28.04 <info> [Backend]: [LOG] undefined
What will be the correct way to access the name-value from the preset? Am I missing something here?
Soundflow version 5.8.2 on macOS 13.6.7
thanks in advance
best
Guenther
- SSoundFlow Bot @soundflowbot
Thanks for contacting SoundFlow support.
Please note, that the best way to get help with a script, macro or other content installed from the Store or content that you've made yourself, is to select the script/macro, then click the red Need help button, and then click "Get help with this script or macro".
By using this method, we will get access to more information and so should be able to help you quicker.
You can read more about how this works here: bit.ly/sfscripthelpIf you're seeing an error that isn't related to scripts or macros, and you think this is a bug in SoundFlow, please file a Help/Issue bug report.
You can see how to do this by going to bit.ly/sfhelpissue - SIn reply toG_O⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-1473
In reply toG_O⬆:Chad Wahlbrink @Chad2024-10-13 15:46:16.933ZHey @G_O,
Thanks for this report! I appreciate your thorough explanation and sharing of the code and logged messages.
I can confirm that I see the same behavior on SF 5.8.0+. I've logged this as a bug; once it is resolved, you will get an update on this thread.
Christian Scheuer @chrscheuer2024-10-13 18:50:02.072ZHi @G_O,
Thanks for reporting. We can confirm this will be fixed in 5.9.0, which is due to come out later this month.