Vegas Pro 13 Can't Open Brinno Cam AVI

vidmanic wrote on 6/1/2014, 6:05 PM

Anyone have experience with opening files from Brinno cameras in Vegas? I'm using a Brinno Construction Cam. It seems to be MJPG in an AVI container, but perhaps missing some of the metadata that Vegas needs. The only way I've gotten it open is transcoding to MP4 with Handbrake, but obviously I'm losing some quality that way. Any advice?

Comments

musicvid10 wrote on 6/1/2014, 6:22 PM

Post the complete MediaInfo readout.
Probably just a codec.

vidmanic wrote on 6/1/2014, 9:05 PM

Here's the Media Info:

General
Complete name : C:\timelapse\5 sec better 720p\TLC00002.AVI
Format : AVI
Format/Info : Audio Video Interleave
File size : 66.2 MiB
Duration : 14s 667ms
Overall bit rate : 37.9 Mbps
Writing library : TLC200

Video
ID : 0
Format : JPEG
Codec ID : MJPG
Duration : 14s 667ms
Bit rate : 36.4 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 30.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Compression mode : Lossy
Bits/(Pixel*Frame) : 1.316
Stream size : 63.6 MiB (96%)

musicvid10 wrote on 6/1/2014, 9:09 PM

Try the Mainconcept linked to in the other thread . . .

vidmanic wrote on 6/15/2014, 7:42 PM

The MJPEG codec didn't help - or at least it wasn't the only thing I needed. I installed it, but Vegas still didn't recognize the Brinno AVI files.

I did find a fix though - there seems to be a problem with the metadata in the AVI files. I ran DivFix++ on them, and now they open in Vegas just fine.

http://www.divfix.org/

videoITguy wrote on 6/15/2014, 8:18 PM

Do you know what divfix is doing ? Looks like smoke and mirrors from here.

vidmanic wrote on 6/21/2014, 1:25 PM

MEDIA INFO BEFORE DIVFIX++:
General
Complete name : G:\videos\2014-06-16 - Drive To Lot.AVI
Format : AVI
Format/Info : Audio Video Interleave
File size : 57.3 MiB
Duration : 6s 367ms
Overall bit rate : 75.5 Mbps
Writing library : TLC200

Video
ID : 0
Format : JPEG
Codec ID : MJPG
Duration : 6s 367ms
Bit rate : 72.5 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 30.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.624
Stream size : 55.1 MiB (96%)

MEDIA INFO AFTER DIVFIX++:
General
Complete name : G:\videos\DivFix++.2014-06-16 - Drive To Lot.AVI
Format : AVI
Format/Info : Audio Video Interleave
File size : 57.3 MiB
Duration : 6s 367ms
Overall bit rate : 75.5 Mbps
Writing library : TLC200

Video
ID : 0
Format : JPEG
Codec ID : MJPG
Duration : 6s 367ms
Bit rate : 75.2 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 30.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.720
Stream size : 57.1 MiB (100%)

Main difference seems to be the last two lines. Not sure what this means, but the files open in Vegas now, so I'm happy. Only downside I've seen so far is that DIVFIX++ doesn't seem to work well with large files (> 1GB).

NormanPCN wrote on 6/21/2014, 3:15 PM

Only downside I've seen so far is that DIVFIX++ doesn't seem to work well with large files (> 1GB).

DivFix rebuilds the AVI index. You can do this with other software like ffmpeg (command line) or Avidemux (GUI) and certainly others.

In AVIdemux simply use copy for both video and audio and output to a new AVI file. Nothing should be re-encoded but the index should be rebuilt. Avidemux may be fine with your large files.

vidmanic wrote on 6/21/2014, 9:13 PM

Thanks Norman, but no luck with Avidemux. It couldn't read the files (of any size).

ffmpeg looks a little over my head. I read about it quite a bit, but I don't think I have the know how necessary to write the appropriate command line to make it add missing data. Most of the examples I found were about pulling metadata from the source video file and adding it to a rendered version.

I may just give up and Handbrake the large files to MP4. Hate to render twice, but better than nothing.

NormanPCN wrote on 6/21/2014, 11:46 PM

Thanks Norman, but no luck with Avidemux. It couldn't read the files (of any size).

Bummer. Something is quirky about those AVI files with both the Vegas and Avidemux decode having issues.

Interesting about Avidemux. It uses the open source libavcodec library like Handbrake does. AFAIK. Maybe something to do with exactly how something tries to access the file.