Yes, you're right Ean. I mentioned the "multiple formats" case because the debate originated from why would changing the order in formats.tcl make a difference. But sure, if there's more than one format with the same res, it'll match the first one; and if there's only one, it'll match that one, of course.
I suppose a better statement would be: "yes, formats already defined in the list of formats DO have an effect on the Read's pixel_aspect when pixel_aspect can't be recovered from the metadata" Thanks for pointing it out, though. Have a good weekend! Ivan 2011/6/24 Ean Carr <eanc...@gmail.com> > Hey Ivan, > > Doesn't have to be more than one format... just one will do. Try a test: > > 1. Write out a file without pixel_aspect in the header, like SGI with the > format: 20x20 5 > 2. In a new Nuke instance, read that in. It's square; Nuke has no way of > knowing it had a pixel_aspect of 5.0. > 3. In a new Nuke instance, create a format in the root: 20x20 5 (you don't > need to set it as the root format, just define it). > 4. Read the same file back in and Nuke matches it to that format, > pixel_aspect included. > > -E > > Read thg > > > 2011/6/23 Ivan Busquets <ivanbusqu...@gmail.com> > >> Formats.tcl file has nothing to do with Reader's aspect ratio. >>> >> >> It does when there's more than one format defined with the same >> resolution, and the file does not contain metadata of its pixel aspect. >> >> In that case, Nuke will set the format of the Read to the first format in >> the list that matches the file's resolution, with whatever pixel aspect is >> defined in that format. >> >> >> On Thu, Jun 23, 2011 at 1:50 PM, Adrian Baltowski < >> adrian...@poczta.onet.pl> wrote: >> >>> Hey >>> >>> Formats.tcl file has nothing to do with Reader's aspect ratio. This is >>> only list of names of formats in Nuke, created for users convenience. >>> Reader set up format based on info about resolution and aspect ratio of >>> file. Then Nuke compares the format with the formats.tcl and if format has a >>> name, Nuke uses this name. Thats all. >>> If you remove standard PAL (1.09) format from the list, Nuke will create >>> new unnamed format. >>> >>> I guess that you have problem with quicktime files. The actual problem is >>> inside movReader in Nuke, which in some cases can't read out actual aspect >>> ratio from quicktime file. Its worth to say, that sometimes this information >>> is not saved in mov files. >>> >>> Best >>> Adrian >>> >>> W dniu 2011-06-23 21:43:45 użytkownik Deke Kincaid < >>> dekekinc...@gmail.com> napisał: >>> >>> I suggest you don't edit the files in your application directory. Copy >>> it to your .nuke or wherever you NUKE_PATH is and edit it there. >>> >>> -deke >>> >>> On Thu, Jun 23, 2011 at 15:25, Ned Wilson <ned.wil...@scanlinevfx.com>wrote: >>> >>>> >>>> As an alternative, edit formats.tcl. >>>> >>>> On windows machines, you will find this here: >>>> >>>> C:Program FilesNuke6.2v4pluginsformats.tcl >>>> >>>> >>>> On Mac, here: >>>> >>>> /Applications/Nuke6.2v4/Nuke6.2v4.app/Contents/MacOS/plugins/formats.tcl >>>> ( This is from memory, I don't have a Mac in front of me ) >>>> >>>> Inside this file you will notice that 16:9 video formats are listed >>>> after 4:3 video formats. Simply cut the 16:9 formats and paste them before >>>> the 4:3 ones. Then, Nuke will default to the 16:9 version for both NTSC and >>>> PAL. >>>> >>>> >>>> >>>> >>>> On 6/23/2011 8:42 AM, Ean Carr wrote: >>>> >>>> Hey Donat, >>>> >>>> Just edit the built-in PAL format to a different pixel aspect and Read >>>> nodes will match images that match the PAL resolution to that format. >>>> >>>> Edit > Project Settings... >>>> >>>> Change PAL from 1.09 to whatever you want. >>>> >>>> -E >>>> >>>> On Thu, Jun 23, 2011 at 2:35 PM, Donat Van Bellinghen < >>>> donat.l...@gmail.com> wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> Is there a way to change the default pixel aspect ratio for read nodes. >>>>> We use PAL Anamorphic footage a lot and when I drop some footage in Nuke >>>>> the >>>>> Read node is set to a standard PAL pixel aspect ratio. >>>>> >>>>> I hope there's a solution for this. >>>>> >>>>> Regards. >>>>> >>>>> Donat Van Bellinghen >>>>> www.nozon.com >>>>> _______________________________________________ >>>>> Nuke-users mailing list >>>>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Nuke-users mailing listnuke-us...@support.thefoundry.co.uk, >>>> http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>>> >>>> >>>> _______________________________________________ >>>> Nuke-users mailing list >>>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>>> >>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> >> >> >> _______________________________________________ >> Nuke-users mailing list >> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> > > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
