On Sat, Sep 29, 2012 at 5:32 PM, Markus Kienast <elias1...@gmail.com> wrote: > I am trying to downscale a 1080i50 SDI input on decklink:3 to PAL SDI output > on decklink:0 directly with melt. > > Which is exactly, what I have done here successfully with the Ruby bindings: > https://gist.github.com/3805493 > > However, I seem to not get the command line right! > > That's what I had: melt -profile atsc_1080i_50 decklink:3 -consumer > decklink:0 mlt_profile=dv_pal_wide
You have not actually used 2 different profiles. -profile and mlt_profile= are fighting to be the chosen profile, and I believe mlt_profile= wins, but it is rather arbitrary. This is because these are both ways to set _the_ profile as described here: http://www.mltframework.org/bin/view/MLT/Profiles Now, what you need is an encapsulation mechanism - a way to encapsulate one service network within another. There is a special producer named "consumer" that does this: http://www.mltframework.org/bin/view/MLT/ProducerConsumer melt -profile dv_pal_wide consumer:decklink:3 profile=atsc_1080i_50 -consumer decklink:0 It actually builds a separate service network within the producer by acting as its consumer, and you can give the encapsulated network a distinct profile. > Please advise, > Markus -- +-DRD-+ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
