Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by raster/c.p.u.

  1. Also Greg said me that he was surprised at this exotic sound used in my "Time to turn" (timett.com) Forever5 msx compo. It's created by envelope filter change. Do you hear my example song horror.rmt ? (it is in RMT ZIP package /songs/horror.rmt) There is used exotic sound called "jugular scream" (instrument $00) based on similar principle.
  2. I'm sorry, Jaskier, I'm not sure if I expressed clearly: I expected that TMC2.0 command "0" (P+F->frq) does the same as TMC1.0 command "2" (P+A->AUDF). So, If envelope looks like this: Step AAAA 0000 0000 1111 and note C-1 will be used (i.e. frq 243), then there will be played frequencies: 244,245,246,247 and if last command (in column 4) will be in loop, then it will be performed in the same way (248,249,250,...). And I have one important remark: Command 1 (P->frq) should set AUDF to direct "P" value, but now it works like frq+P->AUDF and there is missing some (totally needfull) command for setting direct value to AUDF. (this instrument feature is wholly important, in TMC1.0 it works of course and it is used very very often) Oh... I'm confused... Maybe I don't understand how it works in TMC2.0 (what is "F", "frq" (source frq? destination frq? AUDF?) etc... ). I'm sorry...
  3. Wow! Atari Tennis with 4 players together via Multijoy. It's great invention!
  4. Of course, I thought that AUDF of filtered channel will be AUDF(primary)+1,+2,+3,+4 ... (i.e. difference between AUDF primary and AUDF filtered will be increased about +1 for each command in loop). If it will works in this way, it give much more variation potential of loops at all. Similarly, command 0 should really increase current frequency (see the description: P+F->F !). So, if we use A 0 0 1 in loop, then resultant Frequency should be increased about +1 for each step (+1, +2, +3, ...) , no constantly +1 forever as it does now.
  5. For example, lets loop contains: a 4 0 1 And I expect, then filter value will be ...,1,2,3,4,5,6,7,8,.... (+1 for each this command) a 5 0 1 Now I expect the filter value will be .....1,1,1,1,1,1,.... (=1 for each this command) (And BTW - I think command p+filter->filter is enough and there is no need of p->filter, because it is possible to do everything we need by command p+filter->filter)
  6. Yes, I have set AUDCTL to 6 (filter is turned on), but command 5 doesn't P+filter->filter .... Aha! There is bug in help text. Command with number 4 is missing and command 6 is twice there. Ok, I tried to use command 4 with parameter 01 in loop now, but it doesn't work too. Or I don't understand how it should works?! Very nice!!!
  7. Good work, Jaskier! I have some few questions only: 1.) command 5 (P+filter -> filter) doesn't work yet, am I right? (I tried to use it in loop, but it has no effect.) 2.) command 6 (P -> filter) ... I think it's redundant (IMHO command 5 is fully sufficient). Don't you think? 3.) will be possible to show "Instruction" by Help k.... OH?! HEY! It works already! Oh Yes, it seems to me be intuitive behaviour.
  8. Miker, you're totally right! I tried to run it on real Atari yesterday... I was using some few boot loaders, I made some few adjustments (additional routine for moving some lower memory blocks), but no success appeared and I didn't want to spend more time with it.
  9. If I'm right, ADSR means "Attack Decay Sustain Release" envelope mechanism. RMT is able to fully control the instrument envelope, so there is ADSR in RMT already. I assume you mean there will be fine to use some SoftSynth method for mixing of true Pokey and SoftSynth voices. Ok, I have no objection for it, but I'm afraid here is problem to do it: Main routine is spending too much time, that's why SoftSynth routine will be breaked too often (up to 4 times per frame) and for too long time, therefore SoftSynth can't produce nice continuous sounds. Of course, we could create some "special cutted off RMT routine without most of (without all) RMT effects", but then it's easier to use some existing routine - for example great Swiety's Pokey+SoftSynth routine and we need not to remove prime RMT features from RMT and glue SoftSynth possibilities there. Am I right?
  10. Chorus with Samurai's voice: Where is the download link ?
  11. I think it's another purpose of RMT/TMC and this great softsynth SID emulation. RMT/TMC is "for normal daily use", but this SoftSynth is "singular event". Hmm... Here is more active people on Atariage (all the active people from Atariarea + rest of active people from all the world).
  12. Swiety, I can say only: It's great, Great, GREAT!
  13. IMHO, I assume it needs all the CPU power absolutely. No ANTIC, no other operations, SoftSynth routine only. But it is great anyhow!
  14. Wow... It's great! It seems to me like a full software emulation of C64 SID chip. I'm amazed.
  15. :wink: TMR, how integrated tune compresser/compiler are you waiting for? You have all sources of RMT player, you know xasm, you are able to compile whatever you want by xasm, you are the champion...
  16. No. There is one main difference. RMT supports "FM" (Frequency Modulated - or strictly speaking "PM" - Pokey Modulated ) music only with 50Hz (up to 200Hz = 4 changes per frame) frequency of changing Pokey registers. IMHO, higher frequencies means something like "samples"... I'm uninteresting in it. If I want use the samples, I don't need the Atari and POKEY chip - I can use my PC with 44100Hz 16-bit stereo sounds. On Atari, I like pure Atari music with true "PM" (Pokey Modulated) sounds. If you mean "model" the various sounds by "PM" (preferably with 1 change of Pokey registers per frame... ???... hmm, ok... up to 4 changes ), I thought about it many times already, but I haven't tried it so far. Please, try it!!! I think it's great idea!
  17. BTW - It was big surprise also for me. When I heard this sound first time during the development of RMT prealpha version, I remarked to source code this note: //26.12.2002 10:59 .... stvoril jsem monstrum s montrooznimi moznostmi. Umi to hrat i jako SID ze C64.;-) English translation: 26.12.2002 10:59 ... I have created the monster with amazing possibilities. It's able to sound like a C64 SID chip. BTW2 - good news: Jaskier accepted my suggestion to implement this feature to his TMC2.0:
  18. Tatqoo, Great song! Will you want me to add some new special feature to RMT ?
  19. Hi. Maybe I don't understand you... But RMT is standard Atari binary file with headers addresses (from-to memory location) and it contains only song data, that's why it can't contain any "asm source" linked at the end of the rmt data. So, initialization (ldx#..,ldy#..,jsr RASTERMUSICTRACKER) and calling of the player routine (jsr RASTERMUSICTRACKER+3) you have to put to your source code certainly.
  20. I hope You know in RMTracker there is possible to use File - Export as - "RMT stripped song file" and set any memory location address for stripped module song data (without song name and all instruments' names), also you can take advantage of RMT_FEAT definitions for compilation of greatly smaller&quicker RMT player routine.
  21. New RMT tracker version 1.16 is out. My big thanks goes to Jaskier/Taquart for his great speed/size optimizations of Atari RMT routine! http://www.infos.cz/raster/atari/rmt/rmt.htm There is implemented also some instrument "paste special" features Tatqoo (Samurai) requested. Enjoy it!
  22. I think I'm (maybe) a good programmer, but (for sure) bad businessman. Ehmm... I suggest You can freely compose great songs... and I will freely upgrade RMTracker (if there will be need of some upgrades of course).
  23. Samurai, it's your credit. I took delight in your RMT music activities, that's why I made new improved RMT version.
  24. Very nice song, Samurai. I'm looking forward. Thank you for new fine Atari songs. ...Take it easy, Samurai. I think RMT was created latest, that why it is mentioned last. It doesn't matter absolutely...
  25. Hi Atari musicians! New RMT 1.15 tracker published. http://www.infos.cz/raster/atari/rmt/rmt.htm Changes in RMT 1.15 ------------------- - Quadruple instrument speed allowed also for 8 tracks STEREO modules. - .rmt (.txt,.rmw) filename can be used as the commandline parameter for the automatic loading of this file after start of the RMT tracker. (It's recommended to make association for "rmt" extension to run RMT tracker.) - Show Play time counter (from 00.0 sec to 9:59 minutes). (default is on, turn off by menu View - Play time counter) - Menu Track: * Info about using of actual track. * Renumber all tracks (2 types of ordering). * Clear all tracks unused in song. - Menu Instrument: * Renumber all instruments (3 types of ordering). * Clear all unused instruments. - Two tracks functions moved from Song menu to Track menu (Search and rebuild wise loops in all tracks, Expand loops in all tracks). - Size optimization function (menu Song - All size optimizations) perform also clearing of all unused instruments and renumbering of all tracks and instruments now. (So there can be a bit better result of size optimization thanks to removing unused instruments and removing empty gaps after deleting of unused tracks and instruments.) - Preserve last "From address" value in export of stripped RMT file dialog. RMT routine changes - Several improvements of RMT Atari assembler routine - it is 22 bytes shorter now and faster about 50-150 CPU cycles. - New speed/size optimalization options FEAT_VOLUMEMIN and FEAT_TABLEGO supported and optimalization for FEAT_AUDCTLMANUALSET improved. (Coders, you have to use new rmtplayr.a65 and rmt_feat.a65) - New mono/stereo compile modes. There is variable STEREOMODE (instead of previous variable STEREO8T) with the following values: STEREOMODE equ M ;M=0 => compile RMTplayer for 4 tracks mono ;M=1 => compile RMTplayer for 8 tracks stereo ;M=2 => compile RMTplayer for 4 tracks stereo L1 R2 R3 L4 ;M=3 => compile RMTplayer for 4 tracks stereo L1 L2 R3 R4 * Note: If RMTplayer routine compiled with STEREOMODE 2 or 3 is used on Atari computer without STEREO upgrade, then standard 1 POKEY mono music will be played. It exploit POKEY memory area mirroring - there isn't used any "stereo detection" method! Bug fixes - Bug in rmtplayr.a65 initialization part if nonzero "starting song line position" was used. (This problem occured in some cases only.) - Buffer overflow error with export of stripped RMT file for too high address. - Other small corrections and bugfixes.
  • Create New...