Like I wrote before I only looked at the preview when AvisynthView + FilterView was used.
About the thre errors added screenshots: Nothing I can do about it, these are bugs in the wine version you use, seeing that they got 'fixme' in their name I guess the wine dev are aware of them. -> might be fixed in a later version of wine.
Quote:!) loaded mp4, set x264, no filters, started encode = NOTHING
Create a debug level 9 of that and I can look into it.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Why do you create seven debug outputs when I ask for one regarding one of the problems?
When you create multiple debug output files at least name them somehow so I don't have to read the whole damn thing so know what it is about.
HybridDebugOutput-1 crashes (during the encoding) with:
FFmpeg : Error while processing the decoded data for stream #0:0
Seems like your mplayer is compiled with broken VDPAU support.
HybridDebugOutput-3 reports some wine problems (when avsViewer is called):
Avisynth preview error: 0009:fixme:msvcrt:__clean_type_info_names_internal (0xae9b38) stub000b:fixme:winediagtart_process Please mention your exact version when filing bug reports on winehq.org.
-> this is a bug in wine, nothing I can do about it
HybridDebugOutput-4 shows you stopping an encoding:
/usr/bin/wine "/usr/bin/hybrid-bin/avs2yuv.exe" "/tmp/encodingTempSynthSkript_11_02_51_7510.avs" -csp I420 -o - | "/usr/bin/x264" --preset slow --crf 18.00 --profile high --level 4.1 --psy-rd 1.00:0.15 --vbv-maxrate 62500 --vbv-bufsize 78125 --sar 1:1 --deblock -1:-1 --non-deterministic --range tv --colormatrix bt470bg --demuxer y4m --input-range tv --fps 24000/1001 --output "/tmp/11_02_51_7510_03.264" -
So avs2yuv doesn't seem to cause problems for your wine environment.
HybridDebugOutput-5 shows you stopping an encoding:
/usr/bin/wine "/usr/bin/hybrid-bin/avs2yuv.exe" "/tmp/encodingTempSynthSkript_11_07_18_1010.avs" -csp I420 -o - | "/usr/bin/x264" --preset slow --crf 18.00 --profile high --level 4.1 --psy-rd 1.00:0.15 --vbv-maxrate 62500 --vbv-bufsize 78125 --sar 1:1 --deblock -1:-1 --non-deterministic --range tv --colormatrix bt709 --demuxer y4m --input-range tv --fps 24000/1001 --output "/tmp/11_07_18_1010_02.264" -
So avs2yuv doesn't seem to cause problems for your wine environment.
HybridDebugOutput-6 shows you stopping an encoding:
/usr/bin/wine "/usr/bin/hybrid-bin/avs2yuv.exe" "/tmp/encodingTempSynthSkript_11_11_23_7210.avs" -csp I420 -o - | "/usr/bin/x264" --preset slow --crf 18.00 --profile high --level 4.1 --psy-rd 1.00:0.15 --vbv-maxrate 62500 --vbv-bufsize 78125 --sar 1:1 --deblock -1:-1 --non-deterministic --range tv --colormatrix bt470bg --demuxer y4m --input-range tv --fps 24000/1001 --output "/tmp/11_11_23_7210_03.264" -
So avs2yuv doesn't seem to cause problems for your wine environment.
HybridDebugOutput-7 crashes (during the encoding) with:
FFmpeg : Error while processing the decoded data for stream #0:0
Not sure what you want me to say to that or notice there.
If you want to know how the mplayer/mencoder versions are compiled that are part of djcjs Hybrid repository, you need to ask him.
I see that you have problems with the Avisynth preview, but like I wrote before these seem to be all rooted in wine, which I can do nothing about.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Filter preview works when a file is inputed directly into Hybrid but does not when the input is via avs.
This is with the exception of VOB's because Hybrid cannot process them.
Blaming wine is a cop out.
I have already shown that previews can be called through wine without errors just not by Hybrid in the instance of avs input.
Problem is unless I can reproduce the issue or at least see why it isn't working I can't do much about it.
1. For vob input Avisynth isn't used at all by default, so anything vob related is due to the mplayer version you use.
2. regarding avsViewer, no clue why it's not working for you aside from the errors your wine throws.
-> If Vapoursynth isn't a solution for you and I can't figure out the issue your best choice is probably to not use Hybrid.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
All dvd's have VOB files and that Hybrid cannot handle them directly is a big deficiency.
Again, avsViewer does work when I call it outside of Hybrid and I have shown that.
Why you keep mentioning vapoursynth I do not know. I DO NOT use it with Hybrid and there are no linux vapoursynth filters
for Hybrid that I know of ??
I have gone back to the original Hybrid_180408_64bit-binary_qt521,
Attach debug of loading a mp4 direct into Hybrid. Filter preview is okay just irritating errors.
I then load the same mp4 but via avs. Preview window launches but nothing to see except notice "Preparing environment for /tmp/temp/PreviewAvisynthFile07_29_49_303.avs".
DebugOutput only shows:
a. the wine errors
b. the "I don't know what "Source" means", since FilterView is enabled
-> no surprise there and we are back where we started.
Why I mention Vapoursynth is easy:
a. it runs nativly on Linux (no wine)
b. it offers better performance on multi core systems
Quote:I have gone back to the original Hybrid_180408_64bit-binary_qt521
If that version works for you 'better' good for you.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
You have said the selur.avs is faulty but I have shown it works.
1) Load selur.avs, set x264, disable deinterlace & Tweak filter, proceed to encode = okay.
2) Stop encode, click filter Preview, minor errors but preview launches and am able to step through, no issue.
3) Close preview, activate tweak filter, window launches but no preview just error message "Preparing environment etc".
Debug attached