Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

User Interfaces of the Demo Scene

datagubbe.se

Post reply on HN
Print view View original

81–83 of 83 posts

Re: User Interfaces of the Demo Scene

#81

Post by spankibalt »

tosti wrote: post #72
superted wrote: post #25

I vividly remember FastTracker II, and how intuitive and tactile it felt to get things done in it, despite the minimal user interface real estate. As an example, there were no sound effects. So, I routinely manually created echo effects by copying the sounds from one channel to another one of the available channels, offsetting the notes by a few ticks and lowering the volume. It was simpler times.

Intuitive? I never thought anyone would ever describe something as arcane as a tracker intuitive. I can't think of something worse. Pure Data comes close.

If you have no serious problem to wrap your head around the columnar presentation of data than "intuitive" is not an unapt way to describe the whole deal. Say, where music theory and practice intersect with something like a spreadsheet, for example... two things one might've already been exposed to before.

Re: User Interfaces of the Demo Scene

#82

Post by 5-0 »

tosti wrote: post #80
5-0 wrote: post #79

Earlier quoted context omitted.

Loading a module and playing it in a tracker is how I learned to make music. You see what notes and samples are triggered when and whatever effect commands are used to make it sound the way it does. Besides, once you've memorized screens and hotkeys (which happens pretty fast, because there aren't that many) you don't need it to be intuitive. A couple of years ago I downloaded SchismTracker. The muscle memory from Sc…

So you basically brute-force your way through? Like, you load or generate a sine wave as a sample and just keep changing the numbers until you've got a rough idea of what does what? I guess nowadays it's easier to read the source code of mikmod or milkytracker. But back in the day, heck no. MIDI sorta worked, but not great. My recordings were an awful mess because the timings were always slightly off such that it was…

Being an impatient teenager, I did brute-force the note-key layout, but I didn't have to - each context/screen had it's own help page. You could view all screens (and their respective shortcut) by pressing ESC.

I'd rather label it "experimenting" than "brute-forcing", testing what would happen if I were to put this or that value to this or that effect. Perhaps others would do it differently but I'd go by ear almost all of the time and adjust bit by bit.

Since you could save samples from downloaded modules, you could quickly build a starter library - although "ripping" samples was considered "lame". In lack of (expensive) synthesizers, some musicians would buy Sample CDs.

In my experience (90s Sweden), of those fortunate enough to have a home computer (usually a 486 66 MHz w 8 MB), few also had MIDI. I knew of one person who ran Cubase on Windows 3.11 with hardware samplers etc, which I found immensely exotic!

Post reply on HN