Search options (Page 125 of 137)

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

A sharp knife, a round file, a steady hand and some patience can get you a long way. This is probably not placement you're going to us, but the picture might work as inspiration:
This is the placement I chose. It's attached with this super glue. For this particular one, I had to remove the speaker and bend the connection pins on the jack, so it was a tight fit.

Then I used a knife to make  rough hole. I started out with a smaller v-shaped hole and worked my way down to vertical cuts.

Here comes the cheat. I used a round file to even out the hole. If you don't have one, you just have to buy one.
Also notice that I've removed some of the plastic normally holding the speaker in place.

Here's what it all looked like when assembled. For this particular method, you really need align everything correctly, since the glue dries instantly, and the hole can't be undone. In fact, I misaligned the Prosound jack on this one slightly by putting it too far into the GB, which means that most 3.5 mm plugs won't fit unless you press them in firmly, and they tend to fall out. This could've been avoided if I had just placed the jack 1 mm farther out before the glue dried. Lesson learned though.

However, for what he used it for, it would've been much more compact to define a groove and just have one transpose value on each row. So if your chord is 00, 00, 00, 00, 03, 03, 03, 03, 05, 05, 05, 05, 07, 07, 07, 07, 0A, 0A, 0A, 0A, 0E, 0E, 0E, 0E what yo can actually do is just enter 00, 03, 05, 07, 0A, 0E and use a groove which just has 4 in it. Use the G command in the table to activate that groove. That will wait 4 ticks between every step.

What's more, you can use this to easily make groovy chords by entering a groove 5,3,4,2