Problems using .MP4 and .MOV Input Video? (GoPro and others)

Helpful tips, solutions, and how-to's
Forum rules
This is a read-only section, consisting of information provided or approved by RaceRender LLC

Problems using .MP4 and .MOV Input Video? (GoPro and others)

Postby RaceRender LLC » Thu Feb 07, 2013 1:05 pm

GoPro Users: If you are encountering problems with your videos in RaceRender or other software, please make sure that your camera is using a good Class 10 or better microSD card, and update the camera with the latest firmware available from GoPro. They have released several updates that appear to address issues that users were having. If you find better results with lowering the recording resolution (ie 480p or 720p instead of 1080p or higher), that tends to point to an issue with your camera's microSD card, or possibly your computer's CPU and RAM performance (although that case is typically just slow). The 2.7k and 4k resolutions will of course come at a much higher processing performance cost, but should work in RaceRender on Windows 8 and Mac OS X, as well as older versions of Windows if you have Apple's QuickTime Player installed. Keep in mind that RaceRender 2's maximum output resolution is 1080p, and the GoPro HD Hero 3 Black Edition's battery appears to last the longest at 1080p30, so it's usually not advisable to record at higher resolutions unless you have a specific reason for doing so. 720p can also provide a good balance of quality versus faster processing performance, especially for cameras that are used for picture-in-picture.

If you are processing your video with the GoPro Studio software (formerly known as Cineform), please also review this topic: viewtopic.php?f=6&t=170


All Users:

The rest of this topic applies only to the Windows version of RaceRender

Although RaceRender works very well with reading MPEG-4 and H.264 videos (.MP4 or .MOV file types), there have been a small number of reports of problems when opening these files. A few cases even included program crashes, but others were typically smaller issues such as the video length appearing wrong, the video ending prematurely, or the file not opening at all. These rare problems are often related to the specific video file, camera model that it came from, that particular computer, or some combination of those factors. In such cases, you may also notice odd behavior when using those video files with other software.

There have also been a few cases where audio was not immediately available in RaceRender from this type of video. This is a simpler issue that's typically caused by Windows 7's Media Foundation being unable to convert that audio codec into a plain format for RaceRender, and that can depend on what camera or software was used to encode that video file. It appears that Microsoft has improved this in Windows 8 (as well as improved the H.264 encoder), but it is unclear if they will update Windows 7 with that or not.

An easy workaround for most of these cases is to have RaceRender use QuickTime to decode these videos:

Note: This workaround does not apply to the 64-bit version of RaceRender. Please use the 32-bit version if needing to make use of this.

Step 1) Install Apple's QuickTime 7 Player for Windows (it's a free download; more info here: viewtopic.php?f=6&t=22 )
Step 2) Start or restart RaceRender and go to its main screen. Under the "File" menu, select "Media Libraries", and then un-check the line for "Media Foundation". .MP4 and .MOV files opened after this point will now be decoded with QuickTime, which may not be quite as fast, but it should work. In some cases, you may need to close and re-open RaceRender for the change to first take effect.

Alternatively, you may want to try using a 3rd party video conversion tool to re-encode the problem file into another supported format, or simply just recompress it into the same format.
RaceRender LLC
by HP Tuners
RaceRender LLC
Site Admin
 
Posts: 313
Joined: Sun May 13, 2012 10:39 pm

Return to Knowledge Base - RaceRender



cron