Neue Testversion 22.90b13

[Martin Huber]

Sure, i understand that it may be caused by multiple reasons or may be linked to other apps in background. I never expected similar problem before. In that specific situation i played with Effects->Distort->Outline Wrapping.

"Effects > Distort > Outline Wrapping" only exists for backwards compatibility. The recommended way is using the Distort tool.

Martin

[shijan]

Currently Vector Distort (as well as Mesh Gradient) works only like this:


Same time Raster layers use sort of double sided pseudo 3D path and also use some customized options for this.
But same time Raster layers can't be Distorted in same "single sided" way as Vector:


Is it possible to add similar double sided pseudo 3D option to PhotoLine Distort and Mesh Gradient tools? And also add "single sided" Distort option to Raster Layers Distort.

[Andre]

Ist nicht spezifisch für die Beta Version mir aber trotzem aufgefallen:

In Eingabefeldern kann der Wert mit dem Mausrad oder durch Strg + Klicken und Ziehen verändert werden.
Beim Ändern per Mausrad werden die Änderungen sofort wirksam (z.B. bei Parametern von Vektorobjekten), bei Strg + Klicken und Ziehen erst nach Beendigung des Ziehens. Ich empfinde dieses Verhalten inkonsistent, lässt sich das vereinheitlichen?

[Martin Huber]

Currently Distort (as well as Mesh Gradient) works only like this when applied to Vector object:

I don't understand the "Mesh Gradient" part. A mesh gradient isn't applied to a layer (neither image nor vector) but a layer type on its own.

Same time Raster layers use sort of double sided pseudo 3D path and also use some customized options for this.
But same time Raster layers can't be Distorted in same "single sided" way as Vector:
(...)
Is it possible to add similar double sided pseudo 3D option to PhotoLine Distort and Mesh Gradient tools? And also add "single sided" Distort option to Raster Layers Distort.

"Distort" distorts the data of a layer. With images these are the pixels, with vector the path (not the colors). Adding an option is complicated an will probly confuse most users.

You can manually the "other" behavior manually:

• A "single sided" version for images would be adding the outline of the mesh as layer mask/clipping layer.
• Getting the image behavior with vector layers is more complicated. This requires pixel data, so you will have to convert the vector layer into an image or a placeholder.

Martin

[shijan]

Yep, i see now the difference. Other apps seems have same difference between distort vector vs raster objects. Seems like it is a global fundamental difference between vector and raster distort.
Placing vector to Placeholder works, but as you noticed - vector object placed inside Placeholder simply behave and look as raster object.

Here is also small observation. By accident i place LUT Adjustment layer as Background and notice that this start to load CPU a lot and everything in PhotoLine became very slow. Sure this situation makes no sence real life, but maybe it may help somehow to fix something

[shijan]

...

[shijan]

...

[shijan]

...

[shijan]

...

[Martin Huber]

In Eingabefeldern kann der Wert mit dem Mausrad oder durch Strg + Klicken und Ziehen verändert werden.
Beim Ändern per Mausrad werden die Änderungen sofort wirksam (z.B. bei Parametern von Vektorobjekten), bei Strg + Klicken und Ziehen erst nach Beendigung des Ziehens. Ich empfinde dieses Verhalten inkonsistent, lässt sich das vereinheitlichen?

Bei den Vektorform-Werkzeugen haben wir das geändert. Wenn du noch welche findest, schreib uns das bitte.

Martin

[shijan]

...

[Martin Huber]

Here is also small observation. By accident i place LUT Adjustment layer as Background and notice that this start to load CPU a lot and everything in PhotoLine became very slow. Sure this situation makes no sence real life, but maybe it may help somehow to fix something

i can't reproduce that. Is the behavior different with any other LUT adjustment?
Can you send us a small sample PLD?

Martin

[shijan]

You need to load some LUT to the LUT Adjustment to make it produce problem as described. Also seems slowdown depends of LUT resolution. Here is example with 1D high resolution LUT:

[Martin Huber]

You need to load some LUT to the LUT Adjustment to make it produce problem as described. Also seems slowdown depends of LUT resolution. Here is example with 1D high resolution LUT:

I still can't reproduce the problem. The performance is always the same.

Does it depend on the dialogs that are opened? Is it faster after "View > Hide Dialogs"?

Martin

[Martin Huber]

Levels Adjustment -> Output Levels and Gamma behave non-realtime with command + mouse drag.

The others behave the same here, but these are realtime.

Martin