Speed variable Table Play? noob questions

#21

Got the hash issue fixed. Thanks smile I would NEVER be able to figure stuff like that out on my own.

Ahh yeah I see... I mistaken it for a wave player with pitch. I havent used the tables much, I use mostly the wave players.. They make more sense to me for now.

I checked the help file and "play table as sample" seems pretty interesting smile But is there anyway that I can use the table "play pitch" to trigger a sample that is loaded like you would in a wave player? Can I load a sample in another table object and then play it directly from the play pitch object? I just cant get my head around how to do that. Tables a still a bit blurry to me.

Also any chance that there will be a waveplayer with pitch modulation?

#22

thats what you gotta do - load a .wav into a table and then put that table name into the pitchable table play. but remember to use .raw files actually..because of that header problem.

#23

Yes I need to change all files on my SD card to raw files. Just didnt have the time yet smile

The tables: all of the tables only has table names slots... I dont see any table I can put wavefile names into.

Do you mean I have to record it into a table and then play it back? Sorry guys, really noob on this path.....

#24

ive been doing nothing but tables for like a month now hehe.

letable.JPG1315x659 92 KB

Reverse Audio in Tables
#25

wave/play is for streaming playback. That means that only a little bit of buffer memory is used between SDCARD and playing. This allows to play extremely long samples.

Tables can be used to load samples into. Those will need to fit into the 8MB of SDRAM memory. SDRAM is much much faster than SDCARD. Once in a table it is more flexible to pitch up/down, skip, reverse whatever.

Don't expect pitching streaming playback objects any soon.

#26

Johannes, not sure if you want feedback on the table play pitch loop object, but I downloaded it as well.

in case you do:

If i have the pitch set to the same thing as the "play pitch" object, the play back is pitched lower on the loop version.
As for the looping, I assume the loopstart and loopend are for selecting the element #s of the table that is loaded..and I should be expecting the table to loop once triggered - but im failing to do that. I'll experiment some more, unless this object isn't ready.

also, not to be annoying but, playback direction toggle could be cool blush

#27

Looks interesting smile

I guess I better dive into tables. I see a lot of potential using loops like 1 to 4 bar...

Was also wondering how to use those filename inputs, but I see now. I can use it to load a sample into the table without having to record anything.... Great smile

Though I got some pretty awesome sounds out of wave players I really miss the pitch input. I'll start experimenting with tables for those scenarios where pitch is essential...

Anyway, got a lot smarter on the topic from this thread. Thanks @johannes @alexk

#28

put a phasor comp osc into a table read object with some single cycle .raw wav. much fun!
i've been copying an sq80 but it evolved into some kind of monster hehe. Read a bunch about the ppg, prophet vs and some modern vsts..it is a lot of fun to make one of your own!

The reason i was fighting with a pitchable triggered play table object today though was because i started a drummachine based on the drummatic4 (you can construct sounds out of different parts in it). Super fun.

I am also thinking tables can be used for "complex" envelopes.

#29

WIll try that out smile Thanks

Yeah, I was aiming at making a copy of Camel Audio(Now Apple) Alchemy with the waveplayer, but missed the pitch. I really like Alchemy for granular/glitchy sounds, cause you have endless control of every parameter... Really good. But I try to use hardware only these days, so using Alchemy is not an option and needs a computer.

Are tables used in other software modular system like Max or Reaktor? I don't now them that well. Maybe I could learn from reading about tables in Max or Reaktor?

#30

yeah reaktor for sure. max probably too but im not that familiar with sound generation in it. I feel like PureData is more educational!

#31

Reaktor has different types of tables (iirc) : a table similar to what you see in Axoloti, and a loop-player which time-stretches the sample using (probably) granular synthesis.
I made some granular synthesis patch using event-tables in Reaktor 10+ years ago, same thing could probably be done using Axoloti. Getting the envelopes right for the grains is tricky and influences the sound quality a lot.

There is not much to learn about tables though; it just reads the values one by one.
But I think you mean using granular synthesis, right? (that is what Alchemy uses)

#32

I'm seeing a glitch in table/play pitch.

I hear an audible click when playing back from the table using 'play pitch'
I have 2 tables (stereo).
It seems to have something to do with initialization - notice that if you drag the table/alloc object for 't1L' table down below the other alloc, the clicking will be on the right instead of the left.

I've attached a very simple example. Simply run it to hear the click. You don't actually need to record input or do anything else.
SimpleSampler.axp (4.6 KB)

#33

@Mood_Organ

I have not tested it, but I guess the click is the result of loop-points not being at zero-crossings.
That is not a glitch, but just what happens.

If you use 2 tables it is almost impossible to find matching zero-crossings (= where both signals are '0' at the exact same time).

So, solution is to have some envelope for the entire loop, to add a very short attack/release at the beginning and end. (which can result in a short silence). Another trick is to crossfade beginning and end, but that is not easy (mostly because you'd need to store some extra ms of audio. without it your loop would be shortened by the time it takes to do the crossfade).

#34

Are you using .raw og .wav files? You should use .raw files. Using .raw files should eliminate the click in the beginning of files.

#35

No files. I am recording into the table from the audio inputs.

#36

Did you check out the example? The click happens without any audio recorded into the tables at all. So the tables should be ALL zeros.

#37

works for me without clicks... are you using 1.03? (help/about)
try connecting a scope in axoloti see what it looks like, i.e. is it a large spike?

the odd thing is... tables are initialised explicitly to zero, i.e. we are not relying on the compiler to do it, so it seems unlikely they are not being initialised correctly.

#38

Yes, it says 1.0.3-0-gc248736

Yes, it's a quick spike from 0 to maxval
Very strange that it doesn't repro for you

#39

Does anyone else want to run this patch and see if my issue is reproduced on yr hardware?
TableClickBug.axp (5.2 KB)

btw - this is correct I assume?
Firmware version: 1.0.0.1

#40

OK folks. I was (unintentionally) able to eliminate the click. I think it happened because I ran a different patch that allocated larger tables than the ones I was using. Maybe there's an off-by-1 index error in initialization, and I had a sample that was stuck high (instead of zero) in memory. If allocation happens to the same location in memory every time you run a patch, that would explain why the click moved from left to right channel depending on which allocation was evaluated first.