pixel space problems and then some

[werlin]

i already mentioned that fx like kaleidoscope and bendoscope have strange results outputing oval results when applied in 16:9 comp (i guess it might be the same in 4:3 but less noticeable)

i forgot to mention one thing i find strange, that is if you have a 16:9 comp, when you choose fullscreen output... it comes out 4:3 or 5:4 depending on which monitor i choose... it ends up all stretched out (didnt test it on the projector yet though but there its only a question of changing the projectors format, although im not sure how that much pixel stretching and shrinking might end up like...

but now i have yet another issue... i have a 2000:660px jpeg with a mirror efect applied to it, and i noticed that if i put a 1600:1200 video on top, the percentage of the mirror axis suddenly changes (in this case on Y)... so im assuming that as soon as the video starts playing there's some internal mambo-jambo that says to the whole app "yeah now you're a 2000:1200px, just crop all of it at the very end to 16:9 and you're good to go" which sincerely its a pain...

also there's another thing i've been struggling with, that is, concerning the clips position... when changing from +\- to timeline it seems to respond more than needed to the dimensions of the clip... you can always drag the clip out of the screen, and then some, and then some more
what's that all about?

ps: on an unrelated note that i've also mentioned on another thread, but is it possible, through notepad in a preferences file somewhere, to change the max steps of relative midi encoders? at 500 steps knobs feel a bit slow

ps2: on yet another,is there any plans to include a 1\4 beat, and so on, on bpm timeline?

thanks

[Joris]

Hey Werlin

You don't mention what sort of connection you're using to your second monitor, but in general when you're using SD video connections, every signal will be resized to 5:4. The monitor or projector will then stretch it to 4:3 or 16:9.

I tried to recreate your issue, but I think I'm missing a few steps. Can you give us a step by step walkthrough on how to recreate it?

Regarding the moving of the clip, Avenue uses the texture limit of 4096 pixels.

We saw your post about the relative midi signals, and put in a feature request.

We'll have a look at lower BPM values. I'm kind of curious to see what kind of visuals you are making that require this though. Can't be safe for epileptics I reckon?

Joris

[werlin]

asus 8600gt board has dvi, then i got connectors to vga cables that go into the monitors

as for the issue just dl http://werlintm.no.sapo.pt/problem.rar put the two pics on c: and open the composition

once you're in, click on the photo with mirror, then click on the solid color photo and you'll see a small hickup followed by the mirror center jumping... (the parameters dont jump... just the output)

apparently with some pics tends to happen others doesnt, i even tried converting the photo to dxv, change proportion, crop it a bit, save it on top of another pic which doenst have problems... but i find it strange its behaviour even on dxv

ah ok, makes sense for triple head's and stuff..

thanks, its always good to have large parameter mins and maxs, be it the knobs, or speeds (altough the position still drives me a bit crazy) since the world doesnt run only at 140bpm (and doesnt run only on single screens )

[werlin]

hello again,

any word on this issue? were you guys able to replicate it on your end? if so, do you already have any idea on whats causing it?

thx

[Joris]

hey werlin

we haven't gotten round to checking this yet. my apologies for that, we've been quite busy with the 3.3 release. it's definitely on our radar though!

joris

[werlin]

thanks joris

hope 3.3 to be a blast, good luck guys

[werlin]

btw one more on these kind of issues...

whats up with layer effects working directly within clip canvas space?

shouldnt they work more like compfx and use the comp's canvas?

i noticed this yesterday when i was messing around with a logo... and if you trow any kind of layerfx on top of it it, does not use the whole comp space and ends up all boxed out, which it looks kind of ugly...

[Joris]

Instead of adding an extra render pass to the pipeline, translations and effects on both layers and clips are first calculated cumulative and only then rendered. Basically Resolume treats translations and effects on clip and layers as the same thing. This shaves off quite a bit of render time, giving a boost in FPS. Since it is rather different to what you would expect, we're looking into making this an option in future.

Hope that makes sense.

Joris

[werlin]

Since it is rather different to what you would expect, we're looking into making this an option in future.

indeed especially when you're dealing with cilp scale, position and rotation, and you want to apply effects on the fly to them alone and still wanting them to fit into the composition and not standing out from the rest.
im glad you're seeing into it though

[werlin]

btw if you proceed with this is there anyway to have layerfx render after blend mode? so you can apply a nice little blur to lumakey for instance?