QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- Vipp image shift: My experience with this is, it is file related but you would think that xerox could compensate for the problem. If it is the same problem I am having, it is predictable and can be worked around, and it tends to only be when I send from Fusion pro. On a side note the Nexpress had the issue worst but not with VIPP necessarialy and when I stopped running Nexpress it still was an issue, but again it was predictable and we could work around.
It is a file issue, we hand code VIPP, but the issue doesn't show in IDE or thin printer so one would make the logical leap that it is a printer issue. Also, outputing the files from fusionpro with the same bounding box issue as vipp fixes the issue.
QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- Gadatient pantone to pantone: Is more than likely a file issue. It is a problem for a lot of rips. Not a Xerox only issue from my experiences.. The is usually workaround..
It is a Postscript 3 limitation not a file issue. Indigo and Nexpress have the problem fixed. Xerox still wants to blame the file. The net of it is that the Creo is rendering the transistion from one pantone to the next if it is not 50% is inverted...
QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- Drop shadows and Trans: This IS a file issue not only here but in the industry. I have seen it on every rip I have been around and there is almost always a work around and as long as you follow the work arounds it shouldn't be a problem. If you look at Adobes forum for, like indesign (biggest), you will no doubt find a lot of post regarding transparencies. The biggest problem you will find in digital is when you have a process color (such as a drop shadow) going over a spot color (you will have to convert spot color to process 1st).
This is also fixed with Indigo and Nexpress and yes, it is a CPSI Adobe issue, yet 2 other vendors have come up with ways to "fix" the issue until PDF based ripping occurs.
QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- Trapping of CT to pantone: Yes again file issues.. Is an industry issue, not just Xerox. Should the software know haw to handle these?? Yes I think all these ripps out there have had enough time to address and come up with something, but most just have work arounds.
Again, HP Indigo and Nexpress do not have these issues. So it leaves it back in Xerox's lap and all cheap laser printers that also have this issue. The heart of the matter is HP and Kodak "had" these issues and responded with fixes, not the Xerox line of its a file issue...
QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- FONTS - AH! FONTS..... Not a Xerox issue either. Industry problem. I don't see this being fixed ever - PDFs must be made correctly with the fonts embedded. PDF workflow is the way of the future and the process we use here. Educate your clients on how to make a good PDF and your worries will dissapear..
Although not a Xerox issues per sea, it is a bad adobe library that creo has had for over 18 months. The fonts are referenced correctly, but the Creo pukes on it. THis is a creo only issue, thus the reason you don't see it on your DocuSP
QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- Graininess of solids: The only grain I see is the grain of the paper but it is only with screens of solid colors... Papers have an inheirent grain that will show, especially in the lower quality papers. Example uncoated cougar stock will show a grainy and mottle look on solids, but if you print the same file on something like Hammermill color copy its perfect.. Paper plays a big role here..
Do a solid purple, print out the pantone gamut on a smooth coated stock and tell me you don't see dirty colors, especially in yellows and reds. It may not be obvious and excusable, until you hold it up to offset or Nexpress.
QUOTE(Dale Zahnke @ Jul 7 2006, 08:12 AM) [snapback]332[/snapback]
- Streaks: I had this problem and they did several things to the machine to fix it. The thing that made the biggest impact was an adjustment where (I think) they calibrated/adjusted the laser?? Anyway once they did that my problems been gone for months now..
Yeah, they "fix" it for a bit but the issue keeps coming back.
A DocuSP does shelter you from a lot of the Creo issues. Since Kodak bought Creo things have been really slow in solving these Creo only issues.
We now have a Kodak Nexpress 2500 next to the iGen3 and I can tell you without a shadow of a doubt all these issues do NOT exist on the Nexpress. Hard to say they are file issues.
QUOTE(Tracey @ Jul 7 2006, 08:28 AM) [snapback]336[/snapback]
On your streaks and lines, what do they look like, can you describe them?
We have been experiencing different streaks and lines also. Most have been traced back to the Wire Mods & Power supply boards as the problem. They seemed to get bad after 2.2 upgrade, yet there has been no admittance that this is a factor in the cause. We have had all the gears replaced in the developer housings both the Idler gears (front of housing and Drive gears (rear of housings) this seemed to help in board out board bands but no effect on our process direction streaks. We have had new Power supply boards put in the machine for all colors to minimize Harmonic Streaks A wide Fuzzy edge modulated streak that can shift spots on the sheet depending on the wire mod on the affected housing. I am not sure that the boards have made that big of difference in the streaks because they are still coming and going depending the age and condition of the wire mods. Basically we are rotating and playing trial and error with the wire mods until the streaks are minimized to the point they are not effecting the job I am printing at the time. I have also had very fine line streaks that have only showed in one color but have traced back to the PR Belt as the cause even when the lines were not visable on the belt.
We have had every kind of streak, the fact is Xerox can "fix" them but after a few weeks to months they creap back in. Fuser, wire mod, super wire mod failure, doner rolls, PR belt, harmonic calibration of the LED's and much more have been blamed for the streaks and noise.
QUOTE(Tracey @ Jul 7 2006, 08:28 AM) [snapback]336[/snapback]
Fusing issues, Does this stay consistent through out a run or does it go away after a few sheets? We have been experiencing a fusing problem mainly on our 14.33 x 20.5 coated press sheets and sometimes on 12 x 18 sheets on the inboard edge, where the first couple of sheets may not fuse across the entire sheet. The problem started a year ago and basically they have attributed it to us shifting stock sizes and the build up of fuser fluid on the inboard edge of the fuser roll, until that smooths out the ink does not fuse properly to the paper. Usually this is on the first 10- 20 sheets, then the ink fuses properly. Xerox cannot expain why we had no problem for a year and then the problem began occuring. They also tried to blame our paper, but we had been running the same paper for a year without any problems, so I wouldn't let them get away with that as the reason, especially when it would start fusing after a few sheets. However, We have tested some stocks that the ink would not fuse to 100% of the time and that was the result of the paper not holding the charge properly where we would see image drop outs occuring every so often through out the press run.
What is your average impression life of the fuser roll?
It does come and go throughout a run. It started when they swapped out the ceramic doner rolls in the fuser for the metal ones. Xerox claims it shouldn't be that, but my gut tells me metal doesn't hold heat as well as ceramic, so its got to be inconsistent heat to the surface of the fuser due to the metal.
Oh and Xerox always blames paper, even if it is on the RML...
QUOTE(Tracey @ Jul 7 2006, 08:28 AM) [snapback]336[/snapback]
Phantom Jams - I have actually heard about this at another account under 2.0. It was traced back to a Image Transmission Fault ( Pops on status screen then disappears) - Check Log only faults in Administration window for faults attributed to this when it occurs and give service that code to research ( it may say IDIC fault in a particullar color). We were also warned to clean the feeder sensors (Horseshoe shaped sensor at mouth of each feeder) for paper dust build up which has been known to cause Phantom Jams. We have gotten a few of these every now and then but not so many to become a major issue.
Good info, but our logs don't show the ITF, I'll check the feed sensors, but Xerox has told me that they have fixed this in the next version, go figure.
QUOTE(Tracey @ Jul 7 2006, 08:28 AM) [snapback]336[/snapback]
VIPP Bounding box issue - By chance did the affected files originate in InDesign? If so, we have seen this, unfortunately there is no resolution other than to make sure file coming out of InDesign is at final print size other wise the shifts occur.
Sadly, the file orgininated in powerpoint and was hand coded in VIPP. It is a file issue, but as I said above, the IDE and thin printer do not show the issue.
QUOTE(Tracey @ Jul 7 2006, 08:28 AM) [snapback]336[/snapback]
Indesign & Transparency issues - Convert all spots to CMYK and make sure Transparent Photoshop images are exported to EPS files on a transparent background. Turn off Pantone Processing Enabled on DFE. These are the only work around fixes we have for this problem, other than trial and error.
The issue is how the Creo interprets unequal pantone to pantone colors, it is inverted... Yes, turning off pantone processing works, but then all solid areas are off. BTW, Indigo, Nexpress and DocuSP handle the color correctly.
QUOTE(elmo3 @ Jul 7 2006, 06:11 AM) [snapback]324[/snapback]
Why not?
Regarding font missing issues in PDF: are the fonts embedded, or merely reference calls?
If reference calls, do the PDFs originate on a Windows platform? Are the PDFs then transferred to a Unix system at any point in their lives?
Why not? Its a 100k cost option to fix something the DFE should do normally, plus, DocuSP doesn't have these issues, so why?