Thanks for the info - looking into it now!
sudo_whoami
Creator of
Recent community posts
Hi again Giselle! Just wanted to let you know that the latest version is now up for grabs. I was able to fix the issues you were running into and improve a few other things along the way. Let me know if you’re still having trouble with the Open In App… feature, as I might be able to walk you through troubleshooting on your specific machine.
Hey, sorry for all the replies but could you do one last thing for me? If you don’t mind, could you open a command prompt and enter
echo %ASEPRITE_EXECUTABLE%
and then let me know what it says when you hit Enter? It should print out the path to your Aseprite install (you can just tell me “It worked!” if you don’t want to put the path here for all to see). Thanks again!
Hi again Giselle. I think I’ve addressed most of the issues you’ve mentioned, and maybe one you didn’t! I’m testing the latest extension on my Mac and then I’ll move it over to Windows for further poking. Should have a fresh patch out in a few days once I’ve had time to nail everything down.
Sadly, it seems like the slow response time is due to Lospec being intermittently overloaded. I’ve confirmed this with Skeddles (the guy who runs Lospec), so this is at least an explanation but alas not a fix.
Hi Giselle,
Thanks for your support! Sorry to hear you’re running into some issues.
Could you tell me:
- what OS you’re using
- what version of Aseprite you’re using (and whether it’s the standalone or Steam version)
Just a heads up: If you’re on Windows, you’ll need to have run the extension at least once from inside Aseprite for the “Open In App” feature to work!
And FWIW, I’ve also noticed a slowdown with the URL call in the latest version of Aseprite - thank you for confirming my suspicions. I’ll see what I can do to fix that (if anything) and I’ll dig into the other issues you’ve mentioned.
Hi BrandoIRL, to use the extension you can either click on the menu button above the color palette sidebar and select “Import Palette from Lospec…” -or- click on the “Open in software” link on a palette’s page if you’re on Lospec.com. You can find out more by reading the “Features and Usage” section here.
Hi James, sorry to hear you’re having trouble with the extension. Unfortunately Linux isn’t officially supported because I don’t have a way to reliably test the extension in multiple distros. Typically the “unexpected end of input” error is thrown by Aseprite itself when it runs into an issue parsing JSON.
As for the “invalid palette name”, that’s tricker because the daily palette is parsed directly from here: https://lospec.com/palette-list/current-daily-palette.txt and should (barring an issue with Lospec itself) always be valid.
If you paid for the extension, please let me know so I can see about issuing a refund.
Okay, I’ve tested the extension on both Windows 11 and Mac OS Sequoia using the latest stable version of Aseprite, which at the moment is 1.3.10.1. It’s possible that since v1.3.11 is still in beta (not sure if you’re on -beta1 or -beta2) that not all of the API features have been implemented/are working correctly. For the time being I’d recommend rolling back to the stable version of Aseprite.
I’m afraid the short answer is no, or at the very least “I doubt it”.
The longer answer is: I don’t know what parts of Libresprite’s API are compatible with Aseprite’s API, if any. This extension also relies on Aseprite’s CLI to handle Lospec’s “Open In App” links, so that feature would almost certainly not work in Libresprite.
Hey again,
I just got another reply from user @PhoenixTamer who’s been running into the same issue on Windows and they found out that Avast was preventing the script from executing properly (likely because it relys on curl under the hood, but that’s a guess). I’m not sure if that’s what you’re up against, but it’s possible that your AV is being overzealous.
Thanks for the report. Based on the information from you and @PhoenixTamer, it seems like there’s something up with a file path somewhere when using the Steam version of Aseprite. This should give me a place to start looking.
That said, I don’t currently have a Linux machine (virtual or otherwise) set up for testing, so I can’t 100% guarantee Linux support with this extension, but I’ll do my best!
Thank you, that helps! If it’s every name you try then I can assume it’s not just one palette with a weird JSON issue. I just hav a couple more questions if you don’t mind.
- Are you using the Steam version of Aseprite or the standalone version?
- Have you tried removing and reinstalling the extension? If you do, I’d recommend a fresh download just in case something got corrupted last time!
Hey PhoenixTamer! Can you give me some more info when you get a second?
- What version of Windows are you using?
- What version of Aseprite are you using?
- What’s the name of the palette you tried to import?
- Does it only happen with that name, or is it every time?
That’ll help me narrow down the issue. Thanks for the report!
There's some kind of issue applying this theme to Aseprite 1.2.34.1-arm64 (MacOS 12.3). When I click "Apply", the screen just flashes briefly before going back to the default theme. I doubt this is an issue with your theme specifically, but I wanted to put this out there in case anybody else runs into trouble!