[Peter Ilyk]

Thanks Henk.

I would if I could but I don’t know what forums to search.

Cheers

[Peter Ilyk]

Hi Henk

I did use the new cameras before I got my new computer and the video files had no problems playing in the old system. The files were generally shot at 50mbs – although some were shot at 100mbs. The frame rate was 50fps – although some used a variable frame rate.
There was never any problem – it’s only with the new, super-powerful computer that there is a problem.
By the way, when you open a file from the GH4 and right click it, does it show any details eg frame height, frame width, bit rate. When I open the files from the Panasonic FZ2500 or HCX1 there are no details about the video at all. When I used the Canon XA 20 or 7D Mk11, I was always able to see details about the videos when I right clicked the file and clicked details. This is in Windows 7 Ultimate (same Windows as I used in my old set up).

The new system shouldn’t have these problems as it was specifically built to edit 4K – so 1920 should be a breeze.

Very puzzled by what is happening. I see that you use Windows 10 – so maybe I need to move to W10 – although I don’t really want to. I assume that you have np problems with W10 and Vegas.

[Peter Ilyk]

The jpg is the worst, but there is still a problem with the original files from the Panasonics.

[Peter Ilyk]

Hi Graham

I did that. Rendered some of the project to MFX template and then put it in a new project. I always get a prompt to ask whether the project properties should match the first file in the timeline – the answer is always yes.

Anyway, I then did split the project and inserted several transitions. This time there was no problem – the transitions played smoothly like on my old system.

However, just as a further test I then place a jpg photo at the end of the new project and inserted a transition – and this was as bad as it was on the original timeline – unbelievably jerky and stuttery. I also inserted one of the original files and added a transition – same problem as before.

So transitions in the MFX rendered files work well – but transitions with the original files or jpg photos don’t.

[Peter Ilyk]

Hi Graham

I’ll try that.

Not sure what you mean by the project settings – as mentioned in my earlier response, the project properties settings are 1920 x 1080 25.000(PAL), which is the same as the video file properties.

I also just recently added a jpg photo to the project and inserted a slow zoom (Ken Burns effect). Normally this just worked smoothly on my old system. Now it is very, very jerky and stuttery. Very odd!

I rendered the whole project and it all plays back very smoothly – but it is very hard to work in Vegas when the transitions and zooms are jittery.

[Peter Ilyk]

Hi Graham

Yes, it is a mystery. I also had VP13 and 14 on my old system and never had an issue.

There’s more than 1TB of HD space. The C drive also has about 800GB of SSD.
Project settings are 1920 x 1080 25.000(PAL). The video file properties are the same.

The videos were shot with the new Panasonic FZ2500 and Panasonic HCX1 in MP4. The funny thing about these videos is that when I download them from the SD cards into my computer and then click on properties, there are no details about video properties (eg frame height, frame width, data rate, frame rate etc) or audio (eg bit rate audio sample rate). When I import the media into VP14 it does show the properties, eg:

Video: 00:00:47.040, 25.000 fps progressive, 1920x1080x12, AVC
Audio: 00:00:47.040, 48,000 Hz, Stereo, PCM

The system was only installed a couple of weeks ago and all the Windows updates (except for April) were installed.

[Peter Ilyk]

Hi Graham

It’s on. I did try it with the GPU acceleration off, but it made no difference. The dynamic ram preview is set to 200mb. I upped this to 2000mb – but it made no difference – so I’ve put it back to the default 200mb.

[Peter Ilyk]

Thanks very much for replying John. That’s very useful information. I may go that way myself. Cheers Peter

[Peter Ilyk]

John I was interested to hear that you use a MacBook Pro and edit with Vegas Pro. Presumably this is done using the virtual Windows set up. How well does this work when using Vegas Pro 13? I am certainly tempted to change to Mac as I used it in the past (with Final Cut express) and found it quite trouble free. But I was never certain about using Vegas on Mac with something like Bootcamp. I’ve now become quite used to Vegas Pro and would certainly like to stick with it if it will run trouble free on a Mac Book Pro and Bootcamp. So I’d be very interested in hearing of your experience. Thanks. Peter

[Peter Ilyk]

Thanks Dave. I turned off the GPU acceleration and the problem seems to be solved.