Last post by VEG -
I believe we should vote for fixing of this issue if we want to have it fixed: https://issuetracker.google.com/issues/37054258 Just add a star. More stars, more chances that the issue will be visible for somebody who can decide to fix it in Android.
On my laptop, I convert to the Apple Lossless encoder and they become .M4A files from .flac. I assumed .m4a is apple lossless(codex?).
.m4a means it is audio in an MP4 container. MP4 can contain a lot of things, but is the typical choice of file format both for ALAC audio and for AAC audio. Merely looking at the .m4a in the file explorer does not tell you whether it is ALAC or AAC in it, though file size could give you a hint.
If possible I wanted the ability to add label to every panel, not just splitters. Let me illustrate this with my `awesome` MS Paint skills: Spoiler (click to show/hide)
Other possible implementations: `Label` (`Panel Type`) or even only `Label` without panel type.
Unfortunately, I'm bound by the current design of the panel API. All of the data for a panel is managed by its parent panel, and I can't see trying to augment that data in Columns UI working.
So, a custom name would have to be stored in one of the current options, and hence the idea of using the custom title option. The custom title option isn't limited to splitters, it depends on the parent splitter panel supporting it for its child panels. But if Panel Stack Splitter doesn't support it, that probably doesn't make much difference for you anyway.
Last post by dshot -
Before I begin: I have foobar v22.214.171.124 as a portable install on an external HD. I have a laptop that runs windows 07 and foobar runs, and more importantly, converts .flac to .m4a files flawlessly, and simply. It has also been customized to my liking and componets etc.
I recently received a PC from a deceased relative that's running windows 10. It runs and plays foobar that is on the HD fine. But doesn't want to convert .flac>.m4a. (as I got an error msg.(code 2 (0x00000002) like the one at the bottom of this post.)
I ejected my HD and downloaded v1.4 to the Windows 10 PC(before I installed the encoder pack, mind you) I received the following message to locate qaac.exe, qaac64.exe, refalac,exe or refalac64.exe. which I have no idea how to locate or what it means.
Then I installed the encoder pack and I receive a new error message: (Same as I got on v126.96.36.199 on the HD mentioned above):
" An error occurred while writing to file (The encoder has terminated prematurely with code 2 (0x00000002); please re-check parameters) : Additional information: Encoder stream format: 44100Hz / 2ch / 16bps Command line: "C:\Users\Michael\Desktop\foobar2000\encoders\qaac.exe" --ignorelength -s --no-optimize --alac -o Conversion failed: The encoder has terminated prematurely with code 2 (0x00000002); please re-check parameters."
I've spent hours this sat. morning trying to make it work and am getting more confused as I search.
On my laptop, I convert to the Apple Lossless encoder and they become .M4A files from .flac. I assumed .m4a is apple lossless(codex?). However in my search this morning there are different Apple Lossless formats I guess. AAC + Apple Lossless (qaac) and Apple Lossless (refalac). I am choosing Apple Lossless in foobar when I convert on the laptop, so I guess it's refalac, but am not sure.
I'm new to forums, and as I'm sure you can tell not too tech savvy. I know the answer is convert using my laptop, but I want to be able to do it on both devices from the HD, really. But since I can't with either version on the windows 10 PC, and can't find acceptable answers in my searches, I joined a forum in hopes it'll help. Thanks for your patience. dshot
The glitch is very easy to ear (at least with decent headphones). I first noticed it with 128 kbps Opus, and still ear it the same after re-encoding at 256 kbps. The bitrate doesn't seem to have anything to do with it.
It may depend on how the encoding and/or decoding is done. What happens if you manually convert your files to 48 kHz before encoding? What may be happening here is that if the original is 44.1 kHz and gets resampled for encoding, but gets "stitched back" at 48 kHz, then there may be a fractional sample extra/missing.
Last post by j7n -
I can't hear any significant glitch with this sample. The click is blends in with the nasty noise. Strangely, upsampling with SoX makes the click slightly bigger compared to a direct encode, letting opusenc.exe do the upsampling. I can hear it in the 48k sourced encode, as a short hiss impulse on the right side, but it still seems acceptable for a lossy encode, and not noticable without focusing on the position. No bass content in this sample either.
Perhaps the player isn't fully gapless?
I will delete these attachments soon as they don't show anything special.
A better encoder, which is aware of the contents of the previous track, would be nice to have.