defPREMIUM wrote:
TDK wrote:

Not at all. C64's are 3 channels, Amiga's are 4 channels - same with the Nintendo's. It's the difference between using original hardware, and emulating it (or adding to it).

uuuuh srry but no each channel is 1 bits meaning 8 channels for 8 bits......... : /

Haha!

You're obviously making proto-classification wave, although I detect hints of genre-tag rock in there as well.

"Wandering Waves" and "Thunder Zone" are my favorites. Great playlist Aly.

FMDrive is fantastic, thanks again for creating it. My primary sound source for a few months now.

52

(5 replies, posted in Releases)

Glad to hear some good responses. This is the first track I've posted in a while.

Totally love FMDrive, it came at a time when I really wanted to use some typically Genesis sounds, and it doesn't disappoint.

53

(5 replies, posted in Releases)

Hello! This is a new song, made with the FMDrive VST. I also used the Korg M1 VST for the drums. Put it all together in Renoise.

Starts off as a melodic instrumental and goes into some heavier territory by the end.

Thanks for listening!

http://vainamoinen.bandcamp.com/track/o … s-surfaces

Honestly, don't force yourself to use something you don't actually like when you have an alternative that you're already comfortable with.

On the other hand, if you really want to use trackers, then just stick with it. Keep practicing. You'll get it in time. Just focus on one tracker to get comfortable with, and maybe try doing really simple covers of songs to learn the basics instead of immediately trying to write your own.

The only person stopping you from imposing chip limitations in a modern DAW with a piano roll is yourself, and you're also likely the only person who's more worried about the process than the end result.

It can be difficult to start from scratch in a tracker and try to improvise your way into a tune. Like some others have responded, I usually have something prepared before I begin tracking it. I think the difficulty arises from the fact that the latency of many trackers is unacceptable for jamming parts out live.

One tracker without that limitation is Renoise. It will allow you to play in real time like any standard DAW. I have had much more success with improvising in Renoise than say, Milky Tracker or Famitracker.

Use whatever works for you though, no sense in forcing yourself to track when you could do it in FL Studio with much less effort.

56

(4 replies, posted in General Discussion)

You could just try naming the sample something like "F", so you know it's an F chord you're playing when you press a C key. Or you can make the actual root note of the sample an F, so then it will play back as sampled at an F key.

If you find yourself in a situation where you need a C chord with something like an A in the bass, just use slash chords for naming, like "C/A".

It's all in the name.

The Aly James FMDRIVE VST is fantastic. Can't yet comment on his PSG VST yet, but I expect that to arrive soon too. They're both generously priced, 10 euros each, which was about 14 US dollars when I got them. Get both and you have the full Mega Drive sound set up, not to mention the ability to go way beyond the original specs.

Deflemask is a great little multi-chip tracker too, and it's free. I never got into using it, but just listening to the demos of the various chips in action should be convincing enough to know it's really accurate. I kind of want to try it out again someday, mostly for it's SID and PC Engine emulations.

58

(22 replies, posted in Sega)

This looks really cool! I just got FMDRIVE but I may have to pick this up sometime soon as well. Thanks for the great Sega VST's!

I received FMDRIVE yesterday and my first impressions after last night and tonight are fantastic! I'm so happy to have these sounds at my disposal.

I can definitely recommend this to anyone who may be on the fence about getting it.

You could always try Brian Eno's Oblique Strategies:

http://www.rtqe.net/ObliqueStrategies/Ed1.html

They'll at least get you to think a little more sideways about whatever you're trying to overcome.

You could always take what patterns you already have and try to flesh them out more. Let's say you have two patterns, one a "verse", the other a "chorus". Copy and paste the verse 8 times, then the chorus 4 times after that. Then go through and mute or or unmute the individual instruments as the verse plays out so that it builds into the chorus.

The transitions between patterns will probably be jarring, so you'll have to add variations to ease the effect. Think of the generic white noise swooshes that you've heard before a huge part kicks in during transitions in other tunes. These sorts of effects aren't necessarily melodic, so they won't really tax your creative juices if you've maybe been feeling unsure of how the song should progress. They're more like tools that you just have to program in. It's a good exercise to learn about some of the abstract possibilities of whatever software you use, and to think in terms of texture as opposed to notes.

You'll also have to have an intro, which can be a variation on the verse with minimal notes, like the difference between a plot outline and actually reading the story. You can construct an ending in the same way, just a final variation on the chorus or something.

You might still end up with a tune that's only a minute and a half long, but even then, you can probably extract some of the extra transitions and effects that you've worked on and tweak them a bit, maybe cut to half time or play around with weird sounds in order to make a bridge section. If that's even necessary; a lot of great songs aren't actually all that long anyway, and don't really contain much more than a few parts. At least classic pop, anyway.

I end up making a lot of one-pattern wonders. If I don't have much of a plan for a song when I'm starting it, it's almost guaranteed to end up just being a pattern long at first. It's not necessarily bad unless you try to wring too much out of a pattern, which I was guilty of a lot when I started doing electronic stuff on an Electribe. I always try to remember that my favorite old techno and Berlin School electronica musicians weren't working with much more than a 16 or 32 step sequencer and some overdubs.

Apart from any of what I said above, I still prefer to have written something already before I begin tracking it. There's something about writing on a guitar or keyboard that allows me to keep the flow going without getting stuck after a bar or two, so maybe try writing on another instrument before turning it into a chiptune.

I'm sure getting stuck immediately after beginning a song has something to do with the fact that not only are we trying to write a tune on the spot, but we're also programming instruments, mixing them, throwing effects around, juggling the roles of not only every musician in a band, but also the roles of the producer, engineer, and arranger, all the while comparing ourselves to others we deem to be much better at all those things than we can ever be. Sometimes you gotta say fuck it, this song is a minute long and it's finished.

62

(119 replies, posted in General Discussion)

Beer number five.

I got sleepy while trying to make some samples tonight and decided I'd go to bed, then I put off sleep to drink and here I am.

sandneil wrote:
Vaina Moinen wrote:

not smart enough to use GoatTracker

not with that attitude you arent!

Very true! I once thought I'd never learn how to use ANY tracker, and I definitely proved myself wrong there.

At the time I tried GoatTracker, I was still looking for chip-emulating trackers like Famitracker, and I was hoping for easy access to C64 sounds. Whew! I was completely overwhelmed by it, I don't think I even got it to make a sound at all. I only remember playing the sample songs that it comes with.

Anyway, I found my way to Milky Tracker and sample-based tracking, and that's served me well ever since. I certainly don't feel that I'm lacking for possibilities now with Renoise too; there are plenty of C64 VST's out there.

Maybe with more experience under my belt I could actually manage a few beeps out of GoatTracker should I ever try it again.

I  L O V E  Milky Tracker. I just got Renoise a few weeks ago, and it's light years beyond Milky, but I find myself making and editing samples inside of Renoise, and then using them to actually compose in Milky.

There's something about the simplicity of Milky that allows me to dig in and work on tracking and experimenting with effect commands. I really do enjoy using Renoise, but I don't feel like I'm really tracking with it, as I find it unnecessary to use the effects column most of the time. Renoise has many envelopes and built-in DSP effects which handle all the things that I would normally use the effects column for in a tracker.

Having said that, I have a lot of stuff written in Renoise that uses softsynths and large, chopped up samples, and I couldn't do anything like that with Milky unless I wanted a headache. I still prefer both Milky and Renoise to any standard DAW I've ever used.

Famitracker is great for what it does. Very easy to use. It's the first tracker I was able to fathom, and I've never deleted it from my computer even though I rarely use it anymore.

Deflemask is cool too, although I didn't enjoy using it. It's nice to have so many different chip emulations under one app, but there's just something about how it feels to work inside the pattern and instrument editors that puts me off. Much respect to it, though.

Sunvox is obviously very capable but I just couldn't gel with it. Same with Klystrack... and OpenMODPlug, and that one Sega Master System beeper-tracker, and a million other permanent-alpha project trackers that happen to be scattered about the internets.

GoatTracker induced a bout of vomiting, blurred vision, two hallucinations of my own death, followed shortly by my actual death, and then my resurrection with a note in my hand, which read: "You are not smart enough to use GoatTracker". Wish I could, though!