1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
TODO list:
features:
---------------------
- introduce attributes!!
- introduce several log levels (for warning posts)
- grab (and recompose) signals for granular vasp usage
- vasp~s for realtime-capable vasp objects
- complex power operations - delta phase
- optimize (c)osc with table lookup, phasor with Höldrichs code (in pd)
- how to handle beyond buffer-domain:
warning, treat as 0, calculate unit operation, loop, mirror on buffer end, stay on last frame
- better algorithm for vasp.fix
- make loops interruptible ("stop" message?)
- make in place rotation more efficient (use temporary space)
- introduce "groups" for attribute organisation (e.g. detach etc.)
- reduce number of warnings for wrong offset, frame size etc.
objects:
---------------------
- wave object for table-lookup oscs.
- various random distributions for noise
- vasp.window: one should be able to use just a portion of the windowing envelope
- slope: frequency distortion with given exponent
- vasp.trigger object... in PD [t a] is ok, what about Max?
- vasp.expr
- vasp.state.... current vasp, operation, progress meter
- vasp.ahead (vasp.a): abstraction head - set/bang/to handling, radio outlet, attribute processing (?)
- vasp.print (vasp.p): print vasp messages
- vasp.resmp: resampling with vasp argument, instead of vasp.tilt (?)
bugs:
---------------------
tests:
---------------------
- in-place operation (src == dst), test if strides are equal!
- should frame count always be pre-evaluated (e.g. in vasp.f+ etc. ?)
- test DFT objects on strided buffers
- check for odd remainder frame on symmetric operations!!
premature thoughts:
---------------------
- interface to scripting language (python)
documentation:
---------------------
- have all the objects written in their full names
- no special characters!
|
