inspired by @balwyn s spiro-plot patch https://forum.pdpatchrepo.info/topic/9560/spiro-plot @ingox and me built a spiro midi sequencer, similar principle as the lissajous midi sequencer, basically just the expression changed. spiro-seq.pd (updated)

here is a bit of an update of the knob widget, which is not yet a fully working widget, but does input and output 0-100 so could be used in a sub-patch with messages as properties and math for range. Its not the prettiest circle but colour and thickness help.
gridknob-wip.pd
g-knob-help.pd
Then getting even more sidetracked I realised concentric circles of polygons offered the same mouse events as the grid and in fact would only need as many as the radius/10 would require. But pushing the limits I offer this. Warning it does get quite loud, and has visual hints of Daleks
radiant-knob.pd
radiant-knob-dance.pd

Unfortunately Gem doesn't build with the 64-bit OSX Purr Data binary.

I don't currently include the externals in the search index. I'll do that in a future release, which will allow you to type "knob" as the search term and find the relevant object. (I'm also considering just adding "knob" as an automatically loaded object to make all this easier.)

Do keep in mind that audio GUI apps are about the only ones that use "knob" widgets. Physical knobs are great because of the control you have with your thumb and forefinger (plus tennis muscle efficiency for large turns). Using a mouse to control a digital knob is like trying to use a physical knob with chopsticks.

@Pierre-Guillot

so I think the linker should be set to -lCicmWrapper but I got conflicts and undefined
can you help me out ?

cc   -rdynamic -shared -L"D:/WORK/DSP/pd-0.46-7/src" -L"D:/WORK/DSP/pd-0.46-7/bin" -o "src/adsr.dll" "src/adsr.o"  -L"D:/WORK\DSP/PD/CicmWrapper-camo-dev/Sources/.libs" -lCicmWrapper  -lc -lpd  
D:/WORK/DSP/pd-0.46-7/bin/pd.lib(pd.dll):(.text+0x0): multiple definition of `error'
/usr/lib/libc.a(t-d000927.o):fake:(.text+0x0): first defined here
D:/WORK\DSP/PD/CicmWrapper-camo-dev/Sources/.libs/libCicmWrapper.a(libCicmWrapper_la-ecommon.o): In function `epd_add_folder':
/cygdrive/d/WORK/DSP/PD/CicmWrapper-camo-dev/Sources/ecommon.c:578: undefined reference to `sys_searchpath'
/cygdrive/d/WORK/DSP/PD/CicmWrapper-camo-dev/Sources/ecommon.c:603: undefined reference to `sys_staticpath'
/cygdrive/d/WORK/DSP/PD/CicmWrapper-camo-dev/Sources/ecommon.c:603: undefined reference to `namelist_append_files'
/cygdrive/d/WORK/DSP/PD/CicmWrapper-camo-dev/Sources/ecommon.c:609: undefined reference to `sys_staticpath'
/cygdrive/d/WORK/DSP/PD/CicmWrapper-camo-dev/Sources/ecommon.c:609: undefined reference to `namelist_append_files'```

I am trying to Vanilla-ize my PD-Extended patches, and for the most part, it's going great. But I miss "knob," and I can't find a suitable replacement.

I've tried moonlib/mknob but something is unhappy... perhaps related to the PD-X warning about moonlib on 64 bit systems? Anyway, I can't adjust its properties with everything barfing.

I can't find flatspace in Synaptic, in order to try flatspace/knob. I just installed deken (finally) but nothing comes up for Knob or Flatspace.

Does anyone have any suggestions? Basically, I want a nice visual correlation to the knob on my Korg Nanokontrol, for my less PD-savvy (so pretty damned unsavvy) musical collaborators. Guess I could use a really squat HSlider... but I like Knob.

By the way, I'm running KXStudio/Ubuntu 64bit. And I wasn't able to get PD-L2Ork working either (now I've forgotten why - some unmet dependency).

Hi there,

I'm trying to make a nice gui using knobs surimposed over an image loaded by [image]. First I noticed (long time ago) that a knob created before the [image] will be in a layer under it and becomes invisible if placed where the image stands.
My workaround is creating knobs after the image. But if I want a 'two-state' image, thus refreshing the latter the knobs disappear forever.

Is there a way to handle background/foreground plane numbers or something to set my knobs (and other elements) 'always on top' ?

Thank you.

Nau

You might have to use 2 separators or separations I forget exactly which one it is and always type the wrong one. try [separator] or [separation] make 2 of them after your texture then attach the output of each one to the separate cubes.
You can find out which one it is in the help browser easy enough just look through the gem example patches for something that begins with separ. I'm not at my pc at the moment or I would look for it.

First my story: (you can skip down to END OF STORY if you want)

Ever since I saw Mike Relm go to town with a DVDJ, I've wanted a system where I could scratch and cue video. However, I haven't wanted to spend the $2500 for a DVDJ. As I was researching, I found a number of different systems. I am not a DJ by trade, so to get a system like Traktor or Serrato with their video modules plus turntables plus hardware plus a DJ mixer, soon everything gets really expensive. But in looking around, I found the Ms.Pinky system and after a little bit, I found a USB turntable on Woot for $60. So I bought it. It was marketed as a DJ turntable, but I knew that it wasn't really serious since it had a belt drive, but it came with a slip-pad and the USB connection meant that I wouldn't need a preamp. And so I spend the $100 on the Ms.Pinky vinyl plus software license (now only $80). This worked decently, but I had a lot of trouble really getting it totally on point. The relative mode worked well, but sometimes would skip if I scratched too vigorously. The absolute mode I couldn't get to work at all. After reading a little more, I came to the conclusion that my signal from vinyl to computer just wasn't strong enough, so I would need maybe a new needle or maybe a different turntable and I didn't really want to spend the money experimenting. I think that the Ms. Pinky system is probably a very good system with the right equipment, but I don't do this professionally, so I don't want to spend the loot on a system.

Earlier, before I bought Ms.Pinky (about two years ago), I had also looked around for a cheap MIDI USB DJ controller and not found one. Well, about a month ago, I saw the ION Discover DJ controller was on sale at Bed, Bath & Beyond for $50. They sold out before I could get one, but Vann's was selling it for $70, so I decided that that was good enough and bought one. I had planned to try to use it with Ms. Pinky since you can hook up MIDI controllers to it. But it turns out that you can hook up MIDI controllers to every control except the turntable, so that was a no go. If I had Max/MSP/Jitter, I could have changed that, but that's also way expensive. So, how should I scratch? My controller came with DJ'ing software and there's also some freeware, like Mixxx, but none of this has video support. So I look around and find Pure Data and GEM.

And I see lots of questions about scratching, how to do it. And there are even some tutorials and small patches out there, but as I look at them, none of them are quite what I'm looking for. The YouTube tutorial is really problematic because it's no good at all for scratching a song. It can create a scratching sound for a small sample, but it's taking the turntable's speed and using that as the position in the sample. If you did that with a longer song, it wouldn't even sound like a scratch. And then there are some which do work right, but none of them keep track of where you are in the playback. So, whenever you start scratching, you're starting from the beginning of the song or the middle.

So, I looked at all this and I said, "Hey, I can do this. I've got my spring break coming up. Looking at how easy PD looks and how much other good (if imperfect) work other people have done, I bet that I could build a good system for audio and video scratching within a week." And, I have.

END OF STORY

So that's what I'm presenting to you, my free audio and video scratching system in Pure Data (Pd-extended, really). I use the name DJ Lease Def, so it's the Lease Def DJ system. It's not quite perfect because it loads its samples into tables using soundfiler which means that it has a huge delay when you load a new file during which the whole thing goes silent. I am unhappy about this, but unsure how to fix it. Otherwise, it's pretty nifty. Anyway, rather than be one big patch, it relies on a system of patches which work with each other. Each of the different parts will come in several versions and you can choose which one you want to use and load up the different parts and they should work together correctly. Right now, for most of the parts there's only one version, but I'll be adding others later.

There's a more detailed instruction manual in the .zip file, but the summary is that you load:

the engine (only one version right now): loads the files, does the actual signal processing and playback

one control patch (three versions to choose from currently, two GUI versions and a MIDI version specific to the Ion Discover DJ): is used to do most of the controlling of the engine other than loading files such as scratching, fading, adjusting volume, etc.

zero or one cueing patch (one version, optional): manages the controls for jumping around to different points in songs

zero or one net patch (one version: video playback): does some sort of add-on. Will probably most commonly be used for video. The net patches have to run in a separate instance of Pd-extended and they listen for signals from the engine via local UDP packets. This is set-up this way because when the audio and video tried to run in the same instance, I would get periodic little pops, clicks, and other unsmoothnesses. The audio part renders 1000 times per second for maximum fidelity, but the video part only renders like 30 or 60 times per second. Pure Data is not quite smooth enough to handle this in a clever real-time multithreading manner to ensure that they both always get their time slices. But you put them in separate processes, it all works fine.

So, anyway, it's real scratching beginning exactly where you were in playing the song and when you stop scratching it picks up just where you left off, you can set and jump to cue points, and it does video which will follow right along with both the scratching and cuing. So I'm pretty proud of it. The downsides are that you have to separate the audio and video files, that the audio has to be uncompressed aiff or wav (and that loading a new file pauses everything for like 10 seconds), that for really smooth video when you're scratching or playing backwards you have to encode it with a codec with no inter-frame encoding such as MJPEG, which results in bigger video files (but the playback scratches perfectly as a result).

So anyway, check it out, let me know what you think. If you have any questions or feedback please share. If anyone wants to build control patches for other MIDI hardware, please do and share them with me. I'd be glad to include them in the download. The different patches communicate using send and receive with a standard set of symbols. I've included documentation about what the expected symbols and values are. Also, if anyone wants me to write patches for some piece of hardware that you have, if you can give me one, I'll be glad to do it.

Keith Irwin (DJ Lease Def)

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

I'm trying to get http://www.iamas.ac.jp/~aka/max/#aka_keyboard to work with pd-extended. I've googled around and cant seem to find out how to do it. I've placed it in the user/Library/pd folder as well as the ../Pd-extended/Contents/resources/extra folder.

I'm new to all this so I'm not even sure if it is supposed to work in PD. The two files in the aka.keyboard folder are aka.keyboard.mxo and aka.keyboard.help

I appreciate any help

Thanks!

Clay

Hello all (my first post here)

Just started to learn PD. Im doing a surface for my Akai LPD8 at the moment, view attached.

Some questions.

I was looking for a knob, couldnt find one in PD. But when i looked around here in the forums i found the Korg Nano abstraction, with knobs in it, i copied those over to my patch. My question about this is. Where did this knob come from? Was it hidde all the time somwhere in pd? or was it a speciall build or something of the patch i opened? Are there more of these hidden things in pd, and where can i find them?

Question 2:
If you look at my patch to the far right is a little thing ti light up my pads on my my controller when a note is sent. I am not sure about the [== notenumber] part, is that the way to go?

/Jon

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