As would DNxHD. The 6.3v6 release notes mentioned it being blacklisted.

On Fri, Jun 8, 2012 at 2:46 AM, johannes amorosa <
[email protected]> wrote:

> x264 4:4:4 lossless support would be great.
>
>
> On 7 June 2012 17:10, ArnoB <[email protected]> wrote:
>
>> Heya
>>
>> I had a short conversation with Support recently about
>> ffmpeg and why I couldn't get it to work.
>> Even the pre-compiled version that comes with the Linux
>> release doesn't work for me.
>>
>> It's indeed using old sources and doesn't support many
>> of the codecs any current release of ffmpeg does.
>>
>> One thing they said though is that with the next major
>> release they'll include an updated ffmpeg reader/writer
>> compiled against the latest ffmpeg libs.
>>
>> gr
>> Arno
>>
>>
>> On 7 jun 2012, at 13:47, Adrian Baltowski wrote:
>>
>> Hi
>>
>>  Sorry, but I missed that Windows is a center of your question. I'm not
>> on Windows at all so i can't help... :(
>> But generally: ffmpegWriter and Reader in Nuke (and the sources included
>> in NDK) are based on very old ffmpeg libraries and on an old API. You
>> cannot compile it against current ffmpeg libraries. The code have to be
>> modify.
>> But even than keep in mind, that those plugins's implementation in Nuke
>> is quite limited and very simplified. There is no acces to advanced codecs
>> settings, no timecode support, no audio support, no respects for
>> colorspaces, support for 8 bit RGB pixel format only etc, etc. To bring
>> full functionality of modern ffmpeg libraries into the Nuke, those plugins
>> have to be developed almost from scratch. To do that you need to be
>> familiar not only with C/CPP language but also with ffmpeg API, altogether
>> with it's weirdness and traps. I did it for ffmpegReader but not for Writer
>> yet. It's on my long "to do" list.
>>
>>
>> Best
>> Adrian
>>
>>
>>
>> W dniu 2012-06-07 08:39:19 użytkownik Dan Walker <[email protected]>
>> napisał:
>>
>> Hey Jimmy,
>>
>> There is ProRes support in ffmpeg.
>>
>> -D
>>
>> On Wed, Jun 6, 2012 at 10:52 PM, Jimmy Christensen <[email protected]>wrote:
>>
>>> Would be really nice if Foundry would precompile the ffmpegwriter for
>>> Windows and with an updated libavcodec. Then we would have ProRes support
>>> in Windows too :)
>>>
>>>
>>> Best Regards
>>> Jimmy Christensen
>>> Developer
>>> Ghost A/S
>>>
>>> On 07/06/12 06:47, Deke Kincaid wrote:
>>>
>>>> Dan
>>>>
>>>> At the time of that comment (2008 or 2009). It wasn't that the Foundry
>>>> didn't have access to x64 version of Windows. The issue was that at
>>>> that time the ffmpeg source code was only 32 bit and they hadn't created
>>>> a 64 bit version yet.
>>>>
>>>> -deke
>>>>
>>>> On Jun 6, 2012, at 19:53, Dan Walker <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>>
>>>>  Hey,
>>>>>
>>>>> Thanks Adrian. Although this didn't quiet answer my post, I
>>>>> appreciate your feedback. What I'm blatantly asking the Community is,
>>>>> if you've successfully compiled the Nuke supplied ffmpegWriter and or
>>>>> ffmpegReader or any variation of this code and it's working on
>>>>> Windows7 Pro in Nuke6.3v+ and your interaction with the compiled
>>>>> plugin via Nuke's Write node looks like the screen grab Jimmy so
>>>>> kindly offered up, then "How did you accomplish this?".
>>>>>
>>>>> I'm told that I could install Visual Studio 2005 Win7 SP1 and the
>>>>> update for Vista/Win7, but I'm no C programmer and I'd really hate to
>>>>> waste more time thinking, by installing this and compiling, I'm all
>>>>> set. I've read over and over on others multiple attempts at compiling
>>>>> this on Windows and it not working. Although I have read that
>>>>> compiling on Linux is easy peasy and the ones who are fortunate enough
>>>>> to be on Linux also get this pre-compiled for use. The foundry's
>>>>> excuse for Windows is that they don't have access to Windows x64 (only
>>>>> 32) which leads me to think, how the hell did they compile Nuke6.3v7
>>>>> 64bit? Hmmm, maybe that was an old posting from Matt at the Foundry (
>>>>> sorry Matt ). Again, I'm not a C programmer so if I sound like I
>>>>> don't know what I'm talkin about, there's my excuse.
>>>>>
>>>>> This isn't something proprietary, the code is there! All I'm
>>>>> searching for are the steps, compilers used, things to watch out for,
>>>>> etc... One would think with the amount of data on the internet,
>>>>> someone somewhere would have posted something.
>>>>>
>>>>> Sorry for coming off a bit terse but I've been researching this a
>>>>> little to long now.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Dan
>>>>>
>>>>> On Wed, Jun 6, 2012 at 4:00 PM, Adrian Baltowski
>>>>>  <[email protected] <mailto:[email protected]. 
>>>>> pl<[email protected]>>>
>>>>> wrote:
>>>>>
>>>>> Hi
>>>>> We need to creates tons of previews and send them to clients. So I
>>>>> wrote mpeg writer based on ffmpeg libraries and we are using it
>>>>> all the time. It is preseted for instance to create "mail-mpeg
>>>>> with audio" so artists don't need to worry about any format
>>>>> settings; just create mail-mpegWriter, set output path, choice
>>>>> audio file and click render- don't care about anything else.
>>>>> From my practice it's much better to have separate writers for
>>>>> different formats. I strongly recommend this way even if your
>>>>> plugins's code is almost the same. It's better and in the long
>>>>> term even simpler than multi-format writer.
>>>>> Best
>>>>> Adrian
>>>>> W dniu 2012-06-06 08:52:55 użytkownik Dan Walker
>>>>> <[email protected] <mailto:[email protected]>> napisał:
>>>>>
>>>>>
>>>>> Hi all,
>>>>> Wanted to know if anyone has compiled the ffmpegWriter and if
>>>>> so, do you have type of info on how you're using it? Like, if
>>>>> the plugin is selected in a Write node, what type of
>>>>> attributes are associated? Does it function like the
>>>>> "advanced settings" for movie formats, etc...
>>>>> If you have successfully compiled this and you're using it,
>>>>> would love to get a few screen grabs too.
>>>>> Wanting to see how it's implemented before delving into it and
>>>>> possibly extending it.
>>>>> Thanks much!!!
>>>>> -Dan
>>>>>
>>>>>
>>>>> ______________________________ _________________
>>>>> Nuke-python mailing list
>>>>> Nuke-python@support. 
>>>>> thefoundry.co.uk<[email protected]>
>>>>> <mailto:Nuke-python@support. 
>>>>> thefoundry.co.uk<[email protected]>>,
>>>>>
>>>>>
>>>>> http://forums.thefoundry.co. uk/ <http://forums.thefoundry.co.uk/>
>>>>> http://support.thefoundry.co. uk/cgi-bin/mailman/listinfo/ 
>>>>> nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python>
>>>>>
>>>>>
>>>>> ______________________________ _________________
>>>>> Nuke-python mailing list
>>>>> Nuke-python@support. 
>>>>> thefoundry.co.uk<[email protected]>
>>>>> <mailto:Nuke-python@support. 
>>>>> thefoundry.co.uk<[email protected]>
>>>>> >,
>>>>> http://forums.thefoundry.co. uk/ <http://forums.thefoundry.co.uk/>
>>>>> http://support.thefoundry.co. uk/cgi-bin/mailman/listinfo/ 
>>>>> nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python>
>>>>>
>>>>
>>>>
>>>> ______________________________ _________________
>>>> Nuke-python mailing list
>>>> Nuke-python@support. 
>>>> thefoundry.co.uk<[email protected]>,
>>>> http://forums.thefoundry.co. uk/ <http://forums.thefoundry.co.uk/>
>>>> http://support.thefoundry.co. uk/cgi-bin/mailman/listinfo/ 
>>>> nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python>
>>>>
>>>>  ______________________________ _________________
>>> Nuke-python mailing list
>>> Nuke-python@support. thefoundry.co.uk<[email protected]>,
>>> http://forums.thefoundry.co. uk/ <http://forums.thefoundry.co.uk/>
>>> http://support.thefoundry.co. uk/cgi-bin/mailman/listinfo/ 
>>> nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python>
>>>
>>
>> _______________________________________________
>> Nuke-python mailing list
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>>
>>
>>
>> _______________________________________________
>> Nuke-python mailing list
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>>
>>
>
>
> _______________________________________________
> Nuke-python mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
>
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python

Reply via email to