VPX10 - Updated bug list as at patch 16.0.2.322

browj2 wrote on 5/7/2019, 11:11 AM

I decided to reproduce the bug list here under a heading that shows the corresponding patch, mainly because I received a reply from Magix today indicating that they have many tickets open and cannot fix all of the bugs in a short time. Really? Many of the items on the list have been around for at least 6 months, others for 4 months and some even since last July. This is absolutely ridiculous!

I was informed that a major patch would be released this summer. I take this to mean a new version will be issued - meaning new features with more bugs. This is totally unacceptable. Version 10 has been an embarrassment, with many features not working correctly or at all. We have been deprived of the proper use of this program for the better part of a year.

I think that we will need to bombard Magix with tickets, including the list along with any other bugs that have been found. I will put the list in a pdf file on Dropbox so that others may send in the same list.

Below is the renumbered list with a couple more problems added recently.

Comments in italics are from Magix:

1. Missing Icons: "This is a problem and actually our developers didn't know that. It will be fixed so thank you for this hint. (2018.12.17 and 2018.12.18)" Fix the preview of icons under Templates, Image objects - the icons folders are missing from "Test Images" and "Backgrounds" - C:\ProgramData\MAGIX\Video Pro X\8\VideoEffects\BackgroundEffects\ColorFields and C:\ProgramData\MAGIX\Video Pro X\8\VideoEffects\BackgroundEffects\Pictures; only Collages was fixed.

2. External audio editor: "Magix has created a bug entry for this. Again, thank you for this hint. The problem will be fixed. (2018.12.17 and 2018.12.18)"  The problem has not been fixed: Right-click on the audio part of a video object, no command for "Edit in external editor." This has been an intermittent problem, sometimes it's there in a version or patch, sometimes not. It's there for wave files and proxies, but not for my videos clips that are mov, mts, and mp4 files. We need to be able to send out the audio to an external editor for cleaning.

3. Scroll bar on touch screens Templates tab: "This seems to be a bug. Our product owner will check your video. (2018.12.17 and 2018.12.18)" Still problem on my Surface Pro 4 - Templates tab: The vertical scroll bar cannot be dragged up and down, only sideways to expand/contract the listing window. The mouse indicator changes to a left/right arrow. No problem on desktop - non-touch screen. A video of this problem was sent to Magix.

4. HitFilm OXF keyframing X and Y problem: "Could you please send me a video of this problem, too? (2018.12.17)" (Done and submitted 2018.12.17) HitFilm - OFX like Gleam, Radial Blur, Zoom Blur - keyframing X and Y fail. The numbers go crazy, up to infinity.

5. External Audio files not saved: "The whole feature is unfortunately very outdated and nothing has been done on it for a long time so there are problems with newer version. This was mentioned at the meeting yesterday and noted. (2018.12.17 and 2018.12.18)" Audio & Music Lab, Audio Cleaning Lab and Video Sound Cleaning Lab no longer save and bring the modified file back onto the timeline. The new SoundForge Audio Cleaning Lab (my trial has expired) seemed to work properly with patch 306. Now with patch 317, exiting saves/overwrites the imported audio file, but and error pops up that cannot be stopped except with the Task Manager.

6. Object and Edit Trimmers: Seems to have been resolved. Warning, an error has been introduced into the MEP Object Trimmer whereby a fade in/out cannot be set. This bug should not be passed on to VPX.

7. Knoll Light Factory causes distortion: "Bug entry created. (2018.12.17)" Adding Knoll Light Factory effect to a clip produces a distorted image on the screen. The image is at an angle. To see the image correctly, I had to change the Video Mode to Alternative Mode 2 (Video Mixing Renderer9). Strangely, if I go to full screen, the image is fine. The export is also fine.

8. Interface with Xara not working properly: "Problem is already known. (2018.12.17)"  Right-click on a video object, Video effects, Create overlay graphics/animations opens Xara (I have the latest Designer Pro X - 16.0.0.55162) but the video does not display; the screen is white. I tested this with MEPP2019 (18.0.1.213) and it works. Thus the problem is with VPX, not Xara.

9. Titles: Some users are having trouble applying colour and font changes to parts of the text in titles. We have checked this and two users have the problem, two or three do not. Here is a link to the thread and the particular one with a video showing the problem.

https://www.magix.info/us/forum/vpx-problem-with-rotation-horizon-levelling--1218402/?page=1#ca1428696

10. Samplitude Pro X3 to VPX: I was going to raise a ticket on the Samplitude side, but the problem is likely with VPX and may be linked to the external editor problems. Samplitude has a feature under File, Export, Export to Video Pro X. It does a mixdown, saves the file and opens VPX if not opened. However, the audio file does not come onto the timeline. I think that I checked this using an older version, VPX 7, and it worked fine, so the problem is with VPX 10.

11. @Liviu-Tatan has reported that the Bitrate slider in the Bluray Burn settings window does not alter the bitrate when moved. @emmrecs has confirmed this, with a workaround that manually entering the BR in the numbers box will achieve a change in BR.

12. Previous reported removal of items from Import menu: Removed recently from Import, Magix Tools, are: XAR Animations; Downloads; Database; Online Album; and Internet Media (first raised 2018.12.04 with more information added since).

Downloads is now listed separately (I don't think that I created this link myself).

Database disappeared quite a while back. This is useful if you have Photo Manager and have created a database with it. I would like this back.

The Online Album is only useful if you have it. I can live without this as I always export first, check the export, then upload to my Album. Anyone else want this?

Internet Media opened the integrated browser in MAGIX Video Pro X offering you (from the manual) the "possibility to collect media from the Internet to use e. g. for your current movie. The integrated browser offers many useful functions that help you collect material for using in your project. All kinds of media can be collected – images, videos, sound or simply text can be all integrated using the built-in browser with great results." This has been removed and not replaced. Some users have indicated that they would like this back.

13. Rotation slider causes blurring of rotated video: Can only remove the problem by using the up/down rotate buttons then zooming in on image to remove borders. This bug is known to Magix.

14. Undo causes playback marker to jump to beginning of a range: When I undo (Ctrl+Z) something the playback marker jumps to the beginning of a range if one is set. It stays in place if there is no range. Previously, the playback marker stayed where it was, I believe.

15. Multicam: "This is a complicated one. Actually, these problems have already been fixed, but they still occur sporadically. It is very difficult to reproduce these problems. We probably haven't been able to eliminate all the causes yet and have to take a closer look at the problems again. The bugs are now definitely known to us. (2018.12.17 and 2018.12.18)"

Sometimes, although a waveform is copied into track 2 as you watch, there is no audio heard. Nor is any heard when you switch back out of multicam, nor if the result is exported. Track 2 is marked as unmuted all this time. New problem: some of the audio objects created on Track 2 by camera switching get automatic fades, but should not. Even more odd, if you step rigorously through the four available channels on the monitor (cyclically top left, top right, bottom left, bottom right, top left, etc.), the sound display corresponding to the top left "camera" always fades to zero at its right hand side, but not immediately after you've cut to top right, only when you've gone round to bottom left. In fact, there's another inconsistency in that as you cut from top right to bottom left, you don't see the cut visually appear on Track 1 until after you've gone on to bottom right; all other cuts appear immediately. Also, it proves impossible to drag any cut leftwards which is preceded by a volume fadeout.

16. Startup screen - Load existing projects: The box is usually empty as is the popdown, or does not have the last opened project listed in the box or on the list when there is a list.

17. Track Header names: Not really a bug, but annoying; the font colour is too faint to be seen clearly with any colour applied to the track. See the attached image. Only the name on track 7, with no track colour can be seen somewhat well. Even then, the contrast is terrible, making it difficult to read. Perhaps the programmers can do something about this.

18. Title causes crash: If a destination track (track 5 or beyond) is selected for insert, that is, the track header is blue, clicking on the T for inserting a title causes VPX to freeze. This does not happen if the selected track is 4 or less, nor does it happen in MEP. Try adding a video clip to a new project. Select and highlight track 5 or 6, click on the Title button in the button bar and VPX will freeze, requiring Task Manager to stop it.

19. Startup screen search folder: After exporting to almost anywhere except the default document folder, then next time VPX is opened, clicking on the folder button above Load beside the usually empty proposed last project box, goes to the location of the export, not to the Project folder where I have my projects, or the folder of the last project opened. Or, in the case of today, it proposed the Audio Temp folder. Export location has nothing to do with project location. The proposed folder should be the folder of the last opened project, or at worst, the default location of projects as per the Program Settings.

20. Color Picker defective on Surface Pro 4 (touch screen): Only on my Surface Pro 4, not on my desktop. I selected a colour chart, Effect, Video Effects, Glow, open the Color Picker and select the eyedropper and run it over the various colours. They are shown incorrectly and even change colour simply by moving up and down over the same colour. This is not a problem with Glow; it is with other effects as well that use the Color Picker:

21. Transition Effect Transition Basic: Blurry - all of them - Edit Trimmer does not work on transitions with a Blurry effect. The box shows a 0 transition and nothing can be modified. Moving from one transition to the next in the Edit Trimmer, it skips over any
transition to which a Blurry transition is applied. See video. If this problem gets worked on, please, please make sure that the programmers do not break anything. We have had enough problems with the Trimmers in the past and we don't need any new bugs being introduced to fix one.

22. New Blue OFX Effects: Some users are still complaining about the use of NewBlue OFX effects causing the screen to go black. Issue raised in ticket on 2018.12.04; John EB to make a video showing the problem (not done).

23. Title Templates, captions go to wrong place:  If there is something on tracks 4 or 5 and you try adding a caption at the location of the playback marker (with or without an object selected at that location), the caption is put after tracks 4 and 5 are clear. Thus, if there is a music track, the caption will be placed at the end of the video.  However, if a destination track is also selected, VPX will try to place the caption at that location. But, if there is something on that track at that location or on a higher numbered track (depends on how many tracks the caption requires), the caption will be placed further along the timeline, wherever there is space.

The way it should work is that the caption should be placed at the playback marker location, on tracks with a higher number if there is something blocking the way. I know that the solution is to manually select the destination and location, checking that there is nothing that will be in the way of the caption, but most users will not be able to figure this out and will be dismayed that the caption is placed at the end of their project, as has happened to me many times. Selecting a destination track is a relatively new feature.

24. Copy/Drag cause full fade on other objects: A simple copy/drag of an object across other objects cause the other objects to have a complete fade from the beginning to the end. Trying to grab the fade handle does not work. The only way to remove the fade is to go into the Object Trimmer and start reducing (or completely reduce) the fade, then one can drag that handle on the object. Magix was aware of this problem and it should have been fixed in the last patch, but I had this problem happen several times in the last week.

Has the following been resolved?

A. NewBlue OFX: effects still blacking out preview screen on some computers(John EB to prepare a video.)

EDIT: Modified again - revision 3 - dates of replies added to attachment and in the above list.

I am presently struggling with how to reply to Magix. I would appreciate some assistance.

@ralftaro

I can't add Mathias here as @MAGIX_Redaktion does not show up.

John CB

Comments

emmrecs wrote on 5/8/2019, 3:40 AM

@browj2

Hi John.

Whew! It must have taken some time to collate those errors/bugs, let alone writing them all up as you have done! Well done, sir!

Since you are a very experienced user of the software I will PM you with my suggestion of how to reply to Magix since I don't want to have the Inbox of any staff member swamped with messages from everyone!

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

Trensharo wrote on 5/8/2019, 4:22 AM

@browj2

Hi John.

Whew! It must have taken some time to collate those errors/bugs, let alone writing them all up as you have done! Well done, sir!

Since you are a very experienced user of the software I will PM you with my suggestion of how to reply to Magix since I don't want to have the Inbox of any staff member swamped with messages from everyone!

Jeff

Product looks nice (tried the trial), but I need to know that it will work properly with designer Pro 15.1 and VSCL/ACL before I purchase. Some of these bugs are shocking...

Also, can anyone tell me whether or now this NLE needs QT for anything, and whether it actually can import DNxHD? Does this inlude DNxHR? I think it failed to import a file complaining that it needs QT. It's an MP4 file, so not even an MOV...

I noticed Ignite Express 2017 seems incompatible, as well... some NBFX like Stabilizer don't show up...

What kind of content can you download after buying/installing? Trial doesn't allow me to check...

Documentation doesn't really answer any of these questions

emmrecs wrote on 5/8/2019, 6:51 AM

@Trensharo

What kind of content can you download after buying/installing?

Below is a screenshot of the additional content; it does NOT include any "extras" offered, e.g. by other manufacturers, when you initially buy the program.

HTH

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

browj2 wrote on 5/8/2019, 8:32 AM

@Trensharo

Hi,

You can change the External Audio Editor in the Program Settings, Folders tab, near the bottom to the path for VSCL or ACL and try them out. In VPX, because the Edit in External Editor does not show up on an object unless it is just an audio object, you have to do a mixdown. To make it simple, put a video clip with audio on the timeline, do a mixdown using Shift+D, right click on the resulting audio file which should be red, Edit audio in external editor. If you have not changed the External editor, the file will open in Music Editor 3. For each one, make an extreme change, like reverb, exit the editor by clicking on the upper right X. I should ask if you want to save the changes, yes, and it should exit back to VPX. The audio should now be changed. The problem is that in some cases, exiting wants to save the audio editor project, not just update the audio file, and then no changes come back to VPX. Try it to see.

Only third party plugins made for VPX or MEP will show up. Currently, no third party plugins are being offered by Magix, so I wouldn't even consider a new purchase. For an update (renewing Update Service), they are offering Mercalli V4, NB Elements 3 Chroma Key Pro, and NB Filters 5 Refocus.

Try running Xara from VPX to see what happens. Xara must be closed before you try this. See my tutorials on this:

If you get a blank screen when you open Xara from VPX, then you will understand why this is on the bug list. Presently, it works fine in Movie Edit Pro 2019 Plus/Premium.

You will likely need QT. I have it installed and never need to open it. VPX just uses the Codec or dll or something.

John CB

Trensharo wrote on 5/8/2019, 9:54 AM

@Trensharo

What kind of content can you download after buying/installing?

Below is a screenshot of the additional content; it does NOT include any "extras" offered, e.g. by other manufacturers, when you initially buy the program.

HTH

Jeff

Thanks for the screenshot. Doesn't look like any effects are in there, so I'd need to feel assured that I could get Ignite plugins to work.

I thought the program supported OpenFX...

I really prefer the interface to Vegas Pro, and already have V15 of that. So was thinking this would be a nice option to add.

Maybe wait for the next major update and see what is addressed.

There is a lot of potential with the integration Xara basically replaces titling tools Useful videos.

browj2 wrote on 5/8/2019, 10:25 AM

@Trensharo

VPX/MEP have OpenFX, but only those tailored specifically for VPX/MEP. There are several HitFilm plugins that I have, but they were all specifically made for VPX/MEP.

Look at the recent threads in the Vegas forum about Bézier masks. They aren't "Bézier masks," they are masks made using lines with curves that have Bézier handles. As I expect you know, Xara Designer Pro X and Photo and Graphics Designer have the Shape tool, so you can draw your mask (or anything else) in the Xara animator and adjust the curves at the nodes using the Bézier handles. Adjustments and movements can be made between video intervals and the shape tweens from frame to frame. You can have multiple masks. As far as I can tell, this is far more powerful than the Vegas Bézier mask tool - when the Xara interface actually works.

I suggest that you wait until a new version comes out, the main bugs are resolved, and a sale is on that includes more/better plugins. Additional plugins show up in the Store within VPX/MEP. They often go on sale, so I would not pay the full price.

John CB

browj2 wrote on 5/8/2019, 10:36 AM

@ralftaro

It would be helpful if we were able to also link in Mathias, but his @MAGIX_Redaktion does not show up.

To add to the above, here is a list of links in which most of the bugs were raised in reply to Mathias' requests for Feedback, along with a few other relevant threads, starting from the oldest (June 4, 2018):

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-1-242--1206814/

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-1-255--1207408/

https://www.magix.info/us/forum/problem-with-update-268-5-1-audio--1211069/

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-1-268--1208859/

https://www.magix.info/us/forum/new-patch-16-0-2-288-for-vpx-released-what-was-fixed--1216632/

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-2-288--1216637/

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-2-301--1217642/

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-2-304--1218088/

https://www.magix.info/us/forum/vpx-problem-with-rotation-horizon-levelling--1218402/

https://www.magix.info/us/forum/feedback-how-do-you-like-version-16-0-2-306--1219383/

https://www.magix.info/us/forum/screen-capture-where-is-the-internet-media-button-and-magix-tools--1220276/

https://www.magix.info/us/forum/vpx-patch-16-0-2-317--1222625/

https://www.magix.info/us/forum/vpx-patch-16-0-2-322-released-nothing-fixed--1224230/

John CB

 

Scenestealer wrote on 5/8/2019, 6:31 PM

@browj2

Hi John

Mathias is on long term leave so that is probably why his @ is inactive.

Great work with your extensive bug list. I rattled up Ralf about it yesterday and he confirmed that your list(s) are "legendary" in his department and that they are doing as much as they can from his end and the formal bug reports are going through......

Currently, no third party plugins are being offered by Magix, - Not sure what you mean by that as the three you mentioned would be included if @Trensharo bought the current program?

@Trensharo

I installed QT to allow VPX to use Prores.

DNxHD is supported for Import but not export according to the Codecs list in the sales info, no mention of DNxHR though. If you would like to upload a small sample of both I can try.

Ignite Cine style OFX works, as do most of the New Blue OFX I have that came as additional effects with Magix MEP / VPX, as John has stated.

Last changed by Scenestealer on 5/9/2019, 12:05 AM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1809, MEP2016, 2017, 2018, 2019 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

Trensharo wrote on 5/8/2019, 10:19 PM

Yes, it looks like the "HitFilm" branded Effects work, but Ignite Express/Pro do not. My HitFilm Movie Essentials shows up in Pro X, but Ignite Express does not.

NewBlueFX, all of them show up - except Stabilizer (which isn't a biggie, since Mercalli 2.0 is integrated).

I'll play the waiting game and see what happens. VEGAS usually releases new versions around Late August/Early September, and I'm assuming Video Pro X will upgrade around a similar timeframe.

browj2 wrote on 5/9/2019, 11:20 AM

@Scenestealer

Hi Peter,

Thanks for the compliment and support with Ralf. I'm pleased that they are aware of the list and hopefully doing something about the major issues. On the other hand, I wish that this didn't have to be done and that we didn't have to chase after Magix to get some action. Undoubtedly, there are more bugs than what we have found that Magix is aware of.

A few years ago, Magix introduced a different Xara problem and it took about 2 years of complaints to get them to fix it. The video would show up in Xara but would not advance, so there was no way to successfully do any rotoscoping or any animation that required following the action. I don't want to wait another 2 years to get this new bug fixed; 6 months or so is already far too long.

Looking at the Magix.com site under VPX, I don't see any third party plugins being offered with a new purchase, only with an Upgrade. Under MEP Plus, New, they are offering until May 15, NewBlue Filters 5 Refocus, NewBlue Essentials 5 Volume 1, and Hitfilm Cinema Style Pack. Under Premium, New, they mention 3 Plugins but don't specifically say which ones, although after clicking on Offers, the same 3 show up under Plus and then again under "Extra when upgrading Movie Edit Pro Plus & Premium."

I think that Magix should take a look at its offerings as a new version of Premium should specifically indicate what comes with it in the way of plugins.

@Trensharo

Here are the plugins that I have:

Here are the third party plugins available under the Store in VPX:

Vasco da Gama is not a plugin but does get linked to the s/n of VPX or MEP somehow, as far as I can tell. I wouldn't buy it as it is too expensive for a stripped down version of the real thing, and version 12 is available. Best to purchase directly from Motion Studios around Easter to take advantage of the annual Easter discount of 20-30%.

As for HitFilm Ignite, shown in the image above is Color Cine (40$) which includes:

  • Color Adjustments (RGB)
  • Letter Box
  • Grain
  • Output Gamma
  • Vignette
  • Background

Again, I wouldn't purchase at the prices indicated in the Store; wait for a sale or an upgrade sale price that includes some plugins.

We've gone way off topic here.

John CB

Recycler wrote on 5/9/2019, 2:24 PM

@browj2

I'd just like to add my thanks to you John for hammering away at this on our behalf. I'm not sure how the marketing people have the nerve to keep this wreckage in the market place to be honest. I'm sure that in some jurisdictions (probably here in the UK) the broken functionality they continue to advertise must be against consumer protection legislation; my bête noire, the multi-cam capability, being totally unusable, not just tricky, must fall into that category. I wonder if, now Vegas is in the Magix camp, whether they might actually let VPX die of old age.

Serif software in the UK used to have a very capable video editing package some years back, and they made a knowing decision that they couldn't, or didn't want to, keep pouring development money into it as the video standards got more and more demanding. That withdrawal was honestly and openly announced - but the VPX situation is like the paralysis of a thousand cuts! Also Magix's handling of customer communications is not very subtle, is it? They've got all our email addresses in their active users database - how much effort would it take to send out an apology? Or perhaps they think only a handful of people are actually affected.... So back to your point John recommending bombarding Magix with tickets as a last resort.

 

Trensharo wrote on 5/9/2019, 7:47 PM

Honestly they just need to put in a proper OpenFX interface. But at least I tried the trial before I pulled the trigger.

NewBlueFX isn't going to replace the Blurs and Flares in Ignite Express, among other things. They are simply better in both quality and performance than anything you get from NB. I consider NB Effects to be Legacy at this point, and their development track record for those products has been abysmal as of late. I own a few, and they have been a source of instabilities in NLEs for me - and NBFX is more than happy to kick the bucket back to the NLE developers when you contact support about it.

I'd rather save up and invest in Ignite Pro, BCC Continuum Annual Subscription - but the former doesn't work and I can't be sure that the latter will, either. They should at least have a list of supported plugin packages. I believe some companies like Grass Valley do this for their NLEs.

I'm going to wait to see what they release at the next version updates. Right now, VEGAS Pro is missing too many workflow niceties to bother upgrading, doesn't add enough to make upgrading off 15 worth it (considering I can just 15 around "just in case" indefinitely), and the integration with other MAGIX/Xara applications I already own was a huge interest generator for me with Pro X.

But that stuff seems problematic, from what I read here. This is kind of frustrating, Lol.

browj2 wrote on 5/13/2019, 11:06 AM

Another week, no fixes to any bugs.

Update on 7. Knoll Light Factory causes distortion:

This also happens when I use NB Titler. I found that there seems to be a glitch somewhere in VPX Preview and Source monitor sizing that is causing the distortion. Changing the Preview monitor size went from distortion to ok to distortion (repeat) upon dragging the size of the window. I stopped it on a size that worked and saved the Windows Arrangement. Problem solved. The default (F9) also worked.

Still, this glitch should not be happening.

John CB

Scenestealer wrote on 5/16/2019, 7:09 AM

@browj2

I have seen glitches in the preview with a freely resized preview window in earlier versions (VPX8) but have always chosen a window that is "Half" or "Quarter" of Full HD. I had seen a discussion about this where it was suggested that this slightly improved preview smoothness because the real time (re)calculation of a random fractional frame size lead to more complex maths and processing for video output. Might be possible and would explain why F9 or full screen worked properly for you.

Peter

Last changed by Scenestealer on 5/16/2019, 7:11 AM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1809, MEP2016, 2017, 2018, 2019 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

Trensharo wrote on 5/17/2019, 12:54 AM

I tried a trial and every EDL I exported crashes Samplitude.

VEGAS AAFs are a complete mess. Resolve uses DNxHD/R video and MXF wrapped audio, which (one of them) causes Samplitide to crash every single time.

That being said, I really don't like the track layout (though I generally like the UI) - upside down and no separation between audio and video tracks... There seem to be a lot of workflow work-arounds you have to do to get things to work "as expected" (like the Audio Editor thing mentoned above).

Think I'm going to have to get a Premiere Pro subscription. It is flawless with AAF and OMF interchange with Samplitude, but it is $$$. I'd only need Adobe's NLE, though, not the other stuff, so that's sort of a bonus.

That, or refund Samp to buy Resolve Studio; and just deal with the (far) worse Performance (GPU Requirements, etc.)... But I'll lose Sound Forge, which I use for other tasks 😢 That being said, Fairlight Page and Audio in Resolve - in general - has been lacking for quality and robustness (i.e. buggy areas). And it locks everything to Resolve Database, when I do a lot of stuff outside of that with Audio.

MAGIX support has not been very helpful, to put it lightly. The people who respond sound utterly clueless about the products, even when you ask basic questions... and the level of English has been wanting (hate to say that (it sounds pretentious), but it just forces follow-up questions; and they are not in a rush to respond to any of them).

And yea, you need QuickTime even for DNxHD... and I'm not sure DNxHR works, at all, since I'm not installing that stuff on my machine. The files won't load without it (pretty much anything in an MOV container)... It's 2019... Most products have "fixed" this, by now. QT7 has ben dead on Windows for years now.

Not sure why an NLE for 4-6K editing would only support an Avid CODEC that is limited to 1080p, anyways. Why even bother if that is the case?

browj2 wrote on 5/17/2019, 9:37 AM

Another week, no bug fixes.

I have found another irritant. Occasionally, after working on a project for a couple of hours, something that I do causes the playback marker to only playback from the start. Switching to another movie, it works fine. Go back, playback is only from the beginning. I have to restart VPX to get playback to work properly in my movie. Anyone else seen this?

Other than that and the known bugs, it was a good week of editing.

@Trensharo

I can only comment on a few things. Codecs and all of the various abbreviations make my head spin.

"Upside down" interface is relative. Being a Civil Engineer, I always built from the ground up, so level 1 was at the bottom. This is my favourite feature of MEP/VPX. The background stays near track 1, so there is no inserting tracks every time you want to add something like a title. I know where my main video is; I don't have to scroll down hoping to find it somewhere down on track 32.

A track is a track, there are no audio tracks, composite tracks, adjustment tracks, or whatever else name of tracks that other programs have.

Video and audio go to separate tracks. The default when the program is installed combines them into one track. Change the default in Program Settings to put them on separate tracks and determine how you want the waveform shown. I always have video and audio on separate tracks automatically.

Same with the playback head. Change the default to "Playback stops at current location" or use the shortcut K to stop at the current location.

I don't see any workflow workarounds except with some of the bugs mentioned. Hopefully, they will be sorted out. The Music Editor thing is a bug, in my opinion. You won't see this problem if you use proxy files; I don't. The external editor can be changed to SoundForge, and it seems to work fine. Samplitude also works fine as the external editor, giving you access to the Cleaning & Restoration tools with Samplitude Pro X3/4 Suite.

Workflow - MEP/VPX probably have the easiest, most intuitive that there is, IMHO.

I haven't tried exporting to EDL, importing to Samplitude, for quite a while. Last time I did, it worked fine. I'll have to try again.

You can put VPX and Samplitude in master/slave or slave/master and run both at the same time using LoopBe1.

I have QuickTime 7 installed and never have to open it, thus my computer is not exposed to the supposed security problems. Why people get bent out of shape about this, I don't know. If you have MOV files that need QT like I do, just install it and be done with it, like any other Codec (my head is spinning).

John CB

Trensharo wrote on 5/17/2019, 12:49 PM

Nothing I use needs QT, except Vegas and this. Most other NLEs have native support for the useful few of those CODECs, like Animation.

VA tracks are a consumer NLE convention, because those users typically have small simple timelines and don't tend to do much with audio in the NLE. VPX timeline is like that of PowerDirector. That's just personal preference.

Video layers bottom to top in other NLEs because its logical. The top tracks are called OVERlay tracks for a reason. The timelines typically have a splitter and segregate the two (audio and video) from each other.

If you have 8 video tracks and 20 audio tracks, you don't want them all interspersed. That's an organizational nightmare, and the backwards timeline exacerbates this.

The Audio is layered top to bottom under video in other NLEs because Audio mixes, and video doesn't. It's just a logical layout - and not something I consider personal preference.

Scenestealer wrote on 5/18/2019, 1:45 AM

Hi @browj2

".....playback is only from the beginning. I have to restart VPX to get playback to work properly in my movie. Anyone else seen this?"

This has been a "feature" of MEP / VPX almost since they began.Cant say it has troubled me much recently though. Magix seems unable to fix it and their work around is to click the Optimise double headed arrow at the bottom right of the timeline, which works. But yes, it is a bug so should be included in the list.

I am with you on Quicktime - it just sits there and does what it needs to do. I think the security risk is if you use it to play content in a web browser but I think browsers have a setting where you can stop it from starting there.

@Trensharo

Audio mixes, and video doesn't.

Isn't an overlay a mix of two tracks? Magix calls Chroma Key a mix effect.

Peter

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1809, MEP2016, 2017, 2018, 2019 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

Trensharo wrote on 5/19/2019, 9:24 PM

 

Isn't an overlay a mix of two tracks? Magix calls Chroma Key a mix effect.

Peter

Chroma Keying is a compositing effect. Like blending tracks on the NLE timeline. Not the same thing.

If you put two video tracks one above the other, what happens? One will completely cover the other The o ly way to avoid this is by using blending modes, Alpha, or opacity controls.

This is what Keying does. It makes a certain color range Alpha (i.e. transparent).

Audio tracks will just play over each other - mixing. This is how stereo and surround auto files function. This is why you have to mix audio, so that it sounds good with all those channels playing over each other.

You composite video.

You mix audio.

Video naturally overlays, so putting the overlays "under" is illogical.

This is why most NLEs split Audio and Video down the middle, and stack them in opposite directions.

Track and Project Nesting (among other things) are ways some NLEs have evolved to make compositing easier (without going to dedicated solutions like Motion or After Effects).

Scenestealer wrote on 5/20/2019, 2:37 AM

Hi Trensharo

Chroma Keying is a compositing effect. Like blending tracks on the NLE timeline. Not the same thing.

From Magix Help files:- "This section contains the effects for chroma keying used to mix together two videos into a foreground and background." So I was not wrong!

I do know what you mean though and was just being a little mischievous. I can see that grouping the audio tracks separately as in other NLE's could be helpful but I think I am with JCB on the top to bottom ordering.

And....... you can mix the two video tracks by varying the brightness using the downward arrow handles at the top middle of the video clip......

 

Last changed by Scenestealer on 5/20/2019, 5:31 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1809, MEP2016, 2017, 2018, 2019 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

johnebaker wrote on 5/20/2019, 5:24 AM

@Trensharo

Hi

. . . . .Video naturally overlays, so putting the overlays "under" is illogical. . . . . .

That depends on personal experience and is an opinion.

Having worked with many different video editors, including Premiere Pro, Final Cut, Vegas Pro and a couple of old non NLE's, over ~20 years, my opinion is that having universal tracks and the stacking order are one of the most convenient aspects of the MEP/VPX editors.

Stacking tracks 'down' is not a difficult concept to get used to and is also logical, it is only the point of view and experience that is different. An analogy would be how one eats a boiled egg - Bigendian or Little endian?

In either case the end result is the same (unlike Endianness), however that is another topic.

Magix started with music making software where tracks are universal, then broadened their software portfolio with video editing software and, presumably, adopted the same approach for the video editors.

IMO the universal tracks are another good feature, how they are assigned to video/audio/images is personal preference and not restricted by the software designer.

We may have different opinions, on some aspects of the software, however the end result is the same - we help each other and create video.

John EB

 

 

 

 

 

 

 

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

browj2 wrote on 5/20/2019, 9:04 AM

Another week, no update. Sigh!

@Trensharo

Try to explain to a new user that your background video clips keep changing track numbers every time you add something like overlays and titles. Start with background on track 1, add overlays and title, it goes to track 4. Next video clip, well, track 1 is free so put it there. Add in overlays and title and it moves to track 4, but the first background moves to track 8, and so on. Soon, you have no idea where the background, is located; it could be on tracks 48, 35, 27, 10 and 1, depending on where you are on the timeline. The new user would not be impressed.

Watching Vegas tutorials, I keep seeing the user having to delete tracks because they deleted something on the highest numbered track, like the audio that came with the video, and thus have tracks further back than the background. Why? Because a higher numbered track is below the background. Strange system.

The only thing that I could think of, was that way back when a programmer was developing a video program, he needed another track for something, probably a title. So, inserting a track and moving the background down made sense to the programmer because physically, on the timeline, the top layer would be higher. Works great if there are only a few tracks. Then they needed more and more tracks. Since they were already stuck with the inserting tracks method, they kept going. This upside down system became the norm. Users think it's right because that is what they are used to.

Logical system - the background track is track 1 (usually). Think about it - background/bottom track - always the lowest (or close to it) numbered track. Open the program and you always see the background or base track. We mostly work with the background and want to see it. Anything that has to go on top of the background or bottom layer would naturally go on a higher track number (that is why floor numbering in a building starts with 1 at the bottom, not 1 at the top), no need to insert a track, and the background does not get pushed to a higher track number. Thus the MEP/VPX system is more logical and it's easy to explain this to a new user.

The only thing that I could think of to make this more logical would be to have track 1 at the bottom of the timeline window, with track numbers increasing towards the top. Upon opening a project, one would always see track 1 at the bottom, and the norm would be to scroll upwards to see more. This would satisfy users like you who want to see overlays physically higher on the timeline window. I prefer to scroll downwards to see more, but then, that is what I am used to.

Universal tracks - ditto what John EB says. And as I said, a track is a track. Multiple tracks show up on the screen when you open the program. Add more if required. Hardly ever need to delete tracks and don't have to delete tracks that have nothing on them.

Also, as I said, to have video and audio on separate tracks is simply a preference in the Program Settings. You have a choice and some users doing simple projects like to have video and audio on one track - they have a choice.

If a project is very complicated, which is rarely the case, then one has to do some track and object management, no matter which system you use. That is why there are track management tools, track colour coding and object colour coding, and track naming.

Again, we are way off topic; these are not bugs.

John CB

browj2 wrote on 5/20/2019, 11:34 PM

@Trensharo

You indicated that every EDL that you exported caused VPX to crash. CORRECTION: I just reread the initial post and it says that the EDL causes Samplitude to crash, not VPX. My error. I just ran a few tests, each with a different setup and exported 2 different ways to EDL, one with a mix down of audio, the other with "Hand over audio objects." VPX never crashed.

Likewise, opening these in Samplitude Pro X3 Suite worked fine. However, Samplitude cannot handle multiple video files, so if the movie contains multiple clips, it has to be rendered (mixed down) first. Also, any audio with video has to be mixed down, even individually. EDIT: to be clear, Samplitude will not import the audio of a video clip using the Handover method. The audio part needs to be mixed down first. This is done by setting a range and muting any other tracks that are within the range, then Shift+D to mix down the audio of the video file.

Can you demonstrate or describe what you had on the VPX timeline, including source type of video files, types of audio files, export as EDL parameters, and any other pertinent information so that we can test this?

I believe that you were using the trial version which has a limit on length of export. If you selected Export Video:Render videos, this could cause a problem.

I also tested exporting to EDL from Samplitude Pro X3 Suite - no problems.

Which patch of VPX were you using? What is your OS and hardware setup? What are your source file types, etc?

Perhaps someone else can test this as well.

John CB

Trensharo wrote on 5/23/2019, 11:18 AM

Another week, no update. Sigh!

@Trensharo

Try to explain to a new user that your background video clips keep changing track numbers every time you add something like overlays and titles. Start with background on track 1, add overlays and title, it goes to track 4.

That's not how it works, though. Track 1 stays track 1. The difference is track 2 goes above track 1 instead of below it; because it overlays track 1.

The difference is in the track order/layout, not in the numbering. The tracks don't change numbering unless you reorder them. They can also be labeled/named.

Even in image editors, the layers on top overlay those under them ;-) Bottom-Up is a pretty standard convention is creative apps that use layers. A new user who has used any of those will understand this immediately. They won't need any explanation unless they've never used any type of layer-based image/video editing software before.

-----

I was using the latest patch of VPX. MAGIX supplied me with a 30 day full version to test and make sure it wasn't just a trial limitation.

How many video tracks do you have on your timeline when you export to Samplitude? I read somewhere that EDL doesn't work well if you have more than 1 video track, and more than a few audio tracks.

There are many "varieties" of EDL out there, so this may be a limitation of [specifically] CMX3600 EDL, and not Samplitude/Sequoia's EDL format. Most documents talking about EDL refer to that variant (which is what PrPro and Resolve use, IIRC).

I'm assuming Samplitude/Sequoia use their own variant for a good reason.