Simius Posted May 16, 2017 Author Share Posted May 16, 2017 CSYNC isn't TTL signal. It is 0.3Vpp/75ohm. Quote Link to comment Share on other sites More sharing options...
+mytek Posted May 22, 2017 Share Posted May 22, 2017 I got another HD Monitor that works with Sophia's Component output mode... It's an older SCEPTRE X32GV-Komodo 32" HDTV. It has all kinds of inputs: HDMI, 2 sets of YPbPr (component), 2 sets of S-Video, 2 sets of CVSB (composite), and VGA. Since this is an older model, you'll have to find one on the used market. I lucked out and picked mine up from a thrift shop for $25 in perfect but dusty condition. It also works very well in S-Video mode, and has lots of set-up options such as 4:3 normal, wide, or zoom aspect ratios. It mates up very well with Sophia, and produces a beautiful picture. - Michael 1 Quote Link to comment Share on other sites More sharing options...
GlowingGhoul Posted May 23, 2017 Share Posted May 23, 2017 How difficult would it be to accommodate artifcting? Could the Sophia recognize bit patterns are replace them with the colored pixels seen in artificting? I know it's not a euro thing, but such capability would make Sophia the perfect video upgrade, and allow non-NTSC users to enjoy all the early games that utilized artifacts. Quote Link to comment Share on other sites More sharing options...
carlminer Posted May 26, 2017 Share Posted May 26, 2017 Can you add me to your next run of the Sophia please? Quote Link to comment Share on other sites More sharing options...
Synthpopalooza Posted May 27, 2017 Share Posted May 27, 2017 OK, new trick ... here's how to detect if an Atari has Sophia: * Set screen to Antic 4 and GTPRIOR to mode 10 * Fill the background with color pattern #1000 * Place PM0 on the screen and check the collision register. If it's been tripped, then you have Sophia. If not, you don't. This is because color pattern 1100 in Antic 4 Graphics 10 produces color pars of PM0 and PF1. On a non Sophia system it produces BAK register (712) which will not trigger a collision. 4 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted May 27, 2017 Share Posted May 27, 2017 OK, new trick ... here's how to detect if an Atari has Sophia: * Set screen to Antic 4 and GTPRIOR to mode 10 * Fill the background with color pattern #1000 * Place PM0 on the screen and check the collision register. If it's been tripped, then you have Sophia. If not, you don't. This is because color pattern 1100 in Antic 4 Graphics 10 produces color pars of PM0 and PF1. On a non Sophia system it produces BAK register (712) which will not trigger a collision. that needs to be in a handy utility form! Quote Link to comment Share on other sites More sharing options...
Simius Posted May 28, 2017 Author Share Posted May 28, 2017 OK, new trick ... here's how to detect if an Atari has Sophia: I'm affraid it will not work. Because the collision detection is performed by original GTIA. Quote Link to comment Share on other sites More sharing options...
Synthpopalooza Posted May 28, 2017 Share Posted May 28, 2017 So pm to pm or pm to pf collisions no longer work with this upgrade? Quote Link to comment Share on other sites More sharing options...
Simius Posted May 28, 2017 Author Share Posted May 28, 2017 So pm to pm or pm to pf collisions no longer work with this upgrade? Why? Quote Link to comment Share on other sites More sharing options...
Synthpopalooza Posted May 28, 2017 Share Posted May 28, 2017 Well, it is a matter of curiosity ... A lot of Atari games rely on hardware collision registers which check to see if the PM has collided with other PM's or the playfields. If the collisions are no longer handled by the original GTIA, then my question is, how are they handled now? Quote Link to comment Share on other sites More sharing options...
Simius Posted May 28, 2017 Author Share Posted May 28, 2017 Who said the collision are no longer handled by the original GTIA? Quote Link to comment Share on other sites More sharing options...
Synthpopalooza Posted May 28, 2017 Share Posted May 28, 2017 (edited) I misunderstood you then perhaps ... I'm affraid it will not work. Because the collision detection is performed by original GTIA. How my method for detecting Sophia is supposed to work is ... you set up Antic 4, and change the GTIA into Graphics 10. You then place $88 (decimal value 136) into the character memory that references ATASCII 32 (screen code 0) to fill up the screen with color pattern %1000. On a normal stock Atari that produces BAK (712). But with Sophia, you get alternating vertical stripes of PM0 (704) and PF1 (710). So, if you then placed a PMG on top of the screen, why wouldn't the PF1 trigger a PM collision between PM0 and PF1? Anyone who has a Sophia, try typing this in, in BASIC: 10 GRAPHICS 12: POKE 623,128:POKE 756,6 20 FOR I=0 to 7:POKE 1536+I,136:NEXT I 30 POKE 704,192:POKE 705,212:POKE 706,60:POKE 707,30 On a normal Atari this produces black, on Sophia, blue and green bars. Edited May 28, 2017 by Synthpopalooza Quote Link to comment Share on other sites More sharing options...
foft Posted May 28, 2017 Share Posted May 28, 2017 My understanding is that the original GTIA is still present and active. So all _reads_ still go to the original gtia, which is unaware of Sophia. So Sophia listens to the bus to work out colours + mode then listens to AN0-AN2 for data. Quote Link to comment Share on other sites More sharing options...
Synthpopalooza Posted May 29, 2017 Share Posted May 29, 2017 OK, attaching an .ATR Boot this, and run "D:SOPHIA.TUR". It clears the screen, puts CHR$(0) on screen, then puts color pattern %1000 over the whole screen. It then puts PM0 on top and checks the collision register. On my stock Atari it returns "SOPHIA NOT FOUND." ... someone with a Sophia, please run this and tell me if it detects your hardware. sophia.atr 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted May 30, 2017 Share Posted May 30, 2017 How difficult would it be to support a touch screen monitor? Run a jumper over to PoKey and use the unused paddle port for the x-y location of the touch. 1 Quote Link to comment Share on other sites More sharing options...
Simius Posted May 30, 2017 Author Share Posted May 30, 2017 This is the Sophia Rev.C board with the DVI output. 6 Quote Link to comment Share on other sites More sharing options...
TheMontezuma Posted May 30, 2017 Share Posted May 30, 2017 (edited) This is the Sophia Rev.C board with the DVI output. Great news! Do you have any numbers regarding video processing delay? Is is fast enough to play games? What about compatibility with (U)HD TVs (using DVI/HDMI adapter)? Edited May 30, 2017 by TheMontezuma Quote Link to comment Share on other sites More sharing options...
Simius Posted May 30, 2017 Author Share Posted May 30, 2017 Sophia generates 64us (one line) delay only. Compatibility with HDTV through HDMI will be tested as soon as the cable is prepared - this afternoon. 5 Quote Link to comment Share on other sites More sharing options...
Simius Posted May 30, 2017 Author Share Posted May 30, 2017 How difficult would it be to support a touch screen monitor? Run a jumper over to PoKey and use the unused paddle port for the x-y location of the touch. I think it is easy, but I don't know, if the paddle inputs are suitable for this application. Definitely not suitable for the capacitive touch screen. Rather an interface similar to the AKI. Quote Link to comment Share on other sites More sharing options...
foft Posted May 30, 2017 Share Posted May 30, 2017 I found hdmi very fussy. I had to use exact 27MHz pixel clock and adjust the system clock to make Atari exactly 50Hz/60Hz. Then use buffer of a few accumulated scanlines intra frame. Quote Link to comment Share on other sites More sharing options...
+mytek Posted May 30, 2017 Share Posted May 30, 2017 (edited) This is the Sophia Rev.C board with the DVI output. I definitely want at least three of these if you decide to produce them. Scratch me off the list for the component version (assuming that the DVI version is successful). - Michael Edited May 30, 2017 by mytekcontrols Quote Link to comment Share on other sites More sharing options...
Simius Posted May 30, 2017 Author Share Posted May 30, 2017 I found hdmi very fussy. I had to use exact 27MHz pixel clock and adjust the system clock to make Atari exactly 50Hz/60Hz. Then use buffer of a few accumulated scanlines intra frame. Perhaps you're right. But for instance on Medion MD30293 22" LCD TV HD Ready (native 1680x1050) works fine. Other TV I'll test later. Quote Link to comment Share on other sites More sharing options...
+Philsan Posted May 30, 2017 Share Posted May 30, 2017 Already fixed. What's the name of such Our5oft demo? Can you please post the fixed firmware? I received USB Blaster. Quote Link to comment Share on other sites More sharing options...
TheMontezuma Posted May 30, 2017 Share Posted May 30, 2017 Can you please post the fixed firmware? I received USB Blaster. Here you are: http://atariage.com/forums/topic/258702-new-development-gtia-in-cpld/page-19?do=findComment&comment=3745241 Quote Link to comment Share on other sites More sharing options...
+Philsan Posted May 30, 2017 Share Posted May 30, 2017 Here you are: http://atariage.com/forums/topic/258702-new-development-gtia-in-cpld/page-19?do=findComment&comment=3745241 Thank you Marcin but I think it's not the latest version. A bug was discovered and fixed eventually. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.