Hello all and thank you for reading Paul’s Tech Talk on The ChipWIN Blog!
This article is the second part of an issue on the spicy topic of PSG Chip Overclocking. In the first part, we tackled the basic theory behind what overclocking could achieve on an NES when ticks sped up enough to reach into the audio range. Today, we’re going to try and be more specific, and try out some practical examples on Gameboy.
Hello beautiful people and thank you for reading Paul’s Tech Talk on the ChipWIN Blog!
Today we’re going to talk about a very special version of LSDJ, and a tracking method that cannot often be used on Gameboy, but flourishes on other platforms such as NES: ~ OVERCLOCKING ~ ♪♫
During the avalanche of updates that gave light to this column in the first place, the community was hard at work trying to sniff out bugs and offer feature suggestions of their own. Some were very daring, seemed almost impossible, but were still considered by Johan for integration. One of them was actually the notion of underclocking. Why make the gameboy even slower than it is, you will undoubtedly ask? Well there is one limitation of the Gameboy hardware that theoretically could have been overcome with this method: its note range.
Hello all and thank you for reading The ChipWIN Blog!
In the last issue of this column, we tackled the infamous 5.1.0 LSDJ update and dwelled on the theory of what it brought to the table. To cut it short, it all boiled down to a complete redesign of Pitch behaviour. What the community did not expect, was all the ramifications and ripples it would have, and it ended up being a highly controversial update, to which many would actually choose to turn a blind eye.
If you haven’t already, I suggest reading the first part of this article before delving into this one, just to get familiar with what’s at stake. In this second part, I will first spend some time going over the specifics of the all-new L command also introduced in 5.1.0. Then I will go over how I view the anatomy of Kicks. And then, finally, I will try to get more practical, and give several examples of how to work with LSDJ 5.1.0 and above to utilize all these new features to the fullest.
Hello beautiful people and thank you for reading Paul’s Tech Talk on The ChipWIN Blog!
Today we’re going to tackle one, if not THE most groundbreaking update that happened to LSDJ in the midst of all its crazy transformations. With 5.1.0, Johan Kotlinski decided to rewrite the entire pitch behaviour in LSDJ from scratch. For the sake of this article I’m going to try and keep an unbiased point of view. Even though I am pretty partial to the newer versions, I still use the older ones as well. But it’s safe to say that this update was probably the most controversial of all, and it ruffled a few feathers in the community.
In music in general, but more particularly from a software perspective in LSDJ, Pitch is a solid foundation on which a lot of elements are built. And even though LSDJ is a shining example of software ergonomics and accessible design, its complexity still gives it a bit of a learning curve. The 5.1.0 update shook things up so much that artists would either have to relearn a lot of tried-and-true techniques that would now work just as well but very differently, or refrain from upgrading altogether, deliberately missing out on later updates and bug fixes.
Long story short, for a lot of people, upgrading to 5.1.0 and above would break songs from older versions and render quite a few staple sound design techniques obsolete. Let’s take a quick look at what has changed and get a better grasp of the situation.
Hello people and thank you for once again reading Paul’s Tech Talk on the ChipWIN Blog!
Today we’re going to finish the two-part article about LSDJ version 5.0.0 and the wonderful new Commands it came with. Last time, we delved into the new possibilities offered by the Pulse [F]inetune Command, so don’t hesistate to read that one first if you haven’t already!
Today, we will focus on the upgraded W command, which can now control WAV channel instruments. Buckle up!
Just like the pre-5.0.0 F command, W already existed in LSDJ before. It was a very handy command that used to work only in the Pulse channel and controlled Pulse [W]idth Modulation (or PWM for uppity initiates, pronounce “Pwuhmmm”). Even though the Pulse channel Width parameter was only limited to 4 values, (12.5%, 25%, and 50%, with 75% being the inverse phase twin of 25%), being able to control it thanks to the W command opened up a lot of bleepy sound design possibilities. Using and abusing this command has always been, as far as I can remember, a staple of the LSDJ workflow.
Cycling through the 4 Pulse Width settings
But we’re not here today to talk about Pulse channels. These have been thoroughly accounted for last time already. Time for the Wave channel to shine! As true as it may be for the distinctive squarewave sound of the Game Boy Pulse channels, LSDJ probably wouldn’t have been nearly as popular if it didn’t allow us to tap into the nigh-infinite power of the Wave channel.
Hello people, Paul here for a new issue of LSDJ Tech Talk. Today we’re going to look back on LSDJ version 5.0.0 and all the good things it’s brought to the table. Buckle up!
With 5.0.0, the big round number started garnering interest in the community and the wave of updates got more and more feedback. Funnily enough, despite being a big round 5.0 and even though this version introduced some pretty nice upgrades, it wasn’t yet significative of the complete overhaul that was still in the making. Johan K just happens to add +0.0.1 to every new version, regardless of how big the changes are. BAMBOOZLED!
Don’t get me wrong, those upgrades were big too, very useful and very anticipated. It’s not everyday that LSDJ gains 2 new Commands to play with!
In today’s article, we’ll mainly talk about the upgraded F command.
For more accurate info on how LSDJ commands work, have yourself a big ol’ cup of RTFM and click HERE, for all relevant version manuals.