Burn transition --> black output

[Rene]

Hey,

using the Burn transition at the upper layer when the lower layer's opacity is zero I get a black output. When I increase the opacity at the lower layer I see fragments of the lower layer in the output (even if the upper layer's opacity is at 100%) - can somebody reproduce/confirm this?

avenue301_burn.jpg (38.78 KiB) Viewed 10565 times

System:
Vista32 / GeForce 9500M GS

Codec: tried with
DXV with uncompressed Audio and
M-JPEG (.avi) also with uncompressed Audio

[syzygy]

I don't see this behaviour (using the standard clips that come with Avenue)

If you try it with the demo clips, it will tell the Resolume guys whether this is an issue that only relates to specific content on whether there is a software/hardware incompatibility.

Dan.

[GeeEs]

Although this seems logic to me, I think it doesn't matter. Or better... It shouldn't make any difference, otherwise this application is for 99% worthless. (no offence)

If the only way to test a probable soft/hardware error is with the 6 demo clips you can't really tell if Avenue will ever be compatible with any other (homemade) clip. It should behave the same way with every DXV or MJPEG encoded clip imho. I read Rene tested with MJPEG and the new DXV codec. (I cant reproduce this problem either so no solution here...)

As an example... the 6 demo clips are not DXV so we as a user (or the resolume guys) can't really tell from the demo clips if the DXV encoding/decoding work properly. Also.. the demo clips are WITH audio combined and after releasing Avenue it seems to work a lot better with SEPERATED video and audiofiles (my experience also).
(Speaking for myself .. I will probably never use the audio options from Avenue in a live situation... except for fft functions from external source).

I know this isn't really helpfull maybe, but I can't imagine we have to test with the demo clips only...

[syzygy]

No offense, but I think you misunderstood why I was suggesting a test with the demo clips.

I was suggesting testing using those in addition to the other clips as it would provide some useful information that would help the Resolume guys track down the problem. I thought I made that pretty clear but you seem to think I was suggesting that problems that only affect some content should be ignored.

The burn mode doesn't exhibit the behaviour described when used with the demo clips on my machine, so answering the question of whether it works as expected on these clips is useful. If the same problem occurs then the problem is clearly something related to what is different between the machines. If the problem does not occur, then the Resolume guys will need to look at how the content could affect the way the burn mode is behaving.

Testing with the demo clips is useful because we all have those same clips on our machines. The first step in tracking down and fixing a bug in software is reproducing it. If the bug can be reproduced, the Resolume guys can throw all kinds of debugging techniques at it. That's why, when I see someone report a bug, the first thing I try to do is reproduce it on my machine. By letting the guys know that result, I am contributing information that may help them fix the problem (which is good for all of us) If there is a set of steps that produces the bug using the demo clips, that means that any resolume user can try to reproduce the bug and provide useful information.

Yes, the software should work with all compatible content that is thrown at it but that doesn't mean that it's not useful to try to reproduce bugs with a small set of content that we all have available to us.

btw, on my machine, the demo clips are separated .avi and .wav files.

Dan.

[bart]

I can only test on Mac with ATI now and that works (with demo and dxv footage), would love to hear from more people with different hardware.

[VJair]

i cannot re-create this problem, it works as it should for me.

tested with:

XP Pro SP2
ATI HD2600
DXV and Peagsus Pic Video MJPEG codecs ( no audio in clips )

[GeeEs]

No offense, but I think you misunderstood why I was suggesting a test with the demo clips.

I was [.....] to us.

btw, on my machine, the demo clips are separated .avi and .wav files.

Dan.

True... a test with the demo footage is the best way to do this bugtracking for us all. I was referring to his specific problem. After reading your first replay again i see what you mean

The demo footage is indeed seperated.. I guess i was confusing it with something else..

Tested with: see signature

[Rene]

thanks for testing everyone!

I totally agree with syzygy about the demo footage thing. Just tried it with the demo footage on Vista32 SP1 and XP SP3 on both systems exactly the same bahaviour. (as described before)

next I've checked my drivers (I should hae done taht before, I know ) (as far as I understand the latest omegadrivers (nvidia card with xp / vista) do not support notebooks - pls. correct me if I'm wrong) and found a new version (feb 2009) at the nvidia website (179.48_notebook_winxp_32bit_beta) (beta!) - after installation it seems to work! Also the Vista version of the driver fixes this opacity issue.

my apologies for not having checked drivers before!

[GeeEs]

Did some more testing yesterday evening... tried all possible blend modes and I still can't reproduce the "burn-black-output" error... I see you found the solution

However.. I have found a small issue with the "Dodge" transistion mode... on the first two layers when selected the Dodge transition, the output still shows some of the other layers, or the colors are a bit affected... Not a big issue, but putting the sliders to 0 won't kill the Dodg transition it seems... (This is only on the top 2 layers in a composition)

[Rene]

GeeEs, I can reproduce this on my XP with ATI card (did not try on Vista /nvidia yet).

But the problem is also on the lower layer. (however demo footage on the lower layer will not show this issue - unless you look very close !)
I've copied Bass 2 from the middle layer to the top and lower layer (by pressing Ctrl key) - using "Bass 2" I can see exactly what you mean
Also when the middle and top layer are empty and I just mix in the lower layer's "Bass 2".