1 Reply Latest reply: Jan 23, 2011 8:01 PM by Mark Mapes RSS

    A response to Mark Mapes

    Hem12345 Community Member

      Well, Mr. Mapes, I guess this means that I won't be "AT LIBERTY" to continue spending thousands of dollars on your products and your company won't be "AT LIBERTY" to receive my thousands of dollars.  Do you have any idea how difficult it is to find a decent laptop with either firewire or pcmcia slot these days?  You might be a little more considerate in blowing off pretty serious questions from frustrated customers in the future.  We're not talking about a "given feature" here.  We're talking about whether or not Adobe is committed to the satisfaction of its customers by keeping up-to-date with technology trends.

       

      Here, in the real world, people like me have to make decisions about software and hardware that have financial implications.

       

      Adobe is really dropping the ball on keeping up with technology if they expect their users to continue using a practically obsolete format like firewire.

       

      - Angry CS User

       

       

      Mark's comments:

       

       

              Mark Mapes Adobe Employee

      182 posts since


      Jul 5, 2007

      Currently Being Moderated
      2. Oct 4, 2010 2:22 PM in response to: Devys TV
      Re: No firewire connection for On Location

      For live monitoring and recording, OnLocation works only with FireWire inputs. I'm not at liberty to discuss whether a given feature is under development.

       

      As for how to get live video from a camera with HDMI output into OL, there are hardware devices that take in uncompressed video via one or more types of connections, encode the video, and output the encoded stream via FireWire. Not having worked with any of them, I cannot recommend one specifically--or even remember the make/model for such a device. That said, I'm pretty sure you'll find this kind of thing at Blackmagic Design and AJA.

       

       

        • 1. Re: A response to Mark Mapes
          Mark Mapes Employee Hosts

          Yes sir, we are well aware that some newer laptops do not have Firewire ports and, moreover, that the majority of new file-based cameras do not output via Firewire. So adding support in OnLocation for other types of connections is naturally a high priority for us.

           

          Where you are off the mark is in asserting that "Adobe ... expect[s] users to continue using a practically obsolete format like FireWire" and implying that we either aren't aware of technological trends or don't care about remaining on top of those trends. If a product does not meet a customer's evolving needs--for whatever reason--I for one do not expect that customer to buy the product anyway and wait for Adobe to catch up. To the contrary, we're well aware that we risk losing that customer's business. That, after all, is the essence of capitalism.

           

          We put out the best software that we can, adding as many new features and improving performance and stability as much as possible with each passing development cycle. Do we always deliver everything that's on our roadmap in a given release? Of course not. Maybe development takes longer than anticipated, or personnel changes hinder progres, or other priorities crop up that steal time from the cycle. And keep in mind that products in Adobe's Creative Suite are released simultaneously. That means that if a feature is not ready for prime time, we can't simply slip the release date.

           

          Put another way, the development cycle sometimes forces very difficult decisions. The toughest choice for us on the OnLocation team in the CS5 cycle was to not include capture card support. We anticipated that some customers would be disappointed or even angry that we were not able to deliver that support, and clearly had 20/20 foresight in that regard.

           

          Having re-read the post in question several times,* I'm honestly at a loss to comprehend how you are interpreting my words as blowing anybody off. As I interpreted it, the post I was responding to basically asked whether OnLocation was going to support HDMI. Since it's company policy to not discuss future development on the public forums, I replied that "I'm not at liberty to discuss whether a given feature is under development." In such cases, I usually add something along the lines of "We're aware of the demand for this feature and it's in our feature database," which for some reason I neglected to include on that occasion.