Jump to content

ivop

Members
  • Content Count

    2,079
  • Joined

  • Last visited

  • Days Won

    3

ivop last won the day on April 9 2017

ivop had the most liked content!

Community Reputation

2,582 Excellent

1 Follower

About ivop

  • Rank
    River Patroller

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    The Netherlands

Recent Profile Visitors

20,202 profile views
  1. With @mytek's designs at hand, it is possible to create a computer similar to the 800. A main board that provides power, maybe some logic or buffering, and a master bus with multiple edge connectors. Put all five VLSI chips on a separate plug-in card. Sixth card with MMU, seventh card with RAM, eighth card with ROM, and a few spare slots. Base board 20x20cm. Slots 200 mil by 10cm plus 400 mil spacing for chips hanging off the boards. With that width, you can handle 60-70 channels on the bus that rules them all. One ore two standard edge connectors. Plug-in cards are 10x5cm or 10x10 cm, with pin headers at the top to bring out the signals to the connectors. You can have at least 12 bus connectors on 20x10cm, have 6 more on 10x10cm, and leave the other 10x10cm for bus drivers, power, etc... The master bus should consist of at least the address bus, data bus, all clocks, including fast clock/bus between GTIA and ANTIC. SIO. Audio. MMU lines. Perhaps more
  2. Note that with a single Pokey, you lose two channels (channel 3+4) for MIDI communication. A stereo upgrade would be needed to reach at least the channel count of MIDIjoy. But it's a nice project. Something I was considering doing myself somewhere in the future, but there are so many other projects Good you already found the midimon source code. I agree with MyTek that it could function as a starting point. Rip-out the printing part and start playing pokey notes instead
  3. I always wonder, how do you keep this dust free? Do you go over it every week with a vaccuum cleaner? Or dust rags?
  4. I always wanted my monitor on top of the drives, but apparently that wasn't a good idea BITD with CRT monitors Nice setup!
  5. Binning this whole thread would not be the solution IMHO. YMMV. Somehow, I never run into arguments with emkay anymore. I changed the way I communicate with him. Sure, he has issues. So have I. And a lot of other AA members.
  6. Possibly, but a nice feature you mentioned before was arpeggios in the pattern domain, instead of the instrument domain. Converting such a GoatTracker file to RMT will lose that, because RMT does not have that feature. The only way RMT could handle that is if each pattern line is exactly one frame. But you still cannot edit the chords/arpeggios within RMT.
  7. Shorted a whole motherboard on the shielding: check. Misalligned a chip by 1 pin in a 40 pin socket: check. Or the keyboard connector: check. I never got beyond a bicycle But I once I could really have used some help of The Bicycle Repairman. You know, you fix a tire, forget to check the outer tire, put it all together, inflate it, and pssssssssssssssst
  8. Other projects or life got in the way But I'm glad you found use in my RE efforts. Back in 2012 my idea was to write converters to the RMT format. Last year emkay and I shortly discussed a GoatTracker to RMT converter, but it seems there's not a huge library of GoatTracker files available, so that would be wasted effort.
  9. That looks very nice! Especially when the broken walls enter the picture. That guy looks like he rushing for the toilet to do a number two
  10. That's not my problem. But it is easy on the A8. Display List something like: empty space High mountains (DLI slow scroll) empty space Low mountains (DLI less slow scroll) empty space Rocks (DLI faster scroll) empty space Bushes (DLI fastest scroll) last empty space Game stats (no scroll) By modifying the DL on-the-fly, you can vary the empty spaces at will and simulate height. For example, you start with dta 0,0 and work your way up to dta 112,112 to increase the space. Last empty space has to constantly fill up the last missing lines so the stats stay at a constant position.
  11. Now that's proper parallax scrolling where layers actually overlap!! That "stunning" horizontal and vertical parallax on the C64 does none of that and is extremely easy on the Atari 8-bit with some display list juggling you can stretch vertically to simulate the plane going in the air, and back again. Horizontally is just HSCROL at different speeds. No overlap of mountains or terrain features at any speed.
  12. During development of the song, you don't need to constantly LZSS compress the streams. Just push entries to a round-robin buffer that's played by a simple 6502 player that just dumps the frames to Pokey. I did But that's a no-go because it is way too much intertwined with the rest of the emulator. Then I mentioned reimplementing with Altirra as guide. That's a lot of work. After that, I also mentioned another method that might be more promising, namely a direct connection with either atari800 or Altirra. That way, you will automatically get better Pokey emulation if the emulator improves. Speed is a non-issue for so little data. And SHM, Domain Sockets or FIFO's are plenty fast for this.
  13. Ah, missed that one. That's what you get when you optimize your code directly in the browser without testing
  14. That's a tracker for the NES. Here you hear the stock sound chip plus an external Konami VCR6 soundchip. Nothing Atari at all.
  15. True, but perhaps he can shuffle some instructions around. Or use the 3-cycle dummy + 2 new cycles = 5 cycles for something else. Another optimization is loading x with #$20 outside the loop. Remove lda #$20 from second byte part, replace sta IRQEN with stx IRQEN. Saves another 2 cycles. And 2 bytes. IIUIC, you need to complete your work in 33*2 - 9 (refresh) cycles = 57 cycles. So 56 was good enough already, but you can go lower if you want or need it And 7 free cycles could be used for something else. Or 8 cycles if my 57 cycles calculation is correct.
×
×
  • Create New...