The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 135 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once



This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Esxi running macos For selur
uploaded a new dev version to google drive

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Ok, seems it deinterlace and render well now.

A little notice about UI in experimental=true When i resize window to custom size and then grab window or click to main toolbar, it always back to default size. Is this a bug?

Overall guess i will stay in normal mode on macOS yet, because experimental color pressed tabs are hard to see and because auto fullscreen on start is a little bit irritate.

[Image: U9VSnPc.gif]
Reply
Quote:Is this a bug?
Nope. This is as intended. It should also resize when moved. Smile

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Seems filters presets menu is broken. Impossible to select filter from the list:
[Image: uGCMYr5.gif]

Here are also some old ideas:

Hybrid Script viewer ideas:
- Show same friendly colorized code style as in vsViewer.
- Close Script viewer window by Command+W shortcut
- Remember Script viewer window size and position after Hybrid restart

vsViewer ideas:
- Middle click zoom-in to mouse pointer position.
- Remember custom "Fixed ratio x Zoom value" after restart
- Remember window size and position after restart
Reply
Seems like a Mac only problem.
(I can reproduce it on mac, can't on Windows and Linux)
-> looking into it

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
kvazaar pop-up error message when attempt render to mp4 container:

"Your Mp4Box version seems to be too old to handle MPEG-4 HEVC content!"
Reply
Probably an issue with the mp4box version detection,...
Will look at it once I figure out how to fix the comobox issue reported before.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Color->Basic->Autowhite error

Failed to evaluate the script:
Python exception: No module named 'autowhite'

Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 2244, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 2245, in vapoursynth.vpy_evaluateScript
File "/Volumes/temp/Hybrid Temp/tempPreviewVapoursynthFile16_57_17_240.vpy", line 10, in <module>
import autowhite
ModuleNotFoundError: No module named 'autowhite'
Reply
seems like the vsscripts folder needs to be updated to: https://github.com/Selur/VapoursynthScriptsInHybrid
will look at it once I fix the comobox-issue

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Yes, no more Autowhite error with updater scripts.

Also no any other error messages with quick run around all other VS filters.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)