ivop

This thread has some tunes that solely use 16-bit Pokey channels, in stereo. Note to self: convert sid2gumby to mads

SGS Microelettronica from Italy merged with Thomson and eventually changed its name to STMicroelectronics. Perhaps you can get some information from them?

Answering everything after "IIRC" which was not there when I first answered There are four players, 8 pixels wide each, and four missiles, 2 pixels wide each. Players and missiles share a colour register, i.e. player two has the same colour as missile two, unless a certain bit is set and the missiles are treated as a fifth player. In that case, player five (the four missiles) have the same colour as playfield 3, which is not available in graphics 15, the 160x239 four colour mode, which has a background colour and three playfields (0, 1, 2). But, as said in the previous post, the missiles are not used by rastaconverter. About multiplexing, it is possible to change the horizontal position of a hardware sprite after it has been displayed to some point further on the same scanline and it will be displayed again. Players and missiles either get their pixel data through DMA (the contents remain the same if you reposition) or you can write the pixel data directly to the GTIA chip through five GRAFx registers (4 players, 1 register for 4 missiles).

Eight, but the extra four have a lot more restrictions. The four playfields cover 160 pixels, the four players 8 consecutive pixels each. Repositioning a player on the same scan line could potentially add 8 more, but the content is not dynamic, so these pixels have to be the same. Don't think that happens often, unless all 8 are on (one/1) and the player is used to fill large patches of the same colour. The missiles are not used at all. Adding those would add 2 pixels each of the same colour as the corresponding player or all four missiles can share a colour if you enable fifth player. But, IIRC you still need four HPOS registers for the missiles, so that's probably why Ilmenit did not use them.

It's the Amsterdam Gay Pride Week. The canal parade is this Saturday. Here's 8-bit pride! PAL, 51 colours: NTSC, 57 colours: Both images do NOT use any player/missiles! As mentioned in the "Rastaconverter bug"-thread, this image triggers the bug within a couple of million evaluations. They did look better with PMs though Anyway, I thought these turned out pretty good with only four colour registers ivop-rainbow_flag.xex ivop-rainbow_flag_ntsc.xex

Currently I'm converting an image that is displaying this behaviour very quickly. Usually before 2M evaluations are reached. "Fixing" it by the above mentioned method only works for a short time and then the artifacts reappear. Sometimes at the same places, sometimes they move around a bit. It's really unworkable, which is a pity because the image looks great after 50M evals (55+ colours, very little banding). Adding dither did not help. It keeps stumbling on this bug. So, any chance this will be fixed, either by ilmenit or phaeron? Or can either of you give me some pointers to fix it myself? Thanks in advance! I can send the offending image if that helps.

I recently listened to some of your podcasts (Mensch, Zdybel, Koala guys, and a few more) and must say I very much enjoy your interviews! Makes walking through nature and around large patches of water so much more pleasant I wonder though why you beep out certain words. Especially if the connection wasn't that good to begin with, sentences are getting hard to mentally paste together if there are beeps in it. Another thing, how does one properly pronounce Atari? I have heard anything from Ah-Tah-Ree to Uh-Toh-Ree and variations in between Maybe that's something for another thread...

A bit more mellow images. 33 colours: 41 colours: ivop-windmill.xex ivop-kinderdijk.xex

Here's some more Eddie 32 colours: 42 colours: ivop-book_of_souls.xex ivop-eddie.xex

You can ask Albert for permission. I have one such 1st post I can edit indefinitely

You're right. I was thinking of atariwarez's device. That one used an alternate vid/pid for its ftd232.

IIRC Steve used an alternative VID/PID for his device. On Linux you can override this. Connect the device, run lsusb to see what VID/PID he used, unplug the device, modprobe ftdio_sio and echo $VID $PID > /sys/bus/usb-serial/drivers/ftdi_sio/new_id Plug the device back in and it should show up as /dev/ttyUSB0 I'm pretty sure something like this is possible under MacOS X. Or you could set the vid/pid back to the default values with FT_PROG (http://www.ftdichip.com/Support/Utilities.htm#FT_PROG) or ft232r_prog (http://rtr.ca/ft232r/) after which the official ftdi drivers should work.

OH-WAH-AH-AH-AH I think I'm down with the sickness... ivop-guy.xex ivop-guy2.xex

Now (nearly) exact measurements would help, width and length being the most important, in order to "de-skew" the images properly and line them up correctly. After that, perhaps you can convert the images to components for KiCad (bitmap2component) and import them on the eco layers to draw over them.

Coming from multiple "Open Source" mailinglists (ffmpeg-devel, Linux Kernel Mailinglist, et cetera) I find AtariAge mostly free of people with an ego that's too big for them. It's not that bad. It can be much worse!

Here's an Amiga picture (Hair Dog by Cougar) 46 colours ivop-cougar-hairdog.xex

I was under the same impression, i.e. a detail mask did not have much effect, but I totally overlooked and never used /details_val to make the mask have more influence on the decisions made. Guess I'll have to try it again next time.

I needed to add -std=c++1y to compile properly. Otherwise, excellent work!

According to Rob Zdybel (ANTIC Podcast #184), the designer of the 850 was an avid model railroad collector and he actually designed it around his needs for controlling his model trains! That's why there are so many ports.

Yes, it is. Different revisions of the schematic have all been posted here during the design process. Once all known bugs are solved all development files will be released to the public. Some of the components are not open source though. Sophia, UAV and U1MB are all closed.

A full 800XL PCB (or even 600XL) won't fit in the free version of Eagle. I'd say go with KiCad. I think it would be best if you have a high resolution photo of a bare original PCB (top and bottom) and copy that with pcbnew. I'm aware you want a PCB that takes all the original components, but if you're prepared to drop that requirement, I'd say: wait for the 1088XEL design to finalize, redraw it in KiCad and layout the components on an 800XL outline, add the keyboard connector and the circuit that connects it to the Pokey. Then, export gerbers, board house, et cetera

Yeah, it looks a bit more ghoulish with the NTSC palette Here's another one from a favorite band: I cut it out with The Gimp from the original album cover. The whole cover did not fare well 37 colours, PAL. ivop-pal-misplaced_childhood.xex

This is exactly the same "crash screen" I got during my "troubles with U1MB and SIDE2". Don't know what causes it yet. You are seeing part of the program and data memory. The CPLD part does not necessarily apply to you (probably not).

Inspired by The Trooper above: 40 colours ivop-piece_of_mind.xex

If I'm not mistaken, the 1200XL was actually the first XL. The 600XL and 800XL came aftwards, so they moved the cartridge port from the side to the top.