![]() timecode member that report the timecode of the data in that operator in various formats and units. Numerous operators (see below) that deal with time in various ways have a. These objects are built into some operators, or can be created as their own entities in python. Timecode in TouchDesigner is represented in a tdu.Timecode object (see Timecode_Class). In TouchDesigner we try to represent time everywhere possible as timecode, though the fundamental time units are expressed as frames on the timeline, and in seconds or frames in Absolute Time. ![]() The prevalent standard for timecode, SMPTE Timecode, was originally designed for video tape machines, tapes and broadcast transmissions. It can be expressed in a string, for example 03:22:11:10, or as a bit pattern, as in LTC timecode embedded in audio streams. Likely will use libltc and the I2S API provided by esp-idf.Timecode is a way of expressing time as a combination of hours, minutes, seconds, and frames. But I'm a software guy so would need to have someone design a board. I'm thinking eventually this would run on an ESP32 board with a LiPo battery, a stereo mic/line-in jack (useful for receiving LTC, or for passing audio through), a stereo headphone jack, and a micro-USB plug. Stretch - Wireless communication between LuToCs and other devices to ensure time remains synced. Stretch - Sync with phones or other devices over WiFi/Bluetooth. Stretch - Establish/maintain sync via GPS receiver. Stretch - Sync between LuToC devices via Wifi or Bluetooth. Stretch - Establish time with computer over WiFi, Bluetooth. Required - Establish time on LuToC devices via sync with a computer over USB.Stretch - Status reported via audio indicators using built-in speaker. Stretch - LCD/OLED screen with graphical UI. Stretch - LCD/OLED screen with text display. Required - LED indicators showing battery level, current run status (whether LTC is being generated.) Required - A way to indicate that multiple LuToC's are synchronized.Stretch - Screen/button "hold" to prevent accidental presses. Stretch - Configuration via on-device buttons/touchscreen. Stretch - Configuration of the LTC time and signal format (frame rate) from a web UI via WiFi "hotspot" mode. Required - (Re)configuration of device over USB via desktop application.Required - LTC time generation with very low drift (over a day's project cannot drift more than 1/30s), Stretch - Less than one frame drift over one month.Stretch - Multiple power modes (high-power, medium-power, low-power, sleep. Stretch - Accurate battery remaining computation. Stretch - Automatic re-establishment of sync after power restored. Required - Long battery life (12 hours).Stretch - Power-on time of less than 1 second. Required - Power-on time of less than 20 seconds.Stretch - Battery charging on-board from USB power source. Stretch - Multiple batteries, with automatic failover. Stretch - Battery-powered via AA batteries. Stretch - Battery-powered via camera-style battery. Stretch - Battery-powered operation via LiPo. Required - Battery-powered operation via USB power. ![]() Stretch - Built-in mic and speaker for for LTC sync "over the air" and audio alerts. (Encode onto a high carrier frequency?) Stretch - Sense whether LuToC output is connected, only generate LTC when connected, sleep after a period of time of no connection. ![]() Stretch - Support LTC "overlaid" over an audio signal, preferably with LTC encoded so that it can be filtered out and the original audio signal restored. Stretch - Support additional, non-standard, LTC types (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |