Jump to content

Sheddy

Members
  • Posts

    838
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Sheddy

  1. they look familiar. I remember sharing those quite a few years ago now. I had got a trial version of the Intel Compiler to try learning something. That didn't work out, but I played with various processor options and Profile Guided Optimization for RastaConverter. There weren't any changes over beta7, but the compiler just did an outstanding optimization for speed on the code. The Intel compiler isn't the same anymore (but is free) and I can't get Profile Guided Optimization to work with RastaConverter and Visual Studio anymore. But it has been compiled with the best settings I could find for speed.
  2. That's great. I see it now. Thanks @ilmenit
  3. Nice! Is that rate what you normally get or just a fluctuation with 16 threads or more? My best machine only manages peaks of 90 000, but it is old now.
  4. At some point I hope Ilmenit will be able to merge the new version source code changes into his GitHub repository if things look ok.
  5. I think that error is coming from the separate GUI front end program. Are you able to try same options from command line to confirm? Unfortunately I don't know anyone who has the source code for the front end.
  6. RastaConverter Beta8 Testing I've been messaging people who might know a bit about the RastaConverter source code to see if some simple hack or work-around could be done to help stop those ugly horizontal line artefacts it does sometimes which only show up when viewed on real Ataris or modern emulators After being pointed to an idea in the right kind of direction and place (thanks @phaeron) I've done a small hack to the Evaluator function which I'm getting some feedback from @ilmenitabout. The idea (which has been suggested by others in the past too) avoids a complete rewrite of some things, and makes RastaConverter give a bad score to scan lines that meet certain fairly simple conditions instead. In the meanwhile I've been trying it out myself with some good results, and as you can see here recently, have let @Atari8man2004 have at it, as he has a powerful rig and lots of pictures on the go, so would likely notice any problems sooner than most. So far so good by the looks of it! Thanks very much for testing. So sharing it with you all here now. @ilmenit has been kind enough to try getting his RastaConverter development environment set up again to check things out properly, which we've both found is unfortunately a pain to get working now on newer environments due to the age of the libraries and things used originally. Although it is only quite small changes, please let me know if you come across any new weirdness with this version, as it is very possible for me to have made mistakes with this, not being too familiar with the codebase or C++ (learning a lot from trying this) Thanks to @drpeter for managing to find an example of a wrongly self overlapped player and of course for highlighting the artefact issues in the first place, what causes them at a deep level and how to try and fix them (building on @phaeron findings in his Altirra Hardware Reference manual, making Altirra more accurate, and prompted at least partly by... what RastaConverter actually shows on a real Atari) Kind Regards Sheddy RastaConverterBeta8.zip sheddy_ding.xex
  7. Yeah, I know, no music, but it has the rest covered.
  8. RastaSlide 4.3 - RastaConverter Slide Show Maker and Tools Changes in version 4.3 - Compiled with old GO version 1.20.14 which is the last that works with Windows 7 - Early version of tool to help recreate some files for RastaConverter /continue @MrFish Hopefully this should work for you RastaSlide 4.3.zip sheddy_opal_sea_turtle.xex
  9. Ok, thanks. that's interesting. The GO runtime itself is crashing. Were you able to run it OK on the 4.1 version of the color converter? I'm guessing it is crashing when it tries to open the Windows file selector GUI? Feel free to PM me the details Kind regards Chris
  10. IMO it's not unreasonable for a cart based program to cold reset when reset is pushed, unless the program is totally expected to retain RAM
  11. Possibly of use, but only for the 8mbit carts. There will be equivalent for 1mbit presumably. From an Email with Steve Tucker: > At some point I'd like to try adding a high score saving function as > well, so it'd be good to know the proper way of flashing the cart > without relying on my interpretation of a disassembly (and potentially > wrecking my cart!) Hi Chris, Here is the code I used to save game states for Summer Games. The stuff at the end is game specific and probably no useful, but the other routines are general purpose calls for erasing a bank and writing from a block of memory into the erased area. If you need any help just yell. Thanks Steve -- ;; ;; XL/XE Equates ;; inter .equ $3FA ;; Shadow of cartridge interlock cartop .equ $BFFF ;; Last byte of cartridge trig3 .equ $D013 ;; Wired to cartridge on XL/XE random .equ $D20A ;; zerobank .equ $D500 ;; Zero bank ;; ;; Flash program registers ;; copysrc .equ $30 ;; Source pointer copydst .equ $32 ;; Destination pointer cursec .equ $34 ;; Current sector base curbank .equ $35 ;; Current absolute cart bank count .equ $36 ;; 16-bit count of data to read/write pollsame .equ $39 ;; Write polling scratch register ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Set bank to the base of a 64k 'sector' in flash cartridge ;; ;; Valid sectors are 8-15 for an 8mbit cartridge, passed in A ;; setsec sta cursec and #$0F clc rol A rol A rol A tax sta zerobank,x sta curbank rts ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Erase a 64k sector of an 8mbit flash cartridge ;; ;; Valid sectors are 8-15, passed in A ;; erasebk pha _ebc1 jsr cmd_unlock lda #$80 jsr wr5555 jsr cmd_unlock pla jsr setsec lda #$30 sta carbase jsr poll_write rts .export erasebk ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Increment the source pointer, dec the 16-bit byte counter, carry will be clear if it turns over ;; decctr inc copysrc ;; Increment the source pointer bne _dcdst inc copysrc+1 _dcdst inc copydst bne _dccmp inc copydst+1 _dccmp lda copydst+1 cmp #hi(cartop+1) bne _decby inc curbank lda #hi(carbase) sta copydst+1 _decby sec lda count sbc #$01 sta count lda count+1 sbc #$00 sta count+1 rts ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Program upto 64k into a sector of the flash cartridge. ;; ;; copysrc should be set to the start of data to program. ;; count should be set to the total number of bytes to write (0 based) ;; sector to write to should be passed in A ;; ;; you should call erasebk with the sector to erase before programming ;; prgsec jsr setsec _prgnw lda #lo(carbase) sta copydst lda #hi(carbase) sta copydst+1 _prg1 jsr cmd_unlock lda #$A0 jsr wr5555 ldx curbank sta zerobank,x ldy #$00 lda (copysrc),y sta (copydst),y jsr decctr bcs _prg1 _prgerr rts .export prgsec ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Program Initalization and Cleanup ;; init lda #$00 sta nmien sta wsync rts ;; ;; Cleanup routines ;; cleanup sta cartoff sta wsync lda trig3 sta inter lda #$40 sta nmien rts ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Poll for flash write operation to complete ;; poll_write lda #$00 sta pollsame _poll_again lda carbase cmp carbase bne poll_write cmp carbase bne poll_write cmp carbase bne poll_write inc pollsame bne _poll_again rts ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Send unlock sequence ;; cmd_unlock lda #$AA jsr wr5555 lda #$55 jmp wr2AAA ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Shortcut to write a few commonly used 17-bit addresses ;; wr5555 sta $d542 sta $b555 rts wr2AAA sta $d541 sta $aaaa rts ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Write @ sector 2ce from $6320, 2 sector ;; wr2ce jsr init ;; c4a -> cea9 -> pos 4da lda #$08 ;; flash sector 8 jsr erasebk ;; 02 sectors from 6320 to sector 2CE/2CF lda #$20 sta copysrc lda #$63 sta copysrc+1 lda #$FF sta count lda #$00 sta count+1 lda #$08 jsr prgsec jsr cleanup rts .export wr2ce ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Shared memory copy routine. Pass table offset in X ;; memcpy lda #$00 sta copysrc lda #$A0 sta copysrc+1 lda readtab,x sta copydst inx lda readtab,x sta copydst+1 inx lda readtab,x sta count inx lda readtab,x sta count+1 inx lda readtab,x tax sta zerobank,x _cpsec ldy #$00 lda (copysrc),y sta (copydst),y jsr decctr bcs _cpsec rts ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Flash reads ;; ;; dest pointer count (zero based) bank flash sector disk sector readtab .byte $20, $63, $FF, $00, $40 ;; 8 2CE/2CF ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; Read entry points ;; rd2ce ldx #$00 ;; c09 -> cf02 -> pos 499 jsr init jsr memcpy jsr cleanup rts .export rd2ce .end -- -- FREE SHIPPING SALE: http://www.atarimax.com/freeshippingsale/ -- * * * Author of Imagic and APE - The Atari Peripheral Emulator! * * * * * * Turn your 8-bit Atari into a p owerhouse with APE! * * * * * * Ape Homepage: http://www.atarimax.com/ * * * * * ********************************************************* * * !! Request my *FOR SALE* LISTING OF CLASSIC VIDEO GAME STUFF -- 2000+ Items !!
  12. RastaSlide 4.2.zipRastaSlide 4.2 - RastaConverter Slide Show Maker and Tools Changes in version 4.2 - Reduced Colour Mapping Tool mapping failures by checking deeper upcoming changes @MrFish - Fixed truncated slide name display when using many International characters - Fixed corruption on RastaConverter pics extracted from pre-version 4 slide shows - Fixed slide names containing full stops not being recognised - Fixed ini problems when re-adding very sparse over-optimized extracted pictures - Added support for Windows shortcuts when adding slides - RastaConverter pics can now be directly extracted from slide files - Changed to zopfli 1.03 as some pictures taking abnormally long compressing - Higher default compression settings in zoplfi.ini file --i900 instead of --i150 sheddy_aqua_the_boo_buddy_fish.xex
  13. You'll notice there are nowhere near as many graphic and audio assets on the C64 as on the arcade version, as there's no way they'll fit in a single 64K load. Quick cash in port on all home computer versions back in the day sadly. But you can't really blame them for not wanting to release it on 10 disks
  14. RastaConverter kernels definitely stuff 8-bit, 256 colour values into colour registers. It takes advantage of shared colour and hpos values, but whether they are more accurate colours also or just a side effect, I don't know. But they will look different in that special Sophia mode.
  15. RastaSlide 4.1.zip RastaSlide 4.1 - Fixed viewer bug where some slides don't display properly or crash in version 4 - Stopped attract mode kicking in on long slide shows - Fixed bigger than expected slide file sizes in version 4 Kind Regards Sheddy sheddy_glass_paperweight.xex
  16. RastaSlide 4.zip RastaSlide 4 - New tool to add high resolution text to the bottom of RastaConverter pictures - International character set used for picture name during loading if needed - New RastaSlide file format for those features. No longer backward compatible - NTSC/PAL colour mapping tools reinstated in a general colour mapping tool An example of the text tool with Amarok's fabulous snowman picture Please feel free to message me about bugs, questions or suggestions. Happy Holidays Sheddy amarok_snowman_'merry_christmas'.xex
  17. I've really not managed to learn much GO so thanks for the tips also. Will have to try the GUI libraries at some point but all GUI stuff seems steep learning curve
  18. Please, if you could. It looks like the tool failed to undo a move of a HPOS write which didn't fit in the kernel. That is a bad bug as it relies on that function a lot to know what will work or not.
  19. @Beeblebrox please can you PM me the XEX that is causing the trouble. I'll have a look at what is going on. Thsnks
  20. I'm suspecting there's not much. Lack of native GUI support with GO means not many end user programs like PM graphics editors, for example - You'd have to write browser code for the interface and wouldn't need GO at all if someone could already do that. I have code that reads an ATR and XEX but not in a separate package. Other things I've done seem to not be so useful for Atari in general - too low level and specific to use in other projects.
  21. Taking longer than expected. The story of my life. There's a bunch of issues putting back the NTSC and PAL colour converter which I thought I'd quickly do for MrFish.
  22. Definitely would recommend to use latest RastaSlide 3.4 Fix Tool rather than the one from 3.3. It was the only change worth sharing for now, but I wanted to get it out there for you guys. Here's the difference it can make on one of my old (more rubbish that I'd hoped for) pictures I shared: There are still HPOS error lines that will be impossible to fix though where RastaConverter needs the Atari to respond more quickly that the real hardware can actually do (and it seems a really hard fix for new people with good C++ knowledge coming at the RastaConverter code unfortunately) @Atari8man2004 you are on a roll! thanks for sharing - great stuff RastaSlide 3.4.zip
  23. Yep, started out using Fox example, thanks. will PM you at some point. Won't be getting a GUI any time soon though as there's a lot of learning involved on my side for that to be possible
  24. Should be fairly random chances on colour mapping success. Interesting if that holds true is all cases.
  25. You may have found the only picture where it has done a reasonable job! I ripped it out of the latest version in disgust. It makes sense that "easier" pictures have a better chance of a good result, so perhaps I should put it back in. The colour mapping was very basic. But with minimal work it could be made a bit smarter and prioritize the most visible colour differences between PAL and NTSC. What do you guys think those are though? I'm thinking maybe very dark or very bright colours might not be very noticable different between PAL and NTSC? Hmm, except skin tones will stand out in a face. What about the red greens and blues. between the systems. Which of those are most noticeably different? Also, It may surprise @Beeblebrox to hear, but I am actually trying to implement his request for making slides with text at the bottom of pictures in a usable/compatible manner. Hopefully will have something to share in the not too distant future. 🫥
×
×
  • Create New...