I used the track token in folder and file names, otherwise one element
would have overwritten the other upon export.
In your export template there doesn't seem to be any differentiation to
ensure multiple items for the same shot don't overwrite each other. not
sure if that is what is going on,
Thanks Frank,
Yes, that's what I'm seeing too - tracks are included in the nuke script
but not in the copy exporter.
Unless you use 'separate comps' option, which will create a comp and also
copy the track files as expected.
Cheers
Mat
On Tue, 30 Jun 2015 at 12:08 pm, Frank Rueter|OHUfx
Hi Mat,
I just did a test with three track items with the same name on different
tracks (same timing in the timeline), and using collate shot names
produced a nuke script with all three elements (see attached).
Is that not working for you?
The copy exporter however only seems to export one
Hi Frank,
I can get this to work if I'm using the 'separate comp' option but not if
it's a single comp across all the tracks - I'm using the {track} token and
don't seem to be getting any errors.
No matter how I select things, using 'all tacks' or checking each track, I
still only get the one
I see. That sounds like a bug worth reporting to me.
On 30/06/15 14:43, Mat McCosker wrote:
Thanks Frank,
Yes, that's what I'm seeing too - tracks are included in the nuke
script but not in the copy exporter.
Unless you use 'separate comps' option, which will create a comp and
also copy
Hi Frank,
I'm still struggling to get this to work.
Where in your export structure did you use the {track} token ?
I've tried many many variations and seem to get just as many varied results.
Often I get this error
tuple index out of range
which, while appealing in a surreal kind of way, is
Hi Frank
Did you find a solution to this ? I've just conformed from an xml where the
editor has left clips on mulitple tracks and I need all those tracks as
seperate inputs in my comp.
Any solutions yet ?
thanks
Phill
On Mon, Jun 15, 2015 at 7:21 AM, Frank Rueter|OHUfx fr...@ohufx.com
yeah, it did work as expected after a (involuntary) restart.
I used track tokens to pick up the name of the respective track name
during export.
You may need to use collate shot names if the track items share the
sane shot name, or collate shot timings if the track items share the
same
I did
On 15/06/15 07:24, Lucien Fostier wrote:
Hey Franck,
why dont u try create comp (special)?
Seems like what your looking for.
cheers
Lucien
Sent from my iPhone
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk,
Hey Franck,
why dont u try create comp (special)?
Seems like what your looking for.
cheers
Lucien
Sent from my iPhone
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
Hi,
I just tried to create a comp in NukeStudio for a shot that has multiple
track items (BG and FG). The tracks live above each other in the
timeline and have the same shot name. I was hoping that creating comp
with both selected would bring them both into the resulting Nuke script,
but it
hm. NukeStudio crashed on me, and when it came back up it did bring in
the extra tracks. In fact it brought in all active track items even
though I explicitly only had two tracks active in the export template.
Will keep poking it...
On 14/06/15 2:49 pm, Frank Rueter|OHUfx wrote:
Hi,
I just
12 matches
Mail list logo
