*SOLVED* Tables are creating flams

[theotteryears]

Attached is my save file.

If you just connect up TRIG 3 out to a very fast envelope, opening a VCA with an OSC through it - you should hear sometimes that the table flams when I tell the table to stop playing.

I guess the timing of table OFF and a new trigger from the TRIG column at the same time is slightly out.

If you listen to the file for about 30 seconds you should hear what I mean occurring sometimes.

Hope this is clear!

Thanks,
Chris

[XORadmin]

They are some known minor table timing issues (some other thread here) which i still got to check. And its exactly the startpoint of a table which can be slightly off sometimes. No issues here in the most cases, but i guess for you, as you use these for some fast triggers it might affect.
Also trigger 10 is very fast and they are for some envelopes / drums too fast for reliable triggering. Triggers of 20 and more are more stable for modules which use it.
I see you are using the tables for some retriggering. Why aren't you using the retrigger functions for it?

I will check out your file tomorrow with sound...just checked it visually for now.

[theotteryears]

My idea was to create a few variations in the tables (eg. triplets, 32nd notes, and some syncopated stuff) and then have probability on the tables. Also I was hoping to be able to choose randomly which of my created tables get played.

Like the RND FX bit, but really I wanted a new command which said randomly choose from eg. Table 1 to Table 8, when I put in the command. Combined with Table probability, this would be very cool.

This way drum programming would have some user input but with some machine randomisation too. I used to use this a lot in Renoise as a way to make patterns evolving. I think Eloquencer has something like this... probability on a step triggering, and also probability on a variation of that step also.

Hope thats clear. I will try your idea of using RND FX before the table... but what does it randomise??

[XORadmin]

My idea was to create a few variations in the tables (eg. triplets, 32nd notes, and some syncopated stuff) and then have probability on the tables. Also I was hoping to be able to choose randomly which of my created tables get played.

Like the RND FX bit, but really I wanted a new command which said randomly choose from eg. Table 1 to Table 8, when I put in the command. Combined with Table probability, this would be very cool.

This way drum programming would have some user input but with some machine randomisation too. I used to use this a lot in Renoise as a way to make patterns evolving. I think Eloquencer has something like this... probability on a step triggering, and also probability on a variation of that step also.

Hope thats clear. I will try your idea of using RND FX before the table... but what does it randomise??

It does randomize the next coming FX value in the FX field you point to with the randomvalue -> 0 randomizes which FX column should be randomized next,  1..4 points to the FX column which should be randomized next.
So if inserting the randomize function in FX1 with value 2 will randomize the FX2 value if filled in. With that you can choose to randomize any FX value on the same step.

I don't know exactly which function in the Eloquencer does that. Probability on step triggering is also in the NerdSEQ. I don't know about step variations.
NerdSEQ can add probability and randomization to any function. The randomization part needs some finetuning, but with all functions together you can get very far already and let the same pattern never sound the same.
Don't confuse probability with randomisation. Where one decides only if something will happen or not, the other really randomizes the content.

Also i don't know what Renoise can do with it and it's also nothing i normally check as it is not really comparable having a full power PC with gigs of ram and speed vs. a little embedded system. Renoise is filled with great functions but most are just not realistic for embedded systems. Same goes for Ableton, Logic ... (fill in whatever DAW on modern computers). 

I try to include many cool functions and they are plenty more to come.

[XORadmin]

I checked you file and it is what i expected and already mentioned in another thread. The synchronisation of the table start is not always perfect and so the time for the first step of the table will be too short sometimes. This don't affect free running tables, but the one shot ones and the retriggering ones.

On my fix list for one of the next releases.

[theotteryears]

hey Thomas!
thanks for the reply. ah I didn't mean to sound like I was knocking the nerds - I love it and think its one of the best modules out there I also didn't mean to compare this to a PC etc, I just wanted to replace Renoise with this completely, and its so almost there for my needs.

[XORadmin]

Haha, no worries. The tables will be fixed, but first the expanders and midi as this is very closed to finish.

Until then, play with all the other functions and no worry to ask for more features!

[LonzoB]

Haha, no worries. The tables will be fixed, but first the expanders and midi as this is very closed to finish.

Until then, play with all the other functions and no worry to ask for more features!

Well, I don't want to discourage anyone - but working out some basics before expanders would be great... Table timing, Ratcheting from clock instead of by milliseconds, and a way to program Shift/Start for a row would make this unbeatable. Hoping to see these soon! 

[XORadmin]

Haha, no worries. The tables will be fixed, but first the expanders and midi as this is very closed to finish.

Until then, play with all the other functions and no worry to ask for more features!

Well, I don't want to discourage anyone - but working out some basics before expanders would be great... Table timing, Ratcheting from clock instead of by milliseconds, and a way to program Shift/Start for a row would make this unbeatable. Hoping to see these soon! 

Ha no worries, i still feel enthousiastic like on the first day.

Let me get to your definition of basics. I never intended to copy functions of other more or less complex sequencers and most important, i never even knew what they all were doing exactly. When i started, beside all the tracker ideas i had, i thought about that this and that would be cool to have, so i made it. Without looking what others do. I still don't but many typical eurorack stuff ended up anyway in the NerdSEQ, mostly feature requested. So some features that you might expect from a 'classic' Eurorack sequencer are just not there or not there yet. Instead you have tons of other stuff that do more of a compensation of these. And with some you can recreate most of the in the first place missing functions anyway. So things that can be recreated or worked around in some way get a bit of lower priority. Which doesn't mean that they not will be added at some point.

I am aware of the issue with one of the table functions. The fact that it took several months until one informed me about that tells me that this is not a highest priority thing. Even more a fact, using FX in tables is very unusual and i wouldn't consider this and tables in general as 'basic functions'.
So this will be addressed as soon as i finished some higher priority functions & issues. This will be very soon.

Ratcheting, being a kind of classic function will be added. They are several reasons why it's not there yet. One being that it is also not that killer function everyone wants. But beside that i will implement it at some point. And now they are already several ways to create ratcheting functions. There will be an extra ratcheting FX at some point. But also here, they are some higher priority things before. 

Start another pattern or row in the sequencer as a fx function will be in the new release. (by feature request)

They are many feature requests together with a still long 2do list and i will implement many of the stuff. But i also got to think about priorities and how to keep the company running. Firmware updates are nice as they improve a (in my opinion already featurerich) product, but i also got to invest time to develop new things that i can sell (in opposite to firmware updates which are and will stay free), else it's not possible to keep on doing this. As i am a one man company, i got to take care of everything and some things like firmware development is just one little part of it. But i do my best to keep all running well. The expanders are essential to keep things running. And given the feedback and the continious questions about availability it seems that this has a wide covering to be a high priority thing.

And you know, with every firmware update with new killer functions, many of the feature requests are added and problems addressed. In that way it will be step by step improved. 

Now i get back to get the release ready! Cheers and *thumbs up*

[LonzoB]

Thanks Thomas,

..."And now they are already several ways to create ratcheting functions."

I know of 2 ways to ratchet - One Shot Tables and Step Repeats. Both of those have timing issues. Are there other ways also?

I am sorry if I sounded like a downer. I have tried quite a few euro sequencers and I am probably in a different situation than most. I am playing with a band and am playing other instruments as well. The Nerdseq is really close to being everything I need - I'm sure I'm not the only one

Great to hear about the updates. I tell everyone about the awesome Nerdseq!