tuxmain/HexoDSP
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

CV -> Ctrl rename

Browse source
This commit is contained in:
Weird Constructor 2021-08-31 05:00:27 +02:00
parent 8fa9ce35e9
commit 425caaf654
3 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
src/dsp/mod.rs
View file

@ -332,7 +332,7 @@ pub enum UICategory {
Mod,
NtoM,
Signal,
CV,
Ctrl,
IOUtil,
}
@ -726,14 +726,14 @@ macro_rules! node_list {
(12 in_9 n_id d_id r_id f_def stp_d -1.0, 1.0, 0.0)
{13 0 in_cnt setting(3) fa_mux9_in_cnt 0 8}
[0 sig],
smap => SMap UIType::Generic UICategory::CV
smap => SMap UIType::Generic UICategory::Ctrl
(0 inp n_id d_id r_id f_def stp_d -1.0, 1.0, 0.0)
(1 min n_id d_id r_s f_def stp_d -1.0, 1.0, -1.0)
(2 max n_id d_id r_s f_def stp_d -1.0, 1.0, 1.0)
{3 1 mode setting(0) fa_smap_mode 0 3}
{4 0 clip setting(0) fa_smap_clip 0 1}
[0 sig],
map => Map UIType::Generic UICategory::CV
map => Map UIType::Generic UICategory::Ctrl
(0 inp n_id d_id r_id f_def stp_d -1.0, 1.0, 0.0)
(1 atv n_id d_id r_id f_def stp_d -1.0, 1.0, 1.0)
(2 offs n_id d_id r_s f_def stp_d -1.0, 1.0, 0.0)
@ -743,13 +743,13 @@ macro_rules! node_list {
(6 max n_id d_id r_s f_def stp_d -1.0, 1.0, 1.0)
{7 0 clip setting(0) fa_map_clip 0 1}
[0 sig],
quant => Quant UIType::Generic UICategory::CV
quant => Quant UIType::Generic UICategory::Ctrl
(0 freq n_pit d_pit r_id f_freq stp_d -1.0, 0.5647131, 440.0)
(1 oct n_id d_id r_s f_def stp_d -1.0, 1.0, 0.0)
{2 0 keys setting(0) fa_quant 0 0}
[0 sig]
[1 t],
cqnt => CQnt UIType::Generic UICategory::CV
cqnt => CQnt UIType::Generic UICategory::Ctrl
(0 inp n_id d_id r_id f_def stp_d 0.0, 1.0, 0.0)
(1 oct n_id d_id r_s f_def stp_d -1.0, 1.0, 0.0)
{2 0 keys setting(0) fa_cqnt 0 0}
@ -1901,11 +1901,11 @@ impl Node {
/// There is usually no reason to use these, because any parameter can be
/// overridden by assigning an output port to the corresponding input.
/// This is provided for the rare case that you still want to use the
/// value the user set in the interface, and not the input CV signal.
/// value the user set in the interface, and not the input Ctrl signal.
/// * `inputs`: For each `params` parameter there is a input port.
/// This slice will contain either a buffer from `params` or some output
/// buffer from some other (previously executed) [Node]s output.
/// * `outputs`: The output buffers this node will write it's signal/CV
/// * `outputs`: The output buffers this node will write it's signal/Ctrl
/// results to.
/// * `led`: Contains the feedback [LedPhaseVals], which are used
/// to communicate the current value (set once per `process()` call, usually at the end)

2
src/dsp/node_sampl.rs
View file

@ -116,7 +116,7 @@ It can be used for purposes like:
* Adding ambient samples to your patches.
* Using drum samples (set 'pmode' to 'OneShot').
* Having an oscillator with a custom waveform (set 'pmode' to 'Loop').
* As custom CV source for very long or very custom envelopes.
* As custom control signal source for very long or very custom envelopes.
Only a single audio sample can be loaded into this player. In HexoSynth
the sample selection can be done by the file browser in the right panel

8
src/dsp/node_tseq.rs
View file

@ -96,7 +96,7 @@ impl TSeq {
"Tracker (based) Sequencer\n\n\
This node implements a sequencer that can be programmed \
using the tracker interface in HexoSynth on the right.\n\
It provides 6 CV signal and 6 gate outputs.";
It provides 6 control signals and 6 gate outputs.";
pub const HELP : &'static str =
r#"Tracker (based) Sequencer
@ -117,13 +117,13 @@ This tracker provides 6 columns that each can have one of the following
types:
- Note column: for specifying pitches.
- Step column: for specifying non interpolated CV signals.
- Value column: for specifying linearly interpolated CV signals.
- Step column: for specifying non interpolated control signals.
- Value column: for specifying linearly interpolated control signals.
- Gate column: for specifying gates, with probability and ratcheting.
Step, value and gate cells can be set to 4096 (0xFFF) different values
or contain nothing at all. For step and value columns these values
are mapped to the 0.0-1.0 CV signal range, with 0xFFF being 1.0
are mapped to the 0.0-1.0 control signal range, with 0xFFF being 1.0
and 0x000 being 0.0.
Value examples: 1.0 0.9 0.75 0.5 0.25 0.1