xxOToTOxx

I'm not great at Roadblaster, but a few play throughs and I didn't see any issues... The last several minutes of video are blank filler with final test screens, so the 66 frame discrepancy will not be an issue. Many, many thanks for this. I have been waiting for more up-scaled Daphne video besides the DL standards. The other one that works is Cobra Command by LizardKing: This is growing the collection nicely....

Picked up here:

Wow these look gorgeous: These are full resolution screenshots, although my monitor won't display the whole image, the F12 screenshot captures them perfectly. Still some discrepancies in the frames and timings, but I guess only playing will tell.... mediainfo --Inform='Video;%FrameCount%' rb-orig.m2v 54000 mediainfo --Inform='Video;%FrameCount%' rb.m2v 53944 mediainfo --Inform='Video;%Duration%' rb-orig.m2v 1801800 mediainfo --Inform='Video;%Duration%' rb.m2v 1799931 Correct Frame Rate: Frame rate : 29.970 (30000/1001) FPS Run version 2.6.12 of Hypseus Singe with: hypseus.exe roadblaster vldp -framefile vldp/roadblaster/roadblaster.txt -fullscreen OR if you prefer sharp bitmapping: hypseus.exe roadblaster vldp -framefile vldp/roadblaster/roadblaster.txt -fullscreen -nolinear_scale Just rename your current rb.m2v and place this one in the same folder (.dat should automatically be recreated, but removing is also fine): 215784 Aug 5 18:02 rb.dat 5103914456 Aug 5 18:00 rb.m2v 33437613 May 1 2016 rb.ogg 705733047 May 1 2016 rb-orig.m2v 808 May 1 2016 'road blaster.txt' 12 Apr 30 2016 roadblaster.txt Before anyone asks, there is no way this resolution will work on an overclocked Raspberry Pi 4. Windows Template for this 4K video: https://mega.nz/folder/t082hTgT#J9NiuIB9bl2pYSbj-jrjnQ

Coolio, looking forward to testing this. We might want to move this discussion to the Hypseus thread, to save cluttering up Karis' Singe 2... ?

I don't know this software (topaz), but this seems to imply you can ask for a framerate change ? https://photorumors.com/2021/07/04/topaz-labs-video-enhance-ai-v-2-3-0-released/ Is this an add-on extension to the main engine ? You can go larger than 1600x1200, but just ensure the aspect ratio is correct (2880x2160). The resulting file size I guess is the biggest factor. I guess you also need to set the aspect ratio, unless it detects it from the size specified. Did you get the sound sorted ?

mediainfo --Inform='Video;%FrameCount%' rb.m2v 53999 mediainfo --Inform='Video;%FrameCount%' rb-orig.m2v 54000 mediainfo --Inform='Video;%Duration%' rb.m2v 1799967 mediainfo --Inform='Video;%Duration%' rb-orig.m2v 1801800 Some slight differences in video timing, not sure what differences these will make in-game yet, they are quite small. Would require testing... Edit: Here is the aspect ratio and timing issue (top yours, bottom original): Display aspect ratio : 16:9 Frame rate : 30.000 FPS Display aspect ratio : 4:3 Frame rate : 29.970 (30000/1001) FPS 2021-08-04 10:03:09.100 INFO [740887] [ldp_vldp::nonblocking_search@470] NOTE: converting FPKS from 29970 to 30000. This may be less accurate

In Windows: https://mediaarea.net/en/MediaInfo/Download/Windows View -> Tree Debug -> Advanced Mode Look for 'Duration' and 'Frame Count' Ok, loaded into Hypseus fine, there is an aspect ratio issue in the video. I got sound immediately. Did you delete the original .dat file and allow Hypseus to re-create ? I assume you didn't move the existing .ogg file? Also try the Windows WinMM version, which uses the legacy Windows Sound System if sound issues persist. 4096 Aug 4 09:14 . 4096 Apr 23 23:58 .. 216004 Aug 4 09:14 rb.dat 5663510228 Aug 4 09:13 rb.m2v 33437613 May 1 2016 rb.ogg 705733047 May 1 2016 rb-orig.m2v 808 May 1 2016 'road blaster.txt' 12 Apr 30 2016 roadblaster.txt Besides the aspect ratio issue, these look great - displayed here at 1600x1200:

You can use ffmpeg to convert to m2v and pull out the audio as ogg: ffmpeg -i <original>.mp4 -an -qscale:v 4 -b:v 6000k -codec:v mpeg2video <game>.m2v ffmpeg -i <original>.mp4 -vn -c:a libvorbis -ar 44100 -map a -b:a 160k <game>.ogg The important thing is the video frame timings are matched to the original: mediainfo --Inform='Video;%FrameCount%' <file> mediainfo --Inform='Video;%Duration%' <file> You can compare the mp4, and the m2v, with something like this.

Or please try the upscaled video in Hypseus Singe (Daphne SDL2) which will support the higher resolution video. Please provide a link to the upscaled video, if you do, for others to try. e.g. Change -x and -y to the resolution you create. hypseus.exe roadblaster vldp -framefile vldp\roadblaster\roadblaster.txt -x 1600 -y 1200 -fullscreen Edit: There is not a 2Gb limit on file size in Hypseus, so there is no need to split the upscaled .m2v if it exceeds that size.

If the video content is identical why would you think that the framefile timings would be different because of aspect ratio or resolution ? If it's different video content, with different frame order or length, then fair enough.....

Absolutely, in exactly the same way as you can create Singe 2 (LUA) games: https://www.lua.org/ The format for Hypseus follows the original format of Singe 1 LUA games, but in reality not very much has changed in the jump to Singe 2 API calls at this point. Singe 2 has advantages in other areas. You can see the conversion LUA of recent Singe 2 games here: https://github.com/DirtBagXon/hypseus_singetwo_data - Altered Carbon in particular. This can be used as a template for anything you would wish to create. Karis and Poiu etc have moved on to Singe 2 these days, but the game coding principles are the same. Of course if you wanted to get hardcore, you could look to adapt some more ROMS within the Daphne element of Hypseus (C++), this is all open source gaming....

Sinden Borders now implemented: Version: 2.6.2 hypseus singe vldp -sinden 5 g -framefile ... -sinden <1-10> <color> [ Enable software border for lightguns ] [ Color: (w)hite, (r)ed, (g)reen, (b)lue or (x) ]

Sinden Borders now implemented: Version: 2.6.2 hypseus singe vldp -sinden 5 g -framefile ... -sinden <1-10> <color> [ Enable software border for lightguns ] [ Color: (w)hite, (r)ed, (g)reen, (b)lue or (x) ]

Unfortunately, it's down to CPU grunt. Even the overclocked Pi4 will struggle at 1080p and high bitrates. Remember these Daphne files are MPEG-2 (m2v) encoded, not H264 (mp4). "Pi0-3 have hardware accelerated decode for H264, MPEG4, H263, and through optional codec licences for MPEG2 and VC1. Pi4 has the same hardware accelerated decode for H264, but not the other codecs." https://www.raspberrypi.org/forums/viewtopic.php?t=268356 You can downsize resolution for your Pi setup with the ffmpeg utility (or others): ffmpeg.exe -i dls33d4.vob.m2v -an -qscale:v 4 -b:v 6000k -vf scale=960:720 -codec:v mpeg2video dls33d4.vob-pi.m2v https://ffmpeg.org/download.html Have a chat with the guys in the RetroPie forum on optimising, but I think the general consensus is 720p.

https://github.com/DirtBagXon/hypseus-singe/blob/master/src/3rdparty/retropie/RETROPIE.md https://retropie.org.uk/forum/post/263036

No problem. There is no frontend for Hypseus, but there is a zip file with batch files in the hypseus repo for the standard games. Beyond that, I assume some familiarity with Daphne and Singe argument altering. Regarding your long boot on Space Ace Enhanced (sae): there is no option in the daphne codebase to enable -fastboot: void ace::patch_roms() { if (m_fastboot) { m_cpumem[0x121b] = 0x00; m_cpumem[0x123a] = 0x00; } } void sae::patch_roms() { bool passed_test = false; // NOW check to make sure the SAE readme file is present and unaltered // Dave Hallock requested this check to make sure sites don't remove his // readme file // and distribute SAE. passed_test = verify_required_file("readme.txt", "sae", 0xCA4E20E6); // if they failed the test then exit hypseus if (!passed_test) { LOGI << "The SAE readme.txt file is missing or altered."; LOGI << "Please get the original file from www.d-l-p.com, thanks."; set_quitflag(); } }

Version 2.5.6 released:

@wemr97dl Not certain if you are referring to Hypseus here or not.... If so, you would use hypinput.ini, using SDL2 keycodes (details in link).

Last of the bunch, and laid to rest (enjoy):

For the Laserdisc/CRT purists, scanlines and blanked searches: Click for hires image: Other examples:

@meekeee For the Pi, you might want to checkout: https://github.com/DirtBagXon/hypseus-singe Use the RetroPie branch: git clone --single-branch --branch RetroPie https://github.com/DirtBagXon/hypseus-singe.git

Some context here ? Using what software and version, we have mentioned three different emulators thus far? What are the the logs and errors saying ? What is the debugging showing as detailed here: http://www.emuline.org/topic/2301-arcade-pc-hypseus-singe-daphnesinge-sdl2-windows-mac-linux/?page=4&tab=comments#comment-103200

Ok, we are on completely different threads here. 1. Singe 2 cannot run Daphne ROM games. 2. This thread is about the new Hypseus Singe (Modern Daphne replacement) 3. The .bat files will only work in Hypseus Singe. The old Daphne will have issues getting anything over the standard resolutions as it was written over 10 years ago. You need to either: Await the HD games you want to be ported to Singe 2. Tackle installing Hypseus Singe, (see links on the first post in this thread), which will handle HD video within Daphne for those that have video available.

Any clues as to why ? In the logfile ?

@Cool Coyote I have thrown together, literally, some bat files. Do you want to give these a try and report back. Get .bat files from GitHub repo: https://github.com/DirtBagXon/hypseus-singe/releases https://mega.nz/file/59VRHYTQ#UO5dbQoO3NpJrIrazORTfdF56b2A7WdqeGPhfdzj9zM Drop them directly in the Hypseus directory with the other files. Note: They rely on the fact that the games are in the vldp_dl, vldp and singe sub-directories from the download.