One shot ramp

gentleclockdivider · 2025-07-01T22:49:20+00:00

There was an error rendering this rich post.

Anyone has a good idea to create a one shot ramp ?

Inpure data there is this awseome line ~ vline~ object , you could give it arguments like

It's tailor made to read through am idex of samples .
In core I use the primary iteration , but this is mainly used to display the waveform in a multidisplay or get sample data into an array
I guess I could use the primary stage ramp envelope ( all linear ) but would rather have it in core

Find more posts tagged with

Comments

colB

What are you actually trying to do?

gentleclockdivider

I can use the primary iter ( set to 44100 it per sec ) to read the table in core
Iow , does anyone use the iter as a real time linear ramp envelope ?

gentleclockdivider

https://community.native-instruments.com/discussion/comment/232779#Comment_232779

Not trying , actually doing :)

Pipe sample data into core through table framework , run the iterator to display the sample data in a multidisplay : succeeded
Do the same thing for audio , but instead read the index with a ramp wave .

Replacing the ramp wave with alternatives : a one shot upwards linear ramp wave , whcih could be an envelope or even the iterator
Here I use the ramp to read the array , the iterator is usd for display purposes only

gentleclockdivider

And here I use the iterator to read the array , works great becasue the iterator just acts as an upwards one shot ramp wave ( has to be set to 44100 iterations per second though )
Which brings me back to my question , does anyone use the iterator as a real time index reader for audio , and perhaps an alternative in core ?

colB

I use primary iterator (partials framework wrapped sometimes) for driving GUI rendering using Multi-picture.

I wouldn't use the iterator for audio. It's just easier for me to write simple core code to drive that side of things. And that way, you are always fully synchronised with the audio clock. Using the iterator should work, but there are no guarantees. And it's really not flexible when compared to just writing some core code.

For multi-display, I will generally use only the maximum number of required objects, and do scaling etc. in core. So for a waveform display, if its 500 pixels long, I will use 500 objects for the waveform, plus however many other objects are needed for other elements like indicators or whatever. That way I can load up audio that is minutes long, and still handle it gracefully.

You do pay a price for flexibility though. The more control you want, the more work you have to do to maintain it :)

gentleclockdivider

Let me phrase it differently

Does anyone have a macro for a linear attack phase in core , iow a ONE shot ramp wave

KoaN

https://community.native-instruments.com/discussion/comment/232838#Comment_232838

Not sure if that is the proper way to do it but that works for me.

Rmp 1 shot.ens

Michael O'Hagan

There is a one shot ramp setup in the factory sampler instrument (core cell), it's the one that I hacked and re use if I need a one shot ramp.

Quick links

Unanswered questions