@Scenestealer
Hi Peter.
I have to agree with you on the Stabilizing.
I too get a far better result from Mercalli 4 and cmos fixer.
I can't say there any vast improvements with the program compared to VPX 10 for my work anyway but at least it seems they haven't gone backwards.
I did have an issue yesterday when I started a new project. All my settings had reverted back to default. "Strange".
The DVD transitions issue seems to be fixed but since I am using DVD Architect now, it isn't so much of an issue.
Here's hoping for a bright future. There are still issues that have been around since VPX 8 but we can't have everything.
Doug
 

@Scenestealer

Hi Peter

. . . . . There is definitely something flakey happening here as the same clips work fine in with Auto-color in MEPP2019 . . . .

Ditto - looks like we have another 2 bugs in VPX 11.

Auto exposure and Auto colour do not work on any video - tested with mp4 (2 different cameras - Full HD and UHD, AVCHD (2 different cameras - Full HD and UHD) , MOV, m2v, and wmv file formats.

John EB

@johnebaker

Thanks for the additional testing. I will do a little more work in the new version to see if anything else stands out before sending a note to support.

It seems amazing that something that has been in the NLE's forever, suddenly becomes broken.......still.... cleverer guys than us.....

Peter

Hi.

I have purchased also VPX latest version (17.0.127 (UDP3)). Maybe I am doing something wrong, but there are some problems in reliability on some very basic operations. The program gets stuck when I create new project, save it, and import video clips from SD card. It imports them correctly to <project>/my record but after import the whole UI is stuck. Work folder resides on local disk.

Once I restart program (by killing it from task manager first) and dragging clips from <project>/my record to timeline, program works pretty ok. What is nice that when doing basic "video", proxies are not needed as scrolling etc works well.

One minor quick improvement would be adding key to add trimmed clip (I, O keys) from source window to timeline.

For some reason audio tab is empty. I installed VPX after uninstalling previous version. I have also Sony Vegas 16 365 version. Comparing to it, VPX audio editing lags behind. Sometimes VPX command "edit wave externally" is not visible. Both VPX and Vegas audio editors are bit complicated to use. I have replaced those with Goldwave that allow me doing easily audio loudness, noise reduction, compression of loud/peaks to wav files. Vegas external editor support is better than VPX as it automatically creates wav files before invoking external editor.

VPX would be faster to use than Vegas for interview kind and other similar short clips (that i usually do) if basics would work starting from importing clip from SD card. Now the reliability is not in level I would expect from software that advertises it ".. in Video Pro X is even faster and more efficient than ever before..". It is quite huge productivity killer starting debugging what is wrong. Lets say that editing short video takes about hour. Putting 0-15 minutes of problem solving before work is not nice. But like mentioned in beginning on this post, maybe I just do something wrong.

I base my judgement that I also use Sony Vegas to similar kind of videos. My computer setup is Intel I7, 32 GB RAM, NVidia GTX 1050 4GB, non SSD storage for video files. Keyboard, mouse and shuttleProV2 controller. Camera model used for was Sony PXW-X70 and codec setting were "XAVC HD, 1080/25p 50Mbps".

@erkki.salonen@erkki.salonen, @Scenestealer

Hi

. . . . minor quick improvement would be adding key to add trimmed clip (I, O keys) from source window to timeline . . . .

I agree - the existing 'key' for doing this as shown in the image below, is not in the ideal position.

There is a bug with it - after first time use adding a clip range to a project it does not work any more with other clips, dragging from the Source monitor is no issue.

Can anyone replicate this?

Added: it no longer works, even after program reset, and there is another issue as well - see clip below

John EB

. . . . minor quick improvement would be adding key to add trimmed clip (I, O keys) from source window to timeline . . . .

I agree - the existing 'key' for doing this as shown in the image below, is not in the ideal position.

Exactly. I have mapped "i" and "o" to shuttlepro. Then taking selection to timeline is done by pressing that existing 'key' with mouse. This could work (picking ranges from clip using jog, "i", "o" and mouse clicks) as long as your mouse cursor stays on top of key. The dedicated key improves workflow. About range import (video clip example) I think I have same problem too.

HI,

I just got back from 2 weeks of camping so I'll try to catch up on the bug list in the next day or two.

I can confirm that Auto Exposure and Colour Correction do not work on videos. I tried some GoPro video files and photos - nothing happens with the videos, only the photos.

@erkki.salonen @johnebaker

It's Magix Vegas 16, not Sony.

1. Adding trimmed clips - John EB, I'm not sure what you are doing. It looks like you brought the clip into the source monitor, trimmed it and then tried to use the brackets that are in the import screen to put the trimmed clip onto the timeline. Correct? This is not how it works. Look at the hint at the bottom of the screen when you mouse over the brackets. The brackets button "Loads the current file into the video monitor from trimming without playing it (the trimmed file can be dragged and dropped from the video monitor into the Arranger)." The other button to the left "Starts/Stops playback of the current file." For the trimmed clip, simply drag the trimmed clip from the Source Monitor onto the timeline or click on the import button, (Automatic application (1), or use one of the shortcuts 1 through 5.

2. I have I and O mapped to my ShuttlePro for all 3 of my configuration banks. One of my configurations is for importing and I have mapped the 5 import buttons. Thus for a trimmed clip in the source monitor, I press on a button mapped for 1 to 5, depending on what I want to do. If you're not sure what I mean about 3 configurations, I did a tutorial on this, mainly for Vegas.

3. Using an SD card for importing files is not really a good idea. Remember that files are not actually imported into the program, only the filename, thus the files always have to be available at the same location. The correct way is to copy or move files from the SD card to a hard drive and then import into VPX from the HD. I do not keep any source files under <project>/my record - that is the default location set up for any audio recording that you may do using VPX to record. My files are all under separate folders for photos and folders on a drive separate from the system drive.

4. Audio tab - this is only for audio files purchased and downloaded from the in-app Store. There are some free songs and sound FX that you can download from the Store. Audio effects are under the Effects tab.

5. VPX command "edit wave externally" is not visible - this is an on-going problem that I have raised with Magix many times and you'll see it on the bug list. In this latest version of VPX, it doesn't show up for the audio part of a video clip if the External Audio Editor is the default Music Editor 3 or the new SoundForge Audio Cleaning Lab. It does show up if changed to Magix Audio and Music Lab Premium. I haven't test other editors yet. In the past, I have tested SoundForge 11 Pro, Samplitude Pro X3 Suite and a few others.

Vegas external editor support is better than VPX as it automatically creates wav files before invoking external editor.

What is supposed to happen is, for the audio part of a video clip, the audio is mixed down to a wave file and then opened in the External Audio Editor (defined in the Program Settings, Folders). Upon exiting, it will ask to save the files. Selecting yes overwrites the previous wave file and returns to VPX with the audio clip updated. Thus a mix-down to wave is actually done.

If the object selected is already a wave file, then no mixdown is done and the selected clip is opened in the External Audio Editor.

For the moment, the only way around the command "Edit wave externally" not showing up, is to isolate the clip with a range, solo the track, and then do Shift+D to get a mixdown. Then Alt+Z or right-click on the file and select "Edit wave externally."

See this video about the problem. Magix seems to have fixed the second problem, but not the first:

https://studio.youtube.com/video/SF6NqmHBdio/edit

I will keep pressing Magix on this hit and miss of the command showing up. I purchased the new SFACL hoping that it would cause the command to show up; it doesn't.

John CB

@browj2

Hi John

. . . . The brackets button "Loads the current file into the video monitor from trimming without playing it (the trimmed file can be dragged and dropped from the video monitor into the Arrange . . . .

Thanks for the info - the highlighted text is what is missing in the manual ie - Range import: You can define an import range on the source monitor using buttons for the in- and out-point - no mention that there is no need to play it.

When I do use the In/Out functions (rarely) I normally play the clip, use the I and O keys and then drag from the monitor.

John EB

3. Using an SD card for importing files is not really a good idea. Remember that files are not actually imported into the program, only the filename, thus the files always have to be available at

Hmm. I did import by pressing "r" key. Then on recording source selection I selected "AVCHD../" and imported clips that way. Import did import clips to <project folder>/my records but hangs after that.

When I do use the In/Out functions (rarely) I normally play the clip, use the I and O keys and then drag from the monitor.

This is similar workflow for me too. If there would be a key that replaces mouse drag and drop, then user can keep left hand on keyboard and move source window cursor with mouse without doing drag and drop in between.

When I do use the In/Out functions (rarely) I normally play the clip, use the I and O keys and then drag from the monitor.

This is similar workflow for me too. If there would be a key that replaces mouse drag and drop, then user can keep left hand on keyboard and move source window cursor with mouse without doing drag and drop in between.

@erkki.salonen

Hi,

As I indicated in point #2 above, the shortcuts are 1 to 5 on the upper row of the keyboard. 1 is the normal automatic application, meaning import to the end of the timeline on the selected track, or track 1 if no other track is selected. There is no need for any other key. Are you aware of the Import buttons on the toolbar? Right-click on the import button and you'll see the list for importing - 2 = Single track ripple, etc.

Am I missing something here?

John CB

I was looking for workflow where user don't have to use mouse dropping selected range to time line. On Vegas this is simply done on trimmer view by pressing key "a".

On VPX I was looking for similar: On source window user left hand (let's drop shuttlepro from discussion for a while) controls range start, stop and dropping selected range to timeline. Then right hand controls mouse. Mouse is controlling playback position (left button down and moving mouse left/right). As drag and drop to timeline is not done on mouse, taking clips from source window would be faster. Hope this helps.

[[MENTION:undefined]]

Ok, but this is done in Magix pressing the key 1. Did you try it?

John CB

Has anyone had the problem of settings reverting back to default.
This has happened twice now when opening new or existing project.
It is not a big problem on it's own but I have a lot of single key custom shortcuts that are lost every time this happens.
I am also finding when I save or copy video effects, some of the effects don't show in the check list unless I close the program and re start, then they show up.
Mainly Plugin effects and it also happened with lens correction which is a built in VPX effect.
Seems I have a whole new bag of faults to deal with now.
Is this the way of the future.
Thinking of uninstalling and going back to 10 where everything worked for me but I will be stuck in the past and having to renew my update service every year for no gain.
My only other thought is that it's a windows thing.
I am locked into v 1803 but wondering if VPX 11 is more compatible with current build.
Just a stab in the dark.
Doug.

 

@DugsBugs

Hi Doug

I am locked into v 1803 but wondering if VPX 11 is more compatible with current build.

I am thinking this also especially reading this comment from FredW in a discussion about encoding speed in the German forum (Google translate):-

"....with me it was so that only with the patch 1903 the encoding time has decreased. Before, I had 1809 installed and the encoding time was much longer. At 'maedschik' did not fit the latest driver, with me the latest driver on the HP of the PC manufacturer and 1903. It's just a tip to potential problems that have nothing to do first with VdL exclude."

Generally I think Magix is trying to utilise and optimise for the newest technology and hardware (whilst maintaining basic compatibility with older systems) so it is wise to keep everything as up to the minute as possible IMHO.

It is not a big problem on it's own but I have a lot of single key custom shortcuts that are lost every time this happens.

Not sure but I think you should be able to save custom shortcuts and configurations and reinstate them later...?

Peter

@Scenestealer
Thanks Peter.
I installed 1803 from a disc image when my computer had a fit and I have created the same with the current build.
I will still contact support before updating to 1907.
Doug.

Hi

I did a little experimenting with the Auto Exposure / Colour effect and found that changing the mode in the Display tab of Program settings for playback in the arranger, from Standard Mode ie HW accelerated Direct3D to Compatibility Mode Video for Windows made the Auto effect visible and it remained when changing back to HWA mode. It sort of "kick started it" if you like, but only for the selected clip. Choosing another clip would require the same procedure.

@DugsBugs

I did have an issue yesterday when I started a new project. All my settings had reverted back to default. "Strange".

I think this happened to me also but will monitor.

Did support have anything to tell you about a W10 1903 update?

Peter

@Scenestealer

Hi Peter.

They haven’t responded yet.

I tried the new patch and monitoring it.

It hasn’t happened again so I’ll hope for the best.

Doug.

@Scenestealer

Hi Peter

. . . . W10 1903 update . . . .

Have you seen this document from Microsoft ?

I am currently holding off this update and the previous 1809 until I can get the current projects finished or forced to install. I have probably just tempted fate 👿

HTH

John EB

@johnebaker

Hi John.

My computer "decided" last week that it should update to 1809. So far, no major traumas (or is that tempting fate?) 😇

Jeff

@johnebaker @emmrecs

I am also on 1809 on both desktop and laptop. I haven't noticed anything that is not normally wrong.

John CB

Thanks guys.

I have been on 1809 for sometime and have not noticed anything odd, unless this problem with the Auto effect is related...

@johnebaker

I had seen that Microsoft article after my PC indicated that Windows had decided that I was not ready for the update. For what reason I did not know but reading between the lines I decided that it is because of MS's gradual (cautious) roll out of 1903 after previous problems with recent builds.

Strange thing is the notice in WUpdate about not being ready has now disappeared but Check for Updates does not reveal anything.

Which parts of the article you linked to are you concerned about?

This one: -Gamma ramps, color profiles, and night light settings do not apply in some cases

Or this one:- Display brightness may not respond to adjustments

Peter