Search options (Page 125 of 137)

Yes! And what I want to do is close it!

Simple answer: two channels. Plase a hit on the noise pulse channels at the same time. The pulse hit should probably have something like velocity, 91-92. Maybe decrease the length parameter. Pulsewidth: 50%. Either use a suitable sweep or place maybe a PF3-PFA command. Note: Maybe G-5 - G-6.  The noise hit, I leave to you to figure out.

Edit: Shape -> sweep

I'd be up for some detective work, unless arfink really really wants to.

No sound.

Also, a (not so) subtle plug for gbdev.gg8.se
http://gbdev.gg8.se/2010/08/gameboy-emu … avascript/

Remember kids, anything with a square wave is chiptune!

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.)