Crashes for burning 23.976, Audio support, options not saved...

clement5 wrote on 2/7/2022, 5:04 PM

This is a set of 5 reports which need to all be handled.for Media Edit Pro 2022
1.  Crash - I have an HD 1920x1080 video at 23.976 (24000/1001) fps and any attempts to "encode in directory" causes a crash.  I have also tried to export an MP4 at the same frame rate with a similar crash.  This is a serious problem
2.  IEEE WAV codec unrecognized - MEP does not decode the IEEE float audeo codec.  
3.  Frame rate not saved - When I set the frame rate and then close the window, save the project, and then open the Blu-Ray burning window my selected frame rate is still there as it should be.  But if I exit from the project and than return to the burning section, my frame rate is not longer set to23.976 (~24) fps.  This has been a persistent problem with all of the burning menus and the various options.  The options should all be saved for each project so that when someone returns they can burn that project in exactly the same fashion and different projects should each bring up their own set of options.
4.  Incorrect magnification for setting background - This has been a constant problem for the entire life of MEP and apparently nobody has complained.  In the burning menu while "previewing" the Disk menu click the Edit tab.  In the disk option sidbar click the Video box, the click use frame from movie box.  The first time you do this with a new project the frame image in the window is displayed at full pixel size which means it is unrecognizable.  However if you click OK, and come back the image is recognizable.   In reality the images are too small and the sliders difficult to use, so I would suggest a pop up large window with the slider and frame selection at the bottom to replace those small windows which are relics from the old SD monitors.
5.  Use Current terminology - Since MEP is advertised as user friendly, the current terminology should be used so "directory" should be changed to "folder".  The term that I used as a system manager and programmer is not used by most users, and should only be used in technical articles, not in user friendly programs.
Here is a link to some test files and screen shots.
https://1drv.ms/u/s!AgEkZSUlkAcxgb0eg2M8ATSCee6zgQ?e=tFsCOr

--------------------------------------------------------------------------------------------------

Above is the message to support. Since I tend to find the bugs maybe they should hire me to find the problems. The problem of options not being saved, or saved as a program wide option is a big problem. Things that are set while creating a project should all be saved just for that project, and only things saved in the "program" setting should be true for all projects. They seem to be equating user friendly with limiting the options and taking away features that we used to use. In the process they are careless about how this is implemented. One of my favorite bugs is removing support for .JPS, which is just a JPG by another name containing side-by-side or over/under L/R 3D frames. Most other editors support it, but usually just as a standard JPG.

Comments

CubeAce wrote on 2/8/2022, 11:17 AM

@clement5

Hi.

I am completely confused by some of your above statements and inaccuracies not to mention your complete lack of your system details of every post you put up.

One at least on one occasion you have been asked for your computer specifications which should be given in full when requested and to date looking through your older topics I have yet to see a processor identification number or graphics card model mentioned.

The system specs mentioned of the Magix website are specific meaning you need to have all of the specified components to meet the minimum requirements to run the program at it's basic level. Beyond that the specification requirements can leap by a wide margin.

Then you say things like

MEP does not decode the IEEE float audio codec.

That is simply untrue. The files you link to are non standard avi video files that MEP does not support or have the codec for. Unless you made avi copies of the 32 bit float audio and put them into a video codec. If so what did you use? If not why did you not just import the 32 bit float wav files into the project?

Trying to import the downloaded files you had on your OneDrive link MEP immediately told me it was not possible and the reason why.

Whereas a genuine 32 bit float wav file can be used.

Crashes in my experience have most of the time been caused by hardware problems but without enough information from a user or supported files for us to test this is impossible to verify whether it is indeed a bug or a hardware deficiency or a lack of up to date video drivers.

There are people here willing to help but can only help if they can verify if something is a bug or not.

That needs additional information and where possible files to test for ourselves.

Ray.

 

 

 

Last changed by CubeAce on 2/8/2022, 11:19 AM, changed a total of 1 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

Former user wrote on 2/8/2022, 12:27 PM

@clement5 @CubeAce 

1, 'HD 1920x1080 video at 23.976 (24000/1001) fps crash' ? that tells nothing, "any attempts to "encode in directory" can you explain this?

2, I tried 2 IEEE options, Wave (Microsoft) & Sony Wave, Wave (Microsoft) loads into MEP Sony doesn't, so 'MEP does not decode the IEEE float audio codec' is a bit random without more specification,

3. I haven't had any problems with projects not saving,

4.  'Incorrect magnification for setting background', Yes on m 34" 4k screen they are a bit small but on my 24" they're fine, this could be looked into, this problem persists in many programs, but as @CubeAce says you haven't given any of your system or monitor specs,

5.  'Use Current terminology' 'directory" should be changed to "folder"' , I think your splitting hairs,

If your going to be sending this in maybe you should refine it & inc the needed info, I couldn't be bothered reading first time i looked & prob why this is only the second reply you've got.

johnebaker wrote on 2/8/2022, 12:44 PM

@clement5

Hi

In addition to @CubeAce comment

Taking your points:

  1. Is there a reason for Encoding in Directory? This option is a halfway step to burning ad DVD or BD disc, encoding all the files required for the DVD/BD in a folder , however it will not go on to the next step of creating an ISO file, if Image Recorder was selected, or the final disc.

    As the crash also occurs when exporting MP4 this is often caused by a video/image/audio object or transition which which is causing the encoder to trip, an Error -5 message will be placed in the log file.
     
  2. As @CubeAce has commented and which I agree with
     
  3. When you change a parameter/setting in the export or burn dialogs and then do not export, burn a disc or create the files with the option in point 1, on exiting the program the change made is detected and asks if you want to save the project. If you do not save the project then the changes made are not saved.
     
  4. This is a bug - please raise a Support ticket - link at top of page and follow this article to navigate through the support system.
     
  5. Depending on your global location, Directory and Folder are both valid name identifiers and are used interchangeably.

John EB
Forum Moderator

 

Last changed by johnebaker on 2/8/2022, 12:45 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

CubeAce wrote on 2/8/2022, 1:30 PM

@Former user

Hi Gid.

A Sony Wave or wav file may have a Digital Rights Management code embedded into it before a copy of the file can be edited. It may play normally but MEP will pick upon any DRM coding within a file and will not play any form of DRM encoded file.

It is also possible to put DRM into any Microsoft wav file if you have the capacity to do so. I used to be able to do that when I could use my TeraTec sound card.

The only reason for using a 32 bit audio file is when recording live. It prevents clipping and the need to keep a close eye on levels. With a noise floor of 1528 dB it surpasses any sound that can be make on earth which would have a maximum dynamic range of 210 dB. That is purely theoretical as anyone listening to a volume of 190dB would probably be dead at that listening level. Ear drums burst at around 140dB. Most microphones have a capture range of around 96dB although the sound pressure levels to power them can vary depending on their intended use.

Ray.

 

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

Former user wrote on 2/8/2022, 1:45 PM

@CubeAce 👍 I did have to Google IEEE & read about the db levels, the Wave (Microsoft) & Sony Wave i created with Vegas but it's all a bit beyond me, i don't use anything but the default audio that comes with the video format, but this OP seemed to be lacking in so much detail that i had to look it up & try the things mentioned, & i'm always up for a bit of learning, 👍

I read this, clear as mud 🙃🙃🤷‍♂️🤸‍♂️🤸‍♂️😂 https://www.sounddevices.com/32-bit-float-files-explained/

clement5 wrote on 2/8/2022, 2:30 PM

Support has finally acknowledged my inquiry.

1. While folder and directory are generally used interchangeably, there are many people who do not know this. Folder has become the common word used in "applications" so directory has now become the computer professional word, and folder the common user word which appears in user manuals and help. So, to make MEP more user friendly they should use the common word. It is possible that folder will become obsolete when nobody uses paper folders anymore, but older people still often use them along with paper calendars.

2. MEP used to decode the IEEE format, but when I reinstalled it after a crash and full system restore it no longer does that. The problem is that another program (VirtualDub2) created the video file from a PAL file without DRM. I worked around by using another program to convert the IEEE format to standard old wave. Eventually I will get VD2 fixed so it can output the old standard WAV files.

3. As to putting the output into a "folder", it works just fine for standard NTSC, which is then telecined to 29.97. I want to produce a Blu-Ray without any built in judder. MEP has had many problems with 23.976fps in the past. Why put it into a folder, why not? I select the folder I want.

4. I looked at my settings, and they indicate I should be receiving mail from replies, but they are lost in the WOM (Write only memory). I have saved the options (parameters) before exiting, and they do NOT return. This has been a perennial problem with MEP.

clement5 wrote on 2/8/2022, 2:47 PM

Support gave me info to be able to download the IEEE codec. It consisted of Help/Install Extra Content and then select the codec I need, but the extra content was just the design stuff that came with my version of MEP.. As to confusion, I supplied test files in the OneDrive box, so anyone can test my assertions. If there is a hardware problem, it is not evident in other programs, and I have run the test program several times after the crash. Apparently, the problem with the IEEE audio is happening to others as they had sent me a link to a form where I could click yes or no if their fix did not work.

clement5 wrote on 2/8/2022, 3:02 PM

Hallelujah! For some reason I am now getting the replies from my posts, but I haven't changed a thing! I guess it was Black Magix. After thinking about the problem with 23.976fps, you should know that Magix had problems with it before. When exporting at that bit rate they had the wrong frame rate, which was unobvious because often that is quoted as 23.98. Looking at the integer rate it was not 24000/1001, but some other number that I do not remember. Finally they have fixed it, I think, after acknowledging the problem. I have not run an exhaustive test on it yet.

johnebaker wrote on 2/8/2022, 3:25 PM

@clement5

Hi

The folder/directory 'issue' is a matter of semantics.

. . . . nobody uses paper folders . . . . correct - they are plastic now.

. . . . which is then telecined to 29.97. I want to produce a Blu-Ray without any built in judder. . . . .

So the process you are using to go from a PAL file to Blu-ray disc, is via converting the framerate through 2 conversions ie PAL 25 fps → 24fps → 29.97fps NTSC and 2 re-encodes

. . . . I have saved the options (parameters) before exiting . . . .

Assuming you are referring to the parameters in the encoding presets of the burn dialog, they are not saved - the presets always revert back to the standards formats/settings - this is normal and not an issue.

You can change the parameters and then save them as a custom Preset for the encoding section of the burn dialogs as seen in the image below

I also have several presets for exporting to MP4/AVCHD video file as shown below.

Make the changes you require then click the Save icon, name the preset, do not change the location of the preset, and save .

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

johnebaker wrote on 2/8/2022, 3:34 PM

@Former user

Hi

. . . . Yes on m 34" 4k screen they are a bit small but on my 24" they're fine, this could be looked into . . . .

From @clement5 description, I believe he is referring to the bug shown in the image below - the left image is what you see when you first select a frame from the current movie, the right is what you see when you go back to the same dialog again in the disc menu editor

John EB

 

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

CubeAce wrote on 2/8/2022, 5:13 PM

@Former user

Hi Gid.

That is as good an explanation as you will probably get on that link Gid.

If you consider that a 3dB increase is a doubling in volume (assuming power increase is a linear proportion to speaker cone movement) but a 10dB increase is needed to 'hear' the doubling effect (age dependent and air displacement dependent) then you begin to realise how silly bit depth can get in audio. I don't have a dedicated sound card any more as the S1220A sound chip on my ASUS motherboard already exceeds the capability of any of my power amp and speaker combinations and a noise floor way below that of the amps I use at 113dB for the inputs and 120dB for the output. It also supports 192kHz 32 bit playback.

MEP on the other hand is limited to outputting 16 bit and 48kHz at the most using whatever codec is now available within the program.

VPX can do better with wmv files allowing for a 96kHz 24 bit audio export whereas MEP is limited to 48kHz 16 bit using wmv.

At the end of the day though the audio will only ever be as good as the weakest link in the chain. For most people that would be either their microphone or their DA/AD convertors or the components (unless they are buying in higher quality samples) in the final listening setup. Speakers /headphones/ amps etc. None of which on my system exceeds 97dB as a noise floor, which quite frankly is too loud. I probably monitor at levels way below that. Say 15 to 20% of full rated volume before clipping.

Sampling frequency is much more important than bit depth for perceived quality as that allows for much more detailed recording of the shape of the audio wave and even then you need a premium DAC set to not get into trouble. I'm not even sure my ears are up to telling the difference any more at that level of performance.

Yes there can be audible differences when using higher bit depths and sampling rates within a DAW or Video editing program, but equally good recordings can be made with better components in the chain at lower bit rates and sampling levels. They will always win out over trying to record information that was never there in the first place.

[Edit]

One thing a lot of people don't realize is not to turn down the volume of the computers audio output when plugged into an external amplifier. That should be so the input stage of the amplifier is getting the maximum signal to noise ratio into its first stage if it has a line input that can then be controlled.

Ray.

Last changed by CubeAce on 2/9/2022, 12:39 AM, changed a total of 2 times.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

clement5 wrote on 2/9/2022, 4:57 PM

The conversion from PAL to NTSC 23.976 can be done in just one pass using VirtualDub2, and the result was a playable AVI file. I always use Lagarith for intermediate steps to avoid multiple reconversions between lossy codecs, as fixing old movies often requires multiple passes.

OK, so the bug in the disk burning background menu has been confirmed. This has been there through many iterations of MEP and is just a sign of careless quality checking. The small slider and window is also a problem, but is often a problem in other programs.

As to the burning options not being saved, some have been saved as a program option and are the same across all projects, but others are not. There is also a problem that I complained about in the past that when setting burning or export options, going to an advanced menu reset unrelated options on the previous front menu. But this happened for some output codecs, but not for others. Again, very inconsistent careless coding. In particular with respect to saving options, I manually set the bit rate so as to not exceed the capacity of a 25G blu-ray with the 23.976 output. When I came back the same bit rate was still set, but the output had been reset to 29.97 (Default)????? Why go back to 29.97 when the input is 23.976 standard NTSC?????? I have wasted more time and discs by not noticing the squirrely inconsistent saving or not of options.

In the past when burning an NTSC dvd the code set the telecine parameters incorrectly to progressive or top field first. I am sure that the users in the NTSC zones never noticed this, as they only concentrated on getting a DVD. They didn't notice how the result was smeared or had more obvious judder. I think they still haven't gotten it quite right. I notice things like this because I restore old movies which have to be detelecined first before fixing things. The developers of course are in a PAL region, so they have less concern with NTSC standards or common practices.

BTW the audio quality on my restorations is generally not a big issue as the originals have huge amounts of noise with limited audio range and various distortions. As to the superior quality of 48kHz, lots of music is now limited to 15kHz because of MP3s and the quality of on air broadcasts. Only a very small minority of people can hear anything up to 20kHz and my friend who could hear the "silent" alarms in stores, now has hearing aids. In the past most people didn't notice the 15kHz flyback whistle generated by the old TVs. I could, but just tuned it out. In either case at my age, I am just happy that my new hearing aids have improved music and gotten rid of the tremolo my old aids had on sustained piano notes. The shape of wave forms is highly dependent on the phase shift vs frequency and that factor is highly debated. In either case speakers produce huge phase shifts, except for a few phase coherent ones like Ohm Walsh drivers.

clement5 wrote on 2/11/2022, 5:26 PM

Since Magix has not yet come up with a solution, I burned my Blu-Ray using Cyberlink Powerdirector. It doesn't have as many options, but it burned an OK 23.976P Blu-Ray. It is very prescriptive and limits the options, but is reliable and can burn closed captions as well as 3D compatible Blu-Rays and standard 3D MP4s which MEP cannot.