More debug options
Posted: Fri Mar 01, 2024 17:14
Hello!
I almost ripped my hair out trying to figure out why a multiply node wouldn't be converted to a string, or connected to a print node before noticing it was a float2 - and the print node only accepting events.
I would strongly ask you to consider auto-concatenating float2/3/4 nodes if connected to a string node, as the procedure of unpacking -> string (x 2-4) -> concatenate (x amount of values) ->text render is really, really tedious when trying to debug. Especially so when you have multiple values you have to check the relation between, and have to debug in Resolume to get everything to work in context.
Having the option to connect signals and attributes to the print node would also be beneficial, both an attribute and signal stream can contain errors.
Would be great if it was possible to get som debug love for the next release!
I almost ripped my hair out trying to figure out why a multiply node wouldn't be converted to a string, or connected to a print node before noticing it was a float2 - and the print node only accepting events.
I would strongly ask you to consider auto-concatenating float2/3/4 nodes if connected to a string node, as the procedure of unpacking -> string (x 2-4) -> concatenate (x amount of values) ->text render is really, really tedious when trying to debug. Especially so when you have multiple values you have to check the relation between, and have to debug in Resolume to get everything to work in context.
Having the option to connect signals and attributes to the print node would also be beneficial, both an attribute and signal stream can contain errors.
Would be great if it was possible to get som debug love for the next release!