My usage has been crash free, so pushing.
My usage has been crash free, so pushing.
My usage has been crash free, so pushing.
Mainly testing record, generate, hi/lo pass filters, fadein, out, save, export, trim cut paste, zero, normaiize, No issues so far.
Mainly testing open, generate, hi/lo pass filters, fadein, out, save, export, record, trim cut paste, zero. No issues so far.
Works fine on sample tnef I've received. Pushing.
Works OK for my desktop. Going to push into updates.
Works OK for my laptop. Going to push into updates.
Looks good in my testing.
Looks good in my testing.
Extracting conforming content works OK. Extracting from the faulty ProofOfConcept tnef file generates an assertion and core dump. The program author says the core dump is expected.
tnef 1.4.15 fc26 runs, but: testing with the proof of concept generates an assert and core dump. I'm not sure that it should core dump..I would have expected an error message / errorlevel return.
I've asked at: https://github.com/verdammelt/tnef/issues/23
p.s. thanks to Kevin for noticing / updating my package.
Dolphin integration good. Operates as expected.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
It's been working fine on my system, so pushing.
This update has been unpushed.
With this version, vbindiff no longer crashes. However, I notice that once I aligned two (99% similar) mp3 files (audio body), then page up/down work. But then when I did top the files were no longer locked together to the matching positions I set. I'm not sure if the patch introduced this limitation; I assumed that if say the most similar parts of the files are 128 bytes out of alignment, then if I hit home, then the position of one file will be 128 bytes different, rather than resetting the offset to zero (home) in both files. This doesn't occur for the end button.
Installs ok from updates-testing. Able to run python3.12 import timelib and run the examples in the spec file description. Results seem OK.