I have struggled for quite a few days now to try and get MIDI into pd via the IAC driver... from Live, from Logic... and nothing happens.

I've created busses in the driver called Pure Data In and Pure Data Out;
I've selected the driver in Live/Logic;
I've opened Live/Logic before opening pd
I started out trying to get MIDI clock in through the <<midirealtimein>> object and when nothing happened, I checked the <<midiin>> object - still nothing.

Can anyone help out?

I'm on OSX 10.6.8

Thanks,
Brett

I have struggled for quite a few days now to try and get MIDI into pd via the IAC driver... from Live, from Logic... and nothing happens.

I've created busses in the driver called Pure Data In and Pure Data Out;
I've selected the driver in Live/Logic;
I've opened Live/Logic before opening pd
I started out trying to get MIDI clock in through the <<midirealtimein>> object and when nothing happened, I checked the <<midiin>> object - still nothing.
I've seen a few posts where people had a problems similar to this, but the problem just seems to eventually go away or they fix it without knowing how.

Is there a problem with 43.4 as I heard that was previously a problem with 43.1.

Can anyone help out?

I'm on OSX 10.6.8

Thanks,
Brett

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!!

Does anyone know of an audio routing or switching abstraction/external, such that one of two or more incoming signals can be selected to be passed on to the next object, ensuring that the other signals are completely cut off?

I am creating an 2-effect module where the effect order can be switched round.

For example, the audio either routes through a delay then into a panner then to the output, or when switched, routes through the panner then into the delay then to output.

Thought I had the switching all sussed out. There's a switch ahead of the two effects which directs the incoming signal to one or other. This same switch is also used to direct the output of the delay either to the panner or the main out, depending on whether it went through the delay first or not. The same is done for the output from the panner.

The whole system works until I connect the output of one effect into the input of the other, when the signal disappears. It's probably some sort of feedback problem, but it shouldn't be because only one of the input signals should be on at any one time.

I've heard of spigot~ but not sure what library it's in as it doesn't work for me.

Could mux~ possibly handle this problem?

http://www.pdpatchrepo.info/hurleur/monoswitch.zip

Is there a Pd iPhone app yet ie. to run Pd on the iPhone? would be great to be able to make patches on the go. Can't find anything in the App store though.

I'm trying to make a bank of sends and returns for effects. The sends and returns are all in one patch, and I'm using the send~ and receive~ objects to send the original signal from a drum machine to another patch containing the effects, and back again.

I want to be able to switch the relative positions of each effect module in the signal path so have tried to use the [makefilename] object to alter the ID of the send and return coming into and going out of the effect module. However, this doesn't seem to work ~ i get all sorts of unwanted feedback delay effects and whining when changing the position of the effect.

If i set the send~ name manually it's ok, it's just when I try to change the position automatically. Possibly something to do with not being allowed multiple send~s to a single receive~?

Pls refer attached patches

http://www.pdpatchrepo.info/hurleur/panner.zip

Is it possible to create a drop-down list within pd?

Is there anyway to store symbols in a patch similar to the way that arrays store numbers, or do we have to assign a number label to the symbol and store it in an array?

For example, if I've selected certain drum sample names in my drum machine that I want to be recalled automatically next time I open this particular instance of the drum machine, how can I store the name of this drum?

Can someone point me in the right direction for how to create neat colourful GUIs for Pd instruments? I've only been working with sound so far and I find trying to set up sliders and toggles etc. in the parent window of a patch seems quite clumsy - the various sliders and number boxes end up on top of each other and being obscured by other objects.

Should I be using GEM or some other external to make things easier?

I'm using arrays to store drum patterns in a patch and trying to find a way of saving any changes to the arrays that I make at the end of a session, possibly to new arrays to make new drum patterns. Can I use savepanel for this? if so, how to implement it - I've seen the following in control examples:-

[bang]
|
[savepanel]
|
[array99 $1 write]

but not sure what the $1 and write are for in this case, since in my case the array would already have been written to (i just want to save it to disk).