Actually, thanks for chiming-in. That's very good news!
Pixel Monkey / Chris Bové
Pictures say 1000 words. Editors give them meaning.
alwaysediting.com (website)
youtube.com/alwaysediting (My Channel)
wnyppg.org/ (Avid Users Group)
http://www.youtube.com/page11music (The old band... miss those days!)
raspago: Hello Larry!! I think the new logo is "brand recognizable" to people who are already familiar with Avid, but I think those who know little or nothing about Avid are going to find it somewhat confusing. .- Undisputable truth. I'd like to add that the new logo is horrible, confusing and absolutely unnecessary. What was wrong with the older one?
Hello Larry!!
I think the new logo is "brand recognizable" to people who are already familiar with Avid, but I think those who know little or nothing about Avid are going to find it somewhat confusing.
.- Undisputable truth.
I'd like to add that the new logo is horrible, confusing and absolutely unnecessary.
What was wrong with the older one?
I'd agree, i'd say some kind of hybrid image, the triangles and the line with actual text slightly fading over it, so it's predominately the shapes, but you get a little text showing through.
Euphamistically speaking: A logo redesign that partners with a fresh operational plan and business model is as much of an internal morale boost as it is an external confidence builder. Hopefully current customers and potential clients alike will appreciate the strong history and be excited by the new thinking.
Plainly speaking: Shave and a haircut to go with the new wardrobe... but still the toughest kid on the block.
also:
http://www.adhdmedia.no
Their name is from:
http://en.wikipedia.org/wiki/ADHD
:)
They edit with FCP though - perhaps they need to change now...
ouch...thats a little close.
Scott Witthaus
Owner/Editor/Post Production Supervisor 1708 Editorial
www.1708editorial.com
Thoroughly and completely unimpressed by the new logo and lack of real announcements."In Avid's defense, the management shakeup that led to last year's "New Thinking" mantra only happened...what...1.5 years ago? It takes TIME to turn a ship as epic as Avid in a new direction."Are you kidding me? Avid is not that large! Bigger companies have proven to be more nimble than Avid. "And we have one result of the "One Avid" approach. MC 3.5 can be install on the same computer, and partition, as PT8! Yes, it is an ubiquity, but still is has been imposibly during the last years."I am very wary of this. I couldn't get any confirmation from anyone at Avid that this will work regardless of version or upgrade patches going forward. I don't want to be forced to do lockstep ugrades. I don't want AVID and ProTools to use the same Audio engine. That is just asking for trouble. I am keeping them on separate partitions.I totally understand why Avid doesn't want to support 3rd party hardware. But why haven't they figured out how to get third party apps to work with Avid Hardware?This would be a low cost way to get more people to use Avid Hardware. Avid management is cluelesss. Period
Avid MC 3.5 and ProTools 8 play together just fine now on the same system.
Robert Davis President/Creative Director
Davis Advertising, Inc.
Visit my latest blog, "Concept to Creation" on the Avid Community site
Adman: Avid MC 3.5 and ProTools 8 play together just fine now on the same system.
Before jumping in the air and jumping with joy whilst dropping working double boot configs I would want to KNOW
Do they play well on both Mac and PC OS's?
Which Digi IO boxes work (well) with Avids audio on either or both platforms?
Does Protools 8 play nice with both DX boxes on either platform?
Or Adrenalines for that matter?
Is this both LE and HD or just LE?
Thanks for the continued dongle support
I can only assume that since the problem root was compatibility between MC and PT using the same digidriver, that the issue is exclusive to that fact. I would assume that since the driver is not compatible between the software programs, that the issue has been put to bed. Again, my assumption being that the issue was due to incompatibility between the drivers... you had to install one or the other of two different driver files to get either MC or ProTools to work, prior to this fix.
So I can personally attest to the fact that the single driver is working here on both MC and ProTools and we've been working accordingly for a couple of months now.
My assumption is that the driver compatibility was the issue, regardless of the specific configuration...although I cannot confirm this on the Mac. We are running XP Pro SP3.
I would further assume that if the shipping driver for MC 3.5 isn't compatible with various i/o boxes, that the forums would be chock full of posts to that effect...
We are using PT 8.0 LE with a Digi 002r, fwiw.
On the other hand, it is a fact that at least the Mbox 2mini is not currently working with MC, but that fix is due in an upcoming release.
If there are any threads that say otherwise, based on different configurations, I would love to hear about them and I will personally address them with AVID personnel.
What is your experience Andrew?
Adman:What is your experience Andrew?
I have PT8 HD and MC3.1.2 on a dual boot Mac which works flawlessly. When I need this compatability I need it on MAC and without loosing much time setting it up and troubleshooting or waiting for an upcoming release. Ideally for me it would work with Avid using the Digi 192 IO for audio (incidentally FCS has worked this way for 3 years now)
I am concerned by the number of times I see the word assume(d) in your post. We have been close to compatibility several times before but it never really seems to get all the way there. That is why I asked the questions about the wider scope of your original post which I guessed was based on PC, LE and 002 experience.
Yes, the "official" compatibility has been a long time coming...and I purposefully used the word "assume" to great extent, lol. But, I would be quite confident to proceed, personally...based on the facts that I presented. Although, I do understand your concern that I am "assuming" a few critical points.
But, to reiterate:
* Previous releases (before 3.1 which had the satellite issue) required TWO SEPARATE (and conflicting) Digi Drivers...that could not be installed on the same system successfully.
* MC 3.5 and PT 8.0 now share the same digi driver.
* Our systems are working fine and have been for some time now.
It is a valid assumption to "assume" that the forums would be boiling over with complaints if the shipping digi driver was not working with the various MC i/o devices... it was surely tested with these devices in beta. The drivers were also "surely" tested with the various PT i/o devices as well.
So, until there is evidence of issues between these different combinations/permutations here on the forums, I will continue to "assume" that the compatibility issue between MC and PT has been finally put to bed.
Robert,
What would be really helpful is an explanation of the various audio programs ProTools currently offers for MC/Symphony and DS. I've tried to understand the various versions of ProTools, and it's just very confusing, esp. how things like mbox apply (or don't apply) to Avid's NLE's.
I also have no idea how Avid audio tracks are opened in PT; I've read about something called the DigiTranslator, but don't know if it's needed. Do I need to close the project, MC, reboot? Or can I launch PT from inside MC and use it as I would AvidFX / Boris Red?
In short, MC is short on audio tools, but Avid has yet to layout a clear ProTools solution for MC, Symphony and DS users.
I'm not asking you to lay all this out, but I do believe that Avid needs to. It's very unclear for many of us NLE users.
Ok... It would be best to start a new thread with specific questions on that. I'll do everything I can to get the answers and help out.
For specifics on MC and PT compability, check out:
http://www.digidesign.com/index.cfm?navid=3&itemid=37195
Also...check out the readme file in MC 3.5 -- The MC 3.5 ReadMe section titled "Co-Install Supported Configurations" provides notes for co-install as well as a chart that demarcates the specific I/O configurations tested. (tried providing the link but it is apparently broken right now).
Thanks for the information
Adman:http://www.digidesign.com/index.cfm?navid=3&itemid=37195
No indication from Protools that it will send the a timeline movie to an Adrenaline for monitoring. Local agents cannot confirm or deny this. Currently I do not have time to test this config and as I am using a Decklink card with no problems (HD with DNxHD movies) I lack a little motivation to break a working setup on assumptions.
Avid Technology, Inc. brands: Digidesign | M-Audio | Sibelius | Pinnacle Systems | Sundance Digital
© Copyright 2000-2008 Avid Technology, Inc. All Rights Reserved — Legal Notices | Privacy Policy | RSS Feeds | Site Map