Where has VP12 710 gone?

vkmast wrote on 9/10/2013, 1:33 PM

No build 710 available here either at the moment, only b670.

Christian de Godzinsky wrote on 9/10/2013, 1:35 PM

That's the most probable reason. It would be prudent for someone (Paddy?) to chime in here. Actually, it would show some courage too...

I just downloaded b710 and now hesitate what to do with it? Should I install or not? What's going on?

Is there anything else (than the dysfunct image sequence import) that caused SCS to withdraw b710? Please - we deserve to know! And I agree, its unbelievable that such errors slips out in new builds... It's an indication of lousy (or not enough automated) software verification and validation methods...

Christian

albert_kes wrote on 9/10/2013, 1:40 PM

Build 710 was released in error, will soon lay out normal

vkmast wrote on 9/10/2013, 1:42 PM

Christian (and others), see Chris Dolan's post here

FilmingPhotoGuy wrote on 9/10/2013, 1:43 PM

VP711 will be here tomorrow morning with the fix for image sequencing, I hope :)

_Lenny_ wrote on 9/10/2013, 1:49 PM

It's already tomorrow morning in Australia and New Zealand... ;-)

I hope good things are worth waiting for.

ChrisDolan (SCS) wrote on 9/10/2013, 1:50 PM

Yes, we took 710 down for the image sequence bug. The next build is being tested (and re-tested) now.

Christian de Godzinsky wrote on 9/10/2013, 1:57 PM

Holy moses, I read Chris Dolan's post and my first thought was that it was a joke or something... My sincerest aplologies.

It must have taken lots of courace to go public saying "its my fault"... I highly appreciate that you posted this!!!

So I'll scrap the b710 and await for the next one. Probably its here as fast as the 710 disappeared...

Thanks SCS for your openness...

Christian

videoITguy wrote on 9/10/2013, 2:24 PM

A lot of courage for a programmer to go public on the forum? Well maybe, but that is not really the professional protocol at all. Makes me wonder who is running the ship.
The proper response would have been channeled thru a program team leader...where has the profession been going I ask. I don't have a lot of faith left in this whacked two-bit system that SCS is currently running.
Build 710 to be replaced by one single fix, by an internal programmer who just recompiles all of the existing code? Quality control please folks!!!!!!

DavidMcKnight wrote on 9/10/2013, 2:38 PM

videoITguy, there is no way you can infer that from Chris' post. What he said in effect was, "We are aware of it. It's my fault. We're working the fix right now."

Only a micro-managing IT middleman would demand that communications be channeled through them. I have no doubt that all communications were approved, and you have to applaud Chris for taking responsibility.

If you really think Vegas is a "whacked two-bit system", then move along to something else, please!

vtxrocketeer wrote on 9/10/2013, 2:43 PM

There's a fly in my soup! Someone fix it now! Whaddya mean the chef himself is personally apologizing and ladling out a new bowl for me the instant I ask? That's the maitre'd's job. Where is he? What kind of a slip-shod 4-star restaurant is this, anyway?

videoITguy wrote on 9/10/2013, 3:29 PM

Your post is funny, but lacks the real comparison. If your point is that ChrisDolan is the chef, then it should be for him to stand up and say so. But he is not the chef, for it is likely that he is a programmer who was assigned a small piece of the entire code block in this particular point in time. That's the way it is usually done. He is not likely to have any concept of all of the legacy, or the code head to tail. Since he has not qualified himself, this is certainly conjecture.

I just wish SCS would be more forthcoming (about six years ago and since then) of what they are attempting to do. What market do they want? Code reliability over silly added features version to version? ETC

rmack350 wrote on 9/10/2013, 6:27 PM

...over silly added features...

<sarcasm>
All I really want is Red Eye Reduction. The rest of it is all silly features.
</sarcasm>

The problem with labeling things as silly features is that it assumes that every user and every marketer want's exactly the same things.

I appreciate it when a vendor speaks up immediately to say "We made a mistake and we're fixing it as fast as we can". It's so much better than silence which feels like ambivalence.

However, I think I get what Videoit is saying. If you fix a bug and rush it out, was the fix tested? Could there have been unintended side effects? How would you know?

I'm assuming Chris does know because he knows what was broken. Personally, I rush fixes out all of the time but that's to web content which just doesn't have dependencies. Sometimes a fix is quick, easy, and obvious.

Rob

vtxrocketeer wrote on 9/10/2013, 7:03 PM

Well, I'm just the busboy . . . ;)

Dexcon wrote on 9/10/2013, 7:22 PM

VP12 714 is now available with a stills fix

gpsmikey wrote on 9/10/2013, 7:37 PM

SHeesh - folks complain that Sony doesn't respond to problems but then when they do (and quickly) you complain. Spit happens - they stepped forward quickly and fixed (hopefully) this issue. Seems like a good job to me.

mikey