Glad to hear it! Some Linux users have reported that the extension trying to use curl is broken for them - I haven’t nailed down a good fix, and my Linux setup is just a separate partition on this MacBook, so it’s maybe not 100%.
The palette name (as provided by the user) is “sluggified” using a lua port of Skeddles’ own “sluggify” that he uses for Lospec proper, but (as far as I remember) the raw name is used for saved palette files - I’ll look into sanitization for those too.
FWIW, I tried a different r/place palette and encountered the same issue, so I think you’re right on about the slash being the issue:
And I didn’t have any issue saving “|||| 22 PALETTE” on MacOS, so I’ll chalk that up to platform-specific shenanigans.
What I might do is fall back to saving the palette using its slug if using the actual name fails (and if that fails, something else is up).
I’m glad you’re enjoying the extension! I’ve been looking into getting things working under Linux, but it’s still a ways off. It’s not a super high priority, but it is on my radar!
Do you mean you want to be able to select colors that aren’t on your current palette? You can do that already - just select “RGB” (or “HSL” or “HSV”) from the top button bar in the color picker instead of “Index”.
This is the place to post general comments about the extension - off-topic posts will be removed. Bug reports / support requests, and feature requests should be posted in their respective topics.
This is the place to post feature requests and suggestions for how to improve the extension. Bug reports, support requests, or general discussion / comments should be posted in their respective topics.
I can’t promise I’ll implement any given request, but I’m open to ideas!
This is the place to post bug reports or requests for technical support. Feature requests or general discussion / comments should be posted in their respective topics.
Some lag when fetching a palette from Lospec is to be expected, but I can’t think of a technical reason why the extension would take any significant amount of time to start up. I’ll take a look and see if there’s anything weird going on on my end under Windows…
Hi there! Are you pasting the entire URL? If so, that’s the issue - you only need the palette name or its “slug” (the bit of the URL after “palette-list/”), e.g. “reverie38”. And I’ve found on occasion that closing and re-opening your web browser is necessary for the open-in-app handler to take effect.
Glad to hear things are moving in the right direction! The issue you’re describing with the URI handler is a known issue that’s been affecting some Windows users. For now, if you haven’t already, try closing and reopening your browser. I’ll do a bit more digging tonight when I have the time.
Do you happen to remember if you ran the extension in Aseprite before or after tying the “Open in App…” link? I ask because the URI handler relies on a value that gets set by the extension when you run it in Aseprite, so you’ll need to do that at least once first.
Hey there, sorry to hear you’re running into some issues! For now I suggest uninstalling and reinstalling the extension, and I’ll do some digging as soon as I have a moment.
Once you’ve reinstalled, close and open your browser. I’ve noticed that sometimes that can fix the issue with the Lospec URI handler. That window should say “Open in Aseprite” or something like that - the fact that it doesn’t means the handler for lospec-palette:// links isn’t quite registered right (or your browser just hasn’t picked up on it yet).
Also, to ask the software engineer’s favorite question: have you tried rebooting?
It should work on Windows 11. I remember an older post where another user was running into that message from curl and I believe they found it was their antivirus software.
Lovely. Windows environment variables are a pain ~_~ thank you for bearing with me. Have you tried uninstalling and reinstalling the extension? I’ll try that on my PC tonight to make sure it gets completely reset.
Can you try setting the environment variable manually by running: setx ASEPRITE_EXECUTABLE “<path to wherever Aseprite is on your PC>”? I’ve noticed some inconsistency lately with how env vars are behaving in Windows…
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.
Hmm, okay. That would explain why the open-in-app handler isn’t working. That variable is how Windows knows where your Aseprite executable is. Thanks for the info
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.
Thanks for the info! I already tracked down a rogue print statement which explains the message you’re seeing (it might also be related to the issues saving palettes - TBD!). I’m digging into the other issues right now - I hope to have a patch put together and tested in the next few days.
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.
I’ve just re-read through some of the older comments from Steam/Linux users and one thing you might check is your antivirus. The extension uses curl under the hood to interact with Lospec’s API, so there’s a chance that’s being blocked by overzealous AV…worth a shot, anyway.
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.
Hey there! I’ll look into it! curl is the command used to make the URL request to Lospec’s API, so it’s possible something changed on their end. I’ll make sure it’s still working on my Mac, too.
