+ Reply to Thread
Results 241 to 253 of 253
I don't think this would cause a problem with AviSource but did you remember to put a copy of fftw3.dll in your SysWow64 folder?
Regarding the different programs/players -- that's why I mentioned the 32 vs. 64 bit issue. I thought maybe one was different. But it's not too unusual for different programs to react differently to scripts. It's the nature of bugs. But I haven't seen problems with simple scripts like that.
directshowsource.dll being hidden explains why DirectShowSource() didn't work.
Thank you jagabo,
Yes it is there, and apparently I put it there on the day the johnmeyer script worked alright for the first time.
The funny thing is that until August 31st Windows Mediaplayer would DEFINITELY NOT play an avs-script and now it does!
Until that day MPC-HC could play scripts and now not at all.. Very strange.
Yes, I understand that things in the HIDE-folder do not participate in the proces. Should I put it back into the general plugin folder?
As mentioned before, I did not change anything. The johnmeyer script just stopped working on August 31st. That is why I thought of a virus, but MBAM found nothing.
System Restore does not function anymore but it tells me that an 'Essential update' was performed on August 30.
It is my suspicion that this may be the cause, also because from roughly the same date on, Premiere has become a lot slower..
I am trying to find out which KB number it could be. Would you know where this can be found? Do you have experience with damages done by Windows updates? Should I e.g. re-install AviSynth?
My apologies for all these questions but I am really at a loss..
That is what I thought as well, but the last one was the one dated August 19th
whereas, at the time, System Restore mentioned the 'gray' one dated August 30th:
So there must have been a later update, but it does not appear in 'View Installed Updates'. The updates for Office and other parts are even older. I'll continue my search.
- Should I move move DSS frome the HIDE to the general plugin folder?
- I'll try to reinstall AviSynth
1. Sorry jagabo, I do not quite understand: should I put it in the general plugins folder, or do you see no reason to put it there and can I leave it in the HIDE folder?
2.Please be referred to my post #232: do you have an explanation for the fact that VirtualDub/AviSynth refers to line 108 when using the johnmeyer-script?
That line reads: source1= Avisource(film).killaudio().assumefps(play_speed). converttoYV12().
About the Windows update: the August 30 update indeed exists but is one of the type that cannot be removed. So there I am stuck as well..
ALL OF A SUDDEN THE SCRIPT WORKS AGAIN!
That is great of course, but I have no idea why. May be another Windows update?
Anyway, my thanks to all for your efforts to get me on stream again.
See you at the next collaps
Meanwhile I shall be making hay while the sun shines...
On December 14th I started experimenting with VideoFred's scripts and, at first, they worked fine.
Since yesterday (Dec.17) however, they do not run any longer and I am getting this message, when trying to open a script:
Trying to load a script (which worked before) in VDub causes an Avisynth Open Failure.
Again I suspect a Windows 7 update to be the cause, but I am not sure. System Restore does not work anymore on my computer.
Would anyone have clue or better, a cure?
Would be most grateful!
Could be a language thing. What is the full disk/folder path to your plugins etc ? (looking for special characters), yes it could be Windows.
Or ... try this bootable check
Meanwhile I found that from the folder that I used before the script does work. However it does NOT from a newly made folder with an even shorter path!
I am not sure how the path to the plugin file should be determined. Possibly I am doing something wrong there. Could you advise me on that please?
Tried Windows Defender Offline on the system restore thing, but to no avail.