| |
Compyx
Registered: Jan 2005
Posts: 631 |
Release id #212349 : VICE 3.6
Since there are some questions in the comments section of VICE 3.6, I figured it would be better use the forum for any questions.
So to start things off:
Quoting The Human Code MachineBut how can I save the monitor window position on GTK3 Vice Windows x64? After exiting it always opens the same small window.
Currently you can't, window resizing/repositioning support is different across OSes/WMs, so making this work properly for all configurations may never work. That said, I'm working on a "fix" to make it at least work on some systems. |
|
... 65 posts hidden. Click here to view all posts....
|
| |
Compyx
Registered: Jan 2005
Posts: 631 |
All the ffmpeg dylibs appear to be in the Mac dist, so can someone check "Help" -> "Compile time features", and see what it says for HAVE_FFMPEG? |
| |
Rastah Bar
Registered: Oct 2012
Posts: 336 |
r41431:
HAVE_FFMPEG yes
HAVE_FFMPEG_AVRESAMPLE no
HAVE_FFMPEG_HEADER_SUBDIRS yes
HAVE_FFMPEG_SWRESAMPLE yes
HAVE_FFMPEG_SWSCALE yes |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
That's the same as my Linux build. That means VICE is configured for ffmpeg and the video recording tab should work. Odd. |
| |
Youth
Registered: Aug 2003
Posts: 40 |
Sorry wasn't accurate enough, I am using the Apple Silicon Mac (arm64) version. This version does not let me select a video driver (empty dropdown). It says HAVE_FFMPEG yes in the Help section.
I have checked though; this doesn't seem to be an arm64 binary, this is what I did:
lipo -archs x64sc.app/Contents/MacOS/x64sc
The result: x86_64, where it should say arm64
So I tried the Intel Silicon Mac version, this also reports x86_64 architecture, but the video recording works on this version!
For now I will use the Intel (x86_64) version. My two cents from this:
1. The Apple Silicon version on the website it not actually an arm64 binary. It is an Intel x86_64 binary. It will run through the Rosette emulation layer and not make use of the arm64 advantages (speed/stability).
2. You could offer a universal binary with both architectures in it. I did this for SIDFactory II, maybe I can be of some help. |
| |
dqh
Registered: Jun 2019
Posts: 46 |
The binary is ARM - but the wrapper/launcher .app binary is not. The wrapper is generated with platypus, which currently always generates x86 apps. However this is is a launcher, the real binary is tucked away inside VICE.app.
I've replicated the ffmpeg thing on my M1 - I'll look into it and fix it for VICE 3.6.1. |
| |
dqh
Registered: Jun 2019
Posts: 46 |
Quote: There's a "bin" folder next to the app folders, i believe, containing the CLI incarnations of the programs.
Worked for me, although something was always quite off with the working directory.
I've fixed the working directory thing btw. The bin/ launchers will now preserve the current pwd, and the .app launchers will set it to your home directory instead of a folder within VICE.app :)
These changes will be in 3.6.1 but you can get the new behaviour from the r41431 builds at https://sourceforge.net/projects/vice-emu/files/experimental%20.. |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: I've fixed the working directory thing btw. The bin/ launchers will now preserve the current pwd, and the .app launchers will set it to your home directory instead of a folder within VICE.app :)
These changes will be in 3.6.1 but you can get the new behaviour from the r41431 builds at https://sourceforge.net/projects/vice-emu/files/experimental%20..
Thank you for your mac efforts, highly appreciated! 🙏 |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Quoting dqhThe wrapper is generated with platypus, which currently always generates x86 apps.
In case you haven't gotten around to it yet, I just tried Platypus 5.4 r1217 built from the current GitHub master branch and verified that it generates x86_64 + arm64 apps. |
| |
Erhan
Registered: Feb 2005
Posts: 17 |
i'm curious if these bugs only happen in my system...
win10pro 19043.1415 locale TR lang TR,
x64sc.exe,
emulation screen appears in windowed mode as usual, after i click CRT or Mixer controls at lower panel, window is expanded. Unclicking them, gray bars appear above & below emulation screen.
vsid.exe,
buttons below playlist, only
add tune to playlist and clear playlist buttons work. others not. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
That happens on all systems.
The gray bands appear because Gtk doesn't resize the window after the CRT and/or mixer widgets are hidden. And since both the main menu bar and the status bar are set to non-expanding, it expands the rendering area. I used to resize the window to 1x1 pixels when disabling a CRT or mixer widget, causing Gtk to minimize the space used for the window, but that obviously didn't work well for people who had their window manually stretched to a certain size.
Throw in the fact that window decorations are involved in getting/setting window sizes and Gtk doesn't know about them (the window manager adds those) and things get hairy quickly.
I've added a hotkey to restore the display to its minimum size (Alt+R) to alleviate the problem at little bit, quicker than manually dragging the window to its minimum size.
The VSID playlist is still a work in progress, and low priority. My focus (heh) is on the proper emulators, especially x64sc. I'll work on VSID again after we've released 3.6.1. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 - Next |
