Jump to content
SAU Community

Recommended Posts

MajorTangles BF2 Fraps Video #1

featuring "Coma" by Pendulum

-----------------------------------------

Right-eo. First ever go at capturing of video via a pc (thru Fraps), captured a few slides and sorted thru them, and compiled them to a track.

Finally worked out how to underlay the music and overlay the video.

I had my screen at 1024 x 768res with 60mhz, with fraps capturing at 30fps. I used Blaze Media Pro (free for 2 weeks, lol) to string the clips together and lay the music, and to compress it all once completed I used VirtualDub, and compressed it again to get it down from 180mb to 147mb to 58mb, so it has lost a lot of its resolution and quality.

Next time I'll try capturing at 60fps on Fraps and have my screen set at 800x600res with 75mhz. Will take my time and make a good video, but for my first up ever quick-job effort it aint that bad I suppose. I’ve never ever captured vid before, or done any of this so its a bit new to me but next movie will be better, just wanted it to move more 'freely' on the screen. *sigh* oh well

Hosted File (on a free 60mb upload site):

http://www.savefile.com/files/468115

best viewed with VLC Player, http://www.videolan.org/vlc/

Link to comment
https://www.sau.com.au/forums/topic/155038-majortangles-bf2-fraps-video-1/
Share on other sites

its not the resolution thats making your movie large ... btw there is nothing wrong with a 100mb movie if its a good movie 100mb for 10mins or little less

i suspect what is wrong is your not doing the encoding right i havnt used Blaze Media Pro before, but with Ulead VideoStudio you set out your fraps avi's on the story board do you Titles and sound tracks and then when u encode you select a movie extension and go advanced and select a further codec and tweak the settings of it, i imagine Blaze Media Pro is the same there shouldnt be any need to use Virtual Dub

even windows movie maker will do a good compresion

ill see if ive got a movie on FTP to show you the sort of quality

well i cant find what i was after but its still on my hdd its a movie of racer driver 3 @ 720x576 with a bit rate of 1.06Mbps almost 10 mins is 76mb

cheers for the tips mate, I'll follow that when I edit the next lot of footage (started tonight, got 6 nice paddle kills on record, lol). yeah Im a newb+++ with all this. ta for the advice Im sure it'll help the next one come out much better.

currently recording at 800x600 with 30fps half-screen (vid in 400x300 and playback seems to have no choppiness). I'll practise what you've written there and see how I go.

when i take my fraps footage its @ maximum i can take for unpaid version.. then if resizing is needed i let the encode do that

its nothing for me to encode upto 10odd times get get good compresion and codecs bitrate and all that

so when are ya posting all ya home made porn movies tangles ? ie deep throat tangles and tangles in the pool shed lol and not to forget the old fav big sausage tangles.

Edited by mid life crisis
so when are ya posting all ya home made porn movies tangles ? ie deep throat tangles and tangles in the pool shed lol and not to forget the old fav big sausage tangles.

LOL you crack me up Dean.

Funniest post of the day.

:ninja:

there is a program called ZD soft Game Recorder also it has more options for compressing on the fly

there was another one also but i spent some time trying to find/remember the name but cant

http://www.tucows.com/preview/502356

LOL

yeah cheers for the info, help and tips Madaz, and the humor-relief from MLC (mid life crisis or massive loser squad, lol its Fitzy reborn!). :(

taking current footage at 800 x 600 at 75mhz, with 30fps, half screened. So end footage is 400x300 (good for youtube) and seems pretty clear at this stage. Will muck around with window media player this time, but Im still editing via Blaze media Pro (aint a bad program actually)........... got so many shock paddle kills on fraps now, its almost embarresing.

:sorcerer:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...