Jump to content
SAU Community

Recommended Posts

  • Replies 238
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

here it is, skip to around 5:50 for flameage

http://www.youtube.com/watch?v=PnMvr5p_juw&feature=plcp

Does anybody know why outside is so over exposed? im using a GoPro HD2.

I was thinking maybe theres too much black in the picture from the cabin for it. But i have know idea when it comes to filming...

Does anybody know why outside is so over exposed? im using a GoPro HD2.

I was thinking maybe theres too much black in the picture from the cabin for it. But i have know idea when it comes to filming...

Check to see if your metering on the GoPro is set to "Spot Metering," which is the small dot in the middle of a square. That way, it takes a light reading from just the centre of the image instead of the whole screen (Evaluative Metering). That might help, bet even then with a GoPro it can be hit and miss unless you have the LCD Backpak or can aim it almost spot-on out the windscreen.

here it is, skip to around 5:50 for flameage

http://www.youtube.com/watch?v=PnMvr5p_juw&feature=plcp

Does anybody know why outside is so over exposed? im using a GoPro HD2.

I was thinking maybe theres too much black in the picture from the cabin for it. But i have know idea when it comes to filming...

It's trying to balance for the majority of the screen. Since most of your video is of the inside of the car it has gone for that. You can try repositioning it to see more out the window next time.

I don't know what settings they have, but you might also be able to make it work on the focal point, then all you need to do is get the outside of the car in the center of the screen for more magic. Either way, its 1 or the other really, if you get good outside, inside will be dark.

Looks awesome fun either way!!

Check to see if your metering on the GoPro is set to "Spot Metering," which is the small dot in the middle of a square. That way, it takes a light reading from just the centre of the image instead of the whole screen (Evaluative Metering). That might help, bet even then with a GoPro it can be hit and miss unless you have the LCD Backpak or can aim it almost spot-on out the windscreen.

+1 the orginal GoPro HD's came default average metering. I had to turn spot metering on. The down side is that the cabin will be much darker. But when shooting in a dark environment with bright outside you have to "tell" the device what you want to do. The "Dot" that Nick said is pretty much in the centre of the picture that is used to read how much light and therefore what exposure setting to use. When you aim it just be sure the centre of the frame goes out the windscreen.

If you have editing software you can usually bring down the exposure a bit as long as there's still a bit of detail (not washed out or all white). The colors and contrast won't be as good but will give a bit more detail.

Ok, cheers for the info guys. I'll gives that a try

What do you recommend for editing and uploading to youtube with Eric? I used the window's program but it came out pixelated in places and was quite a large file too I think (380m)

When editing I assume you mean just clipping - right? Streamclip (freebie) can do that and maintain the H.264 Mpeg4 codec the GoPro uses. It's only basic but will do clipping. Be sure to stay on an MPEG4 code - H.264 is best right now, or else xvid or divx. H.264 will produce the best looking video with the smallest size but may take longer to encode.

The GoPro in 50/60 frames progressive is ahead of the standards right now. There isn't really an Official standard that does that framerate in HD. Hence why I recommend streamclip if you just want to clip them down.

For full on video editing I use Corel VideoStudio Pro X. Does everything I need and more and only $120 on line.

For YouTube and Vimeo I usually create a 720P file in DivX format with a reasonable bitrate. Still a couple hundred megs for a few minutes but looks so much better now that everyone has big monitors and broadband.




  • Similar Content

  • Latest Posts

    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
    • I don't think it's a good buy, the trend looks bad     lol.
×
×
  • Create New...