I suppose that we will see the MJpeg Bayer solution first?


Thanks

Wayne.

I have one.

I have one.
That was what I initially did myself.



hehe I thought you did :)

I have one.
Here is the web page code (the application source is in the same directory) - it is not too helpful w/o the actual hardware.

http://elphel.cvs.sourceforge.net/elphel/camera323/apps/ccd/lensraw.html?view=markup


Thanks! - still good to have a look at the code - gives me an idea of what I can do and not.


I have one.
The electrical part of the lens interface is rather simple so you could add it yourself if we'll not have the board you need (at least in near future).

Just so I get this right...IF there is room for the circuitry on the 353, there will be a connector on the board where I can solder wires for the lens connector in my EF extension ring? (Im thinking of using an EF extension ring - attach it to the EF <> CS adapter and then solder wires to the connector inside the extension ring - not the cheapest solution but it means no mechanical work, just some soldering...Ill just have to check so the gglass doesent come too far away from the lens when doing this)

If there is no room for the circuitry on the 353...I could then buy the 10347 board (timing control for KAI sensors right?) and that board will have the connector needed?

..the lens control isn't crucial to me - if we have WiFi support and direct to harddrive write of bayer "raw to grayscale" jpegs I will be happy as happy can be ;) ..but it would be really really cool if we could get the lens control to work as well!!

I read some info about the lens interface on the Birger site and it seems it would not be too hard to create an USB or serial interface...but I would very much prefer to build something that avoids circuitry and is integrated with your solution...that way the work I do can easily be copied and used by others! (not only hardware wise but gui, software etc)

thanks

//O.

In the spirit of the phone thing.

http://www.engadget.com/2007/02/13/meizu-m8-minione-closer-to-production-litigation/
http://www.meizume.com/showthread.php?t=888

Yes, that is 720*480 LCD resolution. I don't know how linux goes on these things.

Here are a few others, I view them as potential micro-controllers with displays and buttons, but an network to USB adapter is needed for most.
http://www.gp2x.com/

http://en.wikipedia.org/wiki/XGP

Others:

http://www.linuxdevices.com/news/NS2986976174.html
http://www.slashgear.com/fic-linux-cellphone-can-it-capture-the-imagination-of-the-open-source-community-072392.php
http://72.14.253.104/search?q=cache:i7aIe-OnVi8J:www.openmoko.com/+http://www.openmoko.com/&hl=en&ct=clnk&cd=1&client=opera

www.neonode.com

Cute, interesting features, also other FIC ones interesting:
http://www.linuxdevices.com/news/NS5201088922.html

http://forum2.mobile-review.com//showthread.php?t=56240

http://www.vr-zone.com/?i=4548

And the list of choices goes on, as long as they are cheaper then an UMPC.

Just so I get this right...IF there is room for the circuitry on the 353, there will be a connector on the board where I can solder wires for the lens connector in my EF extension ring? (Im thinking of using an EF extension ring - attach it to the EF <> CS adapter and then solder wires to the connector inside the extension ring - not the cheapest solution but it means no mechanical work, just some soldering...Ill just have to check so the gglass doesent come too far away from the lens when doing this)
If there is no room for the circuitry on the 353...I could then buy the 10347 board (timing control for KAI sensors right?) and that board will have the connector needed?

Odd,

There is no room on the 10353 itself - it is stuffed as dense as I could. It does have connectors to the extension board but those connectors are really difficult to solder wires too ( http://www.hirose.co.jp/cataloge_hp/e53700036.pdf ). So we will probably make some universal boards for simple extensions that will have these connectors soldered.
10347 will not really work - it is a part of the CCD control and connects as other sensor boards (so instead of 5MPix CMOS board)

Ah - I see - that PDF made it all clear.

Well...I'm just happy to hear about the extension board!

This is what I really like about this open solution - the _luxury_ of being able to ask you things and to be able to add-on to the design later on - even after buying the base design. Add to that the ability to design my own gui...in such a simple way as editing flash & html. Brilliant!

Please correct me if I'm wrong - this connector will be on the 353...and once there is an extension board available, I can open my camera, add the board, solder some wires to the extension ring in my adapter...and then add the features in my GUI.

Voila! EF lens control!

I know there is a lot of pitfalls and things that might not work...but in theory? :)

To be quite honest - when I saw birger.com's 1.000USD pricetag on their EF lens control...I thought controlling EF lenses would be totally out of reach. Glad to be wrong!

Thanks

//O.

Well...I'm just happy to hear about the extension board!


We did start working on such simple board that would allow fast prototyping.

This is what I really like about this open solution - the _luxury_ of being able to ask you things and to be able to add-on to the design later on - even after buying the base design. Add to that the ability to design my own gui...in such a simple way as editing flash & html. Brilliant!


Thanks for the nice words. And - there will be php too.



Please correct me if I'm wrong - this connector will be on the 353...and once there is an extension board available, I can open my camera, add the board, solder some wires to the extension ring in my adapter...and then add the features in my GUI.

Voila! EF lens control!

I know there is a lot of pitfalls and things that might not work...but in theory? :)


Yes, that is correct.


1.000USD pricetag on their EF lens control...I thought controlling EF lenses would be totally out of reach. Glad to be wrong!

Electrically interface is simple. I believe the problem is that original manufacturer did not publish it - so even other lens manufacturers had to reverse-engineer it. Then - the first ones were modifying their cameras (probably by reverse-engineering those ones that were built by revers-engineering theirs...) to make those built by others lenses useless with the new cameras, etc. I believe it is rather stupid game and a waste of human creative work.

We did start working on such simple board that would allow fast prototyping.

If you decide to complete it - please let me know!
I would very much like to betatest and be apart of the development.


revers-engineering theirs...) to make those built by others lenses useless with the new cameras, etc. I believe it is rather stupid game and a waste of human creative work.

I agree totally.
On that note - I even believe that the patent system that was created to support inventors and engineers...is now obsolete in many ways. These days it's pretty much just a big idea stealing engine for big corporations with cross licencing schemes and entire departments with patent lawyers. This is something that really kills innovation. (its proven that most innovation happen in small companies...so no surprise the patent system has been hijacked by big corporations) ..but all that is another long discussion ;)

Long live open source! :)

..regarding EOS lens spec - did you try to just email Canon and ask for the communication spec's? Sometimes what was impossible before - can change. An example of that is the Nikon consumer camera communication specs.

Everybody reverse engineered it because it wasn't available. A few years ago I decided to have a go at it (I was developing a control software for timelapse photography) I asked Nikon for the specs. Well surprise surprise - they asked me to sign a simple NDA regarding the specs and then handed me the complete dev info on CD's - at no cost. So things can change.

I look forward to more news about the 353 - until then - Ill be as patient as can be! :)

//O.

Others:
And the list of choices goes on, as long as they are cheaper then an UMPC.

A lot of interesting links Wayne!

ooh I really like the Meizu M8! :) - looks the way my fat little windows mobile SHOULD have looked...(my screen 20% smaller and the device 100% fatter ;)

However - the concept of using an "existing" device like a wifi phone as a camera gui makes a lot of sense I think. First off I get it cheap when I sign up for a contract with my phone company...and secondly its got loads of battery time. Beats any laptop. Plus - portable as portable can be.

That means instead of getting a laptop - we can spend more cash on the important part - the camera.

//O.

I just put an bid on an neonode N1 today (they show N1m, so it is a bit confusing) but I want micro phone until I can get smoothing more suitable to replace this Palm TungstenW (Beautiful, but keeps turning itself on and even making calls :( ).

I have found lots of really interesting, cheap, Korean phones QVGA and pen based) including the one that looks like an PSP). The neonode N2 (77 x 47 x 14.7 mm, 70 g) the M8, and the Apple Iphone are some of my favorites at the moment (the Iphone might drop drastically before it is released). Nokia is coming out with game compatible phones, including a more game oriented model rumor. They also have an update of their keyboard phones (9500, 9300/1 series) and tablet phones but they are likely to be way over the top in price.

I forgot to mention, the cheapest Palm is also a possible target (USB network adaptor providing). Palm is said to be releasing a third category device next week.

Most of these functions could be done in camera by an button interface, and an display output from the preprocessing section.

I would stay away from the N1 if I where you...
..it looks really good - but the screen is very small and from what I hear it is very buggy. (a friend of a friend has it)

just thought I would give you the heads up ;)

//O.

..regarding EOS lens spec - did you try to just email Canon and ask for the communication spec's? Sometimes what was impossible before - can change.


No, I just googled the matter


Well surprise surprise - they asked me to sign a simple NDA regarding the specs and then ...

That is not an option for us - we would not be able to keep our circuit diagrams and code open

Andrey, check out the attached JPG of the chart I made.

I have researched most of micron, cypress, kodak, zoran, and other sensors. I am also a filmmaker and Visual Effects artist. This sensor is perfect for cinema quality.

Kai 4021 Highlights:
- Large 21.5mm imager size (filmmakers will love this, great DOF)
- 60 DB Dynamic Range
- No Rolling Shutter (important!)
- 24 FPS using FULL sensor width (16:9 Aspect Ratio)

the KAI-2093, KAI-2020, and KAI-1010 are also fairly large sensors with good image quality.

I don't know which of these sensors is cheapest, but I'm guessing they are a bit more than the Microns.

Solomon,

It is probably possible to build a sensor front end for this sensor to work with 10347 board (instead of 10342 or 10344), but the ADC is slower - we can run only 25Mpix/sec for each channel (there are 2 channels/CCD outputs), not 40

Solomon,

It is probably possible to build a sensor front end for this sensor to work with 10347 board (instead of 10342 or 10344), but the ADC is slower - we can run only 25Mpix/sec for each channel (there are 2 channels/CCD outputs), not 40

At 25Mpix/sec per channel, that would reduce the framerate to 15fps.

In that case, you can drop some more vertical lines and get Cinema Aspect Ratio of 2.35:1. You could also do 16:9 at 1280 x 720 resolution.

The KAI-1011 has 20Mhz channel output at 30 FPS. That could work with your ADC hardware at full speed. The chip is also fairly large (9.1mm x 9.1mm) so DOF would be good with 2/3 lenses. (it's also probably cheaper than the KAI-2093)

just some thoughts.

No, I just googled the matter


ah...well..too bad.
sorry for wasting your time.


That is not an option for us - we would not be able to keep our circuit diagrams and code open

But of course!
..the reason I could accept it at the time was that I was only putting together a quick hack for an animation I did. obviously wouldn't work in an open source situation.

I was more thinking along the lines of it being so old and reverse engineered that they might had finally released it in the wild.

Obviously not. :(

Lets hope there is info enough out there to make it work anyways. time, effort and experimenting can do wonders.

//O.

Solomon,

It will be possible to increase the frequency in some next generation sensor board (that will still work in 353 camera) - just in 10347 we targeted lower frequency.

I do not know the price of those sensors, but large CCDs are (naturally) expensive. 11MPix ones we use are about 100x compared to Micron CMOS ones.

Andrey

Lets hope there is info enough out there to make it work anyways. time, effort and experimenting can do wonders.
I hope that with our hardware and (even rather basic) software more people will be able to play with different lenses and post results.

Spoiled by FOSS I feel really bad when I have to reverse-engineer (stupid waste of time) but it can be a fun game that I enjoyed myself many years ago - I was behind the Iron Curtain at the time :-)

I would stay away from the N1 if I where you...
..it looks really good - but the screen is very small and from what I hear it is very buggy. (a friend of a friend has it)

just thought I would give you the heads up ;)

//O.

Thanks for the heads up. Yeah, but I cannot get N1m model in this country, but at the price they are going at, it looks like an good buy. Besides I want the very small pocket feel (my previous monster Nokia phone is not good for tropical pockets because of weight ;)). The N2 is smaller again, screen around the same, would be fun if I could film HD with it, but doubt it. The mob selling it shows the N1m, but says it is N1, that is why I am not putting more money into it, an N1m is definitely worth more to me. I have found an smaller PDA phone again then the N1, it is around $76US. Definitely in the cute play thing category, but I wonder if they are using the same chipset as the N1, but different software, hardware setup.

If the right phone came along with HD video, I would be interested in seeing how my alternative 9Mb/s codec theories on it.

and why not use a nintendo ds with opera!?
now you can install linux on this device! it have wifi and a touch-screen, a microphone ....and it is cheaper than any other wifi device :-)

I hope that with our hardware and (even rather basic) software more people will be able to play with different lenses and post results.

I have no doubt they will. (!)


Spoiled by FOSS I feel really bad when I have to reverse-engineer (stupid waste of time) but it can be a fun game that I enjoyed myself many years ago - I was behind the Iron Curtain at the time :-)

hehe makes me think of when I was a kid and hacked the commodore C64 to squeeze every last bit out of it... :) - it sure was a different time. I grew up in Sweden..not that far from old soviet - in many senses.

He, He, Matteo, I wasn't going to suggest that because people might think it was too much. I don't know how capable the DS would be to control, decompress and display the data. In the Digital Cinema projects we mused with the idea of doing control of SD RAW through an Game Boy advance.

Odd, I know this is off topic, but exactly how did they get the extended resolution, 80 column text mode, and sprite in the borders? I used to have fun with different ideas to extend things in those days, sort of similar to what we are talking about here of using consumer electronics as viewers fro the camera. I used to be in a community that had the most powerful processor design available (the Novix, latter it became the Harris RTX engine). Like plugging the Novix into an Atari 2600 cartridge, and letting the Novix do the graphics and sound control, with the Atari hardware acting as an viewer (I think the Atari might have lacked writes control from the cartridge to the chips for that. Another was to bypass the buss, and replace chips in the C64 or Amiga with socket in expansion boards that have extra performance (when the IBM CELL comes down in power requirements, it could even, theoretically, be place in and commodore 64 with an scheme like that). Fun times ;).

I have no doubt they will. (!)

Odd, next week we'll order some of the new 10349 boards (and post info) - it will have rs-232, usb (with hub), ide connector (44 pin, 2mm - for 2.5") and just some pin headers. So it will be possible to attach some prototype board to it, solder-wire it to the connections on the 10349, using that pin header for custom I/Os.

We will have some unused 10347 boards Rev 0 (after finishing with prototype I will update the layout before production run) - it will be possible to use the part with the lens interface. So cutting 10347, installing some components on it and soldering it on top of 10349 will make lens interface. Actually it is possible to attach that part of the 10347 board to the 16-pin connector of the 333 camera, but you'll need to add 3.3V->5V converter (and make a custom software build).

hehe makes me think of when I was a kid and hacked the commodore C64 to squeeze every last bit out of it... :) - it sure was a different time. I grew up in Sweden..not that far from old soviet - in many senses.

Current administration in this country (where I am now) seems to follow steps of the failed soviet system so familiar to me ... :-(

Odd, I know this is off topic, but exactly how did they get the extended resolution, 80 column text mode, and sprite in the borders?

Extended resolution - no idea :) - sprites in the border, if I remember correctly I hooked an interrupt and then used NOP (no operation) commands to delay/sync up commands so they are done when the screen cathode ray is outside the frame...if that makes sense? :)


even, theoretically, be place in and commodore 64 with an scheme like that). Fun times ;).

Things like these are so much easier these days as we have the internet to draw information from...add to that all open source projects!!

Now when even hardware is turning open source - things are really getting interesting! :) - like elphel (!!)...and on a smaller scale, projects like arduino: http://www.arduino.cc - I use this one to control my Canon SLR for timelapse.

Odd, next week we'll order some of the new 10349 boards (and post info) usb (with hub), ide connector (44 pin, 2mm - for 2.5")

Hub - so it's a USB host? Great!

I tried to find info on the 10349 board on the wiki...no luck - I look forward to the more info post! :)


So cutting 10347, installing some components on it and soldering it on top of 10349 will make lens interface. Actually it is possible to attach that part of the 10347 board to the 16-pin connector of the 333 camera, but you'll need to add 3.3V->5V converter (and make a custom software build).


You really make me want to buy the 333 ;) - but I'll try to hold on and wait for the 353. The main reason being the harddisk - being able to use the camera on the go without a laptop is gold to me.

Once a 353 is available - would it be possible/hard to use part of the 347 prototype board to make a lens interface? I know how to solder and read spec sheets...but I'm far away from high tech stuff. I studied electronics for three years when I was 20...but that's 15years ago ;)


Current administration in this country (where I am now) seems to follow steps of the failed soviet system so familiar to me ... :-(

The way huge corporations get more and more powerful...in the end - in my humble opinion - extreme left wing meets up with the extreme right wing. Guess they have..."mutual interests". :)

Extended resolution - no idea :) - sprites in the border, if I remember correctly I hooked an interrupt and then used NOP (no operation) commands to delay/sync up commands so they are done when the screen cathode ray is outside the frame...if that makes sense? :)

Yep, makes sense, interesting. If we only new the tricks back when we had the machines, we might have been more inclined to keep them around. The Commodore 128 was a good selling machine in the US for years with the Amiga around.

35mb 'original unaltered' full frame 12fps 333 clip. Its 10secs long & recorded at 70%.

http://www.tacx-video.com/Elphel/

Phil

RAW, as in 3 mpixel bayer grey scale image?

How do we play it back?

Thanks, will probably look at it tomorrow or so, god willing, after I finish a few things.

great looking video. i forget how nice these look compared to every video camera. no scaling, no cheap lens, no heavy processing/sharpening, what a nice clean looking image, and nice dynamic range. i mean cut the vertical res in half and double the frame rate and you have a wide 2k cinematic image right there. how is there no rolling shutter? short exposure? I mean even the 333 technically could handle anything modern camcorders could handle. the hvx200 seems to have almost identical pixelrate limitations. 960x720@60, 1280x1080@30 ~= 42MP/s (which is what elphel 333 lists as its hardware pixel compression speed limit). wow, direct capture to hard drive? sounds wonderful

plays fine for me, i dont think its real raw, my computer decodes it with mpeg-4

Sorry thats just my own words for things confusing everyone, its original video not Raw. Its 70% quality Mjpeg that was in a ogg container. I just put it in a avi container without rendering it. It looks crisp because its 3megapixels using the entire lens. Once you start only using a small part of the lens things get obviously a bit less crisp & tougher to focus.

You need a Mjpeg codec to work with the video in say Vegas etc. if you have Virtualdub it should play in that.

Phil

42MP/s (which is what elphel 333 lists as its hardware pixel compression speed limit)

42 comes as 125MHz/2/1.5
125Mhz - memory/compressor clock, I believe we'll be able to get 133 at least - memory in 353 is 6ns already, but the FPGA code should be improved.
Then = FPGA is larger, so we can runs some critical parts in parallel.
/2 comes from the compressor implementation - last stages (Huffman, bit stuffer) have to run twice faster than the input pixels to guarantee there will be no buffer overflows (currently input stages of the compressor get /process data without asking next ones if they are ready).
/1.5 - comes from Bayer -> YCbCr 4:2:0 conversion, for each 4 raw sensor pixels compressor has to process 6 (4 - Y, 1 - Cb, 1 - Cr).

wow, direct capture to hard drive? sounds wonderful
Yes, that should be possible (if you mean hard drive in the camera) with IDE available in 353.

http://www.tacx-video.com/Elphel/vlcsnap-10453.png here is a frame from the clip. (saved as a png file from the VLC player thats recommended for being able to play just about any type of video clip).

http://www.tacx-video.com/Elphel/Rabobank-333-Original-frame.jpg A 1280x1024 frame from another clip, its the same lens set at the same focus. If your looking at the full frame compressed into a browser then you will see the difference in clarity between 3megaPixels & 1megapixels combined with more grain from the lens.

http://www.tacx-video.com/Elphel/elphelDemo.wmv a little clip made from the older 313 footage (1280x1024 sensor 22fps), please right click & select 'save target' as its got music & its got to play properly.


Phil

Is there any example footage of the bayer pattern being recorded as grey scale, and of it debayered and converted to video (for playback)?

Thanks

Wayne.

Seems like it would be tough to compress a bayer image, it might look really noisy to jpeg compression, and jpeg doesnt deal well with noise. I dont doubt it would mess up colors. maybe separating out each color and compressing them to jpeg separately?

Well that's what's proposed...separate the colours and then grayscale JPG them separately...then combine them in post.

yes - I would also very much like to see what could be done using this!

//O.

I can give you raw file of the four planes if you want to play with it. I would have test it myself but i don't have photoshop and the gimp raw import function is not really working...
I have done experiment with bayer compression some times ago, using DCT only on the red and blue channel, leaving the green untouched and then range coding everything. Size wasn't bad at all, but i had some bug in the quantization, so i've no idea about the quality.
Time to get back to work, i guess :)

Oh btw, i was here because i read some news about a Dirac Pro profile, even if the news is quite old, it sound very interesting, as it should be supported by the BBC...
http://sourceforge.net/forum/forum.php?forum_id=609681

Yes please post the file!
Do you know what kind of hardware captured the raw file?

Also - andrey? Is there a raw file from the 333 that we can play around with?

I work a lot with 3dsMax (its my day job) and I believe it would be quite easy to write a script that can separate the colours and then save them as Jpeg + load and combine...just to try out the idea.

I would of course post my findings.

//O.

amazing display of the power of the elphel camera Phil!
if with the 353 we can achieve a 2000 x 850 pixel at 24fps without exposure difference from left to right side we could make very good cinema camera!

Yes please post the file!
Do you know what kind of hardware captured the raw file?

Also - andrey? Is there a raw file from the 333 that we can play around with?

I work a lot with 3dsMax (its my day job) and I believe it would be quite easy to write a script that can separate the colours and then save them as Jpeg + load and combine...just to try out the idea.

I would of course post my findings.

//O.

Yes, i asked Andrey for material, in fact you can download the current raw image from the elphel public camera at any moment ;)
I'll compile my little tool tonight and post the raw files.
And i forgot to say that the previous video is completly amazing!

Seems like it would be tough to compress a bayer image, it might look really noisy to jpeg compression, and jpeg doesnt deal well with noise. I dont doubt it would mess up colors. maybe separating out each color and compressing them to jpeg separately?

This is what was talked about an week or two ago, that Andrey had an Bayer compression scheme for the 323. It would also be interesting to see how good an result could be achieved by Jpeg compressing the bayer sensor image in camera, rather than speculating how bad it is. When I say how good can be achieved, by trying all Jpeg compression options and setup available in the existing circuit.

amazing display of the power of the elphel camera Phil!
if with the 353 we can achieve a 2000 x 850 pixel at 24fps without exposure difference from left to right side we could make very good cinema camera!

Oh Ive got to finally cut a section from the film in Rome! Some of it is a bit over exposed but when the light is good I have some really nice images with the Fish eye lens. Personally I like the 313 image better due to the bigger % of sensor area thats being used in the video. But its too slow for me.

Yes a bigger then standard image is going to result in great looking video or film. I will want to film 4:3 though for the PC. Although even many PC monitors now days are wide screen.

I get 2000x800 @ 85% quality on the 333 at exactly 24 frames per second.

http://www.buysmartpc.com/333/333framecc.jpg
(color corrected)

I am very pleased.

Impressive Daniel. What data rate does that work out to?

Impressive Daniel. What data rate does that work out to?

If its the mjpeg stream the data rate is going to be either dependent on the the jpeg size (how complex is the image??) , the camera cpu, the write speed of the hard drive (if you have a really cheap slow laptop drive) or perhaps the bandwidth.

So if your filming a face with blue sky the image will be small & thus also the data rate, If your filming in the forest with loads of leaves its going to be huge. You need to think about this before you set up the camera. There perhaps needs to be a variable % quality setting that adjusts the quality level of the jpeg stream?

You can see this effect with any digital camera. the elphel when filming mjpeg is in effect a super fast digital camera.

Phil

I'm curious if I can push it any higher. I don't know if the bottleneck is the computer or I reached the limit of the camera.

x64 3500 amd
1 gig ram
7900 geforce
7200 sata II hdd

I have not yet found a laptop available to me fast enough to handle the 333 stream at 2000x800@85. The best I have found so far was 11 fps on a new sony vaio.

Currently I am building an acrylic body for the camera to hold all the necessary computer components. While I will still require a power source, it would be nice to integrate everything into a single unit. I have a prototype built, and while I am satisfied with the size I still need to refine it to get a more professional appearance. A keyboard and mouse is not a very mobile solution so I plan to use the Nostromo N50 for input. I will address noise issues with sound dampening foam and proper cooling.

I'm curious if I can push it any higher. I don't know if the bottleneck is the computer or I reached the limit of the camera.

x64 3500 amd
1 gig ram
7900 geforce
7200 sata II hdd

I have not yet found a laptop available to me fast enough to handle the 333 stream at 2000x800@85. The best I have found so far was 11 fps on a new sony vaio.

Currently I am building an acrylic body for the camera to hold all the necessary computer components. While I will still require a power source, it would be nice to integrate everything into a single unit. I have a prototype built, and while I am satisfied with the size I still need to refine it to get a more professional appearance. A keyboard and mouse is not a very mobile solution so I plan to use the Nostromo N50 for input. I will address noise issues with sound dampening foam and proper cooling.

I filmed that clip above with my Acer & that clip is full resolution 2048x1536 12fps. I think you need to play with the settings in knoppix? Or you have a really slow hard drive?

I filmed that clip above with my Acer & that clip is full resolution 2048x1536 12fps. I think you need to play with the settings in knoppix? Or you have a really slow hard drive?

Are you filming inside with it? If you are then you you have to think exposure & use a LOT of extra light. Light the inside up like a TV studio. If exposure needs to be longer then the frame rate the frame rate will drop. its probably this thats causing the slow down. Try it outside in the sun.

Are you filming inside with it? If you are then you you have to think exposure & use a LOT of extra light. Light the inside up like a TV studio. If exposure needs to be longer then the frame rate the frame rate will drop. its probably this thats causing the slow down. Try it outside in the sun.

I noticed a slowdown at higher exposure times, but I try not to touch the exposure setting and just add more light.

The tests were done with the laptop outside on a sunny day. I'm not sure about the laptop specs, I believe it was an intel core duo with a 5400 hdd.