PDCON:Workshops/DIY electronic music using Visual Tracker: Difference between revisions
From Medien Wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== VisualTracker and pdLive – Music Creation Workshop === | |||
VisualTracker and pdLive – Music | |||
Creation Workshop | |||
VisualTracker is a prototype of modular time based pd environment exploring the possibilities of | VisualTracker is a prototype of modular time based pd environment exploring the possibilities of | ||
sharing data and functionalities across dynamically created external patches (abstractions). The | sharing data and functionalities across dynamically created external patches (abstractions). The | ||
| Line 9: | Line 7: | ||
that process. VisualTracker will lean on the strenghts of pd to evolve, its community, its | that process. VisualTracker will lean on the strenghts of pd to evolve, its community, its | ||
modularity and its connectivity to other softwares. | modularity and its connectivity to other softwares. | ||
Main part of VisualTracker is linear sequencer which triggers events i.e. basic time based | Main part of VisualTracker is linear sequencer which triggers events i.e. basic time based | ||
objects such as [bang], [toggle], [line] or even complex patches such as audio or video players | objects such as [bang], [toggle], [line] or even complex patches such as audio or video players | ||
built as structured abstractions independent from main program (modules). | built as structured abstractions independent from main program (modules). | ||
Each module can be loaded into VisualTracker in (theoretically) infinite number of instances and | Each module can be loaded into VisualTracker in (theoretically) infinite number of instances and | ||
each instance is handled as independent program (e.g. each sample player can play different | each instance is handled as independent program (e.g. each sample player can play different | ||
| Line 17: | Line 18: | ||
delivers essential VisualTracker features such as event duration changes, looping, time | delivers essential VisualTracker features such as event duration changes, looping, time | ||
stretching, fit in tempo or output management according module placement on “VisualTracker | stretching, fit in tempo or output management according module placement on “VisualTracker | ||
Timeline”. | Timeline”. | ||
Once module instance is loaded into VisualTracker, “connector abstraction” automatically | Once module instance is loaded into VisualTracker, “connector abstraction” automatically | ||
creates its graphical representation ([cnv]) and places it on GUI timeline divided vertically to | creates its graphical representation ([cnv]) and places it on GUI timeline divided vertically to | ||
| Line 25: | Line 28: | ||
canvases (representations) are of course “time sensitive” i.e. duration of module event has its | canvases (representations) are of course “time sensitive” i.e. duration of module event has its | ||
interpretation in size of canvas. | interpretation in size of canvas. | ||
Another essential feature of VisualTracker is fully integrated storage system which allows to | Another essential feature of VisualTracker is fully integrated storage system which allows to | ||
save main program state (such as BPM, track names and outputs) together with all loaded | save main program state (such as BPM, track names and outputs) together with all loaded | ||
modules including their position on timeline and current module instance values into external | modules including their position on timeline and current module instance values into external | ||
text file and load them back (recreate whole composition) | text file and load them back (recreate whole composition) | ||
For now there are only a few modules available : | For now there are only a few modules available : | ||
* a bang module, that will output a bang at the time it’s placed. | |||
* a toggle module, which turns a toggle on at the start of the event and off at the end. It features time stretching possibilities to fit a predefined number of bars for instance. | |||
time stretching possibilities to fit a predefined number of bars for instance. | * a line module, which will count from zero to a defined value. | ||
* an audio-track module, which will load a soundfile and play it back at original tempo or fitted into VisualTracker timeline. | |||
into VisualTracker timeline. | |||
These modules already allow a great deal of possible use, but VisualTracker also aims at | These modules already allow a great deal of possible use, but VisualTracker also aims at | ||
developping instrument-modules with sequencing and dsp possibilities, such as a piano roll | developping instrument-modules with sequencing and dsp possibilities, such as a piano roll | ||
controlling an FM synth. For this purpose we will rely on the pdlive project | controlling an FM synth. For this purpose we will rely on the pdlive project | ||
( | (http://code.google.com/p/pdlive/) which is a big collection of patches found on the web and port | ||
patches proven to be efficient and easy to use to release a comprehensive and extensive set of | patches proven to be efficient and easy to use to release a comprehensive and extensive set of | ||
tools to compose and produce sound for VisuaTracker. | tools to compose and produce sound for VisuaTracker. | ||
VisualTracker is regularly developed and tested for more than a year (after several ALPHA | VisualTracker is regularly developed and tested for more than a year (after several ALPHA | ||
versions comes already into BETA phase) with the idea of cooperation and open source | versions comes already into BETA phase) with the idea of cooperation and open source | ||
| Line 65: | Line 61: | ||
source and 100% readable environment of pd they can be really explored and used the way | source and 100% readable environment of pd they can be really explored and used the way | ||
they were never used before. | they were never used before. | ||
In this way we would like to suggest a worksop activity leaning towards music creation for any | In this way we would like to suggest a worksop activity leaning towards music creation for any | ||
level of experience with pd (from complete new-commers to experienced users). This workshop | level of experience with pd (from complete new-commers to experienced users). This workshop | ||
| Line 70: | Line 68: | ||
album of pd-music freely available on the web (as patches, and as audio tracks) to promote our | album of pd-music freely available on the web (as patches, and as audio tracks) to promote our | ||
development and it may also lead to the release of a pack of new modules. | development and it may also lead to the release of a pack of new modules. | ||
Until the time of the convention, we will focus on developping a few more modules, and we will | Until the time of the convention, we will focus on developping a few more modules, and we will | ||
be releasing a demo track featuring VisualTracker as a composition tool, as an example. The | be releasing a demo track featuring VisualTracker as a composition tool, as an example. The | ||
future paper will present key points of VisualTracker as presented in this draft and a discussion | future paper will present key points of VisualTracker as presented in this draft and a discussion | ||
on the composition features based on the demo track case study. | on the composition features based on the demo track case study. | ||
Complete documentation, screenshots and download : http | |||
Complete documentation, screenshots and download : http://code.google.com/p/visualtracker | |||