Ideas for version 3 » History » Version 23

Chris Cannam, 2017-01-11 11:13 AM

1 21 Chris Cannam
h1. Features for version 3
2 1 Chris Cannam
3 13 Chris Cannam
h2. Implemented
4 7 Chris Cannam
5 16 Chris Cannam
The following are already included in some branch or in some capacity, though the implementation is not necessarily complete.
6 1 Chris Cannam
7 22 Chris Cannam
h5. Audio recording
8 22 Chris Cannam
9 22 Chris Cannam
Live analysis may have to remain out of scope. But recording a clip (using a popup window to start/stop recording) and then analysing that should be quite feasible. Would be useful for apps such as Tony as well.
10 22 Chris Cannam
11 15 Chris Cannam
h5. Unit conversion utility
12 13 Chris Cannam
13 16 Chris Cannam
See #905. This is suitable to ship.
14 13 Chris Cannam
15 16 Chris Cannam
h5. Handle very long audio files
16 13 Chris Cannam
17 16 Chris Cannam
As requested e.g. "here":http://vamp-plugins.org/forum/index.php/topic,276.0.html. Around 30 hours at 44100Hz is a good starting point (exceeding 2^32 frames). This is mostly working in 64-bit builds but there are some associated problems still, such as #1284.
18 1 Chris Cannam
19 16 Chris Cannam
h5. True retina rendering on OS/X
20 1 Chris Cannam
21 16 Chris Cannam
Largely done, see #1158.
22 1 Chris Cannam
23 16 Chris Cannam
h5. Icon and widget overhaul
24 1 Chris Cannam
25 18 Chris Cannam
Scalable icons for high-resolution displays, etc. This is really a requirement for the true retina support. This work is started in the scalable-icons branch but there is still quite a bit to do.
26 16 Chris Cannam
27 16 Chris Cannam
h5. Multiplex audio input into plugins
28 16 Chris Cannam
29 16 Chris Cannam
Allowing plugins like MATCH that require separate audio files as inputs to be run and output displayed within SV. See #1108. This is essentially working but needs a number of fixes.
30 16 Chris Cannam
31 20 Chris Cannam
h5. Simpler FFT model
32 20 Chris Cannam
33 20 Chris Cannam
The existing FFT model code in SV is based on assumptions that are not always reliable, in particular that a machine has vastly more hard disc space than any other storage (which became unreliable when SSDs started appearing, though sizes are going back up again now) and that it's cheaper to store and recall transform outputs for large FFT sizes than it is to recompute them from the original audio (this is still just about true, but only just). Meanwhile the code to handle FFT cacheing is complex and problematic in many ways. There is now a branch @simple-fft-model@ which replaces it with only the bare minimum of cacheing and it works more predictably, though it may still need some work in the SpectrogramLayer code to make the results faster to render.
34 16 Chris Cannam
35 16 Chris Cannam
h5. Windows 64-bit build
36 16 Chris Cannam
37 16 Chris Cannam
Not much point in being able to open very long audio files in the 64-bit build, if the majority of SV users aren't getting the 64-bit build.
38 16 Chris Cannam
39 16 Chris Cannam
The blocker here is loading Vamp plugins, which are all 32-bit only on Windows at the moment (and some of the existing binaries will likely never be updated). So this has a dependency on being able to run 32-bit plugins from a 64-bit build, which probably means running the plugins in a separate process (though I've listed that as a separate item below because it isn't necessarily the only way to achieve this).
40 16 Chris Cannam
41 16 Chris Cannam
h5. Improve layer parameter box layout for OS/X
42 16 Chris Cannam
43 1 Chris Cannam
The layer parameters easily get very squashed on OS/X (and only there, I wonder why). This absolutely needs fixing. See #1304.
44 1 Chris Cannam
45 1 Chris Cannam
h5. Additional normalisations for colour 3d plot and spectrogram
46 16 Chris Cannam
47 1 Chris Cannam
The normalisation used in Tony is quite useful -- it exists on a branch (normalize_hybrid_option) in spectrogram only, but without any sensible UI. See also #147. Additionally recent default branch of SV has added a feature-derivative option to the colour 3d plot -- I actually think this was a mistake, at least to add a whole new button for it. That should either be backed out or replaced with better UI.
48 16 Chris Cannam
49 1 Chris Cannam
h5. Permit changing colour of overview widget waveform
50 1 Chris Cannam
51 1 Chris Cannam
Some chap who made a nice Youtube video about SV complained that he hated the green waveform colour in the overview. Anyone who goes to the trouble of making a nice video about SV deserves some small compensations. This is slightly trickier to work out where to fit into the UI than I'd originally thought though.
52 1 Chris Cannam
53 1 Chris Cannam
h5. Combo gain/pan widgets
54 1 Chris Cannam
55 23 Chris Cannam
As used in Tony, but with higher adjustable resolution. (Todo: they still don't actually have higher resolution)
56 1 Chris Cannam
57 1 Chris Cannam
h5. Run plugins in a separate process
58 1 Chris Cannam
59 1 Chris Cannam
For reliability, and to allow e.g. Win64 build to run Win32 plugins
60 1 Chris Cannam
61 23 Chris Cannam
h5. SVG export
62 23 Chris Cannam
63 23 Chris Cannam
Has been requested several times, but see e.g. "SF feature request 146":http://sourceforge.net/p/sv1/feature-requests/146/.
64 23 Chris Cannam
65 23 Chris Cannam
h2. Desired
66 23 Chris Cannam
67 23 Chris Cannam
These are features I am hoping to get into the release, but haven't implemented yet.
68 23 Chris Cannam
69 23 Chris Cannam
h5. Colourblind-safe default colour scheme for spectrogram and colour 3d plot
70 23 Chris Cannam
71 23 Chris Cannam
[I did add a new colour scheme, but I haven't (yet?) changed the default.]
72 23 Chris Cannam
73 23 Chris Cannam
The green-red default scheme is about as bad as it gets for colourblind viewers. I wince every time I see a poster or presentation that uses screengrabs from it.
74 23 Chris Cannam
75 23 Chris Cannam
h5. Multi-feature editing
76 23 Chris Cannam
77 23 Chris Cannam
See #209.
78 23 Chris Cannam
79 13 Chris Cannam
h2. Other
80 1 Chris Cannam
81 19 Chris Cannam
Things that have been added to this list at some point but that are currently not planned for inclusion.
82 13 Chris Cannam
83 16 Chris Cannam
h5. Sub-sample zoom
84 4 Chris Cannam
85 13 Chris Cannam
Currently SV limits the max zoom level to 1 pixel per sample: you can't zoom in to sub-sample resolutions. Might be nice if you could. (Of course the sub-sample display would need to be accurate, i.e. oversampled.) There are rather a lot of assumptions about integer zoom levels in the code so this would take a bit of care.
86 1 Chris Cannam
87 16 Chris Cannam
I'd definitely like to do this, but probably not for the next major release.
88 1 Chris Cannam
89 16 Chris Cannam
h5. Score display
90 16 Chris Cannam
91 13 Chris Cannam
Either or both of: page-by-page PDF rendering along the lines of the Image layer; proper score rendering from a symbolic format.
92 13 Chris Cannam
93 16 Chris Cannam
h5. Collapsible quick-view strips
94 13 Chris Cannam
95 4 Chris Cannam
See #25. Tony's selection strip might give some idea of how this could look.
96 5 Chris Cannam
97 16 Chris Cannam
h5. SV Mini Edition (and Tablet Editions?)
98 5 Chris Cannam
99 16 Chris Cannam
See "SV Mini project":/projects/sv-mini.
100 9 Chris Cannam
101 16 Chris Cannam
h5. Integrate IMAF support
102 11 Chris Cannam
103 16 Chris Cannam
The "IMAF build":/projects/sv-imaf-enc is still a separate project and branch; what's the best way to merge it?
104 12 Chris Cannam
105 16 Chris Cannam
h2. Unknown status
106 11 Chris Cannam
107 16 Chris Cannam
h5. Bundle some plugins
108 16 Chris Cannam
109 16 Chris Cannam
See "SF feature request 151":http://sourceforge.net/p/sv1/feature-requests/151/. Bundling at least MATCH, VamPy, and the QM plugins would be a great help.