Jonny007-MKD/multicutmkv

multicutmkv on bullseye

Opened this issue · 6 comments

Hello I tried to install on raspi-bullseye.
Unfortunately I get some error with avxsynth.

Will you install multicutmkv on bullseye or do you know of another headless OTR Cut Script?

Thank you very much

Hi,
I'm still running on buster 🤔
Did you pull in the PRs of avxsynth fixing some compiler issues?

I'm going to try to update to bullseye after creating a backup of the sd card, but I won't have time for that in the next weeks.

Yes I merged p120, p121 and p122.

tried 64 as well as 32 bit...

Thank you!

I made the upgrade and am now trying to compile avxsynth. I guess you are having these "conversion from int to unsigned int" errors, too? That's due to the more recent gcc being more strict about the quality of code that it accepts. I can create another PR for avxsynth that fixes these issues (at list quick and dirty ;))

I hope, this fixes your issues:

avxsynth/avxsynth#126

Thank you, took me a while sincve I was on holiday.
Unfortunately I did:
git fetch origin pull/120/head:p120
git fetch origin pull/121/head:p121
git fetch origin pull/122/head:p122
git fetch origin pull/126/head:p126
git merge p120
git merge p121
git merge p122
git merge p126

and get this error:
In file included from core/src/core/parser/expression.cpp:40:
core/src/core/parser/expression.cpp: In function ‘const char* const avxsynth::StringSystemError(unsigned int)’:
../include/windowsPorts/WinNTLinux.h:13:64: error: narrowing conversion of ‘-1073741801’ from ‘avxsynth::LONG’ {aka ‘int’} to ‘unsigned int’ [-Wnarrowing]
13 | #define STATUS_NO_MEMORY ((NTSTATUS)0xC0000017L) // winnt
| ^
core/src/core/parser/expression.cpp:94:8: note: in expansion of macro ‘STATUS_NO_MEMORY’
94 | case STATUS_NO_MEMORY: // 0xc0000017
| ^~~~~~~~~~~~~~~~

Did it work for you?
Thank you

yes. interesting.
Please add the (unsigned) after every case as in line 92 of avxsynth/core/src/core/parser/expression.cpp.

Alternatively you could try avisynth+ which shall be a better alternative. I haven't tried that, yet, though.