I have i386 debian 11 on my arm tablet now, but road to it was somewhat bumpy. debootstrap as provided by termux does not like --foreign option, so I tried modification of scrip commands found at https://github.com/sp4rkie/debian-on-termux/blob/master/debian_on_termux_10.... (I have Android 10 tablet) $ debootstrap --variant=minbase --exclude=systemd --arch=i386 bullseye deb_11 but you need to set main repo here or create debootstrap/mirror by hand REPO=http://ftp.debian.org/debian/ unset LD_PRELOAD $ proot -0 -b /dev -b /sys -b /proc -b /system -b /apex --link2symlink -r deb_11/ -q qemu-i386 /bin/bash --login (for some reason my system need /system and /apex added to proot bind directories for qemu to function) this worked but ssl / ca-certificates were not installed, and coreutils for some reason needed re-install by dpkg -i /var/cache/apt/archive/pkg.deb also debootstrap/debootstap script had termux pathes in it, so I edited them back for normal Linux/debian pathes after installing /etc/resolv.conf network/apt worked but building man page index was a bit slow. Installing libgtk2.0-dev resulted in 1.011 Gb directory simple openssl benchmark: root@localhost:~# openssl speed sha256 Doing sha256 for 3s on 16 size blocks: 275533 sha256's in 3.00s Doing sha256 for 3s on 64 size blocks: 175841 sha256's in 3.00s Doing sha256 for 3s on 256 size blocks: 65455 sha256's in 3.00s Doing sha256 for 3s on 1024 size blocks: 20649 sha256's in 3.00s Doing sha256 for 3s on 8192 size blocks: 2779 sha256's in 3.00s Doing sha256 for 3s on 16384 size blocks: 1389 sha256's in 2.98s OpenSSL 1.1.1k 25 Mar 2021 built on: Tue Aug 24 08:28:12 2021 UTC options:bn(64,32) rc4(8x,mmx) des(long) aes(partial) blowfish(ptr) compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-eBODPh/openssl-1.1.1k=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DRMD160_ASM -DAESNI_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes sha256 1469.51k 3751.27k 5585.49k 7048.19k 7588.52k 7636.70k === $ termux-info Application version: unsupported Packages CPU architecture: arm Subscribed repositories: # sources.list deb https://termux.librehat.com/apt/termux-main/ stable main # x11-repo (sources.list.d/x11.list) deb https://packages.termux.org/apt/termux-x11 x11 main # science-repo (sources.list.d/science.list) deb https://packages.termux.org/apt/termux-science science stable # game-repo (sources.list.d/game.list) deb https://packages.termux.org/apt/termux-games games stable Updatable packages: mc/stable 4.8.27-2 arm [upgradable from: 4.8.25-3] Android version: 10 Kernel build information: Linux localhost 4.14.141+ #1 SMP PREEMPT Fri Dec 3 19:05:26 CST 2021 armv8l Android Device manufacturer: HUAWEI Device model: KOB2-L09 $ $ lscpu Architecture: armv8l Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: ARM Model name: Cortex-A53 Model: 4 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 Stepping: r0p4 CPU max MHz: 2001.0000 CPU min MHz: 400.0000 BogoMIPS: 26.00 Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfp v4 idiva idivt lpae evtstrm aes pmull sha1 sha2 crc32 $
Bumpy is an understatement! On Sun, Jan 9, 2022 at 11:07 PM Andrew Randrianasulu via Cin < [email protected]> wrote:
I have i386 debian 11 on my arm tablet now, but road to it was somewhat bumpy.
debootstrap as provided by termux does not like --foreign option, so I tried modification of scrip commands found at
https://github.com/sp4rkie/debian-on-termux/blob/master/debian_on_termux_10.... (I have Android 10 tablet)
$ debootstrap --variant=minbase --exclude=systemd --arch=i386 bullseye deb_11
but you need to set main repo here or create debootstrap/mirror by hand REPO=http://ftp.debian.org/debian/
unset LD_PRELOAD
$ proot -0 -b /dev -b /sys -b /proc -b /system -b /apex --link2symlink -r deb_11/ -q qemu-i386 /bin/bash --login
(for some reason my system need /system and /apex added to proot bind directories for qemu to function)
this worked but ssl / ca-certificates were not installed, and coreutils for some reason needed re-install by dpkg -i /var/cache/apt/archive/pkg.deb
also debootstrap/debootstap script had termux pathes in it, so I edited them back for normal Linux/debian pathes
after installing /etc/resolv.conf network/apt worked but building man page index was a bit slow.
Installing libgtk2.0-dev resulted in 1.011 Gb directory
simple openssl benchmark:
root@localhost:~# openssl speed sha256 Doing sha256 for 3s on 16 size blocks: 275533 sha256's in 3.00s Doing sha256 for 3s on 64 size blocks: 175841 sha256's in 3.00s Doing sha256 for 3s on 256 size blocks: 65455 sha256's in 3.00s Doing sha256 for 3s on 1024 size blocks: 20649 sha256's in 3.00s Doing sha256 for 3s on 8192 size blocks: 2779 sha256's in 3.00s Doing sha256 for 3s on 16384 size blocks: 1389 sha256's in 2.98s OpenSSL 1.1.1k 25 Mar 2021 built on: Tue Aug 24 08:28:12 2021 UTC options:bn(64,32) rc4(8x,mmx) des(long) aes(partial) blowfish(ptr) compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-eBODPh/openssl-1.1.1k=. -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DRMD160_ASM -DAESNI_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes sha256 1469.51k 3751.27k 5585.49k 7048.19k 7588.52k 7636.70k
=== $ termux-info Application version: unsupported Packages CPU architecture: arm Subscribed repositories: # sources.list deb https://termux.librehat.com/apt/termux-main/ stable main # x11-repo (sources.list.d/x11.list) deb https://packages.termux.org/apt/termux-x11 x11 main # science-repo (sources.list.d/science.list) deb https://packages.termux.org/apt/termux-science science stable # game-repo (sources.list.d/game.list) deb https://packages.termux.org/apt/termux-games games stable Updatable packages: mc/stable 4.8.27-2 arm [upgradable from: 4.8.25-3] Android version: 10 Kernel build information: Linux localhost 4.14.141+ #1 SMP PREEMPT Fri Dec 3 19:05:26 CST 2021 armv8l Android Device manufacturer: HUAWEI Device model: KOB2-L09 $
$ lscpu Architecture: armv8l Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: ARM Model name: Cortex-A53 Model: 4 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 Stepping: r0p4 CPU max MHz: 2001.0000 CPU min MHz: 400.0000 BogoMIPS: 26.00 Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfp v4 idiva idivt lpae evtstrm aes pmull sha1 sha2 crc32 $ -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi! In this page of the Cinelerra-GG manual: Complete Options File Example https://cinelerra-gg.org/download/CinelerraGG_Manual/Complete_Options_File_E... it reads: acc instead of aac in two places in that page and I think in some other pages in the manual. However, there is, upon building Cinelerra: ffmpeg/audio/acc256k.pro which is wrong filename. Should be acc256k.pro of course. I was only able to get mjpeg processing to work. No h264, no h265. When rendering with FFmpeg I get only something like empty mp4 in menus. So I doubt there may be other formats/codecs/other errors there too. I see these are all relatively new changes: [Cin] Formats and Codecs in CinGG https://lists.cinelerra-gg.org/pipermail/cin/2021-November/004085.html And in the Git repo the log says: commit b0fd1700736a56a8c206bff1e699a9a130faafbf Author: Good Guy <[email protected]> Date: Mon Nov 22 20:09:14 2021 -0700 ffmpeg patches for TERMUX from Andrew + mpeg formats but I haven't studied the diffs (yet?). However, it's there that I would search to try and solve this. So much for now. Regards to the whole team! (I couldn't use any other video editor but Cinelerra. Libre is always best. But I work so slow myself...) -- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr my PGP-key: https://www.croatiafidelis.hr/FCF13245ED247DCE443855B7EA9884884FBAF0AE.asc
I apologize for forgetting to remove the "In-Reply-To: " header when using any unrelated mail in my cinelerra folder. Really sorry! On 220112-23:28+0100, Miroslav Rovis wrote:
Hi!
In this page of the Cinelerra-GG manual: Complete Options File Example https://cinelerra-gg.org/download/CinelerraGG_Manual/Complete_Options_File_E... it reads: acc instead of aac in two places in that page and I think in some other pages in the manual.
-- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr my PGP-key: https://www.croatiafidelis.hr/FCF13245ED247DCE443855B7EA9884884FBAF0AE.asc
On Thursday, January 13, 2022, Miroslav Rovis via Cin < [email protected]> wrote:
Hi!
In this page of the Cinelerra-GG manual: Complete Options File Example https://cinelerra-gg.org/download/CinelerraGG_Manual/ Complete_Options_File_Examp.html it reads: acc instead of aac in two places in that page and I think in some other pages in the manual.
However, there is, upon building Cinelerra: ffmpeg/audio/acc256k.pro which is wrong filename. Should be acc256k.pro of course.
I was only able to get mjpeg processing to work. No h264, no h265. When rendering with FFmpeg I get only something like empty mp4 in menus. So I doubt there may be other formats/codecs/other errors there too.
can you make screenshot/screencast of empty menu? I used user build with whole directory of cin binaries and other files (including format profiles) located in 'bin' subdir inside CinGG source tree. it was working for me... How exactly you build your cinelerraGG, you hopefully not forgot make install?
I see these are all relatively new changes: [Cin] Formats and Codecs in CinGG https://lists.cinelerra-gg.org/pipermail/cin/2021-November/004085.html
And in the Git repo the log says: commit b0fd1700736a56a8c206bff1e699a9a130faafbf Author: Good Guy <[email protected]> Date: Mon Nov 22 20:09:14 2021 -0700
ffmpeg patches for TERMUX from Andrew + mpeg formats
but I haven't studied the diffs (yet?). However, it's there that I would search to try and solve this.
So much for now.
Regards to the whole team!
(I couldn't use any other video editor but Cinelerra. Libre is always best. But I work so slow myself...)
-- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr my PGP-key: https://www.croatiafidelis.hr/FCF13245ED247DCE443855B7EA9884884FBAF0AE.asc
@Miroslav Rovis Thanks for pointing out the error; I've changed the manual, but if anyone notices other sections with the wrong "acc", please let me know. The git introduction to the "Overview on Formats and Codecs" section can be found here: https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=commit;h=... Subsequently, there were other corrections. @Phyllis You also need to change the preset name "acc256k.pro" to "aac256k.pro" in the source code. I attach the changes in the manual.
GIT checkin of the manual changes (to include Terje's DVD/Blu-ray fixes) has been done. GIT source code checkin to add the correctly named aac256k.pro and delete the incorrectly named acc256k.pro is complete. Thank you Miroslav as it has been wrong since at least July 2016 and thanks Andrea for making sure I fix the source code too or I would have failed to do so. @Miroslav Rovis
Thanks for pointing out the error; I've changed the manual, but if anyone notices other sections with the wrong "acc", please let me know. The git introduction to the "Overview on Formats and Codecs" section can be found here:
https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=commit;h=... Subsequently, there were other corrections. @Phyllis You also need to change the preset name "acc256k.pro" to "aac256k.pro" in the source code. I attach the changes in the manual. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On 220113-08:02+0300, Andrew Randrianasulu wrote:
On Thursday, January 13, 2022, Miroslav Rovis via Cin < [email protected]> wrote:
Hi!
In this page of the Cinelerra-GG manual: Complete Options File Example https://cinelerra-gg.org/download/CinelerraGG_Manual/ Complete_Options_File_Examp.html it reads: acc instead of aac in two places in that page and I think in some other pages in the manual.
However, there is, upon building Cinelerra: ffmpeg/audio/acc256k.pro which is wrong filename. Should be acc256k.pro of course.
I was only able to get mjpeg processing to work. No h264, no h265. When rendering with FFmpeg I get only something like empty mp4 in menus. So I doubt there may be other formats/codecs/other errors there too.
So, while the codec name and its filename is wrong (and I'm glad Andrea paz found my notice useful), I now think that this screencasting/shotting probably won't be necessary:
can you make screenshot/screencast of empty menu? I used user build with whole directory of cin binaries and other files (including format profiles) located in 'bin' subdir inside CinGG source tree. it was working for me... because I think that I: How exactly you build your cinelerraGG, you hopefully not forgot make install? exactly that: I think I forgot to execute "make install". (I don't see the log of it, and I do have the log of sole make run, and I always do log STDOUT and STDERR when I build things. I'll be back to report if that isn't so, but it probably is so: I think I forgot to run "make install".)
So thanks, Andrew, for (likely) a very quick diagnosis of my real issue. Regards! -- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr my PGP-key: https://www.croatiafidelis.hr/FCF13245ED247DCE443855B7EA9884884FBAF0AE.asc
On Thu, 2022-01-13 at 12:36 +0100, Miroslav Rovis via Cin wrote:
On 220113-08:02+0300, Andrew Randrianasulu wrote:
On Thursday, January 13, 2022, Miroslav Rovis via Cin < [email protected]> wrote:
Hi!
In this page of the Cinelerra-GG manual: Complete Options File Example https://cinelerra-gg.org/download/CinelerraGG_Manual/ Complete_Options_File_Examp.html it reads: acc instead of aac in two places in that page and I think in some other pages in the manual.
However, there is, upon building Cinelerra: ffmpeg/audio/acc256k.pro which is wrong filename. Should be acc256k.pro of course.
I was only able to get mjpeg processing to work. No h264, no h265. When rendering with FFmpeg I get only something like empty mp4 in menus. So I doubt there may be other formats/codecs/other errors there too.
So, while the codec name and its filename is wrong (and I'm glad Andrea paz found my notice useful), I now think that this screencasting/shotting probably won't be necessary:
can you make screenshot/screencast of empty menu? I used user build with whole directory of cin binaries and other files (including format profiles) located in 'bin' subdir inside CinGG source tree. it was working for me... because I think that I: How exactly you build your cinelerraGG, you hopefully not forgot make install? exactly that: I think I forgot to execute "make install". (I don't see the log of it, and I do have the log of sole make run, and I always do log STDOUT and STDERR when I build things. I'll be back to report if that isn't so, but it probably is so: I think I forgot to run "make install".)
If you do ./bld.sh in the cinelerra5 directory it will do it all for you. After that there is an executable "cin" in the bin directory. MatN
Hi Andrew, What OS did you use to compile it on the Orange Pi Lite? I tried earlier this year to compile it on a Cortex-A7 based CPU (Allwinner A20 2 core), the Orange PI lite has the 4 core version of that. I used Debian, and it failed quickly. MatN
пн, 26 сент. 2022 г., 15:05 mat <[email protected]>:
Hi Andrew,
What OS did you use to compile it on the Orange Pi Lite?
this is not my personal experience, I just tried to condense talk we had at linux.org.ru forum. I think last OS mentioned there was "Arch Linux ARM" and simple addition of armv7l case in guicast/Makefile along with previous arm8l fixed predictable build failure .... fix already in cingg git thread https://www.linux.org.ru/forum/linux-hardware/16959253?cid=16983577
I tried earlier this year to compile it on a Cortex-A7 based CPU (Allwinner A20 2 core), the Orange PI lite has the 4 core version of that. I used Debian, and it failed quickly.
you can try again with this reported config ./configure \ --prefix=/usr \ --disable-libaom \ --disable-libwebp \ --disable-dav1d \ --disable-static-build \ --without-nv \ --without-cuda \ --with-exec-name=cinelerra-gg and/or disable thirdparty build completely for speeding up test compile in guicast and cinelerra dirs
MatN
I got it to build. Configure options: --with-single-user --with-booby --disable-dav1d (because av1 has code written in x86 assembly). --without-vaapi --without-vdpau --without-nv --without-wintv --without-x10tv --disable-libaom (there seem to be "always inline" functions that causes problems with arm_neon.h and other files. --disable-libwebp CinGG loads fine, menus work. Audio can be loaded and played, but no sound output. This is not a CinGG error, something with the machine low-level config. Even speaker-test does not work. Alsa config seems OK, output does not go to HDMI monitor. Video (tried short 720p video) can be loaded, but as soon as you do anything CinGG is terminated with a "bus error". don't know what that is. Not CinGG I think. Hardware is 2 core Cortex A7 at 1 GHz, 1G ram, 8G flash (for OS), 500G hdd (data), swapfile 10G on hdd (and being used quite a lot). MatN On Mon, 26 Sep 2022 16:21:39 +0300 Andrew Randrianasulu <[email protected]> wrote:
пн, 26 сент. 2022 г., 15:05 mat <[email protected]>:
Hi Andrew,
What OS did you use to compile it on the Orange Pi Lite?
this is not my personal experience, I just tried to condense talk we had at linux.org.ru forum.
I think last OS mentioned there was "Arch Linux ARM" and simple addition of armv7l case in guicast/Makefile along with previous arm8l fixed predictable build failure .... fix already in cingg git
thread https://www.linux.org.ru/forum/linux-hardware/16959253?cid=16983577
I tried earlier this year to compile it on a Cortex-A7 based CPU (Allwinner A20 2 core), the Orange PI lite has the 4 core version of that. I used Debian, and it failed quickly.
you can try again with this reported config
./configure \ --prefix=/usr \ --disable-libaom \ --disable-libwebp \ --disable-dav1d \ --disable-static-build \ --without-nv \ --without-cuda \ --with-exec-name=cinelerra-gg
and/or disable thirdparty build completely
for speeding up test compile in guicast and
cinelerra dirs
MatN
вт, 27 сент. 2022 г., 22:37 <[email protected]>:
I got it to build.
Configure options: --with-single-user --with-booby --disable-dav1d (because av1 has code written in x86 assembly). --without-vaapi --without-vdpau --without-nv --without-wintv --without-x10tv --disable-libaom (there seem to be "always inline" functions that causes problems with arm_neon.h and other files. --disable-libwebp
CinGG loads fine, menus work. Audio can be loaded and played, but no sound output. This is not a CinGG error, something with the machine low-level config. Even speaker-test does not work. Alsa config seems OK, output does not go to HDMI monitor.
Video (tried short 720p video) can be loaded, but as soon as you do anything CinGG is terminated with a "bus error".
oh, fun! probably something unaligned ... can you gdb? ) also try to disable x11 direct checkbox. don't know what that
is. Not CinGG I think. Hardware is 2 core Cortex A7 at 1 GHz, 1G ram, 8G flash (for OS), 500G hdd (data), swapfile 10G on hdd (and being used quite a lot).
MatN
On Mon, 26 Sep 2022 16:21:39 +0300 Andrew Randrianasulu <[email protected]> wrote:
пн, 26 сент. 2022 г., 15:05 mat <[email protected]>:
Hi Andrew,
What OS did you use to compile it on the Orange Pi Lite?
this is not my personal experience, I just tried to condense talk we had at linux.org.ru forum.
I think last OS mentioned there was "Arch Linux ARM" and simple addition of armv7l case in guicast/Makefile along with previous arm8l fixed predictable build failure .... fix already in cingg git
thread https://www.linux.org.ru/forum/linux-hardware/16959253?cid=16983577
I tried earlier this year to compile it on a Cortex-A7 based CPU (Allwinner A20 2 core), the Orange PI lite has the 4 core version of that. I used Debian, and it failed quickly.
you can try again with this reported config
./configure \ --prefix=/usr \ --disable-libaom \ --disable-libwebp \ --disable-dav1d \ --disable-static-build \ --without-nv \ --without-cuda \ --with-exec-name=cinelerra-gg
and/or disable thirdparty build completely
for speeding up test compile in guicast and
cinelerra dirs
MatN
On Wed, 28 Sep 2022 01:30:22 +0300 Andrew Randrianasulu <[email protected]> wrote:
вт, 27 сент. 2022 г., 22:37 <[email protected]>:
I got it to build.
Configure options: --with-single-user --with-booby --disable-dav1d (because av1 has code written in x86 assembly). --without-vaapi (hw accell does not work on this machine) --without-vdpau --without-nv --without-wintv --without-x10tv --disable-libaom (there seem to be "always inline" functions that causes problems with arm_neon.h and other files. --disable-libwebp
CinGG loads fine, menus work. Audio can be loaded and played, but no sound output. This is not a CinGG error, something with the machine low-level config. Even speaker-test does not work. Alsa config seems OK, output does not go to HDMI monitor.
Video (tried short 720p video) can be loaded, but as soon as you do anything CinGG is terminated with a "bus error".
oh, fun! probably something unaligned ... can you gdb? ) also try to disable x11 direct checkbox.
Interesting. dmesg showed indeed an alignment problem. Running it under gdb showed 0x012c24a8 in ff_yuv420p_to_rgba_neon () Consequently I manually set up the format to RGB instead of RGBA, and loaded the video from resources. It does play, but the speed is not impressive. About 1 frame/s :-) . It does not matter if I use X11 or GL, except GL gives a higher CPU utilisation. With X11, CPU utilisation is about 50%, and the hairline cursor keeps jumping back for about a second each time, but the end value you see slowly increasing. This was a static build. I'll try a dynamic build next. MatN
пт, 30 сент. 2022 г., 18:08 <[email protected]>:
On Wed, 28 Sep 2022 01:30:22 +0300 Andrew Randrianasulu <[email protected]> wrote:
вт, 27 сент. 2022 г., 22:37 <[email protected]>:
I got it to build.
Configure options: --with-single-user --with-booby --disable-dav1d (because av1 has code written in x86 assembly). --without-vaapi (hw accell does not work on this machine) --without-vdpau --without-nv --without-wintv --without-x10tv --disable-libaom (there seem to be "always inline" functions that causes problems with arm_neon.h and other files. --disable-libwebp
CinGG loads fine, menus work. Audio can be loaded and played, but no sound output. This is not a CinGG error, something with the machine low-level config. Even speaker-test does not work. Alsa config seems OK, output does not go to HDMI monitor.
Video (tried short 720p video) can be loaded, but as soon as you do anything CinGG is terminated with a "bus error".
oh, fun! probably something unaligned ... can you gdb? ) also try to disable x11 direct checkbox.
Interesting. dmesg showed indeed an alignment problem. Running it under gdb showed 0x012c24a8 in ff_yuv420p_to_rgba_neon ()
Consequently I manually set up the format to RGB instead of RGBA, and loaded the video from resources. It does play, but the speed is not impressive. About 1 frame/s :-) . It does not matter if I use X11 or GL, except GL gives a higher CPU utilisation. With X11, CPU utilisation is about 50%, and the hairline cursor keeps jumping back for about a second each time, but the end value you see slowly increasing.
sounds like audio output issue. try to disable sound tracks?
This was a static build. I'll try a dynamic build next.
MatN
participants (6)
-
Andrea paz -
Andrew Randrianasulu -
mat -
Miroslav Rovis -
mnieuw＠zap.a2000.nl
-
Phyllis Smith