MIO bus binding bug fixed, and SCSI bus no longer mislabeled as IDE bus.
On turbo tapes -- the decoder is still a work in progress. There are a couple of cautions regarding creating or using existing recordings of turbo tapes. Unlike the standard Atari encoding, which uses FSK and is relatively robust, turbo encodings are more sensitive to distortion. In particular, attenuation of higher frequencies can distort the waveforms and make the tapes more difficult to decode. The AST-encoded Arkanoid tape in the a8cas example archive has this problem:
This shifts the zero crossing times, affecting decoding. Carefully applying a high-pass filter can reverse this:
Currently Altirra cannot detect or correct for this issue automatically, so it is a manual process. If you are recording an actual turbo tape, turn off all enhancements on the tape deck including Dolby-B; these are not done by a normal Atari tape deck and turning them off will reduce the need to correct the recording.
The analysis mode available in the Tools menu can be useful for diagnosing these issues, though it requires a lot of elbow grease. It decodes the tape and outputs a multi-track sound file that can be opened in a sound editor:
The tracks, from top to bottom, are: resampled raw audio, FSK raw decoder outputs, FSK decoded data, turbo decoder AGC, turbo decoded data.
@Avery did you altered Altirra Hardware Ref guide? as the VBXE part says 128x pattern size possible while Electron's dev docs (and my hardware shows) 64x is max.
"If the IN_USE bit is 1, then, when PATTERN_WIDTH+1 (1 ... 64) bytes have been copied,
the source address value is restored to its initial state for the line, and, next to this, the
PATTERN_WIDTH+1 bytes will be copied again, and the source address will be restored
again etc. until blt_width+1 bytes are copied."
This is fixed in the emulator, but not the hardware manual yet as I release that on an independent schedule.
What are these bars (in corners and right side) in Full Overscan GTIA mode 10?
Tiny bug in horizontal + vertical blank areas. Full Overscan is actually even more than that -- it shows blank/sync regions as well, where there actually isn't any color and beyond what any TV can possibly display. It's there for when analysis modes are used since these overlay cycle timing data over the display. Extended overscan already shows the maximum display region, except for the PAL vertical border hack for which there is a separate option.
Indus GT emulation with LEDs is awesome! Thank you!
Are drive buttons mapped?
Also, with http://atarionline.pl/utils/9.%20ROM-y/BIOS-y%20-%20stacje%20dysków/Indus%20GT%201.4.romI'm getting error 139 on track 27 of Numen_A.atr.
http://atarionline.p...ter Reality.atrdoesn't boot.
The drive buttons are available in System > Console Switches. Some of the button combos that the Indus GT requires for corner functions may be difficult to do, though. That's why the CP/M boot combo has its own entry.
Audio is also supported. For fun, run this (you may need to increase the Power-On Delay setting to give the drive time to finish init): http://atariage.com/...pier/?p=2640869
Error 139 on enhanced density disks means that you are using an old version of the Indus GT firmware ROM. The version labeled 1.4 is actually 1.1 and is known for NAKing sector reads above sector 720 on ED disks:
You need 1.2 for enhanced density to work.
When I run the Altirra from the 2.99-zip file it shows 2.80 in the header and change log. Is this normal for betas or am I missing something. I also don't see 2.9 on the virtualdub.org site.
No, that is not normal. You should be seeing 2.99-test1 in the window caption. Try manually extracting the archive instead of running the executable directly from it, in case something is wrong with the run-from-zip process.