TWO 4 Win 0.12.7 Vezer and TouchDesigner

I’m using TWO as an Interface between Vezer and TouchDesigner, the result displayed in MadMapper which then drives the DMX lighting in Unreal Engine.

I find it easy to manually adjust the sliders so I can debug without having to change the source system Vezer, ideal if you have many channels of data.

It will be great when I can assign some OSC or Midi values and control these with a hardware device in the future.

I also use the record option in TWO (WinOS) to allow replay on a loop and I can then remove the source system (macOS) and unit test each stage. Then I can support system integration testing as I connect the data touchpoints together and test the data flow.

This approach also helps to keep the resource requirements to a minimum as I can record inputs/outputs in TWO, TouchDesigner and Unreal Engine if I thought either of the following were true;

  • my computer resources we’re becoming a bottleneck
  • not enough screen real-estate to make it an ideal setup
  • support regression testing during debugging when you need a specific data flow on a loop

Example

1 Like

Thanks for this writeup, very nice to see people’s workflows!

Sooner rather than later I’d like to expand on TWO’s curve editing features, then you could depend on one less app, since I’m assuming you’re using Vezer for it’s ability to specify automation curves in its timelines with more precision than TWO’s current simple spline interpolation.

1 Like

Hey yes that’s right, if I’m creating a timeline based project, I mainly align to cue points derived from an audio track with different curves with values between 0 -1. There are many tracks controlling the OSC data. Some tracks are just flags with a value like a variable hight where I may not want to automate a curve and just need a specific value.

The keyboard, midi/OSC controls would be good first please.

1 Like

Thanks! I hear you :slight_smile:

1 Like