Re: AW: AW: [Nuke-users] Alexa Artifacts

[Diogo Girondi]

Out of curiosity at what ISO most of these images were shot?

We've been having some problems here and I'm starting to think it has
something to do with ISO 800 while trying to get the best of both worlds.
I'll try to get an ALEXA one of these days to run some tests.


On Fri, Mar 29, 2013 at 5:40 PM, Simon Blackledge <
simon.blackle...@spacedigital.co.uk> wrote:

> Have some recent prores 1080 files here shot greenscreen.
>
> If ya post a script here that shows the issue ill try it on my clips.
>
> I have seen dancing pixels also. All over the place but it tends to be
> clips shot later in the day. Not ideal either.
>
> Maybe anyone going to NAB could go see Arri? :)
>
> S
>
>
> Sent from my iPhone
>
> On 29 Mar 2013, at 20:06, Howard Jones  wrote:
>
> The shots I had looked like compression and had jpeg edges in the blocks
> rather than the pattern I'd get with resizing.
> Also seemed mostly in the green. However it was large blocks.
>
> Not to say it's not resizing but nothing like the artifacts Nuke would
> produce.
>
>
> Howard
>
>   --
> *From:* Ivan Busquets 
> *To:* Howard Jones ; Nuke user discussion <
> nuke-users@support.thefoundry.co.uk>
> *Sent:* Friday, 29 March 2013, 19:37
> *Subject:* Re: AW: AW: [Nuke-users] Alexa Artifacts
>
> I'm with Jonathan in that this looks like a resizing filter.
>
> You said it's most obvious on even backgrounds. To me that's yet another
> sign that it's a resizing artifact.
>
> What resolution are your source files? I don't know the specific details,
> but I believe you can only get 1920x1080 ProRes quicktimes from the Alexa
> (or 2K in newer firmwares).
> The Alexa sensor being 2880x1620, there has to be some kind of
> downsampling.
>
>
>
>
> On Fri, Mar 29, 2013 at 9:43 AM, Howard Jones wrote:
>
> It was the same here - shot directly in ProRes 444.
> No idea what though
>
>
> Howard
>
>   --
> *From:* Igor Majdandzic 
> *To:* 'Nuke user discussion' 
> *Sent:* Friday, 29 March 2013, 16:29
> *Subject:* AW: AW: [Nuke-users] Alexa Artifacts
>
> Do you know what caused them?
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [mailto:
> nuke-users-boun...@support.thefoundry.co.uk] *Im Auftrag von *Magno Borgo
> *Gesendet:* Freitag, 29. März 2013 14:06
> *An:* Nuke user discussion
> *Betreff:* Re: AW: [Nuke-users] Alexa Artifacts
>
> I've seen the exactly same artifacts when working on a film shot on Alexa.
> These are nasty specially when keying... same issue, shot directly in
> Proress .
>
> Magno.
>
>
>
>
> We've been having some problems with noise on some footages from Alexa,
> but nothing remotely near to that.
>
> diogo
>
> On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad 
> wrote:
> No idea, but it looks an awful lot like filtering from a slight resize
> operation.
>
> -jonathan
>
> On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic" 
> wrote:
>
> do you mean in camera? because that was from the original qt footage
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [mailto:
> nuke-users-boun...@support.thefoundry.co.uk] *Im Auftrag von *Jonathan
> Egstad
> *Gesendet:* Donnerstag, 28. März 2013 01:10
> *An:* Nuke user discussion
> *Cc:* Nuke user discussion
> *Betreff:* Re: [Nuke-users] Alexa Artifacts
>
> Looks like a very  slight resize was done.
> -jonathan
>
> On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic" 
> wrote:
>
> Hey guys,
> we got footage from a shoot with Alexa being the camera. It was shot in
> ProRess 444. The problem is: The picture has some artifacts which confuse
> me the codec being 444. I attached some images which show some of the grain
> patterns. Is this normal?
>
> thx,
> Igor
>
>
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [
> mailto:nuke-users-boun...@support.thefoundry.co.uk]
> *Im Auftrag von *Deke Kincaid
> *Gesendet:* Mittwoch, 27. März 2013 23:47
> *An:* Nuke user discussion
> *Betreff:* Re: [Nuke-users] FusionI/O and Nuke
>
> Hi Michael
> I'm actually testing this right now as Fusionio just gave us a bunch of
> them.  Early tests reveal that with dpx it's awesome but with openexr zip
> compressed file it it is spending more

Re: AW: AW: [Nuke-users] Alexa Artifacts

[Simon Blackledge]

Have some recent prores 1080 files here shot greenscreen.

If ya post a script here that shows the issue ill try it on my clips.

I have seen dancing pixels also. All over the place but it tends to be clips 
shot later in the day. Not ideal either. 

Maybe anyone going to NAB could go see Arri? :)

S


Sent from my iPhone

On 29 Mar 2013, at 20:06, Howard Jones  wrote:

> The shots I had looked like compression and had jpeg edges in the blocks 
> rather than the pattern I'd get with resizing.
> Also seemed mostly in the green. However it was large blocks. 
> 
> Not to say it's not resizing but nothing like the artifacts Nuke would 
> produce.
> 
>  
> Howard
> 
> From: Ivan Busquets 
> To: Howard Jones ; Nuke user discussion 
>  
> Sent: Friday, 29 March 2013, 19:37
> Subject: Re: AW: AW: [Nuke-users] Alexa Artifacts
> 
> I'm with Jonathan in that this looks like a resizing filter.
> 
> You said it's most obvious on even backgrounds. To me that's yet another sign 
> that it's a resizing artifact.
> 
> What resolution are your source files? I don't know the specific details, but 
> I believe you can only get 1920x1080 ProRes quicktimes from the Alexa (or 2K 
> in newer firmwares).
> The Alexa sensor being 2880x1620, there has to be some kind of downsampling.
> 
> 
> 
> 
> On Fri, Mar 29, 2013 at 9:43 AM, Howard Jones  wrote:
> It was the same here - shot directly in ProRes 444.
> No idea what though
> 
>  
> Howard
> 
> From: Igor Majdandzic 
> To: 'Nuke user discussion'  
> Sent: Friday, 29 March 2013, 16:29
> Subject: AW: AW: [Nuke-users] Alexa Artifacts
> 
> Do you know what caused them?
>  
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>  
> Von: nuke-users-boun...@support.thefoundry.co.uk 
> [mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Magno 
> Borgo
> Gesendet: Freitag, 29. März 2013 14:06
> An: Nuke user discussion
> Betreff: Re: AW: [Nuke-users] Alexa Artifacts
>  
> I've seen the exactly same artifacts when working on a film shot on Alexa. 
> These are nasty specially when keying... same issue, shot directly in Proress 
> .
>  
> Magno.
>  
>  
>  
> We've been having some problems with noise on some footages from Alexa, but 
> nothing remotely near to that.
>  
> diogo
>  
> On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad  
> wrote:
> No idea, but it looks an awful lot like filtering from a slight resize 
> operation.
>  
> -jonathan
> 
> On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic"  
> wrote:
> do you mean in camera? because that was from the original qt footage
>  
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>  
> Von: nuke-users-boun...@support.thefoundry.co.uk 
> [mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan 
> Egstad
> Gesendet: Donnerstag, 28. März 2013 01:10
> An: Nuke user discussion
> Cc: Nuke user discussion
> Betreff: Re: [Nuke-users] Alexa Artifacts
>  
> Looks like a very  slight resize was done.
> -jonathan
> 
> On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic"  
> wrote:
> Hey guys,
> we got footage from a shoot with Alexa being the camera. It was shot in 
> ProRess 444. The problem is: The picture has some artifacts which confuse me 
> the codec being 444. I attached some images which show some of the grain 
> patterns. Is this normal?
>  
> thx,
> Igor
>  
>  
>  
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>  
> Von: nuke-users-boun...@support.thefoundry.co.uk 
> [mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Deke 
> Kincaid
> Gesendet: Mittwoch, 27. März 2013 23:47
> An: Nuke user discussion
> Betreff: Re: [Nuke-users] FusionI/O and Nuke
>  
> Hi Michael
> I'm actually testing this right now as Fusionio just gave us a bunch of them. 
>  Early tests reveal that with dpx it's awesome but with openexr zip 
> compressed file it it is spending more time with compression, not sure if it 
> is cpu bound or what(needs more study but its slower).  Openexr uncompressed 
> files though are considerably superfast but of course the issue is that it is 
> 18 meg a frame.  These are single layer rgba exr files.
> 
> -
> Deke Kincaid
> Creative Specialist
> The Foundry
> Mobile: (310) 883 4313
> Tel: (310) 399 4555 - Fax: (310) 450 4516
> 
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>  
> On Wed, Mar 27, 2013 at 3:26 PM, Michae

Re: AW: AW: [Nuke-users] Alexa Artifacts

[Howard Jones]

The shots I had looked like compression and had jpeg edges in the blocks rather 
than the pattern I'd get with resizing.
Also seemed mostly in the green. However it was large blocks. 

Not to say it's not resizing but nothing like the artifacts Nuke would produce.


 
Howard



>
> From: Ivan Busquets 
>To: Howard Jones ; Nuke user discussion 
> 
>Sent: Friday, 29 March 2013, 19:37
>Subject: Re: AW: AW: [Nuke-users] Alexa Artifacts
> 
>
>I'm with Jonathan in that this looks like a resizing filter.
>
>
>You said it's most obvious on even backgrounds. To me that's yet another sign 
>that it's a resizing artifact.
>
>
>What resolution are your source files? I don't know the specific details, but 
>I believe you can only get 1920x1080 ProRes quicktimes from the Alexa (or 2K 
>in newer firmwares).
>The Alexa sensor being 2880x1620, there has to be some kind of downsampling.
>
>
>
>
>
>
>
>On Fri, Mar 29, 2013 at 9:43 AM, Howard Jones  wrote:
>
>It was the same here - shot directly in ProRes 444.
>>No idea what though
>>
>>
>>
>> 
>>Howard
>>
>>
>>
>>>
>>> From: Igor Majdandzic 
>>>To: 'Nuke user discussion'  
>>>Sent: Friday, 29 March 2013, 16:29
>>>Subject: AW: AW: [Nuke-users] Alexa Artifacts
>>> 
>>>
>>>
>>>Do you know what caused them?
>>> 
>>>-- 
>>>igor majdandzic
>>>compositor |
>>>i...@badgerfx.com
>>>BadgerFX | www.badgerfx.com
>>> 
>>>Von:nuke-users-boun...@support.thefoundry.co.uk 
>>>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Magno 
>>>Borgo
>>>Gesendet: Freitag, 29. März 2013 14:06
>>>An: Nuke user discussion
>>>Betreff: Re: AW: [Nuke-users] Alexa Artifacts
>>> 
>>>I've seen the exactly same artifacts when working on a film shot on Alexa. 
>>>These are nasty specially when keying... same issue, shot directly in 
>>>Proress .
>>> 
>>>Magno.
>>> 
>>> 
>>> 
>>>We've been having some problems with noise on some footages from Alexa, but 
>>>nothing remotely near to that.
>>>> 
>>>>diogo
>>>> 
>>>>On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad  
>>>>wrote:
>>>>No idea, but it looks an awful lot like filtering from a slight resize 
>>>>operation.
>>>> 
>>>>-jonathan
>>>>
>>>>On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic"  
>>>>wrote:
>>>>do you mean in camera? because that was from the original qt footage
>>>>> 
>>>>>-- 
>>>>>igor majdandzic
>>>>>compositor |
>>>>>i...@badgerfx.com
>>>>>BadgerFX | www.badgerfx.com
>>>>> 
>>>>>Von:nuke-users-boun...@support.thefoundry.co.uk 
>>>>>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von 
>>>>>Jonathan Egstad
>>>>>Gesendet: Donnerstag, 28. März 2013 01:10
>>>>>An: Nuke user discussion
>>>>>Cc: Nuke user discussion
>>>>>Betreff: Re: [Nuke-users] Alexa Artifacts
>>>>> 
>>>>>Looks like a very  slight resize was done.
>>>>>-jonathan
>>>>>
>>>>>On
 Mar 27, 2013, at 4:56 PM, "Igor Majdandzic"  wrote:
>>>>>Hey guys,
>>>>>>we got footage from a shoot with Alexa being the camera. It was shot in 
>>>>>>ProRess 444. The problem is: The picture has some artifacts which confuse 
>>>>>>me the codec being 444. I attached some images which show some of the 
>>>>>>grain patterns. Is this normal?
>>>>>> 
>>>>>>thx,
>>>>>>    Igor
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>-- 
>>>>>>igor majdandzic
>>>>>>compositor |
>>>>>>i...@badgerfx.com
>>>>>>BadgerFX | www.badgerfx.com
>>>>>> 
>>>>>>Von:nuke-users-boun...@support.thefoundry.co.uk 
>>>>>>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Deke 
>>>>>>Kincaid
>>>>>>Gesendet: Mittwoch, 27. März 2013 23:47
>>>>>>An: Nuke user discussion
>>>>>>Betreff: Re: [Nuke-user

Re: AW: AW: [Nuke-users] Alexa Artifacts

[Ivan Busquets]

I'm with Jonathan in that this looks like a resizing filter.

You said it's most obvious on even backgrounds. To me that's yet another
sign that it's a resizing artifact.

What resolution are your source files? I don't know the specific details,
but I believe you can only get 1920x1080 ProRes quicktimes from the Alexa
(or 2K in newer firmwares).
The Alexa sensor being 2880x1620, there has to be some kind of downsampling.




On Fri, Mar 29, 2013 at 9:43 AM, Howard Jones wrote:

> It was the same here - shot directly in ProRes 444.
> No idea what though
>
>
> Howard
>
>   --
> *From:* Igor Majdandzic 
> *To:* 'Nuke user discussion' 
> *Sent:* Friday, 29 March 2013, 16:29
> *Subject:* AW: AW: [Nuke-users] Alexa Artifacts
>
> Do you know what caused them?
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [mailto:
> nuke-users-boun...@support.thefoundry.co.uk] *Im Auftrag von *Magno Borgo
> *Gesendet:* Freitag, 29. März 2013 14:06
> *An:* Nuke user discussion
> *Betreff:* Re: AW: [Nuke-users] Alexa Artifacts
>
> I've seen the exactly same artifacts when working on a film shot on Alexa.
> These are nasty specially when keying... same issue, shot directly in
> Proress .
>
> Magno.
>
>
>
>
> We've been having some problems with noise on some footages from Alexa,
> but nothing remotely near to that.
>
> diogo
>
> On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad 
> wrote:
> No idea, but it looks an awful lot like filtering from a slight resize
> operation.
>
> -jonathan
>
> On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic" 
> wrote:
>
> do you mean in camera? because that was from the original qt footage
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [mailto:
> nuke-users-boun...@support.thefoundry.co.uk] *Im Auftrag von *Jonathan
> Egstad
> *Gesendet:* Donnerstag, 28. März 2013 01:10
> *An:* Nuke user discussion
> *Cc:* Nuke user discussion
> *Betreff:* Re: [Nuke-users] Alexa Artifacts
>
> Looks like a very  slight resize was done.
> -jonathan
>
> On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic" 
> wrote:
>
> Hey guys,
> we got footage from a shoot with Alexa being the camera. It was shot in
> ProRess 444. The problem is: The picture has some artifacts which confuse
> me the codec being 444. I attached some images which show some of the grain
> patterns. Is this normal?
>
> thx,
> Igor
>
>
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [
> mailto:nuke-users-boun...@support.thefoundry.co.uk]
> *Im Auftrag von *Deke Kincaid
> *Gesendet:* Mittwoch, 27. März 2013 23:47
> *An:* Nuke user discussion
> *Betreff:* Re: [Nuke-users] FusionI/O and Nuke
>
> Hi Michael
> I'm actually testing this right now as Fusionio just gave us a bunch of
> them.  Early tests reveal that with dpx it's awesome but with openexr zip
> compressed file it it is spending more time with compression, not sure if
> it is cpu bound or what(needs more study but its slower).  Openexr
> uncompressed files though are considerably superfast but of course the
> issue is that it is 18 meg a frame.  These are single layer rgba exr files.
>
> -
> Deke Kincaid
> Creative Specialist
> The Foundry
> Mobile: (310) 883 4313
> Tel: (310) 399 4555 - Fax: (310) 450 4516
>
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>
> On Wed, Mar 27, 2013 at 3:26 PM, Michael Garrett 
> wrote:
> I'm evaluating one of these at the moment and am interested to know if
> others have got it working with Nuke nicely, meaning, have you been able to
> really utilise the insane bandwidth of this card to massively accelerate
> any part of your day to day compositing?
>
> So far, I've found it has no benefit when localising all Reads in a
> somewhat heavy comp, or even playing back a sequence of exr's or deep
> files, compared to localised sequences on a 10K Raptor drive also in my
> workstation - hopefully I'm missing something big though, this is day one
> after all.
>
> There may be real tangible benefits to putting the Nuke cache on it though
> - I'll see how it goes.
>
> I'm also guessing that as gpu processing becomes more prevalent in Nuke
> that we will see a real speed advantage handing data from a card like thi

Re: AW: AW: [Nuke-users] Alexa Artifacts

[Marten Blumen]

My tests show that  by itself shouldn't produce these large-block
artefacts

What is the workflow? Are you decoding the QT directly in Nuke or is it
converted in-between. Which platform and quicktime version etc.




On 30 March 2013 05:43, Howard Jones  wrote:

> It was the same here - shot directly in ProRes 444.
> No idea what though
>
>
> Howard
>
>   --
> *From:* Igor Majdandzic 
> *To:* 'Nuke user discussion' 
> *Sent:* Friday, 29 March 2013, 16:29
> *Subject:* AW: AW: [Nuke-users] Alexa Artifacts
>
> Do you know what caused them?
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [mailto:
> nuke-users-boun...@support.thefoundry.co.uk] *Im Auftrag von *Magno Borgo
> *Gesendet:* Freitag, 29. März 2013 14:06
> *An:* Nuke user discussion
> *Betreff:* Re: AW: [Nuke-users] Alexa Artifacts
>
> I've seen the exactly same artifacts when working on a film shot on Alexa.
> These are nasty specially when keying... same issue, shot directly in
> Proress .
>
> Magno.
>
>
>
>
> We've been having some problems with noise on some footages from Alexa,
> but nothing remotely near to that.
>
> diogo
>
> On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad 
> wrote:
> No idea, but it looks an awful lot like filtering from a slight resize
> operation.
>
> -jonathan
>
> On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic" 
> wrote:
>
> do you mean in camera? because that was from the original qt footage
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [mailto:
> nuke-users-boun...@support.thefoundry.co.uk] *Im Auftrag von *Jonathan
> Egstad
> *Gesendet:* Donnerstag, 28. März 2013 01:10
> *An:* Nuke user discussion
> *Cc:* Nuke user discussion
> *Betreff:* Re: [Nuke-users] Alexa Artifacts
>
> Looks like a very  slight resize was done.
> -jonathan
>
> On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic" 
> wrote:
>
> Hey guys,
> we got footage from a shoot with Alexa being the camera. It was shot in
> ProRess 444. The problem is: The picture has some artifacts which confuse
> me the codec being 444. I attached some images which show some of the grain
> patterns. Is this normal?
>
> thx,
> Igor
>
>
>
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>
> *Von:* nuke-users-boun...@support.thefoundry.co.uk [
> mailto:nuke-users-boun...@support.thefoundry.co.uk]
> *Im Auftrag von *Deke Kincaid
> *Gesendet:* Mittwoch, 27. März 2013 23:47
> *An:* Nuke user discussion
> *Betreff:* Re: [Nuke-users] FusionI/O and Nuke
>
> Hi Michael
> I'm actually testing this right now as Fusionio just gave us a bunch of
> them.  Early tests reveal that with dpx it's awesome but with openexr zip
> compressed file it it is spending more time with compression, not sure if
> it is cpu bound or what(needs more study but its slower).  Openexr
> uncompressed files though are considerably superfast but of course the
> issue is that it is 18 meg a frame.  These are single layer rgba exr files.
>
> -
> Deke Kincaid
> Creative Specialist
> The Foundry
> Mobile: (310) 883 4313
> Tel: (310) 399 4555 - Fax: (310) 450 4516
>
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>
> On Wed, Mar 27, 2013 at 3:26 PM, Michael Garrett 
> wrote:
> I'm evaluating one of these at the moment and am interested to know if
> others have got it working with Nuke nicely, meaning, have you been able to
> really utilise the insane bandwidth of this card to massively accelerate
> any part of your day to day compositing?
>
> So far, I've found it has no benefit when localising all Reads in a
> somewhat heavy comp, or even playing back a sequence of exr's or deep
> files, compared to localised sequences on a 10K Raptor drive also in my
> workstation - hopefully I'm missing something big though, this is day one
> after all.
>
> There may be real tangible benefits to putting the Nuke cache on it though
> - I'll see how it goes.
>
> I'm also guessing that as gpu processing becomes more prevalent in Nuke
> that we will see a real speed advantage handing data from a card like this
> straight to the gpu.
>
> Thanks,
> Michael
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support

Re: AW: AW: [Nuke-users] Alexa Artifacts

[Howard Jones]

It was the same here - shot directly in ProRes 444.
No idea what though


 
Howard



>
> From: Igor Majdandzic 
>To: 'Nuke user discussion'  
>Sent: Friday, 29 March 2013, 16:29
>Subject: AW: AW: [Nuke-users] Alexa Artifacts
> 
>
>Do you know what caused them?
> 
>-- 
>igor majdandzic
>compositor |
>i...@badgerfx.com
>BadgerFX | www.badgerfx.com
> 
>Von:nuke-users-boun...@support.thefoundry.co.uk 
>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Magno Borgo
>Gesendet: Freitag, 29. März 2013 14:06
>An: Nuke user discussion
>Betreff: Re: AW: [Nuke-users] Alexa Artifacts
> 
>I've seen the exactly same artifacts when working on a film shot on Alexa. 
>These are nasty specially when keying... same issue, shot directly in Proress 
>.
> 
>Magno.
> 
> 
> 
>We've been having some problems with noise on some footages from Alexa, but 
>nothing remotely near to that.
>> 
>>diogo
>> 
>>On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad  
>>wrote:
>>No idea, but it looks an awful lot like filtering from a slight resize 
>>operation.
>> 
>>-jonathan
>>
>>On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic"  
>>wrote:
>>do you mean in camera? because that was from the original qt footage
>>> 
>>>-- 
>>>igor majdandzic
>>>compositor |
>>>i...@badgerfx.com
>>>BadgerFX | www.badgerfx.com
>>> 
>>>Von:nuke-users-boun...@support.thefoundry.co.uk 
>>>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan 
>>>Egstad
>>>Gesendet: Donnerstag, 28. März 2013 01:10
>>>An: Nuke user discussion
>>>Cc: Nuke user discussion
>>>Betreff: Re: [Nuke-users] Alexa Artifacts
>>> 
>>>Looks like a very  slight resize was done.
>>>-jonathan
>>>
>>>On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic"  
>>>wrote:
>>>Hey guys,
>>>>we got footage from a shoot with Alexa being the camera. It was shot in 
>>>>ProRess 444. The problem is: The picture has some artifacts which confuse 
>>>>me the codec being 444. I attached some images which show some of the grain 
>>>>patterns. Is this normal?
>>>> 
>>>>thx,
>>>>    Igor
>>>> 
>>>> 
>>>> 
>>>>-- 
>>>>igor majdandzic
>>>>compositor |
>>>>i...@badgerfx.com
>>>>BadgerFX | www.badgerfx.com
>>>> 
>>>>Von:nuke-users-boun...@support.thefoundry.co.uk 
>>>>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Deke 
>>>>Kincaid
>>>>Gesendet: Mittwoch, 27. März 2013 23:47
>>>>An: Nuke user discussion
>>>>Betreff: Re: [Nuke-users] FusionI/O and Nuke
>>>> 
>>>>Hi Michael
>>>>I'm actually testing this right now as Fusionio just gave us a bunch of 
>>>>them.  Early tests reveal that with dpx it's awesome but with openexr zip 
>>>>compressed file it it is spending more time with compression, not sure if 
>>>>it is cpu bound or what(needs more study but its slower).  Openexr 
>>>>uncompressed files though are considerably superfast but of course the 
>>>>issue is that it is 18 meg a frame.  These are single layer rgba exr files.
>>>>
>>>>
>>>>-
>>>>Deke Kincaid
>>>>Creative Specialist
>>>>The Foundry
>>>>Mobile: (310) 883 4313
>>>>Tel: (310) 399 4555 - Fax: (310) 450 4516
>>>>
>>>>The Foundry Visionmongers Ltd.
>>>>Registered in England and Wales No: 4642027
>>>> 
>>>>On Wed, Mar 27, 2013 at 3:26 PM, Michael Garrett  
>>>>wrote:
>>>>I'm evaluating one of these at the moment and am interested to know if 
>>>>others have got it working with Nuke nicely, meaning, have you been able to 
>>>>really utilise the insane bandwidth of this card to massively accelerate 
>>>>any part of your day to day compositing?
>>>> 
>>>>So far, I've found it has no benefit when localising all Reads in a 
>>>>somewhat heavy comp, or even playing back a sequence of exr's or deep 
>>>>files, compared to localised sequences on a 10K Raptor drive also in my 
>>>>workstation - hopefully I'm missing something big though, this is day one 
>>>>after all.  
>>>> 
>>>>The

AW: AW: [Nuke-users] Alexa Artifacts

[Igor Majdandzic]

Do you know what caused them?

 

-- 

igor majdandzic

compositor |

  i...@badgerfx.com

BadgerFX |   www.badgerfx.com

 

Von: nuke-users-boun...@support.thefoundry.co.uk
[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Magno
Borgo
Gesendet: Freitag, 29. März 2013 14:06
An: Nuke user discussion
Betreff: Re: AW: [Nuke-users] Alexa Artifacts

 

I've seen the exactly same artifacts when working on a film shot on Alexa.
These are nasty specially when keying... same issue, shot directly in
Proress .

 

Magno.

 

 

 

We've been having some problems with noise on some footages from Alexa, but
nothing remotely near to that.

 

diogo

 

On Wed, Mar 27, 2013 at 9:50 PM, Jonathan Egstad 
wrote:

No idea, but it looks an awful lot like filtering from a slight resize
operation.

 

-jonathan


On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic" 
wrote:

do you mean in camera? because that was from the original qt footage

 

-- 

igor majdandzic

compositor |

  i...@badgerfx.com

BadgerFX |   www.badgerfx.com

 

Von: nuke-users-boun...@support.thefoundry.co.uk
[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan
Egstad
Gesendet: Donnerstag, 28. März 2013 01:10
An: Nuke user discussion
Cc: Nuke user discussion
Betreff: Re: [Nuke-users] Alexa Artifacts

 

Looks like a very  slight resize was done.

-jonathan


On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic" 
wrote:

Hey guys,

we got footage from a shoot with Alexa being the camera. It was shot in
ProRess 444. The problem is: The picture has some artifacts which confuse me
the codec being 444. I attached some images which show some of the grain
patterns. Is this normal?

 

thx,

Igor

 

 

 

-- 

igor majdandzic

compositor |

  i...@badgerfx.com

BadgerFX |   www.badgerfx.com

 

Von: nuke-users-boun...@support.thefoundry.co.uk
[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Deke
Kincaid
Gesendet: Mittwoch, 27. März 2013 23:47
An: Nuke user discussion
Betreff: Re: [Nuke-users] FusionI/O and Nuke

 

Hi Michael

I'm actually testing this right now as Fusionio just gave us a bunch of
them.  Early tests reveal that with dpx it's awesome but with openexr zip
compressed file it it is spending more time with compression, not sure if it
is cpu bound or what(needs more study but its slower).  Openexr uncompressed
files though are considerably superfast but of course the issue is that it
is 18 meg a frame.  These are single layer rgba exr files.




-
Deke Kincaid
Creative Specialist
The Foundry
Mobile: (310) 883 4313
Tel: (310) 399 4555 - Fax: (310) 450 4516

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

 

On Wed, Mar 27, 2013 at 3:26 PM, Michael Garrett 
wrote:

I'm evaluating one of these at the moment and am interested to know if
others have got it working with Nuke nicely, meaning, have you been able to
really utilise the insane bandwidth of this card to massively accelerate any
part of your day to day compositing?

 

So far, I've found it has no benefit when localising all Reads in a somewhat
heavy comp, or even playing back a sequence of exr's or deep files, compared
to localised sequences on a 10K Raptor drive also in my workstation -
hopefully I'm missing something big though, this is day one after all.  

 

There may be real tangible benefits to putting the Nuke cache on it though -
I'll see how it goes.

 

I'm also guessing that as gpu processing becomes more prevalent in Nuke that
we will see a real speed advantage handing data from a card like this
straight to the gpu.

 

Thanks,

Michael


___
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

 





-- 

Magno Borgo
www.boundaryvfx.com
www.borgo.tv
Brasil:Curitiba:GMT= -3

___
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

Re: AW: AW: [Nuke-users] Alexa Artifacts

[Simon Blackledge]

Are the rolls that have it later in the day and earlier clips ok ? 

Sent from my iPhone

On 28 Mar 2013, at 07:31, "Igor Majdandzic"  wrote:

> I had to resize the crop to make it obvious, but the filtering from that 
> operation did slightly add to the appearance of that artifact. Some rolls do 
> have it, most obvious in even backgrounds and some dont. First I thought they 
> filmed with LT or such, but the metadata proved me wrong.
> So maybe, I contact the Arri guys.
>  
> Thanks guys.
>  
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>  
> Von: nuke-users-boun...@support.thefoundry.co.uk 
> [mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan 
> Egstad
> Gesendet: Donnerstag, 28. März 2013 01:51
> An: Nuke user discussion
> Cc: Nuke user discussion
> Betreff: Re: AW: [Nuke-users] Alexa Artifacts
>  
> No idea, but it looks an awful lot like filtering from a slight resize 
> operation.
>  
> -jonathan
> 
> On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic"  
> wrote:
> 
> do you mean in camera? because that was from the original qt footage
>  
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>  
> Von: nuke-users-boun...@support.thefoundry.co.uk 
> [mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan 
> Egstad
> Gesendet: Donnerstag, 28. März 2013 01:10
> An: Nuke user discussion
> Cc: Nuke user discussion
> Betreff: Re: [Nuke-users] Alexa Artifacts
>  
> Looks like a very  slight resize was done.
> 
> -jonathan
> 
> On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic"  
> wrote:
> 
> Hey guys,
> we got footage from a shoot with Alexa being the camera. It was shot in 
> ProRess 444. The problem is: The picture has some artifacts which confuse me 
> the codec being 444. I attached some images which show some of the grain 
> patterns. Is this normal?
>  
> thx,
> Igor
>  
>  
>  
> --
> igor majdandzic
> compositor |
> i...@badgerfx.com
> BadgerFX | www.badgerfx.com
>  
> Von: nuke-users-boun...@support.thefoundry.co.uk 
> [mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Deke 
> Kincaid
> Gesendet: Mittwoch, 27. März 2013 23:47
> An: Nuke user discussion
> Betreff: Re: [Nuke-users] FusionI/O and Nuke
>  
> Hi Michael
> 
> I'm actually testing this right now as Fusionio just gave us a bunch of them. 
>  Early tests reveal that with dpx it's awesome but with openexr zip 
> compressed file it it is spending more time with compression, not sure if it 
> is cpu bound or what(needs more study but its slower).  Openexr uncompressed 
> files though are considerably superfast but of course the issue is that it is 
> 18 meg a frame.  These are single layer rgba exr files.
> 
> -
> Deke Kincaid
> Creative Specialist
> The Foundry
> Mobile: (310) 883 4313
> Tel: (310) 399 4555 - Fax: (310) 450 4516
> 
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>  
> 
> On Wed, Mar 27, 2013 at 3:26 PM, Michael Garrett  
> wrote:
> I'm evaluating one of these at the moment and am interested to know if others 
> have got it working with Nuke nicely, meaning, have you been able to really 
> utilise the insane bandwidth of this card to massively accelerate any part of 
> your day to day compositing?
>  
> So far, I've found it has no benefit when localising all Reads in a somewhat 
> heavy comp, or even playing back a sequence of exr's or deep files, compared 
> to localised sequences on a 10K Raptor drive also in my workstation - 
> hopefully I'm missing something big though, this is day one after all.  
>  
> There may be real tangible benefits to putting the Nuke cache on it though - 
> I'll see how it goes.
>  
> I'm also guessing that as gpu processing becomes more prevalent in Nuke that 
> we will see a real speed advantage handing data from a card like this 
> straight to the gpu.
>  
> Thanks,
> Michael
> 
> ___
> 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.u

AW: AW: [Nuke-users] Alexa Artifacts

[Igor Majdandzic]

I had to resize the crop to make it obvious, but the filtering from that 
operation did slightly add to the appearance of that artifact. Some rolls do 
have it, most obvious in even backgrounds and some dont. First I thought they 
filmed with LT or such, but the metadata proved me wrong.

So maybe, I contact the Arri guys. 

 

Thanks guys.

 

-- 

igor majdandzic

compositor |

  i...@badgerfx.com

BadgerFX |   www.badgerfx.com

 

Von: nuke-users-boun...@support.thefoundry.co.uk 
[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan 
Egstad
Gesendet: Donnerstag, 28. März 2013 01:51
An: Nuke user discussion
Cc: Nuke user discussion
Betreff: Re: AW: [Nuke-users] Alexa Artifacts

 

No idea, but it looks an awful lot like filtering from a slight resize 
operation.

 

-jonathan


On Mar 27, 2013, at 5:29 PM, "Igor Majdandzic"  
wrote:

do you mean in camera? because that was from the original qt footage

 

-- 

igor majdandzic

compositor |

  i...@badgerfx.com

BadgerFX |   www.badgerfx.com

 

Von: nuke-users-boun...@support.thefoundry.co.uk 
[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Jonathan 
Egstad
Gesendet: Donnerstag, 28. März 2013 01:10
An: Nuke user discussion
Cc: Nuke user discussion
Betreff: Re: [Nuke-users] Alexa Artifacts

 

Looks like a very  slight resize was done.

-jonathan


On Mar 27, 2013, at 4:56 PM, "Igor Majdandzic"  
wrote:

Hey guys,

we got footage from a shoot with Alexa being the camera. It was shot in ProRess 
444. The problem is: The picture has some artifacts which confuse me the codec 
being 444. I attached some images which show some of the grain patterns. Is 
this normal?

 

thx,

Igor

 

 

 

-- 

igor majdandzic

compositor |

  i...@badgerfx.com

BadgerFX |   www.badgerfx.com

 

Von: nuke-users-boun...@support.thefoundry.co.uk 
[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Deke Kincaid
Gesendet: Mittwoch, 27. März 2013 23:47
An: Nuke user discussion
Betreff: Re: [Nuke-users] FusionI/O and Nuke

 

Hi Michael

I'm actually testing this right now as Fusionio just gave us a bunch of them.  
Early tests reveal that with dpx it's awesome but with openexr zip compressed 
file it it is spending more time with compression, not sure if it is cpu bound 
or what(needs more study but its slower).  Openexr uncompressed files though 
are considerably superfast but of course the issue is that it is 18 meg a 
frame.  These are single layer rgba exr files.




-
Deke Kincaid
Creative Specialist
The Foundry
Mobile: (310) 883 4313
Tel: (310) 399 4555 - Fax: (310) 450 4516

The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027

 

On Wed, Mar 27, 2013 at 3:26 PM, Michael Garrett  wrote:

I'm evaluating one of these at the moment and am interested to know if others 
have got it working with Nuke nicely, meaning, have you been able to really 
utilise the insane bandwidth of this card to massively accelerate any part of 
your day to day compositing?

 

So far, I've found it has no benefit when localising all Reads in a somewhat 
heavy comp, or even playing back a sequence of exr's or deep files, compared to 
localised sequences on a 10K Raptor drive also in my workstation - hopefully 
I'm missing something big though, this is day one after all.  

 

There may be real tangible benefits to putting the Nuke cache on it though - 
I'll see how it goes.

 

I'm also guessing that as gpu processing becomes more prevalent in Nuke that we 
will see a real speed advantage handing data from a card like this straight to 
the gpu.

 

Thanks,

Michael


___
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