Bitte lesen Sie diese Seite (auf Englisch) https://community.adobe.com/t5/indesign/where-are-the-controllers/m-p/11135976 ... View more

Acrobat cannot do "automatic" measurements; but in AutoCAD it is a one-command solution. Buy a copy, demand that your clients supply plans in DWG with each wall type on a different layer. If they refuse, charge them for the extra work of measuring. ... View more

Automatically varying the brightness of the new plate (uniformly across the plate) is quite easy with expressions. Simply track a representative point on the existing plate, then use the sampleImage() expression to read the RGBA value of a small group of pixels under the track point. You can then use those time-varying RGB values to control brightness/tint adjustments on the new plate layer. It's not going to replicate partial shadows moving across the plate, but it's probably too small in frame to care about that.   A walk-through of a similar task (using sampleImage to set the brightness of a lens flare) is here. ... View more

"you haven't worked with the sort of Creative Directors/Marketing Directors that I have!"   I deal with corporate livery rules every day, written for print with Pantone spot or foil embossed logos, and applied to everything from TVCs to YouTube - plus CAM specs that define color with RAL paint codes. I just make stuff that looks right, and in 20 years of production nobody has noticed their "Company Purple" is half a percent off in Rec.709 space. Outside of film and TV, corporate top brass don't have calibrated monitors!   ..and I also use Resolve and Fusion for everything color-critical. They don't pretend to have fancy-schwancy swatch libraries but they can be trusted to keep colors accurate when you're given a bunch of weird footage, and they do ACES properly. After Effects has its uses (e.g. updating hundreds of text clips for video translations is a nightmare with Fu, wheras in AE you can one-click import from a spreadsheet) but you are correct about wasted opportunities. All the attention goes into stuff like "team projects", which is fat use if the colors are borked.     ... View more

Need a bit more information on what your pipeline is. Are you compositing frames from 3D software, applying effects to camera footage, generating synthetic motion graphic overlays...   ACES in After Effects is "possible", to varying degrees of the definition of "possible". You basically have to disable all of the ICC-based Adobe color management stuff, switch the project to 32-bit linear and use multiple OCIO adjustment layers to send all of your working layers through the IDT (and back out through the ODT/RRT so you cna see what you're doing), and finally check your outputs in something that understands ACES (even if you think you've set the project up right the exports can go wrong, and that will stuff it up for whoever is downstream in the pipeline). It's nowhere near as simple as it is in Nuke, Fusion, etc.   Also important to note that while an entire production can be ACES2065-1, CGI is almost always done in ACEScg. It's just better at dealing with passes and synthetics. A smaller gamut but the missing bits are largely irrelevant.   You can also (with significant limitations) work in Rec.709/Rec.2020 and shoehorn the output into ACES color space. Someone tried that here.   The problem is knowing when your software path is legal (i.e. acceptable within an ACES pipeline, which forbids certain things) and the results are legitimate (i.e. the colors match the real scene and are reacting correctly to what you're doing). For example if a background plate is tagged with the wrong IDT, it will have a gamma shift - often enough to make it not match the original, but not enough for it to look "wrong" on your AE monitor (which is not going to be color managed). The same will happen to a texture used on a 3D object, or an HDRI environment map. Some 3D rendering engines can output ACES-legal data, some cannot (Arnold in Maya...brilliant. Corona in Max...roadkill)   Sitting in splendid isolation in a production pipeline you would never know if something is a few percent too green, which is why it's really important to have vision of the steps either side. If someone says your files are "not displaying correctly" you need the tools to analyze them. Maybe the colors are off, maybe it's just a metadata problem. Maybe someone gave you the wrong IDT. In After Effects everything has to be set up manually in OCIO so wrong choices will not throw error messages.   When anyone's starting on this road, especially if they're stuck using Adobe software, it's important to build an in-house pipeline to run loop tests, be that with BL/Nuke/Resolve/etc.. Push something round in a circle and see if it matches itself.     ... View more

It's a well-known issue; The After Effects "intelligent" color management engine is stupendously dumb. No matter what you do in the project or export settings, imported Pr422 footage is always interpreted as if it was Rec709/2.4 and the option to tell After Effects the truth is grayed out (you as a mere user cannot be correct, only Adobe can be correct). I would resolve to use a software suite that understands color properly.   https://community.adobe.com/t5/after-effects/another-color-management-issue/m-p/11223259 https://community.adobe.com/t5/after-effects/importing-prores-into-colour-managed-compositions/m-p/10232242 https://community.adobe.com/t5/after-effects/how-to-stop-adobe-after-effects-from-changing-colors-on-shared-imovie-footage/m-p/11175231   All the way back in 2009, Todd was telling everyone just how bad the problem was on the official Adobe blog. The only thing that's changed in eleven years is which wrong profile it assigns.   ... View more

Agreed - aside from the faff with actually opening something, everyday user actions like "take me to page 3" are often impossible, because the UI was built to expect flowable content where pages are meaningless. ADE has always been an unwanted child, it started life as the "eBook Reader" plugin in Acrobat and in the decade or so since it was kicked out as a standalone application it's hardly changed.   Maybe, just maybe, the likes of ERDlab will up their game when they see people fleeing from PDF. We can but hope! ... View more

You are doing everything correctly, but Adobe is hell-bent on breaking rich media in PDF. They messed up by insisting that Flash Player be involved whenever someone wants to play video or audio in a PDF (despite there being no reason why the embedded MP3 or MP4 can't be played natively, just like your Web browser does), and now they're trying to force people off the bus by messing with the user interfaces in Acrobat and InDesign.   FXL EPUB-3 is the way to go in the medium term, but it's a more complicated user experience at the moment (with the default EPUB apps like Apple Books you can't just "open" a random file or email attachment, you have to import it to your library, which puts a copy into some hidden folder you've never heard of and syncs it to your phone, etc. etc.)   For info on all those warnings see here. ... View more

Non-Acrobat PDF viewers are terrible at understanding PDF forms and JavaScript actions, which is how the show/hide stuff works under the hood.   If you know you are targeting web browsers then ditch PDF and create your documents in HTML, after all that's what you're trying to simulate anyway. If you need something portable there's always fixed-layout EPUB3. ... View more

No longer realistically possible. Many years ago there was a method to "embed" the YouTube player into a PDF, but it broke YouTube's terms and conditions so the loophole was rapidly plugged. The only thing you can do now is embed (or stream) a regular MP4 video file, with standard playback controls. You can't embed part of a website, nor can you load up an installed player like VLC.   As far as Adobe is concerned PDFs are for "documents", which are boring printable things with maybe a form field at the very most. Anything interactive / multimedia is dumped into the lap of EPUB and native apps.   Host the video online somewhere with working navigation controls, and just put a hyperlink in the PDF. ... View more

This sounds like you want to sell on-demand access to Creative Cloud to other users (a service bureau system). That is completely forbidden and will provoke legal action.   The features which allow After Effects to be used across a network are only permitted as a way for the licensed subscriber to operate the software (e.g. as part of a personal render farm or via remote-working). The Adobe Terms of Use are absolutely clear:   6.2 You must not: offer, use, or permit the use of the Services or Software in a computer services business, third-party outsourcing service, on a membership or subscription basis, on a service bureau basis, on a time-sharing basis, as a part of a hosted service, or on behalf of any third party. ... View more

The View SDK does not "prevent download", it simply allows someone to hide the on-screen burger menu. The very first thing your script does is fetch("...brochure.pdf") which downloads a complete copy into the browser cache. If the page containing the SDK frame is public, the document URL will be indexed by search engines.   It also means Adobe can slurp thousands of tracking data points every time someone views a document, even if the document is not hosted on Adobe's network. Every mouse click, every scroll, all sent back to the Mothership without the slightest hint of a consent agreement.   ... View more

It's technically impossible. When you print to PDF (as opposed to saving as PDF) then the parent application is simply told to print to a generic Postscript printer, and it sends standard PS commands to the virtual printer port. There is no command to set Acrobat's page view styles in Postscript, and Adobe doesn't set the rules on what Postscript can and cannot do.   If you have a bunch of "printed" files and need to change something about them, run them through an Action in Acrobat Pro. ... View more

"Lets wait for PDF2 first shall we" ISO32000-2 was published in July 2017. The fact Adobe software doesn't create PDF/2.0 tagged files is because they don't want it to, not because they can't. Flash is only a minor issue, there are several great new features in PDF/2.0 that people have been asking for for years (document parts, per-page output intents, pronounciation hints for tagged text) which you still need to go outside the Adobe bubble to make use of.   It's pointless for anyone (Adobe included) to keep saying "get over it, Flash is dead" unless they can offer a replacement technology which can embed multimedia in a view-as-authored, cross-platform, secure offline document that supports commenting, forms, layers, signatures, etc etc etc. Maybe one day EPUB3 will get there but it isn't anywhere close at the moment. If people want to keep using the current system right up to the 31 December deadline, it's their decision.   To quote from the official policy document:   How will this decision impact Adobe Flash Player support and distribution for the remainder of the year (2020)? Adobe will continue issuing regular Flash Player security patches, maintain OS and browser compatibility, and add features and capabilities as determined by Adobe through the end of 2020.   Show me where in that sentence it says "...and we'll remove features and capabilites in May 2020..."   ... View more

Because Flash Player, in its role as the Rich Media engine for ISO-compliant PDF files, is not dead.   Adobe lost control of PDF years ago, they do not get to suddenly say that feature X is "wrong", they only get to say "we no longer provide a standards-compliant PDF renderer".   There is no replacement for the Flash Player multimedia engine in Acrobat/Reader and no sign there will be one anytime soon. No vendor - not Adobe, Apple nor anyone else - can suddenly decide that RMAs should contain HTML5 or Quicktime, so until ISO release PDF/3.0 (which will happen long after we're all dead) creating and viewing a PDF with a SWF-based Rich Media annotation remains 100% standards-compliant. Someone in Adobe has thrown up all these obstacles for purely political reasons, they intend to make people so annoyed by the popups that we stop using PDFs for multimedia seven months before the actual deadline.   If I want to create a document today, and show it to an audience tomorrow, what may or may not happen in December is absolutely irrelevant. By all means show a warning to the author inside InDesign but don't mess with what the readership sees, especially not if the document is in full-screen.   Imagine trying to buy a 2020 calendar and finding that every copy now has "DANGER: EXPIRES IN DECEMBER" printed over each page.   ... View more

Yeah, the latest "improvement" to Acro DC has borked rich media. Color me surprised.   Every rich media annot [RMA] gets the "3D content" warning instead of the correct one. Agreeing to "enable 3D" then should trigger another popup: Say "Ask me later" and this damn thing will KEEP APPEARING every time you open a page with an RMA, even in full-screen mode. That is completely against the conformity rules for full-screen, but hey; Adobe doesn't care anymore, it's going to make you regret using Flash even if that means messing up a sales presentation in front of your top client. If you click "Ok" it disables Flash Player completely, and the next time you encounter an RMA you will get this security message:   Which doesn't tell you jack sht about how to undo what you just did by clicking that "Ok".   To re-enable rich media you have to dig into the Preferences panel, and re-check this box: Which of course sends you right back to that impossible-to-kill black popup.   A cynical person might think that Adobe is intentionally breaking every possible feature that involves Flash Player in the desperate hope that people will give up and use something else; but the way they're going about it that "something else" will be from another vendor. Even PowerPoint is looking good in comparison. ... View more

The correct way to pipeline through a third-party colorist is to export a wide gamut master, usually an EXR frame sequence. EXRs can include unpremultiplied alpha channels and multiple layers. ... View more

The way Acrobat "improves" your URIs keeps changing, it's pot luck which versions do or do not mess with the characters. It's been broken on and off since Acrobat 8, but I've never seen it mentioned in the change notes.   There is no config option in Acrobat that controls URI parsing, even in the secret PreferenceReference. ... View more

"unauthorized viewing and printing, modifying and copying, printing to file."   "Possible" using password or certificate encryption in Acrobat, but apart from the document open password, everything else is just a suggestion to the viewing application. Adobe says it will respect the suggestion, other vendors do not. So if your PDF is opened in something else, it'll be fully printable/editable/copyable.   "unauthorized saving and sharing"   Completely impossible. PDFs do not stream, they cannot be opened by anyone until after they have been saved. Nothing inside the file can prevent people from saving copies and sharing them, all you can hope is that they don't also tell people the password. You can only control who has access to the contents of a PDF if you secure it with digital rights management (a massively expensive LiveCycle Enterprise service). ... View more

This is nothing to do with Unicode or spaces or JavaScript. Acrobat has always had major problems understanding the structure of a URI, and it makes an invalid assumption about reserved characters.   The RFC3986 standard defines which characters can and cannot be used in a URI, and also defines a set of "reserved" characters that have a special meaning (such as / : ? # ). Any character not on the permitted list, such as a space, must be percent-encoded (commonly called "URL-encoding"). The RFC is perfectly clear about the rules:   If a reserved character is being used for a reserved purpose (such as # to indicate an anchor name, or ? to show the start of a parameter list) then it must NEVER be percent-encoded. Browsers must process the character using its defined reserved function. If a reserved character is being used for any other purpose (a parameter might want to define mystring=has#tagz) then it must ALWAYS be percent-encoded, so it must be written mystring=has%23tagz . Browsers must process the character as plain text.   Some browsers are a little flexible when it comes to spaces in URLs, but they will always follow RFC3986 when they encounter a ? # or %   Acrobat always applies rule 2 and percent-encodes everything, no matter what. For the vast majority of URIs that is going to break things, and there is no way to tell Acrobat to stop messing about with the string. Adobe will argue it is playing safe by guaranteeing there will never be any "illegal" characters in a web link, but it's totally wrong to forcibly change the intention of user-entered data. It should leave the URI exactly as entered; if it's invalid that's the author's problem. ... View more

"The idea of putting multimedia in a PDF (at least until PDF 2.0 magically appears) is a fantasy for anything except a very controlled environment."   PDF/2.0 has been a published standard for 3 years - Adobe was flag-waving how wonderful it was going to be back in August 2017 - in theory Acrobat Reader can display a PDF/2.0 document, but no Adobe application can create one. If it did ever happen, InDesign would probably be first given the type of documents it can create.   Rich media PDFs with 3D content are widely used in CAD/CAM, just not with Adobe software. The video and sound versions never took off precisely because of Adobe's decision to handcuff them to their embedded Flash Player runtime, ensuring that nobody else could support it. ... View more

My level of confidence in Adobe's ability to fight its way out of a wet paper bag, while wearing Wolverine gloves and a jacket made of razor blades, is well known.   Acrobat and InDesign were born in separate business units with totally different ambitions. If one side can "improve" something and also mess up a feature in the other's application, all the better. ... View more

The ISO 32000-1/EL3 standard defines how a Rich Media annotation is structured, and Adobe's implementation for sound and video media content relies completely upon Flash Player. It is possible to extract the raw MP4 video data and play it through something else (like in the bad old days pre-Acrobat 9 when we handed off to the operating system video player, and had a truckload of exploits because of it), but the controller buttons and playback options are defined solely by the embedded SWF files and not by any settings in the PDF "dictionary" itself. It's a stupid system but Adobe went with it back in the days of Acrobat 9 so they could promote Flash Professional, and now they get to feast on their own dogfood.   In InDesign the controller SWF filename gives a hint as to which buttons it defines, but that is only because the SWFs were poached from the old Flash Pro libraries; they could just all be called "X.swf" as far as ISO 32000 is concerned. Unless the PDF rendering application can run the videoPlayer and skin SWFs it has no idea whatsoever what the playback settings should be - and as people in this thread have found to their cost if there's no skin to load, you have zero control over playback. Acrobat doesn't think "gosh, maybe I should show people a default set of controls..." because the rules say that having no skin must be an intentional choice that should be respected.   ISO 32000-2 (PDF/2.0) is very clear; Rich Media annotations remain the correct and proper way to deliver video and 3D, but it drops the specific scenario where the media being played is itself a SWF file [see ISO 32000-2:2017 table 342]. PDF/2.0 does not add any new ways for the annotation to define its playback options*, it just copies the Adobe EL3 implementation which assumes that something embedded alongside the media will "handle" all that stuff when it is sent to the rendering engine.   *(to be geekily specific there should have been new entries in the /RichMediaPresentation dictionary to define controller buttons, etc. but since Adobe had said it wasn't necessary, ISO went along)   Whatever might happen in the future is beside the point: PDF/2.0 does not revoke PDF/1.x, the billions of existing files do not suddenly become "wrong". Removing as-authored playback of anything with embedded video or sound pre-PDF/2.0 would break files which comply to a valid ISO standard. Since Adobe claims Acrobat is the world's only "compliant" renderer, they have boxed themselves into a corner. If you create a PDF today, embedding a video that just has play and mute buttons which appear on rollover, then that is precisely what must appear whenever that document is opened. ... View more

You're talking garbage. The XMP metadata packet for a PDF file has never been, and never will be, anything sacrosanct. It's "faked" billions of times every day, by software that lies about its name or version, or simply because the computer clock is wrong. Incorrect XMP has ZERO, repeat ZERO security risk, it cannot ever include executable code and no self-respecting anti-virus or firewall software would even bother to look at it. I have no idea why you're ranting on about javascript and government reports, it's utterly irrelevant to the question, which was perfectly legitimate. Or maybe you think that merely adding a fake author name turns everything into a virus? In which case show a birth certificate for "ls_rbls".   If an author wants to ensure a PDF file is not "invisibly" altered after creation then they have to digitally sign it. That is the reason AATL members can rake in millions of dollars a year for hardware tokens. If someone is creating a document in one application, and for whatever reason needs to edit the output file, then it is entirely their business what the metadata says - and in this case they are not even trying to change it, they are trying to NOT change it! ... View more

Just because a corporation is an AATL member does not mean all its certificates will validate. You can sign a PDF with anything, and many people try to use PKF files bought for use on websites, but only specific hardware-token certificates will chain correctly in Acrobat.   See https://www.digicert.com/document-signing/ ... View more

Inside InDesign you don't set the "controller" options in the PDF export window, you do it to the media object itself. Window > Interactive > Media Otherwise it would be impossible to set different options for each video in a document. ... View more

The problem with that code is there's no way to stop the thing from advancing. The PDF Page Transitions system only works in full screen mode for that very reason - without the ability to assign hotkeys to escape from the interval timer, the document will become impossible to work with.   It makes more sense to use real transitions, which you can apply to a range of pages (including defining a specific timer for every page) using the doc.setPageTransitions() API call - read the Acrobat SDK for a complete guide to the parameters. Just exclude the first page with the button, then all the trigger script needs to do is enable full-screen mode and advance one page. ESCaping to the UI will stop it. ... View more