8.0c Bug: Blu-ray path

Sidecar2 wrote on 9/12/2008, 4:18 PM
Tools: Burn Disc: Blu-ray disc:

Dialog box contents: Image Parameters: File Path: "Browse..." button

Bug:

You can't change the File Path by pressing the "Browse..." button. I have to change it manually in the window. Very "DOS" like. I haven't had to type a \ in years!

It was a stark bug because I had only minutes earlier used the same command in 8.0b without issue. The "Browse..." button renaming function doesn't work in 8.0c.

If you hit "Browse..." and navigate to a new location and file name, when you hit OK the path reverts back to what it was before and if you start a render, it will ask if you want to overwrite the file you previously rendered.

Comments

Sebaz wrote on 9/12/2008, 4:38 PM
Yep. Confirmed. Evidently Sony didn't test this thing very much.
Robert W wrote on 9/12/2008, 6:02 PM
I'm curious, can anybody confirm if this bug is present in 8.1?

Ha ha, I can see a lot of performance increases being swallowed up by having to run 8.0c and 8.1 in parallel just to navigate all the daft little bugs. Honestly, why did they not release a beta to us all in this forum so we could highlight these things? How much trouble would it save them and how much more solid would it make the application?

I would not like to think how much time they spend trying to find bugs like this that could be spend fixing them after we told them they existed.
Yarin VooDoo wrote on 9/13/2008, 12:47 AM
Ciao,

Confirmed, same bug here on 8.0c!
Click on Browse button, on the pop-up choose you path, click on save to close the pop-up window....the path doesn't change!

Ciao
rmack350 wrote on 9/13/2008, 9:40 AM
File a bug report. Put a link to this thread in it.

Rob Mack
rmack350 wrote on 9/13/2008, 9:43 AM
Several people here have made it obvious that they were beta testers. It wasn't caught. Might have been introduced at the last minute.

Rob
Robert W wrote on 9/13/2008, 10:42 AM
Well "several people" is obviously not enough. Like i said, why not offer it to everyone as a Beta first, and then get the most possible bug reports when your development team is mobilised to do somethign about it? Every single version of Vegas 8 I have seen has been more like an Alpha. It is obvious to most people that these testing periods are compeltely ineffectual. I would also guess that they selection process for testers means the product is tested on a very narrow range of systems.

If they are happy to issue pieces of junk like this, I do not see why they would not offer Betas to everyone on the basis that if they are happy to put this junk out, putting something out which they admit probably has bugs, and will be accepted by the public. at least it might make us a little less frustrated at how poor the feedback to bug reports and repair is.

The bug described in this thread could well be somethign that would have been picked up if they had goen through a proper "Release Candidate" phase. They haven't so a stupid bug got through, and seemingly along with outhers too. And that will most likely always happen. No point wasting development time on finding the bugs. Give the Betas and Release Candidates to us and we shall fidn them for them.

Or are they scared of how many we shall find, and that they may actually have to do something about them?
JohnnyRoy wrote on 9/13/2008, 11:01 AM
> Several people here have made it obvious that they were beta testers. It wasn't caught. Might have been introduced at the last minute.

Did you ever stop to think that perhaps it WAS caught by the beat testers and Sony didn't have time to fix it?

In software development a severity is assigned to every defect with sev 1 being a show stopper, sev 2 being a major impact, sev 3 being minor impact and 4 being cosmetic or minimal impact. You fix the sev 1's first, then sev 2's etc. Most shops will not ship code with known sev 1's & 2's. Some will allow a certain percentage of sev 2's. The bottom line is that no one ships code with no known defects.

I would venture to guess that anyone serious about making a Blu-ray disc is authoring them with DVD Architect and that not being able to make one from the timeline is sev 3 at best. You can create one with DVD Architect so there is a viable work-around.

~jr
Wolfgang S. wrote on 9/13/2008, 12:16 PM
"> Several people here have made it obvious that they were beta testers. It wasn't caught. Might have been introduced at the last minute.

Did you ever stop to think that perhaps it WAS caught by the beat testers and Sony didn't have time to fix it?"


And beside that, what Johnny said: did you ever think about that a lot of errors were caught by beta testers, so that you do not see them at all, since they were fixed?

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Robert W wrote on 9/13/2008, 1:01 PM
JohnnyRoy,

I think it would have taken more time to think about what class of error it was than to fix it. Simple GUI coding error. Probably would have taken roughly 5 minutes at most to correct. Plus it worked in the last version, so it must have been something that had broken in the new release.

I doubt anybody had got the current build of 8.0c to beta test. Somebody may be able to tell us otherwise though. Was the released build the same as the last "Release Candidate"?