I found the amount of post-processing time when taking Megapixels photos to be a bit annoying so decided to move that to batch processing which can be run manually when convenient.
This is a real quick-and-dirty kludge. I'm not familiar with the image processing tools being used by the original postprocess.sh, so I stripped that down and sussed out the filename handling as best I could. If there are grievous errors please let me know, but this seems to work.
When taking photos the .dng files are copied directly to ~/Pictures and not further processed. The batch processing is done directly in ~/Pictures by manually running a script when desired. Intermediate .tiff files are deleted but original .dng files are kept in case something goes horribly wrong. If the corresponding .jpg file already exists that .dng file is skipped. (It is assumed that dcraw, imagemagick, and exiftools are installed. The original code determining what programs are installed is stripped out for simplicity.)
The following custom postprocess.sh is placed in ~/.config/megapixels:
Code:
#!/bin/sh
# The post-processing script gets called after taking a burst of
# pictures into a temporary directory. The first argument is the
# directory containing the raw files in the burst. The contents
# are 1.dng, 2.dng.... up to the number of photos in the burst.
#
# The second argument is the filename for the final photo without
# the extension, like "/home/user/Pictures/IMG202104031234"
#
# The post-processing script is responsible for cleaning up
# temporary directory for the burst.
if [ "$#" -ne 2 ]; then
echo "Usage: $0 [burst-dir] [target-name]"
exit 2
fi
# Move the first frame of the burst into ~/Pictures as the raw photo
mv "$BURST_DIR/1.dng" "$TARGET_NAME.dng"
# Clean up the temp dir containing the burst
rm -rf "$BURST_DIR"
exit 0
The following is saved to ~/bin/pp (the short name makes it easy to type via on-screen keyboard):
Code:
#!/bin/bash
# The post-processing script processes and converts the .dng files
# in ~/Pictures to .jpg files.
# Define processing function
process() {
CONVERT="/usr/bin/convert"
DCRAW=/usr/lib/libraw/dcraw_emu
EXIFTOOL=/usr/bin/exiftool
TIFF_EXT="dng.tiff"
# -fbdd 1 Raw denoising with FBDD
set -- -fbdd 1
# +M use embedded color matrix
# -H 4 Recover highlights by rebuilding them
# -o 1 Output in sRGB colorspace
# -q 3 Debayer with AHD algorithm
# -T Output TIFF
echo "Enhancing raw image, convert to tiff..."
$DCRAW +M -H 4 -o 1 -q 3 -T "$TARGET_NAME.dng" "$TARGET_NAME.dng"
echo "Converting to jpg..."
$CONVERT "$TARGET_NAME.$TIFF_EXT" -sharpen 0x1.0 "$TARGET_NAME.jpg"
echo "Copying exif data to jpg..."
# Copy the exif data over from the tiff to the jpeg
# since imagemagick is stupid
$EXIFTOOL -tagsFromfile "$TARGET_NAME.$TIFF_EXT" \
-software="Megapixels" \
-overwrite_original "$TARGET_NAME.jpg" >/dev/null
$EXIFTOOL -tagsFromFile @ "-ModifyDate>DateTimeOriginal" \
-overwrite_original "$TARGET_NAME.jpg" >/dev/null
# We get an error in the loop if there are no .dng files, so check first.
if [ ! -f ~/Pictures/*.dng ]; then
echo "No .dng files found, aborting."
exit 0
fi
# Loop through dng files and call process() function
pushd ~/Pictures >/dev/null
for file in *.dng
do
TARGET_NAME=`echo $file | cut -d . -f 1`
if [ ! -f $TARGET_NAME.jpg ]; then
echo '----------------------------------------'
echo Processing $file...
process
echo '----------------------------------------'
fi
done
popd >/dev/null
So basically you just take your photos and the .dng files are quickly deposited in ~/Photos. Then when you want to process them and convert to jpg you just run "pp" from the terminal. (An icon on the screen could be set up for this if desired.) When satisfied that the jpg files are OK you can delete the original dng files to save space if desired.
I'm just beginning to play with my new Pinebook Pro. Arrived May 2021.
The only issue I'm unhappy with is that the touchpad seems to lag on initial movement. i.e. you move your finger then the arrow moves some time later. It's making button pressing and resizing windows very awkward. I currently have a mouse plugged in and this works fine. However I would like the touchpad working for 'sofa surfing'.
I've already read a lot of previous post about the issue from 2019 and 2020. I've tried re-flashing the keyboard driver and tried some of the previous reported 'fixes'. There may be some slight observable improvement but it's marginal. The main issue is initial finger movement and a lag in the pointer. Has anyone got one of the newer pinebook pros and is experiencing the same issue?
I'm running the Manjaro install that came with the laptop. I've also tried the Debian release booted from sd card and this exhibited the same issue.
I think it maybe a driver or power management issue rather than hardware since the hardware seems to function fine other than this initial lag.
Is there a solution to this problem? Other than that the laptop is brilliant!
Just got my pinecil and it looks good. Did a quick test with lead free solder and it worked fine.
The only barrel 5.5 mm power supply I had in the house was 12 volts. (no USB C in the house either) With my temperature set up to 360 C it barely maintained it that hot. I put a watt meter on the AC electric side if the cord and it showed a maximum of 19 watts, even though the 12 vDC converter can deliver 3 amps. . . 36 watts.
I see in the wiki in the QC discussion, it says 12v will only deliver 18 watts. I assumed that was a QC limitation. Is the 18 watts at 12 volts always a limitation? (I’ll go read some datasheets)
I have been wearing my Pinetime basically nonstop since I got it. I took it off just now and there is a burn mark on my arm where I was wearing it. Has anyone else experienced this, and should I be worried?
I'm confident this is not any form of allergic reaction to the materials of the device as this burn is exclusively under the sensors on the backside of the pinetime. I think the sensors somehow burnt me, but the device itself never got hot to the touch.
I've started playing music in my headphones without realizing it's also blaring from the speakers in public enough times now to try to fix this.
If headphones are in on boot, sound will come out of both them and the speakers unless you remove them and put them back. How to make only play from headphones if they are in on boot?
This is for a user who just got a PBP (loves it ) and before has used LinuxMint Cinnamon since forever.
Since he's used to Cinnamon, he wanted that as a DE, and I thought, "Easy. Go to Add/Remove software, find cinnamon-desktop, and install."
Well, that part was easy. But it keeps booting into KDE. I simply cannot find where you tell the system to use cinnamon. There's no option to choose DE at login (that I could see), and no setting that can be changed after it's booted.
Hi guys,
I just got my phone few weeks back and been testing different builds. The 2 that I like and are working most of the time are Arch Linux Arm and Mangaro Phosh also Manjaro plasma(but having problem waking up the screen).
I find that when I try to call my Cell the modem for the sim card and I use shaw mobile services in BC always have busy signal on a first dial, if I hangup and call again the call goes true. Any one have the same experience? Other than that I love the phone and the option to ungoogle myself is great.
pretty new to cell phones with previous desktop experience with linux. i have an old blackberry z30 that needed replacement and didn't like the iphone/ android options.
i recently inserted my sim card into the pinephone and keep getting the 'modem no carrier' messages. i'm on the koodo/telus network in canada. koodo network is displayed on the top right of the pinephone. sms, spacebar, and the phone seem to be functioning normally!? is there something i should be doing/configuring?
Have you cut a hole in the back cover of your pinephone and regularly switch off your cellular modem with the dip switch to keep the 3 letters from being creepy? If so, you will need these scripts so you can turn off/on the modem without having to restart your phone.
Turning modem off:
Install "minicom"
Code:
sudo apk install minicom
Create file "modem_shutdown" with the following text:
Code:
sudo minicom -S shut_down -D /dev/ttyUSB2
Create file "shut_down" with the following text:
Code:
send AT+QPOWD=1
now make both executable (Probably don't need to make "shut_down" executable)
I also added read/write so I can edit them as needed later.
Install gnome-terminal (So you can click "Run in terminal" in the filemanager "Nemo")
Code:
sudo apk install gnome-terminal
now click on "modem_shutdown" in your home or whatever directory you put these files. Be sure to click "open in terminal" and supply your user password. You should see a minicom screen pop up and it will eventually say "Cannot open /dev/ttyUSB2!". Close out the minicom instance. You can now switch off the modem with the dip switch.
Turning modem on:
Create file "modem_startup" with the following text:
Code:
sudo rc-service eg25-manager restart
make it executable
Code:
sudo chmod 700 modem_startup
Flip the dip switch back on and click on "modem_startup" and "Run in terminal" like the shutdown script.
) and before has used LinuxMint Cinnamon since forever.
Help, please. 
