DNxHD 1920x816 reverts to 1920x1080 after render

essami wrote on 5/8/2013, 11:55 AM
Hi,

Im trying to render a 1920x816 file with Vegas Pro 10 in quicktime .mov, DNxHD format. I've downloaded and installed the latest DNxHD codec from Avid website.

What happens is after rendering the file plays back stretched as 1920x1080 and also Mediainfo reports it as 1920x1080 size.

Upon render I've chose custom frame size and set it at 1920x816 and these are the project settings as well. I'm a bit at a loss here so help would be appriciated.

Thanks!

Sami

Comments

essami wrote on 5/8/2013, 12:01 PM
Doing further testing this doesn't happen when rendering to mp4. So I'm guessing it's a DNxHD issue. Is it possible to render 1920x816 with DNxHD?
musicvid10 wrote on 5/8/2013, 12:30 PM
Unfortunately, DNxHD renders everything to its own chosen template dimensions.
essami wrote on 5/8/2013, 2:10 PM
Any work around for this? How do people deliver 2.35:1 material with Vegas?

I need to ftp the video so it has to be managable size...
Chienworks wrote on 5/8/2013, 2:43 PM
Pretty much every mainstream 2:35:1 material i've ever seen has been embedded in a 16:9 frame, letterboxed.

This probably shouldn't be an issue with file size as the black edges will require almost no additional storage space in the output file.
essami wrote on 5/8/2013, 2:54 PM
Ah sorry, I meant that I cant do uncompressed quicktime etc. in regards to file size.

Ive been specifically requested to deliver a non letterboxed version though. Will have to look into this but all suggestions are welcome!

Thank you!
John_Cline wrote on 5/8/2013, 5:49 PM
I have used Cineform to do non-standard image dimensions and Cineform can also be rendered to a .MOV container at 1920x816. The free Cineform Studio codec package for both PC and MAC is available at www.gopro.com. It integrates into Vegas, Premiere, Final Cut Pro etc and can render to both AVI and MOV containers.

The video quality and file size are essentially equivalent to DNxHD. If your clients can be talked into installing the free Cineform codec, your problem is solved.
musicvid10 wrote on 5/8/2013, 8:22 PM
Excellent suggestion, John Cline.
I was thinking of MXF, but isn't it also confined to standard template sizes?

One could also place the video on a full 1080p project canvas, render in DNxHD, then let Handbrake crop out the black for MP4 delivery.
WillemT wrote on 5/9/2013, 4:17 AM
@John_Cline, with reference to the free Cineform Gopro codec.

I am using the free Cineform Gopro codec all the time, mostly with Deshaker.

Thought I would download the latest version to mess with the Protunes mode from a Hero3 (I do not know whether this was required - just thought it should be the wise option). The download was version 1.3.2. Vegas would no longer render to the Cineform codec.

I had to finally restore an image backup to get the older version working again - version 1.2.1 (I do not have any versions in between - if there were any). A simple uninstall and reinstall of 1.2.1 would still not allow a Cineform render. I cannot remember if VirtualDub allowed a render to the version 1.3.2 install.

The above versions refers to the GoPro CineForm Studio installer. Version 1.2.1 installs Cineform Codec 8.1.2 - I cannot remember the codec version for the 1.3.2 install.

Am I missing something?

Willem.
Mark_e wrote on 5/9/2013, 4:26 AM
I went through this and checked with the vendor at the time, here is my understanding,

The free gopro ciniform codec comes with restrictions on what third party applications can use it, deshaker and virtual dub it appears as an option and works up to 1080p, Vegas 12 it doesn't not appear because of that restriction. If you install one of the paid gopro studio options it will appear in 12 and also unlock 1080p and upwards for the codec.

If you drop an older version (vegas 10 or sound forge 10 etc.) avi.dll's into Vegas 12 it will pick it up, I'm not sure if that's a bug with the new version or it was intended to block it.

That's why it works for some people and not others if you have the paid version or the older version you will see it, if you have only ever had the free version that's why you do not.
WillemT wrote on 5/9/2013, 4:34 AM
Thanks for the explanation.

I only use the free version. For my purposes I will just stay with the older install - it does all I require at present. The paid version are not exactly cheap - GoPro in general is getting a lot more expensive as well.

Willem.
Mark_e wrote on 5/9/2013, 4:50 AM
I did same I almost got it as I do like it but was just too much and I'm not going to be working above 1080p for some time + the free one will render out the higher resolution files from the studio app into ciniform without restriction and then can just crop those or render into something else if required for the odd time I might need it.