Currently ReactOS only covers through Windows XP/2003.
FFmpeg has required Windows 7 or newer since 2015.
Thus without some hacks or compiling FFmpeg on ReactOS yourself, FFmpeg isn’t currently available on ReactOS.
A current version of VLC is in the ReactOS Application Explorer, try doing what you need with VLC instead of FFmpeg with ReactOS until ReactOS can support Windows 7 applications better.
These programs use syntax similar to the $1000 Matlab Mapping and Aerospace Toolboxes, while being independently developed as open-source software.
We use continuous integration on each package to help ensure quality results.
Instead of low-quality screen-shots a PDF to get the images, use Poppler to extract the original high-resolution images from the PDF.
Note: only raster images can be exported with Poppler.
Examples of PDF image extraction tasks:
List all PDF images:
pdfimages -list in.pdf
Extract PDF images from all pages, dumping all images in mydoc.pdf to the same directory.
Filenames start with out-.
There might be a lot of images.
pdfimages -all in.pdf out
Extract PDF images from specific pages: example is for page 3 only:
We have created Python scripts in
LibreOffice Utils
that recursively search for files matching a glob pattern (such as *.docx) and convert or print these input documents.
They use LibreOffice in headless (console) mode, just a single Terminal command.
doc2pdf.py: recursively converts directories containing DOC, DOCX, RTF or other word processing files to PDF.
doc2print.py: recursively print documents to the default printer
Python code using xarray.open_dataset() or xarray.open_dataarray() or similar functions reading from NetCDF4 use an
LRU cache
that automatically closes unneeded files.
As of xarray 0.11.0, the obsolete autoclose=True option should no longer be used.
Problems fixed by LRU cache: the LRU cache used to open NetCDF4 files with xarray fixes these problems, and gives high performance:
random segmentation fault while reading NetCDF4 .nc files, where the same file is reopened in the program.
OSError from too many open files, where even increasing ulimit doesn’t help
On upgrading major versions, say from VirtualBox 5.2 to VirtualBox 6.0, you may find you can’t start any of your VM images, getting an error including “kernel modules do not match”.
This may mean you haven’t removed all of the old version VirtualBox components.
Consider using synaptic or
apt list --installed | grep virtualbox
to see if any old VirtualBox components are installed that may be conflicting with the new VirtualBox version.