(In reply to comment #0)
> Also it doesn't store/restore volume until I switched the output device once
> in GNOME's sound setting.

This sounds like bug 55262.

Did you have some other problem? The bug title says "balance shifted right after restore", but you didn't explain that any further.

Created attachment 95606 [details]
before changing output device for once

before reboot

Created attachment 95607 [details]
before changing output device for once

after reboot

Created attachment 95608 [details]
after changing output device for once

before reboot

Created attachment 95609 [details]
after changing output device for once

after reboot

I thought the title was clear enough. Anyway, let the pictures speak.

Ok, so the word "balance" in the bug title referred to the overall volume, not left/right balance. I'll close this bug as a duplicate of bug 55262.

*** This bug has been marked as a duplicate of bug 55262 ***

Did you check all the attachments? I did mean left/right balance. The overall volume issue is just another thing that I thought might be related.

I doubt if it's a duplicate. Of course they are of similar nature (well volume restore), but the actual sympton seems to be quite different to me, both the overall AND the balance one.

In my case, to put it in text, the volume is stored but the balance shifted right (or I guess I can say, it (re)store only volume of the left channel), and it only (re)store something after I have changed the output device ONCE.

and by ONCE I mean after I deleted .config/pulse and rebooted

pulseaudio store the volunexpected in the *.tdb in .pulse directory

does pulseaudio store the volume, balance , fade and bass in these database ?

do pulseaudio have any tools to dump the database content instead of using tdbdump ?

(In reply to comment #8)
> Did you check all the attachments? I did mean left/right balance. The
> overall volume issue is just another thing that I thought might be related.

Oops, I did look at them all, but apparently I didn't pay enough attention to the balance slider (I guess I somehow made the conclusion after the first three pictures that the balance slider isn't changing).

> I doubt if it's a duplicate. Of course they are of similar nature (well
> volume restore), but the actual sympton seems to be quite different to me,
> both the overall AND the balance one.

Yes, this appears to be a separate bug, so reopening.

Can you reproduce this with these steps:

1) Disable autospawning:
        echo autospawn = no >> ~/.config/pulse/client.conf

2) Stop pulseaudio:
        killall pulseaudio

3) Remove the device volume database:
        rm ~/.config/pulse/*device-volumes*

4) Start pulseaudio in a terminal:
        pulseaudio -vvv

5) Do what you did when making those screeshots (switch the output once, set the volume).

6) Stop pulseaudio with Ctrl-C and save the log output.

7) Start pulseaudio again:
        pulseaudio -vvv

8) Check if the balance is wrong. If it is wrong, attach the logs from the two pulseaudio runs to this bug. If it's not wrong, then this is more mysterious.

(In reply to comment #10)
> pulseaudio store the volunexpected in the *.tdb in .pulse directory
> 
> does pulseaudio store the volume, balance , fade and bass in these database ?

Pulseaudio doesn't know anything about bass, but the device volume, balance and fade (these are all represented by a single per-channel volume structure) are stored in *-device-volumes.tdb.

> do pulseaudio have any tools to dump the database content instead of using
> tdbdump ?

No. Would be nice to have (or I'd actually like to store the data in plain text format).

(In reply to comment #11)
> (In reply to comment #8)
> > Did you check all the attachments? I did mean left/right balance. The
> > overall volume issue is just another thing that I thought might be related.
> 
> Oops, I did look at them all, but apparently I didn't pay enough attention
> to the balance slider (I guess I somehow made the conclusion after the first
> three pictures that the balance slider isn't changing).
> 
> > I doubt if it's a duplicate. Of course they are of similar nature (well
> > volume restore), but the actual sympton seems to be quite different to me,
> > both the overall AND the balance one.
> 
> Yes, this appears to be a separate bug, so reopening.
> 
> Can you reproduce this with these steps:
> 
> 1) Disable autospawning:
>         echo autospawn = no >> ~/.config/pulse/client.conf
> 
> 2) Stop pulseaudio:
>         killall pulseaudio
> 
> 3) Remove the device volume database:
>         rm ~/.config/pulse/*device-volumes*
> 
> 4) Start pulseaudio in a terminal:
>         pulseaudio -vvv
> 
> 5) Do what you did when making those screeshots (switch the output once, set
> the volume).
> 
> 6) Stop pulseaudio with Ctrl-C and save the log output.
> 
> 7) Start pulseaudio again:
>         pulseaudio -vvv
> 
> 8) Check if the balance is wrong. If it is wrong, attach the logs from the
> two pulseaudio runs to this bug. If it's not wrong, then this is more
> mysterious.

Well funny enough, it's not wrong.

Hmm suddenly the balance problem is gone. Though the volume still become zero after reboot unless I changed the output device.

I don't recall I did anything special, only that I deleted .config/pulse in console with root before I login in gdm, instead of deleting it in gnome.

Created attachment 95673 [details]
before reboot (volume adjusted)

Created attachment 95674 [details]
after reboot (volume is zero/muted)

Created attachment 95675 [details]
log of a seperate process

the process is started only if .config/pulse is deleted before that boot, may not be relevant

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/124.