I've run the movie.frame example and tapped through frames of the station.mov file. No problem.
I've run the same code but switching to an avi file type. It doesn't generate errors, but it doesn't run properly either. My screen seems to run at 59 fps .. could that be a source of error?
The .avi file is one generated on my pc. The first attempt was using 640x480 at capture (with some zoom enabled), but I've reduced the capture size to 320*240 (and no zoom) to match the example, but still disordered presentation on screen.
First of all, my problem probably is understanding the general jargon and 'how-to' of video & capture. That's not conductive for understanding the somewhat scant info available. Any good source on general information would be appreciated.
The misrepresentation on the screen is the printing of the frame-number .. it's not correct, it may make large jumps or not change all together. Looking at the images themselves it often seems as if the frames changes, but once in a while backward ..
I've tested in both processing 1.5 and 2.0 .. the misrepresentations are somewhat similar.
I've been rigging up for a project that involves processing video-frames .. and I'm looking for the /SaveVideo()/ and get to realize, that it may not be possible. Is that true, or am I just disoriented?
A lot of you have tried to construct a sphere by iterating through longitudes and latitudes and tessellate from that. It produces a sphere ok, but sometimes it has annoying shortcomings. One of them is the unequal size of the triangles generated. So, I'm looking at constructing the sphere from equal size triangles. From my flat pencil-sketch, it looks as it is possible by starting out with eight six-sided symmetric polygons. That would be very convenient, becourse the polygons easily are split into equal size triangles .. and they again can be split if need be for further detail.
I work on an Asus Notebook 64bit with Win7. I just downloaded Apple Quicktime for Windows to try out the video example "GettingStartedCapture". I've got an onboard video-device running and executed the example. .. It sounds as an impossible concoction, and, yes, it doesn't work.
Has anyone got a suggestion as how to get 'some' video to work. Are other libraries robust enough for my mix? I downloaded and installed quicktime particularly for this example.
I've been looking around in 'Learning' and libraries but haven't been everywhere. Is there a usable library for 3D modelling? I think of ie functions that takes two volumes/solids as parameters and returns the intersection between the two?
Alternatively .. would any of you be interested in colaborating on building such a library?
I've recently worked a lot with Arduino-scetches, but seem to have come to a point where the scetch programming doesn't seem enough. I was looking for windows MovieMaker on my win7 pc, and found only references in a PROCESSING archive. I've forgot all about the PROCESSING files that I've got lying on my drive. I thought that I would give it a try if it would 'work' right there (like the arduino) .. without any installation and after having reinstalled my win7 a couple of times.
And it did!
The 3d rgb-cube example didn't hesitate a second.
When I think of how much trouble I have had to go through to get the 3D things working in visual-studio, in particular installing the code-editor, then the ready availabillity of PROCESSING is no shorter than a miracle! Cudos to those behind!
That said ..
Ofcourse I have all my trouble with the code, and I've probably clodded my question with a wrong header :
I went to the gettingStartedCapture example and tried it out. The error-message worries me: It complains about the fact that I havn't got QuickTime installed. .. ofcourse I havn't .. this is an 'ordinary' computer, not a MAC.
I may be a bit quick on popping questions in this regard since I haven't taken my time to look for manuals/educational pages and such .. but feel free to comment with whatever.
I look forward to move my future 2D & 3D work to PROCESSING .. and graphic user-forms. What a treat PROCESSING is.