exif-rs
rp-hal
Our great sponsors
exif-rs | rp-hal | |
---|---|---|
2 | 30 | |
178 | 1,256 | |
- | 5.8% | |
0.0 | 9.3 | |
about 1 month ago | 5 days ago | |
Rust | Rust | |
BSD 2-clause "Simplified" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exif-rs
-
Hey Rustaceans! Got a question? Ask here! (27/2022)!
I dont want the files to waste a lot of space so i decided to resize them. For that i used the resize method from the "image" crate. Everything works fine, until i start to upload images above 5mb. Then the resize method starts to rotate the images. I think i narrowed it down to the resize function deleting any existing exif data inside the image file. That way the orientation flag is removed and the image is in its default position. I already tried to fix this, by saving the exif data before resizing and then rewriting it to the image file. The only library that i could find that supports writing (at least for png and jpeg) was this one: kamadax-exif. The problem is, that when i write the exif data (all the previous data or just the orientation data) the file gets corrupted. Now to my question: Can someone recommend a library that can resize images, that preserves the aspect ratio and does not delete the exif data? if not, does someone have an idea on how to resize the images differently? Or maybe there exists another exif data crate that i can use? I hope this question is understandable, thanks in advance :)
-
Announcing: ImageSieve, a tool to assist in sorting and archiving images and videos
I absolutely loved all the crates available that made my life very simple in many cases. I used (among others) the slint ui framework, kamadak-exif, img_hash, fast_image_resize and rawloader.
rp-hal
-
Embedded Swift on the Raspberry Pi Pico
probably, I didn't really check it, but I found [1]. Rust has a lot of support for embedded systems, even from the companies that provide the chips, like STM and Espressif.
[1] https://github.com/rp-rs/rp-hal
- Rp-hal: a Rust Embedded-HAL for the pi pico series microcontrollers
-
I built a column staggered keyboard with firmware written in Rust!
About the same time, I was learning Rust and discovered how it could be used on embedded targets from Low Level Learning on YouTube, the video introduced me to the amazing rp-hal crate that provides abstractions to talk to the Raspberry Pi Pico microcontroller. Getting used to the no_std mode took some time, the most challenging was not being able to collect an iterator to a container.
-
How can I access the Pico W's LED with the rp-hal crate?
Well, just as I posted this, I came across the issue on Github: https://github.com/rp-rs/rp-hal/issues/525
-
&[u8] to *const u8
Have a read of https://github.com/rp-rs/rp-hal/issues/257 for more info.
-
Question: Elegant way of getting a 'static reference?
I've made an example for a RPI Pico (PR for the RP2040 HAL project here) .
-
Pico as a usb hid without circuitpy
Here's an example: https://github.com/rp-rs/rp-hal/blob/main/boards/rp-pico/examples/pico_usb_twitchy_mouse.rs
-
Learning Embedded rust
Embedded rust for the raspberry pi pico: https://github.com/rp-rs/rp-hal
-
The Rise of Rust, the ‘Viral’ Secure Programming Language That’s Taking Over Tech
What are you on about, can you clarify? Rust can compile in no-std/embedded style just as fine (or better) than C can for basically any ARM or RISCV based processor, and quick googling shows this hal for nearly all pi needs and even MEGA65 is "as supported" (read: not at all officially by anything, fan-only) as any current C compiler. Setting up rust for a new target, so long as the code-gen is supported somehow by LLVM, LLVM plugin, LLVM IR transpiler (and maybe libgcc-jit sort of soon) is just as painful or unpainful as setting up a whole team to work via C/C++ with comparable testing harnesses. This doesn't mean easy and is an area Rust is still improving rapidly by the various enterprise agencies (Ferrous systems, Oxide, more I can't remember...) who specifically want to bring rust to such low end hardware because frankly both C and C++ suck with vendor proprietary tool chains and quirks.
-
"pub use bare_metal::CriticalSection;" Error
He says he can't find crate for 'bare_metal'. He was setting up and testing the HAL for the pico (https://github.com/rp-rs/rp-hal). While compiling it pulls down critical-section-0.2.7/src/lib.rs and bars on line 7
What are some alternatives?
img-parts - Low level crate for reading and writing Jpeg, Png and RIFF image containers
tutorials - 📚 Stash of tutorials completed for learning cool stuff.
fast_image_resize - Rust library for fast image resizing with using of SIMD instructions.
embassy - Modern embedded framework, using Rust and async.
rawloader - rust library to extract the raw data and some metadata from digital camera images
rlox
rust-analyzer - A Rust compiler front-end for IDEs
edn - Extensible Data Notation
exiftool-rs - Image metadata scrubber written in Rust.
rp2040-project-template - A basic rp2040-hal project with blinky and rtt logging example code. With this you can quickly get started on a new rp2040 project
image-sieve - GUI based tool to sort and categorize images written in Rust
avr-hal - embedded-hal abstractions for AVR microcontrollers