Hi Jeff,

I have saved a couple of versions on the project but still occasionally get the same message. I wonder if it might be just one of the several audio and video streams that I am editing. I'll try to note what stream is active next time I get it.

It was yesterday that Peter suggested the GPU-Z utililty and I haven't had time yet as I am desperately trying to get projects finished and delivered. I'll try later today.

Thanks,

Roger

I'm beginning to wonder whether I should have bothered upgrading to VPX. I thought just now I would check for upgrades, having done that when I installed two nights ago. I had a message saying there was an update which I installed, then immediately afterwards another message saying that there was a major update, I think it was about 245mb. Just after the update started, a popup appeared which disappeared when I clicked on 'Retry' and the update appears to have installed, but I am just about to open the programme again to attempt to carry on editing. I'm wondering if the popup is connected to my earlier ones.

This list of corrections on the Major Update, seemed quite substantial.

Roger

Hi

Roger

The error message relates to one of the sample files that is used by the Noise reduction effect, this has been causing issues with Movie Edit Pro as well - see here.

What version number did you end up at?

HTH

John EB.

Hi John,

Thanks for the link, I've downloaded the file in case the problem persists. Since the last update I haven't seen the error message again and I have done another 3 hours editing.

The current version number is shown as 15.0.4.176 but I don't know if that is a new programme update, or just to bring my new install to whatever was current.

Roger

Hi Roger,

176 is the most recent patch. Other than specific problems that I have on my desktop but not on my laptop, and that the NewBlue Essentials 3 and 4 (which you probably don't have) under OFX don't work properly, I haven't had any problems.

John CB

Hi Roger,

176 is the most recent patch. Other than specific problems that I have on my desktop but not on my laptop, and that the NewBlue Essentials 3 and 4 (which you probably don't have) under OFX don't work properly, I haven't had any problems.

John CB

Hi John,

My upgrade to VPX included NBE 3 & 4, Mercalli V4 and a music creation programme. The main download must have been a recent version but not the latest. I'm surprised it didn't update to the current version when I downloaded the add ons. At least it is current now.

Roger

Hi All

Just FYI there is a download for all the Noise Print samples available on the support site:- https://support2.magix.com/customer/en/customer/downloads/tools which I imagine is a response to this problem although from responses here it appears to have been fixed in the .176 patch. Only problem is that my VPX is still not showing a patch is available beyond .171, which has the issue.

@RogerGunkel

I posted some guide lines about checking what is happening with hardware acceleration near the end of this thread: https://www.magix.info/uk/forum/best-pc-configuration-for-vpx--1192930/.

Are you using the Intel codec and encoder for your exports or Main Concept's encoder?

Peter

Hi Peter,

Thanks for the info and strange that you can't get beyond patch171.

I'm pretty sure that I'm using the Main Concept encoder at the moment as I didn't change it after taking the NVidea card out. I won't be able to check until tomororrow evening though as it is 7.45am here and I am just leaving to film a wedding and won't be back until around midnight, then a wedding show tomorrow!

Roger

Hi

@Scenestealer, @RogerGunkel

. . . . strange that you can't get beyond patch171 . . . .

I am in the same boat - cannot get .176 update unless I use the link posted in another topic.

John EB

Hi Roger

The second problem I have noticed is that rendering out to MP4 or AVCHD seems to take twice as long as VPX7, that is either using my nVidea GT740 graphics card, or the graphics on the I76700 CPU. With the claims for higher render speeds on GPX from Magix, I am puzzled. I have kept VPX7 installed just in case.

It is possible that you are rendering without HWAccel. to the Intel encoder (the default) in VPX9, whereas in VPX7 you were using the Main Concept encoder which is quite swift in comparison when not using using HWA.

Try exporting using the Intel codec / encoder with activated HWA and you could see faster than realtime encodes with your newly found Intel GPU. If not, check as per the instructions in my earlier posted link that HWA is actually occurring on the Intel HD530 graphics.

Peter

Hi Peter,

I am seeing the HWA message appearing now when rendering to AVCHD, but not if I have effects on the timeline, which seems to tie in with another post. When I first installed VPX, I initially loaded a previous project to test rendering times, but that would have had some effects on. Using a new section of video with no effects, I am now getting about 25% better than real time, but I would rarely use raw footage as I am using crops, pans and zooms on 4K for a lot of footage, plus colour matching from different cameras.

I am also not seeing Intel as a render option, only default or main, so although the CPU seems to be processing the graphics, I can't see where to access the Intel rendering.

Roger

Hi Roger

HWA should also be occurring for mp4 files as well as AVCHD.

. . . .but not if I have effects on the timeline . . . .

Some effects will not/can not be rendered using HWA. I am not seeing any issue with crops, pans or zoom HWA is used with the Intel codec exporting to AVCHD or mp4

. . . . not seeing Intel as a render option, only default or main . . . . I can't see where to access the Intel rendering . . . .

If you are using the 'Default' codec then you are using the Intel codec, and should be seeing 'Hardware encoding' in the top bar of the export dialog as it is rendering.

The other option is MainConcept, which is what I presume you mean by 'Main', and you see 'QuickSync' in the top bar of the export dialog as it is rendering.

Note: if you use the MainConcept codec, which I find is slower than the Intel codec, do not turn on the Calculate video effects on the GPU option in the export dialog - otherwise you will end up with a zero byte file.

HTH

John EB

Hi John,

That makes sense, the Intel codec being the default. I haven't noticed the 'QuickSync' indication whilst using the Main Concept codec, but I'll have a quick experiment as I am taking a break now from another 8 hours of editing.

My wife has been using VPX for the first time today and loves the colour matching option as she is working on a 3 camera shoot that she filmed a few weeks ago. She is a very accomplished videographer, photographer and editor and a partner in our business. She usually likes to stick with what she knows, so it's a thumbs up for the upgrade from VPX7 to VPX.

Roger

Hi Roger

I am seeing the HWA message appearing now when rendering to AVCHD, but not if I have effects on the timeline

You should still see the message but yes, in cases where the clip has some heavy "CPU only" effects (like Mercalli stabilising) and the CPU is saturated with those you will see the GPU activity drop to almost nothing (in GPU-Z), even if there are GPU accelerated effects on the same clip. I think this is due to the fact that the GPU effects need part of their processing done on the CPU and that causes a bottleneck to what is being sent to the GPU.

I haven't noticed the 'QuickSync' indication whilst using the Main Concept codec

To use HWA with the MC encoder you must select "Quick Sync" instead of "Auto" at the top of the "MPEG4 Export>Advanced >Advanced Video Settings>Main Settings tab>AVC Encoder" window. QS should then appear in the MPEG4 Export template's Format Description box instead of "CUDA" or "Hardware Encoding". Without changing this setting HWA export will fail with MC.

if you use the MainConcept codec, which I find is slower than the Intel codec, do not turn on the Calculate video effects on the GPU option in the export dialog - otherwise you will end up with a zero byte file.

I find MC is generally slightly slower and sometimes slightly quicker but it depends on the effects in the project, the format being exported to, and of course our machine configurations.

The zero byte file (despite a seemingly successful export) John mentioned, I find occurs with MC QSV HW export to .mp4 but not .m2ts. Calculate VFX on GPU does not have a bearing on this in my case.

One thing I am sure of is that the Default Intel codec / encoder always gives a better quality result, HW or SW, with less blurring of darker low contrast areas of the frame.

Good to see you and your wife like the new Colour correcting tools in VPX9 although Ifind I have to resort to the manual Shot Match option with the pipette as the auto nearly always creates a colour shift towards another colour, often yellow.

One option you should consider is trying the creation of LUT's for the different colour characteristics of your multi cameras. The idea being that you spend time adjusting effects to get the other cameras looking the same as your main camera and then save a LUT for each other camera which you can then easily apply in the future. The bonus of a LUT is supposed to be that in applying it, the stacking of many effect adjustments is eliminated, reducing processing load during preview.

I mainly shoot with one camera and I find I am using the "Curves" adjustment more and more for the bulk of my grading adjustments, with the aid of the RGB parade and vectorscope - very cool!

Peter

Just thought I would post a quick update as we have been using VPX for a week now.

Having tweaked a few bits following following the recommendations here and we have had no further problems at all. The colour matching is excellent and Mercalli V4 seems to give a smoother output than we were getting on VPX7. Claire(the Wife) has just finished editing a wedding that she shot with 3 cameras and 2 sound recorders with absolutely no hesitating or stuttering. That included synching 3 cameras in 4K and the two sound recorders for the ceremony. All previewed beautifully and the export to mp4 was carried out at just a bit faster than half real time. The first section of 53 minutes took 23 minutes to export, about 4-5 times faster than we were getting in VPX7.

I've had equally good results with editing a two hour school production also with 3 cameras in 4k and 2 audio recorders.

Once again, thanks for everyone's help :-)

Roger

Hi Roger

Sounds great. Thanks for the feedback.

BTW which codec / encoder are you exporting with, and which GPU do you have selected in the "Display Properties" for "Preview in the arranger"?

Peter

Good Morning Peter,

The export drop down in 'Programme Settings' is set to 'Default' which will be the Intel and I usually use the User defined MP4 1080 HD 25fps Pal setting which I have found is the most compatible for our wedding video clients across most TVs and laptops etc. AVCHD(M2ts) gives problems for some people. We also keep the export at VBR 10000kbs min & 14000kbs max, which enables us to get up to about 55mins into a 4Gb clip when using USB2 delivery. Shorter videos we just increase the BR. As there are so many variations with client playback systems we have refined it to an output that works with just about everything but still looks good.

Roger

Version 176 broke 3d bluray creation .. luckily I'd backed up and was able to restore my computer to versions 144 or 154 which happily render a 2hr 3d bluray.

Irritatingly this is almost my last day of available updates .. not certain I'll be paying for another year.

Also still no over/under 3d movie file import!