New piece. Mostly in Pd.

http://snd.sc/lf6Ijb

Synopsis;

"Axon" is a collaborative project that began life as a series of recorded guitar improvisations. These initial recordings provide the main source materials used in the fixed media element of the piece. Throughout the creative process the guitar and tape have been involved in a continual loop of mutual influence. Due to this working method we discovered that the line between the the composer and the performer became continually blurred and resulted in what we believe to be a truly collaborative piece that follows a combined creative vision. "Axon" was written by Michael Andrews and Ricky Graham.

Thoughts (+ feelings) welcome,

Ricky

what's the best way of preventing glitch artefacts when triggering a sample from a vline~ object multiple times in rapid succession?

For example, if a metro~ object is being used to trigger the vline~, which in turn is playing a sample from a tabread~ object, the length of the vline~ can be set to match the metro speed so that the amplitude drops to zero before the next trigger, thus avoiding any nasty glitch.

However, if the metro~ is accelerating the length of the vline~ will be slightly longer than the elapsed time between one metro~ trigger and the next, since the length of vline~ can only be set before it's triggered, not during playback. Hence the tail of one vline~ will overlap with the start of the next, resulting in an audible step.

I have played about with adding a short fade out upon each trigger and delaying the start of vline~, but this seems cumbersome and doesn't work when you get to very high flamming speeds.

I'm thinking about using multiple vline~'s and tabread~'s, and distributing the metro~ bangs between them consecutively, to allow the vline~ from one trigger (bang) to complete its cycle before it gets banged again.

But if there is a way to prevent level discontinuities (glitches) while using a single vline~/tabread~ set up, I'd love to hear it!!

Hey
I'm using phasor for an index to a tabread~ to play a sample.
I'm also using line~ as an envelope to control audio output.

The timing for the envelope is set by the size of the sample size and samplerate~ as well as the frequency for the phasor~.

The magnitude of the phasor is adjusted to the sample size.

The sample player can be re-triggered and when this happens a line~ is set to go to 0 in 5ms,
a delay is set for 5ms,
then bangs another line~ to go to velocity in 0,
as well as setting phasor~ frequency to 1/t and phase to zero.

At which time another delay is setup at samplelength in ms.

After the sample is played the phasor~ frequency is set to 0 then
another line~ to 0 in 5ms is sent to the [*~] .

This causes a glitch when the sample is retriggered because the phasor~ is reset to zero and starts replaying the sample.

This glitch can not be heard when the sample is not re-triggered so maybe it's a control vs signal timing issue.

I did hear the glitch at the end of the sample re-triggered or not using vline~.

So my question is how do you do audio rate envelope triggering of envelopes ? I would post the patch but it is a mess. A good answer or pointer to some reference material would be greatly appreciated. I haven't quite wrapped my head around the sample and hold sampler examples yet.

I'm attmpeting to create a patch to do some glitching. As part of my university work I've already attempted

sver3 has been very helpful in at least telling me his methods but I'm having trouble replicating it. I've created a patch that follows his explanation but using my computer (running an ATI Radeon 4500 card) I get no glitching.

Is anyone else able to test this?

http://www.pdpatchrepo.info/hurleur/glitchpatch.pd

Hi everyone,

I'm having an issue with audio output in PD : when setting audio to output via portaudio, all the audio that gets out of PD has audio glitch in it, some kind of random-spaced crackles or clicks. It is completly useless as such. Increasing the delay in PD's audio settings doesn't change a thing.
However, using Jack as an audio outlet supresses all this problem, and the audio is clean that way.

Would anyone know the reason for this? I would be glad to know it as there may be a link with another issue about audio on my hardware : system audio of mac os X has the same kind of glitches that I got with PD on portaudio, only it's only occasional glitches so it's bearable. Solving this issue would be a big relief to me.

My hardware is a hackintosh (pc with osX installed on it), and mbox2 as audio interface (but I have tested with an m-audio transit and I have the same crackling issue). My soft is osX Snow Leopard 10.6.5.

Any help appreciated!

Today is the official release of Infinite Glitch, an online based artwork that was created using, among other things, Pd-extended and PdGst. Thanks so much to everyone who has helped with the development of these great tools!

You can read through the description below or jump straight to the project page: http://infiniteglitch.com

--

Every day an incomprehensible number of new digital media files are uploaded to hosting sites across the internet. Far too many for any one person to consume. Infinite Glitch is a stream-of-conciousness representation of this overwhelming flood of media, its fractured and degraded sounds and images reflecting how little we as an audience are able to retain from this daily barrage.

Infinite Glitch is an automated system that generates an ever-changing audio/video stream from the constantly increasing mass of media files freely available on the web. Source audio and video files are ripped from a variety of popular media hosting sites, torn apart, and recombined using collage and glitch techniques to create an organic, chaotic flood of sensory input.

Ben Baker-Smith

http://bitsynthesis.com

I beg your pardon if this post is slightly offtopic and deals more with hardware than the patch itself, but it should take one more message for testing results to be complete:
@az said:

If PureData only uses 50% CPU, could it be the case, that you have a DualCore CPU?

Yes, all CPUs under consideration apparently had two cores, even Atom N280 on Eee - task manager shows two 1,66GHz cores. But I'm not sure its architecture has much in common with DualCore family. It looks slower than Core2Duo 1,66GHz. Well, anyway, it turns out that 50% CPU means 100% of one core under WinXP and Pd just can't distribute calculations between both cores to use more CPU in this case.

I just installed Ubuntu 10.10 NBR as 2nd OS on this Eee, and loaded this patch with Puredata Vanilla 0.42.6. It runs with no glitches at all with 44100Hz sample rate and 50ms audio buffer size! The same result with 48000Hz. But as I turned on 96000Hz, I even started hearing through glitches: "man, its just a netbook!" No matter what audio latency was set.

Task manager (named here "system monitor") showed 50-55% average usage of both cores (when 48kHz sample rate and 50 ms latency were set). Here it didn't mean that total usage was 100% (sometimes 80%-85% peaks appeared and again, no glitches). 50% CPU usage and no buffer underruns at all.

So, it's possible to use Eee with Atom N280 or later to make complicated patches, just under Linux. As for me, main problem is small screen, not Atom CPU, that's why I use it only for small abstractions and don't care what OS is installed. Also, if you'd use touchpad instead of mouse to work with Pd on Eee, I bet you'll say at least a couple of bad words in an hour of such torture.

haha, lol... well I expected a response like Arif's pretty much word for word, some what predictable... and besides which if no-one ever lets off steam and says how they see it from time to time then no-one takes note, you become lost in the sea of more agreeable comments, and I also think it's the sort of thing developers might actually find useful, it's called feedback (though noted "direct to the developers" is probably best). I recall last time I read this that Arif also said something about the software developers being offended by my comments, not sure what happened to that part of your comment... I think they should care little about the momentary episodic fury of a newbie PD programmer, they're clearly bigger than that!

Thanks for all considered comments btw, better late than never (my thanks I mean).... I do find PD very prone to freezing up though in general, and used it on many different computers in and out of University. It's my liking of it that fuels the frustration when you are held back from the creative process by glitches, creative states are so killed by hiccups. It's one of the main problems with trying to work on both sides of the process, technical and creative, the two flow so much better when they are separate....

As for "video causing the problem", maybe it was, I forget what I was working on at the time now... I am trying to get my head into Supercollider a bit more at the moment but also using MAX/MSP a little. I'll be sure to be more positively productive in my posting when I return to PD

Call for Papers and Presentations : Free and Open Source Software Panel Session at CAA 2011

Deadline Extended: May 24, 2010

Fight the Power: Open Source, Free Software, and Critical Digital Practice

We invite proposals for papers and presentations for a panel on creative Free/Open Source Software at the College Art Association Conference in New York, February 9-12, 2011.

Digital technology has become a standard tool for artists working in both new media and traditional forms, just as it has become enmeshed in ever aspect of contemporary life. The Free/Open Source Software movement has recently emerged as an alternative model to the traditional software industry. This panel explores the use of Free Software in the studio and the classroom. What possibilities can it open for students, and how does it impact our teaching? How does it fit into professional creative work? Can the ideas behind “open source” be applied to other forms of collabo-
ration? This panel seeks papers and presentations addressing the use of open source software in studio practice and pedagogy, the state of the art in free creative software, and the nature of cultural production in a digital society.

Please submit proposals and queries to

Ben Chang
ben@bcchang.com

For the full conference call for participation, visit http://www.collegeart.org/proposals/

All participants in the conference must be members of CAA. For more information, visit www.collegeart.org.

Hi everyone, my name is nacho and I'm new around here ...

I always wanted to get into Pd but just recently I started this little project which uses a existing 3D sound systems based on two 7.1 sound cards (14 speakers, 1 woofer, two creative audigy 4)

I already found out about the vbap extension (vector based amplitude panning) which is exactly what I need.

Now the problem: It seems Pd cannot handle the different outputs. Nether with MMIO nor with ASIO (I tried asio4all as well as creative asio which doesn't output anything).

I've attached the patch I use to send noise to the different speakers (to only one card for starters). With most configurations I get only output on 1 and 2.

The creative test applications work perfectly fine. I use Windows XP, just thought about trying it with a Ubuntu Studio Live CD but in the end I'd have to use win since another project on that computer must be ready for demonstration.

Thanks for your help on advance ... looking forward to wire the shit out of Pd

... nacho

http://www.pdpatchrepo.info/hurleur/Screen_shot_2010-01-19_at_2.47.15_PM.png