Access Violation & no Audio Driver

CurtisMovi escrito el 07.06.PM a las 12:56 horas

UPDATED Fixed see last post --->> right click and run in compatibility mode for windows 7, since I am using windows 10. <<---- so that and enable driver solved my problems. End UPDATE.

I installed Magix Movie Edit Pro 2013 Plus version on a new Windows 10 pc and got a pop-up saying "Access Violation" when first trying to use the "Screen Capture" feature. Problem 1. Problem 2 is no Audio Driver is in the box. See pictures. ----->>>>UPDATE, I fixed no audio partially but only for audio recording still not for screen recording, see update #1 post several comments down below so all this is still valid question END UPDATE <<<<------
1.) Access_Violation (see pic)
2.) There is no Audio Driver in the top box and can't select one either. (see pic)
3.) Magix was installed to my HDD not a default install since it wanted to install to my solid state drive. Is it an error because it is trying to use some solid state windows OS info and can't access the HDD. Or do I need to give access to magix to use that folder it is installed in on the HDD?

4.) Attempts to fix include -->> In Magix I went to top left to File - Settings - Program- and in that box to the top left tab "Playback" and played around with the audio settings but nothing changed (see pic below) when I went back to "Screen Capture". No audio driver selection also same error pop-up everytime. Attempt to fix #2, "reset Magix to default" didn't help.

5.) When I close Magix and reopen it, it presents me with a crash log and restore 'program/project' pop-up. All I did was try to use screen capture. Says don't continue in the screen cap pop-up error (see 1st pic) I close the pop-up. Eventually end up here needing help.

Comentarios

johnebaker escrito el 11.06.PM a las 22:27 horas

Are you still having problems with this issue?

If so try restarting your computer ie Windows button, Power, Restart - to ensure that all the Windows drivers are reloaded.

With problem 5, did you get a request to send the error to Magix and did you do this?

HTH

John EB

Scenestealer escrito el 12.06.AM a las 00:41 horas

Magix do not recommend placing the program on a non OS drive so it may be a cause of some of your problems.

emmrecs escrito el 12.06.AM a las 10:55 horas

@Scenestealer

Hi Peter.

Any idea why Magix do not recommend placing the program on a non OS drive? I ask because on this computer and its predecessor I have always installed all Magix programs to D:\, so keeping C:\ predominantly for the OS only. (D:\ is dedicated to program installations, so no "data" there).

Jeff

Scenestealer escrito el 12.06.PM a las 13:04 horas

Hi Jeff

I read this very recently by chance on the support2.magix.com website but can not remember in connection with what question. Sorry, do not know exactly why as they did not elaborate. Maybe it makes the program data slower to access? I would feel more comfortable with it on C: and have always done so.

Peter

emmrecs escrito el 12.06.PM a las 13:15 horas

Hi Peter.

Thanks for this.

Interesting that you feel more comfortable with it on C:. My thinking has always been to keep OS, programs and data all on different drives, so that reading/writing to OS cannot interfere with reading/writing to Programs or data.

Certainly, I've never felt there is any "negative performance hit" with the great majority of my programs on D:\, including those from Magix. (Some programs, of course, offer no option to not install on C:\ 😡.)

Jeff

CurtisMovi escrito el 16.06.PM a las 22:13 horas

UPDATE #1

I still need help for the access violation and it is not letting me select an Audio Driver for Screen Recording.

1.) I can now since last post go into "Record Audio" by pressing that red button to get to the screen to select between either Record Audio or Record Screen and I can now use Record Audio because I enabled the driver and it shows up but no driver is showing up in the Record Screen option... the next paragraph explains what I did to get just the Audio Recording to work now but still not Screen Recording.

2.) So I discover that the 'audio sound card' (realtech something) was not "Enabled" so I enabled it in a pop up window with several tabs to go through in Windows 10. This made it so when selecting "Record Audio" the (realtech) was now the only "Audio Driver" option being displayed, however when selecting "Record Screen" I got the same popup "Access Violation" and could not select "Audio Driver" which is odd because there are only 2 record options with magix movie edit pro 2013 plus, and before I enabled the sound card driver realtech whatever I could also not select Audio Driver for audio recording so why is it not showing up in screen recording?

Those are the questions
1.) Why no driver in screen cap - since it is now available in audio cap?
2.) Why access violation

Really need some expert help here please. I searched web for why access violations occur and have no clue what to do now. I eventually found and solved the driver issue took a long time to find it but I did and it worked/fixed issue I thought at first but for Audio only and now audio driver still doesn't show up or is even selectable in Screen Recording. Argh....!!! This is the 2nd copy I bought of Magix Movie Edit Pro 2013 since the first one wasn't Plus I had to buy it again to get the Screen Recording capability. Now I have access violation and no driver??? Thank you, please

CurtisMovi escrito el 17.06.AM a las 00:04 horas

Solved!

I fixed it! I right clicked on the desktop icon for Magix (in windows 10) and selected run compatibility test/check mode and it came up with windows 7 compatibility. So I ran the Magix program and the Screen Capture was now working with the Audio Driver displayed as well. Since I prior to this discovery had enabled the sound card / audio driver.

I wondered why the Magix boxes had the bottom clipped some. Still clipping them though. Any idea how to fix that? I did also uninstall the HDD install of Magix and put Magix on my SSD but that still gave the same access violation using Screen Capture. So right click compatibility solved it HDD or SSD had no impact most likely since same Access Violation numbers and letters of code in the error message. Always the thing with me and computers is just keep clicking on stuff till you find the answer.

wongck escrito el 17.06.AM a las 06:00 horas

You have MRP pro 2013, which is rather old, so running in compatibility mode is a must especially if it uses the older interface to the API of drivers and DLL.