Hi Ray,
Your observations are right on track - I think most everyone using MEP and even VP-X went over to Win 10 - I say this from the reaction I got from Magix Tech Support - certainly they were not looking at Win 7 problems esp if they were minor - remember Magix is a business and follows the trends - Now I do think MS is working behind the scenes to keep developers loyal to their brands of software and current OS (Win10) you can guess what that means - so people like myself are going to loose out at some point - I use UBUNTU on my Internet machine and it is AMD driven - at 1st UBUNTU was hard to understand and reminded me of the old Radio Shack TRSDOS OS - not friendly esp coming from Windows but once you get into it it's great as a OS - robust, Very FAST, and just solid where you need it (not going there) as for NLE migration - since I do a lot of basic NLE functions and all my Gee Whiz in Lightwave (really neat stuff) I just want a NLE that is robust and does Professional output rendering i.e. good codecs - I manipulate all my video via a 3rd party software that is FAST but also it trans_ codes, and trans_ rates tons of formats plus gives you many options with these functions and even does audio like .mp3 - so again I just need a NLE that is reliable from release to release and runs on UBUNTU. At present I haven't found one that provides this under UBUNTU - they are getting close and it's not free - actually expensive and using the ADOBE business case of annual licensing but I suspect Magix is going there in the near future so what's new? If Magix supports UBUNTU I'd certainly stay with their software - matter of fact I keep telling COREL if they do this I'll buy all their software (they only have one program at this time under UBUNTU) so if Magix does this 1st that's where I'm going. re: Video cards I only use GeForce GTX 1060 SC 6 GB GDDR5 single fan cards - remember I have 4 on their own Ethernet network working in parsing out Lightwave renders - I did this as this arrangement is stable as heck and biggest bang for the buck and even have spares like in the AMD machine I'm using now so out of desperation I can run the network with 2-3 PC's or take cards from machines not being used for parts r even put a 5th PC on line to improve rendering times as 4K 3D is very storage and rendering intensive. I render in Uncompressed Raw for video and stills and use Sony 3 chip MOS camcorders and Fuji XT3 cameras for stills and also video output to a Ninja 5 via the HDMI port - either Apple Raw 4.2.2 10 Bit or HEV265 are native to this camera arrangement. I just bought into the Fuji GFX 50R MF camera and several lenses - Always loved my 1st MF Fiji that used 4x4 film and now this MF digital with 50 Mp is out so for landscape and studio I'm going there for stills - the video on this is just HD so useless compared to the XT_3 but the stills are magic. That's it - thanks again for the info and conversation - hope this helps with your work in some way - best.
Hi
Magix is using the integrated H265 support from Win 10 and Win 7 doesn't support H265
I don't believe this is correct. Magix MEP does not rely on Windows codecs for import and playback. It has it's own embedded. If you read the specification for MEP it has a tick next to Import and Export HEVC but a foot note that says " **HEVC encoding require a fee based activation." H.264 is similar but need a free activation to encode
Ray, we discussed this situation on your Win 7 machine a while back and you said you could import and play H.265 but a thumb nail for the file would not come up in Explorer.
Peter
Actually I have not had an issue with MEP 2019 or 2020 importing or exporting H265 - I was also referring to XP 11 with the update version I listed - XP 10 and early XP 11 releases worked fine as well - XP 10 was slow to encode but read H265 normally - early XP 11 releases were faster Encoding and Exporting - then came my current release 17.0.1.27 and that ended the import of H265 video - it exports fine but no import - even it's own exports or other sources of H265 (HVEC) video. I suspect XP11 current releases are using Win 10's native codecs and certainly Win 7 has no HEVC Native support. How MEP 2020 does HEVC H265 has to be via a codec and I do have other HEVC codec's on my machine but doubt MEP 2020 is using them - could it be using the codec for XP 11? as I never purchased an optional HEVC codec for my 2019 version? and how can I tell what codec it's using - I can tell you it works well - good video quality and fairly quick exporting ? I originally started this thread cause I couldn't install the MEP 2020 upgrade - 2019 was working fine at that time - it went from there. I have noted on 2020 there are features missing from 2019 - did 2019 support HEVC natively and now Magix wants a optional fee for the HEVC codec on 2020 and could it be since I upgraded to 2020 on the optional upgrade program they are not enforcing the new optional codec fee for new 2020 users? Only thing that makes sense to me. All I know is my system is working fine excepting the import of HEVC on XP 11 and I no longer use that SONY Intra I codec I bought as all my work is now done outside of my NLE. I take my proprietary SONY S,L and I video and trans code it to 422 10 bit uncompressed Raw and take it into my NLE so I am relying less on my NLE for support excepting basic NLE functions and Uncompressed RAW .avi exports. Hope Magix starts supporting UBUNTU ! Best ...
Hi Peter. That is correct. That is why I needed the Microsoft codec for playback within Win 7. I think some versions of Win7 or 8 came with the codec while others did not but I'm not sure.
No, I've still had to activate the paid for codec to get H265 reading and exporting on my machine despite having an Intel GPU, VPX should not need it I understand correctly but MEP Premium does. The last versions and before (2018) were the same. If you had the paid for codec like I did you can contact Magix for a new activation code. To get to it use MEPs download manager to look for additional content. Both that and the alternative paid for MP4 codec should be there.
You have just written you have additional video codec packs on your machine. That is known to have a detrimental effect with MEP. John EB. may be able to tell you why.
Ray.
Hi
I concur with @Scenestealer's comment MEP and VPX come with their own h.265 codecs. The activation of the encoder is fee based for MEP.
VPX 10 and VPX 11 it is installed and activation is included - I assume these are what you are referring to when you say XP 10 and XP 11.
An Intel GPU is not essential for HEVC only in VPX 10 and 11 as they can use a NVIDIA GeForce 1050 or better graphics card.
. . . . additional video codec packs on your machine. That is known to have a detrimental effect with MEP . . . .
That is correct, there may be up to a hundred or more codecs and DirectShow filters installed on a PC. When installing codec packs, some can get corrupted or incorrectly installed if you update a codec pack, or promote the priority of their encoder over the software preferred codec, these can cause issues either because the 'new' codec causes the program to crash or give an error message, or does not behave in the same manner as the one the program is designed to use.
John EB
Hi John
Yes I was referring to VPX 10 and 11 up to the version I referenced as I haven't renewed the update program re: MEP I did and I'm finally running the update for 2020 and it runs fine - does H265 export and import and I never paid for that codec? - re: Codec packs - actually I think you are referring to actual CODEC PACKS - err, I don't have them as I understand your reference - my Codecs are associated with software not just a universal Pack of Codecs - so they are compatible with those software programs and they are specifically named and have controlled access so Magix couldn't access them if it wanted to so I doubt these are issues with my Magix NLE programs - also, had a little time to play with these NLE's and they do not act exactly like you guys have indicated so it makes me wonder if Magix has different changes between version updates - one example - for VPX 11 I bought the Optional Sony Intra Codec for their S,L, and I Codecs - like I said I am not using it anymore and went external - being curious, I looked in VPX 11 to see if my Codec was listed as avail - NOT, no reference anywhere - yup the .MPG4 and Audio for 5.1 was there but NOT the INTRA Codec - since I had recently shot some SONY footage I decided to try and import the .MFX file and Guess What? - Magix VPX11 jumps in and says - the INTRA Codec will NOW BE Downloaded OK? - Where did that come from ? I had spent some time searching to no avail and here it was - err, my point is - 1/2 the time I never know what and where these things are located and from update to update some functions, and options seem to change or disappear with both of these NLE's and that is why I finally said enough - and stopped updating VPX11 and now do most of this work outside of the NLE's so I have some control. Don't get me wrong, I like Magix NLE's but I'm convinced that the software developers DO NOT DO NLE FOR A LIVING OR ANY SERIOUS AMOUNT OF NLE CAUSE IF THEY DID - THEY WOULDN'T MAKE THE CHANGES AND CODE LIKE THEY DO - THESE GUYS ARE JUST CODERS NOT SERIOUS USERS OF THEIR SOFTWARE. Any rate, my Magix software works and I'm OK with the few limitations - thanks again for the responses and information - best to all on the forum.
Hi
I'm finally running the update for 2020 and it runs fine - does H265 export and import and I never paid for that codec?
No surprise there! MEP would have picked up the codec from your VPX installation.
I decided to try and import the .MFX file and Guess What? - Magix VPX11 jumps in and says - the INTRA Codec will NOW BE Downloaded OK? - Where did that come from ?
Or there! you would have paid the fee and the program would have downloaded the required codec or access after being prompted by the program when you tried to import, or export the Intra material.
my Codecs are associated with software not just a universal Pack of Codecs - so they are compatible with those software programs and they are specifically named and have controlled access so Magix couldn't access them if it wanted to
This is true with Magix NLE's and apart from making sure licensing / royalties are paid to the codec supplier, is likely to prevent just what John EB is referring to with codec packs whereby they codecs could overwrite the "Merit Values" of other codecs on the system. I don't have experience with Non Magix NLE's but Magix may be unusual in that it will share the codec between its products the same way it shares plugins. Anyway that's all good for us!
did 2019 support HEVC natively and now Magix wants a optional fee for the HEVC codec on 2020 and could it be since I upgraded to 2020 on the optional upgrade program they are not enforcing the new optional codec fee for new 2020 users?
No and No!
I can not say why your VPX11 will not import / play HEVC after all the advice offered here, but if you do solve that you will be amazed at how it previews on the timeline with the infusion engine and the Nvidia 1060, and the speed it renders at using the NVENC chip on the same card.
Peter
Ahhhhhhhh - the plot thickens - re: that Intra Codec for those pesky Sony Codecs that VPX11 wanted to install - I quickly plugged in my WiFi modem and it installed real quick (had to be very small file) - message read successfully installed and some thing like ready to use or whatever and ... didn't even require a restart like a patch so I thought - bet me - gotta see this and clicked on the file and poof it loaded to the timeline so I - clicked the time line and the video and audio played just fine - No Big deal - from that I assume the codec wasn't on my PC and a bit was set to enable the codec somewhere on my PC cause it was way to fast for the request to go to Magix and back ? Yes that no reading the H265 on VP11 is still a mystery esp since it writes H265 - I did forget to mention that it loads the H265 files to the timeline but just plays the Audio part not the video err, and no video is displayed either - might be a clue there ? Like I said - other than that - both NLE's work normally i.e. not overly fast but not slow either like any other Win7 Intel I7 16 GB @ 4.0 GHz running 2 TB of Samsung 860 SSD's. Oh, not sure if you noticed but I went back and installed VP10 (had to remove VP11) and activated VP10 and it runs H265 export and imports - now H265 export is really slow and always was - import is normal - with VP11 H265 Export and Import improved measurably - Ok that's my story and I'm sticking to it LOL :-)) thanks for the info and help.