@alexandros said:

Can't you send 248 to [midiout]? That's the MIDI clock byte. Just setup a [metro] to the desired tempo and connect its outlet to a "248" message. Then use a MIDI interface to send that to your other devices.

Perfect. I'll give that a shot (far easier than I was anticipating).

Thank you.

Edit: I see this message is sent 24 times per quarter note, I assume I'd want to multiply the metro bang into 248 by this factor (assuming I send a quarter note tick)? Oh well, I'll experiment.

Hello,

I'm away from my studio, but inspired to put an idea into effect that would necessitate bridging the divide between PD and my larger studio.

I have worked with the noteout and makenote, but for this experiment I'll need to have PD generating the master clock to some Elektron boxes. I've yet to find a sync module, nor have I found any tutorials that cover this.

What modules should I investigate? Is there something that takes metro output and resolves that as midi sync?

Sorry for such a basic question. Again, I'm not at a system that has Pure Data loaded to explore.

@alexandros said:

Am I missing something, or the patch below isn't correct?

[phasor~ 1]
|
[threshold 0.5 10 0.5 10]
|
[o]

This does output a bang whenever [phasor~] resets.

Nice, provided this operates as suggested (haven't tested), this does precisely what I'm looking for.

I literally started with PD last week, so I just haven't encountered the threshold module to consider (I used Max/MSP back in the Nato.0+55+3d days, supercollider in the early 2000s, and patch modulars extensively since the Nord Modular days, but ignored PD for the most part under an impression it lacked refinement).

My aim is quite simple, embarrassingly so: I'm learning how to play back samples loaded into arrays, and wanted to test my bpm calculations after changing the phasor's speed. As a test I wanted to run a metro at the quarter note time of the new BPM, triggering a kick sample, and confirm the hits are falling where I expect them to,... but then I ran into the issue of getting my metro to start precisely in time with the looping sample (which is just freely looping endlessly via a phasor). Since the phasor~ lacked a phase output, I was stumped, and figured getting the array index = 0 = bang would be a simpler approach.

Per the randomF, the multiplicative scaling by 0.1 works, but then limits my range to 0-1. The use of a second random added to these values would fix this easily, but didn't seem as efficient as finding something that might already exist. Good to hear else has a "rand.f" (or whatever is typed above). I have this external already installed, but haven't exhaustively worked through what is included.

Thanks again, one and all.

p.s. Per the playback of arrays, I have learned a method of chopping samples with a dedicated start button using direct indexing of the slice's start in sample size values (fed as arguments into a vline module set to read from tabread4), but haven't learned how to do so when indexing via a phasor~, I suspect I'll get there in the next day or so.

The vline approach feels superior, but I'm not so sure it lends itself to rate control as easily as phasor~. Indexing via phase seems simpler too since it'll always be 0-1.

Hello,

I keep half posting questions today, only to find my answer while reflecting on how best to frame my explorations. Earlier it was in relation to extracting BPM from a soundfiler based audio loop, but I was able to muddle through by manipulating the sample size (sample size divided by sample rate * 1000 to get total length in ms, then multiplying 60,000 by beats in the loop / total sample length in ms to get BPM).

Two very fundamental questions remain, however:

1. there used to be a random object that spit floats (randomF). That doesn't appear to be included in vanilla anymore, and I do not see anything by that name in the external search. Anybody familiar with something that will do this?

2. Earlier I was working on an array, and really wanted to send a bang every time it looped around to index 0. This feels like it should be really easy, but I couldn't think of anything that would send the active index step as out (the contents of the index step, sure, but not the step number itself).

Is there something in the toolbox that will allow for this?

Thanks!

@whale-av said:

@_ish No, the GOP window cannot be set by the mouse. You have to put values into the Size and Margin boxes in its properties dialog.
When you click "apply" you will see the changes whereas if you click OK you will have to open the properties again to make further adjustments.

Welcome to the Forum...!
David.

Thank you. Figuring out whether this was a bug, or just a version difference was chief in my aim.

Thank you to everybody else for your commentaries and assistance. Very useful information.

@willblackhurst said:

you make a pd "sub-patch" object. you put object and type pd and then a space and a name.. and off click so then you are immediately inside the sub patch page. then you right click for properties. you make it yes graph-on parent. and then you move it with margin in the properties window and the size is also in the properties window. then if you go to the above page parent page and you see the object box you made except its larger according to the properties you entered on the inside page.

Not sure what you're trying to say. I know how to make subpatches, and the video I linked is creating a general use object for use in other patches.

I assumed you meant this behavior would change if done in a subpatch, but it's the same.

In short, when I right click on the canvas and select properties, and then enable graph on parent, the red box appears but cannot be moved by the mouse -- is that expected behavior? Hovering over the red box's borders doesn't allow me to relocate or change the size of the box (unlike in the video I linked).

I understand what the red box represents, and got it to work through a laborious process of trial and error as I stated in the "edit" at the bottom of my post.. but am uncertain if it's supposed to be draggable / resizeable via the mouse as evidenced in that video.

Apologies, I'm new around here (and new to PD). Unsure what information I should lead with, but suffice to say I'm using a mostly vanilla version of PD 0.56.2.

I was trying to follow along with this oscilloscope tutorial posted six years back by pd_777.

At the 3:53~ mark he goes into the Canvas properties and enables "graph on parent," which creates a red box that will constrain the visibility when the object is loaded into a later patch.

When I do this, I similarly get the red box, but cannot interact with it. I cannot adjust its position or size. It is like the box isn't there.

Is this a bug, or am I missing something?

Thank you!

p.s. I'm aware he is using "Purr Data," something that no longer seems to exist (or does it?). Still, the functionality in this tutorial all seems to still exist in the modern iteration, save the ability to interact with that red box.

Edit: I figured out a workaround; the canvas box lists "range and size" parameters, which included a size and "margins" field for X and Y. By trial and error I was able to offset the box to what I needed, but this was far less useful than what is shown in that video (click and drag to resize).