Collaborative Roadmap - Revision history

Admin at 10:44, 20 August 2016

2016-08-20T10:44:47Z

Admin at 10:43, 20 August 2016

2016-08-20T10:43:32Z

Admin at 10:42, 20 August 2016

2016-08-20T10:42:02Z

Admin at 12:07, 12 March 2011

2011-03-12T12:07:06Z

Admin at 17:27, 11 March 2011

2011-03-11T17:27:42Z

Admin at 16:54, 11 March 2011

2011-03-11T16:54:08Z

Admin at 16:53, 11 March 2011

2011-03-11T16:53:05Z

Admin at 16:36, 11 March 2011

2011-03-11T16:36:39Z

Admin at 16:19, 11 March 2011

2011-03-11T16:19:08Z

Admin at 16:14, 11 March 2011

2011-03-11T16:14:49Z

@@ Line 23: / Line 23: @@
 You can follow the state of the tasks in the [https://savannah.gnu.org/task/?group=psychosynth Savannah task tracker]. If you want something not in this list to be implemented you can also use Savannah or our [[community|user mailing list]].
-<div class="note" style="margin-top:15px;font-size:120%;">'''Update''' [https://flattr.com Flattr] is changing towards a different model which makes it unusable for building a collaborative roadmap. This website is left here to inform about ideas on how the project could evolve, but does not allow people to vote anymore. I'm sorry for that.</div>
+<div class="note" style="margin-top:15px;">'''Update:''' [https://flattr.com Flattr] is changing towards a different model which makes it unusable for building a collaborative roadmap. This website is left here to inform about ideas on how the project could evolve, but does not allow people to vote anymore. I'm sorry for that.</div>
 == I want to contribute with code ==

@@ Line 1: / Line 1: @@
 {{Languages}}
 == What is this? ==
@@ Line 24: / Line 22: @@
 You can follow the state of the tasks in the [https://savannah.gnu.org/task/?group=psychosynth Savannah task tracker]. If you want something not in this list to be implemented you can also use Savannah or our [[community|user mailing list]].
 == I want to contribute with code ==

@@ Line 1: / Line 1: @@
 {{Languages}}
 == What is this? ==
 The '''collaborative roadmap''' allows you to vote which features you want to see implemented sooner. We use the [http://www.flattr.com Flattr] micro-donation system such that the developer implementing that feature gets some aid from the people benefiting from his work. You can learn more about Flattr in this video:

@@ Line 35: / Line 35: @@
 Hierarchical patches would allow to have a notion of ''sub-table''. This is, a module in an upper level can be ''zoomed'' such that it has another synthesis network inside. This can be done recursively. The configuration of each of these pre-packed submodules should be storable such that they can be reused in later sessions. [https://savannah.gnu.org/task/index.php?10983 Status and discussion page]
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === Polyphonic patches ===
@@ Line 45: / Line 45: @@
 Polyphonic patches in combination with the previous feature &mdash; and specially interesting in combination with the MIDI feature below &mdash; would allow to have parts of the synthesis graph that can process different notes at the same time, for example, in response to simultaneously pressed keyboard keys. [https://savannah.gnu.org/task/index.php?10984 Status and discussion page]
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === Plug-in system ===
@@ Line 55: / Line 55: @@
 A plug-in system would allow third party developers to deploy their own synthesis modules independently. This plug-in system should support also the [http://www.ladspa.org/ LADSPA] and [http://lv2plug.in/ LV2] standards, thus being able to use the vast variety of DSP modules based on those standards that can be found on the internet and are distributed along with popular GNU/Linux systems. [https://savannah.gnu.org/task/index.php?10985 Status and discussion page].
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === Audio input ===
@@ Line 65: / Line 65: @@
 Audio input is essential to have real interaction with analog instruments. It would allow to plug in any analog signal from the soundcard or even any [http://jackaudio.org/ Jackd enabled] software, so you can process and add effects to your own voice or traditional instruments from within the Psychosynth environment. [https://savannah.gnu.org/task/index.php?10986 Status and discussion page].
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === BPM Synchronization ===
@@ Line 75: / Line 75: @@
 Currently Psychosynth has no notion of the beats-per-minute of the playing music and no way to synchronize the different manipulation and effects. This feature would allow to set the BPM's of the music &mdash; maybe even different BPM's for different part of the performance surface &mdash; and synchronize effects &mdash; like the frequency paramter of an LFO &mdash; and auto-quantize events &mdash; like waiting to play a loop until the next beat. [https://savannah.gnu.org/task/index.php?10987 Status and discussion page]
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === MIDI Support ===
@@ Line 85: / Line 85: @@
 MIDI is the standard for communicating among electronic music devices. Supporting MIDI would open the doors controlling Psychosynth with keyboards and a the huge range of MIDI controller hardware available on the market. [https://savannah.gnu.org/task/index.php?10988 Status and discussion page].
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === Multi-touch user interface ===
@@ Line 95: / Line 95: @@
 While the current user interface of Psychosynth is visually appealing and an interesting experiment, experience has revealed that 3D does not give much usability boost apart from the zooming ability. Moreover, the [http://www.cegui.org.uk/wiki/index.php/Main_Page CEGUI] library have proven a to be bug-full and a rewrite of the UI using maybe Qt would boost the development speed. New multi-touch devices are becoming very common and we even have a the [http://www.indamixx.com/ Indamixx] tablet which works with Free Software and is specially targeted at music production. This task specially needs economic aid because our team does not have any multi-touch hardware at the moment. [https://savannah.gnu.org/task/index.php?10989 Status and discussion page].
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === Tangible user interface ===
@@ Line 105: / Line 105: @@
 Using the [http://reactivision.sourceforge.net/ Reactivision] software we could develop an special user interface based on the [http://www.tuio.org/ TUIO protocol] that would allow users to easily build a home-made Reactable with a webcam. [https://savannah.gnu.org/task/index.php?10990 Status and discussion page].
-<html><div style="clear:left;margin: 0 10px 10px 0;"/></html>
+<html><div style="clear:left;"></div></html>
 === MacOSX port ===
@@ Line 116: / Line 116: @@
 [https://savannah.gnu.org/task/index.php?10991 Status and discussion page].
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === Windows Port ===
@@ Line 126: / Line 126: @@
 Also, most people out there are sadly using Microsoft Windows. Even though we would like them to go ahead and try a Free Operating system we could implement an ASIO based output system and deploy Windows binaries of Psychosynth such that the software is easily available to all those musicians. Porting Unix applications to Windows is painful, specially for a Free Software developer, so do not expect us to pick this task without economic aid. [https://savannah.gnu.org/task/index.php?10992 Status and discussion page].
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>
 === VST plugins ===
@@ Line 136: / Line 136: @@
 Even though our above proposed plug-in system is based on LADSPA and LV2, most DSP modules out there are based on the VST standard. Sadly, it is subject to patent issues and it is also a bit painful to get to work under GNU/Linux systems. Still, if many people Flattr it, we are still open to pushing it upwards in our roadmap. [https://savannah.gnu.org/task/index.php?10993 Status and discussion page]
-<html><div style="clear:left;"/></html>
+<html><div style="clear:left;"></div></html>

@@ Line 93: / Line 93: @@
 </div></html>
-Will the current user interface of Psychosynth is visually appealing and an interesting experiment, experience has revealed that 3D does not give much usability boost apart from the zooming ability. Moreover, the [http://www.cegui.org.uk/wiki/index.php/Main_Page CEGUI] library have proven a to be bug-full and a rewrite of the UI using maybe Qt would boost the development speed. New multi-touch devices are becoming very common and we even have a the [http://www.indamixx.com/ Indamixx] tablet which works with Free Software and is specially targeted at music production. This task specially needs economic aid because our team does not have any multi-touch hardware at the moment. [https://savannah.gnu.org/task/index.php?10989 Status and discussion page].
+While the current user interface of Psychosynth is visually appealing and an interesting experiment, experience has revealed that 3D does not give much usability boost apart from the zooming ability. Moreover, the [http://www.cegui.org.uk/wiki/index.php/Main_Page CEGUI] library have proven a to be bug-full and a rewrite of the UI using maybe Qt would boost the development speed. New multi-touch devices are becoming very common and we even have a the [http://www.indamixx.com/ Indamixx] tablet which works with Free Software and is specially targeted at music production. This task specially needs economic aid because our team does not have any multi-touch hardware at the moment. [https://savannah.gnu.org/task/index.php?10989 Status and discussion page].
 <html><div style="clear:left;"/></html>

@@ Line 33: / Line 33: @@
 </div></html>
-Hierarchical patches would allow to have a notion of '''sub-table'''. This is, a module in an upper level can be '''zoomed''' such that it has another synthesis network inside. This can be done recursively. The configuration of each of these pre-packed submodules should be storable such that they can be reused in later sessions. [Status and discussion page]
+Hierarchical patches would allow to have a notion of ''sub-table''. This is, a module in an upper level can be ''zoomed'' such that it has another synthesis network inside. This can be done recursively. The configuration of each of these pre-packed submodules should be storable such that they can be reused in later sessions. [Status and discussion page]
 <html><div style="clear:left;"/></html>
@@ Line 42: / Line 42: @@
 href="http://psychosynth.com/index.php/Collaborative_Roadmap#Polyphonic_patches"></a>
 </div></html>
 <html><div style="clear:left;"/></html>
@@ Line 50: / Line 52: @@
 href="http://psychosynth.com/index.php/Collaborative_Roadmap#Plug-in_system"></a>
 </div></html>
 <html><div style="clear:left;"/></html>
@@ Line 58: / Line 62: @@
 href="http://psychosynth.com/index.php/Collaborative_Roadmap#Audio_input"></a>
 </div></html>
 <html><div style="clear:left;"/></html>
@@ Line 66: / Line 72: @@
 href="http://psychosynth.com/index.php/Collaborative_Roadmap#BPM_Synchronization"></a>
 </div></html>
 <html><div style="clear:left;"/></html>