I really like the pitchbend + arpeggio that you showed in your video. something I've been thinking about myself.

Regarding nested tables; I think that only makes sense, in LSDj at least, if the main table calling other tables is set in instrument screen to step mode.

  YAAAAHHH :''D

@ nitro2k01 : Some good info there. I learned a few things.

There is no absolute right or wrong.

That goes for life in general, not just chiplife.

The commands in tables are processed from left to right, so if you have, eg, two C commands executing on one tick, the right one will take precedence. However, if you have two A commands, the left one will happen first. Still, however, if there's an A command and something else on the same step, the athor command will be executed, whichever side it is on.

It does work fine. Here's what happens. (This is, assuming that the vibrato mode is HF. Vibrato mode also affects P. See below.)

In HF mode, the P and V commands aren't clocked by the playback engine, so pitch effects are running desynced from the BPM and the way tables are running. It's clocked faster than the BPM, so it typically executes in between table steps/master ticks.

In "slow" mode, on the other hand, P and V are run in the playback engine, and are synced to ticks, so P won't make a difference when used with C. However, if you're using a table that runs slower than 1 step/tick and use the table transpose column, you can still hear the effect.

In either way, what the command does is to take the "current" pitch value and continuously add the value from the P command to it. This is the same for HF and LF, but in LF , the value is of course added much less often, so it's slower.

This applies to transpose in tables and with the C command the following way: Whenever a table or C command requests a transpose, the "current" pitch value is reset to the the base note + any applicable transpose. So in effect, the pitch sweep is restarted on every step with a change in transpose. (If there are multiple steps in a table with the same transpose value, and nothing else causes a change, the value is not reset.)

As a asshole musician i prefer the broken version jsut for character reasons..

http://blog.ntrq.net/?p=192

How else is it supposed to sound? Its basically the same as if you played an arp on a synthesizer and had a pitch lfo going.. sounds broken, but could def. be musical in the right hands.

all these responces, but no one has just picked up a game boy to try it out?

if still no one has done this by the time I get back from my daily soul sucking corporate experience, i will try it!

Yeah, I am in contact with him.

I mainly wondered what users' perception of operation was. I'd try to get my head around it and failed but I realised there's a distinct possibility that my lack of LSDJ experience/knowledge was the reason for fail.

I know I could ask Johan and he'd (most likely) tell me. However, despite what I've already said I don't want to "port' LSDJ to NES so I'd rather hear from users as to how they expect the program to behave.

Take the Pxx and Cxx command combination. I can see that it fails and I know only too well why, having spent a lot of effort in NTRQ making that combination work. But if people don't miss it because it doesn't quite work in LSDJ then it will help me design the coding for Pulsar's player.

I don't think I'm explaining myself too well. I have a cold, a man cold. :S

I think Nick is right, but I never did "nested tables"

i would say it would be logical if it went from left to right.

Neil the person you'd want to ask is Johan. He's actually very helpful w/ people with regard to that stuff.

Or in other words, it doesn't work...

Cxx and Pxx if i remember right makes a detuned sounding horrible arp