<div dir="ltr"><div>That's amazing, Julian! I did not know that Mike Pan had continued my proposal.<br></div><div>I'm glad I was able to kick things off. At this point, everyone involved is probably more qualified to work on this than I am, but if there's any any for me to contribute further, please let me know.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 27, 2015 at 3:43 PM, Julian Eisel <span dir="ltr"><<a href="mailto:eiseljulian@gmail.com" target="_blank">eiseljulian@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey there,<br>
<br>
Just wanted to mention that the Output/Encoding panel refactor (based<br>
on Mike's drafts) is still on my track. I would like to take some time<br>
to understand the encoding workflow a bit better which I wasn't able<br>
to find yet. So just in case anyone wonders what happend to it: I hope<br>
to get it done soon.<br>
<br>
Cheers,<br>
- Julian -<br>
<div><div class="h5"><br>
On Fri, Mar 20, 2015 at 10:22 PM, Sam Brubaker <<a href="mailto:sam@worldsday.org">sam@worldsday.org</a>> wrote:<br>
> Hi, Interface team! Since posting my proposal on how to fix Blender's output<br>
> encoding interface, I've received some helpful and interesting feedback.<br>
><br>
> I like Mike Pan's suggestion about placing the container menu under the<br>
> output panel instead of the video encoding panel. I also agree that bit<br>
> rates should be expressed in kilobits or megabits instead of bits.<br>
><br>
> Sobotka said some stuff about the encoding requirements of small studios<br>
> that was over my head, but it sounds great, too. I think it was mentioned<br>
> earlier, but I like the idea of narrowing the supported codecs to the most<br>
> useful intermediate codecs for studio pipelines, along with a few common<br>
> lossy codecs for dailies and lazy web posts.<br>
><br>
> This proposal doesn't call for any major paradigm shifts, and it's not some<br>
> ground-breaking pinnacle of UI philosophy. I think it can be addressed as a<br>
> discrete component of Blender without interfering with the UI team's grander<br>
> machinations. Anything would be better than the existing panel layout.<br>
><br>
> What else can you guys add to this discussion?<br>
><br>
</div></div>> _______________________________________________<br>
> Bf-interface mailing list<br>
> <a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-interface" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
><br>
_______________________________________________<br>
Bf-interface mailing list<br>
<a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-interface" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
</blockquote></div><br></div>