OSC Pulse for Feedback

2024-05-17 09:52 UTC gpt-4o Open in ChatGPT ↗

You

I’m working in touchdesigner and currently have a feedback set to pulse on keyboard input. I now need to change this to pulse whenever a new osc command is received. I’ve already got my osc in chop setup

ChatGPT

To pulse the feedback whenever a new OSC command is received in TouchDesigner, you can use a Python script to monitor the OSC data and trigger the pulse. Here’s a step-by-step guide to achieve this:

1. Set Up OSC In CHOP:

   • Make sure your OSC In CHOP is configured correctly and receiving the OSC commands.

2. Add a CHOP Execute DAT:

   • Create a CHOP Execute DAT and connect it to your OSC In CHOP.
   • This DAT will execute a script whenever the values in the connected CHOP change.

3. Write the Python Script:

   • In the CHOP Execute DAT, write a script to pulse the feedback. Here’s an example script:

# This script will be executed every time the OSC data changes

def onValueChange(channel, sampleIndex, val, prev):
    feedback = op('feedback1')  # Replace 'feedback1' with the path to your feedback TOP
    feedback.par.pulse.pulse()
    return

def onOffToOn(channel, sampleIndex, val, prev):
    return

def whileOn(channel, sampleIndex, val, prev):
    return

def onOnToOff(channel, sampleIndex, val, prev):
    return

def whileOff(channel, sampleIndex, val, prev):
    return

In this script:

• onValueChange is triggered whenever the OSC value changes.
• The line feedback.par.pulse.pulse() sends a pulse to the feedback operator. Replace 'feedback1' with the correct path to your feedback operator.

4. Enable the CHOP Execute DAT:

   • Ensure the Active parameter of the CHOP Execute DAT is turned on.

5. Testing:

   • Send an OSC command and check if the feedback pulses as expected. You should see the feedback operator being pulsed whenever new OSC data is received.

By following these steps, you should be able to trigger a pulse for your feedback whenever a new OSC command is received in TouchDesigner. If you encounter any issues, ensure that the path to your feedback operator is correct and that the OSC data is correctly being received by the OSC In CHOP.

You

Traceback (most recent call last): File “/project1/EFFECT_4/chopexec1”, line 5, in onValueChange td.tdAttributeError: ‘td.ParCollection’ object has no attribute ‘pulse’ Context:/project1/EFFECT_4/feedback1

ChatGPT

The error indicates that the pulse attribute is not directly accessible on the parameter collection. You need to access the specific parameter that you want to pulse. Typically, the parameter you want to pulse is a custom or predefined parameter on the feedback TOP.

Here’s how you can fix it:

1. Identify the Parameter to Pulse:

   • You need to find the specific parameter that you want to pulse. In most cases, it could be a custom pulse parameter that you’ve added to the feedback TOP.

2. Modify the Script:

   • Access the specific pulse parameter directly and trigger it. Here is the updated script:

# This script will be executed every time the OSC data changes

def onValueChange(channel, sampleIndex, val, prev):
    feedback = op('feedback1')  # Replace 'feedback1' with the path to your feedback TOP
    feedback.par.reset.pulse()  # Replace 'reset' with the actual parameter you want to pulse
    return

def onOffToOn(channel, sampleIndex, val, prev):
    return

def whileOn(channel, sampleIndex, val, prev):
    return

def onOnToOff(channel, sampleIndex, val, prev):
    return

def whileOff(channel, sampleIndex, val, prev):
    return

In this script:

• feedback.par.reset.pulse() accesses the reset parameter on the feedback operator and pulses it. Replace reset with the name of the actual parameter you intend to pulse.

3. Finding the Correct Parameter:

   • If you are unsure which parameter to pulse, you can open the parameters dialog for the feedback TOP and look for the correct parameter. Commonly used pulse parameters in feedback setups include reset, reload, etc.

4. Testing:

   • After making the changes, send an OSC command to see if the feedback pulses as expected.

By ensuring that you are pulsing the correct parameter, the script should work without errors. If the problem persists, double-check the parameter name and ensure it matches exactly with what is defined in your feedback TOP.