<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: New Products Coming</title>
	<atom:link href="http://blog.razerzone.com/2005/10/10/new-products-coming/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.razerzone.com/2005/10/10/new-products-coming/</link>
	<description>Latest Happenings Around the Razer World.</description>
	<pubDate>Thu, 24 Jul 2008 17:54:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Jonathan</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-1710</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 14 Sep 2006 09:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-1710</guid>
		<description>Apparently I can't stop posting. I'm typing this from a basic Linux system (main system's HD died, and I don't have a replacement yet), and the right side buttons also scroll there, in exactly the same way. When holding one down (left?) it first sends three scrolls at perhaps four/sec, and then it increases to about 30/sec. Does anyone who still reads this know what's up?

Oh, and because it's easy to configure on Linux I can confirm that it works very well with 2 ms (500 Hz) polling. At least the mouse interface came with new valid-looking data every 2 ms. Unfortunately this system isn't very suitable for games.</description>
		<content:encoded><![CDATA[<p>Apparently I can&#8217;t stop posting. I&#8217;m typing this from a basic Linux system (main system&#8217;s HD died, and I don&#8217;t have a replacement yet), and the right side buttons also scroll there, in exactly the same way. When holding one down (left?) it first sends three scrolls at perhaps four/sec, and then it increases to about 30/sec. Does anyone who still reads this know what&#8217;s up?</p>
<p>Oh, and because it&#8217;s easy to configure on Linux I can confirm that it works very well with 2 ms (500 Hz) polling. At least the mouse interface came with new valid-looking data every 2 ms. Unfortunately this system isn&#8217;t very suitable for games.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-1426</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Thu, 24 Aug 2006 23:41:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-1426</guid>
		<description>Ah, the these pages are working again. I have a Diamondback now, and found that the main drawback is its sensitivity to non-perfect surfaces. After some experimenting (holding above the surface, pointing at a distant light, etc) I have concluded that it seems to travel in straight lines until the deviation passes a threshold, and that threshold depends on the quality of the sensor readings. On a good surface it can track very well at the advertised 1600 CPI, but even then on bad spots the effective resolution is more like 800 CPI (to those with a bad understanding, the 'speed' doesn't go down), and it can get a bit over-excited.

The above implies that *I* (not the mouse) had no problems with that resolution, on this low-friction surface. :-)

That said, its long-distance tracking is pretty good, and it didn't get confused in my maximum tracking speed tests. I've moved it at speeds where the individual reports said something in the 700-800s at 125 Hz. Speeds that high (which need only 11 bits at 125 Hz; as mentioned 16 and 12 bits are more than enough for now) are not generally useful for anything, but the good long-term tracking is quite useful in games, and during stalls because the resulting position is more predictable. It also hasn't forced me to look down for 3 seconds yet, let alone when someone with rockets is approaching.

The shape of the two big buttons was clearly made for the first two fingers next to the thumb. It's not really bad when you have your middle finger on the scroll wheel and ring finger on the right button (reverse if you use your left hand), but you'll miss some comfort. After a bit of use I've noticed that the spots where my fingers rest on the main buttons have been reflecting less light in the diffuse way but more in specular. I.e. it makes them look darker but shinier.

On Mac OS X buttons 6 and 7 (the right-side buttons) are mapped to the scrolling axis at a low level, so you can't just have a button 6/7 without changing the system (AFAIK). The Razer driver offers some configuration, but the only potential way to get to get the buttons is pass-through, and as you can guess the system alters that. Regarding the Razer driver, if I set everything to pass-through, it refuses because it wants at least one "click"; it doesn't see a button 1 pass-through as click.</description>
		<content:encoded><![CDATA[<p>Ah, the these pages are working again. I have a Diamondback now, and found that the main drawback is its sensitivity to non-perfect surfaces. After some experimenting (holding above the surface, pointing at a distant light, etc) I have concluded that it seems to travel in straight lines until the deviation passes a threshold, and that threshold depends on the quality of the sensor readings. On a good surface it can track very well at the advertised 1600 CPI, but even then on bad spots the effective resolution is more like 800 CPI (to those with a bad understanding, the &#8217;speed&#8217; doesn&#8217;t go down), and it can get a bit over-excited.</p>
<p>The above implies that *I* (not the mouse) had no problems with that resolution, on this low-friction surface. <img src='http://blog.razerzone.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>That said, its long-distance tracking is pretty good, and it didn&#8217;t get confused in my maximum tracking speed tests. I&#8217;ve moved it at speeds where the individual reports said something in the 700-800s at 125 Hz. Speeds that high (which need only 11 bits at 125 Hz; as mentioned 16 and 12 bits are more than enough for now) are not generally useful for anything, but the good long-term tracking is quite useful in games, and during stalls because the resulting position is more predictable. It also hasn&#8217;t forced me to look down for 3 seconds yet, let alone when someone with rockets is approaching.</p>
<p>The shape of the two big buttons was clearly made for the first two fingers next to the thumb. It&#8217;s not really bad when you have your middle finger on the scroll wheel and ring finger on the right button (reverse if you use your left hand), but you&#8217;ll miss some comfort. After a bit of use I&#8217;ve noticed that the spots where my fingers rest on the main buttons have been reflecting less light in the diffuse way but more in specular. I.e. it makes them look darker but shinier.</p>
<p>On Mac OS X buttons 6 and 7 (the right-side buttons) are mapped to the scrolling axis at a low level, so you can&#8217;t just have a button 6/7 without changing the system (AFAIK). The Razer driver offers some configuration, but the only potential way to get to get the buttons is pass-through, and as you can guess the system alters that. Regarding the Razer driver, if I set everything to pass-through, it refuses because it wants at least one &#8220;click&#8221;; it doesn&#8217;t see a button 1 pass-through as click.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cary</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-1058</link>
		<dc:creator>Cary</dc:creator>
		<pubDate>Mon, 08 May 2006 10:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-1058</guid>
		<description>I just ordered the white pro pad and a copperhead, I see you mention that the copperhead works perfectly with the exact mat now, does it work perfectly with the white pro pad also?  Also, since the white pad gets dirtier does that effect tracking also?

Thanks,

Bostton1


"Razerguy Says: 

April 11th, 2006 at 2:13 pm 
Yes, anodized aluminum is much longer wearing than plastic … about 3 to 5 times longer wear, plus as you mentioned there is 2-sides that if used can possibly outlive you and your system:)

The Pro Pad is made of the same mateial as the eXactMat but the white surface is harder to keep clean. I’d suggest the eXactMat for gaming and the Pro Pad for office use.

Since my original post we have been able to adjust the laser performance on the Copperhead to track perfectly on the eXactMat and the eXactMat laser has been dropped from the development list.

If you purchased a Copperhead today the tracking on the eXactMat will not be a problem."
</description>
		<content:encoded><![CDATA[<p>I just ordered the white pro pad and a copperhead, I see you mention that the copperhead works perfectly with the exact mat now, does it work perfectly with the white pro pad also?  Also, since the white pad gets dirtier does that effect tracking also?</p>
<p>Thanks,</p>
<p>Bostton1</p>
<p>&#8220;Razerguy Says: </p>
<p>April 11th, 2006 at 2:13 pm<br />
Yes, anodized aluminum is much longer wearing than plastic … about 3 to 5 times longer wear, plus as you mentioned there is 2-sides that if used can possibly outlive you and your system:)</p>
<p>The Pro Pad is made of the same mateial as the eXactMat but the white surface is harder to keep clean. I’d suggest the eXactMat for gaming and the Pro Pad for office use.</p>
<p>Since my original post we have been able to adjust the laser performance on the Copperhead to track perfectly on the eXactMat and the eXactMat laser has been dropped from the development list.</p>
<p>If you purchased a Copperhead today the tracking on the eXactMat will not be a problem.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-957</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Mon, 01 May 2006 20:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-957</guid>
		<description>The IR sensor performs better? Good to know.

Thanks for the info!</description>
		<content:encoded><![CDATA[<p>The IR sensor performs better? Good to know.</p>
<p>Thanks for the info!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Razerguy</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-956</link>
		<dc:creator>Razerguy</dc:creator>
		<pubDate>Mon, 01 May 2006 19:20:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-956</guid>
		<description>I stand corrected however the forum you refer to dates back to August of 2004. Since then we have updated both the drivers and the sensors and if there were any problems they would have been more recent reports. If you are looking for the best Diamondback available I would highly recommend the Plasma or the new Acid Green as they feature the higher performing IPS infrared sensor which performs at much higher IPS than we actually state on the box.

What's interesting about the Mantis is that we have pro players swearing about its performance at both high and low sens games.

Sorry but you'll have to do a search in and around Southern Flevoland for traditional retailers or you can contact our major EU distributor online through our EU store.</description>
		<content:encoded><![CDATA[<p>I stand corrected however the forum you refer to dates back to August of 2004. Since then we have updated both the drivers and the sensors and if there were any problems they would have been more recent reports. If you are looking for the best Diamondback available I would highly recommend the Plasma or the new Acid Green as they feature the higher performing IPS infrared sensor which performs at much higher IPS than we actually state on the box.</p>
<p>What&#8217;s interesting about the Mantis is that we have pro players swearing about its performance at both high and low sens games.</p>
<p>Sorry but you&#8217;ll have to do a search in and around Southern Flevoland for traditional retailers or you can contact our major EU distributor online through our EU store.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-955</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Mon, 01 May 2006 19:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-955</guid>
		<description>Only Diamondback: fine, it looks OK for now anyway.

Pixel skipping:

Well, I came across this:
http://razer.tigga.org/phpBB2/viewtopic.php?t=3400
which links to these:
http://razer.tigga.org/phpBB2/viewtopic.php?t=3409
http://razer.tigga.org/phpBB2/viewtopic.php?t=3354
(yes, they're old)

Apparently it thinks direction changes are jitter, and when you finally move it enough it can skip over the pixel it's been ignoring. It's at a small scale, but I am considering a higher-CPI mouse with a reason: I have much more control than the 400 CPI of my current mouse. I.e. I can make many small movements without moving the pointer. And in games I find that I'm sometimes fighting to get a pixel on a target that's far away. It's not that I don't have pixel-precise control, it's that at the sensitivity required by my current surface space/tracking speed limitations (not much of a problem with the Diamondback and a large surface, I guess), combined with 400 CPI, a pixel becomes too large. But, umm, the point is that I think I'd be able to use its 1600 CPI, and notice imperfections at that scale.

It was apparently fixed by a driver update. Is that in the sense of trying to detect common problem patterns and doing what seems best, or perhaps updating firmware? I found that the sensor uses a small program that the controller sends to it to detect movement, so the latter might be possible if there's some interface to update it. I also found that the Diamondback used an early version of that sensor (to be the first). Could that be different in current versions? I've taken a look at the driver and found some evidence in one of its files (the one that would end up at /System/Library/Extensions/RazerPRODriver.kext/Contents/Resources/Info.plist): it mentions two different mice (Razer PRO v1/v2), gives some hints that each is a Diamondback, and the difference is in the product ID. Still, even if it's not fixed perfectly, it's a big improvement over what I have now, especially considering tracking speed which can make low sensitivity more useful on a larger surface.

Polling rate: I've read about people using it at a higher rate, and getting real updates between 500–1000 Hz. It might not be official, but it seems it does support it. But still I can make no guess how much it'd help (or how I could get it working here for that matter…). It's certainly not preventing saturation of the giant 16-bit deltas, simply because there's no way to saturate them.

Surface: ah yes, I can imagine the Mantis Control works well at low sensitivity, for which there is enough space. Combined with fine control (if friction doesn't get in the way) that could make for some interesting precision without significantly compromising the ability to make large turns quickly.

I think it'd be best if I could try all of this. Any idea where that's a possibility in the Netherlands, near Southern Flevoland? It's hard to find out.</description>
		<content:encoded><![CDATA[<p>Only Diamondback: fine, it looks OK for now anyway.</p>
<p>Pixel skipping:</p>
<p>Well, I came across this:<br />
<a href="http://razer.tigga.org/phpBB2/viewtopic.php?t=3400" rel="nofollow">http://razer.tigga.org/phpBB2/viewtopic.php?t=3400</a><br />
which links to these:<br />
<a href="http://razer.tigga.org/phpBB2/viewtopic.php?t=3409" rel="nofollow">http://razer.tigga.org/phpBB2/viewtopic.php?t=3409</a><br />
<a href="http://razer.tigga.org/phpBB2/viewtopic.php?t=3354" rel="nofollow">http://razer.tigga.org/phpBB2/viewtopic.php?t=3354</a><br />
(yes, they&#8217;re old)</p>
<p>Apparently it thinks direction changes are jitter, and when you finally move it enough it can skip over the pixel it&#8217;s been ignoring. It&#8217;s at a small scale, but I am considering a higher-CPI mouse with a reason: I have much more control than the 400 CPI of my current mouse. I.e. I can make many small movements without moving the pointer. And in games I find that I&#8217;m sometimes fighting to get a pixel on a target that&#8217;s far away. It&#8217;s not that I don&#8217;t have pixel-precise control, it&#8217;s that at the sensitivity required by my current surface space/tracking speed limitations (not much of a problem with the Diamondback and a large surface, I guess), combined with 400 CPI, a pixel becomes too large. But, umm, the point is that I think I&#8217;d be able to use its 1600 CPI, and notice imperfections at that scale.</p>
<p>It was apparently fixed by a driver update. Is that in the sense of trying to detect common problem patterns and doing what seems best, or perhaps updating firmware? I found that the sensor uses a small program that the controller sends to it to detect movement, so the latter might be possible if there&#8217;s some interface to update it. I also found that the Diamondback used an early version of that sensor (to be the first). Could that be different in current versions? I&#8217;ve taken a look at the driver and found some evidence in one of its files (the one that would end up at /System/Library/Extensions/RazerPRODriver.kext/Contents/Resources/Info.plist): it mentions two different mice (Razer PRO v1/v2), gives some hints that each is a Diamondback, and the difference is in the product ID. Still, even if it&#8217;s not fixed perfectly, it&#8217;s a big improvement over what I have now, especially considering tracking speed which can make low sensitivity more useful on a larger surface.</p>
<p>Polling rate: I&#8217;ve read about people using it at a higher rate, and getting real updates between 500–1000 Hz. It might not be official, but it seems it does support it. But still I can make no guess how much it&#8217;d help (or how I could get it working here for that matter…). It&#8217;s certainly not preventing saturation of the giant 16-bit deltas, simply because there&#8217;s no way to saturate them.</p>
<p>Surface: ah yes, I can imagine the Mantis Control works well at low sensitivity, for which there is enough space. Combined with fine control (if friction doesn&#8217;t get in the way) that could make for some interesting precision without significantly compromising the ability to make large turns quickly.</p>
<p>I think it&#8217;d be best if I could try all of this. Any idea where that&#8217;s a possibility in the Netherlands, near Southern Flevoland? It&#8217;s hard to find out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Razerguy</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-954</link>
		<dc:creator>Razerguy</dc:creator>
		<pubDate>Mon, 01 May 2006 16:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-954</guid>
		<description>Currently only the Diamondback supports Mac OS drivers. There hasn't been any reports of pixel jumping on the Diamondback as far as I know. The Diamondback only supports USB polling rate at 125hz. Many pro gamers are using the Mantis Control as there is a reported difference in tracking and control over our other mats.</description>
		<content:encoded><![CDATA[<p>Currently only the Diamondback supports Mac OS drivers. There hasn&#8217;t been any reports of pixel jumping on the Diamondback as far as I know. The Diamondback only supports USB polling rate at 125hz. Many pro gamers are using the Mantis Control as there is a reported difference in tracking and control over our other mats.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-931</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Sat, 29 Apr 2006 20:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-931</guid>
		<description>As of lately I've been looking for a better mouse, because my current low-end one is getting more and more annoying, and Razer looks interesting. I'm currently using Mac OS X (grown up with Macs; and yes, I've been able to map mouse counts directly to pixels) so my choice is basically the Diamondback or the pro equivalent. Some questions:

Pixel skipping/high jitter threshold: what exactly happened to that?

Polling rate: what would be used in my situation? What is the actual improvement I read about caused by? I can only conclude that the delay difference is relatively small, and that a higher rate would be more synchronized with the screen.

Surface: is there a tracking difference between the ProPad and the eXactMat, although I think it doesn't really matter? How do they compare to the Mantis/Everglide Titan? ((effective) static/sliding friction, potential tracking problems, wear)

And last but not least, could there be coming anything of interest to me in the near future?</description>
		<content:encoded><![CDATA[<p>As of lately I&#8217;ve been looking for a better mouse, because my current low-end one is getting more and more annoying, and Razer looks interesting. I&#8217;m currently using Mac OS X (grown up with Macs; and yes, I&#8217;ve been able to map mouse counts directly to pixels) so my choice is basically the Diamondback or the pro equivalent. Some questions:</p>
<p>Pixel skipping/high jitter threshold: what exactly happened to that?</p>
<p>Polling rate: what would be used in my situation? What is the actual improvement I read about caused by? I can only conclude that the delay difference is relatively small, and that a higher rate would be more synchronized with the screen.</p>
<p>Surface: is there a tracking difference between the ProPad and the eXactMat, although I think it doesn&#8217;t really matter? How do they compare to the Mantis/Everglide Titan? ((effective) static/sliding friction, potential tracking problems, wear)</p>
<p>And last but not least, could there be coming anything of interest to me in the near future?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Razerguy</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-870</link>
		<dc:creator>Razerguy</dc:creator>
		<pubDate>Tue, 25 Apr 2006 18:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-870</guid>
		<description>Good idea ... a black and blue combo would be sweet. FYI on www.razerpro.com there is a white version available called the ProPad.

I'll see what we can do about offering some images of the Pro Tools images on our gallery. Maybe Razer Blueprints can do this for us as their product gallery is pretty complete.

Because of the anti-ghosting multi-button binds (chording) capability the Tarantula backlighting will be limited ... you can't backlight keys that are chordable (if that's a real word). There will be an accessory sold that will allow you to top light the Tarantula ... more info to come on this after market product later.

There are no plans on offering a full Razer PC but we never say never to anything. If we ever do that it will be ultimate.</description>
		<content:encoded><![CDATA[<p>Good idea &#8230; a black and blue combo would be sweet. FYI on <a href="http://www.razerpro.com" rel="nofollow">http://www.razerpro.com</a> there is a white version available called the ProPad.</p>
<p>I&#8217;ll see what we can do about offering some images of the Pro Tools images on our gallery. Maybe Razer Blueprints can do this for us as their product gallery is pretty complete.</p>
<p>Because of the anti-ghosting multi-button binds (chording) capability the Tarantula backlighting will be limited &#8230; you can&#8217;t backlight keys that are chordable (if that&#8217;s a real word). There will be an accessory sold that will allow you to top light the Tarantula &#8230; more info to come on this after market product later.</p>
<p>There are no plans on offering a full Razer PC but we never say never to anything. If we ever do that it will be ultimate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ASSASYN</title>
		<link>http://blog.razerzone.com/2005/10/10/new-products-coming/#comment-859</link>
		<dc:creator>ASSASYN</dc:creator>
		<pubDate>Mon, 24 Apr 2006 21:14:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.razerzone.com/?p=18#comment-859</guid>
		<description>Will Razer ever offer a different color scheme for the exact mat logos? Black and green is not very common in most custom PCs and I like to coordinate my whole system.

Could you also provide some pictures of what a pro-tools modified Copperhead looks like? If I am going to void my warranty I would at least like to see why I am doing it and weight its worth.

Will the tarantula be backlit? In the prvided image I only see a few keys lit not the whole board.

RaZeR RoX...the way you guys are going I will have a full Razer PC</description>
		<content:encoded><![CDATA[<p>Will Razer ever offer a different color scheme for the exact mat logos? Black and green is not very common in most custom PCs and I like to coordinate my whole system.</p>
<p>Could you also provide some pictures of what a pro-tools modified Copperhead looks like? If I am going to void my warranty I would at least like to see why I am doing it and weight its worth.</p>
<p>Will the tarantula be backlit? In the prvided image I only see a few keys lit not the whole board.</p>
<p>RaZeR RoX&#8230;the way you guys are going I will have a full Razer PC</p>
]]></content:encoded>
	</item>
</channel>
</rss>
