On Tue, Aug 6, 2013 at 1:00 AM, Alar Sing <alar.s...@err.ee> wrote: > Hello, > > I'm testing melt for internet broacasting. > My setup is that i have decklink sdi card for live broadcast input and > multiple h264 outputs for different screen sizes. > Everything is fine when I one consumer: > > melt -profile square_pal_wide consumer:decklink: profile=dv_pal_wide > -consumer avformat:rtmp://host/live/test properties=err/x264-medium-main > > Sample picture from output > http://londiste.etv.ee/users/arclyde/melt-normal.PNG > > But if I dry to use more than one consumer then there is problem: my wide > screen input is compresse to 4:3 > > melt -profile square_pal_wide consumer:decklink: profile=dv_pal_wide > -consumer avformat:rtmp://host/live/testm > properties=err/x264-medium-baseline -consumer avformat:rtmp://host/live/test > properties=err/x264-medium-main > > Sample picture from output > http://londiste.etv.ee/users/arclyde/melt-broken.PNG
I found a bug and pushed a fix for it into git. Are in a position to build MLT yourself? > Profiles are from mlt source. > My properties for baseline > http://londiste.etv.ee/users/arclyde/x264-medium-baseline > My properties for main http://londiste.etv.ee/users/arclyde/x264-medium-main > > There is documentation for using consumer multi ( > http://www.mltframework.org/bin/view/MLT/ConsumerMulti ) I see some of the documentation is not properly escaped for HTML. I need to improve my script that generates these pages. You can also view it with "melt -query consumer=multi". > melt -profile square_pal_wide consumer:decklink: profile=dv_pal_wide > -consumer multi 0=avformat:rtmp://host/live/testm > 0.properties=err/x264-medium-baseline 1=avformat:rtmp://host/live/test > 1.properties=err/x264-medium-main > > But this gives error: *** Error in `melt': double free or corruption > (!prev): 0x00007f52d006c0e0 *** I think the problem here is that the preset failed to load, then encoding setup was rejected by libavcodec, and it failed miserably. When you try to refer to a preset from the installation path, then there is some "lookup magic" that might not be working here. Also, the documentation "You can put these into a MLT properties file and supply that to this consumer." is a little confusing or misleading. It means that if you know the MLT properties file syntax, you can put all of these options into a text file and supply that text file name as an argument to the multi consumer. For example: $ melt ... -consumer multi:my.properties where my.properties contains something like: 0=decklink .mlt_profile=atsc_1080i_50 .buffer=50 .prefill=1 1=sdl .mlt_profile=quarter_pal .buffer=50 .prefill=1 or as a YAML file: - mlt_service: decklink mlt_profile: atsc_1080i_5994 buffer: 3 - mlt_service: sdl mlt_profile: quarter_ntsc - mlt_service: avformat target: test.dv mlt_profile: dv_ntsc properties: DV -- +-DRD-+ ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
