Default inputs #491
Comments
|
This request sounds interesting! Could describe how this would look in the user interface? It might be related to "clicking" the input region of the parameter. This currently opens the symbol browser with some recommendations. Maybe there could be on prefilled on top... |
|
I'm working on a something similar on the new version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding a patching input to the input node that functions as a source of default data to pass through when no external input is connected.
Touch designer has a similar patching mechanic and its extremely useful for having patches that function as ready to go complex generators and effects that also have built in demonstration, so when they are added to the patch you can immediately see what they do, but they are also instantly ready to plug in your own video/model/etc.
For example I am currently using the OpticalFlowExample from the image effects examples library, and it has a video file inside the patch demonstrating it, I like the nature of the effect and wanted to make use of it, in order to do that I have to go into the example, delete the video, add an input and wire it up and then connect that into my patch.
This saves several steps and helps in the flow of learning, since the complex example patches can often be a go to for the initial learning stage, the examples could be reusable drag and drop assets that are setup for immediate use.
The text was updated successfully, but these errors were encountered: