I will manually build Winapple at a later time. The lr-mame.sh script is at retroOSMCmk2/submodule/RetroPie-Setup/scriptmodules/libretrocores/lr-mame.sh. I did run the build from the UI. I believe the UI calls the script I just mentioned above. PTR64=0 would perhaps allow 32 bit. I found some messages along those lines. I believe modding that script would be a useful experiment. I
Yes, mame 2015 (maybe but likely buggy) but 2016 or later can run Apple 2 games. It runs very well as I am using a year old mame on Batocera on a PI in another place.
How might I be able to try building lr-mame using PTR64=0? tmp/build is still there.
Update, I guess I found the doc for manually building cores. I am going to try forcing PTR64=0 on make. Maybe that won’t work, but that’s ok.
I guess there’s no reason I couldn’t run standalone mame, and simply apt install mame.
So you are saying, you want to eat the cake and keep it?? That toogle, switches TV of when kodi process enters ending process, guess that switch trigger the same response from kodi.
I wonder if you could do a ugly hack, make a script that switches that setting, and trigger script before and after RetrOSMC launch?
Maybe something like that, or prevent CEC communication at this point. The better and faster solution would be to get the fast switching working with sound, then I could skip this effort altogether.
Not familiar with the topic and the specifics here, but if I get the gist of what is trying to be done here I would suggest a dirty hack might be to insert something like…
cec-client -l>/dev/null
which would pull CEC communication away from whatever program has it (because it only works with one program at a time), to performing an innocuous task, and leave it doing nothing until another program goes to use it (like starting mediacenter again). I’m not sure if it is available without installing cec-utils though.
I originally tried to solve it by temporarily disabling the option, by editing guisettings.xml, but it seems to only be read at launch, so had no effect.
Then I tried over the JSON API, but the option was not exposed.
The fast switching turned out to be a good workaround. I did have a “keep alive” type option in my addon settings that would use it without providing the other frills. I seem to have removed it at some point though.
That was the challenge. The original user had liked the facility as a general rule, but didn’t want the lights to go out every time they started gaming!
Ok, so, apt install mame and adding the config manually to retropie works, spawning off the external emulator. It’s barely fast enough for the Vero V, but it just barely is!
The other option was a newer version of linapple (recalling with was linux version of AppleWin I believe). This version is still called AppleWin and has been in development for a few years. They have a libretro build. It’s found here:
This compiled without issue on the Vero and it’s actually more efficient than mame. I had to manually install into RetroArch as they don’t do that part, but, it runs perfectly! That project is merging all changes to AppleWin into the project as it was designed to be able to easily keep it up to date! It’s very nice for a apple2e emulator on linux.
That might be the most recent version that RetroPie are providing right now. They sometimes freeze at a particular version until proven to avoid instability, or in response to issues.
My installer is now pointing to a fork of Retropie-Setup to avoid breakages when they update sensitive components. From now on I will be updating it to newer versions manually to control that situation.
Cutting edge versions of anything aren’t usually a requirement and early adoption needs to bug reports. Also, most people will prefer to wait for the available binaries that I will have to have manually compiled, rather than installing from source, so it shouldn’t make much difference.
Out of curiosity, what does this incremental update to Retroarch provide that you are looking for?
Ah, I get it, so you are pointing to the fork on purpose, wondered about that as that hasn’t been updated in a year. I definitely understand and appreciate lack of bugs!
I am not a bleeding edge kind of guy at all actually. I’ve been doing a lot of research, and it appears 1.16.0 broke audio for quite a few people. Though I saw no specific bugfix for audio in the changelog for 17, I was going to see if maybe updating made any difference. I cannot for the life of me get any audio at all from retroarch. From standalone mame, audio is fine. Emulationstation also does not play the menu sounds, just clicks. So, just trying to figure out what else I can do. I’ve spent quite a few nights playing with all sorts of settings. I can speaker-test from the command line to a specific device with -D and I get audio, it works. But that same device with alsa, tinyalsa, alsathreads, sdl, nothing works. I am not sure how or why it had worked before unless i was confused or had just run the mame version. Yes, I have an avr, and no I can’t hook it direct (I can for testing but nothing else). The AVR has lots of devices and automation to it. The “tv” is a projector hanging from the ceiling. Don’t have TV. I thought today of trying 3.5mm port to see if analog audio might actually play, which would be ok for the games. Or even spdif. Kodi could still play 7.1.
Update: Got the retro core sorted on audio. It was a core specific issue so all is well.
So is it ok or adviseable to run gamemode in conjunction with retroarch? It suggests it. It’s in the Vero repo so I assume there’s nothing wrong with it on this platform with retrosmcmk2 but just in case anyone found out something wrong with it.
I’m afraid I’ve not been able to reproduce the audio issue with an AVR.
I’ve tested the retrOSMCmk2 launcher, with the Vero4k run by HDMI into an AVR (Denon X2400H).
Audio was working fine without any reconfiguration.
I’ve tried with and without fast-switching enabled.
Just a general question for anyone with a Vero V - does the extra power allow for any additional emulators? On my Vero 4, the PSX and N64 were the limits.
Has anyone tried Dreamcast games? And did anyone notice better N64 emulator compatibility?
PSP emulation was the pinacle on Vero 4K I’d say. Not got it working on Vero V yet. I got it built, but it needs some proper GPU debugging for runtime crashes that I’ve not had time to dig into yet.
I had several Dreamcast successes on the 4K, particularly after I switched to lr-flycast. It’s a bit better on V.
N64 I’ve always struggled with. Not so much performance as outright compatibility issues. Maybe I’m missing a trick with plugins and configuration. MarioKart has always been ok. Smash Bros I was keen to use, but each plugin had it’s own proglems and none playable.
Thanks for the response (and your continued work on this project). I never thought to try the PSP emulators, I will try setting that up on my vero 4k this evening. Hopefully you eventually find the time to debug them on the vero 5.
Similarly I will try lr-flycast on the 4k and see what kind of frame-rate I get in preparation of receiving my vero 5.
I share similar experiences with the N64 emulators at least on the 4k; some of the more popular games run, but most have weird artifacts or don’t run at all. I chalk most of that up to the complexity and fragility of N64 emulation in general though.
I just installed this and I’m wondering which version of MAME I should install for a balance of performance and compatibility on a 4k+.
Once I know that, I’ll know which sets I need to seek out. As I don’t want to break any rules, if someone could PM me for potential sources, I’d appreciate it. I was a long-time and superbly-ratioed member of… “enjoyable half sphere”… but haven’t been back in the game (no pun intended) since they shut down.
I tried lr-mame2010, but it kept crashing on something as simple as Donkey Kong, so it doesn’t appear ready for prime-time. I went to lr-mame2003 and that seems to be running fine, but I’m having an issue figuring out where the samples folder needs to be. This just doesn’t seem to be clearly explained anywhere. I had trouble with getting the roms into the right place, but figured it out through trial and error.
I’m using cifs to get to the files on my NAS. My fstab has the following mount working for the roms:
