Activity Feed Forums Printing Discussions Mimaki Printers New Problem with mimaki jv3

  • New Problem with mimaki jv3

    Posted by Taroon Mistry on April 1, 2011 at 11:35 am

    Afternoon All

    After a crazy thursday trying to print a file, I thought id post it up and see if someone else has had these problems

    Print starts ok then half way through this starts, black bands appearing

    had it before with some poor jpg files

    and we have printed over 30metres in a straight run with our own artwork before

    just wanted to know if anyone has had this problem before

    cheers

    T


    Attachments:

    Stafford Cox replied 12 years, 11 months ago 6 Members · 7 Replies
  • 7 Replies
  • Karl Williams

    Member
    April 1, 2011 at 11:43 am

    Which software did you use to generate the artwork and what file type are you printing?

  • David Rowland

    Member
    April 1, 2011 at 12:35 pm

    is it an early version of corel draw with a transparent image around that area?

  • Kev Mayger

    Member
    April 1, 2011 at 12:40 pm

    Looks like a rip error

  • Taroon Mistry

    Member
    April 1, 2011 at 1:22 pm

    Afternoon all…

    The File was created on a clients PC using flexisign or something.

    and exported out as a RGB jpg. the print itself was 8m long

    but this occured at 50% print on the rip…

    I think it was the file that is corrupt or not rendered properly given its such a large file to print….

    just wondering if someone has had this problem before.

    thanks for all the help and advice

    T

  • Jamie Wood

    Member
    April 1, 2011 at 1:36 pm

    I don’t know which RIP you are using, but we find that RGB JPG files can be flaky in
    Onyx, so whenever possible, I convert them to CMYK.

  • Karl Williams

    Member
    April 1, 2011 at 6:27 pm

    I’d say it was a fault with the file. If you can turn the image to a wire-frame, this might just show the problem.

  • Stafford Cox

    Member
    June 10, 2011 at 1:13 pm

    I haven’t logged on to here for a while and just noticed this post. This does look like a data related error. Did you get it resolved in the end?

    Stafford

Log in to reply.