Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ivop last won the day on April 9 2017

ivop had the most liked content!

Community Reputation

2,268 Excellent

1 Follower

About ivop

  • Rank

Contact / Social Media

Profile Information

  • Gender
  • Location
    The Netherlands

Recent Profile Visitors

19,780 profile views
  1. Except for a Instrumentarium by @analmux, I'm not aware of any other tune. As for recording SKCTL every frame, future players could switch between two-tone mode and normal mode. And if they don't, that "channel" will be LZSS compressed to just a few bytes. But as said before, tight timing for @pavros's way of syncing distortion $Cx, cannot be captured this way. That requires cycle exact stores to SKCTL for poly restarts.
  2. A few years ago, somebody did a presentation in Maarssen (The Netherlands) about the Sharp X68000. Very interesting! But not many were sold IIRC. Not even in Japan. It had a nice FM sound chip. And the graphics was arcade quality. But it was very expensive. And for the collectors, it still is
  3. Another note: @Synthpopalooza's and Pokey Explorers notion of Reverse 16-bit is NOT the same. Pokey Explorer: ; this affects AUDF (i.e. the 16-bit frequency) Channels 1+2: 16-bit: LSB + MSB Reverse 16-bit: MSB + LSB AUDC order: Channels 1+2: 16-Bit: Mute + Play Reverse 16-bit: Play + Mute (<---- @Synthpopalooza's reverse 16-bit) Edit: this comment shows how both can be combined. Play+Mute (synthpopalooza's reverse 16-bit), and both LSB/MSB and MSB/LSB storage of frequency. All result in pure sawtooths.
  4. I was talking about SAP type R (which sadly only records $d200-$d208). But you are right that normal SAP type B can handle that, provided that the SAP player has a proper 6502 and Pokey emulation. SAP-R could be extened (SAP-X?) to include SKCTL, for example to also record two-tone mode, and @dmsc's LZSS player can be extended to include the extra register(s). But once you start using pavros' sync methods, you can't record that to SAP-R/X as the writes have to be cycle exact. That's what I meant to say Edit: in addition to the openmpt+sample pack idea: I understand that you mean a sample pack of notes/arpeggios/drums/etc of which you know the exact SAP-R representation, and can then afterwards mix them according to the song and pattern data. I think that's a lot of work. There are so many potential samples. Just preparing all the possible samples you might need will take ages. And record the SAP-R version, too. Then align them properly, create sample pack, and all mappings between notes and samples. You need a sample for every note. You can't just sample C and F#, and have the MOD tracker play the samples faster/slower according to the needed frequency. Oh, and how about glissandos?
  5. Jumping eight bytes in a routine that is normally called through a vector ($ef94 is open E:ditor in the XL OS) BTW for 128 or 256 bytes challenges, this is very helpful!
  6. Sure, you need to define your message as screen bytes For example (mads syntax): dta d'Hello World'
  7. And if you want to use CIO put, set ROWCRS (84/$54) and COLCRS (85,86/$55,$56) before calling CIOV to put a byte to the screen at the specified position. COLCRS is 16-bit, because it can range from 0-319 in graphics 8. Just set the MSB to 0 and let the LSB go from 0-39.
  8. Better use SAVMSC (88,89 ($58,$59)) instead of ADRESS (which is a temporary value btw). SAVMSC points to the upper left corner of the screen, i.e. the first byte of screen memory. For split screens (graphics mode with text window below), you can use TXTMSC (660,661 ($294,$295)), which points to the upper left corner of the text window.
  9. In theory, every tracker can be used, and the resulting song and pattern data can be converted to RMT or another player. But afterwards, you have to (re)create all your pokey instruments. Pokey VST plugin is a nice idea. Not just for tracking, but for "real" musicians, too
  10. If I understand it correctly, that's a sample pack for a MOD tracker. If you carefully sequence your MOD file to not use more than 3 (SID) or 4 (Pokey) channels at the same time, you can indeed replay the same patterns and song data on a real machine. I think both Goat Tracker (C64) and Raster Music Tracker (Atari) can import MOD song and pattern data. But after that, you have to create your own instruments.
  11. I decided to keep the version number the same for the new batch processor, so here is v1.1rc2 of Pokey Batch Explorer. The batch sweep settings are seperated from the main source in sweep.s. Audacity screenshot of amplitudes: You can clearly see that during the "plain $ax" sweep, the volume increases when the frequency decreases. I suppose that's what emkay means when he complains about volume problems first-batch-3-sweeps.mp3 pokeyexp-batch-v1.1rc2-ntsc.xex pokeyexp-batch-v1.1rc2-pal.xex
  12. This part was not joking BTW. Either Synthpopalooza, or I, or both, or together, or somebody else, will probably write a new player that can handle all these exotic settings and note tables. Except for STIMER reset and SKCTL (reset and two-tone mode), everything can be captured to SAP-R and replayed with dmsc's LZSS player. ~1140 cycles per frame. So the new player does not have to be optimized for performance, but for features And then implementing a tracker is an exersice for the reader
  13. Yes, "just" that Yeah, that's a pity. But a new player routine will be written. Expect the tracker late 2025 or early 2026
  14. Here are the settings I think are all without disharmonics: (n) start_value --> interval (1) $0001 --> $0101 (n=prime) start_value --> interval (2) $0002 --> $0202 ($0001 --> $0202 doesn't sound that bad, too) (3) $0205 --> $0303 (5) $0106 --> $0505 (7) $030a --> $0707 And all the sweeps work with both 16-bit and reverse 16-bit! (where $030a turns into $0a03 for example, for prime number 7). I don't think the next primes (11,13,17) are useful. Edit: All sweeps eventualy end up with that high pitched overtone I mentioned earlier. It depends on your age when you start hearing it
  15. I enabled 16-bit intervals. Most of the code was already prepared for that. Here's a sweep of one of synthpopalooza's discoveries. Filter 1+3, 1 and 3 @1.79MHz, 16-bit sweep of 1+3, start value $0001, interval $0101, short play time, no gap, just an example Notice how after $8081 you slowly hear a high note that messes things up in the bass range But, here's v1.1rc2 with 16-bit intervals pokeyexp-v1.1rc2-ntsc.xex pokeyexp-v1.1rc2-pal.xex sweep-synth-0101.mp3
  • Create New...