I agree - if you follow every 409 workarounds then Avid MC5 is a superior product.
Fix this bug! Avid MC5 is unstable since more than 4 month and 1 week!
editorofchoice, I do not believe that Your behaviour will speed up the bug fixing process; I suscribed to this thread thinking that it is the place where the fix will be announced, but I'm kind of weirded (roman slang horribly translated to english) by Your attitude.
peace luca
Sorry to disturb you Luca.
My attitude to my customers is that I give them exactly for what they paid for. Unfortunately that is obviously not the attitude of Avid anymore. I'm waiting now more than 4 month to use MY PAID UPDATE but I can't because it is unstable and not usable in my production enviroment.
BTW:
I can't understand the attitude of some users of this forum by jumping into my back. We're all in the same boat - trying to use our Avids as professional as possible and to make a living with that. It doesn't really help to glorify this product if it has massive problems and a bug that Avid is now aware off by more than 4 month. Sorry to say that - but I think Avid doesn't have an idea how to fix this bug. Otherwise it would be rediculous to let MC5 stay unstable for more than 4 month. Meanwhile long time Avid users (with more than 5.000 posts) and Mods of this forum keep sending me PMs about not giving up on this. I know it's not popular in this forum to critizise Avid but I will continue to do so until I get what I paid for.
Please unsubscribe to this thread if you're feeling disturbed by my weekly message to fix this bug. I need that update really and I will keep kicking Avid into the XXX until this is fixed. This delay is not funny and not explainable anymore.
editorofchoice:I can't understand the attitude of some users of this forum by jumping into my back.
editorofchoice:Sorry to disturb you Luca.
I would like to support Luca's post in that
1. Constant harping on about something that has been said over and over again will almost never give positive results. Unfortunately this is the case even if the person doing the harping is correct.
2. I have said elsewhere, and I will repeat it again - I have tried to emulate all of the scenarios you have described about the crashes you are having in MC. I have NEVER been able to replicate a crash - EVER!So I guess there is something wrong with my installation of MC/ my computer or my workflow.I know that you are not alone in being able to provoke these crashes. But I just cannot get them to happen.
I am sure that you will ignore the following advice, but here goes anyway:
You have made your point. Larry has escalated it. Now please be patient.I mean "Patient" with a capital P. Patience may not be a question of a few days......or even months! it is not easy to show real patience....... Finally, if you wish to continue with the "bumping" and caustic comments - I am not going to stand in your way........ but you will be doing absolutely nothing to further you credibility or respect on the Forums.
Regards,Douglas
By the way: the above was not what is known as a "rant".It was intended as a friendly pointer . . . . . . .
[email protected]
Sorry - I disagree again:
Because I could crash 4 MC5 PCs in a row at the IBC with that bug within minutes. I don't have any idea how you work and what is your source material but this bug is REAL on every machine (see the dozens of posts in this thread that report the same bug on their machine)
drbgaijin:but you will be doing absolutely nothing to further you credibility or respect on the Forums.
the exact opposite is true: Avid ignores this thing since 4 month - escalating means nothing. A bug fix would help. What about the respect to the paying customers? What about the credibillity of a company that doesn't care about their own professional product not being stable for more than 4 month? And you have the nerv to say to me that I will lose my credibility and respect in this forum? Just by telling Avid (not only for me but also for every other user that has this problem) every week to fix this bug? Man - you have a strange view to the world and to the people that hardly earn their money with editing.
So please support the users that have a problem - not the company that tries to hide it.
Harpy Dude: Must have been fun for you crashing all those Avids at IBC. Maybe you just have bad Avid Karma.
Ronn Kilby
San Diego
The fun thing is: The guys on the Avid booth told me that this bug was fixed in MC5.0.2, which was a false information as I could easily demonstrate.
editorofchoice, MC5 UNUSABLE!! (all caps) is an overstatement, I've installed the software and kept my clients happy using it since the package was released; moreover: spotting the faulty code, fixing it, testing the patch/software, and releasing it to the public will take the needed time, there's no forum post that can speed up the process, and the bug is being taken care of, as far as we know; if You had a job involving two days of capture, two days of editing, and two days of finishing, titles and audio sweetening, would an annoying client making phone calls every 20 minutes telling You, "HURRY UP, YOU LAZY BOY!!" speed up Your work? Please relax and stop wasting bits, band, and, most of all, Your and our time; I don't want to unsubscribe the thread, even if at the moment it's more irritating than informative.
luca.mg:editorofchoice, MC5 UNUSABLE!! (all caps) is an overstatement
Luca, I changed that line already long time ago(please have a look at the title of this thread). Unfortunately I can't change the headline of the individual posts.
luca.mg: if You had a job involving two days of capture, two days of editing, and two days of finishing, titles and audio sweetening, would an annoying client making phone calls every 20 minutes telling You, "HURRY UP, YOU LAZY BOY!!" speed up Your work?
That is not the right picture. It should be like this:
You have a job to do and the client paid already. The job should be finished in 4 days. After 4 month and 1 week your client keeps calling you every week to ask if you are ready with the editing. He keeps doing this allthough you've stated that you are aware of this problem. In my world the client has every right to do this.
If you want to wait an burry the thread in this forum then this is your decision. I think it is good to keep this thread alive every week to remind Avid of this redicolous situation. So sorry Luca, but I will remind Avid to finally give us (the clients that paid) a working software. If this bug was reported 4 weeks ago I would understand that it is not the right choice to remind Avid every week. But this bug is 4 month old. Time enough to get it fixed.
Please accept that this is my point of view. And I want to thank everybody that sent me positive PMs to keep up this thread.
Cheers
Having done my share of software debugging - ten years of my working life was spent writing software - my sympathy is totally with Avid on this. You cannot know how much or how little work they're devoting to this issue. One thing that you can absolutely count on is that they would not knowingly sell faulty software. That's a great way to go out of business.
Since this appears to be a bug that some can easily reproduce and others can't - I'm in the latter group - it's likely that Avid are having real trouble isolating and fixing the faulty code. From my own experience, bugs of this type can be real devils to fix. Often they're only found almost by accident.
editorofchoice:I think it is good to keep this thread alive every week to remind Avid of this redicolous situation.
You may believe that holding your breath till your blue in the face will speed the debug process. You may believe that high-pitched screaming will do it. Or you may believe that continuously bumping this thread will help. In my opinion each is childish and none are likely to make any difference to the end result.
editorofchoice:I will remind Avid to finally give us (the clients that paid) a working software.
But in one thing I totally agree with you. This thread has become a ridiculous situation.
Just for the record, I have requested a status update on this issue some time ago. Awaiting a reply.
Larry Rubin
Senior Editor
The Pentagon Channel
www.pentagonchannel.mil
I can't reproduce this bug too, I'm on the default Interface settings, and maybe just lucky, the software works for me, editing a long form docudrama with P2 XDCAM and HDCAM footage both AMA and MXF Avid mediafiles, DNxHD 185; I'm unhappy with some of the changes introduced with MC 5, but that's another story.
editorofchoice, let's agree that we disagree, as I keep thinking that a weekly complain will not improve the bug fix process.
Thank You for the peacekeeping post from the Pentagon channel!!
That's entertainment
luca.mg: Thank You for the peacekeeping post from the Pentagon channel!! That's entertainment
"Out of mud the lovely Lotus Blooms, Out of Strife something higher vies "
luca.mg:as I keep thinking that a weekly complain will not improve the bug fix process.
Yes - after 4 month I think you are right. But maybe this prevents some people to update if they need the script view as much in their workflow as I do. Not everybody has to run into this bug trap and waste money on an update that isn't stable when you work a lot with script view.
Most of my collegues are still using MC4.5 because of several issues. But as you mentioned this is another story.
Take care
Not sure why some systems are NOT affected by this bug, but my system crashes after a few minutes of using the script view without exception. It usally happen when using the mouse to scroll. I have experienced the issue with every update/patch of MC 5.
At first, I thought it must be something wrong with my setup, but I've double and triple checked everything else. I just recently discovered this thread and after several successful attempts, can confirm that the crashing is definitely due to this bug with the script view. All my crashes have occured when scrolling through P2 DVCPRO HD (1080i) media.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller