Corrected my link above. Sorry Nick, I hadn't had my morning cup of coffee 😎

Are you f'ing kidding me?! I just spent $50 to wait 1 month to get something I should of had originally?! I have content that needs to be posted! How do I get my money back?

@Cornico Lol you must be working for Magix because what I'm watching on YouTube shows the same program I bought and users having the disable resample feature on it. Which means that the version magix is selling is a fake and they are unlawfully selling a copies at a reduced rate because this feature is not part of the FULL program they advertise it to be.

...the version magix is selling is a fake and they are unlawfully selling a copies...

Wow; hopefully that's just hyperbole. I understand your frustration and I offer all of you my personal apology for the mistake--I accept full responsibility. We are fixing the problem as quickly as we can.

In the meantime (for the record) the accusation that we are trying to cheat you somehow is utterly untrue. Casting such aspersions upon all of the good people who work in this company is not fair, not nice, and shouldn't be done lightly. Accuse me of what you will, but my colleagues don't deserve that kind of treatment for my blunder.

Adding my name to the list of frustrated new version 14 owners and the whole "disable resample" debacle. Would have been fine if you reprogrammed the software to keep it TURNED OFF but with the resample setting always on, my videos (especially timelapse clips) look like crap.

How long do we have to wait for this simple fix?

they have said ' couple of months' = April/May. It will be problem where ever the frame rate differs to the output frame rate - basically if you've slowed down a clip

Actually Tim I'm finding if I slow down a clip on the timeline MS14 behaves as if Resampling is disabled. The rendered file has additional frames which are copies. There's no ghosting from a crossfade effect.

But if there's a change of framerate then resampling does takes place and the extra frames created have crossfades or ghosting.

We are going to make sure video resampling works in the next update. Sorry about that...

If by making sure 'resampling works' you mean making sure we can properly DISABLE it...then that is awesome. As of right now the resampling of everything which ruins the final edit no matter the frame rate definitely is working.

And Tim/Eric, i'm actually getting this with my project and render frame rate set to 60fps, and ALL of my source clips are 60fps...yet the final render has ghosted frames everywhere.

PaintballTwin - are both your source and output 60 fps progressive? Also are you altering the playspeed on the timeline?

PaintballTwin - are both your source and output 60 fps progressive? Also are you altering the playspeed on the timeline?

Well, i never had an issue with it happening when resampling was disabled in MS12, so i'm guessing the sources are 60p. Whenever i watch the raw clips in a media player and pause actiony scenes i don't see ghosting. I can't find any specific tags in the files info that denotes i/p, so i've used the tools available to determine it is p. And the session properties and render both say the are p, unless they are lying to me, every setting i can find is set to p. Also, yes, i can read, and no, i'm not adjusting the play speed anywhere on the timeline. (because that only makes the ghost frames look worse imho)

I believe I speak for many new Movie Studio Platinum 4 users that we would all appreciate a simple GLOBAL ON/OFF option to DISABLE RESAMPLE for an entire video. Which, I believe, is currently available in the full version of Vegas.

I'd also like to vent that I lost the HITFILM Color Temperature Video Event FX. It was available in version 13. Did you take those effects away too? Can I get them back (transferred) into version 14?

I'm back to running version 13 until MAGIX can fix these issues. And if they don't start releasing timely updates, I'll be deleting it from my computer and requesting a refund. It sure doesn't feel like an "upgrade".

@LRay_Photo,

I'm sorry for your frustration.

How long do we have to wait for this simple fix?...And if they don't start releasing timely updates, I'll be deleting it from my computer and requesting a refund.

I wish that such fixes were as "simple" as you suggest, and that releasing updates was a low impact activity such that we could pump them out without testing, verification, and the time that it takes to properly prepare them. We expect an update before the end of this month.

...we would all appreciate a simple GLOBAL ON/OFF option to DISABLE RESAMPLE for an entire video. Which, I believe, is currently available in the full version of Vegas.

Yes, this feature exists in VEGAS Pro 14. It is a pro-exclusive feature.

I'd also like to vent that I lost the HITFILM Color Temperature Video Event FX. It was available in version 13. Did you take those effects away too? Can I get them back (transferred) into version 14?

We did not intentionally "take those effects away too," but that's not to say that there might not be an issue. Is anyone else seeing a problem with that specific plug-in? You may want to establish a support ticket if you continue to see this problem so that a solution can be properly pursued and tracked.

 

...we would all appreciate a simple GLOBAL ON/OFF option to DISABLE RESAMPLE for an entire video. Which, I believe, is currently available in the full version of Vegas.

Yes, this feature exists in VEGAS Pro 14. It is a pro-exclusive feature.

Did I read that correctly? You REMOVED a standard option in Movie Studio and only allow it to be turned ON/OFF in the PRO version???

If that is true, I will begin whatever process it takes to get a refund. Forcing the resample feature makes no sense and, in my opinion, makes this software totally useless.

However, if I misunderstood your statement, are we expecting this to be returned to Movie Studio in the "next month" update?

 

LRay - Magix have stated on several occasions that the resampling option will be restored in the forthcoming update. As for having it operate globally I would not like this unless it could be overridden for individual clips. Anyway Magix have said this will not happen in MS and it will be restored to how it was in MS13.

As for the HitFilm effects you had in MS13 this thread should help you make them available in MS14. Also the Boris FX that came with MS13. https://www.vegascreativesoftware.info/us/forum/hitfilm-light-flares-from-movie-studio-13-platinum-not-in-14-suite--105941/

Did I read that correctly?

No, you did not. As EricLNZ states, when we release the update, the exact functionality from VMS 13 will be restored. You will be able to set your resampling for every event. The "global" function that's being referred to is the ability that VEGAS Pro has that enables you to set your resampling method in Media Properties and then have every event in your project pick that setting up automatically so that you don't have to set each event one by one. That was never part of VEGAS Movie Studio and is the pro feature I'm referring to.

Not to start another firestorm, but we've unfortunately discovered a reasonably significant snag that will delay the update. Hopefully we'll see it in the first week of May.

@gary-rebholz - Thanks for being honest and upfront. It's never easy to announce that there will be delays.

Did I read that correctly?

No, you did not.

I'm not one to deny being wrong which is why I asked.

That sounds good. No "global" feature but restoring the "Disable Resample" in the next update (like before in v.13). That's perfectly acceptable.

EricLNZ - Thanks for the link above. I tried it just now and the effects moved over to ver. 14. I appreciate the help.

I wish that such fixes were as "simple" as you suggest, and that releasing updates was a low impact activity such that we could pump them out without testing, verification, and the time that it takes to properly prepare them. We expect an update before the end of this month.

You mean like you should have done BEFORE you released this garbage? (even basic menus not functioning, render button!!! nobody checked to see if the render button was even there?) Not to mention all the headaches that were incurred with the Pro update(s) as of late. As i've since gone back to using MS12 until you guys can ever get your crap together...should i be looking at switching to another company's product? Am i wrong to be upset to pay good money to essentially be a beta tester?

I see that this thread is in danger of devolving into one of "those" threads. I'm sorry you're not happy; I really am. And I understand why you're not. I already apologized for the problems. I already told you we're working to fix them. I already explained that these issues are always bigger than they must appear from the outside.

You're still angry, and I get it. No, you are not wrong to be upset. But now you're reverting to abusive language and all caps (the meaning of which I've no doubt you fully understand) as if that will somehow suddenly make me see the errors of my ways and instantly fix the problems. You are completely welcome here to express your frustration and anger. But if this thread devolves further into abusive territory, I will ask our moderators to close it. Then you can start a new one to yell at me, call me all manner of nasty things, and accuse me and my colleagues of illegal and unethical behaviors and motives. I fail to see how that will solve the problem, but...flame on.

@gary-rebholz I'm glad that you chimed in again, but if you want to worry about how the thread is deteriorating: if you have any method of dissuading/blocking/deleting unhelpful posts, like the latest (and a previous one) from the "character" above your post - who I am amazed to discover is apparently in charge of a Vegas forum elsewhere... 😂 - and perhaps give us some facts/gossip to go along with your assurances, then people would perhaps be less upset.

Having worked in software myself for a number of years, the reinstatement of a removed feature is pretty trivial, and we've been told that happened right away, as one would expect. However, we've since been told that other complications have arisen. In what way? As VMS 14 is essentially a reskinned SMS12 with a few features cut'n'pasted from SMS13 to handle 4K (or SMS13 with a darker SMS12 skin; you say poh-tay-toe etc.), what's the actual hold up? Are there plans to add more (currently) Pro features? Are there other bugs that are unconnected to this issue being worked on that are responsible for the prolonged delay?

Does Magix have some aversion to putting out incremental updates with, say 10 fixes in them, against more intermittent ones with 50 fixes? Have they asked the users what they'd prefer? If they are asking, I'd prefer both SMS12 and SMS13 would stop bothering me to upgrade to VMS14 every time I open them. Check the Registry if you have to: I already have. 😃

I've also reverted to SMS12 - mainly because all my old (and new) plugins work there - so if there is also a way for VMS14 to pretend to be SMS12 or SMS13 so they'd all work again in VMS14, I'm all for waiting a little while, but throw us a few crumbs can't you? 😜

@Brandigan,

Now that's the kind of well-reasoned, post I am happy to respond to.

As VMS 14 is essentially a reskinned SMS12 with a few features cut'n'pasted from SMS13 to handle 4K (or SMS13 with a darker SMS12 skin; you say poh-tay-toe etc.)

I realize you have no way of knowing it, so I don't blame you for this assumption, but it is unfortunately completely wrong. When we set about to create VMS 14, I made the decision to essentially scrap the code that had evolved into VMS 13. Why? Several reasons, but mainly because under the previous owner, it had begun to diverge greatly from our pro code base (VEGAS Pro) and to maintain that code base separately would mean our small team of developers would have to maintain two similar-but-definitely-and-increasingly different code bases. This, as you saw with VMS 13, also meant that the VMS line would continue to diverge from the pro line in look, feel, and function. Thus anyone who wants to move from VMS to VP would experience a transition that was more and more like learning a new product. As some forum participants seem fond of saying, "not a great user experience."

I knew there would be pain involved. Essentially, we had to start over with VP codebase and strip out everything that is a pro-only feature that shouldn't be in VMS. This is how some of these mistakes happened. I can see how from the outside it looks unbelievable that we could have made such "stupid" errors, but we're talking about hundreds of features and thousand of lines of intertwined code that were involved.

In the end, the good news (hopefully you'll see it that way), is that what we've now implemented is a system where when we work on VP, we're also working on VMS. So, if there is a long-standing bug that we fix in VP, VMS gets that fix too, not automatically, but with less work and less danger of two different solutions being implemented by teams that aren't communicating.

Are there plans to add more (currently) Pro features?

Well, there will be new features in future versions, but they won't be "pro" features. A good example is the multicam workflow we added in VMS 14. It is not a "pro" feature in that it is a bit stripped down from the full feature that is in VP 14. This has to remain the model, otherwise there's no distinction between a pro and consumer product.

Are there other bugs that are unconnected to this issue being worked on that are responsible for the prolonged delay?

Yes, several.

Does Magix have some aversion to putting out incremental updates with, say 10 fixes in them, against more intermittent ones with 50 fixes?

Not in theory, but unfortunately in practice there are limitations. Since you mention a software history, then you understand that every release has to have not only testing on what's been fixed or added, but also regression testing to try and confirm that nothing else has been broken in the process of the fix, and also general release testing to make sure all of the download and other systems are working properly. These things take lots of time, and that makes instant update releases highly impractical for us, especially since we're simultaneously making progress toward new features for future versions. As the Scrum Product Owner, it is my job to try to push for as many updates as possible, and my Scrum Master's job is to push back in an attempt to balance the frequency of such releases with all of the other work his team of developers must do. I may have gotten that balance of this one wrong, and if so, again please accept my apology. To exacerbate the situation, we found this new issue just as we were about to release it--which is why we do the testing in the first place.

I'd prefer both SMS12 and SMS13 would stop bothering me to upgrade to VMS14 every time I open them

If you're talking about the newsfeed or net notify messages that come up when you open your product, there is a checkbox on the newsfeed system to tell us not to send the same message again. In the old Net Notify system, there is a general preference that enables you to turn Net Notify off.

I hope these answers help you understand what's going on here on our end.

@gary-rebholz Thanks for the quick and detailed response. Scrum? I feel your pain. Could be worse. Could be Agile or any one of the other "Let's spend so much time doing the processes that no actual work gets done because we don't actually trust the people we're paying lots of money to to do their jobs properly without some software holding them to account at every stage. Breathe In, two three; breathe out, two three". 😮

Yikes! OK, so you first had to take what was a complicated (and potentially convoluted and ageing) code base for Pro, which had a) it's own bugs and problems, b) needed all the Sony references taking out without breaking anything and c) identify all the places where you could fork off 'reduced functionality' versions for the 'Studio' version. Then rewrite them, or adapt/wrap the original ones to behave, as far as the interface was concerned, identically to the 'Pro' versions, to produce a Studio version that's essentially a stripped down version of Pro.

Then add some new features to Pro along with all their 'reduced functionality' versions for Studio, as well as block up/hide all the places where there was no 'Studio equivalent' without the interface falling down a manhole when it looked for a feature that wasn't there.

OK, well, at least at the end of this process: all your routines will be 'Blackboxed' up to the eyeballs where the interface won't care if it's running on Windows, Linux, Mac or Android and you'll be able to slot in new features right left and centre without it throwing a wobbly. So, give it a year and you'll have no excuses not to make both Pro and Studio even more amazing! 😜

Seriously though, as NewBlue say it's your (Magix's) fault that (only some(!) of) my SMS12 and SMS13 plugins don't work any more, find what they're looking for and 'fake it'. I paid for them (indirectly through buying Suite), so I'd like to have access to them in VMS14, as I'm sure would everyone else with any history of using previous versions of SMS (I started at 11).

Oh, and I was worried turning off Net Notify would stop me getting any future news, but I guess at this stage they'll not tell me anything I can't get through VMS14, so I can risk that.