LilyStilson / AErender-Launcher

GUI for Adobe After Effects aerender console interface with various features
http://aerenderlauncher.com
MIT License
52 stars 3 forks source link

[Bug] Launcher Path panel in AE 2021 does not close after pressing OK #12

Closed DanieleRia closed 3 years ago

DanieleRia commented 3 years ago

What happened? In After Effect 2021 (CC 18), the panel where you feed the exe file does not close after pressing OK.

To Reproduce 1) From After Effects, open AErenderer Launcher Script 2) Press the Settings tab 3) Press the "..." button 4) navigate to the file called "AErender Launcher BETA.exe" and 5) Press OK - but nothing happens

...

  1. Error Appears Every time

Expected behavior When I feed the exe file, the file should be accepted

Screenshots If applicable, add screenshots to help explain your problem.

Required information: Software

Hardware

Additional context The panel works well in AE 2020

LilyStilson commented 3 years ago

Have you enabled Allow Scripts to Write Files and Access Network in After Effects' settings? https://github.com/LilyStilson/AErender-Launcher-Script/blob/master/README.md

If it's enabled, then can I ask you to provide me some more details in AErender Launcher's Discord server?

Also, this is an issue with AErender Launcher Script, not with AErender Launcher and it should been reported in a specific repository.

DanieleRia commented 3 years ago

Hello Alice

Firstly, let me say I love this little tool, I am experimenting a lot, but i found it very promising

Please accept my apologies, I was under the impression the preferences were inherited from my previous versions of AE, but in this case, Allow Scripts to Write Files and Access Network was not on - and turning it on made the trick!

Far from telling you how to do your job, I would like to suggest adding this check in your script: app.preferences.getPrefAsLong("Main Pref Section", "Pref_SCRIPTING_FILE_NETWORK_SECURITY") I am a developer myself (this is my page on aescripts.com https://aescripts.com/authors/a-b/braindot-design/) and I found that this check saves me a lot of Support Tickets

While we are here, I would like to flash one more thing: the "Help" section is actually not displaying on my machine - any suggestions?

And finally, I have installed ffmpeg inside the AErender Launcher directory

[image: image.png] [image: image.png]

Any more info about using AErendered Launcher with FFMPEG would be very much appreciated

Many thanks for your hard work with this tool

Best regards Dani

On Mon, 21 Jun 2021 at 16:45, Alice @.***> wrote:

Have you enabled Allow Scripts to Write Files and Access Network in After Effects' settings?

https://github.com/LilyStilson/AErender-Launcher-Script/blob/master/README.md

If it's enabled, then can I ask you to provide me some more details in AErender Launcher's Discord server https://discord.gg/Bh2MkxG?

Also, this is an issue with AErender Launcher Script, not with AErender Launcher and it should been reported in a specific repository https://github.com/LilyStilson/AErender-Launcher-Script.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LilyStilson/AErender-Launcher/issues/12#issuecomment-865141810, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHWVKJNPYYRQORUX5XSCMI3TT5NBZANCNFSM47B2MJTA .

-- Daniele Ria (He/Him) Motion Graphic, UX Designer Third-Party Developer (Adobe) M. (+44) 797 229 3604 danieleria.com https://www.danieleria.com/

LilyStilson commented 3 years ago

Thanks for the suggestion, I will definitely add this to Script :)

Help section not working currently due to the fact that I haven't written any of it yet and after the future Launcher's version v0.9.0-beta, the workflow will significantly change and the previous help files would be obsolete, so now I'm working on this update, after which I will dedicate all my time to make a proper documentation.

About FFMPEG... Launcher can only detect if there is a folder with name that contains "ffmpeg" and checks if in /ffmpeg/bin exists any FFMPEG executables. But that's it, currently I just postponed all the FFMPEG implementation until v0.9.0-beta. Only FFMPEG detection is working currently. I know it's a bit confusing, but that's gonna be changed soon :)

PS. Your pictures are broken