ReminderVDP

I sent this problem to Alex and Doug over a year ago. I attached a screen shot of our current compositions in 9.3.36 and one from 10.0.3. The 10.0.3 is the PDF on top.

Doug and Alex know of this issue and they didn't respond when I asked them 6 months back about the pixel shift and if there was a fix for it.

Thanks Dan. I think I may have found a work around. It seems like certain settings in the advanced options change the edge from short to long. I'll try it again when we upgrade to version 10.

I made one change to the imposition file and it switched to long edge and I can't get it back to short edge.

Thanks Aaron. That worked. I need to make one change and I'm hoping that doesn't break it. I had tried making a new imposition several times and it always went back to the long edge. I've never seen this before with the Imposer software.

Aaron, I tried it with Rotation off and it doesn't work that way either. It still defaults to long edge even when I choose short edge. I must have forgot to turn off the rotation on the file I attached here. Sorry about that. I opened the file you attached and composed with it and page 2 is rotated 180 degrees. And it changed to long edge after I chose short edge.

I am having an issue with an Imposition I am building for a Rollem slitter. I have it set up on the sheet how I want it but the Duplexing choice keeps staying on Long edge when I choose Short Edge and hit okay. The next time I go into the options, it's back to Long Edge and both choices are checked. Is there any way to fix this? I'm getting the second page of the document rotating 180 degrees because of this. I did not have this problem last week when I started building the imposition layout. I'm attaching the Imposition file here to look at.Imposition_PC_5.5X8.5_ROLLEM.fpi

Dan, I changed the white text to black on our front cover image with the drop shadow at 100% and it still doesn't work in the preview or when it's composed. The black text on the inside front cover that is all black previews with the drop shadow but doesn't compose on the server with a drop shadow. I did also do a search and looked through old posts and didn't find the info I needed.

Our entire magazine is variable images. I did get the text to preview with the drop shadows but then it didn't compose with any drop shadow. I'll chalk it up as this feature works as well as text wrap.

I'm trying to see if the drop shadow feature actually works on a text frame for white type. I keep getting the drop shadow around the inline image and not on the text in the text frame. I made sure I had the drop shadow box checked on the Composition settings and composed one record and there are no drop shadows. I've never been able to get this to work before so if anyone is using it properly, please let me know if I'm missing a setting or a check box somewhere.

I've managed to recreate this issue a second time in FusionPro 10 API. I will send a data file to the hot folder that has maybe 1,100 records total in the file. It will start composing. The files are fine and then around record 500 or 600, the fonts stop embedding in the output PDF. The files keep writing until they are all composed and there is nothing in the msg file about a font error or embedding issue. We output our files in batches of 100 records so 200 pages per file, each page is different. Has anyone else experienced this with version 10? I'm using 10.0.16 right now. The first time this happened was in version 10.0.3. Same exact issue.

You mention Producer and a server but you say that the plug in succeeded. Are you composing from the desktop or composing on the server? And did you compose locally and it composed the entire job? The amount of ram and space on the server doesn't matter. We had, still have, a server that is only running FusionPro server at the time and it still failed. Our server has more ram and space than what is required for the server version back then. It's an issue with the hand off from the desktop to the server for composition. We checked our network speeds and ran all types of tests on that to see if that was the issue and it's not. I can find you 2 or 3 other posts including our original post that explains this issue. http://forums.pti.com/showthread.php?p=14419#poststop I saw one earlier that mentioned your problem going all the way back to version 7.2.

I'm a little confused that you say that it fails at the pre-compose but composes 5,000 records. So, does it compose, just not all the records? We had a similar issue to this a few years back. We were having compositions not composing when the data was transferring from our Mac or PC to the server. There was too much data to pass from the computer to the server. It failed at the hand off to the server and would not even start composing. Our solutions: 1. We broke down our data files into 50,000 record chunks and composed from that. And our data files have almost 200 data fields and we have photos and advertisements all over the layouts. 30-ish MB two page layouts. We break our composed files down into 100 records also. 2. We eventually upgraded to Server API to avoid that hand off from the computer and everything is composed right on the server. We have not had a problem since.

That works great. Thanks again. If I were to strip the file extension from the folder name, would that happen in the variables? I tried it in the file path and it didn't do anything.

Step, Thanks again for your help. The part where I said the data file names don't have the same number of input slots is because we have proof files so when I have input[0], input[2] and I added an input[3], I get 20170405A_PC_test_undefined-.txt because we don't list the record numbers in the proof file names. As long as the files list the record numbers, I don't get an _undefined in the folder name. Minor annoyance but we could just change our naming of the files.

I got it to work. The only issue I see is that all our data file names don't have the same number of input slots. Thanks for your help!

Step, Would that work for all the file names? This is a list of all the file names that I would need to compose to the correct folders: 20170405A_STD_DM_1-50000-.txt 20170405A_STD_DM_50001-100000-.txt 20170405A_STD_DM_100001-150000-.txt Would it work for when the file name changes to a B after the run number? We alternate weeks from A to B on an 8 week cycle.

I'm working on a rule to output files to a specific directory based on the letter designation on a data file. And I'm getting some odd errors that I have never got before and I'm not certain my regex is correct for what I need to do. Our data files are named as the following: 20170405(A or B)_STD_(PC or DM)_record numbers-.txt i.e. 20170405A_STD_PC_1-20000-.txt I'm looking to place these in the following location: D:\FPDirect\Submitted\RUN 20170405A\20170405A_PC_ALL I started with the following code in a OnJobStart rule and it returned code 1071. I tried it in a OnRecordStart rule and it returned code 1112. Here is what I am trying in the rules. I'm a novice at regex so bear with my code if it is completely wrong. ------------ FusionPro.Composition.inputFileName = '[^2[0-9][0-9][0-9][0-9][0-9][0-9][0-9]A_STD_PC_1-[0-9][0-9][0-9][0-9][0-9]-.txt$]') FusionPro.Composition.outputFileFullPathName = 'D:\FPDirect\Submitted\[^RUN 2[0-9][0-9][0-9][0-9][0-9][0-9][0-9]A\2[0-9][0-9][0-9][0-9][0-9][0-9][0-9]A_PC_ALL$]' Any help would be appreciated. I am using the hot folders for the new Web Services dashboard and leaving the Output File location blank.

Dan, Is there a fix for the pixels shifting when something is composed in 10.0.3? I have sent this problem to Support and have not heard anything about a fix or a solution to the shifting.

Has there been any reports of version 10.0.3 software moving the image on a body page up a few pixels? I have composed the same files in API versions 9.3.36 and 10.0.3 and the images move up a few pixels in version 10.0.3 making PDF comparisons almost impossible. I sent a screen shot to support and have not heard anything back.

Dan, We figured it out. The Producer components were not installed the first time.

I received an error that I can't find listed in the Producer documentation. When I start composing it gives me the error: "Connect failed with the error 10061". Has anyone seen this before or know what the error is for? Thanks

I go to the Compose Tab in FusionPro Designer, Under the Output Tab, there is an option to check "Create Bookmark for each record". That is not selected and it was not selected on the job composed one minute before that. Also, there is no where in the Config file that mentions that the composition includes bookmarks. See original post where I said it was composed in Producer 9.0.3. See previous paragraph in this post on how I created the composition.

Thanks Dan. The Create Bookmarks for each record is not checked under the Output tab though.

I composed two jobs consecutively last week and the second one finished with a Output format: VPDF in the Job Completion email I received. I asked Support about this and they told me it was from another piece of software. It's from FusionPro Producer 9.0.3, not another software. Has anyone experienced this before? Does it cause problems for RIP software?