It doesn't allow for a particularly fine resolution in your vibrato sweep since every other step is taken up by H commands, but in most cases I find that the difference is negligible if noticeable at all.

But, wouldn't the climb to VF6 be smoother if done over 2 or 3 fast tables, rather than a single table slowed down by a G command? Wouldn't having only 16 steps (15, if using the H0E trick) for the vibrato slide would make it a somewhat jagged slide into the deeper and faster vibrato? although at higher BPM's it probably wouldn't matter as much I guess.

I feel like such a dingus

...you're not alone

Invisible Robot Hands wrote:

So some people prevent wraparound either with the G command, but many others just send their table to an empty table  with A (because a slower groove on the table may mess with the other stuff in your table, like arps), but today I accidentally discovered that you can actually prevent effect wraparound without forcing a perfectly good table to be empty (only tables 00-1F are useable so conservation can be crucial) by actually sending the end of a table to a table that doesn't exist, like A20. Ex: let's say you have a noise instrument that uses table 03, using the TSP column to make a "ptchooo" sound shifting downward, and you want it to hold on a certain frequency, but you don't want to waste tables by sending 03 to 04 just to hold a pitch. You can actually send table 03 to a nonexistent table and it'll sustain the pitch.

Or you could always put a H0E on the bottom of that table. Which I do both for the pun and because it has the desired effect.

Also a viable option. I suppose neither takes up any more space.

Where's the pun, though? It just spells "hoe" without any context.

So some people prevent wraparound either with the G command, but many others just send their table to an empty table  with A (because a slower groove on the table may mess with the other stuff in your table, like arps), but today I accidentally discovered that you can actually prevent effect wraparound without forcing a perfectly good table to be empty (only tables 00-1F are useable so conservation can be crucial) by actually sending the end of a table to a table that doesn't exist, like A20. Ex: let's say you have a noise instrument that uses table 03, using the TSP column to make a "ptchooo" sound shifting downward, and you want it to hold on a certain frequency, but you don't want to waste tables by sending 03 to 04 just to hold a pitch. You can actually send table 03 to a nonexistent table and it'll sustain the pitch.

Or you could always put a H0E on the bottom of that table. Which I do both for the pun and because it has the desired effect.

V commands don't stack at all, you can totally do a swell!  I use it for basically every single table ever.  Arps especially.

What have I been doing all this time?! I guess that's what 8 months of lsdj gets you. A really limited knowledge of awesome code. I feel like such a dingus.

How far do you stretch your second value?

What the heck double post?

You don't really NEED to run a table from a table in this instance.  You can use a G command in a table to make the table run slower, conserve tables and make it less confusing to edit as well.

Right on man! I wasn't sure if putting a g command in would make the entire song's groove slow down. That's actually helpful for more situations other than just this one. Is it posibble to do a swell like that or do the V commands stack? Like, would a VF1 after a VF4 actually sound like VF5?

What do you think?

I'm shooting for a dynamic grit similar to some sid sounds without using a pwm wav synth. I already have one drawn in the project I'd be using this idea with. Just throwing out an idea that popped into the noggin.