Hi there,
I was using this example to simply play a WAV file without having much clue
of audio:
https://www.freedesktop.org/software/pulseaudio/doxygen/pacat-simple_8c-example.html
I changed the sources to match (IMHO) my settings, i.e. channels=1 and
rate=48000.
I have two wavefiles, the first
Thanks Sean. I unloaded the suspend module but the plop is still there.
I don't really think it is HW related since the file plays just fine with
paplay and aplay.
On Fri, Aug 27, 2021 at 5:49 AM Sean Greenslade
wrote:
> On Thu, Aug 26, 2021 at 09:43:23PM +0200, mindfsck wrote:
>
>
> Why is the sample rate set to 48000?
>
No idea! The sourcing of the file is outside of my hands..
On Fri, Aug 27, 2021 at 4:14 PM guest271314 wrote:
> Why is the sample rate set to 48000?
>
> On Fri, Aug 27, 2021 at 6:40 AM mindfsck wrote:
>
>> Thanks Sean. I
you resample to 22050?
>
> On Fri, Aug 27, 2021 at 7:18 AM mindfsck wrote:
>
>> Why is the sample rate set to 48000?
>>>
>>
>> No idea! The sourcing of the file is outside of my hands..
>>
>> On Fri, Aug 27, 2021 at 4:14 PM guest271314
>> wrote:
>&g
lent samples at the
> beginning of the problematic wav files
>
I checked. The first 20ms are silent samples.
Attached is the file.
On Sun, Aug 29, 2021 at 12:06 AM Sean Greenslade
wrote:
> On Fri, Aug 27, 2021 at 04:57:07PM +0200, mindfsck wrote:
> > I seem to be to silly for it:
> > # sox
I repeat myself...use 'paplay' or 'aplay' and the result is fine.
On Sun, Aug 29, 2021 at 6:31 PM guest271314 wrote:
> How do we know what the expected result is?
>
> On Sun, Aug 29, 2021 at 5:01 AM mindfsck wrote:
>
>> you could try is making use of the bu
or use 'vlc' or use any Video/Audio playback you have on your machine.Sigh,
I may just reach out for alternative APIs instead of trying to convince
people that this might be a bug in the simple API you provide.
On Sun, Aug 29, 2021 at 6:53 PM mindfsck wrote:
> I repeat myself...use 'pap
:02:25PM +0200, mindfsck wrote:
> > or use 'vlc' or use any Video/Audio playback you have on your
> machine.Sigh,
> > I may just reach out for alternative APIs instead of trying to convince
> > people that this might be a bug in the simple API you provide.
>
> Apologies f