Understanding smart rendering using cineform codec

[John Rofrano]

[brad barnes] “So I’m convinced the problem is in my windows media player and not the rendered file.”

That’s what it sounds like to me. Glad you found it.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Brad Barnes]

Ok, I have one last little problem. The bass kick in the song is way to bass heavy in the uploaded youtube video but in the cineform render it’s eq’d properly just like the original song master and in the sony avc I made from rendering the cineform master it’s eq’d properly.
How do you think I can solve this problem?

I can replace the cineform masters audio with the original song before I convert the song to sony avc to get rid of a pointless render of the song but I don’t know if that will help or not.

Other than that I don’t know what to do because if the problem is converting a highly compressed mp4 into another highly compressed webm or mp4 then I would have to convert my cineform master into a lossless codec that youtube accepts and maybe that will prevent the audio bass issue.

Google is my brain now my real one has atrophied.

[John Rofrano]

You could just use the Track EQ to roll off the bass a little when rendering to AVC.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Brad Barnes]

I could do that If I had a treated room to get an honest mix. It would take days to let the audio engineer I use do it because he’s busy. But I guess I gotta do what I gotta do.

I’ve converted the audio so far from .wav 44.1 24bit master to pcm uncompressed 44.1 24bit to get the cineform video/audio master. If I converted to another avi format youtube recognizea like sony yuv I would convert my audio yet again to pcm uncompressed 44.1 24bit audio.

What happens when you keep converting pcm uncompressed 44.1 24 bit audio to pcm uncompressed 44.1 24 bit audio?
Does vegas smart render the audio?

Google is my brain now my real one has atrophied.

[John Rofrano]

Audio for video is 48K/16bit. So I would convert the 44.1K/24bit to 48K/16bit as a first step. Since PCM is uncompressed, you can render as many times as you’d like after that and there will be no loss (other than the initial dither from 24bit to 16bit)

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Brad Barnes]

Just thought I’d inform you that I was having trouble rendering the avi cineform codec master to other avi codecs like lagarith, all codecs vegas wouldn’t render properly.
I imported the same avi cineform master to adobe premiere and it rendered it to lagarith the first try with no errors in the video.
All the settings were Identical that I rendered to in vegas and premiere pro. Even made sure and rendered to lagarith yuy2 since that is what I tried to render to in vegas.

And one question. If you select gaussian blur when rendering then you decide to import your master render that you used gaussian blur on to render it to something else should you deselect the gaussian blur?
Thats what I assumed and I didn’t select gaussian or any type of blur in adobe premiere when I rendered to lagarith.

Google is my brain now my real one has atrophied.

[Brad Barnes]

does gaussian motion blur ever need to be selected in the project properies if the video is of real people and not animation?

Google is my brain now my real one has atrophied.

[John Rofrano]

[brad barnes] “does gaussian motion blur ever need to be selected in the project properies if the video is of real people and not animation?”

This setting has nothing to do with video content. It is the type of blur to use when you enable the Motion Blur envelope on the Master Video Bus. If you never apply this envelope it doesn’t matter what you select.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Guy Smith]

Don’t get too hasty on dismissing this. I also ran across the audio offset effect from NeoScene. I recently took captured HDV footage (with a Sony Z1U) and processed it in NeoScene and discovered a 2-3 frame offset (audio ahead of video).

I took some test footage (shot of a standard film clapboard) and imported in into my PC as straight m2t files. Putting them on the Vegas timeline, the audio “clap” on the m2t file was in perfect sync with the visual frame showing the clapboard coming together. After converting to Cineform however, the video frame appears 2-3 frames after the audio.

It is a subtle difference, but one that, embarassingly, a client noticed on a tight closeup on an interview. With over 20 years of video editing experience, I didn’t notice it, primarily because I believed it was in sync (after all, no pink offset in Vegas).

I’d be interested in others trying testing Neoscene and it’s conversion capability to see if they have this issue also. I’ve tried it on 2 PCs now with the same results (Neoscene 5.5.1 build 323).

I’m currently swapping emails with support at Cineform related to this issue.