Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] Moab Entrada

2004-08-01 by Allan Chen

For anyone using Entrada (wither bright white or natural) with UT2 inks, 
what curve are you using?  Just curious.  I need to pick a paper for some 
prints someone wants to buy, and am considering Entrada as a fairly 
affordable option.

thanks,
allan

At 12:08 PM 7/30/2004, you wrote:
>Hi Rob,
>
>I've tested Moab Entrada BW and Natural on my Epson 2200 with UC inks 
>against EEM, Epson Velvet Fine Art, Epson Ultrasmooth, PR, and Premier Art 
>Hot Press. For me, personally, the Bright White print characteristics were 
>not to my liking, however, I quickly became entralled with the Natural 
>selection. For B&W, it prints ever so slightly warmer than Epson Velvet, 
>but slightly cooler than Ultrasmooth. Placing the same image printed on 
>Velvet, Ultrasmooth, and Entrada Natural side-by-side in many light 
>condidtions, the EN print just seems to "glow" a little more than the 
>others. Paper color and surface characteristics are very similar to 
>Ultrasmooth.
>
>A very nice paper, indeed. Order a sample pack and test for yourself.
>
>Alan Huntley
>
>P.S. I should mention that I print through IP 5.6.
>
> >
> > From: Robert Krawiec <robk64@...>
> > Date: 2004/07/30 Fri PM 02:15:11 EDT
> > To: digitalblackandwhitetheprint@yahoogroups.com
> > Subject: [Digital BW] Moab Entrada
> >
> > Hi,
> >
> > Does anyone have experience with Moab Entrada papers
> > with either 2200 or UT2 inks? Good? Bad?
> >
> > Thanks,
> >
> > Rob
> >
> > PS I bought the UT2 inks based on the information
> > given on this list and I'm delighted with them. Thanks
> > too to Paul Roark for his curves!
>
>
>
>
>Please visit the Group Homepage to check the Files, and other resources as 
>they are often being updated.
>
>http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint
>
>If you wish to receive no emails or just a daily digest, or you wish to 
>unsubscribe, please edit your Membership preferences by visiting this same 
>page.
>
>Please follow these basic guidelines:
>- As threads develop, trim off excess portions of earlier messages to keep 
>them short.
>- Good manners are required at all time. No personal attacks or flames. 
>Hostile, aggressive or argumentative users may be removed from the 
>membership without notice.
>- Keep your posts and threads related to the group topic of digital B&W 
>printing. Users who persistently make off-topic posts may be removed from 
>the membership.
>- By posting on this forum you agree to abide by the group rules and 
>guidelines, and to abide by the actions and decisions of the group Owner 
>and Moderators. See "Group Topic, Rules and Guidelines" in the Files section:
>http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint/files/
>
>BY PARTICIPATING IN AND/OR POSTING MESSAGES TO THE DIGITAL BW, THE PRINT 
>YAHOO! GROUP YOU EXPRESSLY UNDERSTAND AND AGREE THAT THE "OWNER" AND 
>"MODERATORS" OF DIGITAL BW, THE PRINT YAHOO GROUP SHALL NOT BE LIABLE TO 
>YOU FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR 
>EXEMPLARY DAMAGES, INCLUDING BUT NOT LIMITED TO, DAMAGES FOR LOSS OF 
>PROFITS, GOODWILL, USE, DATA OR OTHER INTANGIBLE LOSSES (EVEN IF 
>THE  "OWNER" AND "MODERATORS" OF DIGITAL BW, THE PRINT YAHOO GROUP HAVE 
>BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), RESULTING FROM: (i) THE 
>USE OR THE INABILITY TO USE THE DIGITAL BW, THE PRINT YAHOO GROUP; (ii) 
>UNAUTHORIZED ACCESS TO OR ALTERATION OF YOUR TRANSMISSIONS OR DATA; (iii) 
>STATEMENTS OR CONDUCT OF ANY THIRD PARTY ON THE DIGITAL BW, THE PRINT 
>YAHOO GROUP; OR (iv) ANY OTHER MATTER RELATING TO THE DIGITAL BW, THE 
>PRINT YAHOO GROUP.
>
>Yahoo! Groups Links
>
>
>
>

------------------------------------
Technology Projects Manager
Academic Computing & The Office of Accessible Education
Stanford University
v - 650-996-0546
f - 650-725-4685

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.