Dude... these are all badass! I had to take some time off from playing around on the AI but i am getting back to it. I still haven't posted on it... so i better get to work! hahahhaa Thanks again for all your contributions bro!
You are viewing a single comment's thread from:
Yeah dude, go to work and deliver us something cool! :D
Thanks for your always kind comments, and grab your !PIZZA!
Tomorrow (actually later today since i am way up past my american bedtime) i will post some of my 20+ days worth of content. Thank your for the motivation, inspiration, and encouragement. Hopefully, when AI takes over... it will consider all of us experimental artists as some of it's first and best friends and perhaps it will spare us from the impending SkyNet doom! hahahhaha
Thanks for the....
Haha yeah, better we start to praise SkyNet right now, before is too late!
Cool, I'm eager to see what you deliver "tomorrow" so "my evening" hehe
I'm glad if I'm somehow inspiring hehe thank you!
Get some more !PIZZA!
By the way, I read a comment of you somewhere, and cannot find it anymore lol... so I'll reply here.
It is about, trying to make videos and getting errors. You have mentioned that got a K-80 and were trying to make a 720x480 video, if I'm not wrong. That's impossible, k-80 cannot bear more than 480x480 pixels... so to keep the same aspect ratio you wanted for the video 3:2, you should render it at 480x320 (maybe K80 could bear 540x360px, but I'm not sure), and then upscale it... the good notice, is that as the videos are images in motion, any blur that the upscaling could cause, gonna be far less noticeable than in a static image.
Hey, thanks for the info. I was setting the videos to 640x480 and that may still be too big. Some of the parameters i am not familiar with so it's either operator error from ignorance or the code at times. I am sure it's probably almost always my misunderstandings or bad inputs.
I also ended up taking the day off from internetting yesterday... i was getting digital burnout... so i will work up on the post today a bit. Thanks again my friend. =)
Yeah, sometimes a break is a must, I got a fried one week ago, you wisely warned me about, thanks! Now I enjoy more, and stress less (:
Are you using the video with features notebook? If your problem was that the resolution of the videos was too big, then it dropped a CUDA error. If not, anything else might be related to the prompt. Had to figure that respect the format of the given example is a must, the regular way that we use to prompt in the other notebooks, breaks the code of this particular one.
Take care friend (:
@jotakrevs i just tried to run the video notebook and upon installing the Libraries i got this code...
Downloading CLIP...
Downloading Python AI libraries...
Installing libraries for handling metadata...
Installing Python video creation libraries...
NameError Traceback (most recent call last)
<ipython-input-4-3acbd96b0750> in ()
20 print("Installing Python video creation libraries...")
21 get_ipython().system('pip install imageio-ffmpeg &> /dev/null')
---> 22 path = f'{working_dir}/steps'
23 get_ipython().system('mkdir --parents {path}')
24 print("Installation finished.")
NameError: name 'working_dir' is not defined
I see in step 22 is where the error occurs. Do you have any idea what that error means or how i might go about correcting it?
Yes, you missed create the directory. So at the beginning of the notebook, it offers you use Google Drive to store the images. You can execute that cell. If not, below that cell, there is a text telling you that if you don't want the Google Drive option, you must uncomment the code of the cell below that text, and then execute it.
The working dir/steps will be created in the Colab, and you won't get that error.