471
The Lobby / Re: Hello...
« on: September 20, 2008, 01:08:34 »
Hehe.. "tracker".
- June 26, 2024, 02:05:09
- Welcome, Guest
News:
Please note: Your main modarchive.org account will not work here, you must create a forum account to post on the forums.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
472
MilkyTracker Support / Re: fadeout and keyoff
« on: September 20, 2008, 01:07:39 »
Shouldn't be.. The lesser the fadeout value, the slower the note death.
473
MilkyTracker Support / Re: How the hell do I pan?
« on: September 20, 2008, 00:57:17 »- Using the per-sample setting in the Instrument Editor. (static)
- Using panning envelope. (changes over the course of played note)
- Using pattern commands 8xx and Px (to set) or Pxx and ◄x/►x (to slide). (dynamic)
474
MilkyTracker Feature Requests / Re: wave edito filter please
« on: September 20, 2008, 00:51:15 »
We accept. Now, go make.
475
MilkyTracker Feature Requests / Re: wave edito filter please
« on: September 18, 2008, 13:06:44 »
Have you tried the EQ? It's not filter, agreed, but more effective than smooth and boost for that purpose.
476
MilkyTracker Community / Re: sample copy paste problem
« on: September 18, 2008, 13:05:14 »
MilkyTracker automatically adjusts the relative note and finetune values (in the Instrument Editor) for samples when they are loaded but not when you copy a snippet and when paste it into an empty slow. That one stays with the default 0 values.
You can continue working like you already do but then you have to manually adjust the aforementioned values for the new samples so that the pitch is the same across all of them.
Another way to quickly have the same settings on multiple slots is using the instrument copy dialog (the Copy button in the Instrument Editor) if you first clone your sample in multiple slots, the settings are carried over as well. How you proceed is your choice. One way is to crop each sample how you like..
You can continue working like you already do but then you have to manually adjust the aforementioned values for the new samples so that the pitch is the same across all of them.
Another way to quickly have the same settings on multiple slots is using the instrument copy dialog (the Copy button in the Instrument Editor) if you first clone your sample in multiple slots, the settings are carried over as well. How you proceed is your choice. One way is to crop each sample how you like..
477
MilkyTracker Community / Re: Hello I am a new user!
« on: September 17, 2008, 14:13:27 »
Hello there.
Here are some intelligent answers:
The source code for the v0.90.80 release is on the download page, on the bottom of the MilkyTracker box. But to take part in active development, you probably need a more recent snapshot and/or Subversion access. For that, come chat on the IRC channel.
How can you help? You name it! Is there something you wish to contribute? A port? A feature? A bugfix? This is what you're going to be asked anyway when you ask for the up-to-date source.
No dedicated forum, we're one (not that) big, (mostly) happy family. Post on these boards or join the chatroom.
Here are some intelligent answers:
The source code for the v0.90.80 release is on the download page, on the bottom of the MilkyTracker box. But to take part in active development, you probably need a more recent snapshot and/or Subversion access. For that, come chat on the IRC channel.
How can you help? You name it! Is there something you wish to contribute? A port? A feature? A bugfix? This is what you're going to be asked anyway when you ask for the up-to-date source.
No dedicated forum, we're one (not that) big, (mostly) happy family. Post on these boards or join the chatroom.
478
MilkyTracker Community / Re: Instrument
« on: September 14, 2008, 14:58:14 »
You can't edit the envelopes with commands but you can change a note's volume envelope position. Lxx works beyond the second loop point (unlike 9xx) which makes it possible to have two volume envelope behaviors for one instrument. One inside or before a loop and one after.
You can create an alternate sustain point in the latter one by setting Lxx outside your envelope entirely. Then the envelope won't be followed, the note will just play at the volume of the last point in the envelope and a key-off will fade it according to the fadeout value.
I attached an example image from one of my own songs. The volume envelope is a very simple rhythmic loop between points 0 and 18. At point 19 I have a "useless" full volume point. Normally when a note is played, the volume will pulsate according to the envelope but when I couple that with an Lxx command where xx is 19 or higher, I get a sustained note without the loop. (I use L20 because one digit is simpler and faster to type in than two.
)
You can create an alternate sustain point in the latter one by setting Lxx outside your envelope entirely. Then the envelope won't be followed, the note will just play at the volume of the last point in the envelope and a key-off will fade it according to the fadeout value.
I attached an example image from one of my own songs. The volume envelope is a very simple rhythmic loop between points 0 and 18. At point 19 I have a "useless" full volume point. Normally when a note is played, the volume will pulsate according to the envelope but when I couple that with an Lxx command where xx is 19 or higher, I get a sustained note without the loop. (I use L20 because one digit is simpler and faster to type in than two.
)
479
MilkyTracker Community / Re: Spd?
« on: September 14, 2008, 02:35:26 »
You're not wrong, that's what I was trying to say. Of course your near-120 BPM is easily made near-60 or near-240 depending on how you space your rhythmic notes (base kicks for example). You can think of the song speed as sequencer resolution in that sense.
An older version (1.5) of Renoise had this useful display (Song properties) of the actual BPM while the tracker itself works with the BPM/Spd values. The BPM display has 4 decimal accuracy so whenever it shows x.0000, you've hit a proper real world BPM value. I haven't been keeping up with Renoise that much lately as I've been pretty much preoccupied with Milky but I think the more recent versions are in fact operating with real BPM, so you cannot use them to look up tracker BPM/Spd vs real BPM equivalences.
An older version (1.5) of Renoise had this useful display (Song properties) of the actual BPM while the tracker itself works with the BPM/Spd values. The BPM display has 4 decimal accuracy so whenever it shows x.0000, you've hit a proper real world BPM value. I haven't been keeping up with Renoise that much lately as I've been pretty much preoccupied with Milky but I think the more recent versions are in fact operating with real BPM, so you cannot use them to look up tracker BPM/Spd vs real BPM equivalences.
480
MilkyTracker Community / Re: Spd?
« on: September 13, 2008, 19:58:55 »
The basic time unit in traditional trackers is a tick which comes from the original implementation on Amiga computers where trackers began. The Spd value is actually the number of ticks per row, or a line of text you see in the pattern editor.
The BPM value has a misleading name since it controls the duration of ticks, not actual beats per minute. Setting Spd to 3, 6 or 12 makes BPM appear almost like actual BPM value, but it's not entirely accurate. Only a handful of Spd/BPM combinations result in song speeds that are synchronizable with modern sequencers. It's a little unfortunate but you can't rewrite history. :/
Some pointers on Spd values:
Using Spd 1 is not advised because it renders most pattern commands nonfunctional. This is because notes are triggered on the first tick and commands mostly come into effect on the following ones. If you only have one tick per row, they'll never get their chance.
If you're into making chiptunes and you like the sound of the 0xy arpeggio command..
That's because a tracker arpeggio is made of 3 notes, the base note and 2 offsets. If you choose a Spd where those 3 notes aren't spread evenly among the ticks of your rows, some notes will get more attention from the replay. But that's a subjective thing, really. It may well be a desired effect sometimes.
The BPM value has a misleading name since it controls the duration of ticks, not actual beats per minute. Setting Spd to 3, 6 or 12 makes BPM appear almost like actual BPM value, but it's not entirely accurate. Only a handful of Spd/BPM combinations result in song speeds that are synchronizable with modern sequencers. It's a little unfortunate but you can't rewrite history. :/
Some pointers on Spd values:
Using Spd 1 is not advised because it renders most pattern commands nonfunctional. This is because notes are triggered on the first tick and commands mostly come into effect on the following ones. If you only have one tick per row, they'll never get their chance.
If you're into making chiptunes and you like the sound of the 0xy arpeggio command..
Quote from: the Manual
it is wise to use a song speed value divisible by 3 in order that the arpeggio sequence can loop smoothly.
That's because a tracker arpeggio is made of 3 notes, the base note and 2 offsets. If you choose a Spd where those 3 notes aren't spread evenly among the ticks of your rows, some notes will get more attention from the replay. But that's a subjective thing, really. It may well be a desired effect sometimes.