Big Films effects already had trouble getting me a version of the effects that worked with Magix (16, 17, etc), and I had to be sent a different version of their drag and drop effects. I allowed for the new 2022 movie studio to be installed, and the effects worked inititally. After the last update, they all now no longer work properly.
Hi
Do you have Quicktime or Quicktime Alternative (preferred) installed?
What error messages are you getting - please quote in full or post a screen shot?
John EB
Forum Moderator
It doesn't have an error. Instead of being able to make it transparent, they now show up in black and white with scanlines (attaching a pic) and cannot be made transparent. They worked right after I upgraded to 2022, but after the latest update, they no longer work. I have the QuickTime clips formatted in png because the other type didn't work with Magix 16 - 18.
Hi Derek.
Are all your graphics drivers up to date? There have been more than a few driver updates over the past month.
Do not rely on Windows to update those but visit the relevant websites.
It would help if you would please keep your complete computer specs up to date in the signature portion of your replies as requested in the important posts section of this forum. Then we may be better able to diagnose problems quicker without the need to ask additional questions.
Ray.
I have updated all the video drivers. The only other recent change is going to Windows 11, but the Big Films effects initially worked properly after that update as well. The problem is still there now though after video driver updates. The videos also play fine on the computer separately. They just don't work anymore as intended in the 2022 suite anymore. What does show is off center (as can also be seen on the previous screenshot). The only thing that makes sense to me is that something from the most recent app update did this.
I can't update my signature for some reason.
Hi Derek.
It may be the case but unlikely that the program is not as Windows 11 compatible as it is within Win 10.
Did you also check your Windows 11 install was completely up to date?
Windows and driver updates should go hand in hand or the program may not be able to use some functions available within Direct X or your GPU may no longer be coping with new instruction sets.
Did you install QuickTime Alternative as John suggested? It is a requirement for all mov based files.
Hard to tell any more without the complete and full computer specs.
The last thing to try would be to disable any hardware acceleration within the program or turn off hardware acceleration for individual third party effects that can be an available option within certain effects.
If that works then there is a hardware software compatibility problem.
The signature is edited only within your personal login area of this site.
Ray.
Hi
. . . . I have the QuickTime clips formatted in png because the other type didn't work with Magix. . . .
Edit: removed incorrect statement
The issue with the PNG encoded versions I have seen before - when applying Chromakey Black to some, though not all, PNG or JPG encoded video.
Download and install MediaInfo and analyse one of the clips and post the results, see this tutorial on how to setup MediaInfo and analyse a video clip for all the data required.
John EB
Forum Moderator
Hi John, Derek.
If the Pro Res files are containing an MP4 codec using 442 rather than 444 they can be imported into MEP and used. They do not show correctly in the editor as I think Windows can't actually display them either but they can be successfully exported and do actually appear correctly in the preview monitor.
Ray.
Hi Derek.
I think you have found a new bug introduced into the last MEP and VPX update that has caused this problem.
I am going to start a new topic for others to check for.
Ray.
I've tried changing to Quicktime Alternative. That didn't change the symptoms. Here is the info from MediaInfo:
General
Complete name : E:\STARTER-PACK\EFFECTS\1 - EXPLOSIONS\06 - Explosions.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 2005.03 (qt )
File size : 96.8 MiB
Duration : 5 s 714 ms
Overall bit rate mode : Variable
Overall bit rate : 142 Mb/s
Encoded date : UTC 2016-02-12 22:50:46
Tagged date : UTC 2016-02-12 22:58:35
Writing library : Apple QuickTime
TIM : 00:00:00:01
TSC : 2997
TSZ : 125
Video
ID : 1
Format : PNG
Format/Info : Portable Network Graphic
Compression : Deflate
Codec ID : png
Duration : 5 s 714 ms
Bit rate mode : Variable
Bit rate : 142 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : RGBA
Bit depth : 8 bits
Compression mode : Lossless
Bits/(Pixel*Frame) : 2.858
Stream size : 96.8 MiB (100%)
Language : English
Encoded date : UTC 2016-02-12 22:50:46
Tagged date : UTC 2016-02-12 22:58:35
Other
ID : 2
Type : Time code
Format : QuickTime TC
Duration : 5 s 714 ms
Frame rate : 23.976 (23976/1000) FPS
Time code of first frame : 00:00:00:01
Time code of last frame : 00:00:05:17
Time code, striped : Yes
Language : English
Encoded date : UTC 2016-02-12 22:58:35
Tagged date : UTC 2016-02-12 22:58:35
Hi Derek.
If you can still import the file into MS but it still looks like your original screen shot, try the following.
It is not an ideal solution but may work.
Ray.
Thank you. It didn't work though. At this point I'm hoping another update comes soon and fixes it again.
Hi
Thanks for the MediaInfo data.
I have some PNG RGBA encoded files which, apart form the bitrate and framerate, are identical in the encoding format and encoder and they import OK into MEP/MMS.
I think we need more information:
Computer specification and program version, see this topic for what is required and please quote processor and graphics card make/model in full.
I would suggest you put this information in your profile signature so we do not have to keep asking for it.
Are the graphics card drivers up to date?
A screen shot of the Program settings, Display options tab would help.
John EB
Everything worked fine a couple months ago when I first accepted the upgrade to MS 2022. This all either started with the latest MS update or the WIndows 11 upgrade. Both happened within a week of each other. I double-checked though, and there is a video I rendered with on of the Big Films effects during the time between upgrading to WIndows 11 and the latest MS update.
Edition Windows 11 Home
Version 21H2
Installed on 3/19/2022
OS build 22000.652
Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz 1.80 GHz
Intel UHD 620 graphics card
Movie Studio 2022 Suite version 21.0.2.138 (UDP3)
Has anyone found anything on this issue? It's affecting my business.
I found a new clue to this problem. The MOV files show n.a. on color depth and color scanning under the object properties as shown in the attached image.
Hi Derek.
I spent more than 10 hours testing various Pro res files with MEP on Saturday and Sunday here (please read through it) and although sometimes annoying to use some Pro res files types I could not replicate your problem with similar file attributes to the one you published.
All the Pro res file types with one exception worked. Your file type (As far as I could replicate the file type) also showed up in the timeline OK and exported OK. (Check the data in the image above) While other Pro res files types that did not use a PNG encoding displayed similar characteristics in the timeline to your own uploaded images here, they too exported OK and did not appear in my monitor as your file seems to appear. Two other people also tried and had the same results as myself.
The only difference I can see is our systems also include nvidia graphics cards as well as a working Intel GPU.
There could be another reason such as a difference in the Windows versions used ( I am using the enterprise version of Windows and John is using Pro). or it could still be a driver issue.
Did you check you are using the latest Intel GPU driver (as John suggested) which is 30.0.101.1660
The only way to tell if that not having an nvidia graphics card is the missing link now in the ability for the program to use the files is for you to upload such a file to Dropbox or Google Drive and share it with us to test. As it is a bought file, I suggest you send a link to it via personal message to me and John Baker by clicking on our avatars. If we can get it to work then my guess would be Magix will not consider it a bug or try to fix the issue but instead suggest up-rating your system to the minimum required specs as suggested on their website.
The only other alternative is to ask Magix to send you a link to the last version that worked and re-install the program and don't update the program to any further new update.
Ray.
Hi Derek.
I have just tried one more thing as it appears that the Intel GPU is not doing much when Pro res files are present in the timeline.
All the hardware acceleration work seems to be done with my nvidia card .
Changing the program settings to use Microsoft WARP has forced the Intel GPU to do more work and ignore my nvidia GPU. It is working but the added stress to your CPU may make editing more difficult for smoother playback on your machine.
You can see in the last image that the Intel GPU is also working much harder.
Ray.
Hi Derek
. . . . I found a new clue to this problem. The MOV files show n.a. on color depth and color scanning under the object properties . . . .
Nothing to worry about there, I get the same with PNG encoded RGBA files that do work.
As @CubeAce has suggested upload one effects clip that has the issue for us to test and PM us the link.
John EB
I can verify John's observation about the colour space not being picked up by the 'properties' within MEP or VPX as not the probable cause of the problem.
As presently showing in the latest update of MEP / MMS.
Even in the older version of MEP or VPX, that data was never picked up on even though the files displayed and worked as expected.
Using my copy of VPX 12.
I realize these are not Pro res PNG files but my Copy of MEP like John's is not having any issues with those files hence the request for a file to test to see if there are any differences we can find out about.
As you may have noticed though. In the past (and present) Windows itself cannot produce visible thumbnails of those file types.
Pro res is not a proprietary Windows file format but one specifically for use within Apple products and programs. You cannot play such a file in any Windows playback program except VLC media player and even then doesn't scale properly.
Apple has always wanted an enclosed ecosystem. They do not play well with others and make it difficult for other platforms to accommodate which is a pity as some of their innovations would be a lot cooler if they allowed cross platform use.
But then again Apple can have problems with AVI file types as well which is easier to handle in a Windows program.
This is the downside to a 'healthy' competitive consumerism market.
We don't know what Magix has done to the latest update but so far John and I can't replicate your problem and Magix is probably unaware of this problems existence or even think it a problem if individual systems as they specify them are capable of handling such files.
All John and I can confirm is they do not always appear in the timeline correctly. Not that they do not work.
For that we need a sample video to verify.
Ray.
Here is a link to one of the mov files uploaded.
https://www.dropbox.com/s/1vpwxkzb9mbgnon/05%20-%20Explosions.mov?dl=0
Hi,
I tested this with both VPX13 and MEP2022 (21.0.2.138) and had no problems with either...except from some people walking their dogs in the woods.
Something is wrong with your setup.
What selections do you have under Program Settings, Device Options, Hardware acceleration for Import, Processing and Export?
John CB
Hi Derek.
Thanks. I'll copy John in so he can tell you when he downloaded it. Ideally bought files should not be shared hence we said give us links in our personal avatar areas. Once John confirms his download please remove the file from Dropbox. Once we have done our tests we will delete the file.
Ray.
I have already also deleted the file.
I'm attaching settings screenshots. This is how they always were before. I did try changing a few and then putting them back just to see if it helped.
I actually just found setting the processing to my video card fixed the issue. The only reason I had it as CPU was because it would error out when trying to export videos when I first installed MS 2022. On any case, it's working now with these settings. What do you think is optimal for import/processing/output?