User Details

Username: Razzkazz
Website: alangleeson.net
Facebook: www.facebook.com/gleesonalan
Twitter: twitter.com/gleesonalan
Soundcloud: www.soundcloud.com/alangleeson
Account Status: enabled
Member since: Dec 12 2010
About Razzkazz: https://alangleeson.bandcamp.com/
(report this profile)

Devices by Razzkazz

Nudge Version 1.0
Nudge Version 1.1
Note Retrigger Version 1.1
Spectrum Analyzer Version 1.3
Note monitor Version 1.1
Note range fold Version 1.1
Simple Rungler Version 1.0
Rungler Modulator Version 1.0
Low pass gate Version 1.0
Note and Velocity constrain Version 1.0
Repetitor Version 1.6

Total Downloads: 3,948


Comments by Razzkazz

Comments

Update available (1.5)

X phase controls playback/read rate, normally driven by a phasor~ object. Y phase modulates playback position, it's not always apparent on shorter samples unless you're using > 5 rows, more obvious on long samples. Instead of using a phasor~ to modulate Y I also like to use line~ so I can scan through the sample, using a rate between 0. and 1.

Yes, almost done :)

I am guessing this is the same code, I got it from the Max forum :)

OK, i'll check it out.

Want to know what a Rungler is. Here is one persons answer;

https://www.muffwiggler.com/forum/viewtopic.php?t=92049&sid=f35a37a5aa1b409de5319628333ba286

Unpredictable, chaotic modulation! A (top) modulates B (bottom) & B modulates A using "rungler" circuits, so you get feedback/cross-modulation. That's how it's supposed to work anyway ;) The other controls scale the effect. Then you can map the output or A & B to one or multiple parameters in Ableton. If I get time in the next days I will make a video.

Hi Zip

Thanks for the feedback. Yes I understand it's not perfect, I have a real low pass gate myself so I know how they respond. If you are familiar with Max most of the code for this is written in gen, and not by me, it's someone else's research. I don't do gen programming so not sure I can adjust the response time, but I can look into it. With points 2 & 3 I agree. When I get some free time I will work on an update.

Indeed! There's a explanation of it here, albeit for the hard module circuit. It's also part of a Benjolin module, if that doesn't confuse things further ;)

https://www.muffwiggler.com/forum/viewtopic.php?t=92049&sid=f35a37a5aa1b409de5319628333ba286

I was able to solve the problem, but then today when I load the original version the problem is gone! doh! Anyway it was got to do with "del 1" going into the gate before start/stop.

On another point it might be worth setting "start/stop" and "reset to transports" parameter visibility to hidden as they fill up the undo buffer.

OK, did a bit rtfm and it's a bit clearer now ;) If anyone has any further insight it couldn't hurt :)

I'm investigating why I am getting double triggers/flams on the 2 and 4 but not 8. I think it has something to do with the change/gate patching just under plugsync. Is this a known bug/limitation?

I'm investigating why I am getting double triggers/flams on the 2 and 4 but not 8. I think it has something to do with the change/gate patching just under plugsync. Is this a known bug/limitation?

Can anyone explain what the different options in the drop-down menu that contains "clock, bit 1, bit 2....etc" does? Something got to do with how info is stored and output in the shift-register?

Anyone get the presets working? I just get the "Could not access the Max device file" message. The device itself works.

Requires the Max external "spectrumdraw~", get it here;

http://eprints.hud.ac.uk/id/eprint/14897/7/HIRT_v1.1.zip

Worked fine in Live 9, causes Live 10 to crash.

I have done and seen that implemented on other devices. I'll get working on it.

Is there any reason why you made the patch so difficult to decipher when opening it in Max?

Is there any reason why you made the patch so difficult to decipher when opening it in Max?

Cool, having fun with this.

Cool, thanks :)

Great! I was just about to build something like this.

Link is dead, is this still available?

Not hearing the "release sensitivity" have any affect?

Nice work, thanks :)

Sorry, ignore that last comment, that's only for material with transients, ie a drum loop. Last time I was using this was for measuring sine waves, so it behaves differently. Maybe a feature to add ;)

Is it just me or do you now have to set/edit the "value for trigger" in the scope to get the trigger mode to work properly, I adjusted it to .5? It worked before, now it doesn't. I recently upgraded to Max 6.1.8.

OK, thanks Peter :)

Alan

Hi Peter, I notice that to remove DC offsets sometimes you use cross~ and other times biquad~. I have been using the dcblocker external from Jasch. Do you find one more efficient? I want to switch and use a native solution.

Thanks

Cool, I must check it out :)

Thanks for this, very handy :)

Updated link to modified version https://www.sugarsync.com/pf/D7749808_2230749_982559

I have just uploaded an updated version. The new version makes track selection automatically.

http://www.maxforlive.com/library/device.php?id=845

Here is a link to a modified version of the above device, that works better.

http://www.sendspace.com/file/md14pe

I have hacked the patch and am using M4L.api.chooser instead of M4L.api.SelectDevice, seems to be working ok so far.

Having the same problem as pokem. Using Live 8.2.2, OSX 10.5.8. If I test the device in a new blank session it seems to work fine. If I try to use it in an existing session when I select a plugin to modulate no device parameters appear. Also sometimes after I refresh the device list I get duplicates of certain devices. No device parameters appear for any device selected.