Music Sync
We used to often publish educational
materials on writing music (ZX-Guide
#4.5- music theory, ACNews #14 -
how to make an echo, ACNews #26- music for─
data samples, ACNews #27- how to use─
Pro Tracker'om, ACNews #28 - where
take the rhythm, ACNews #47- how to adjust
glides). Continuing the tradition, let's consider
question of writing music for the demo.
Events take placeFebruary 5, 2015,in
New View 48K demo writing time.
nq> I can make demos faster─
tracks for the timeline, you can make it for me
such a plan?
Alone> Not yet, but there is a script.
No graphics, and effects are only polo─
half the fault. But for now we can sketch out the topics
do - you don't do that?
nq> If you need to pull something out of your head and
without specifics - long and painfulsemi─
is expected. With the plan I’m in almost 1.5 days
I can give everything away.
Alone> Even before mounting the demo it’s unclear, boo─
children 2 tracks or 3 - it’s 48K, there’s memory
always ends suddenly)
nq> Again! For demos it is always only in
plus goes - when the effects are worked, under
they create a track that is clearly depicted─
tears every part, it is written exactly under
specific scene.
Alone> However, sync is best done
to ready-made music) The very type of effects is mo─
May vary depending on the music. It is necessary
so far 1 pattern for each topic. I am so
did The Board.
nq> I heard about this, but! can you imagine that
you have a track, it's written in quantities
patterns for each scene. And so you take
some part and imagine it - conditions─
but 4 patterns, dynamics, development - that’s all
you display it in the plan as if it were written
everything, and then I do it according to plan.
Alone> I understand) But I didn’t even
I know how long it will take what de─
crunch and what a load. This is not a demo
cartoon for 128K)
nq> Then I suggest making a track after ka─
some conditional readiness - half ef─
fects or 70%. Because I need a plan)
Almost all the demos in which I took part─
Lately we've been doing things like this
plan - some of them have not yet been released.
The theme works :) I'm talking about the conditional
division, it doesn’t matter if the patterns suddenly
some kindthe parts became not 4, but 8 - the main thing is
the point is in the patterns - these 4 fall into the topic, and
extending them to 8 is a matter of technique.
Alone> There is another option that I will write a group─
Bo, and it will be necessary to make an arrangement, but this
will greatly distract you from coding. The main thing is that
The topics themselves were on point.
nq> I need to describe everything more accurately :)
Alone> Maybe mock-ups of screenshots?
nq> They are also needed, but I still need them
at least some plan so that I know approximately how
develop the track, which parts go one after the other
another, that is, it’s simply a must have. Head─
cool joke - then references for all this
find :)
Alone> The key effect will be even more difficult,
than in Mission Highly Improbable - so much so
to the extent that there was nothing similar at all─
go.Plus for him you will need to draw a ku─
chu graphics. That's the problem with complex effects─
effects... Therefore, probably, SaiROOs himself
I wrote music for myself... What to do with the muses─
whoa, if there is a week left before the party, part
effects are not ready, and you need to do a feature?
nq> It's like launching spaceships
at random from the ground to get into orbit in
space station) Need an accurate calculation
me...
Alone> You can’t see the end result
anyway?
nq> Yes, but I need a motion vector, and I
I want to play out the scenes as accurately as possible, and
don’t rewrite it over and over again when
the scene changes 10 times.
Alone> How will you do this if in advanceyou don’t know how objects and the camera move?
nq> No way) I won’t write until there is
more or less clarity.
Alone> Licking is always important. We need those─
steel assemblies...
nq> Isn’t my approach better than what
Yerz offers you? He's just a pi─
He says what he wants, and you adapt. And I
I suggest joint prescribing for each
I blow part, subject to the plan.
Alone> With Yerz everything is simple - he immediately
gives a track. He writes them in advance and a lot. Ino─
where they made small fixes to the track (you’re stupid─
throwing patterns).
nq> But my plan essentially ties you up
hands, isn't it? As a demo coder. Where you are
“I took what they gave”, now you can buy it yourself─
nite and wait, in the end, more accurate
fixed
Alone> For this method you need to melt in advance─
nirate absolutely all movements and all precision─
ki binding is very difficult until the effect
not ready. The most I gave to Yerz
in advance - pace and mood. But in the end
perfect fix. Even when scrolling in the credits)
nq> So, imagine what you know
tempo, under the tempo conditional amount of pattern─
new - in general, I’m not convinced :) I’m telling you, there
where 4-8 can always be 8-12-16, this is
corrected on the fly, as soon as some part
ready and you can substitute it for the track
- editing is done after the fact. Dynamic subst.
swarming one under the other is a pleasure
because this is precisely what the process entails─Xia. Don't you get a kick out of it if you get it?
exactly the code for the restrictions? In this case─
due to restrictions in the number of patterns, on─
example.
Alone> I told you, I don't have fun─
effects from the process. It's just a job...
I have to do it. There the fix goes more tone─
to, than under the patterns. Somewhere there are drummers, somewhere-
then the accents, somewhere the instrument comes in...
nq> So I can do something similar
fix, if you need to somehow beat something -
it will all appear in the track.
Alone> Correcting sync in a track is more difficult than
in the script!
nq> This is a mutual process: you rule with
for my part, I ideally for mine, we should─
zheny work better than when you just
you do it to the finished track. In the end
we are talking about conditional parts, like you
do you want to have in some part
fix for drums, or melody, or arpeggio
- I, relatively speaking, do this part for you,
so that it simply exists in the right place─
ste, and you sharpen the rest for it─
no fix. In my understanding, the demoplan is
under construction.
Alone> So I’m talking about what is needed in parts)
nq> I just ask that the parts be available─
cut down the development of the track so that I wouldn’t create it
demo, and demo created the track. That is, so that I
didn’t bother yourself with a THOUSAND OPTIONS,
how to start a demo or how to start the first one
part, but just looked at the demo plan - intro
4 patterns, at the end of the 4th pattern, conditionally,
from the 32nd line -fill and transition to part
1. Part 1 - 8 patterns... and so on,
Due to the availability of parts, dimensions may vary, di─
namika.
Alone> But if, for example, there is a cube, then─
which somehow spins and should twitch
accompanied by music - in what form should you give it?
nq> Part 2 - cube - part description: needed
place emphasis on the rotation of the cube, on─
example, every turn must fall under
strong beat in the track, conventionally 00,16,32 and 48
pattern lines. We both live in this track
all the time. You follow every note. Ka─
Each new added sound may be re─
written and somehow improved, because everything is de─
barks dynamically.
Alone> Essentially, you need an invoice (to look─
see how it fits with the design) and rhythm (for
fix, then hang the arrangement there
final fix).
nq> Exactly. I usually offer a choice
tempo options that suit the effect─
Whoa, I’m doing a test drum loop and those options─
MPa with him. Which one fits better─
exactly - that one becomes the main one. Why?
I'm sticking with this approach - it works
sometimes in both directions, the effects charge
track, and the track, in turn, can give a boost─
to give birth to new effects, which -
development of existing ones, improvements and
a closer interweaving of everything with everything :)
Thus, the problem is “chicken or egg─
tsa" is solved like this - the track is writtenparallel─
but with code, according to the same plan (storyboard)
and with some references, it will be fixed in
testing time and (in our case) for─
ends on the same day as the code. This
is not the only solution, but it probably gives
the best result.
Share your thoughts about the article