Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- _vk June 2014
- ATC243750496 June 2014
- Chrisir June 2014
- PhiLho March 2014
Answers
Well, if I understood correctly, yes, that's the way Processing makes movies now: save all the images to disk, then use the built-in tool (or an external tool) to make a movie out of the frames.
To save to another folder, just put the full path in the saveFrame() parameter.
is there another way save too much image seems messy .......
This is a very common way of dealing with video by professionals. Known as "image sequence". Think the folder containing the frames as your "movie" file. : ) After making a self contained movie out of this, the folder can be deleted.
It's ok, you need 20.000 or more images