I assume you have raised this as a Support issue direct with Magix? If not, I think you should.
I wonder whether it is related to the problem that you and I previously discussed, that third-party effects either do not appear at all in the KF editor or, if they do, they cannot be deactivated? I have raised that issue as a bug and Support have acknowledged it and the developers are, apparently, aware and "working on it".
Magix upgraded my software and now it is totally unusable!! I was still trying to figure out the latest version, which I bought and paid for. And I only purchased the upgraded version so that I could use a. USB webcam. Magix told me that the USB webcam would not work on my 32 bit Windows 10. So, I purchased the newer version, then the webcam worked. Now, it upgraded itself to Magix Suite 2023, and I absolutely hate it so much that I'm ready to throw my laptop out the danged window! A simple thing like titling is ridiculously complicated now!! And my USB webcam isn't working with your "new and improved" version!! Plwase uninstall your "improvements". I will never, ever, EVER recommend this complicated software to ANYONE!! I am just a YouTuber who wants to add sone royalty free music to my videos, add titling, some pictures and thats IT. You people have made it so complicated that college courses are needed!! PLEASE UNINSTALL YOUR CRUMMY UPDATES!!
I have recently upgraded from MEP 2022 to MS 2023. I am having a problem Exporting one particular set of clips within the project.
The 10 clips concerned are from my camera (1920 x 1080 x 59.94) all taken on the same day, same journey and vary from 31.2Mb to 400Mb, with bitrates between 26,123 and 27,350 kbps.
If I enter these 10 files into the timeline BACK-to-BACK, the Export SUCCEEDS. However, if I introduce a 1 second simple Fade Transition between each clip, the Export FAILS, giving an Error Message containing NO Error code. (Additionally, if I do this more than a couple of times without closing MS 2023, it frequently freezes up, requiring Task Manager to clear it)
I have done a lot of testing using both the MP4 FullHD 1920x1080 59.94 preset and the MP4 Web 1280x720 29.97 preset (with amended FullHD parameters) to no avail. I have found that by removing clips 3, 5 and 6 from the project, the Export SUCCEEDS. I cannot understand why this should happen. There appears to be nothing wrong with these clips as they all play individually and, as mentioned previously, they WILL Export if no transitions are present.
I have experimented with the Bitrate settings within the Export presets, wondering if the differing Bitrates are a problem during transitions.
I have exported each clip individually to MP4, wondering if going through MS 2023 might help with possible compatibility problems.
I have tried entering clip 1 ten times into the timeline with transitions and this SUCCEEDS, so it's not to do with number of clips in the project.
I even used a File Converter application to convert all the clips to MOV files. Nothing has worked.
I have since uninstalled MS 2023 from my main (Windows 11) PC and reinstalled MEP 2022. All the above experimentation has been carried out on my spare PC (Windows 10) and the results have been the same, so it seems not to be about the change of OS.
MEP 2022 WILL export this project with no problem so I will be staying with that unless I can get this situation rectified somehow.
Has anybody got any ideas about what might be going on? Thanks.
. . . . 10 clips . . . with bitrates between 26,123 and 27,350 kbps. . . .
The above, and the exporting of 1 clip and loading 10 times works, would suggest the video clips are variable frame rate (VFR),
Try using a video converter to change the frame rate mode to Constant frame rate (CFR), both handbrake and Avidemux can do this, then import these into the project.
Thank you for your response. First of all, the videos were taken using a Panasonic compact camera.
As for the other part, I have used Wondersoft File Converter to convert my files. As I wrote before, I had tried this already (to .MOV files) but had not altered any settings and that attempt resulted in failure. After your suggestion I did the same thing but changed a couple of settings. Both the Frame Rate and Bit Rate have a default of "SMART FIT". CFR was not mentioned specifically in the settings but there was an unchecked checkbox for VBR, so...
I set the Frame Rate setting to 59.97 and Bit Rate to 2,000kbps. (I actually meant to use 20,000, nearer to the original video value, but made a mistake). Anyway, having discovered my error, I still loaded the files into MS2023. Lo and behold, the Export completed. I then did the same using 20,000kbps and this was also successful!
Now at least I have a workaround but, as you might appreciate, this is not a perfect solution. If the Export works perfectly in MEP2022 then I think it is reasonable to expect the same with MS2023. I didn't pay good money to upgrade to a faulty version that requires a lot of faffing around.
I did have another idea of my own whereby I would do an Export of all the clips Back-to-Back, taking note of the frame positions at all the junctions, then reloading the new MP4 file by itself, splitting the file at those positions and creating the transitions, but I haven't tried this yet.
I don't know what Magix could have done between versions but, as the saying goes, "if it ain't broken, don't fix it!". Do Magix read complaints on this site? I don't know how to let them know about this fault directly.
. . . . Both the Frame Rate and Bit Rate have a default of "SMART FIT". . . . .
That is both VFR and VBR.
Video is constant frame rate by definition though this was not explicitly stated when the standards were written. The increasing popularity of variable frame rate is a 'fudge' to squeeze more video into the memory space of mobile devices.
MediaInfo will tell you exactly what the minimum and maximum frame rates are - for small variations MMS can handle the video correctly, however wider ranges are known to cause issues - to setup MediaInfo correctly see this tutorial.
VBR is the norm for video as this allows the encoder to use more data bits for higher detail scenes and less data bits for lower detail scenes while maintaining the Average target bitrate - the use of CBR should be avoided.
Thank you for the further information you provided. I will have a look at this Mediainfo thing you mention.
However, I have to say that I am certainly no expert on the finer inner workings of movie file production. That is why I suspect that Mediainfo will go far over my head and is why I buy something like Magix Media Studio. I do that so I don't have to worry about the technical side. Import->Edit->Export, Bish Bash Bosh!
So it's not really extra software I require, especially when Wondersoft File Converter has enabled me to obtain a workaround for my exporting problem already with this particular set of .mp4 files. I have no wish to work or dabble with Constant Frame Rate related issues etc. at any level. I shouldn't have to.
What I want, and expect, is that a procedure like exporting files, that worked with no trouble in MEP2022, should still work in MS2023.
Something surely must have changed in coding somewhere that has caused this problem. Maybe the coders found a tweak that would enable ever faster movie processing but has had consequences elsewhere in the system. Or something of that ilk.
I have had experience of C and C++ programming so I know I can happen. Why would I get Error Messages with no specific error number? Errors that eventually end up freezing the application unless I reboot it each time it happens.
Until Magix become aware of a problem, it will never be fixed. I AM starting to wonder if I'm the only person in the world who has been unlucky enough to experience this though lol.
I have been using Movie Studio 17 and have had a difficult time getting keyframes to work properly. I was using them on video trying to zoom in on some activity in the back of the frame. I could see it on the keyframe window but I could never get it to show properly on the main video screen after I closed the keyframe window. Does Movie Studio 2023 do anything to improve the keyframe functionality. It should be easier to use and something that can be included in the video when it is rendered.
@ericlnz I did post a question a while back but the person who answered only talked about how to do the keyframes with a still picture. I could never get it to work with a video clip. Do you recommend the download version or the subscription version for the 30 day free trial.
Personally I'd download the perpetual version, not the subscription. Also the Platinum version, not the basic.
With VMS the basic version was a pain when dealing with problems due to its cut down nature. I'm saddened that Magix haven't dropped this from the "new' Movie Studio.
Do you recommend the download version or the subscription version for the 30 day free trial.
Mimi, the free trial is just that; only when you decide to buy do you need to choose between the subscription or perpetual versions.
As @ericlnz has said Magix Movie Studio is a completely different program to Vegas Movie Studio in every way, so be prepared for a surprise. That said, we think it is a great program.
Here is a tutorial in which I show keyframing on an image starting at about 5:50. There is no difference between keyframing an image and keyframing a video.
However, it was done with an older version. Magix has changed the View/Animation - Size/Position effect to include Rotation. There is no longer a Rotation handle on the preview monitor, unfortunately, but there are more sophisticated 3D type rotation effects.
Since you're coming from Vegas Movie Studio, you may want to watch my other tutorials, especially Getting Started in MEP (Movie Edit Pro = Movie Studio) part 3, and the Basic Editing tutorials.
You'll note from the above tutorial one of the main features of Magix Movie Studio that is not in Vegas Movie Studio - Movies or multiple timelines.
As has been pointed out, do not get the basic version of Movie Studio. I agree with @ericlnz that this product should not be sold. Users very quickly run into frustrating limitations.
For any more questions, I suggest that you open your own thread as this one is supposed to be about feedback on MS 2023. Otherwise, your questions/answers will just be buried in a thread with no pertinent title.
I have had similar temporary freezups over the last week or so but with VPX14 and with Sound Forge ACL3 and Samplitude Pro X3 being used as External Audio Editors. I'm on W10. It doesn't happen in every project or all of the time. I have even had my computer freeze right up once and had to do a button shutdown. Something has been going on, but what.
In your case, it could be W11.
Also, what are your project settings and Program Settings/Device options?
What is the resolution of your screen?
I used Full HD, 29.97fps, Processing: NVIDIA GeForce RTC 3060 and the other two are Intel IHD Graphics 630.
I did a similar test with MS2023 and here is what I got:
Try clicking on the effect you wish to select in the area you ringed off in your image until it turns blue and see if that activates the key frames for that effect.
I just downloaded a trial version of Magix Movie Studio 2023. I have a very short video, less than 2 minutes, that I took with a GoPro 11 camera. It is in an MP4 format. But when I try to upload it into the program to edit it, I get an error message than makes no sense to me. The dialog box in the screenshot below is hard to read but it says "Unfortunately, the function 'HEVC-Codec' is not available due to licensing conditions". My computer is a Dell XPS15 9510 w Intel i7-11800H processor 64-bit using Windows 11 Home