-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error message after .png generation #53
Comments
Hey, I'm quite sure that this is relate to space in directory path. Sadly
this is bug in library I'm using and can't be fixed today :(
Please try to generate in different directory
pon., 27 mar 2023, 16:54 użytkownik fpvandi ***@***.***>
napisał:
… Hello together,
when i try to render my videos from the internal hard drive i get an error
message that there are no .png available. When I then go into the
AvatarGxxxx_generated folder it is actually empty. As soon as the video
files and the .srt and .osd files are on another drive (e.g. external SSD
or microSd card) I can render the videos normally.
Is this error known or is it just me?
[image: image]
<https://user-images.githubusercontent.com/129083871/227978057-9c2b8fef-598b-4710-90da-53b47a2c3dc9.png>
—
Reply to this email directly, view it on GitHub
<#53>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOKQC7QE7OLK6NPMYY2HIDW6GS35ANCNFSM6AAAAAAWJIDA3I>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks for the quick response. |
Duplicate of #23 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello together,
when i try to render my videos from the internal hard drive i get an error message that there are no .png available. When I then go into the AvatarGxxxx_generated folder it is actually empty. As soon as the video files and the .srt and .osd files are on another drive (e.g. external SSD or microSd card) I can render the videos normally.
Is this error known or is it just me?
The text was updated successfully, but these errors were encountered: