Are you saying that this feature is currently only partially available? If so, to what extent is it functional, and has this partial version already been released? We’d appreciate any details you can share, as we’re also in the process of updating our customer. Additionally, if the full version is unlikely to be available by June, could you let us know when we can expect a working release?
@3stan in the June Release, the restriction of Text Layer rendering will be provided. In the July we plan to implement restriction for other layers. In the case of unexpected complexity, this update will be provided later. I think the worst case - no later than September. But we’ve done big work in this direction last month.
@Dmitriy.Sorokin are we still on target by July release for the fixed mentioned from your previous comment?
Just in case you missed my comment. Any updates on this if we are still on target?
Thanks
@3stan at this moment, Aspose.PSD team optimized rerendering of Text Layers, so, speed of rerendering should faster. Optimizing of other layers is in work.
@paldueso at this moment, rendering of Text Layers is optimized. Rendering of SmartObjects is also improved both qulity and rendering speed. Please create additional topic with your input files if you are experiencing issues.
Just a clarification, you’ve mentioned that “rendering of Text Layers is optimized. Rendering of SmartObjects is also improved both qulity and rendering speed”
Does this includes on release 25.7? or it will still be included on the future release? We need to know as if this is already part of the current release (25.7) we might need to test this if somehow the performance improved but we still not know if this will address the issue on PSDNET-2382
Moving forward, any comment from @paldueso consider kindly consider this as part of the issue as we are on the same team.
@3stan @paldueso
This is included in 25.7. Text Layers will not be rerendered if they were not changed. So the original font will be used if you don’t use AllowNonChangedLayerRepaint = true
using (var psdImage = (PsdImage)Image.Load(srcFile,
new PsdLoadOptions() { AllowNonChangedLayerRepaint = false /* The new default behavior */ }))
{
psdImage.Save(output1, new PngOptions());
((TextLayer)psdImage.Layers[1]).TextData.UpdateLayerData();
psdImage.Save(output2, new PngOptions());
}
SmartObject Warp Transformation also became more accurate.
But the best way to check if the current implementation status is suitable for you tasks is to check this using Temporary License
So we’ve update our Aspose.PSD to 25.7 but we are still encountering the issue on saving the PSB with XMP Metadata back which is the original issue. I guess we need to wait for this to be out.
image.png (10.8 KB)
Given this result? I guess the initial ETA which is June (March 18 Post) is already not feasible since we are already in the middle of july, any feedback from the team the next ETA?
hi @Anzim
Yes the same issue. To give you some background, The issue only occurs on production environment which have have a allocation of around 4 to 6gb of resources and since the file that we are processing is more than 2gb of file, it seems that this is an memory issue because we don’t encounter this on a local environment due to that our local have more resources on our local. We cannot just upscale our production environment upright because by doing this, it means that every prod environment of our customer will need to be upscale and this will be cost us a lot.
One suggestion of @Dmitriy.Sorokin which i think on the ticket PSDNET-2382 is to have a feature that it will update the XMP without re rendering the PSB again to save memory allocation.
On your perspective is this feature is doable on your end? and how long we will wait for this update? because one of our important customer are waiting for this to be able to processes their PSB files
@3stan I’ll need make some investigation. I think Aspose.PSD Image processing is ready up to 70% to start support editing of XMP data without rendering at this moment. I’ll write you back on this week.
Do we have an update on this and expected target date? as we need also update our customer.
@3stan the fix will not be delivered in 25.8, but the Team is working on it. The Team will try to make suitable fix in Aspose.PSD for .NET 25.9.
@Dmitriy.Sorokin - we are at the middle of August. Is 25.9 on track to release with the fix we are expecting? Please note I am with the same team with @3stan
@paldueso the task is in work. On this stage of development, the most likely option, that will be added new property to PsdLoadLoadOptions.
Hi @Dmitriy.Sorokin - We still have one more week before September begins, and we’d like to request a status update on the fix and the 25.9 release. Could you confirm if everything is still on track with our schedule? Please also note that I am part of the same team as @3stan.