Johannes Wagner
Johannes Wagner
I have a MP3 encoded stereo file of the following length: ``` >>> audiofile.duration(path) 3.996734693877551 ``` Reading in the full file works: ``` >>> audiofile.read(path) [[0. 0. 0. ... 0....
As far as I see the benchmark only measures how long it takes to read full files. Might be interesting to also benchmark how long it takes for a library...
Currently `oyaml.BaseLoader` is used to load the config file, which according to the [documentation](https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation) loads everything as a string:  Although, we currently have only strings in the config file,...
Once a database is completely loaded there is actually no need to lock it. But currently we need to get access to the `db.yaml file` to get this information and...
Currently, we always publish media files as zip files. This makes sense for bundles and uncompressed files like WAV, but not for single compressed files like MP3, OGG, etc. In...
We should add additional security checks that check for out-of-bound segments in segmented tables and files with zero duration. Both are most likely bugs. In case the user adds such...
With large databases I sometimes do the following: 1. go to the `audb` cache and delete all table files 2. rename version folder from previous, e.g. 1.0.0, to new version,...
As discussed in https://github.com/audeering/audb/issues/201 we have switched to a soft lock mechanism as a platform-independent lock mechanism. Unfortunately, this is not always safe and we can run into dead locks...
See https://github.com/audeering/audb/pull/266#discussion_r1158622796
When loading a database with `audb.load()` we currently check the repository in which the requested version was found. Loading files from a previous version published in a different repository (which...