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
There are few tiny visual bugs in UI. Maybe you have time to fix them?
When use custom UI size 14px or larger this text line became cropped. This is probably the only place in UI that have visual bug like this. So maybe increase that box a little bit?
[Image: rjT6ez2.jpg]

In "disableicons" mode buttons size in Filter Queue looks random.
Maybe instead of Move Up/Move Down use names Up/Down (same names as used in all other similar places). This will allow to save space and perfectly align button sizes.
[Image: ENY9Ftg.jpg]
Reply
Will look at it after work.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
It is known limitation in Hybrid with file or folder path names contain non latin or some special characters like Ö ß Ы Ї Ω and many others. Files with special characters stuck in Temp folder with different types of errors that seems depends of output codec and container used.
Aborting '2021-09-02@11_56_48_6410_06_muxing' due to: Error: The XML tag file '/Volumes/temp/Hybrid Temp/VTS_01_2-VC01 telecine ' could not be read.

It happens in "Passtrough" mode as well:
Aborting '2021-08-12@18_12_37_5610_01_audio' due to: ERROR: /Volumes/temp/Hybrid Temp/iId_5_aid_0_lang_en_2021-08-12@18_12_37_5610_01.ac3 was not created!

In situations when a lot of content use names duplicated on different languages this this limitation may be a serious problem. A lot of time may be wasted for renaming and managing of original file names.
Do you think it is possible somehow fix this problem (i can send you a debug if it helps)? Or is this some specific limitation of some internal components and we just need accept it as is and live with it?
Reply
Quote:It is known limitation in Hybrid with file or folder path names contain non latin or some special characters like Ö ß Ы Ї Ω and many others.
Works fine here on Windows and Linux.
This is not a general Hybrid problem,...
-> yes, a debug output of one of the occurance would be needed for me to have me look at it.
My guess is that it's not a problem of the characters but of whitespaces.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Nice to hear that it is macOS only related problem. PM'ed you a debugs.
Reply
will look at it after work
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Send you a link to a dev verison for testing which hopefully fixes the issue of mkvtoolnixs and Hybrids tokenizing of calls interfering.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Don't works yet.
Unmuxed files remains in Temp folder. But also now it outputs file without extension and without special character in name. PM'ed you new debug.

This time i also add special character to the folder path (for additional complexity)

Redesigned layout for ProRes settings looks great! Big Grin
Reply
Quote:Unmuxed files remains in Temp folder. But also now it outputs file without extension and without special character in name. PM'ed you new debug.
Hybrid calls:
"/Applications/Hybrid.app/Contents/MacOS/mkvmerge" --ui-language en_US -o "/Volumes/media/-DVD/-MKV EXTRACTED/VTS_01_2-VC01 telecine Ω_Title_1-hybrid.mkv" --global-tags "/Volumes/temp/Hybrid Temp/_2021-09-02@17_52_46_2210__03.xml" -d 0 --default-track 0:yes --default-duration "0:29.97i" --aspect-ratio-factor 0:0.889 --no-chapters --compression -1:none --forced-track 0:yes --no-audio --no-subtitles "/Volumes/temp/Hybrid Temp/2021-09-02@17_52_46_2210_02.m2v" --default-track 0:yes --sync 0:-120 --forced-track 0:no -a 0 --compression -1:none --no-video --no-subtitles --no-chapters "/Volumes/temp/Hybrid Temp/iId_1_aid_128_DELAY_-120ms_2021-09-02@17_52_46_2210_01.ac3"
and the output I see in the debug output is:
mkvmerge v53.0.0 ('Fool's Gold') 64-bit
'/Volumes/temp/Hybrid Temp/2021-09-02@17_52_46_2210_02.m2v': Using the demultiplexer for the format 'MPEG-1/2 video elementary stream'.
'/Volumes/temp/Hybrid Temp/iId_1_aid_128_DELAY_-120ms_2021-09-02@17_52_46_2210_01.ac3': Using the demultiplexer for the format 'AC-3'.
'/Volumes/temp/Hybrid Temp/2021-09-02@17_52_46_2210_02.m2v' track 0: Using the output module for the format 'MPEG-1/2 video'.
'/Volumes/temp/Hybrid Temp/iId_1_aid_128_DELAY_-120ms_2021-09-02@17_52_46_2210_01.ac3' track 0: Using the output module for the format 'AC-3'.
The file '/Volumes/media/-DVD/-MKV EXTRACTED/VTS_01_2-VC01 telecine ' has been opened for writing.
Warning: Found at least one B frame without second reference in a non closed GOP.
after that the next message is that the muxing process stopped.
What happen is you call that call inside a terminal, does mkvtoolnix output some additional info?
you can also try:
"/Applications/Hybrid.app/Contents/MacOS/mkvmerge" --ui-language en_US -v -o "/Volumes/media/-DVD/-MKV EXTRACTED/VTS_01_2-VC01 telecine Ω_Title_1-hybrid.mkv" --global-tags "/Volumes/temp/Hybrid Temp/_2021-09-02@17_52_46_2210__03.xml" -d 0 --default-track 0:yes --default-duration "0:29.97i" --aspect-ratio-factor 0:0.889 --no-chapters --compression -1:none --forced-track 0:yes --no-audio --no-subtitles "/Volumes/temp/Hybrid Temp/2021-09-02@17_52_46_2210_02.m2v" --default-track 0:yes --sync 0:-120 --forced-track 0:no -a 0 --compression -1:none --no-video --no-subtitles --no-chapters "/Volumes/temp/Hybrid Temp/iId_1_aid_128_DELAY_-120ms_2021-09-02@17_52_46_2210_01.ac3"
which should output more verbose output.
Also try whether it helps to replace mkvtoolnix with the latest 61 version which has some fixes around character handling.



Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
1. I can't use newer than 53 version of MKVtoolnix because i am on Mojave.
2. There is no problem when i mux the same file with special character with MKVtoolnix GUI 53 app.
2. When i enter your code to terminal i got this:

mkvmerge v53.0.0 ('Fool's Gold') 64-bit
Error: The XML tag file '/Volumes/temp/Hybrid Temp/_2021-09-02@17_52_46_2210__03.xml' could not be read.
Reply


Forum Jump:


Users browsing this thread: 9 Guest(s)