Activity for RECOIL
-
Piotr Fusik posted a comment on ticket #110
I'm making progress. The thumbnail extension feels harder to debug because of caching. File URLs now show the real paths under the Xcode debugger - I don't know what has changed.
-
Ok, thumbnails are working after OS restart. Any hints how to debug? Xcode breakpoints don't work for me while they work for the preview.
-
I found https://github.com/Marginal/QLVideo and I started with my simpler project https://github.com/pfusik/qoi-fu. The preview is working. Now need to do the thumbnails. One problem is that the debugger shows request.fileUrl="file://.file/id=6571367.2787389" and RECOIL relies on file extensions for file format identification, as many formats have no header at all. Can I access the filename extension? An alternative would be to create 565 appexes, one for each format (x2 for preview/thumbs). ;)
-
Matt Sephton posted a comment on ticket #110
i have it in two of my closed source apps. i will see how i can share with you
-
I'm making progress, but the Xcode template doesn't register a file extension and Apple documentation sucks. Is there a single working example? All the projects I could find on GitHub are qlgenerators.
-
I'm making progress, but the Xcode template doesn't register a file extension and Apple documentation sucks. Is there a single working example? All the projects on GitHub I could find are qlgenerators.
-
Piotr Fusik committed [8b9c3b] on Code
[osx] Migrate to a new build machine.
-
No, sorry, I only hve Apple silicon M1
-
Right! App + Thumbnail target + QuickLook Preview target. The code would be Shared and accessed by all.
-
Right! App + Thunbnail target + QuickLook Preview target. The code would be Shared and accessed by all.
-
Right! App + Thunbnail target + QuickLook Preview target. The code wluld be Shared and accessed by all.
-
Right! App + Thunbnail target + QuickLook Preview target.
-
Ok, I think I need to create an App project, then New/Target/Thumbnail Extension. This handles thumbnails, where are previews?
-
Xcode has a template. What do I click in "Choose a template for your new project" in my Xcode 16.4 ? I don't see anything named "Quick Look" or "App Extension".
-
Did you test on Intel?
-
GIMP plugin works fine. I downloaded GIMP, ran it once so it created the support folder, then copied the file-recoil folder into there, making sure to un-gatekeeper the executble (my method is to right-click-open a couple of times until you see it run in a terminal window).
-
GIMP works fine. I downloaded GIMP, ran it once so it created the support folder, then copied the file-recoil folder into there, making sure to un-gatekeeper the executble (my method is to right-click-open a couple of times until you see it run in a terminal window).
-
Thanks for info! Please don't spend too much time debugging this. I expect that once we get the appex, it will be recommended for all the OSes that support it. Can you test GIMP 3? still shows version 6.4.5 in Get Info This part is expected. I haven't bumped the version numbers for the alpha, as I don't even know if it will be 6.5.0 or 7.0.0.
-
Sadly 6.5.0-ALPHA2 (still shows version 6.4.5 in Get Info) doesn't work for me on macOS 14.7.8, M1 MBP. No thumbnails or QuickLook space previews.
-
I'll be more thorough with my testing in future! Thanks the steps above, but no joy. even gatekeeper! I can get RECOIL to work on macOS 12.7.6 (apart for image file extensions claimed by the system, IMG, PL5, PIC, SPX, OBJ, ODF, and more - see attached screenshot) On macOS 14 I do not see either the thumbnails or the space-preview. I do see some errors in Console app, sadly redacted so not very useful. These are all lines from quicklook on DOORS.PC1 info 20:41:28.513459+0100 Finder start loading...
-
Also: do you see RECOIL thumbnails but not the Space-activated preview?
-
I'm still looking for why I can't QuickLook any files with RECOIL through pressing Space bar in Finder. Some ideas: qlmanage -r qlmanage -r cache Reboot https://sourceforge.net/p/recoil/bugs/109/#573a
-
Column of blank pixels down right of QuickLook
-
DOORS.PC1 has one black column on the left and two black columns on the right. PC1 is a simple format which is always 320x200.
-
Column of blank pixels down right of QuickLook
-
I can run both on macOS 14.x, but qlgenerator files were discontinued in 15.0 sorry I was not totally clear about that. Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear that is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limit oldest support to 10.15 (2019) rather than the current 10.6 (2009) Xcode has a template. Compared to .qlgenerator that...
-
I can run both on macOS 14.x, but qlgenerator files were discontinued in 15.0 Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear that is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limit oldest support to 10.15 (2019) rather than the current 10.6 (2009) Xcode has a template. Compared to .qlgenerator that lives alone, .appex lives inside an app,...
-
I can run both on macOS 14.x, but qlgenerator files were discontinued in 15.0 Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear that is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limit oldest support to 10.15 (2019) rather than the current 10.6 (2009) Xcode has a template. Compared to qlgenerator that lives alone, Appex lives inside an app, which...
-
I can run both on macOS 14.x, but qlgenerator were doscontinued in 15.0 Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limit oldest support to 10.15 (2019) rather than the current 10.6 (2009) Xcode has a template. Compared to qlgenerator that lives alone, Appex lives inside an app, which I guess...
-
I can run both on macOS 14.x Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limite oldest support to 10.15 (2019) rather than the current 10.6 (2009) Xcode has a template. Compared to qlgenerator that lives alone, Appex lives inside an app, which I guess could be a simple image viewer that presents...
-
I can run both on macOS 14.x Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limite oldest support to 10.15 (2019) rather than the current 10.6 (2009) Xcode has a template
-
No, I can run both on macOS 14.x Quick Look App Extensions (.appex) were introduced in macOS Catalina (10.15) back in 2019. Just to be clear is not macOS Sequoia 15.0 (2024), which is the current OS soon to be replaced with macOS 26 (2025). Ultimately, by building as appex, you would limite oldest support to 10.15 (2019) rather than the current 10.6 (2009)
-
App wrapper with appex for modern macOS QuickLook support
-
Thanks for bringing this to my attention. I didn't even notice that qlgenerator no longer works on macOS 15. Is there some sample code for the new API? I guess we should ship both, as old macOSes only support qlgenerator?
-
App wrapper with appex for modern macOS QuickLook support
-
I managed to compile for both Apple Silicon and Intel. Now please test on Intel as I only have an M1. It's a GIMP 3.0.4 plugin. https://recoil.sourceforge.net/recoil-6.5.0-ALPHA2-macos.dmg I don't think I can include a link to home folder in a DMG file. This means you need to open it yourself. Finder hides the Library folder by default. Either View / Show View Options / Show Library Folder or Go / Go to folder / /Users/YOU/Library/Application Support/GIMP/3.0/plug-ins Now drag the file-recoil folder...
-
I managed to compile for both Apple Silicon and Intel. Now please test on Intel as I only have an M1. It's a GIMP 3.0.4 plugin. https://recoil.sourceforge.net/recoil-6.5.0-ALPHA2-macos.dmg I don't think I can include a link to home folder in a DMG file. This means you need to open it yourself. Finder hides the Library folder by default. Either View / Show View Options / Show Library Folder or Go / Go to folder / /Users/<you>/Library/Application Support/GIMP/3.0/plug-ins Now drag the file-recoil folder...
-
The GIMP plugin should run from the user plugins folder
-
Piotr Fusik committed [0248a1] on Code
[osx] Build GIMP plugin for x64_64.
-
Piotr Fusik committed [18a1e8] on Code
[android] Disable "Share as PNG" on Android 9 and older.
-
Piotr Fusik committed [d96bc6] on Code
[android] Target Android 16.
-
Piotr Fusik committed [a5e363] on Code
[setup] Fix "Change destination folder" not working with new WiX.
-
Piotr Fusik committed [5dd4b4] on Code
[imagine] Update the SDK.
-
Piotr Fusik committed [64e741] on Code
[osx] "make install-gimp" to home directory.
-
Piotr Fusik committed [1878a1] on Code
[osx] GIMP 3 plugin.
-
Piotr Fusik committed [447e63] on Code
[android] Upgrade the build system.
-
Piotr Fusik committed [2f3a71] on Code
[scr] sf bug #107 256x192 mode 1.
-
Sam Coup posted a comment on ticket #105
Nice. I am also very happy for the linux support, I personally use Linux MX, in my family and friends I install Linux Mint. I also use XnView.
-
I added support for 16000-byte 256x192 mode 1 files. Also 16000-byte mode 0, mode 2 and EGX1 because it was straightforward, but I have no test files and I don't know if these variants are possible? Maybe you could try to contact the ConvImgCPC authors on its Github project? Emailed last week - no response yet.
-
Thanks for confirmation, Josef! The next RECOIL is going to be 7.0.0.
-
Hi, Piotr! after several weeks of usage I can say, all these formats work!!! Many thanks for support! I personally appreciate hires formats and two VRAMs combinations. I wish you a wonderful summer time! Looking forward to RECOIL 6.4.6 :-) Kind regards Josef
-
Hi, Piotr! after several weeks of usage I can say, all these formats work!!! Many thanks for support! I personally appreciate hires formats and two VRAMs combinations. I wish you a wonderful summer time! Kind regards Josef
-
Hi, Piotr! after several weeks of usage I can say, all these fromats work!!! Many thanks for support! I wish you a wonderful summer time! Kind regards Josef
-
Hi, Piotr! after several weeks of usage I can say, all these fromats work!!! Many thanks for support! I wish you a wonderful summer time! Kind regards Josef
-
Incorrect integer linear color scaling
-
Reopening for the new CG116F.MAG file. The problem is that it is recognized as for the PC-88 VA platform, with 5 bits per Red and Blue components and 6 for Green. While the palette in the file has four low-order bits zeroed. The byte that determines the platform is zero.
-
SD Snatcher posted a comment on ticket #109
Nice to hear that GIMP3 will be supported! And shame on Apple for treating developers this way. Then I'll appreciate your beta testing, to avoid the "works on my machine" trap. What version of macOS do you have? Apple silicon or Intel? I'll be glad to help you with the tests. My machine has macOS 13.7.6 running on Intel.
-
Some background news: Recently GIMP 3 appeared, with a new, incompatible plugin system. I've already updated the code, so the upcoming RECOIL 7.0.0 will come with GIMP 3 plugins. However, I have multiple problems with macOS builds: - Our build machine at https://www.macstadium.com had a disk failure and it no longer boots. I'm setting up my local Mac to do the builds. - I bought an Apple Developer subscription, but notarization with it fails with a mystery error code. I opened a support ticket at...
-
Also, it would be nice to add the following command to the install steps of all the RECOIL plugins for macOS, otherwise macOS blocks them from being executed. xattr -dr com.apple.quarantine <path to file or folder>
-
The GIMP plugin should run from the user plugins folder
-
(deleted incorrect comment)
-
Why are overscan files smaller than expected? (e.g. rs2.scr is <24 KB, expected 96*270=26 KB) Apparently, the file rs2.scr was corrupted. Here's another file for the same image that I tested and it loaded correctly on ConvImgCPC.
-
The compressed formats need more work because apparently there are four compression algorithms. While I'm familiar with ZX0, adding all four will take some time. Can you place add support for ZX0 then? This way at least one algorithm would be supported.
-
I confirmed that this problem happens with the MAG (Makichan v2) file format. Here's the exactly same image (*1) stored in the Pi and MAG formats. As you can see, the MAG has incorrect levels. What's even weirder is that recoil expands the Green channel differently than the R and B channels. *1: NFSW image. Handle with discretion.
-
I confirmed that this problem happens with the MAG (Makichan v2) file format. Here's the exactly same image (*1) stored in the Pi and MAG formats. As you can see, the MAG has incorrect levels. What's even weirder is that recoil expands the Green channel differently than the R and B channels. *1: NFSW image. Handle with care.
-
Piotr Fusik committed [1625cd] on Code
[scr] sf bug #107 ConvImgCPC EGX modes.
-
dark_sceptre.scr is smaller than expected (7972 bytes). Perhaps compressed? I attached another version of dark_sceptre.scr that seems to work fine. The other files are 16000 bytes that I asked about. Now I see these are 192 and not 200 lines - I'll handle that. Their resolution is 256x192 instead of 320x200. This is why the file is smaller.
-
dark_sceptre.scr is smaller than expected (7972 bytes). Perhaps compressed? The other files are 16000 bytes that I asked about. Now I see these are 192 and not 200 lines - I'll handle that.
-
dark_sceptre.scr is smaller than expected (7972 bytes). The other files are 16000 bytes that I asked about. This is just the size of the 320x200x4 bpp bitmap, no room for palette or header of any kind. Looking inside, they do have a header with the title in ASCII.
-
Just tested it. The following mode1 images were decoded incorrectly as garbage, with the file type detected as "Electronika MC 0515, 640x200", or just have thrown a "decoding error": casanova2.scr dark_sceptre.scr hudson_hawk.scr panic_dissy.scr toi_acid_game-bis.scr
-
I didn't update the web app yesterday. Updated now.
-
Implemented modes 1 and 2 and both EGX modes. Thanks! I tried to test it on the web version, but sadly the files couldn't load yet.
-
I'm trully sorry, I don't have almost any CPC experience, so I can't answer these questions. Maybe you could try to contact the ConvImgCPC authors on its Github project? https://github.com/DemoniakLudo/ConvImgCpc)
-
Implemented modes 1 and 2 and both EGX modes. Questions: 1. At what offset is the per-line palette in Mode X files? I couldn't figure it out from SauveImage.cs 2. 16000-byte mode 1 files have no room for the palette 3. What are 32 KB files? Alternating frames? 4. Why are overscan files smaller than expected? (e.g. rs2.scr is <24 KB, expected 96*270=26 KB)
-
Piotr Fusik committed [e4f173] on Code
[scr] sf bug #107 ConvImgCPC modes 1 and 2.
-
Piotr Fusik committed [a33a53] on Code
[android] Upgrade the build system.
-
Piotr Fusik committed [33edd2] on Code
[scr] sf bug #107 ConvImgCPC mode 0.
-
I couldn't find any modeX, egx1 and egx2 sample images, so I resorted to some stinky conversions.
-
Here are some mode0 overscan examples.
-
Here are some mode2 examples.
-
Here are some mode2 examples.
-
Here are some more mode1 examples.
-
The single SCR example is regular mode 0 with an embedded palette. Do you have examples for mode 1, mode 2, overscan, EGX modes, "CPC plus"? The compressed formats need more work because apparently there are four compression algorithms. While I'm familiar with ZX0, adding all four will take some time.
-
CPC: Support for ConvImgCPC images
-
The single SCR example is regular mode 0 with an embedded palette. Do you have examples for mode 1, mode 2, overscan, EGX modes, "CPC plus"? The compressed formats need more work because apparently there are four compression algorithm. While I'm familiar with ZX0, adding all four will take some time.
-
CPC: Support for DPS (Dual Picture Viewer) SCR images
-
CPC: Support for ConvImgCPC images
-
Piotr Fusik committed [9dd83d] on Code
[uwp] Update Windows SDK.
-
Piotr Fusik committed [68accb] on Code
[android] Upgrade the build system.
-
Piotr Fusik committed [b4adf6] on Code
[www] Scale images down to fit.
-
Piotr Fusik committed [dcc46a] on Code
[sra] sf bug #106 SRx files with 256 lines.
-
Support for SRx files with 256 lines
-
Implemented, thanks!
-
How to tell 256-line files from files with sprites? SRx files don´t support neither embedded sprites or palette. Only SCx files have them. OTOH, SCx can't support 256 lines, because they use areas of the VRAM above the 212th line to store the sprites and palette. So yes, the extension is the way you differentiate the features between them.
-
How to tell 256-line files from files with sprites? SRx files don´t support neither embedded sprites or palette. Only SCx files have them. OTOH, SCx can't support 256 lines, because they use areas of the VRAM above the 212th line to store the sprites and palette.
-
Ops, sorry! I didn't notice that the image conversion tool I used added this 7 byte header to the palettes. This is incorrect. Please strip it from the PLx files.
-
How to tell 256-line files from files with sprites? SRx files don´t support neither embedded sprites or palette. Only SCx files have them.
-
How to tell 256-line files from files with sprites? SRx files don´t support neither embedded sprites or palettes. Only SCx files have them.
-
Ops, sorry! I didn't notice that the image conversion tool I used added this 7 byte header to the palettes. This is incorrect. Please strip it from the files.