| |
lft
Registered: Jul 2007
Posts: 369 |
Playroutine coding: A new way to represent pitch
Introducing the 9-bit pitch technique:
http://www.linusakesson.net/programming/9bitpitch/index.php |
|
... 24 posts hidden. Click here to view all posts....
|
| |
gegegege gugugugu
Registered: Jul 2002
Posts: 469 |
some great resource on Arabic music there, Hein - thanks! |
| |
lft
Registered: Jul 2007
Posts: 369 |
Hein: That's right, the user could still use normal C-1, C#1... syntax, and these are converted to integers in the normal way. Then the integers are shifted two steps to the left. |
| |
Perplex
Registered: Feb 2009
Posts: 257 |
Has anyone implemented or considered implementing an editor and player for 31-tet music? |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1424 |
Perplex, I wasn't familiar with 31 equal temperament before today. It does seem to present something of a sweet spot for interval accuracy.
Personally I've occasionally considered leaning towards just specifying frequency per note - everything beyond that is just data compression, and arguably shouldn't be musician-facing. If they want a perfect fifth, give them a perfect fifth! Generating tables of frequencies used should be a compile time operation, not a musical constraint.
31-tet does look like an intriguing abstraction, mind, as well as fitting nicely in five bits. |
| |
lft
Registered: Jul 2007
Posts: 369 |
ChristopherJam, I can see your point of view, but some pragmatism is inevitable. The question is where to draw the line.
Demo coding is also "just data compression". We could start from a desired on-screen result and have a compiler generate the program for it. That's what a video encoder does. Sure, size and rastertime are through the roof, but the art director gets maximum flexibility.
Of course, you didn't suggest that. But my point is that playroutine design is about exploring the interaction between size, rastertime and flexibility, and trying to find sweet spots. Especially if you want to use the music in a demo, you're going to have to expose some constraints to the musician.
I also think that if we just blindly design for flexibility, we're going to end up with uninspiring systems without personality. Kind of like the modern PC.
On another note (ha!), ProTracker MODs store a 16-bit frequency for each note, but only a small set of frequencies are allowed. Players then perform a reverse-lookup (e.g. binary search) to get a note number. Then they look up the actual frequency to use, based on the note number and the finetune parameter from the instrument. There is much madness in the world. |
| |
Frantic
Registered: Mar 2003
Posts: 1661 |
@lft: Probably because fine-tune wasn't there in early .mod formats. But yeah... gradual mutations into madness. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1424 |
"..especially if you want to use the music in a demo, you're going to have to expose some constraints to the musician. "
Oh absolutely. I just prefer to express constraints in terms of costs, and give artists some space to juggle their own tradeoffs - eg, "you can have up to 15 instruments per track, but any instrument that spans more than 32 semitones counts as two instruments"
Back in my PS2 dev days we'd just give artists a texture budget per map region and a few different compression options, and let them make their own mind up how many texels they wanted. The lead artist for each level would then make up some finer guidelines so different suburbs didn't vary too wildly in degree of compression, but that was an artist call not a coder one.
I do take your point about constraints also adding flavour of their own. |
| |
Dane
Registered: May 2002
Posts: 423 |
Constraints are fun. Balancing out a tune/trying to tell a story with music somewhere between max rastertime allowed and max memory usage allowed is what excites me. |
| |
Hein
Registered: Apr 2004
Posts: 965 |
Quote: Has anyone implemented or considered implementing an editor and player for 31-tet music?
Yes, considered it, at least different scales, like the beforementioned 24-tet. Doing it with extended freq-tables and a 24-tet scale representation (with half sharp accidentals) would require some work to the standard editor setup. The whole player would need to be adjusted as well. Meh.
But I've changed my finetune routine a bit so the finetune intervals are small, allowing for $30 values between each half tone in the arpeggio step routine. Only the scale representation in the pattern editor isn't accurate this way. Someone willing to do 31-tet music shouldn't be bothered by that detail, me thinks. :)
Haven't put it in practice yet musically, though, because I'm busy posting thought bubbles about clever 9 bit tricks and having fries with that. |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Compared to 2 tones, lets say D and D#, will this give another tone that isnt possible with detune of D ?
else, what use is it ? |
| Previous - 1 | 2 | 3 | 4 - Next |
