Point File In TOP

Summary

The Point File In TOP loads 3D point data into TOPs from either a single file or a sequence of files. Points are composed of one or more floating point values such as XYZ positions, RGB color values, 3D normals, scanner intensity, etc. The Point File in TOP will load all available point data, but only four channels can be placed into the output image. By default, the first four point data channels are placed into the red, green, blue and alpha channels respectively; however, you can assign any point channel to a colour channel using the parameters on the Point Data page. Attach a Point File Select TOP to create additional output images from the same source file.

The Point File In TOP will read point data from various mesh and floating point data files including: .obj, .ply, .fits (astronomy format), and .exr. It can also load ASCII point files (.xyz, .pts, .csv, .txt, etc) with one point per line and comma or space separated fields. The first line in ASCII point files can either be the number of points, the names of the point fields or the first point in the file.

For a complete list, see File Types. The OpenEXR file format is generally best to use as it is binary, can be read in multi-frame file sequences that uses TouchDesigner's movie file pre-reading and buffering, and can be written from TouchDesigner's Movie File Out TOP with unlimited numbers of channels.

Examine the state of a Point File In TOP by attaching an Info CHOP. This will show information like the number of points, fields per point and the number of frames. It also shows dynamic information like the file open status, current frame, readahead frames and queue size, dropped frame count, CPU decode time and GPU upload time.

Headers: If the file contains any additional header data, this can be viewed by attaching an Info DAT. Header data is stored as key-value pairs with the keys in the first column and the corresponding data in the second column, which can easily be interpreted with python.

All of the ASCII point list formats are loaded the same way whether their extention is txt, csv, xyz, etc. The parser looks for the first separating character (comma, space or tab) and then uses that to delimit the rest of the file. It will ignore delimiters that are inside single or double quotes. There are a few special rules depending on the delimiter style e.g. multiple spaces are merged together, but a comma at the end of a line indicates a blank field afterwards. Once a delimiter is established, The first line can be the number of points, but it is ignored. If the next line are strings then it is treated as a row of headers (channel names). Each row after that is considered a point.

See also OpenEXR.

pointfileinTOP_Class

Parameters - Point Data Page

Control how the point's field data is placed into the output image.

The custom toggles control whether to use a custom field name to select which field is placed in the corresponding color channel. If false, the fields are selected in order e.g. the first field goes in red, the second in green, etc.

When set to custom, you can select the field from the dropdown menu or enter it directly. This parameter will be disabled if the color channel is not available in the output image format (see Pixel Format parameter).

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
  <Settings>
      <attributes fps="30.0" />
  </Settings>

Parameters - Play Page

Parameters - Trim Page

Parameters - Tune Page

Parameters - Common Page

Info CHOP Channels

Extra Information for the Point File In TOP can be accessed via an Info CHOP.

Specific Point File In TOP Info Channels

• num_points -

• num_loaded_points -

• num_src_points -

• num_channels -

• index -

• true_index -

• index_fraction -

• file_resx -

• file_resy -

• start -

• length -

• sample_rate -

• last_index_uploaded -

• mv_has_audio -

• preloading -

• odd_field -

• last_frame -

• loop_frame -

• pre_read_misses -

• last_pre_read_miss_wait -

• hard_drive_timeouts -

• num_pre_read_frames -

• first_index_to_read -

• last_frame_hd_read_time -

• last_frame_decode_time -

• last_gpu_upload_time -

• open -

• opening -

• open_failed -

• fully_pre_read -

• true_length -

• hardware_yuv_to_rgb -

• has_non_av_track -

• pre_read_fails -

• disk_read_mbit_rate -

• has_decode_errors -

• num_decode_chunks -

• hardware_decode -

Common TOP Info Channels

• resx - Horizontal resolution of the TOP in pixels.

• resy - Vertical resolution of the TOP in pixels.

• aspectx - Horizontal aspect of the TOP.

• aspecty - Vertical aspect of the TOP.

• depth - Depth of 2D or 3D array if this TOP contains a 2D or 3D texture array.

• gpu_memory_used - Total amount of texture memory used by this TOP.

Common Operator Info Channels

• total_cooks - Number of times the operator has cooked since the process started.

• cook_time - Duration of the last cook in milliseconds.

• cook_frame - Frame number when this operator was last cooked relative to the component timeline.

• cook_abs_frame - Frame number when this operator was last cooked relative to the absolute time.

• cook_start_time - Time in milliseconds at which the operator started cooking in the frame it was cooked.

• cook_end_time - Time in milliseconds at which the operator finished cooking in the frame it was cooked.

• cooked_this_frame - 1 if operator was cooked this frame.

• warnings - Number of warnings in this operator if any.

• errors - Number of errors in this operator if any.

TouchDesigner Build: Latest\nwikieditorwikieditor2021.100002020.20000before 2020.20000