Wish for a bugfix in primary audio table

gentleclockdivider
gentleclockdivider Member Posts: 275 Advisor
edited May 30 in Reaktor

When you import an audio file in the audio table , x output is set to units ( sample length ) screenshot 1
Whenever you re-load the ensemble it automatically switches to milliseconds , This is a real pita since the units are used to drive a ramp wave ( samplerate/unit length = speed inHz )

Screenshot 2

1.jpg 2.jpg

Before anyone says , Use core : 0 ,

I have used core and the table framework , it works nice but there is no x-interpolation

Interpolation is needed because 1 audio table is used for the playback speed of the other .

please fix this bug
Also found something verry weird , a pop menu from the audio table still has the old kontakt 5.5 gui :)

3.jpg

I don't expect a fix either way

Tagged:

Comments

  • colB
    colB Member Posts: 1,075 Guru
    https://community.native-instruments.com/discussion/45573/wish-for-a-bugfix-in-primary-audio-table

    Before anyone says "Before anyone says , Use core : 0 ," ;-p

    You can use interpolation in core to playback from table framework.

    If you don't want to roll your own, you can use the 4 point from the factory delay module.

  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor

    Well I have no I dea how to do that , since I am pipin the samples into core via the tableframework .

    I have an audiotable controlling the audio playback and works fine , reverse , table scratching etc…

    image.png image.png image.png
  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor

    I also found a pretty nifty low-res time stretch technique

    I play the sample back and forth , with a smaller higher percentage of forward playback speed , now speed up the modlation.
    Instant timestretch

  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor

    if it wasn't clear , I am using the primary table framework to pipe in the data into core .

    Should I use another core table + interpolation ?

  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor
    edited May 30

    I f anyone wants to have a go at it , here is the ensemble
    Just drop the samples in the Primary tableframework , the sample data is then send into the core cell
    The sample data is read out by a phasor ramp and the speed of this phasor is controlled by the audio table
    Y axis Everything > 0 = forward , < 0 = backwards

    The playhead can be stopped , reversed and resumed

    When depth = 1 , +1 = normal speed , -1 normal reverse speed

    1.jpg
    controlthetablecorenosamples.ens
  • Chet Singer
    Chet Singer Member Posts: 80 Advisor
    edited May 31

    If it's helpful, attached is the 4-point interpolator core macro. I've been using it in Beauchamp Brass and Moravia Reeds, which use the table framework.

    The interpolator is a useful piece of work. Just give it:

    • The position in sample memory you want to read from (a float, which drives the interpolation).
    • The size of sample memory, to prevent overflows (int, of course).
    • The data pointer to the sample.
    4-point core interpolator.zip
  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor

    Thanks , can't open the macro ..still running 6.4.3
    Also I have no idea where I should place the interpolator .

    The sample data that is going into core is from primary , I have no array and or tables inside core

    image.png
  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor
    https://community.native-instruments.com/discussion/comment/228910#Comment_228910

    That's where I am at loss ( se screenshot above )
    The position in sample memory : ramp wave reading from the data pointer

    The size of the sample memory : easy , that's just the [?] size module
    The data pointer to the sample : Index [] , I assume

  • Chet Singer
    Chet Singer Member Posts: 80 Advisor
    edited 4:16AM

    It looks like your ramp input is moving from 0 to 1, so multiply it by the size of the sample memory.

    And your core cell is already doing that, so the output of that multiplier should go to the position input of the 4-point interpolator.

    In fact, I think your core cell is already producing the three inputs needed by the interpolator. I've circled them.

    image.png
  • gentleclockdivider
    gentleclockdivider Member Posts: 275 Advisor

    Awesome , I haven't yet checked your module out because I need to upgrade

Back To Top

Categories