Using Singe games with Hypseus Singe (inc. Raspberry Pi) #60
Replies: 2 comments
-
One option is to use the This utilizes a resized overlay that can reduce CPU utilisation and correct audio/video sync issues. As these games are not designed to be run with this option it may cause some overlay misalignment. Usually in the lower right 'lives' display. This misalignment can be corrected in one of two ways:
For example, in
|
Beta Was this translation helpful? Give feedback.
-
If you already own a Singe 2 HD MPEG-2 version of video (
Note: Always, try to maintain aspect ratios when recoding. Most overlays are designed to work at the original resolution of the video as described above. Hypseus Singe will try to align the overlay according to the new resolution. Sometimes it may be necessary to change sprite positioning, via the service menu (9 in-game) if supported, or in the LUA. The LUA is an easily editable text file, locate the sprite name in the LUA file then alter the x or y coordinates:
Remember these are fan written games, and designed to be easily altered and improved. |
Beta Was this translation helpful? Give feedback.
-
There are currently two generations of the Singe games: Original Singe (1) and Singe 2.
Singe games are simulation in LUA, not emulation via ROM, like Daphne. They are fan created and easily editable.
Original Singe games were contained in a sub-folder of Daphne conveniently called
singe
* and ran as a plugin to Daphne (alongside the original vldp and vldp_dl game data folders of the original Daphne).Daphne used MPEG-2 and OGG (video.
m2v
and audio.ogg
) containers. Hypseus is an extension of this original engine and therefore adopts this structure and video/audio format to maintain Daphne compatibility.Singe 2 is a complete rewrite of the Singe engine, uses a different video container (
MP4
) and adopted a different folder structure. It also does not contain the Daphne emulation engine.You cannot directly use Singe 2 MP4 in Hypseus, they require recoding to MPEG-2. The LUA and other peripheral files are now fully supported including full 32bit overlays. Only minor changes are needed to LUA resource paths using the MYDIR and BASEDIR variables in the main .singe file.
If you possess original Singe (1) games you should be able to use them directly (See below also).
For porting Singe 2 games
we flatten the folder structure, à la Singe 1, and convert video/audio to align with the original Singe format. Changes to the overlay structure are made in the LUA and graphics for SBC versions with lower resources. No changes to gameplay are made.For Singe 2: Convert the MP4 to MPEG-2 and OGG as described in the porting repo.
The 'ffmpeg' tool is simple and fast, so should only take a few minutes to convert video on a standard PC.
You will find it faster to encode on a PC (Windows binaries are available) rather than a Raspberry Pi.
A full list of games can be found in the porting repository: https://github.com/DirtBagXon/hypseus_singe_data
.daphne
for Retro Emulation platforms]Your only porting concern should be the video and audio files, everything else needed is in the porting repo. If you are familiar with Daphne, you will know about framefiles, so reference these (.txt) for the video/audio file structure layout.
Although original Singe games will work unaltered, there is a
00-singe1
folder in the porting repo, this either fixes bugs found in the original games or makes alignment changes that work better in hypseus overlays. Using these is advisable.Many of the Singe 2 games contain high bitrate HD video and the Raspberry Pi will struggle to render them at reasonable speeds. On these games it may be better to downscale the video at the ffmpeg stage, so a 1920x1080 MP4 recode would be downscaled like this (Halve each axis resolution):
* The singe folder is required (as it is hardcoded in the LUA ) but hypseus contains a path rewrite argument,
-retropath
, that can remove the need for this directory in Retro Emulation platforms. See hereBeta Was this translation helpful? Give feedback.
All reactions