entry for chipyxa6:
http://chiptown.ru/chipyxa6/pages.php?type=chipyxa&page=readcomments&id=18
Long time no see, xaimus.
This is a strong piece, I enjoyed it.
Is it some contest boundary, this 100 kb ?
yeah, 100kb is the maximum file size in the competition
awesome stuff. hard to believe this is 100k.
Quote from: "Jojo"awesome stuff. hard to believe this is 100k.
+1, or even "адинадин"!
Man, this is another stone to the edifice of MPT's glory!
In other words: you once again proved that MPT is ideal for breakbeat :welldone:
great d&b piece xaimus!
I hate restriction rules :D, we had been very limited on trackers so many years (both, processing power and software). Now, that we have fairly unlimited possibilities, people are desiring for limitations again. :lol:
2 psishock
Well, one could see it as a challenge of one's skills.
Never felt limited on trackers that much, I had a drive of my own to make files as small as possible anyway.
Now, with the almost unlimited possibilities, I think sometimes it goes far beyond the other way, having a file of >200 MB for a piece of 2:30..
Quote from: "Sam_Zen"I think sometimes it goes far beyond the other way, having a file of >200 MB for a piece of 2:30..
There you go, one of the main disadvantages of the rendered samples :), one of the reasons why should the sound stay in its synthetical form. But ~200mb/song can still be alright when you have a bigger HDD, and you just need/love to work with samples.
My OMPT songs are taking nowdays about 300-700kb space. Renoise seems to be able to compress the stuff even more, because it manages to store the same things in 100-200kb (samples aren't involved in both cases).
you surely sound like you can't do good music without your "pro-VSTis". :P
i love small mods, and those restrictions make them even cooler. showing what you can do in 64k or 100k is awesome, many tunes sound so much better than you expect them to sound.
Quote from: "Jojo"you surely sound like you can't do good music without your "pro-VSTis".
:insert proud looking psi smiley here: :D I could of course, like i did for many years, but my job is much-much more easier and the possibilities are more "wider" now that i've discovered the technology. It's not just about "my personal pro-VSTis", but with most VSTis and VSTs in general. Think about it, if you got sample, you are mostly "stuck" with the given sound. You can't finetune or reshape it totally for your needs. Also the sample will mostly sound exactly the same every time you will play it, but the VSTi can be dynamic and can change the structure of the sound with every new note (or time based). That could give a much more "living" experience to the listener.
Don't get me wrong, i love the cool small (and even the big) mods too, and highly value the creative tracking skills from any person. But personally i'm just more like a freedom friendly tracker, than a (strict) restriction lover. And i am far from disregarding the sample usage, just not preferring it recently.
Quote from: "Jojo"many tunes sound so much better than you expect them to sound.
One of the reasons why I could keep the trackers small was the fact, that I could use even 22 kHz samples, without losing evident quality in the result, because OMPT appeared to have an excellent subsampling algoritm.
this is really good
and the coding very impressive. It was cool to watch it play in Open MPT
editor
How did you keep the drum tempo the same when the pattern was shrunk and slowed down?
I didn't see any loops... so I am mystified and really impressed.
QuoteHow did you keep the drum tempo the same when the pattern was shrunk and slowed down?
uh... isn't that quite "normal"? The drums are chipped so if the tempo is high, there's more space between the single notes than when it's slowed down. i don't see a need for loops here.
I'm sorry - the explanation doesn't make sense to me
I'm no a good module coder
what I saw was that the pattern visibly slows (to half speed or less) and the incidence of notes do not increase...
so how can the percussion tempo be the same?
solo channel 1 on patterns 13/14 and you'll see... hopefully. :P
@uncloned:
when the drum loop (or any other sound in fact) is in sample form, the pitch and the time length won't shift with tick/row/tempo change, basically will sound the same no matter what will you do.
So in his example, the tick/row was 6 and when he just coudn't make the fast slice changes on that speed, someplace just switched it to 3 and the tick went on with double speed. That meant double precision, but naturally the pattern length is needed to be doubled from from 32 to 64 to be able to fit every note.
About the same effect could be archived with double bpm, and maybe he could do the same on constant tick/row, but with delay (SDx) and another channel involved.
I hope this could make a sense for you. It is quite a "basic" "techonogy" for me also, as Jojo stated, but will help naturally if things are not clear.
Hi psi and jojo
I stated there was no loops in this - but indeed there are two - they just were short enough that they were not as evident visibly.
However... this stuttering through the loop is new to me.... and look at and compare patterns 15 and 16 channel one to see what I was talking about.
well, that's exactly what i was talking about. the beat is sliced up into pieces. so the peaces could be BD, SN and HH. at normal speed, your sequency would look like:
BD
--
HH
--
SN
--
HH
if you play it at half the speed and still want to have the same BPM, you have to write
BD
HH
SN
HH
i.e. leave out spacing.
Quote from: "uncloned"this stuttering through the loop is new to me
Fear not, this is actually pretty simple stuff, you will understand it fast. Maybe you need to try out yourself and play with doubling and halving the tick speed to see the results.
Quote from: "uncloned"and look at and compare patterns 15 and 16 channel one to see what I was talking about.
Well, i just knew you will mention this :D. Ok so what is happening on those patterns?
xaimus halved the "default" speed (6 tick/row) with setting the tick/row to 12 now (A0C effect) possibly because he had a fun and thought that he could put together those slices even on that speed.
Basically he could do the whole song on the fastest 3 tick/row, everything would sound the same, but the optimization was needful in this case to fit on the 100k limit. That's why he went to faster speed only when he couldn't (or wouldn't) make the wanted sounding in any other way.
well its pretty neat coding as far as I'm concerned.
when I do modules it is a far simpler affair.
Thanks for the explanations!!!