Skip to content

Blueprints and named channels instead of channels numbers #166

Description

@linzuzeng

Currently VI uses channels numbers, making it hard to be shared across recipes.
The proposed change is to use named channels within each VI, and add a blueprint (a graphical node editor like the one in Blender, that bidirectionally sync with text) to connect them.

The real instrument like haydraharp should go into blueprint instead of staying at virtual instrument.

CONNECT(vi_name2, chn1, vi_name2, chn2)
# a new thiny for connect

RFILE(hydraharp, chn1)

the channel number will be automatically assigned for all named channels, but manually assign should also be supported for backward compatibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions