olllllllo Posted December 29, 2023 Share Posted December 29, 2023 I just installed the 13.1.2 update on a MAC running Acrobat Pro build_2023.008.20423. The cut-stack function in the Imposer template, both old and created from 13.1.2, does not work. The variable is stepped across and down the sheet versus stacking. Ideas? Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted December 29, 2023 Share Posted December 29, 2023 Nothing was caught in our regression testing, which includes stacked imposition jobs. Can you please post a sample job which reproduces the problem, and a clear explanation of what the expected output is, and how it's different than the actual output? Also, in what previous version of FusionPro did this work differently? Quote Link to comment Share on other sites More sharing options...
dbarbee Posted January 2 Share Posted January 2 We are also experiencing this issue where it is not honoring the "Infinite Stack" as the Primary Imposition Step. I am running Acrobat Pro Version 2023.006.20380 on Mac OS 12.7.2. We were previously using the latest version of FusionPro without issue, which I think was 13.0.4. Is there any progress on a resolution? Are you able to duplicate the error, or do you need assistance? Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted January 2 Share Posted January 2 2 minutes ago, dbarbee said: We are also experiencing this issue where it is not honoring the "Infinite Stack" as the Primary Imposition Step. I am running Acrobat Pro Version 2023.006.20380 on Mac OS 12.7.2. We were previously using the latest version of FusionPro without issue, which I think was 13.0.4. Is there any progress on a resolution? Are you able to duplicate the error, or do you need assistance? No, so far we have not had enough details about the problem to analyze it, nor a job which reproduces the issue. Is it an issue with the FP Imposer program? That is, is it that saving a new FPI file doesn't have the "Infinite Stack" set correctly? Or is it a composition issue, where if you take an existing FPI file, it doesn't compose correctly? Quote Link to comment Share on other sites More sharing options...
dbarbee Posted January 2 Share Posted January 2 Thank you for your quick response. I created a new .fpi file from scratch to make sure it wasn't a corrupt file. I also used imposition files that were created with the previous version of Imposer. I am unable to get it to work any way I try. I have also attempted a two step (Stack then Horizontal) and a three step (Stack then Horizontal then Vertical) imposition to no avail. I also attempted declaring a stack size, which did not fix the issue. We did have an earlier version of fusionpro installed on another computer, which composed the project without issue. Quote Link to comment Share on other sites More sharing options...
Alex Marshall Posted January 2 Share Posted January 2 Try specifying the Stack value (Divide total records by n-ups), then UNCHECK Infinite Stack. Recompose and test. Quote Link to comment Share on other sites More sharing options...
dbarbee Posted January 2 Share Posted January 2 Hi Alex, That worked. I thought I had already run that test, but I must have forgot to UNCHECK Infinite Stack. Hope this helps. Quote Link to comment Share on other sites More sharing options...
olllllllo Posted January 2 Author Share Posted January 2 The issue I was running into was from Fusion Imposer 13.1.2, the Infinite stack function in the Step and Repeat module, Acrobat Pro build_2023.008.20423. My apologies, my initial question did not detail the specific part of Imposer I had issue with. The infinite stack was being ignored, in both legacy and newly created .fpi files in FP build 13.1.2. Acrobat Pro build_2023.008.20423 seems to be a real problem with other Plug-ins as well, specifically Pit Stop Pro. I uninstalled Acrobat and re-installed version Adobe Acrobat 2020. Everything works as expected now. I have not tried to update Fusion to the latest build just yet, but will once the critical jobs are out and I can have some cushion time to un-install if needed. Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted January 2 Share Posted January 2 The attached infinite stack job composes correctly for me in FusionPro 13.1.2 on Mac. Can you please verify whether the attached job works for you? Also, can you please collect up a job which reproduces the problem? PresidioPostcard-infinite-stack.zip Quote Link to comment Share on other sites More sharing options...
dbarbee Posted January 2 Share Posted January 2 Your file imposed correctly. Attached is a collected FusionPro document that imposes incorrectly when I compose it. Stack Test.zip Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted January 2 Share Posted January 2 Okay, thank you for attaching that job. It was very helpful to me in identifying the problem. It's an issue when Infinite Stack is set AND the Stack Count is set to 1. So the workaround is to set the Stack Count to anything other than 1, and Infinite Stack will work again. This will be fixed in an upcoming release. Quote Link to comment Share on other sites More sharing options...
olllllllo Posted January 3 Author Share Posted January 3 Thank you Dan and dbarbee. The file I created was overwritten and soon as I downgraded to Acrobat 2020, so it is not available unless I go back to the latest acrobat build, which I will not do. Changing the stack to "2" from "1" fixes the problem in FP 13.1.2. I am going to uninstall and bounce back to the previous version so templates do not have to be altered. Quote Link to comment Share on other sites More sharing options...
dbarbee Posted January 3 Share Posted January 3 Thanks Dan, I tried the workaround, and it didn't resolve the issue. Any other suggestions? Or should I downgrade to a previous version? Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted January 3 Share Posted January 3 9 hours ago, olllllllo said: Changing the stack to "2" from "1" fixes the problem in FP 13.1.2. Thank you for that confirmation. 9 hours ago, dbarbee said: I tried the workaround, and it didn't resolve the issue. Any other suggestions? Or should I downgrade to a previous version? Hmm, it worked for olllllllo. Are you sure you're referencing the FPI file that you changed? If so, please collect and post a job that reproduces the problem. A patch build is in the works and we hope to make it available soon. Apologies for the trouble. Quote Link to comment Share on other sites More sharing options...
dbarbee Posted January 4 Share Posted January 4 I was unable to recreate the issue I was experiencing before. The workaround is a solid solution. Thank You. Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted January 8 Share Posted January 8 This is fixed in the 13.1.3 release, which is now available. Apologies again for this slipping through in 13.1.2. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.