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]
I've just compiled mt 0.90.85 on an ubuntu 9.10 system with self-compiled jack 1.9.5, and finally...jack works!! :D

it's working really well, I've just tested at 88200 khz rate, and milky seems to be able to handle that, no aliasing on high-pitched notes that _did_ alias badly at 48000 with the cheapest resampler! strange that sdl/alsa drivers don't offer >48000 in the gui while it's working with jack, maybe that should be fixed?

well...the problem: sometimes with jack in rt mode (happened at 48khz, so I doubt it's related to an unsupported sample rate), when I click around the system and reenter the mt window, the player becomes unresponsive to input! gui updates well, sound is gap/xrun-free, with cpu around max (it's a slow pc), but keyboard and mouse input won't respond for long times, like it takes half a minute after I clicked something (also the wm close button) for mt to respond, keyboard also lags like that. working is impossible when it happens (other than listening to the song & watching the gui).

I'd really like to get that fixed, because it's annoying. anyone got ideas on how to solve this prob?

btw, how does milky do its mixing & passing data to jack? jack works with 32bit floats, I hope the mixing isn't 16bit integer & then converting to floats (but I fear so...)

MilkyTracker Tracks & Songs / milky tracker made my day(s) - bofba
« on: February 07, 2009, 22:40:12 »
just a thing I began in 2001 with ft2, and then after 8 years without trackers was "finished" with milkytracker

a bit different to what you're used to hear here normally I assume...let me hear what you think about it anyways!!

MilkyTracker Community / Re: Tuning Help?
« on: February 07, 2009, 17:47:41 »
tuning samples properly may seem senseless to people who just want to create tunes and listen to them one after another, but imagine following examples:

- a dj wants to mix 2 tunes in sync, so he better makes sure both tempo and tuning of both tracks match in a way that makes them sound good together. modern dj mix tools might have pitchshifting/timestretching to make that task easier, but many are proud of their skill to match songs with pure replay-speed adjustments

-you have a song, and want to include recorded tracks, like a guitar solo or whatever. though the samples can get very long, and it really bloats up an .xm, it's possible. I've already done this, and it works well (unless the sample is very long, and the tracker doesn't check for sample size, causing it to crash due to some overflow - I've had that with jeskola buzz, making a not-backuped song impossoble to load, because saving the .bmx seemed to work) only problem is that the track can't be changed in speed, unless you use a timestretching tune on your recorded parts.

the best sollution is to create an instrument with a simple beep as looped sample. probably a sinewave, or whatever you fancy, and make sure it's "A" is tuned to 440 Hz. save it as "tuning.xi"
and load for every song you build, tuning each new instrument to that sound. I could imagine making a pattern where this beep is triggered in the beginning, in the pitch you think works best, or that is appropriate because you have a multisample instrument. now you let that pattern loop and "keyjazz" the same note in the instrument/sample you want to tune. you need good ears for that, it's similliar to tuning a guitar without help of a tuning gadget: if you think the result sounds "wobbly" or "spacy" a little, i.e. pulsating readjust until the pulsing gets slower. the slower it is, the closer both sounds are together; in ideal conditions you won't hear any chorus-like effect, because both sounds have the same base-freq.

MilkyTracker Community / Usual Volume levels for .xm modules
« on: February 07, 2009, 16:02:23 »
hi people!
finally a tracker which is not only compatible to ft][, but also has an interface that looks & feels like ft][, and even the "same" keyboard commands. after years of abstinence from any .xm editor I have now motivation to dig into my collection of unfinished tunes, which lay dormant for so many years...

anyways this is just about  a simple question: how is by convention in the/this scene (or whatever) the usual volume of a .xm module (i.e. of the loudest sections in a whole song)?
I'm asking because I noticed that most of my own .xm files distort by mixer clipping in the standard mixer volume setup. i've had to toggle amplification to 25% and mixer volume to somewhere between 60% and 70% in order to play my works without clipping. this applies also to the .wav recorder. this seemed strange to me, as original ft2 never clipped, probably amplifying each channel by 100% / number_of_channel (which also meant that adding channels reduced overall volume of the whole song, can't remember correctly, since it's years since I last used original ft2, but I think it was this way). I'm using milkytracker under ubuntu 8.10 with SDL driver, as installed from original repositories.

I'm asking because, being treated with a free, open source piece of software that I really like I wish to share my music with other people from the scene associated with it, and nothing could be worse "first impression" for the listener of a tune than getting his ears bust by levels higher than he's used to listen, or having to listen to a distorted piece, probably thinking it was composed intentionally that way (...hmmm, sometimes it can fit nicely, but not always, you see...). with sharing in mind I wish to reduce levels of tunes I want to share to something that is usual, for example by de-amplifying the samples (instrument volume won't work, because it's overridden by volume commands...). back those days I seldom listened to other mods, and used "bad" technics like normalizing every sample to 100%, or doubling a bass channel to make it more present.

maybe you could treat me with links to .xm-files that you think are leveled properly, so I can compare and adopt my tunes.

thanks in advance :)

Pages: 1 2 [3]