The nature of fixing bugs is that the hard part isn't necessarily fixing them, it's often finding them.

I know that this has been mentioned in the past, but perhaps considering using a dedicated Bug Tracking Tool such as Jira etc could shift the load and wasting time on finding the bugs to fixing them. I am certain there's many community members that would like to contribute in a meaningful way, and not just have their findings buried in a forum thread.

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I am bumping this along as it is really a headache to see this performance issue in front of a client.

[XAVC-S user, PAL] what I Am seeing (and that does concern me) is, that in a simple timeline playback, with no FX or transitions applied, the preview playback framerate drops where there'a a new clip start.

It seems, the playback buffering stops / doesn't look 'ahead' far enough as it should, past the actual currently playing clip's duration, hence causing issues.

I can playback 4K XAVC-S on full quality, no problems, if the clip is long enough, the PC will preload enough material to 'feed the playback pipeline', or I briefly wait before hitting that space bar. But when there's a new clip assembled, this pipeline seems broken.

I cheered too soon. This latest build still freezes minutes after launching, every time. It just stops playing video (sometimes I still hear the sound) and the app becomes completely unresponsive and then goes white and I have to kill it. I've tried disabling the GPU acceleration of video processing, but that doesn't seem to make a difference. Back to Vegas Pro 14 it is.

The nature of fixing bugs is that the hard part isn't necessarily fixing them, it's often finding them.

I know that this has been mentioned in the past, but perhaps considering using a dedicated Bug Tracking Tool such as Jira etc could shift the load and wasting time on finding the bugs to fixing them. I am certain there's many community members that would like to contribute in a meaningful way, and not just have their findings buried in a forum thread.

To my opinion that happens. But the public may not know that.

@AVsupport : I've asked for this on and off/privately of the MADISON Diggers from 2006 onwards

I know that this has been mentioned in the past, but perhaps considering using a dedicated Bug Tracking Tool such as Jira etc could shift the load and wasting time on finding the bugs to fixing them.

@AVsupport . . . Oh yes . . .

I am certain there's many community members that would like to contribute in a meaningful way, and not just have their findings buried in a forum thread.

Give me a VEGAS Debug Tool that is Grazie-Proof and I'd use it.😉

My preview window has slowed down, making it unusable. Anyone else having the same problem, or have a solution. I can't edit my videos at the moment.

I tried to edit a multicam performance with the newest Vegas 15 but it kept crashing during the multicam editing. I did it in Vegas 14 and it didn't crash at all. I had two X AVC L and an X AVC S video file. The X AVC L from Sony PXW-X70, Sony PXW-Z150 and the X AVC S from the Sony a6300.

I know that this has been mentioned in the past, but perhaps considering using a dedicated Bug Tracking Tool such as Jira etc could shift the load and wasting time on finding the bugs to fixing them. I am certain there's many community members that would like to contribute in a meaningful way, and not just have their findings buried in a forum thread.

That is just a registration. The hardest part is to find out why the bug (registered symptoms) occurs and even the best bug tracking system will not help.

Disabling So4 dll again keeps mine going strong

Disabling So4 dll again keeps mine going strong

Same for me, but I also had my Intel graphics driver updated by the Dell Support on my laptop and this just would lock Pro 15 up as soon as I played any video on the timeline, rolled back to my previous driver and all ok again.

I think we all paid for computers we think should be able to handle timeline playback. I know buy computer should. Playing back a simple cross dissolve between two clips should not cause it to slow down. but I do have to say, the memory management so far has been much much better. And now I can render using my AMD graphics card to it's full potential.

Of course there is room for improvement. And those with show stoppers, I feel your pain. I just haven't experienced any yet.

Reyfox my machine was hand built and works flawless with other software as well as using fast drive systems. There seems to have always been a problem with h264 XAVC-s footage. Don't understand why it only effects vegas specially since it used to be run by my Sony tech friends out of wisconsin. Just would love to someday actually use this great product with XAVC-S. Fingers crossed.

I tried to edit a multicam performance with the newest Vegas 15 but it kept crashing during the multicam editing. I did it in Vegas 14 and it didn't crash at all. I had two X AVC L and an X AVC S video file. The X AVC L from Sony PXW-X70, Sony PXW-Z150 and the X AVC S from the Sony a6300.

Ok so I am not alone here. ; )

XaVC-s (mp4) still see something as simple as a fade between clips freezing between the transitions. Not smooth. It seems random when happens though. Any one else?

Is there anyone else seeing this? Hoping I am not alone here. : )

I am bumping this along as it is really a headache to see this performance issue in front of a client.

[XAVC-S user, PAL] what I Am seeing (and that does concern me) is, that in a simple timeline playback, with no FX or transitions applied, the preview playback framerate drops where there'a a new clip start.

It seems, the playback buffering stops / doesn't look 'ahead' far enough as it should, past the actual currently playing clip's duration, hence causing issues.

I can playback 4K XAVC-S on full quality, no problems, if the clip is long enough, the PC will preload enough material to 'feed the playback pipeline', or I briefly wait before hitting that space bar. But when there's a new clip assembled, this pipeline seems broken.

Yes this is the problem. Thank you.

@david-ruby, I haven't bought a pre-built computer since 1990. That was an Amiga (I had several and tricked them out). I've built computers for businesses that have specific needs. Also, of course my own. Had a long stint with trouble shooting other people's computer problems too. My present computer works fine. SSD C: drive and SSD for "scratch/render". Then things are moved to mechanical drives. My editing demands aren't what they used to be, but I love good editing software. After years of avoiding VP, I finally bought VP14 and was impressed with the speed of it's timeline editing. Really impressed enough to upgrade to VP15 Suite. Then RAM issues started. But now, they are fixed in the latest build.

I can not speak to your specific problems. I too would figure since Vegas started with Sony, that XAVC-S would work flawless. But reading the replies says otherwise. I personally edit Panasonic MP4 4K UHD files. Yes, I also let proxies be made. But the previews look pretty good, and now, with AMD VCE, rendering is a breeze.

I hope they come up with a solution for you. Really. I also think that transitions and titles should not have to take "forever" to render to RAM, and they should be able to be played back smoothly without having to jump through hoops...

Reyfox my machine was hand built and works flawless with other software as well as using fast drive systems. There seems to have always been a problem with h264 XAVC-s footage. Don't understand why it only effects vegas specially since it used to be run by my Sony tech friends out of wisconsin. Just would love to someday actually use this great product with XAVC-S. Fingers crossed.

@david-ruby I'm going to take a wild stab at this since I reviewed your hardware specs - I think the culprit causing the lackluster performance for transitions could be the GTX 670 you list in your hardware specs - I currently use a GTX-660ti (Currently waiting for an R9 380 4GB card to arrive this next week) - I get the same issues as you even with Cineform AVI's - I think transitions and motion title graphics are OpenCL accelerated in Vegas. In Premiere Pro, the transitions are CUDA accelerated so I'm guessing it's the same in Vegas for AMD based cards since nVidia support for OpenCL on older cards is mediocre at best.

...I wish transitions and titles were OpenCL accelerated.... at least on my computer, they certainly do not appear to be so.

...I wish transitions and titles were OpenCL accelerated.... at least on my computer, they certainly do not appear to be so.

Are you saying transitions and titles aren't?

If they are... they certainly do not work like it on my computer. AMD RX480 8GB graphics card. Use one of the standard VP titles with a little bit of motion and unless I render it, I won't see the animation.

The problem could be me.... it certainly isn't the computer hardware.

Are you editing off of SSD's or spinning drive(s)? I have found the bottle neck on my system is the eSata Raid 0 I have used for the past few years is not able to handle even 1080p footage well enough - I think it's my eSata card itself. If I stick with straight cuts I'm ok but add some of the more intensive FX in Vegas and my fps does drop. I'm willing ot live with it and work around by dropping down to Preview Full or half quality.

The nature of fixing bugs is that the hard part isn't necessarily fixing them, it's often finding them.

I know that this has been mentioned in the past, but perhaps considering using a dedicated Bug Tracking Tool such as Jira etc could shift the load and wasting time on finding the bugs to fixing them. I am certain there's many community members that would like to contribute in a meaningful way, and not just have their findings buried in a forum thread.

To my opinion that happens. But the public may not know that.

Do you have proof of that, @Wolfgang S., or is that a guess? If there was, it would be good to have a 'public component' of this system, a little bit like what Nick Hope does with his marvellous 'Known Issues' thread, only with more depth & information to a specific issue

I have found the bottle neck on my system is the eSata Raid 0 I have..

The 'Playback-buffering-look-ahead-pipeline-broken' - issue I described earlier even happens with straight cuts, no transitions, no FX. Data drive barely registers any read/write traffic. nor is anything else maxed out in the system. This seems to be a systemic programming issue at the core of VP that is at the root of all other consequential poor timeline playback performance when you start adding 'fancy stuff'...