what's been reported AND noted by sony?

ushere wrote on 10/13/2007, 4:03 PM
further to my thread re 'twitching' with no-no-recompress in pal...

bob pointed out that this had been covered in another thread - so i looked it up and yes, it had been to some extent. not a 'major' in your face type bug, but just another of those irritating small ones that takes the edge off working with what could be the best nle around.

but i have absolutely no idea whether this has been formally reported to, and noted by sony.

what is the exact procedure to put in a bug report, and where can we find a list of reported ones so i don't waste my time, or sony's reporting already known problems?

leslie

Comments

Cheesehole wrote on 10/13/2007, 11:05 PM
The only way I know of to report bugs is to use the product suggestion form - under Support --> Product Suggestion
jaegersing wrote on 10/14/2007, 12:03 AM
I would report it using Technical Support, under the Support menu at the top of the forum page.

Grazie wrote on 10/14/2007, 1:17 AM
Ditto! Worked for me!!

Grazie
farss wrote on 10/14/2007, 3:14 AM
"where can we find a list of reported ones so i don't waste my time, or sony's reporting already known problems?"

As far as I know there isn't one and as you've noted it would save a lot of time and frustration on both sides.

Bob.
John_Cline wrote on 10/14/2007, 7:14 AM
I think it's important for everyone having any particular issue to report it. Depending on how many people report a problem would allow Sony to prioritize the importance of fixing certain things. Plus there could be subtle differences in each error report that could help them track down more ellusive bugs.

For example, there is a annoyance that some people are having when they close Vegas Pro 8 that says a certain memory address couldn't be read, but the few of us that have reported it have had slightly different memory addresses and those differences could provide a clue as to what's happening.

John
blink3times wrote on 10/14/2007, 8:26 AM
I know that Vegas crashing on various scene split clips in HDV has been reported and I know that Vegas capture scene splitting a few frames early/late has been reported.

I reported these things, and sony has acknowledged that problems exist and should be cleaned up on the next patch.
ushere wrote on 10/14/2007, 5:32 PM
b3t,

it's a pity then that sony doesn't have a 'bug' page that lists those they have acknowledged. this would mean i don't have to spend time discovering that 'my' problem IS a bug after all, and i could simply look to see if my problem was listed, and if not, a simple way to notify sony of a problem....

leslie
TLF wrote on 10/14/2007, 11:31 PM
If Sony's beta testing programs are anything like the ones I have been involved with, any list that exists is available only to beta testers and program developers.

And if Sony is like the company I have tested for, it's the bugs that affect the masses, not the few that get fixed; minor bugs are left version after version after version.

I'd like to think that Sony is better than that.
Zelkien69 wrote on 10/15/2007, 4:31 PM
I thought we were the BETA testers for Sony!
ushere wrote on 10/16/2007, 4:27 PM
would appear so - especially in pal land.

it's all well and good releasing software, but at least it should, as a minimum, do what it says on the box. more 'complex' issues might arise, but if sony states 'no-norecompress' as a 'main' selling point, one would expect it to work in practice?

leslie
CorTed wrote on 10/17/2007, 8:12 AM
I just got off the phone with them explaining my problem. I am finding that when rendering and the memory is around 80% usage, I can pretty much be asured the render/program will crash. almost always at the same spot... When I cut the project in half, save each half under a different name, I can render each project just fine, tells me media is not really the problem.
I have spent some significan time testing my box, ran memtest 86+ for 20 hours, no problems, ran Prime95 for 18 hours, no failures, but I run Vegas, and It goes down within minutes. The biggest problem I have is that according to Sony I am the only one with this problem, they have not heard of it...... what I am to do??

Ted
JJKizak wrote on 10/17/2007, 8:26 AM
Like I always say you do not have enough ram. Throw in 4 gig and your problems will be over. Set the ram preview to somewhere between 16 and 158 megs. Remove any anti-virus. Disable all the Microsoft XP visual baloney, remove the hard drive indexing, turn off system restore on all drives.
JJK
CorTed wrote on 10/17/2007, 8:52 AM
JJKizak, if you were replying to me.... I have 4 Gigs, running Q6600 with Vista, raptor 10,000RPM drive for OS 500gig for Video.
It is not a lack of memory
JJKizak wrote on 10/17/2007, 9:04 AM
Wow! Something ain't right. I have an AMD 4600 X2 with 4 gigs. I started out with 2 gigs and had the same problems you have. Changed to 4 gigs Kingston and no more problems. This is with Vegas 7.0e and presently V8 with XP Pro. Vista might be the difference. I plan to get either the Q6600 or Q6700 to run Vista 64 bit. I don't have any "OS headaches" at the present time so I figure to get Vista to correct this intolerable, dull, boring XP RPO OS.
JJK
ushere wrote on 10/17/2007, 4:08 PM
jjk,

heck, you're one masochist, ain't you ;-)

so far i've avoided vista (i like a boring, unexciting os), simply because i've read so much here, and on other forums regarding vista problems - even my local pc shops are advising against it - unless you know what you're doing...

have a friend who has both xp and vista running ppro and vegas - and both are prone to various 'problems' that identical xp system doesn't have....

leslie