This is a MULTI emulator (5-in-1), emulator refresh adds cool features to existing emulators.
They both add features to the existing emulators. They both aim to add key bindings, customisable controls and a graphical UI.
The point of emumaster is that it does all of these at the same time with reusable code. Update the configurations once and it's for all emus.
And for anyone saying 'but emumaster is five emulators in one'. No, it is a front-end. The emulators are essentially plug-ins (they are separate apps!) that are added and called by emumaster when required. The emulators used aren't unique to emumaster and actually have their own source repositories. This is why we can re-use the community emulator ports in emumaster.
Hello,
I am creator of original EmuMaster. I want to clarify some things.
Original EmuMaster is not front-end only. It's frontend+backends.
This port will essantially differ in experience since different backends are used. It's a whole different thing. This port only looks and has similar functionality and same intent, but is essentially different from original EmuMaster.
My backends are essential in my project, and they integrate seamlessly in my application. Therefore the user does not see a difference between nes,gba,psx .... emulations at all.
I have to just warn you that it's not EmuMaster at all. The frontend used here is only a small amount of work put into the project.
I wish well to this project, but I wanted to clarify above things.
Kind regards,
elemental
Hello,
I am creator of original EmuMaster. I want to clarify some things.
Original EmuMaster is not front-end only. It's frontend+backends.
As mentioned in first post.
Originally Posted by _elemental_
This port will essantially differ in experience since different backends are used. It's a whole different thing. This port only looks and has similar functionality and same intent, but is essentially different from original EmuMaster. My backends are essential in my project, and they integrate seamlessly in my application. Therefore the user does not see a difference between nes,gba,psx .... emulations at all.
The same backends are currently used but just not displayed due to Playbook issue (which may be resolved in next firmware version).
The seamless integration is the same goal of this port and will be achieved in final version.
I have to just warn you that it's not EmuMaster at all. The frontend used here is only a small amount of work put into the project.
I wish well to this project, but I wanted to clarify above things.
Kind regards,
elemental
To clarify, the source repository from elemental is being compiled as-is with both front-end and back-ends provided. The source code is as given by elemental's github.
The work I have done is porting Meego libs to Playbook which has made this possible by (essentially) disabling DBus and changing width/height in Qt Components.
As stated in first post, the back-ends (currently by elemental) will eventually be replaced with more playbook-tuned community ports due to emumaster's method of calling external emulators (back-ends). I'd also respectfully disagree that the front-end is only a 'small amount of work put into the project' as it is most definitely the majority of work with the back-ends having their own community source repositories that simply require integration with libbase for config settings (which is how the other emulators are possible in the first place).
Currently, while not functioning as desired, it is just emumaster (as given by elemental). If there was any confusion, it functions correctly on the N9 of course.
The same backends are currently used but just not displayed due to Playbook issue (which may be resolved in next firmware version).
The seamless integration is the same goal of this port and will be achieved in final version.
To clarify, the source repository from elemental is being compiled as-is with both front-end and back-ends provided. The source code is as given by elemental's github.
The work I have done is porting Meego libs to Playbook which has made this possible by (essentially) disabling DBus and changing width/height in Qt Components.
As stated in first post, the back-ends (currently by elemental) will eventually be replaced with more playbook-tuned community ports due to emumaster's method of calling external emulators (back-ends). I'd also respectfully disagree that the front-end is only a 'small amount of work put into the project' as it is most definitely the majority of work with the back-ends having their own community source repositories that simply require integration with libbase for config settings (which is how the other emulators are possible in the first place).
Currently, while not functioning as desired, it is just emumaster (as given by elemental). If there was any confusion, it functions correctly on the N9 of course.
so we have to wait till next firmware update for issues to be resolved?
Why oh why is this thread slowly closing down, this should be the best thread ever along side with the refresh project because with this thread alive and well known the maker of the app well increase there production by hope and longing desire for the app!
What is the status of the released source code? I really wanted to try to get an Amiga emulator running and put my (legal) kick13.rom in the amiga subfolder, but I guess the problem with loading the uae binary from the main binary is still there.
I downloaded the sources for this and attempted a quick recompile of just uae in Qt Creator, but there are quite a few dependencies to the main emumaster project. Did you manage to get Amiga emulation working as a standalone application?
Amiga should work standalone if you remove all its hooks for configuration (eg. it expects a config file by emumaster front-end).
You should just grab the original Amiga emulator before it was modded to work for emumaster if you are attempting this.
Right now I'm waiting for a future Playbook firmware where running multiple windows is allowed within an app. The API is there but currently faulty.
