$0.00

Knowing When to Duplicate

Knowing when to duplicate your project as opposed to replication can be pretty simple to figure out. In general, if you need less than a 1000 copies of the same master, then duplication is the method to use.

An example of this would be if you 5 masters and need 20 copies of 1 and then 40 of the other 4 each. Smaller quantities will always be better and cheaper to duplicate. Replication does not become cost effective until you get to the 1000 or more number.

Another good reason to duplicate is if you have a master that may change in a short period of time, for instance software companies. With the high definition printing and lacquer coating of duplicated discs, it is really hard to tell the difference between a replicated or duplicated disc. Instead of committing to pressing a large number of discs, you have have smaller batches duplicated so that when the master changes, you don't have large quantities of old mastered discs sitting around.

You can use our Wizard Helper to figure out which is best for your project.

1054 - Unknown column 'reviews_status' in 'where clause'

select count(*) as count from reviews r, reviews_description rd where r.products_id = '145' and r.reviews_id = rd.reviews_id and rd.languages_id = '1' and reviews_status = 1

[TEP STOP]