1 Reply by Leondre

(8 replies, posted in Using SVP)

Alright not sure if it is the same issue as you are having but I managed to get madvr to work on my end without any of the issues in my prev post. I ran the uninstall .bat, copied the madvr folder elsewhere eg C:\madvr, and then ran the install .bat and the madvr icon once again showed up during playback. Simply uninstalling and reinstalling from the svp dir was not enough for whatever reason. After that I uninstalled it again from C:\madvr and I was able to go back to the svp directory and install madvr again and have it work from the default location.

Go to forum: Using SVP

2 Reply by Leondre

(8 replies, posted in Using SVP)

This is also happening for me. Not sure when it started, likely in the last few weeks, but I no longer have a tray icon for madvr and if I bring up the madvr properties window via the ffdshow tray icon and click either 'edit settings' or 'show tray icon' simply nothing happens. And the more videos I play the more madHcCtrl.exe processes are spawned.

I have tried manually uninstalling and reinstalling madvr with the latest version, same issue persists. Not seeing anything related to this on the madvr forum thread either.

Go to forum: Using SVP

3 Reply by Leondre

(10 replies, posted in Using SVP)

I wanted to chime in on this again. I just encountered the "Invalid script!" error once more. However this time it happened immediately after I installed Webroot, which I had previously before doing a clean install of Windows. I removed Webroot and SVP started working fine again.

Just an FYI for anyone who may be in a similar situation.

Go to forum: Using SVP

4 Reply by Leondre

(10 replies, posted in Using SVP)

I ended up just reinstalling windows and all my issues are solved. Not an elegant solution, but whatever.

Thanks

Go to forum: Using SVP

5 Reply by Leondre

(10 replies, posted in Using SVP)

Alright I uninstalled SVP, and then uninstalled the remaining 64bit avisynth. I then reinstalled SVP.

Initially I was able to play videos and svp worked, but after closing svp and reopening it and playing another video I now get.

I posted another problem report. Is there anything you can tell me from those logs?

https://dl.dropboxusercontent.com/u/10835356/ShareX/mpc-hc_2016-09-20_16-33-33.png

Thanks for the assistance so far.

Go to forum: Using SVP

6 Reply by Leondre

(10 replies, posted in Using SVP)

Avisynth is already unchecked when I open a video with svp-manager closed. I don't get the error unless svp-manager is actually running.

I've gone ahead and sent the problem report to you.

edit: Here are the easy reproducible steps of how I encounter this. I have found it doesn't even need a reboot, simply closing the manager is enough to do it.

1. Install SVP 4
2. Open a video, svp works fine.
3. Close SVP-Manager, and then reopen it.
4. Open a video, error is thrown.
5. Close SVP-Manager and reinstall the '[DS_32] Core for DirectShow 32-bit'
6. Open a video, svp works fine.

Go to forum: Using SVP

7 Topic by Leondre

(10 replies, posted in Using SVP)

https://dl.dropboxusercontent.com/u/10835356/ShareX/mpc-hc_2016-09-18_15-55-41.png

I keep encountering the above issue when trying to play media after a reboot. SVP 4 works fine after a reinstall of the application, but the moment I reboot my machine it stops working and throws that error.

I saw a previous post from a while back that said to uncheck avisynth in ffdshow options. That does make the error go away, but svp does not actually do anything after that. And that box automatically checks itself again whenever I open a new file. I have also noticed that the file it is looking for in that path does not even exist.

How do I fix this? I'm using mpc-hc and Windows 10.

Go to forum: Using SVP