Hey there! Thanks for providing help for this issue!
I’ll try to patch up the script copying sometime soon, but thanks a ton for providing your solution already :)
Unfortunately, v1.x is busted. It failed to work on pretty much all devices I tested it on excluding my own computer.
v2.0 should fix this, as it works based on a much more robust and safe method (Lua scripting).
Yup.
I had the idea a few months ago, but due to me working on another project, I kept postponing working on this extension. I did eventually add this on v2.0 though. Thanks for the suggestion!
Yeah. v1.x had a recurring issue of simply not working on multiple devices. I doubt this was related to the Aseprite version, instead I think it’s related to how it used memory peeking on other applications (which is considered unsafe and might’ve been blocked by the OS or anti-virus – with very good reason I might add).
Aseprite Audio Extension has only consistently worked on my machine (running on Intel). v2.0 should fix any issues since it changes the way that the values are accessed (it now uses a Lua script).
Hi there! Thanks for the idea!
I’ve been trying to make the extension more user-friendly and I’m pretty confident that v2.0 solves this!
I’m not exactly sure if displaying a preview of the audio is possible exactly according to the reference, but other ways of displaying it might be possible. Might look into this in the future, thanks! :)
Hi there!
Thanks for bringing this to my attention!
Turns out I’ve had the “Default First Frame” option set to 0 for so long I just didn’t know it was 1 by default.
I’ll push out an update that prevents it from saying frame 0, thanks again :)
