We are getting an exception using Aspose.Slides 21.1.0 and Aspose.Imaging 21.2.0 for .NET when trying to process an embedded EMF file in a pptx file.
This happens on windows platform.
Please find an example solution attached for reproducing the issue.
Can you investigate the issue and confirm the root cause please.
I can confirm that I can open the pptx with MS PowerPoint 2016 on Windows and with LiberOffice Impress 6.4.6.2 on Linux and I am able to save the embedded emf image into a standalone emf image on both platforms. So from my point of view this pptx file is valid.
However, if by “I am unable to access any image in the shared PPTX” you actually mean that you are unable to do that by using Aspose APIs, I can confirm that it seems a valid issue that I already reported alongside this issue at
I have used MAC OS and Windows 7 on my end. In case you have separate ticket for EMF reading from PPTX. You can share the EMF with us here for which you are getting exception.
I meant to say that I am unable to extract the EMF image using provided sample project from a PowerPoint presentation that you have shared. It returns 0 image. Therefore, Aspose.Imaging doesn’t proceed further with saving of image to validate the image save exception.
@mudassir.fayyaz: I have double checked this with one of my team mates.
He took the solution from this ticket, built it on his windows machine and received the same exception.
I agree with your investigation. However, there is no source EMF image extracted on my end from PowerPoint presentation. Therefore, I have requested you to please share the source EMF (not the one in PowerPoint) that I may use to verify and log the issue.
I have tried to open the attached EMF using online tools and the file seems to be corrupt. Even, when I tried to convert it to PNG or JPG online, I get empty file. Can you please verify your file.
I have created a ticket with ID IMAGINGNET-4466 in our issue tracking system after reproducing the issue on saving EMF using Aspose.Imaging for .NET 21.4. This thread has been linked with the issue so that you may be notified once the issue will be fixed.