multicam, first steps, syntax wrong?

Mlapse

584
S95 S110

Re: multicam, first steps, syntax wrong?

« Reply #10 on: 13 / April / 2022, 01:56:53 »

Advertisements

Quote from: reyalp on 12 / April / 2022, 16:41:29

That said, I'm don't really understand why you want to run rawopint from within multicam.lua. The purpose of multicam is primarily synchronized shooting with multiple cameras. Using to to run a different script to do the shooting doesn't really make sense to me. If you just want to start a script on several cameras, multicam seems like needless complication, you do do a very simple script to iterate over chdk.list_usb_devices. See extras/simplemulticam.lua for a possible starting point, though beware it may be out of date. Or just use a chdkptp command script to connect to each camera in turn by name or serial number.

what i'm trying to make is a rig with 2 cams that shoot syncronised without end. i'm not that interested in getting it right up until the milisecond, but the closer i get, the better.
i was thinking of using multicam for that or use an usb 5v pulse. i wouldn't know of any other methods available, or it must be this:
https://chdk.setepontos.com/index.php?topic=14195.msg144819#msg144819

however, i would like the cams to keep shooting even if the pc is not available with the risk of loosing syncronisation due to rtc differences between cameras.
this means something has to run cam side that keeps the interval going if there is no message from the pc within the set time.
and if all that is working i want the cam to use some long exposure calculations, like what i use in SUIx. and after that, it can be tested and used.
maybe downloading between shots while a script is active will come into play again...and hopefully i've accumulated the knowledge to make that by then.

seperate, but related:
i also have this one project that is running for over 4 years now with one stand alone cam. this cam needs occasional syncronisation with time and i do that by hand.
i wrote a simple line to only set the clock: press the button and all active cams will be set.
since mc already had utc and a fairly accurate timing loop it looked most obvious for me to use that.
i was thinking of connecting the pc every now and then to that cam to set the clock.
this can be done each time i exchange the sd card, but ideally i think it should be possible to do that at any given moment during the script run (reboot, between shots, maybe once a day)
should this entail stopping the cam side script, setting rtc, starting the cam side script? or is there a way to do this while the cam side script is running, like with a message or f.i. by counting shots taken this day.

those are things that i'm thinking about and when i get stuck, as a distraction, i sometimes spend days in solving something trivial, like a shortcut instruction for chdkptp.

i installed libreadline8, as for running misc/setup-ext-libs.bash that ended sadly:
### building Lua ###
setup-ext-libs.bash error: make linux

i'm running 21.10 as i see from the readme that's untested, moving to 22.04 in a few weeks

« Last Edit: 13 / April / 2022, 17:56:02 by Mlapse »

Logged

frustration is a key ingredient in progress

reyalp

14118

Re: multicam, first steps, syntax wrong?

« Reply #11 on: 13 / April / 2022, 17:57:23 »

Quote from: Mlapse on 13 / April / 2022, 01:56:53

i installed libreadline8, as for running misc/setup-ext-libs.bash that ended sadly:
### building Lua ###
setup-ext-libs.bash error: make linux

i'm running 21.10 as i see from the readme that's untested

Check the log in extlibs/built/build-lua.log

Note that you need the readline *development* package, often called something like libreadline-dev or similar, not just the library needed for precompiled apps.

Logged

Don't forget what the H stands for.

Mlapse

584
S95 S110

Re: multicam, first steps, syntax wrong?

« Reply #12 on: 14 / April / 2022, 01:06:40 »

Quote from: reyalp on 13 / April / 2022, 17:57:23

Note that you need the readline *development* package, often called something like libreadline-dev or similar, not just the library needed for precompiled apps.

got further but alas the list only got longer. 5.3 the problem?

build-lua.log (4.11 kB - downloaded 4 times.)

« Last Edit: 14 / April / 2022, 09:11:50 by Mlapse »

Logged

frustration is a key ingredient in progress

reyalp

14118

Re: multicam, first steps, syntax wrong?

« Reply #13 on: 14 / April / 2022, 14:23:19 »

Quote from: Mlapse on 14 / April / 2022, 01:06:40

Quote from: reyalp on 13 / April / 2022, 17:57:23
Note that you need the readline *development* package, often called something like libreadline-dev or similar, not just the library needed for precompiled apps.

got further but alas the list only got longer. 5.3 the problem?

No. In the current svn, Lua 5.3 is the default, and 5.2 is deprecated.

The error

Code: [Select]

lua.c:82:10: fatal error: readline/readline.h: No such file or directory
   82 | #include <readline/readline.h>
      |          ^~~~~~~~~~~~~~~~~~~~~

This says it couldn't find the readline header file, which suggests the readline development package is not installed, or the paths are somehow unusual in your distro (IMO less likely).

What distro are you using?

Logged

Don't forget what the H stands for.

Mlapse

584
S95 S110

Re: multicam, first steps, syntax wrong?

« Reply #14 on: 14 / April / 2022, 15:26:06 »

i did not know how to fix that, but reinstalling seemed to have solved it.

now that this is done what to do with make

because i'm really looking forward to this new build....should i start that from the trunk? and what do i tell make?

Code: [Select]

~/trunk$ misc/setup-ext-libs.bash
mkdir -p /home/xxxx/trunk/extlibs/archive /home/xxxx/trunk/extlibs/src /home/xxxx/trunk/extlibs/built
### downloading packages ###
skip download existing: lua-5.3.6.tar.gz
skip download existing: cd-5.14_Linux415_64_lib.tar.gz
skip download existing: cd-5.14-Lua53_Linux415_64_lib.tar.gz
skip download existing: iup-3.30_Linux415_64_lib.tar.gz
skip download existing: iup-3.30-Lua53_Linux415_64_lib.tar.gz
### check download shasums ###
lua-5.3.6.tar.gz: OK
cd-5.14_Linux415_64_lib.tar.gz: OK
cd-5.14-Lua53_Linux415_64_lib.tar.gz: OK
iup-3.30_Linux415_64_lib.tar.gz: OK
iup-3.30-Lua53_Linux415_64_lib.tar.gz: OK
### unpacking downloads ###
rm -rf /home/xxxx/trunk/extlibs/src/lua-5.3.6
tar -xzf /home/xxxx/trunk/extlibs/archive/lua-5.3.6.tar.gz -C /home/xxxx/trunk/extlibs/src
rm -rf /home/xxxx/trunk/extlibs/built/cd
mkdir -p /home/xxxx/trunk/extlibs/built/cd
tar -xzf /home/xxxx/trunk/extlibs/archive/cd-5.14_Linux415_64_lib.tar.gz -C /home/xxxx/trunk/extlibs/built/cd
tar -xzf /home/xxxx/trunk/extlibs/archive/cd-5.14-Lua53_Linux415_64_lib.tar.gz -C /home/xxxx/trunk/extlibs/built/cd
rm -rf /home/xxxx/trunk/extlibs/built/iup
mkdir -p /home/xxxx/trunk/extlibs/built/iup
tar -xzf /home/xxxx/trunk/extlibs/archive/iup-3.30_Linux415_64_lib.tar.gz -C /home/xxxx/trunk/extlibs/built/iup
tar -xzf /home/xxxx/trunk/extlibs/archive/iup-3.30-Lua53_Linux415_64_lib.tar.gz -C /home/xxxx/trunk/extlibs/built/iup
### building Lua ###
### configure Lua binaries ###
mkdir -p /home/xxxx/trunk/extlibs/built/lua53/doc
cp doc/contents.html doc/index.css doc/logo.gif doc/lua.1 doc/luac.1 doc/lua.css doc/manual.css doc/manual.html doc/osi-certified-72x60.png doc/readme.html /home/xxxx/trunk/extlibs/built/lua53/doc
ln -s -f liblua.a liblua53.a
mkdir -p /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/cd/libcdlua53.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/cd/libcdcontextplus.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/cd/libcdluacontextplus53.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/cd/libcd.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/iup/libiupcd.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/iup/libiup.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/iup/libiuplua53.so /home/xxxx/trunk/lib
cp /home/xxxx/trunk/extlibs/built/iup/libiupluacd53.so /home/xxxx/trunk/lib

« Last Edit: 14 / April / 2022, 16:18:45 by Mlapse »

Logged

frustration is a key ingredient in progress

Mlapse

584
S95 S110

Re: multicam, first steps, syntax wrong?

« Reply #15 on: 14 / April / 2022, 15:43:50 »

i would like both gui and non gui build...although i think i have little use for the gui version i made that shortcut

« Last Edit: 14 / April / 2022, 15:58:28 by Mlapse »

Logged

frustration is a key ingredient in progress

reyalp

14118

Re: multicam, first steps, syntax wrong?

« Reply #16 on: 15 / April / 2022, 00:00:55 »

Quote from: Mlapse on 14 / April / 2022, 15:26:06

now that this is done what to do with make because i'm really looking forward to this new build....should i start that from the trunk?

Yes.

Quote

and what do i tell make?

Just make by itself should work, but to do a full build, use

Code: [Select]

make clean all

To include the GUI, add GUI=1 like

Code: [Select]

make GUI=1 clean all

If you want separate GUI and CLI executables like in the zip packages, you need to add GUI_SFX=_gui and use the chdkptp_gui.sh script. However, this should not be needed, you can run the GUI executable in CLI mode by passing -i (or any command line options other than -g)

If you want to make a complete zip you can install elsewhere, use

Code: [Select]

misc/bin-snapshot.bash

Logged

Don't forget what the H stands for.

Mlapse

584
S95 S110

Re: multicam, first steps, syntax wrong?

« Reply #17 on: 15 / April / 2022, 15:22:51 »

Quote from: reyalp on 15 / April / 2022, 00:00:55

If you want to make a complete zip you can install elsewhere, use
Code: [Select]
misc/bin-snapshot.bash

i probably could have finished this by now,
but felt daring

so i tried again with bin-snapshot
alas it stated

Code: [Select]

bin-snapshot.bash error: missing .extlibs/built/

this is not from the svn, but the zip.
have you got a suggestion what i'm missing here. there is no built-lua.log yet.

Logged

frustration is a key ingredient in progress

reyalp

14118

Re: multicam, first steps, syntax wrong?

« Reply #18 on: 15 / April / 2022, 16:52:02 »

Quote from: Mlapse on 15 / April / 2022, 15:22:51

this is not from the svn, but the zip.
have you got a suggestion what i'm missing here. there is no built-lua.log yet.

It sounds like you just ran bin-snapshot in a clean tree, without running setup-ext-libs first? If so, you need to run setup-ext-libs first.

setup-ext-libs downloads / builds the dependencies that aren't included in chdkptp svn. It needs to be run once after checking out the source or downloading the zip, or when you want to change some things about how the dependencies are configured.

bin-snapshot runs make and puts the results in zip file suitable able for distribution.

Logged

Don't forget what the H stands for.

Mlapse

584
S95 S110

Re: multicam, first steps, syntax wrong?

« Reply #19 on: 15 / April / 2022, 17:10:14 »

Quote from: reyalp on 15 / April / 2022, 16:52:02

It sounds like you just ran bin-snapshot in a clean tree, without running setup-ext-libs first? If so, you need to run setup-ext-libs first.

setup-ext-libs downloads / builds the dependencies that aren't included in chdkptp svn. It needs to be run once after checking out the source or downloading the zip, or when you want to change some things about how the dependencies are configured.

bin-snapshot runs make and puts the results in zip file suitable able for distribution.

should i run make after setup-ext-libs and before bin-snapshot?
because i just tried setup-ext-libs and then bin-snapshot but that wasn't it i guess

Code: [Select]

misc/bin-snapshot.bash
chdkptp-rUnversioned directory-Linux-x86_64.zip
Makefile:163: bottom.mk: No such file or directory
make: *** No rule to make target 'bottom.mk'.  Stop.
bin-snapshot.bash error: build failed

just tried 'make clean all', it gave the same bottom.mk error
but i can see it in the trunk folder....as far as i can see it is an empty file though.

« Last Edit: 15 / April / 2022, 17:29:33 by Mlapse »

Logged

frustration is a key ingredient in progress