forum.defence-force.org

Does flipflop work? Surely you're calling it at 100hz (1 and -1 both should evaluate to true).

Would expect something like FlipFlop ^= 1 (initialised to 0 or 1).

Nice! Good work.

I have to say I used to have the exact same opinions as dbug on svn vs. Git but when my work went all in on git and i had to learn it properly, i did an full 180 and now I love git and find going back to svn a pain in the arse.

I also have experience with CVS and ClearCase as well as svn and git.

Simple. Real PAL television sends a 312 line field followed by a 313 line field (interlacing). The oric (and other old computers) send a progressive scan image (continuous 312 line frames) which isn't really to PAL spec but TVs would generally sync OK anyway.

1 frame isn't 20000 cycles.

Its 64 cycles per scanline x 312 lines = 19968 cycles.

If you upload oricutron videos direct to YouTube, they often turn into an overcompressed mess, although it seems to depend slightly on the device you use to play it back. There is a thread on here describing how to pass the video through ffmpeg first for better results.

Looks really nice . I wish you had put the vid through ffmpeg before uploading, though.

Just a quick additional note, if you change the "scale=720:672:flags=neighbor" parameter to "scale=960:672:flags=neighbor", you'll also give the video a bit of a horizontal stretch and make it look closer to the aspect ratio of a real Oric:

Several people have found that if you upload Oricutron video captures direct to youtube, it re-encodes them into a crappy mess, even though the original video was losslessly encoded (and thus pixel perfect). The issue is that the videos are low resolution (240x224), so youtube encodes them with low ...

Our, to avoid fisheye, you just add a constant to all your distances, iirc. Simples.

This is really cool Good work!

Oricutron also has accurate AY noise (or should )

Wow, iss! Nice work! Glad someone has time to work on Oricutron while I'm too busy

No, it doesn't need to encode that.

Normal Oric data is stored in decoded bytes (same as .tap), so the fast/slow encoding has been stripped off. You could re-encode it as fast or slow if you like.

Other data is encoded as a waveform, so again no "fast" or "slow" really applies to the format.

Thats awesome, and the end result looks really great!