Battlefield 5 - Re-Cut and Audio Remastered Reveal Trailer, synced to "The Man Comes Around" by Johnny Cash

Looking forward to BF5, I saw the ‘Reveal Trailer’ that was released and noticed no music in it. So - inspired by “The Dawn Of The Dead”’s Title Sequence (‘opening credits’), I thought Mr. Cash’s song would go great with this gameplay trailer as a Backing Track...

Because the original Reveal Trailer wasn’t a Montage but a Sequence Shot (‘one-shot long take’) [nicely done btw, imo] – I had to re-cut it and re-master the audio levels to blend with the added music track (and Effects I added). I also had to cut/edit down Mr. Cash’s classic song a bit, because there wasn’t enough footage to cover the entire length (for one section, I added a bit of some Early Alpha Screenshots and Concept Art released by EA). I also added a few extras to the audio, such as Environmental Audio Enhancements to some Explosions, and Tinnitus (‘ear ringing after an explosion’) at the close-up section.

In the end, I think both matched up not too bad; the emotion of the song and the chaos of the gameplay… so I thought I would share it here for you all – I hope you enjoy it. Looking forward to what Battlefield 5 might be – See You In The Game! 

~T 

.

.

. 

Source Video by EA/DICE, here:

https://www.youtube.com/watch?v=fb1MR... 

Source Music by Johnny Cash, one version here:

https://www.youtube.com/watch?v=k9IfH... 

Edited and Remastered by Tesityr (Troy from The Game Tips And More Blog), in a combination of: 

CyberLink’s PowerDirector 

Sony’s Vegas Pro Edit (now by MAGIX) 

Corel’s PaintShop Pro 

Original Gameplay Material Copyright EA/Activision 

No Copyright Infringement Intended (Fan Creation Advertisement)



[Note1: If it looks kind of low-quality, it was a couple things: one, I used the very first Trailer footage that came out, which was 30fps and lower quality (now they have 60fps HQ Trailer available). Two, I accidentally re-compressed it twice while processing/editing. It was too much to start over, so here it is, sorry, heh.]


[Note2: I did not add advertisements to the video, but I got a warning that they will be added due to use of the song...]

Bandicam - Their 2.1.0 Release and Testing Compatibility of the MP4 Container Recordings with Nine Different Video Editing Programs [Link To Forum Post]

Just letting those who use Bandicam to record their gameplay know, I tested the newest version (2.1.0.708, released two days ago) and Bandicam's new ability to record into an MP4 container [natively], an addition that would hopefully increase compatibility with video editing programs. All I did was some quick tests by importing recordings created by Bandicam into different video editing applications; but I wanted to share the results with you all. Here are the programs I tested:

- Adobe Premiere Pro 6 (Trial)
- Avid Media Composer 8.1 (Trial)
- Sony's Vegas Movie Studio 11 Platinum
- CyberLink's PowerDirector 12
- Lightworks 12
- Nero Video 11
and some free video editing applications...

For the results of my testing the new MP4 container recording option with those video editors, visit my short post at the Official Bandicam Forum here:

http://www.bandisoft.com/forum/viewtopic.php?f=10&t=2956&p=10235

I hope you find it useful and See You In The Games!

And More: Editing NVIDIA's Shadowplay Recordings and 'The VFR/CFR Problem' (Text-Only Version)

[Updates at bottom of article]

Just a quick post on the problem many people seem to be having with editing NVIDIA's Shadowplay recordings and how to work around it, for now...

For those who don't know, Shadowplay is a free game recording capability that is included in NVIDIA's GeForce Experience utility and is accessible by anyone with an NVIDIA GPU that is a GTX 650 or higher [they state "600 Series or higher"]. Simply install the GFx utility [my abbrev.] and turn it on and Shadowplay will record a buffered period of time, overwriting that space/file again and again, until you decide to save something cool that happened in the game.

Whether FRAPS sold NVIDIA the code to do buffered/looped recording (as FRAPS has had it for many years), or NVIDIA developed it on their own, the end result is the same. The problem is, a ton of people [if technical and game forums everywhere are an indication] are unable to edit the end output correctly, when using Shadowplay.

The main reason why this seems to happen, could be due to Shadowplay utilizing VFR to record it's video data into a file. VFR stands for Variable Frame Rate, and essentially it allows the frame rate to change from slow to fast, above and below the 'set' frame rate, many times if needed, within a single video file. This helps to save space by making low-motion (or static) scenes use less frames within the video file and make complex scenes (with high-action/movements) look smoother by inserting more frames into the video file. Sounds good and test videos look fine, but the problem is when going to then edit the 'Shadowplays'.

Many video editing applications (especially NLE's [Non-Linear Editors]) may not like Shadowplay and will choke on the video, hold back sound in spurts and spit up bits of food on your screen if you try to edit the recordings. This could be due to the usage of VFR.

Note: I don't want to 'put the blame' on NVIDIA or VFR here, NVIDIA is a fantastic company with great innovations and products, and VFR is a great method for organizing frames within video data that creates a lot of 'headroom for compression' (lower file sizes by reducing the number of frames used) while trying to maintain Quality as well (by increasing the frames utilized per second within the GOP data of the file, as the codec decides it is beneficial). It merely is not as compatible, when it comes to video editing programs. As another example, Plays.Tv uses Accelerated VFR in its' Client to buffer/record with, which it notes here in their Support section, is simply less compatible and can create audio/video synchronization problems - the issue is VFR and editing compatibility -  not these companies/utilities themselves...

Fortunately, the 'fix' [which in my opinion of more of a work-around] is relatively easy, if slightly time-consuming:

Simply re-render the Shadowplay recordings into CFR (constant frame rate) video (where 60fps really is 60 frames being recorded or played back in sequence, in the video, every second, throughout the entire clip). There are many apps that can do this, but the most popular [most-popularly-used in the video-editing circles that are experiencing this problem] is probably Handbrake (it is completely free to use). Simply import your video and choose Constant Framerate in the Video Tab. That's it.

Another program you can use, is built right in (if you use Windows): Windows Movie Maker [Note: Windows Movie Maker does not seem to be bundled with Windows 10, it may however be available as a separate download]. Simply import the video and without adjusting anything, export (render) it out to MPEG-4 (MP4) format. It will produce a CFR (Constant Frame Rate) video that you can then import into programs that were having trouble with VFR - like Adobe's Premiere and other video editing applications.

[Choose a high quality setting or high bitrate, to maintain as much of your original recording detail as possible (so it won't compress it even more and lose detail). If you need to set a BitRate for the export, make sure to set it higher than the original video clip(s) BitRate ((Personal Suggestion: 2x more if you can))]

Once this is done, you'll be able to import your Shadowplay 're-renders' without problem, whether you use Premiere, Vegas, Lightworks or some other video editing application that has been having trouble importing your VFR video (for instance, some people have had problems with Shadowplay recordings using CyberLink's PowerDirector and others have not had a problem with PowerDirector at all, importing it fine - I have not used Shadowplay Recordings in PowerDirector yet [I do not have a GPU capable of using Shadowplay at this time] but I have personally imported VFR material into PowerDirector 12 without problem).

[I might come back and add screenshots to this article in the future, or create a new one talking more specifically about VFR and importing it into Premiere, but for now I wanted to bang it out and get it up here to help people who have been having this problem (many since last year, when Shadowplay first came out, with even more people having the problem earlier than that with Premiere and VFR recordings from their cameras)]

I hope that helps some people out for now, anyway. Have fun recording - and See You In The Games!




Update 1:

Bandicam has now implemented an option in their game recording software (as of July 2015), which allows choosing CFR recording or VFR recording. Since it also uses GPU-accelerated codecs such as AMDAPP, NVENC, QuickSync (and can be made to use CUDA, if you still have that), it seems to have become a viable alternative to this problem. As a Registered User of Bandicam, I shall test out this latest version of the software and perhaps write a post about it Soon™


Update 2:

I have done some quick testing with this new version of Bandicam (with the ability to choose CFR as well as use VFR if desired) and have written a short post about it at this blog, here.


Update 3 - 2018.06:

NVIDIA's Game Recording Utility seems to have changed names a few times, known as Shadowplay, then Share, then In-Game Overlay. Whatever it is called today, while this issue with editing VFR might remain, on some older video editing applications; it seems to be less of an issue on the most recent versions of video editing apps (as of 2018) - tested personally with a few programs, such as Sony's Vegas Pro 14 (now taken over by MAGIX), CyberLink's PowerDirector 16, and Corel's VideoStudio 2018 - all three video editors did not have an issue Importing and Editing VFR material (as of June 2018 when I did these short tests) [I do not own and did not test Adobe's Premiere/Elements, at this time, sorry]. So, if you are having an issue editing Shadowplay/NVENC recordings circa 2018 or later, try updating your video editing application(s), if you can.

And More: The EULA Keeps Popping Up When Starting Sony's Vegas Video Editing Applications (FIX)

Since the most popular answer on the ongoing poll I have running here at the blog ("what type of posts would you like to see more of in 2014" [top right, it will run until the middle of the year]) is "Tips And Tricks Of Video Capturing And Editing", I thought I would start more of these types of requested posts by sharing this fix for a problem that seems to pop up intermittently with Sony's Vegas line of products.


Whether you have just re-installed it or whether it has been on your system for a while, 'something' is causing the EULA (End User License Agreement) to pop up and require you to agree to it, even if you have already done so and/or Registered the program. This question comes up once in a while on the Sony Creative Software Official Forums and I have seen it elsewhere. I was recently reminded of it again because it is also something that just happened to me on my system! I didn't re-install Vegas or make any large changes related to Vegas, yet this little guy started popping-up every time I started up Vegas Movie Studio HD**:

The popup that comes up for some people, every time they start Vegas

The fix is a simple one, originally suggested by a Sony Forum Moderator and quoted/forwarded frequently on the official forums, to those who come and ask the question there. Although it seems more like a 'workaround' than a 'fix [in my opinion], it works just fine and since it is officially supported by Sony and I just tested it for verification myself [that it does indeed solve the problem], so now I share it here with you:

• To stop the EULA popping up every time you start Sony Vegas, simply open Windows Explorer and navigate to the folder where you installed it on your system. 
• Then, find the file that is titled, simply, "eula". There will be no Extension showing, even if you have the Windows option to 'Hide Extensions For Known File Types' turned off. 
• Rename (or delete) the file. That's it! 

Now the EULA cannot pop up anymore and won't, every time you start up Vegas to edit your game captures.

**Although this example shows steps for the Movie Studio version of Sony's Vegas Video editing line, the EULA 'fix' is the same steps for Vegas Pro, Vegas Edit or other versions of Vegas

Enjoy popup-free video editing once again - and See You In The Games!

Quality Test - Diablo III and Bandicam's "For Edit" Preset / YouTube Upload Test

With the Bandicam "For Edit" Preset, every frame is an independent Keyframe or I-Frame (Information Frame), which is a type of frame that can be 'cut' or started from in video editing programs (technically, every frame is a JPG picture). Also, the audio is Uncompressed, which means that any video editor should be able to recognize the sound data. Errors in programs like Virtualdub saying "Error initializing audio stream decompression" or Sony's Vegas showing "Stream attributes could not be determined" will not occur and these will open the audio just fine with this setting.

Testing out Bandicam as a game recorder and playing during the launch of Diablo 3 (woot!), I've put together some settings/specifications, uploaded it to YouTube, and collected some results for you all:

The video is short, but I was mainly testing a few things:
1) D3's performance, with all options maxed out
2) Capture quality of Bandicam's 'For Edit Premiere/Sony Vegas' Preset and performance/lag of using it
3) The Logo/Watermark capability of Bandicam
4) YouTube's quality maintainability


Recorded with: Bandicam
- v.179204 (Latest at time of this post)
- 'For Edit (Premiere, Sony Vegas)' Preset
- MJPEG, "Full Size", 80%quality (Preset), 30fps, Uncompressed PCM Audio at 48kHz
- Logo option (our GTAM watermark), lower right, 10% opacity


Game: Diablo III (Retail Release) Launch Day
- Witch Doctor, Cathedral Level 3
- Texture Quality: High
- Shadow Quality: High
- Physics: High

- Clutter Density: High

- "Anti-Aliasing" checkbox ticked ON


Resolution: 1680x1050 (1.6AR) recorded at 1680x1050 ("Full Size")**
Filtering: 4xMSAA, 4xAF, set in Control Panel of Videocard
Framerate while not recording: 80-100fps
Framerate while recording: 80-100fps

For people trying out Bandicam and finding your recordings are choppy/laggy on playback (when looking at the original generated/recorded file), you should find that compressing it to a file with a smaller bitrate/size in a format you will keep it permanently in, it will play back that file just fine.

I chose this D3 clip for a Quality Test because it was a good example of both fast movements/action on the screen, as well as slow/non-moving parts, including text. It has dark and light areas, high contrast edges, and tests wide area panning as well.

Bandicam's "For Edit" Preset worked great, with clear text and action in the original recording, while flatter, darker parts were not overly compressed which would create excessive macroblocks or be too smoothed out. There were some Gibbs Effects/Mosquito Noise around text and on some of the button logos in the original recording, but you had to look closely to see it, which is pretty good for not being a 100% Quality setting.

The very small amount of color banding present in the original recording was somewhat generated by the Game Engine (seen in the lower-right quadrant of this video, and in the Diablo3 login screen around the moon, etc.), and there shouldn't be much, due to using MJPEG as a recording codec.

If you are having problems with Color Banding that is not in the game itself, try MJPEG as your recording codec




Average bitrate of the original was about 40Mbps, which meant a writing stream to the disk of about 5MB/s, which any hard drive can handle (recorded onto a drive capable of 150MB/s).
Framerate during recording was maintained at 80-100fps (same framerate as not recording).
The original 1 minute generated file is about 300MB in size with these settings. The recompressed MPEG-4, resized to 1080p file, has an average bitrate of 20Mbps and is about 140MB in size.

While this Preset in Bandicam is designed for compatibility with editing programs, the original recording was uploaded directly from the Bandicam-generated file anyway, to test the effects of uploading to YouTube from an original recording.

** The video at the top was Lanzcos3 resized from the original 1680x1050 capture to a 1728x1080 (1.6 AR) [MPEG-4 H.264 AVC/AAC file with a bitrate of 20000kbps (audio at 384kbps) using a Deblocking Filter setting of +0+0] because the original upload was down-sized to 1280x720 by YouTube and looked much worse, see here below:

The Result:
Recorded at 1680x1050, YouTube had downsized that one to 720 vertical lines. The Gibbs Effects were no longer present because of this, but excessive smoothing and other compression artifacts were introduced. Text was far less readable and nothing on the screen was as crisp as the original 1050p recording. Aliasing was also introduced. This was unfortunate but understandable however, as YouTube can no doubt not keep 'everything' at 'very high bitrates' on their servers, and since it was not 1080p, it simply scaled it down.

A single frame taken from each video for comparison (Frame 813, zoomed section) from the original Bandicam recording, YouTube's version of the 1080p upload and YouTube's 720p version of the 1680x1050 upload. Click to see Full Size.

The resized-from-1050p-to-1080p version maintained much of its detail after uploading to YouTube. The text is closer to the crispness of the original recording, and there is only some smoothing and deblocking being done. There are some macroblock artifacts and color banding accentuation in the darker areas however (for instance, the lower-right quadrant much of the time) but other than that, it is a decent quality version of the 1080p upload.


For those recording at 1680x1050, I recommend upsizing it to 1728x1080 so that YouTube keeps most of the detail of your recordings

  Well done, Bandicam (and YouTube).

Hopefully this information will help out any gamers that are looking to start recording their experiences, or even the already numerous people who are recording and sharing their great videos. Thank you all for sharing and your efforts.



Please note dear reader, that I am not saying "This codec is the best one to record with" or "use this one only". I am merely showing that it is possible or how to tweak it for quality or file size, as to your own personal tastes. There are many codecs out there to choose from when game recording and although some are more apt for certain types of games than others, overall it is your own choice to do with as you will.


See you in the games!