Jump to content

Fnord42

Members
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    1

Fnord42 last won the day on August 21

Fnord42 had the most liked content!

Community Reputation

18 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No, have a look here: https://github.com/commanderx16/x16-docs/blob/master/VERA Programmer's Reference.md The VERA does a fixed resolution of 640x480@60Hz, smaller resolutions are actually done via scaling.
  2. Just uploaded the new version, completely rewritten in assembly. Much more fun! (To write and to play)
  3. Judging from your response, I might have sounded more negative than I had intended. Let me clarify: I don't think that the X16's audio capabilities are disappointing. I was personally a bit disappointed because I had hoped that it could also do MOD files. MOD files have very high retro nostalgia value for me, but that was maybe just a bit much to hope for. Additionally it's probably also a matter of personal preference, because I just don't like the sound of the YM2151 very much. That being said, the current audio capabilities are of course not bad at all - Amiga-like sound capabilities just would have been the icing on the cake for me, so to speak. You guys are doing an awesome job, and I didn't mean to step on anyones toes; sorry if I did.
  4. TBH I am still a bit disappointed about the X16's sound capabilities, mostly because I had hoped it would be able to play MOD files, which does not seem to be possible with the current hardware. (Despite having four(?) different chips with overlapping capabilities, which also feels a bit weird to me.) I assume that it is much too late to change the general design of the X16's sound architecture (and, more importantly, that the core team probably had good reasons to go for the chips they chose, that I am not aware of). But I have been thinking if it might be feasible to build a sound card for the X16 instead. I haven't investigated the topic thoroughly yet, but the fact that there are complete MOD players consisting of not much more than an ATMega32 and a TDA1543, makes it seem quite doable. To clarify, I don't want something that just plays a MOD that you throw at it, but rather the necessary hardware that would enable the X16 to play MOD files (for example as background music in a game) - you should be able to upload samples/instruments and then play them at different frequencies, much like the Amiga's Paula chip did, If I understood it correctly. What do you guys think? Is this a good idea or a bad one, and why?
  5. Awesome, thank you for the explanation! I understand that a "dumb" ROM cartridge would make little sense here, but I was thinking about a "smart" expansion card anyway - for example something that can be used more or less like a disk drive by the X16, but also acts as an FTP server to the outside world, so I can easily transfer files without having to move the sd card all the time.
  6. @rje Which kind of switches did you choose?
  7. That doesn't sound too bad - so the CPU could for example instruct an expansion card to write data directly to a specified memory area without having to squeeze everything through the 32 bytes of dedicated ram. Missing autostart capabilities are probably not much of an issue, if that can be done via sd card. I hope it will be possible to run multiple autostart programs in a row, so I can load the drivers for my expansion cards and still autostart my boot menu system or favorite game or whatever. Maybe an Expansion card can even detect a reboot via the characteristic memory access patterns of the bootup process and act upon that. Not sure if that is a feasible approach, but It seems not too far off. (I once built a Kickstart switch for the Amiga 500 that was controlled entirely via "magic" memory access patterns, so that I could switch the ROM without needing a hardware switch. (I didn't want to damage the case.)) On the other hand, an autostart program could just tell the card when a reboot has happened.
  8. While I agree that Kickstarter will probably bring in some more people, I must say that most of the Kickstarter projects that I backed, I heard about outside of Kickstarter first. Also, keep in mind that the team has some rather popular youtube channels, and Hackaday and other media will quite probably cover the campaign, too. So I don't expect that it will be a problem to find enough interested people for the first batch of Commander X16s. If interest is lower than expected, Kickstarter might still be an option, but I have no idea if the gained audience would be worth the Kickstarter fees.
  9. So, the expansion ports are seperate from the user port? Can an expansion card override ROM functions and/or make the CPU run code on power on? (In other words: can an expansion card provide its own drivers, without the need of an extra disk?)
  10. "Cherry MX Blue Equivalent Switches"... But the TKL one does indeed look quite nice. Still, compared to what else is out there, for a custom printed Cherry MX keyboard that is not mass manufactured (I believe they build it especially for each order, right?) $200 (roughly 170€) is not too much. Of course, you're free to disagree.
  11. I'm a bit surprised - can you name a keyboard with Cherry MX switches for 49€? I couldn't find anything below 100€ when I last looked for one.
  12. IMHO, if you are the type of person who prefers mechanical key switches, the price of the WASD keyboard is okay for what you get. If you can live just as well with a rubber dome keyboard, it's probably not worth it. Unfortunately (for my wallet) I just recently found out that I appear to belong to the first group.
  13. Okay, since I cannot select two^H^H^Hthree best answers, I'll quote them here and select this post instead.
  14. Nice, so there won't be a shortage of timers. I assume the 6522 timers can be used to trigger an interrupt? I'll have to read up on the 6522 anyway. Okay, that sounds good. I don't think I have to worry about the interrupt taking longer than 16ms - it only checks the counter and sets a bit, but the actual work is being done elsewhere. For now, I'll stick with the vsync interrupt, but the cycle counter could come in handy at some point. Thank you!
  15. Hi, I'd like to have some timers for various purposes in my program and I'm wondering what would be the best way to accomplish that. What I came up with is just using the vsync interrupt to count down my timer variables and set a corresponding bit in another variable when one of them hits zero. The main program then just has to check the timer_trigger variable at a convenient time and reset the counter if necessary. The thing is, I'm not sure if I can just assume the vsync frequency to be 60Hz in all situations. If not, is there a better way to do it?
×
×
  • Create New...

Important Information

Please review our Terms of Use