Page 2 – Download and Changelog
ChangeStrings 1.4 (18.07.2020)
- Fixed a rare bug that incorrectly renamed tools when not in case sensitive mode and tools had similar names
- Fixed a rare bug when using shortcodes not in case sensitive mode
- Changed some debugging messages to better reflect the current mode
ChangeStrings 1.3 (16.07.2020)
- Fixed a bug that prevented the correct saving of inputs in Resolve when the About window was opened and saved
- Fixed a bug that prevented Change Strings to search for single characters when not in case sensitive mode
- Fixed a bug that prevented Change Strings to properly print the correct saving mode when in Fusion Standalone and Global Saving mode
- Added support to search and replace percentage signs “%”. Both single percentage signs and strings containing them
- This does not affect the shortcodes such as “%d”
- The opposites of the shortcodes have been tested and work properly. For example, “%D” will search for all characters that are not digits
- Fixed a typo
ChangeStrings 1.2 (06.07.2020)
- Redesign of the UI to make space for all the new features
- The UI now looks correct on a higher UI scale
- All text inputs now have a clear button
- Remember Inputs will keep its check status even if unchecked
- Options to change Filepaths individually for Loaders, Proxys and Savers
- Support for Styled Text in tools like the Text+ and Text3D
- Select Loaders, Savers or both with a single button click
- Change Strings remembers your previous selection and can revert back to it
- Support to search and replace in Modifier Names and Expressions
- A new Tristate Checkbox is added for Modifiers
- Toggle between no Modifiers, include Modifiers and only Modifiers
- This will only change connected Modifiers not connected Tools in general
- A new checkbox was added to keep Change Strings open even after clicking OK
- A new checkbox was added to the Advanced Settings to reduce the console messages of Change Strings. It is on by default, meaning it will print its actions to the console.
- The main Search and Replace operation was consolidated which makes it easier to add features and made the operation much more robust:
- Change Strings can now properly find and replace single dots “.”
- Previously working shortcodes such as “%l” are found and replaced much quicker without triggering a loop
- Support for the uppercase letter shortcode “%u”
- Support for all letters shortcode “%a”
- Searching and replacing single characters is much more efficient
- General improvements to the operation make it much more robust
- Improvements to the loop counter make it pretty much impossible for Change Strings to fall into an endless loop or crash
- The Max Replace Limit will now limit the replacements for each input as well
- Due to these improvements, the default Max Replace Limit increased to 30
- Change Strings handles the switching between Local and Global Saving modes much better (Fusion Standalone) and makes sure variables are correct once it closes (DaVinci Resolve and Fusion Standalone)
- Fixed minor issues with the Resolve or Global Saving mode
- Updated the manual for the new UI and features
ChangeStrings 1.1 (01.07.2020)
- Change Strings now supports DaVinci Resolve’s Fusion Page (thanks Bryan Ray)
- It automatically detects if it was opened in Fusion Standalone or DaVinci Resolve and changes its behavior to properly work in the corresponding software.
- Added the possibility to save the Inputs globally (Fusion Standalone only)
- Added a new “?” for this new setting
- Updated the manual accordingly
- Fixed a bug that prevented the Script to work when more Search for Inputs than Replace with Inputs were available
ChangeStrings 1.0 (29.06.2020)
- The first (sort of) Open Beta release of ChangeStrings. (Fusion Standalone only)
Change Strings likes to communicate, this is why you will quickly fill your console with messages from it. Through it, you can exactly see how Change Strings sees the world/strings.
Besides telling you about the current Pattern Breaker and Max Replace Limit, Change Strings will also tell you which node, expression, or filepath it changes and how. Through the console messages you will be able to tell exactly where a Pattern Breaker was placed and if it stopped because it couldn’t find the pattern anymore or because it reached the Max Replace Limit.
Without these many console messages, I wouldn’t have been able to debug the code and I also find it quite interesting to see what it does. But I also understand that this many console messages can be annoying. And with Change Strings 1.2 you are able to stop Change Strings from filling up your console if you choose so.
Thank you for being interested in my script Change Strings. If you’ve come to this page without seeing the manual, then I highly recommend reading it to understand how Change Strings works.
All future updates will be logged on this page and I will make sure that previous versions are available as well.
I don’t know of any composition breaking issues, but of course, use at your own risk. If you do experience issues, try closing and opening the composition again.
This script was successfully tested in:
- Fusion Standalone 16.2
- Fusion Standalone 9
- DaVinci Resolve 16.2
But please tell me of any issues or suggestions you have so I can improve the script.
How to report bugs
Please message me if you run into bugs or inconsistencies. For suggestions, you can use the comments under this post. Actual bug reports would be great as an email.
These things would be helpful to know:
- Fusion Standalone or DaVinci Resolve?
- Which version of the software?
- Which Version of Change Strings?
- What did you try to replace?
- What happened? (Crash? Unsuccessful replacement? Endless loop?)
- For critical bugs: Can you copy and paste the console messages in an email?