Yes, I commented it out and modified the Makefile (to point to the FFMPEG
headers and libs) and it works (more than) fine! A FFMEG reader node is SOO
powerful!
-----Original Message-----
From: "Jimmy Christensen" <[email protected]>
Sent: Monday, June 23, 2014 3:13pm
To: "Nuke plug-in development discussion" <[email protected]>
Subject: Re: [Nuke-dev] Reader Extension Registration
Well, to be honest I cannot comment on wether or not the NDK is changed.
Just that the ffmpegReader compiled has changed however not the example
code.
Where did you get the blacklist.h from? Or did you comment it out?
Hilsen
Jimmy Christensen
Developer
Ghost A/S
On 23/06/14 21:11, Jimmy Christensen wrote:
> Yes. I opened a ticket on it earlier and they confirmed that the example
> is not updated to the 8.0 version compiled/shipped.
>
> They mentioned that they might update it in next big release.
>
> Hilsen
> Jimmy Christensen
> Developer
> Ghost A/S
>
> On 23/06/14 19:40, Vincent Olivier wrote:
>> Nuke 8.0v5
>>
>> Are there significant changes in the NDK that were not ported to the
>> ffmpegReader.cpp example?
>>
>> Thanks!
>>
>> On Jun 23, 2014, at 2:43 AM, Jimmy Christensen <[email protected]> wrote:
>>
>> > Just a bit curious. Which version of nuke was this for? AFAIK the
>> nuke8 ffmpegReader example is still based on Nuke7. > > Hilsen > Jimmy
>> Christensen > Developer > Ghost A/S > > On 22/06/14 00:20, Vincent
>> Olivier wrote: >> Hi, >> >> Starting from “ffmpegReader.cpp” which
>> compiles and installs fine, I >> want to register additional file
>> extension (“mxf”, for instance). >> >> >> Changing the original line >>
>> >> const Reader::Description ffmpegReader::d("ffmpeg\0", build, test);
>> >> >> to >> >> const Reader::Description
>> ffmpegReader::d("ffmpeg\0mxf\0", build, test); >> >> doesn’t work (no
>> plugin named “mxfReader” found). >> >> Renaming the file “ffmpegReader”
>> to “mxfReader” works but is cumbersome. >> >> Is the description method
>> broken or am I doing something wrong? >> >> Regards, >> >> Vincent >> >>
>> >> _______________________________________________ >> Nuke-dev mailing
>> list >> [email protected],
>> http://forums.thefoundry.co.uk/
>> <http://tracker.up4.com/track/click.php?u=30239142&id=fcb1879b77344371b79a346059b10fc6&url=http%3A%2F%2Fforums.thefoundry.co.uk%2F&url_id=84bf64b7d568b18806d5e0df3f2dbb1bb7ca3789>
>>
>> >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>> <http://tracker.up4.com/track/click.php?u=30239142&id=fcb1879b77344371b79a346059b10fc6&url=http%3A%2F%2Fsupport.thefoundry.co.uk%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnuke-dev&url_id=9cb3c1479c1cdaec096bec3971a6168ef510bad0>
>>
>> >> > _______________________________________________ > Nuke-dev mailing
>> list > [email protected],
>> http://forums.thefoundry.co.uk/
>> <http://tracker.up4.com/track/click.php?u=30239142&id=fcb1879b77344371b79a346059b10fc6&url=http%3A%2F%2Fforums.thefoundry.co.uk%2F&url_id=84bf64b7d568b18806d5e0df3f2dbb1bb7ca3789>
>>
>> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>> <http://tracker.up4.com/track/click.php?u=30239142&id=fcb1879b77344371b79a346059b10fc6&url=http%3A%2F%2Fsupport.thefoundry.co.uk%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnuke-dev&url_id=9cb3c1479c1cdaec096bec3971a6168ef510bad0>
>>
>>
>>
>>
>> _______________________________________________
>> Nuke-dev mailing list
>> [email protected], http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>>
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
