Mod Archive Forums Mod Archive Forums
Advanced search  


Please note: Your main 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.

Messages - TraumFlug

Pages: [1] 2 3
MilkyTracker Support / Re: screen problem
« on: January 03, 2011, 01:30:16 »
hehe just delete, in your home folder, the file ".milkytracker_config". yes the file's "hidden". open terminal, run "rm ~/.milkytracker_config" (no sudo!!!).

this will wipe all your mt settings, envelopes, paths etc, but the tracker will run again ;)

next version should really have a startup parameter to wipe all resolution&screen settings & make mt start at 640&480 windowed again...

MilkyTracker Community / Re: Mod help - Waveform info
« on: December 19, 2010, 17:10:51 »
nice idea!

but I'd say, best would be to place it into some sub-menu/popup of it's own, like the other "generators". I imagine it hard to integrate into the current drawing code & the like.

but wait, maybe just a function to warp an existing hand-drawn sample with an fft, treating the existing samples as bin magnitudes? that'd require least gui hacking.

maybe you'll find open-source libs like "kissfft" (small code size, works well) or "fftw" (large code size, but optimized like....for realtime) interesting for you project.

MilkyTracker Community / Re: Mod help - Waveform info
« on: December 18, 2010, 21:54:26 »
I don't know the mt sources too deeply, but read a little in it from time to time: have a look into "src/tracker/SampleEditorControl.cpp/h".

search for "drawMode", will lead you to the point, where mouse events are handled & the function are called (in "SampleEditorControl::dispatchEvent").

further down it leads to "SampleEditorControl::drawSample", where it seems the coordinates are translated, pushing them to the sample editor. change source file to "src/tracker/SampleEditor.cpp" (without "Control", now leaving gui/drawing code & entering the "guts"). "void SampleEditor::drawSample" does some more wrapping/interpolation, but go on yourself...

hope that helps, what do you want to do to the code (question out of curiosity)?

hey yeah, I'd love an up-to-date win.ce binary of milky, too. I've got an h4150 lying around here that linux sucks on (porting project seems abandoned before usable, a real pity) and just needs a new battery (old lasts like less than one hour or the like  :P) & is waiting to be milkyfied so I can finally find some time to get some tracks done when away from my pc.

can't build it myself, seems impossible from linux & my current pc is somewhat too weak to get this done in a virtual machine. in case I should really get some neater box soon where a vm is possible: do you know any links to downloads/documents on how to build ce apps like milky from win2k, or do I need to purchase stuff like msvc?

MilkyTracker Feature Requests / Re: Allow GUI templates?
« on: September 27, 2010, 00:23:04 »
dude, I'm not one of the dev's, but read the code a little: milkytracker's user interface is "hardcoded" in c++ as far as I know. sorry.

so there's no easy way to modify it, unless you learn how to code c++, understand the milkytracker source-code, and have lots of time (lots...). the only alternate user interface is for 320x240, supposedly for pocket-pc pda's small displays.

if you really, really care - take a look at the sourcecode "src/tracker/TrackerInit.cpp" to get some idea on how the interface is built up. consists of manual tweaking almost completely, but when being carefully and investing some time to understand it, you could, for example, swap some buttons, change their text, or redesign the whole interface even. you'd have to recompile the whole program after modifications, of course - giving you a second _complete_ milkytracker version with the changes you've made. subdialogues seem often managed in their corresponding source-modules, but I haven't been really intense on the sources due to lack of time yet to understand them fair enough to give you real advice.

by the way, I also think a more modular, configurable interface-code would be great, also for the input (keyboard bindings etc), but would involve MASSIVE work I another layer for the ui-setup to be read from configuration files, and some means to edit those properly. would be possible, but involves lots of hacker's manhours...anyway, it's great that it's opensource at all  :-*

MilkyTracker Support / Re: Same sample for different instruments
« on: August 19, 2010, 21:33:30 »

concerning "old school, 2nd generation trackers", only impulse tracker and thus clones of it like schism/chibi tracker can do that; fast tracker 2 and thus milkytracker can't  :(

it's a design flaw in the .xm format imho, sorry. I also sometimes copy a sample, blowing up file size when I need different envelopes, tunings, panning positions and such for it. but most of the time I try to use the one copy with heavy effect command usage to get the different sounds I'd like to accomplish out of it, but sometimes I also wish for either more effect columns or copied samples in different instruments.

better don't ask about implementing it in milkytracker, as far as I've seen it tries to orient itself strictly on the fast tracker 2 .xm format, and an enhancement like that would mean breaking compatibility with that format: all other apps that can load/play/edit .xm's couldn't handle those modules. yeah, including fast tracker 2, I bet there's lots of people with original ft2 in dos-emulators or on legacy machines, and I think it's the whole point of milkytracker to stay as compatible with this as possible. not just to be able to load all the old modules from the 90's, but also to be able to put new modules on a floppy, and send it back to yourself with a time machine to a point where milkytracker did not yet exist, in order to boost your whole musical development and such... ;D

MilkyTracker Support / Re: Resolution Issue
« on: August 07, 2010, 05:05:44 »
yeah, sure, when I've got time & enough space in my head to learn a few bits I'd love to contribute!

but another thing: I've managed to toggle fullscreen from shell, with a command. grip might find it useful to keep his settings, colours & envelopes he'd loose by deleting the config-file. thanks to inspiration from the posts above!!!

the command is, from your home directory, while milky is not running (it can't as it segfaults... :P):

Code: [Select]
echo 0 | dd of=.milkytracker_config bs=1 seek=542 count=1 conv=notrunc

and milkytracker will start in windowed mode next time you launch it!

[edit] I was probably a bit too optimistic as of the config file having a fixed byte-order

please do:

Code: [Select]
dd if=.milkytracker_config bs=1 skip=528 count=10

before trying the first command. if it gives you a "FULLSCREEN" in the output (with a lot of other stats data after it, but the "fullscreen10+0" should be first), then you can switch off fullscreen mode with the first command, at least I hope worked for my system & config. otherwise I can tell you how to find the right "skip" "seek" value yourself.

MilkyTracker Support / Re: Resolution Issue
« on: August 06, 2010, 20:14:07 »
open milkytracker.cfg (its benath milkytracker.exe) with a hex-editor of your choice. go to line 230...

lol, he's running linux, there's no .exe or .cfg...

I think under linux the settings are all stored in "/home/username/.milkytracker_config", try deleting it to make the tracker revert to default values (better backup before...see below).

heh, there's a "-fullscreen" command line parameter, but no "-windowed", 4 lines of dead-simple code in "SDL_Main.cpp" and you could keep your settings, starting milky with windowed mode enforced  :P

MilkyTracker Support / Re: Starting questions
« on: July 22, 2010, 23:48:00 »

1) the envelope handling is a bit "special", as it tries to do the same as fast tracker 2, and that had nutty behaviour in many cases. I'm not able to run mt properly at the moment to test in detail (hardware phrackedness in mouse, keyb, sound & video on my old system, no time to fix it), but iirc for the envelopes it's important to have the instrument number set or not for how it behaves. for example if you use the "3xx" command _with_ an instrument number, it will restart the envelope, without it will continue (you'll have to del the instrument number after entering the note for 3xx to make the envelope continue instead of restart). likewise, a note without instrument number next to it will restart the sample (of the last instrument used on that channel), but not the envelope.

envelopes go sustain-first and then loop. so if you place a sustain inside a loop, the envelope will progress until sustain, and when note-off is issued, it will ignore the sustain and loop it. if the loop is positioned before the sustain point, the sustain point will never be reached (unless you trigger the envelope at a position after the loop with an "Lxx" command, I guess).

the "rectangle" (please call it "note-cut" or "note-off") will do 2 things in regard to envelopes:

-1) it will break the "hold" of the sustain-point, making the envelope continue

-2) it will start fading the volume at some totally obscure rate specified with the "fadeout"-value in the instrument editor. if set to "cut" it will stop any playback at note-off, if set to zero, it will just make the envelope handle volume. everything in between fades out more or less slowly, useful for example for an envelope-loop that simulates somekind of echoe behind the sustain point, letting it raise/lower the volume periodically, while the "fadeout" makes it more and more silent over time.

[-3) if no volume envelope is turned on, the note-off thing will just turn volume to zero.]

2) as for "chipsample" creation (small loops) of samples, it's hard to get what you want without lots of practise. the sample size just determines for example how many high-frequencies ("richness" in sound) are preserved when playing a low pitch. the shorter the loop, the duller it will sound at the same frequency, in most cases. so length is not really an issue otherwise, let alone you manage to tune your chipsound correctly.
I'm not a big fan of chipsounds, too static sound imho, and have seldom used them with joy, but to get an idea, you could get some sample collection of synths and/or real instruments, find something that has an similliar timbre to what you want, and cut out from a part of that sample a loop of one "period" (i.e. the soundwave will repeat more or less, warping all the time, choose one part that is repeated at the position that sounds interesting for you, make sure you cut out from zero-crossing to zero-crossing, zoom in, highlight & hit crop). then do with many sounds, and look into how the waves sound & look like. that way you can intuitively learn what shapes sound like (mostly, heh heh...), and how to "draw" similliar loops.
generally slow/flat/round curves sound dull, and fast/steep changes in the curve will make it sound sharp, bright.
I'd advise you to use instrument samples from samplepacks or ripped from other modules first, to get the hang of tracking.

good luck, & make nice tunes  8)

MilkyTracker Support / Re: Starting questions
« on: July 18, 2010, 17:18:13 »
1) the rectangles are "note-off" commands. when a note is playing in that channel, and such a "rectangle" followes, the note is cut, i.e. turned off. when using envelopes with a "sustain mark", that volume/panning is held at that mark until a note-off command. you can enter such a note with the key right next to your left shift or above the tabulator key.

2) there's many ways to create samples, so your question is too generic imho. how do you try to create them, and how does it differ from the sound you want them to have? creating good samples is a very delicate art, btw.

3) normally the playback speed of rows is linear, unless changed by special commands. for example if the first letter of the command is an "F" with 2 numbers behind it, it changes the playback speed...from the moment it is issued until loading a new song or another "Fxx" command is issued. a special case is the "EEx" command you meant in slumberjack: it will make the row it's last longer, speed is not really changed but it just stops playback for an ammount of time and then resumes. another note to slumberjack: did you notice the "E60" and "E62" commands? that's a "pattern loop", breaking the global sequence deliberately. but don't try to mess with pattern-breaking commands as a newbie too much, try to concentrate on the music, and volume/portamento effects first.

also I'd advise you to download a keymap and effect-command reference and print it out. there's good ones on the homepage, under documentation the "quick reference printout"-pdf's. it's 2 pages, and really worth the paper, as all keyboard commands are on one page, and all effect commands on the second.

happy tracking!

Pages: [1] 2 3