My Windows 7 PC (8gb RAM) will clear the RAM if chdkptp exceeds 900 mb of memory. It shot 1500 pictures (about 6gb) without any problem.My RPi3 (1gb RAM) with Raspian does not clear the RAM, so it crashes. The following pictures are saved to the camera SD card (as you mentioned in https://chdk.setepontos.com/index.php?topic=13386.msg136688#msg136688). Sometimes the RPi will clear the RAM once or maybe twice, but it crashes always. My best attempt was about 800 pictures.
edit /etc/udev/rules.d/40-libgphoto2.rules, immediately below the lineCode: [Select]ENV{ID_USB_INTERFACES}=="", IMPORT{program}="usb_id --export %%p"AddCode: [Select]ENV{ID_USB_INTERFACES}=="*:060101:*", ATTRS{idVendor}=="04a9", MODE="0664", GOTO="libgphoto2_rules_end"
ENV{ID_USB_INTERFACES}=="", IMPORT{program}="usb_id --export %%p"
ENV{ID_USB_INTERFACES}=="*:060101:*", ATTRS{idVendor}=="04a9", MODE="0664", GOTO="libgphoto2_rules_end"
ENV{ID_USB_INTERFACES}=="", IMPORT{builtin}="usb_id"
As discussed in this thread I was able to get CHDK PTP working on OpenSuse Leap 42 using a slight modification of the instructions for Fedora 27.
2. question about special (not A-Z) characters after the path command when in rsint modeWhat characters are supported after the path command? Could support be added for characters such as the german ü ?For example if we start rsint mode and then enter the commandsCode: [Select]path C:/1ü2/1sone would expect the file Code: [Select]C:/1ü2/1.jpgBut in my tests the image is instead saved as Code: [Select]C:/12/1.jpg where the character between 1 and 2 is https://unicode-table.com/en/search/?q=%C2%81 , a character not visible in File Explorer in Windows 10
path C:/1ü2/1s
C:/1ü2/1.jpg
C:/12/1.jpg
Unfortunately, chdkptp currently isn't unicode aware at all, so I'd recommend sticking to straight ANSI for now. Maybe I can fix this in the future.
QuoteOk, I'll make users stick to A-Z 0-9 Space in paths for now.You can allow other ASCII symbols if you want (_-+= etc), excluding any the OS disallows of course.Spaces may be a problem in some contexts, but as long as you've tested that it works it should be fine. For most normal chdkptp commands (download, rs etc), spaces would need to be quoted, but rsint has it's own parsing.
Ok, I'll make users stick to A-Z 0-9 Space in paths for now.
setup-ext-libs.bash likely does not work on OSX, but I think I fixed the bug in the script @ftm encountered in https://chdk.setepontos.com/index.php?topic=6231.msg135956#msg135956
Mostly works on MacOS (10.15.1) with a couple of tweaks:
- requires -nogui option (CD does not build anymore, I've given up trying to make it work)
- copy_runtime does not copy the Lua libs if -nogui is set- the path for the Lua libs in liblist-osx.txt should be lua52/lib not lua
Quote- requires -nogui option (CD does not build anymore, I've given up trying to make it work)Does the version from https://chdk.setepontos.com/index.php?topic=6231.msg135842#msg135842 still build with that procedure? Those libs should still work with chdkptp. If you don't want to mess with it, that's totally fine.
Quote- copy_runtime does not copy the Lua libs if -nogui is set- the path for the Lua libs in liblist-osx.txt should be lua52/lib not luaHmm, on the other platforms I link lua statically. There's a special case in copy_built_lua to make a dylib, if you leave that out can it just link to the .a?
Started by waterwingz General Discussion and Assistance
Started by alex73 « 1 2 » General Discussion and Assistance
Started by dmitrys General Discussion and Assistance
Started by nod5 General Discussion and Assistance
Started by Caefix General Discussion and Assistance
