Replies: 1 comment
-
If the design intention is to make it solely functional via text file, audio file resources could be stored via delimiter & path/ UID at the end of a dialogue line. To integrate dragging & dropping, we could simply reformat drag & dropped objects on the CodeEdit via I'm more than happy to do all the necessary work on this addition myself, as I'm likely going to do so regardless of whether it's accepted as a contribution here or not. I love this plugin and intend to use it, along with VO, in many future projects to come, however, I'd love to see it integrated into the main branch as opposed to a fork. Please let me know if something like this would be accepted or not in the first place and under which conditions, if so, as I'd love to find a way to integrate some form of these changes. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Goal
Introduce smoother mechanics to adding discreet voice-acted recordings (or, heck, any audio file) to individual lines of dialogue.
Methodology
Add some form of drag & drop to allow developers to quickly drag audio files to their corresponding line of dialogue, then pass each audio file through to runtime along with its corresponding line of dialogue, to be played by the balloon when that line is fetched and displayed.
Proof of concept
I have an initial (currently non-functional) quick & dirty implementation of the idea here. I designed what I have so far to be as far out of the way of normal use of the plugin as possible, but available if needed (via toggle). The reason it's nonfunctional is that I'm unsure of the approved way of saving the file path data to the all-text resource, and can't run the data all the way through without that.
In Conclusion
Let me know what you think! I'm happy to scrap as much of what I've done so far as necessary, just looking to hopefully streamline the VO process as much as possible.
Beta Was this translation helpful? Give feedback.
All reactions