[Bf-committers] FFMPEG properties from Blender presets overridden by defaults?

[Randall Rickert]

My goal is to encode H264 Quicktime files that are compatible with
Apple's Quicktime Player (should not be too much to ask, right?). Before
2.5, I could do this by tweaking the individual ffmpeg options that were
exposed in the UI after selecting the H264 preset. That preset was
clearly designed for making H264 AVI files, but it would work for
Quicktime after changing the container format and tweaking ffmpeg
options, especially getting rid of "flags:loop".

2.5 doesn't expose those options in the UI. They seem to be hardcoded in
source/blender/blenkernel/intern/writeffmpeg.c under case
FFMPEG_PRESET_H264. They mirror the options in libx264-default.preset
that is distributed with ffmpeg. So I'm editing the settings in
writeffmpeg.c to see if I can get Blender to write a QT
Player-compatible Quicktime movie. No matter what I do to those
settings, Blender's stderr stream shows that it is still using the
defaults, not the settings I modified.

The settings seem to be stored in a RenderData->ffcodecdata.properties,
but I get lost (I'm not a programmer) as I try to figure out where they
come from, since they obviously don't come from the FFMPEG_PRESET_H264
settings I edited. Any help?

Thanks,
Randall

p.s.: Please don't suggest rendering an image sequence, then encoding
from the command line! That's what I do for 3D renders, but I want to
encode output from the VSE. It seems stupid to render an image sequence
from the VSE, because it would just duplicate the same frames I already
have on disk but with different frame numbers, wasting a lot of disk
space.

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Default for Raytracer Instancing

[Randall Rickert]

When I read the post about instancing being off by default, I was in the
middle of a big project with raytracing and lots of instancing. I can
turn on instancing to save some rendering time, right?

Wrong! Turning on instancing gave me longer render times, and it also
made a small but visible difference in final gather. This is just the
first file I tried rendering with instancing turned on, and I have not
tried with other projects yet. Definitely not a large enough sampling to
draw broad conclusions, but maybe turning it on by default is not such a
simple answer after all.

-Randall

> On 21 January 2011 10:39, Daniel Salazar - 3Developer.com
> wrote:
> 
> > There's an option in the Performance panel in Render Properties called
> > Instances, it allows the raytracer to memory instance all duplis, IMO
> > this option should be on by default (if optional at all) since, from
> > talking to Jaguarandy some time ago, it should not bring any problems
> > or speed increase in any case, to the contrary, the speed and memory
> > usage when using duplis gets much better. Also sadly many people
> > ignore this setting so they don't benefit from it.
> >
> > cheers
> >
> > Daniel Salazar
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >


___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers