Re: Clock Signal — an Oric emulator for macOS and Linux
Posted: Wed Jul 08, 2020 8:20 pm
Defence Force forums
https://forum.defence-force.net/
Oh, cool! I was just coming here to mention it but I guess that you got ahead of me. I've also been trying to put together a Snap so that it'll appear directly in the app stores of various Linux distributions. Hopefully I'll crack that shortly. That plus whatever Qt issues turn out to be lurking.
I admit I don't really know what modern Pis support, but a potential obstacle is that I'm still targeting OpenGL 3.2+ only. I could probably relax that now; since Apple deprecated OpenGL I've boxed in the permitted input pixel formats for emulated machines and could probably deal with them all in old-fashioned all-floating-point GLSL.
Thank you Iss .. Unfortunately, it doesn't prevent ClockSignal from crashing when I drag'n'drop the rom ..
Assuming you installed the Snap, try refreshing it — `snap refresh clock-signal` from the command line, or there’s probably a check-for-updates button somewhere in the app listing if you’re using one of the storefronts.
Code: Select all
jibe@jibe:~$ sudo snap install clock-signal --edge
[sudo] Mot de passe de jibe :
clock-signal (edge) 20.7.20 from Thomas Harte (tomharte) installed
jibe@jibe:~$ sudo snap refresh clock-signal
le snap "clock-signal" n'a aucune mise à jour disponible
Code: Select all
jibe@jibe:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Code: Select all
jibe@jibe:~$ clock-signal
Qt: Session management error: None of the authentication protocols specified are supported
jibe@jibe:~$ unset SESSION_MANAGER
jibe@jibe:~$ clock-signal
Code: Select all
Cannot make QOpenGLContext current in a different thread
Abandon
Code: Select all
clock-signal -h
Code: Select all
jibe@jibe:~$ sum clk-roms-pack/basic11.rom
64837 16
jibe@jibe:~$ sum clk-roms-pack/basic10.rom
49049 16
jibe@jibe:~$ sum clk-roms-pack/colour.rom
31501 1
Code: Select all
jibe@jibe:~$ ls /home/jibe/snap/clock-signal/49/.local/share/ClockSignal/ROMImages/Oric/
basic10.rom basic11.rom colour.rom microdisc.rom
If it helps at all, Ubuntu Software and direct snap installs are identical — the former uses the latter underneath. But the two distributions I tested with access to the Snap store provided completely different storefronts so giving you the command line was easier.
I suspect there may be a bug here in a workaround I put in place for Qt's method of vsync handling*. What happens if you resize the window? Does it draw in once, then stop until you resize again?
It should handle arbitrarily many files dragged at once, and it identifies them by their CRC32 so you can call them whatever you want. Though it will store them on disk with their normative names.
I saw that myself for the first time yesterday, and have exactly one working theory on it, formulated long after I'd turned the computer off for the day — I think it's whenever one of the activity indicator lights changes, and I've accidentally relied upon something that happened to work in one version of Qt but isn't portable.jbperin wrote: ↑Mon Jul 27, 2020 1:22 pmCode: Select all
Cannot make QOpenGLContext current in a different thread Abandon
Oh, no, that's officially a brand new bug! The Qt version has a really simple command line parser that accepts a file name only. But you've now made me aware that it doesn't properly validate that a file is available.jbperin wrote: ↑Mon Jul 27, 2020 1:22 pm I finally managed to get the drag'n'drop screen back by invoking Cock Signal with an option on command line.
I naively typed :hoping for help .. But I got the start screen .. splitted in two .. with the drag'n'drop part at the bottom.Code: Select all
clock-signal -h
Then I tried to drag'n'drop the roms again but Clock Signal seems not to accept the drag'n'drop on this splitted screen.
No, no, this is fantastic stuff. I really want to get it working properly as a Snap so that I can move it from the 'edge' channel it is currently in and therefore have a natural Ubuntu Software presence. But the world of Linux is such a wide diversity of targets that it's really hard for me to test any substantial subset of them.jbperin wrote: ↑Mon Jul 27, 2020 1:22 pmThomH, I don't want you to loose your time with my struggling with Clock Signal.
I would be very glad to help you by testing things on my ubuntu and give you feed back.
So tell me if you want me to do some more test for you.
But don't loose your time to help me if it works fine for other users.
We can just conclude that I'm a piece of S..T and it's ok.
I want to reiterate my congratulation for this great achievement that is ClockSignal .. and I propose to help for testing because I find it is a great soft.
Code: Select all
jibe@jibe:~$ sudo snap refresh clock-signal
[sudo] Mot de passe de jibe :
clock-signal (edge) 20.7.27 from Thomas Harte (tomharte) refreshed
jibe@jibe:~$ sudo snap info clock-signal
name: clock-signal
....
...
....
snap-id: hAhWy92W0iaSsdrDfufklSnk0AGAr9QS
tracking: latest/edge
refresh-date: today at 07:11 CEST
channels:
latest/stable: –
latest/candidate: –
latest/beta: –
latest/edge: 20.7.27 2020-07-28 (57) 97MB -
installed: 20.7.27 (57) 97MB -
Code: Select all
[ 1206.475959] audit: type=1400 audit(1595914045.134:146): apparmor="DENIED" operation="capable" profile="/snap/core/9665/usr/lib/snapd/snap-confine" pid=3375 comm="snap-confine" capability=4 capname="fsetid"
[ 1206.504252] audit: type=1400 audit(1595914045.162:147): apparmor="DENIED" operation="open" profile="snap.clock-signal.clock-signal" name="/snap/core/9665/usr/share/locale/fr/LC_MESSAGES/snappy.mo" pid=3375 comm="snap-exec" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 1250.270940] audit: type=1326 audit(1595914088.933:149): auid=1000 uid=1000 gid=1000 ses=2 pid=3375 comm="ClockSignal" exe="/snap/clock-signal/57/opt/ClockSignal/bin/ClockSignal" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f24ed40bb9f code=0x50000
[ 1250.270948] audit: type=1326 audit(1595914088.933:148): auid=1000 uid=1000 gid=1000 ses=2 pid=3375 comm="ClockSignal" exe="/snap/clock-signal/57/opt/ClockSignal/bin/ClockSignal" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f24ed40bb9f code=0x50000
[ 1250.270981] audit: type=1326 audit(1595914088.933:150): auid=1000 uid=1000 gid=1000 ses=2 pid=3375 comm="ClockSignal" exe="/snap/clock-signal/57/opt/ClockSignal/bin/ClockSignal" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f24ed40bb9f code=0x50000
[ 1250.284063] audit: type=1326 audit(1595914088.945:151): auid=1000 uid=1000 gid=1000 ses=2 pid=3375 comm="ClockSignal" exe="/snap/clock-signal/57/opt/ClockSignal/bin/ClockSignal" sig=0 arch=c000003e syscall=203 compat=0 ip=0x7f24ed40bb9f code=0x50000
Code: Select all
jibe@jibe:~$ export LANG=en_US.utf8
jibe@jibe:~$ clock-signal
The blank screen happens only when I press the Start Machine button. The rest of the interface works because I could drag and drop the rom. and select Atmos. I even tried to setup a microdisc.ThomH wrote: ↑Tue Jul 28, 2020 7:12 pm To clarify on the locale issue: you get a completely blank screen when launching the emulator rather than any sort of GUI, or once you start a machine it then fails to display anything? Regardless, I'll try it in another language tonight and see whether I can reproduce.
It looked responsive but I should have tried an arcade game to really feel how it responds. I'm going to be somewhat busy over the next few days (travelling for vacation). But I'll try to give a try asap.ThomH wrote: ↑Tue Jul 28, 2020 7:12 pm Also, I appreciate I'm starting to sound obsessed, but I'm still not happy with the output latency for the Qt version so I want to look further into that. How does it feel on your machine — responsive to every keypress, or sort of like there's a resistance to action that you have to overcome by typing very deliberately?