Alexander Bougakov

I've realized that the error is caused by this line: ``` let rc = process::Command::new("./build_ffmpeg.sh") ``` which refers to a clearly not a cross-platform Bash script. Tried recompiling with no...

Found the required `*.lib` files in [https://ffmpeg.zeranoe.com/builds/win32/dev/](https://ffmpeg.zeranoe.com/builds/win32/dev/), placed them into `C:\Program Files\Rust stable MSVC 1.43\lib\rustlib\x86_64-pc-windows-msvc\lib`. Got this: ``` C:\Users\sanja\Downloads\audioserve-master\audioserve-master>cargo build --release --no-default-features Compiling audioserve v0.12.1 (C:\Users\sanja\Downloads\audioserve-master\audioserve-master) error: linking with `link.exe`...

I've realized that I've got wrong libs (32 bit), downloaded the 64-bit version from https://ffmpeg.zeranoe.com/builds/win64/dev/ffmpeg-4.2.2-win64-dev.zip and placed them into `C:\Program Files\Rust stable MSVC 1.43\lib\rustlib\x86_64-pc-windows-msvc\lib` ``` C:\Users\sanja\Downloads\audioserve-master\audioserve-master>cargo build --release --no-default-features Compiling...

Got another Windows-specific bug: the program does not recognize disk labels in paths: ``` audioserve.exe --no-authentication t:\Audiobooks error: Invalid value for '...': "t" is not existing directory ``` I've compiled...

Apologies, I am a moron. I've placed the `bundle.js` I've compiled elsewhere (on a more powerful Mac computer) in a wrong folder. Should have placed it into `audioserve-master\target\release\client\dist\bundle.js` **So the...

One more thing: `audioserve` keeps the terminal window open the entire time it is being run. I believe I could use some tool like https://robotronic.de/runasserviceen.html to run it as a...

I've solved a similar problem - I wasn't satisfied with the printer's built-in fonts, it also lacked support for non-Latin characters. So instead I render Unicode texts using TrueType fonts...

Got an idea, ran `pip3 install -I python-escpos==2.2.0` to downgrade python-escpos. It solved the problem immediately.

> I will work on a fix for this. Please consider making the tool more verbose (like writing g-codes it generates, to the log) - it could have made spotting...

@outlookhazy , check that "steps per mm" in OpenDACT matches the actual setting.