Dave Helmly
Forum Replies Created
-
It’s Thunderbolt 2 . The large connector you see is a Displayport “in” connector for looping graphics into the TB chain if you need to. No requirement to connect it. The card will also change slightly in appearance from this one once it ships. The slight delay is certified TB 2 drivers just like everything else TB 2.
-
8 lane card. TB 2. There is a small cable that connects to the Z820 or Z620 motherboard . This card will only work in these 2 machines.
-
Feel free to to use the “THUNDER WARS” term – it came blurting out of my mouth during a Intel meeting (got a few laughs) I was conducting a few months ago discussing how this stuff connects together and why we don’t have real notes/whitepapers.
ping me anytime – I think you know how get ahold of me at Adobe-
BTW – I don’t get on threads often, as I’m usually swamped with internal questions on workflow in my own Adobe inbox as Premiere gets pushed up the Pro workflow chain.
-
Jeremy,
just a quick note to say thanks for posting the link. It seems most people get the basic idea that I was trying to draw attention to Thunderbolt in general and the possibilities it brings for editors. I should mention for our Mac Users, that I ran the same test on Macbook Air using 10.7 and it kicked @ss. I edit a lot on both platforms and both sides should be impressed.
The purpose was not to compare either OS which the cow users seem to get (other forums are hung on the fact I used Windows ) but to show multiple devices in a chain. Running windows just opens the user base even more to show TB vendors that we need more devices. I should mention that getting the stuff to run on windows TB requires Windows drivers for each device (same as mac) so you can’t simply connect a TB device and have it work (with the exception of the Apple TB 27″ display) .
Another thing for the Cow users to note is that each type of computer has different limitations to how many TB devices can be connected and in what order. I refer to this as THUNDER WARS and you’ll know what I mean once lots of devices start showing up and people try to get everything running perfectly. I’ve got a ton of various early beta TB devices in the lab and it can be challenging at times understanding why things work and don’t work – not a lot of notes on it yet. I think we’re writing it as we go along;) I think all this will work out over time. Both Intel and RED have been very supportive of the things we are working on – stay tuned.
Anyone heading to NAB might stop by our booth, I’ll try and have this or a similar demo setup for people to check out. The realtime scrubbing and playback has to be experienced to be believed. As true geek myself, it takes a lot to get my jaw to drop and this did it pretty quick.
thanks
DKH
-
Just announced today for OSX. It’s a great card.
-
Michael,
I had a chance to discuss your question with one of our top engineers for the Mercury Playback Engine (CUDA HW) and here’s his response and I hope this sheds some light. I know there was just a new 10.6.5 graphics update and NVIDIA OSX drivers were updated to 3.2.17 for CUDA. This may also have an impact on your results (good lets hope).
————- From Engineering ——–
Hey Dave –
The RED Rocket and Mercury Playback Engine are designed to compliment each other with the rocket doing decodes & debayering and the Mercury Playback Engine handling rendering. Currently there are a few Mac specific issues combining the GPU with a rocket but on Windows it all works really well.We confident we’ll get the Mac issues fixed. I would caution against using the GeForce GTX 285 with RED footage, the standard 1GB configuration is not pleasant to work with RED footage. -
.
-
Tim, as usual you’re right on target – thanks.
I don’t get to post as much as I’d like but saw this thread and thought I’d share what I’ve been testing in the Adobe lab. We’ve been testing an NVIDIA card with their SDI daughter card attached and it works excellent for all editing modes. The SDI port basically thinks it’s the 2nd DVI port and you use the same method of setting up the 2nd display ( Settings>Sequence Settings>Playback>1920×1080)
The great thing about this setup is that there are no other drivers but the standard NVIDIA drivers. You get all of the benefits from Mercury HW GPU mode.100% Adobe Native.
Recently, we’ve added the RED Rocket to the Mix to see if we can get FULL quality @ 2K and it works perfectly. 4K works at FULL but appears to drop a frame here and there and we are continuing to hunt that down. It may have something to do with the various SDI displays only supporting 1920×1080 and NVIDIA card combo.
Note* you can’t use the RED Rocket SDI ports as they are not designed for apps like Premiere or others to output to. They are specific to RED.
The only barrier for most will be the cost of the SDI daughter card – not cheap, but it works great.Setup is a bit weird as the control panel settings are not intuitive. Once you do it once, it’s easy.
I will say that for most people, using a DVI to HDMI or Displayport to HDMI cable attached to a $1,000.00+ flatscreen TV will give excellent results for the $$. This also uses 100% Adobe Native and GPU. I recommend this HDMI setup for most users. I recommend spending at least 1,000.00 for this type of display , the cheaper ones are quite soft and non-consistant color.
Lastley – The HP DreamColor display has a unique advantage over other Displayport monitors when using version 5.02 or higher (yes, we’re still at work on more goodness), it provides 10bit color to the DreamColor and once you see the quality , you’ll be hooked. This is a great confidence monitor setup for the $$. No expensive SDI (just an expensive but gorgeous display)
my 2 cents,
DKH
https://tv.adobe.com/show/davtechtable -
Eric,
I’ll be the first to agree that waiting for AME to launch from Premiere when all you need is a quick export is a pain. The CS4 trick is already have AME launched and then it’s pretty fast to queue. Once you use the Render Queue feature in CS4 (if you need multiple outputs) – it’s great.
One thing I often have to explain is why it takes soooo Long to load some projects – It’s basically reloading all assets, titles, filters (and so on) to each Queue – for example, you can have several layers with titles , each in a different language, and you turn off/on the language you need with each queue allowing you to quickly create assets for multi lingual projects. The same goes for filters like Color Correction settings or any filter.
Yes – you did catch a few of the “goodies” we are working on. “Instant Export” was missed in CS4.
DKH
-
Alex – you’re guess would be wrong…. 😉