| |
vincenzo
Registered: Sep 2003
Posts: 83 |
The C64 Grand Tour Challenge
Hey everyone,
I wanted a new year challenge for 2021. The idea is to compose 1 music per each month of the year. Yeah, it's nothing special, right?
So to spice it up, each month I'm going to use a different editor/player.
Now it sounds like some nice fun that I don't want to keep for myself only.
Composers, join me!
List of editors and rules to follow:
Jan: GMC V2 (GMC V2 (Unfinished))
Feb: SID Factory 2 (PC) (https://blog.chordian.net/sf2/ build 20200911)
Mar: Ninja Tracker 2.04 (C64) (NinjaTracker V2.04)
Apr: Defmon (C64) (defMON V20201008)
May: Goat Tracker 2.75 (PC) (GoatTracker V2.75)
Jun: DMC 7 (C64) (DMC 7.0)
Jul: Virtuoso 1.02 (C64) (Virtuoso V1.02)
Aug: X-SID (C64) (X-SID)
Sep: Cheesecutter 2.9.0 (PC) (CheeseCutter 2.9.0)
Oct: Sosperec 1.0 (C64) (Sosperec Editor V1.0)
Nov: SDI 2.17 (C64) (SID Duzz' It V2.1.7)
Dec: SID-Wizard 1.8 (C64) (SID-Wizard V1.8)
Rules:
- Use the linked version of the actual editor only (compatibility)
- 1 SID, 1x speed only
- Track length: please keep it within the usual limits. Not too short, not too long, make it as long as a regular composition would be.
- 1 track per month with the specified tool
- If the editor saves to a format where player is included, use address $1000
- Deadline: last day of the actual month, at midnight
- Send your projectfiles to: strayboom()gmail()com
I don't plan voting, this supposed to be a motivational-fun-self-challenge only. Do it for your own good or don't do it at all. Still, there will be a progress bar with the completed entries.
If there's enough tracks, I'll make a compilation in a form of musicdisk or music mix, etc.
There might be a huuuuuge - or small - C64 musicdisk release of all tracks at the end of the year/early next year. We'll see.
Sincerely,
vincenzo /Lethargy^Singular^SIDRIP^Rebels^Molecoola |
|
... 78 posts hidden. Click here to view all posts....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11418 |
How does it matter? I'm not even looking, i have working emu thing :)
Instead of emufixing for ancient broken stuff, you should rather break the current stuff - so it gets fixed eventually. |
| |
Krill
Registered: Apr 2002
Posts: 2990 |
Well, i still keep seeing that "buggy firmware" nag message in recent demo compos. =) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11418 |
Sure. but while this is funny, it doesnt push ppl to fix anything. |
| |
Sparta
Registered: Feb 2017
Posts: 49 |
I agree with Groepaz. We shouldn't (and shouldn't be expected to) emufix our loaders. In reality, however, people expect everything to work on their old or newer hardware because others work too. If not, then it must be a "loader issue" and they post lengthy comments under the affected release (and then ignore PMs requesting specifics about the "issue"). Others of course are more willing to help. :)
From my point of view, I want people to try and use my loader so I can't leave these issues unhandled, otherwise all people would remember is "ah, that's the loader that failed in that prod..." So I have no choice but to retrofit it to please as many users as possible. Fixing the buggy firmware is way beyond my skills. On the other hand, in this specific case, replacing a single unintended opcode in the drive code which was only left there as an oversight on my part was not a big deal. The loader works either way, so I really don't mind, especially because all previous versions of Sparkle had it this way. :) |
| |
Krill
Registered: Apr 2002
Posts: 2990 |
Yes, same reason why i kept in the work-arounds.
Maybe Sparkle should also come with a nag message once it has detected those firmware issues.
I have it on good authority that Gideon became aware of similar 1541U2 issues (same emulation bugs after a regression) only after that message popped up at various occasions and people started to report.
(But then at least one person said "but i did run the latest firmware, and it still loads, so somebody goofed up with that check routine". Oh my, can't expect everyone to have working logic circuits in their brains.) |
| |
Ninja
Registered: Jan 2002
Posts: 414 |
Full illegal opcode support for the 1541U was the reason I did 1541-Testsuite 13 years ago. It already identified problems back then, but Gideon was prioritizing other features first. Maybe now it is the time? (Note to self: I should update the entry to at least fix the links) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11418 |
And your testbench has been integrated into the VICE testsuite for many years - which i am running against U64 (and thus U2) after every firmware release and report back bugs. Lets say the process has become increasingly difficult and i lost a bit motivation to even care. (It is obviously much more interesting to add more fancy features than hunting those last few tricky bugs). |
| |
Krill
Registered: Apr 2002
Posts: 2990 |
Let's just make a game that everybody and their dogs want to play, and put things all over the place that require correct emulation. =) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11418 |
I can already hear the whining about it not working in VICE 2.4 :=) |
| |
vincenzo
Registered: Sep 2003
Posts: 83 |
Guys, this supposed to be a thread about music and the conversation steered into a very different territory. It might make more sense to open another thread with the 1541U and related loader issues. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 - Next |
