Re: [flac-dev] Release of FLAC coming up
Den fre 9 juni 2023 kl 17:28 skrev Martijn van Beurden : > Hi all, > > I'd like to release FLAC 1.4.3 on Friday the 23th of this month. That > makes 23-06-23, so there's no confusing the year with the date of the > month. > > Or just use the international standard format (ISO-8601): 2023-06-23. No confusion. > If anyone knows of any regressions, please let me know. > > Kind regards, Martijn van Beurden > ___ > flac-dev mailing list > flac-dev@xiph.org > http://lists.xiph.org/mailman/listinfo/flac-dev > ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
[flac-dev] Fwd: Metaflac UTF-8 fixes
Ooops… I accidently sent a reply privately instead of to the list, sorry for that. Here it is again, this time hopefully to the list: -- Forwarded message -- From: Johnny Rosenberg gurus.knu...@gmail.com Date: 2013/4/23 Subject: Re: [flac-dev] Metaflac UTF-8 fixes To: Janne Hyvärinen c...@sci.fi 2013/4/23 Janne Hyvärinen c...@sci.fi: Hopefully the last patch from me to UTF-8 issues. Metaflac can now print all console supported characters from tags on the screen. It also fixes metaflac to be able to import its own exports back without non-ascii characters getting mutilated. And --no-utf8-convert now works properly with import and export commands. I updated my Windows binary archive with these changes for any interested party to test: http://www.saunalahti.fi/~cse/temp/flac-1.3pre3-mod.zip I'm probably not allowed to say anything at all, since I'm not a developer (or at least not a good one), but I have used metaflac for years (in my own bash-scripts) and never had any problems with UTF-8 (I never use anything but UTF-8) what so ever. What exactly am I missing here? Johnny Rosenberg ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] Fwd: Metaflac UTF-8 fixes
2013/4/23 Ulrich Klauer ulr...@chirlu.de: Johnny Rosenberg wrote: but I have used metaflac for years (in my own bash-scripts) and never had any problems with UTF-8 (I never use anything but UTF-8) what so ever. What exactly am I missing here? As you mention bash, you're probably on a *nix system. All those UTF-8 fixes are for Windows only. Bash is available also for Windows, but you are right. I'm on Ubuntu 12.04 at the moment (had thoughts about switching to something else, maybe Arch or whatever, but I didn't yet). That makes sense anyway; in Windows you would expect UTF-16 or something rather than UTF-8, I guess, if not ISO-8859-something. Or even worse: Windows-1252… :P But I didn't use Windows since 2007, so I'm not sure what happened with it since then. Johnny Rosenberg Ulrich ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
[flac-dev] Fwd: (no subject)
Ooops, I accidently replied privately, sorry for that. Here's to the list (the corrected version, since I accidently omitted a word in my original reply): -- Forwarded message -- From: Johnny Rosenberg gurus.knu...@gmail.com Date: 2013/3/16 Subject: Re: [flac-dev] (no subject) To: Marcus Johnson bumblebritche...@gmail.com 2013/3/16 Marcus Johnson bumblebritche...@gmail.com: Does FLAC support 24 bit? I remember reading about people updating ffmpeg for 24 bit support so I'm not really sure what's going on. I almost never use anything else than 24-bit FLAC, and I didn't see a problem with it so far, so I guess it is supported. Johnny Rosenberg ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
[flac-dev] Fwd: flac 1.3.0pre1 prelease
I don't know how it happened, but I accidently sent the message below privately and not to the list. Maybe a result of my built in stupidity. -- Forwarded message -- From: Johnny Rosenberg gurus.knu...@gmail.com Date: 2013/3/3 Subject: Re: [flac-dev] flac 1.3.0pre1 prelease To: Cristian Rodríguez crrodrig...@opensuse.org 2013/3/3 Cristian Rodríguez crrodrig...@opensuse.org: El 02/03/13 20:22, Erik de Castro Lopo escribió: Hi all, I finally managed to bite the bullet and roll a pre-release. Its here: http://downloads.xiph.org/releases/flac/beta/ I have personally tested this code on: x86-linux x86_64-linux powerpc-linux armv7 little endian hard float. ppc64 ppc (linux) all test passes. Maybe a stupid question, but I was born stupid and I have walked that path ever since, so: Is there a changelog? ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] Commonly getting FLAC__STREAM_ENCODER_VERIFY_MISMATCH_IN_AUDIO_DATA on valid audio
2013/2/10 Erik de Castro Lopo mle...@mega-nerd.com: Johnny Rosenberg wrote: Anyway, if I'm allowed to ask a libsndfile question here, Sorry, but no, this list is for FLAC related discussion. And of course you won't waste your time replying outside this mailing list? Is there a libsndfile mailing list? Hm… yet another stupid question, of course. If there is, you wouldn't want me to know about it, right? :P Kind regards Johnny Rosenberg ジョニー・ローゼンバーグ Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] Newbie question about those callbacks
2013/2/10 Erik de Castro Lopo mle...@mega-nerd.com: Johnny Rosenberg wrote: For instance the write_callback thing: client_data – can it be a pointer to just about anything? I assume you mean: https://www.xiph.org/flac/api/group__flac__stream__decoder.html#ga13 which defines the type: typedef FLAC__StreamDecoderWriteStatus (* FLAC__StreamDecoderWriteCallback) (const FLAC__StreamDecoder *decoder, const FLAC__Frame *frame , const FLAC__int32 *const buffer[], void *client_data) Yes, client_data can point at anything. You the callee are responsible to cast your pointer_to_anything to and from 'void*' Thanks. That explains the following line in the write_callback function one of the the two examples I found: FILE *f=(FILE*)client_data; For instance a pointer to a two-dimensional array? Yes. They can even be NULL. Yes, I saw that in the other example… :) Whatever pointer you pass as the client_data parameter in the finction FLAC__stream_decoder_init_stream () will be passed back to you in the callbacks client_data. Are those FLAC-WAV and WAV-FLAC examples the only examples available? There are examples in the examples/ directory of the FLAC source code tarball. They are in Git here: https://git.xiph.org/?p=flac.git;a=tree;f=examples/c;h=dbcb345dcd699ca3f1a1b1d334f5a48d45385558;hb=HEAD Ok, that's the two examples that I already know about. I will not waste more time looking for more examples then. Thanks. What would be the best approach to read a FLAC file to an array of some kind? Passing a pointer to the array as ”client_data”? I'd like to use a two-dimensional array, but it's a little tricky (for a newbie) to pass to functions as a pointer. I agree, coding to the FLAC API is not something that is easy or obvious for a newbie C programmer. No, I realised that at an early stage. The future will show if I will give up or not… I am sure I will finish my code, but I'm not sure whether I will use libflac or something else. Thanks for helping. Kind regards Johnny Rosenberg ジョニー・ローゼンバーグ Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] Commonly getting FLAC__STREAM_ENCODER_VERIFY_MISMATCH_IN_AUDIO_DATA on valid audio
2013/2/10 Erik de Castro Lopo mle...@mega-nerd.com: Johnny Rosenberg wrote: And of course you won't waste your time replying outside this mailing list? Is there a libsndfile mailing list? Hm… yet another stupid question, of course. If there is, you wouldn't want me to know about it, right? :P http://lmgtfy.com/?q=libsndfile+mailing+listl=1 Oh… thanks for making me feel even more stupid…! :) I'll try to be less annoying on that list, if I decide to subscribe… Johnny Rosenberg (no, I'm not the excellent musician from the Netherlands, I'm just another musician, not so excellent, from another country, sorry) Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] Commonly getting FLAC__STREAM_ENCODER_VERIFY_MISMATCH_IN_AUDIO_DATA on valid audio
2013/2/8 Erik de Castro Lopo mle...@mega-nerd.com: Collin wrote: It turns out it was an error on my part; sorry for the trouble. I misunderstood the format libflac was expecting my samples in. I found the wording in the documentation very confusing. My audio file has 2 channels and 16-bit samples, so I have to pull out each individual sample, push it into a FLAC__int32, and fix endian-ness before I can pass it to libflac. The documentation made me think that libflac just wanted me to shove my 2-byte sample into a FLAC__int32. I wasn't aware that it wanted me to extend the sign, as well. At some stage it might make sense for us to make the FLAC API a little more user/programmer friendly. Something to match libsndfile's ease of use. That would be great! I was actually starting my small ”project” with libsndfile, but it was done in a way that I didn't agree with, and since I only work with FLAC files (mostly 24 bits) I decided to try to go with libflac instead, which seems to let me do things the way I want more than libsndfile. For example, when loading an audiofile with libsndfile, all the samples are converted to floating point numbers, which is what I want anyway, but the conversion is done by dividing the integers from the file with pow(2,bps-1), but when converting back, they multiply with pow(2,bps-1)-1, so if you just read and then write, you end up with a slightly lower volume (not that you can hear any difference if you do it only a few times, but still, it isn't right, AND it is very easy to do it right, so why don't they?)… Johnny Rosenberg, the beginner Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
Re: [flac-dev] Commonly getting FLAC__STREAM_ENCODER_VERIFY_MISMATCH_IN_AUDIO_DATA on valid audio
2013/2/9 Erik de Castro Lopo mle...@mega-nerd.com: Johnny Rosenberg wrote: For example, when loading an audiofile with libsndfile, all the samples are converted to floating point numbers, With libsndfile, converting to float is optional. You can just as easily read int or short. which is what I want anyway, but the conversion is done by dividing the integers from the file with pow(2,bps-1), but when converting back, they multiply with pow(2,bps-1)-1, so if you just read and then write, you end up with a slightly lower volume (not that you can hear any difference if you do it only a few times, but still, it isn't right, AND it is very easy to do it right, so why don't they?)… Firstly, you do realise that I am the main author and maintainer of libsndfile, don't you? Yes I do, now that you mentioned it. I'm not sure why that matters in a FLAC-dev mailing list, though. I didn't know there was a maintainer anyway these days, since I didn't get a reply when emailing about this a couple of years ago (or maybe it was last year, I don't remember – I sent it from one of my other email addresses, since I use this one for mailing lists only). Secondly, the scaling can be switched off don't you? See: http://www.mega-nerd.com/libsndfile/command.html#SFC_SET_NORM_DOUBLE Thanks, I don't think I saw that page before, for some strange reason. The sentence ”setting normalisation to SF_FALSE means that no scaling will take place”, does this mean, for instance for a 24-bit file, that the values will be doubles in the interval -8388608 to +8388607? That information should probably be added to question 10 in your FAQ, I suppose. For my purpose, not ”normalising” at all seems to be a good enough idea, I think. I will calculate the levels from dB anyway, so I just need to know how many bits per sample there is, which libsndfile easily lets me know. But I will try to do my thing with libflac first. If I fail making my code clean, simple and readable (and working…), I might give libsndfile another try. Finally, there are about 700 different way so convert between int and float. I chose the one that I thought had provided the best trade off. I stand by that decision. Well, the good thing is that this SFC_SET_NORM_DOUBLE thing allows me to do it the 701th way… Maybe I should convert to % or ‰… Anyway, if I'm allowed to ask a libsndfile question here, is there a special reason why you read sound files into one-dimensional arrays instead of two-dimensional ones (such as AudioData[Channel][Sample])? If so, what is that reason? Thanks. Kind regards Johnny Rosenberg ジョニー・ローゼンバーグ Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
[flac-dev] Beginner's question
I have just found out about the libflac thing and I have searched a bit for information about it. I found its API and two examples. My operating system is Ubuntu 12.04 and I installed the libflac-dev thing from the software center (which is equal to installing it with ”sudo apt-get install libflac-dev”. Is there anything more that I need to install to be able to compile, for instance, the example atthe following place? https://git.xiph.org/?p=flac.git;a=tree;f=examples/c/decode/file;h=911aaf7d72530b8e0f4c8e60d12c1dcaea1fda22;hb=HEAD Since I'm not a very good programmer I just want to compile an existing example, then experiment with it a bit (add and remove stuff to the example, just to learn and get ideas), but it seems like I need more than the libflac-dev package and the c-file on the above destination. I'm not very familiar with creating projects with dedicated IDEs, so far I only use a simple text editor and I want to keep it that way for a while, if possible. I found a similar thread by searching, but the answer was somewhat confusing to me, sorry for being an idiot. Thanks Johnny Rosenberg ___ flac-dev mailing list flac-dev@xiph.org http://lists.xiph.org/mailman/listinfo/flac-dev
