\[zerox~\]
If you plan on using [xerox~] to phase sync two oscillators, it probably won't cut it. Generally, you want those things to be sample accurate. [xerox~] will give you a click corresponding to zero crossings out its right outlet, but, as far as I know at least, Pd's oscillators can't really use that for phase syncing ([xerox~] is actually based on a Max object, yet strangely Max's oscillators can't use it either). It would require a conversion to message rate to reset the phase, which kills sample accuracy, not to mention the fact that the phase input of [phasor~] quantizes to block boundaries (default 64 samples in Pd), which also kills sample accuracy.
However, if you know the ratio between your two oscillators, phase syncing can be achieved using a master [phasor~] to run both oscillators. Use the master sync frequency to drive the [phasor~], then multiply the output of the [phasor~] by the ratio between the synced (slave) oscillator and the master one. In other words, it should be multiplied by:
slave frequency / master frequency
Then, you just [wrap~] the signal and viola, you have a new synced phasor signal to drive the slave oscillator. The attached patch should hopefully clarify.
Sound appear and disapear!!
Hello I installed Pd, jackd and Alsa via apt-get i have debian 5.0(lenny)
Sometimes the sound works, when work it appear an error message:
audio I/O error history:
seconds ago error type
0.14 A/D/A sync
1.00 unknown
1.52 A/D/A sync
5.76 unknown
5.76 unknown
tried but couldn't sync A/D/A
audio I/O error history:
seconds ago error type
1.40 A/D/A sync
3.38 A/D/A sync
3.69 A/D/A sync
7.12 A/D/A sync
when don't works appear this:
couldn't open MIDI input device 0
couldn't open MIDI output device 0
opened 0 MIDI input device(s) and 0 MIDI output device(s).
audio I/O error history:
seconds ago error type
4.69 unknown
4.69 unknown
thnx
L'oeuvre ouverte|PureData Convention '07 - Call for Proposals
[VERSION FRANÇAISE CI-DESSOUS]
* August 21st-26th, 2007, Montréal Canada
* Deadline for artworks/performances and workshops: February 28th 2007
* Deadline for papers: March 31st 2007
http://convention.puredata.org
The PureData Convention Steering Committee is now accepting proposals
for participation in L'oeuvre ouverte (the Open Work), the 2nd
International PureData Convention. L'oeuvre ouverte invites an open
relation between the artwork and the public as well as open attitudes
and practices in the fields of programming, artistic creation and
scientific research. It will bring together artists, developers and
writers who develop, use and reflect on PureData.
The Convention will acknowledge the broad range of artistic and
technical disciplines that make use of the software and will address
questions of openness and accessibility. It will provide a theoretical
and artistic context for the understanding of the aesthetics and
politics of Free / Open Source Software culture.
Selected proposals will reflect varied perspectives and outlooks on
the artistic possibilities of free software and hardware that emanate
from a wide-ranging community. These include, but are not restricted
to connections to art, science and society as well as demonstration of
innovative and intuitive interactions. We encourage a wide range of
submissions from all levels of proficiency with the software as well
as from emergent and diverse PureData communities. Submissions will be
evaluated by peer review committees.
Proposals are sought in the following categories:
Artwork/Performances:
The selected artworks should make use of PureData. All forms of audio
and visual art including real-time interactive works, improvisations
with technology, instrumental/electroacoustic mixes, sound
installations, performances, network art, robotics, software art and
interdisciplinary work are welcome.
Papers and posters:
We are accepting papers that offer varying perspectives on technical,
social, cultural as well as art theory/historical aspects of PureData
or the aesthetics and politics of Free / Open Source Software (FOSS)
culture.
Demos:
Externals, Performance patches, Packages of abstractions, sensors and
physical computing interfaces, etc.
Workshops:
Beginner to advanced level hands-on workshops, installation
help, DIY etc.
::applicants are invited to submit in multiple categories::
please read the application guidelines:
http://convention.puredata.org/guidelines
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
L'oeuvre ouverte|Congrès PureData 2007 - Appel de propositions
* Du 21 au 26 août 2007, Montréal, Canada
* Appel à participation -- Jusqu'au 28 février pour les projets
artistiques et les ateliers, le 31 mars pour les exposés.
http://convention.puredata.org/convention07-fr
Le comité organisateur du Congrès de PureData accepte maintenant les
propositions en vue de participer à L'oeuvre ouverte, 2e Congrès
international de PureData. L'oeuvre ouverte propose une relation
d'ouverture entre l'oeuvre d'art et le public et encourage les
attitudes et les pratiques ouvertes dans les domaines de la
programmation, de la création artistique et de la recherché
scientifique. Le congrès réunira artistes, développeurs et théoriciens
qui sont les créateurs de PureData, qui exploitent le logiciel ou en
font l'objet de leur réflexion.
Le Congrès témoignera de toute la gamme des disciplines artistiques et
techniques qui exploitent le logiciel libre et s'intéressera aux
questions d'ouverture et d'accessibilité. Il servira de cadre
théorique et artistique pour la compréhension des aspects esthétiques
et politiques propres à la culture du logiciel libre.
Les propositions retenues refléteront les nombreuses perspectives que
le logiciel libre et ses applications, émanant d'une collectivité
diversifiée, offrent en matière de possibilités artistiques, qu'il
s'agisse, notamment, de jonctions établies entre l'art, la science et
la société ou de la présentation d'interactions innovatrices et
intuitives. Les propositions les plus diverses sont les bienvenues,
peu importe le degré de compétence de l'auteur à l'égard du logiciel.
L'invitation est lancée, entre autres, aux collectifs de PureData en
émergence. Les propositions seront évaluées par des comités de pairs.
Les propositions doivent se situer dans les catégories suivantes:
Oeuvres d'art/installations:
les œuvres de toute nature, produites à l'aide de PureData, soit toute
forme d'art audio et visuel, y compris les œuvres interactives en
temps réel, les improvisations technologiques, les pièces
instrumentales et électroacoustiques, les installations sonores, les
performances, l'art robotique et télématique et les œuvres
multidisciplinaires.
Exposés et affiche:
communications apportant diverses perspectives sur les aspects
techniques, sociaux, culturels, l'histoire de l'art de PureData, de
même que sur les aspects esthétiques et politiques de la culture du
logiciel libre.
Démonstrations:
périphériques, outils de performance, extras, senseurs et interfaces, etc.
Ateliers:
travaux pratiques de niveau débutant à avancé, aide aux
installations, activités manuelles, etc.
SVP lisez les lignes directrices:
http://convention.puredata.org/guidelines-fr
::Les intéressés sont invités à faire des propositions de nature multiple::
\[newbie question\] sine wave noise, A/D/A sync erro
Hi,
I'm just getting started with Pd on Fedora Core 3; installation was pretty painless thanks to the CCRMA repositories, but I've run into an issue when I first tried to make some sounds with Pd. I recreated Miller Puckette's example of a constant amplitude scaler. When I start the audio, the signal seems to take a few seconds to 'settle' into a constant frequency; I get a few seconds of static that eventually turns into the sine wave I was expecting. When I click the DIO errors button, I get a bunch of A/D/A sync errors, as follows:
audio I/O error history:
seconds ago error type
0.73 A/D/A sync
0.73 A/D/A sync
0.75 A/D/A sync
0.94 A/D/A sync
0.94 A/D/A sync
0.95 A/D/A sync
1.01 A/D/A sync
1.01 A/D/A sync
1.10 A/D/A sync
1.10 A/D/A sync
1.11 A/D/A sync
1.11 A/D/A sync
1.17 A/D/A sync
1.17 A/D/A sync
1.17 A/D/A sync
1.17 A/D/A sync
1.27 A/D/A sync
1.31 A/D/A sync
1.31 A/D/A sync
1.36 A/D/A sync
If I let the steady sine wave tone continue, eventually there's a bit of a 'hiccup' in the sound, and then I get the following errors:
audio I/O error history:
seconds ago error type
1.25 DAC blocked
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
Can anyone help me out in diagnosing this problem and fixing it? Where should I start looking to fix this?
Thanks!