Does this extension work with Windows 11? I don't exactly know if that'd change anything but nothing about the extension seems to be working. It just gives the same error of "curl error: could not close connection" I've been trying everything I've seen such as going over that convo w/ giselle, reinstalling the extension, and reopening aseprite.
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.
Hi there, thank you so much for this tool, it's great!
However i seem to be having some issues:
Not a big deal but worth noting that the "Import Pallete from Lospec" option and importing palettes takes around 5 seconds to load every time
The "Open in App" feature doesn't seem to work, when i click a lospec-palette link the cmd screen pops up for a split second but nothing happens, typing the pallete id manually or using the daily/random options works fine
The "Save as preset" option doesn't do anything
Both other options work fine but the "Save and use now" option displays an odd console log that just says ".gpl"
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.
I'm on Windows 10 and using the latest Steam version (v1.3.10 i believe), also i have run the extension and imported a few palettes and made sure to restart aseprite (and my pc just to be sure) but the Open In App feature still seems to not do anything.
Thank you for the quick response, keep up the great work!
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.
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.
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!
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
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.
Hello, the new version works great and addressed most issues, however the Open in App handler is still not working and "echo %ASEPRITE_EXECUTABLE%" still doesn't show the path to the .exe
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…
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.
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.
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.
I keep getting messages saying "An error occurs when registering the lospec.com URL handler" and “lua:122:curlerror - could not close connection” when trying to get a palette. Is there anything I can do to fix it?
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.
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.
No problem, it's very useful and I've already used it quite a few times even though I just downloaded it today. And the ability to just get random or daily palettes as well is going to be very helpful for me and I can see myself using it very often
Error: /home/$USER/.config/aseprite/extensions/losepec-palette-importer/./lospec-palette-importer.lua:191: unexpected end of input
on the Steam version on Linux (Manjaro). I launched the programme from the command line directly from /home/$USER/.local/share/Steam/steamapps/common/Aseprite so I could see logs and potentially debug it a little more but when launching it this way instead of through Steam the script ran fine.
Might be helpful as a workaround to anyone who needs it or the developer for figuring out what the problem is.
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!
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.
I was going to try and debug it a bit more today but today it has decided to work fine when launched through Steam too, so I have no idea what was happening.
Weird, but okay! Keep me posted if you run into anything else, and feel free to submit an issue to the GitHub repo if you hit any other snags. Thanks for keeping me in the loop.
The extension is developed on Aseprite 1.3.5 and is working on Mac OS Sonoma and Windows 11. I don’t have a Windows 10 machine to test on, but if you’re seeing an error message please post it here.
Hey, I'm running into an error and don't really know why. Just installed and did everything as the page says. This happens after I click ok on the initial import window that pops up.
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!
This seems like a path-related issue with the Steam version of Aseprite. Mind if I ask where your Aseprite executable is located? @Merrow’s Cowl is running into the same issue on Linux, so this is helping me narrow it down further.
Hmm…it could be that the extension is running into an issue writing to /tmp, which it needs to do in order to collect the output from curl. I’ll try to get a Linux test done this week to see if I can figure out what’s going on. Sorry you’re running into trouble!
← Return to Aseprite extension
Comments
Log in with itch.io to leave a comment.
Does this extension work with Windows 11? I don't exactly know if that'd change anything but nothing about the extension seems to be working. It just gives the same error of "curl error: could not close connection" I've been trying everything I've seen such as going over that convo w/ giselle, reinstalling the extension, and reopening aseprite.
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.
Which version of Aseprite are you using?
Thanks for the response! I'm currently using the 1.3.13 version of Aseprite on Steam.
Thanks for the info - looking into it now!
Hi there, thank you so much for this tool, it's great!
However i seem to be having some issues:
Hi Giselle,
Thanks for your support! Sorry to hear you’re running into some issues.
Could you tell me:
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.
I'm on Windows 10 and using the latest Steam version (v1.3.10 i believe), also i have run the extension and imported a few palettes and made sure to restart aseprite (and my pc just to be sure) but the Open In App feature still seems to not do anything.
Thank you for the quick response, keep up the great work!
Thanks for the info! I already tracked down a rogue
printstatement 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.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.
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!
Hmm, that may be the issue, it just prints %ASEPRITE_EXECUTABLE%
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
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.
Hello, the new version works great and addressed most issues, however the Open in App handler is still not working and "echo %ASEPRITE_EXECUTABLE%" still doesn't show the path to the .exe
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…
The variable seems to have changed when i check with echo but the Open in App still does nothing
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.
I downloaded, and installed in aesprite but how do I actually run the program?
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 just installed v1.3.1. Using latest Aseprite version (v1.3.10.1) via Steam + Arch Linux.
When trying Random Palette, I’m getting:
../lospec-palette-importer.lua:278: unexpected end of inputerrors.When trying Daily Palette, I’m getting:
Invalid Palette Nameerrors.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.
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
curlunder the hood to interact with Lospec’s API, so there’s a chance that’s being blocked by overzealous AV…worth a shot, anyway.I keep getting messages saying "An error occurs when registering the lospec.com URL handler" and “lua:122:curlerror - could not close connection” when trying to get a palette. Is there anything I can do to fix it?
I use window 10 and version 1.3.11 of aseprite
Hey there! I’ll look into it!
curlis 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.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.
Thank you! I will try again with an older version
Awesome work! Thanks!
Thank you for your support!
Please tell me this works for libresprite
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.
Never mind, I just got Aseprite lol. Getting the extension now
Thanks for your support!
No problem, it's very useful and I've already used it quite a few times even though I just downloaded it today. And the ability to just get random or daily palettes as well is going to be very helpful for me and I can see myself using it very often
I was getting the error
Error: /home/$USER/.config/aseprite/extensions/losepec-palette-importer/./lospec-palette-importer.lua:191: unexpected end of inputon the Steam version on Linux (Manjaro). I launched the programme from the command line directly from
/home/$USER/.local/share/Steam/steamapps/common/Asepriteso I could see logs and potentially debug it a little more but when launching it this way instead of through Steam the script ran fine.Might be helpful as a workaround to anyone who needs it or the developer for figuring out what the problem is.
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!
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.
I was going to try and debug it a bit more today but today it has decided to work fine when launched through Steam too, so I have no idea what was happening.
Weird, but okay! Keep me posted if you run into anything else, and feel free to submit an issue to the GitHub repo if you hit any other snags. Thanks for keeping me in the loop.
question, how can i change the directory where the palettes should be saved? i have aseprite in drive D:
There’s a button for that on the Palette Preview window. Set the path you want and the extension will remember it.
thank
Funciona no windows 10, e no aseprite 1.3.5?
The extension is developed on Aseprite 1.3.5 and is working on Mac OS Sonoma and Windows 11. I don’t have a Windows 10 machine to test on, but if you’re seeing an error message please post it here.
Hey PhoenixTamer! Can you give me some more info when you get a second?
That’ll help me narrow down the issue. Thanks for the report!
Hi sudo, yeah I can
I can take a screen cap of the order of things if needed also?
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.
I'm using the steam version.
Fresh install results in the same issue even with fresh download as of writing.
Thanks for looking into this!
This seems like a path-related issue with the Steam version of Aseprite. Mind if I ask where your Aseprite executable is located? @Merrow’s Cowl is running into the same issue on Linux, so this is helping me narrow it down further.
Hmm…it could be that the extension is running into an issue writing to /tmp, which it needs to do in order to collect the output from curl. I’ll try to get a Linux test done this week to see if I can figure out what’s going on. Sorry you’re running into trouble!
Thanks for the quick response mate! If it helps I am using Ubuntu 22.04 LTS and PopOs, good luck with the tests!
Epic
Thanks! Much appreciated
Thumbs up