In testing a document upload, we discovered an issue with compression. Please see the images below
Here is 100% view from adobe:
and here is the same area as seen in Tulip’s PDF viewer (at 400%)
Is there a way to adjust the compression type, or change quality? Looking for an option so we can upload large sized PDFs but still zoom in without too much artifacts. Thanks!
Hey @thorsten.langner !
The PDF was embedded into Tulip using the document widget. This PDF is being displayed within the Tulip step.
I guess we could load the documents into a table, but wouldn’t that require opening the document in a new window? Our operators will only have one screen, and we need to have the Tulip player up front at all times. I’m rather new to Tulip, so perhaps there’s another way?
Here you see the detour over tulip tables (left) and the direct way just showing the variable from the input (right). Both are fine and both work on a single step (no need to show the table)…
Thanks for the info @thorsten.langner!
I believe the issue is the “size” of the document I’m working with. Each page is 34" by 22". Much larger than your standard Letter / A4 size document! I embedded the document widget into a Tulip step and then uploaded the document. For this app, the user won’t be uploading anything. They only needed to view a document we already uploaded.
I tried again using a standard sized PDF and you can see there isn’t much of a difference:
From Acrobat at 100%
From Tulip at 400%
So, I don’t believe there’s a solution to my issue other than sizing the PDF to something that isn’t blueprint sized!
So glad I found this. I also experience the same issues (we also have blueprint sized documents).
What I’ve seen is consistent with what @thorsten.langner said above: Tulip does not use the same pdf viewer for embedded documents, vs a variable display of a file type. The embedded document has a consistent implementation across platforms, and I’ve been finding similar performance issues. The variable display of a file type seems to use some kind of “default” pdf viewer depending on what platform you’re running the player in. Ie: When I’m on Chrome, or Windows, the experience is different than what I see on an iPad.
It seems that the built in PDF viewers are preferable to the Tulip embedded document (for iPads and the Windows player). Rather than going through a table, I’m creating a variable of a file type, uploading the file in the variables view, and then displaying that variable on my page. FWIW, my PDFs are mostly text.