| |
ice00
Registered: Apr 2002
Posts: 54 |
Matt Gray competition
Yes, you read good!
Matt Gray has organize a SID Competition for his Reformation project (http://goo.gl/fSsE3J)!
Here his annunce on Remix64:
----
Do you fancy programming SID music old-school style? Do you fancy a good old fashioned competition?
I recently launched a Kickstarter to fund a double album of CD remakes and a Last Ninja 2 remake CD.
When the total hit £40,000, I promised to create six new SIDs in my old Dominator driver: imaginary sequels to my old SIDs, such as "Dominator 2" and "Last Ninja 2 - The Lost Level".
While we were retrieving the driver from my work disks, I thought it would be cool to release the source to one of my drivers so that SID composers would have a go at composing in it.
So, here's "Dominator, tune 6". It contains an assembler file in ASCII which will compile in the 64TASS cross-assembler (also included in the ZIP).
All you have to do is compose your own tune in this driver and submit it to chris@c64audio.com by 31st March 2015 to enter the competition.
Of course, if you don't feel like entering, you can still use my driver under the Creative Commons licence (remix, attribution, non-commercial). It's my gift to the community.
Myself, Martin Galway, Rob Hubbard, Fred Gray, Ben Daglish and Martin Galway all typed their tunes directly into their assembler. Now you can do the same!
My Dominator Subtune 6 Source Code ZIP (with 64Tass): http://www.remix64.com/services/files/matt-gray-dom6-public-sou..
What do I win?
The top ten submitted pieces will be featured in a special digital download released to coincide with the completion of the Reformation project. The composer of the entry that I likes the most will get a VIP invitation to the Reformation launch party, and meet me.
But, remember you can use this source code without entering the competition.
Rules
Entry must be written in my driver and submitted as ASCII source code which will compile and run in the 64TASS cross-assembler
Modifications to my code are permitted to enable extra facilities, but the code must remain largely based on my work
By submitting your tune, you grant me a free, non-exclusive, worldwide, irrevocable right to distribute it on any existing digital download platform
You are free to make available, publicise or otherwise use your tune as normal in accordance with the CC licence, in addition to submitting it to the competition.
Closing date is 31st March 2015, but extensions may be announced depending on circumstances.
More rules may be added later as circumstances deem necessary. Please keep an eye on this page periodically.
Have fun! - Matt Gray, Reformation Project, 26 November 2014 |
|
... 30 posts hidden. Click here to view all posts....
|
| |
Conrad
Registered: Nov 2006
Posts: 833 |
Didn't need to read docs. Worked some pattern bytes myself so far... (isn't this what the compo is all about? Hacking? :))
$FA,<num> ... set instrument number
$70-$7f(?) ... number of steps of following note byte to be played
$ff ... something ;)
... good thing also that the notes are defined rather than hex numbers. :)
btw, it's rather annoying that the example plays subtune 2 by default, I was getting confused when editing pattern data in the first subtune and nothing changed. ... at least I learned that $fe in the orderlist means fade-out tune. |
| |
booker
Account closed
Registered: Jul 2003
Posts: 333 |
Okay, so first step is to find a hero to write the player docs :D |
| |
booker
Account closed
Registered: Jul 2003
Posts: 333 |
Quote: Well, if data inside player can be freely modified - I guess tunes don't have to sound like Gray himself ;]
Kamil, I think the idea is to write your tune with this player :) Rules say you can modify the code, so I gues some candies can be added (ie, proper flt table routine? ;) ) Perchaps even note-converter from GT or SIDwizard :) though I think Matt wants ppl to write the tune using assembler editor...this time ;) |
| |
booker
Account closed
Registered: Jul 2003
Posts: 333 |
Oh, just read what ice00 said, cool :D |
| |
CreaMD
Registered: Dec 2001
Posts: 3034 |
ice00, conrad
\o/ |
| |
spider-j
Registered: Oct 2004
Posts: 444 |
Quoting ice00Entry must be written in my driver and submitted as ASCII source code which will compile and run in the 64TASS cross-assembler
Is it important how "readable" the code is we deliver?
I ask because my first steps would be to transform the given file in a way I'm used to work, splitting data and code over multiple files. And I'd really like to use the assembler that I usually use (acme) for the "workingprogress" versions.
When the tune is ready I'd like to just throw the binary again on Regenerator to create a disassembly that can be compiled with 64tass again instead of manually converting everything back to 64tass syntax. |
| |
GH
Registered: Sep 2014
Posts: 77 |
I will just write some Deliverance meets Last Nina music in general midi first and decide later if it ends up in this player ;D |
| |
Soren
Registered: Dec 2001
Posts: 547 |
The last dominator ninja!
I love Matt's work, BUT I will probably just stick to doing my own stuff AND using my own routines. However I will try to follow this with a great amount of curiousity :) |
| |
cadaver
Registered: Feb 2002
Posts: 1153 |
From the SIDIn #2 dissection (thanks Ice00!), looks like the song & pattern data are very straightforward. Only instruments will take more learning. Without modification, you can either make normal instruments with vibrato+pulse+arpeggio, or drums that execute a wave+frequency table, but not mix both in the same instrument.
If I was to participate, I'd probably be tempted to first optimize away the note-start rastertime peaks :) |
| |
No-XS
Registered: Mar 2002
Posts: 78 |
I need this .asm on a d64 as a prg so I can load in Turbo Assembler. |
| Previous - 1 | 2 | 3 | 4 - Next |
