Kris Fedorenko

Thanks a lot for this explanation, @arthurt ! > libsndfile does not work like `lame --add-id3v2`, and liblame will only output an id3v2 header in circumstances where tag field sizes...

Thanks @arthurt !   > What I meant by using UTF-16, is that UTF-16 could be used internally. The libsndfile user facing `sf_set_string()` would still expect UTF-8 input, but that UTF-8...

Hi @arthurt I am looking into developing a patch to LAME that would add the functionality of writing **ID3v2.4** UTF-8 tags. I have something that seems to work, but I...

Agreed, thanks @arthurt! I was just thinking that writing UTF-8 to ID3v1 is the current (buggy) behavior, so maybe there was some argument about keeping it for backwards compatibility... But...

Hi @arthurt and @evpobr , I have posted my patch to LAME to add the functionality of writing ID3v2.4 UTF-8 tags here: [https://sourceforge.net/p/lame/patches/99/#aad8](https://sourceforge.net/p/lame/patches/99/#aad8). As I was describing above, it adds...

Hi Dennis, have you had any luck? Thanks, Kris

Hi @DennisHeimbigner We seem to have run into a similar issue with a different file: `https://opendap.earthdata.nasa.gov/collections/C3309442935-POCLOUD/granules/NASA-SSH_alt_ref_simple_grid_v1_19921102#dap4` It needs authentication, and I have the .netrc and .dodsrc set up [as needed](https://opendap.github.io/documentation/tutorials/ClientAuthentication.html#dodsrc)...

We got a bit more info about how the file was created. The following versions of libraries and packages were used: libnetcdf 4.8.1 netcdf4 1.6.2 hdf4 4.2.15 hdf5 1.12.2 python...

Thank you for the detailed explanation @edwardhartnett ! I guess I was asking more about what is "allowed" with netCDF APIs (both C and python), i.e. **what the official netCDF...

Hi @edwardhartnett , Sorry to raise this question again, but we have noticed an increased number of such files in recent months. I *think* their source is European Centre for...