xXCpt_NemoXx
I believe I previously raised a frustration—either earlier in this thread or elsewhere on the forums—about how performing a stem split on the FLX10 causes other stems on the originating deck that were already disabled to be re-enabled.
Recently, I’ve been experimenting with AI and ChatGPT to create a script that would solve for this behavior. While the script it wrote seems close, it still doesn’t work as expected overall and makes zero noticable difference.
I’d really appreciate it if any scripting veterans could help identify what might be missing, or if this is a limitation of the FLX10 hardware itself. Any explanations or suggestions would be welcome.
The original script for a vocal stem split, which is missing handling of the rhythm stem state:
My iterated verion for a vocal stem split that should account for the rhythm stem state:
Recently, I’ve been experimenting with AI and ChatGPT to create a script that would solve for this behavior. While the script it wrote seems close, it still doesn’t work as expected overall and makes zero noticable difference.
I’d really appreciate it if any scripting veterans could help identify what might be missing, or if this is a limitation of the FLX10 hardware itself. Any explanations or suggestions would be welcome.
The original script for a vocal stem split, which is missing handling of the rhythm stem state:
( stem 'Instrumental' 0% ? set '$instrOff' 1 : set '$instrOff' 0 ) & stems_split 'vocal' & var '$instrOff' ? stem 'Instrumental' 0% : nothing
My iterated verion for a vocal stem split that should account for the rhythm stem state:
( stem 'Instrumental' 0% ? set '$instrOff' 1 : set '$instrOff' 0 ) & stems_split 'vocal' & var '$instrOff' ? stem 'Instrumental' 0% : ( stem 'Rhythm' 0% ? set '$rhythmOff' 1 : set '$rhythmOff' 0 ) & stems_split 'vocal' & var '$rhythmOff' ? stem 'rhythm' 0%
Posted 5 days ago @ 9:33 pm