Update app.py

app.py

@@ -782,13 +782,13 @@ for i, t in tqdm(enumerate(scheduler.timesteps), total=len(scheduler.timesteps))
     im.save(f'steps/{i:04}.jpeg')
 
 # Make and show the progress video (change width to 1024 for full res)
-!ffmpeg -v 1 -y -f image2 -framerate 12 -i steps/%04d.jpeg -c:v libx264 -preset slow -qp 18 -pix_fmt yuv420p out.mp4
-mp4 = open('out.mp4','rb').read()
-data_url = "data:video/mp4;base64," + b64encode(mp4).decode()
-HTML("""
-<video width=600 controls>
-      <source src="%s" type="video/mp4">
-</video>
+#!ffmpeg -v 1 -y -f image2 -framerate 12 -i steps/%04d.jpeg -c:v libx264 -preset slow -qp 18 -pix_fmt yuv420p out.mp4
+#mp4 = open('out.mp4','rb').read()
+#data_url = "data:video/mp4;base64," + b64encode(mp4).decode()
+#HTML("""
+#<video width=600 controls>
+ #     <source src="%s" type="video/mp4">
+#</video>
 """ % data_url)
 
 """The version on the right shows the predicted 'final output' (x0) at each step, and this is what is usually used for progress videos etc. The version on the left is the 'next step'. I found it interesteing to compare the two - watching the progress videos only you'd think drastic changes are happening expecially at early stages, but since the changes made per-step are relatively small the actual process is much more gradual.