Skip to main content
Topic: Running Foobar in Linux (Read 499696 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Running Foobar in Linux

Reply #500
Thanks for trying to help out! I didn't have time to search for this myself, but maybe you could direct me closer to a solution with the following details you asked:
The sound card is an onboard card (I guess) on the motherboard of a Sony Vaio laptop.
The Wine cfg shows winealsa.drv as the selected driver.
KDE indeed shows Phonon VLC as the backend.
VLC, in turn, has chosen PulseAudio sound server as the output device (I attach screenshots of VLC, so that I won't confuse you):

Any help/brainstorming would be welcome, though you have already helped quite a lot.:)

Re: Running Foobar in Linux

Reply #501
VLC, in turn, has chosen PulseAudio sound server as the output device (I attach screenshots of VLC, so that I won't confuse you):

I think that means WINE should be choosing a PulseAudio driver, not the ALSA one.  Not sure why it chose the wrong driver, or how to force it to use another.   It used to be a selection in winecfg, but no longer, unless you have a really old version of WINE.  Afraid I can't help much with that problem.

Re: Running Foobar in Linux

Reply #502
No, no, you really helped me a lot to narrow it down, thank you for giving me some of your time.
I will post again here when I find a proper solution about the PulseAudio in Wine problem. For now, I tried different versions of Wine (1.62 (from the Neon repositories), 2.05 and 3.0) and none let me choose the "Selected driver". I read in a few places that Wine has (/had?) a notoriously bad relationship with Pulseaudio. That's all I got so far.
This problem needs some real digging and I hardly have any time left for this these days.

Re: Running Foobar in Linux

Reply #503
No, no, you really helped me a lot to narrow it down, thank you for giving me some of your time.
I will post again here when I find a proper solution about the PulseAudio in Wine problem. For now, I tried different versions of Wine (1.62 (from the Neon repositories), 2.05 and 3.0) and none let me choose the "Selected driver". I read in a few places that Wine has (/had?) a notoriously bad relationship with Pulseaudio. That's all I got so far.
This problem needs some real digging and I hardly have any time left for this these days.

You can use winetrick to chance from alsa to pulseaudio.

Just run the following:

Code: [Select]
sudo apt-get install cabextract
wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks
chmod +x winetricks
sh winetricks sound=pulse



Re: Running Foobar in Linux

Reply #504
You can use winetrick to chance from alsa to pulseaudio.
Thank you for this suggestion! I had a long session yesterday, finally, and I concluded that I am probably blocking myself on this, but I don't know how.
So, first I tried winetricks, and it didn't allow me to switch to pulse. Then I realized that even if it did, it would have switched it in only the default Wine configuration, while I needed to do this to the configuration ("prefix"?) made by Playonlinux for Foobar (note: I opted for Playonlinux on top of Wine to avoid having to configure Wine myself everytime something changes with compatibility and whatnot for Foobar in the future). I tried changing the driver manually with regedit, in both configurations, but no luck. The default one seemed to change, but the audio behavior remained the same: only one audio stream at a time.
Then I deleted everything and started over, only with Wine, no Playonlinux. Again it defaulted to the Alsa driver. (at that point I didn't try adding Winetricks; I should have tried that then). Removed everything again, started with Playonlinux this time, same thing: alsa.
I did a circle that took me like 3-4 hours, and I got frustrated. This problem will just have to wait for someone who has dealt with exactly this problem, and either posts here, or I find it somewhere on the internet...

Re: Running Foobar in Linux

Reply #505
That is very strange.

In a new profile with any new version of wine the default driver is always pulse.

Even forcing alsa in wine the pulseaudio daemon takes control of the stream and system pulseaudio see it like "ALSA plugin [wine-preloader]" and of course can be mixed with any other stream.

You can try to start over.

Uninstall all wine software with synaptic (playonlinux too), add the wine-hq repo

Code: [Select]
sudo dpkg --add-architecture i386
wget -nc https://dl.winehq.org/wine-builds/Release.key
sudo apt-key add Release.key
sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/
sudo apt-get update
sudo apt-get install --install-recommends winehq-devel

Now delete the wine profiles of your home and edit .bashrc with the following as the last line of code:

Code: [Select]
export WINEARCH=win32

Open a new terminal and run:

Code: [Select]
winecfg

to create a fresh .wine profile in your home.

If you want to create multiples profiles you can use

Code: [Select]
WINEPREFIX=~/.mywineprofile winecfg

to make new profiles and:

Code: [Select]
WINEPREFIX=~/.mywineprofile winetricks

to launch winetricks in any profile.

I personally run away from playonlinux as far as I can  ;)

If doesn't work maybe the problem is in the system audio configuration and not in wine.











Re: Running Foobar in Linux

Reply #506
Thank you! I'll try this when I find some time to deal with this again carefully and focused. Last night's session left me disheartened. I will get back with the results when I do.

 

Re: Running Foobar in Linux

Reply #507
Thank you! I'll try this when I find some time to deal with this again carefully and focused. Last night's session left me disheartened. I will get back with the results when I do.

Clear the mind is always a good idea when we find a problem.

Good luck.

Re: Running Foobar in Linux

Reply #508
This time it was successful, big heartfelt thanks paregistrase!
Can I ask what the line export WINEARCH=win32 in .bashrc is for? Also, now that I found you :), would you also know what to do about the stuttering when a new file starts playing (this forum has outdated info on this)?
Conclusions: it does seem to make sense to get Wine from their own repositories. KDE Neon (Ubuntu-based) are still using 1.62, which, as I read somewhere, is before the Wine people changed something to make the audio driver default to pulse.
Having also used new versions of Wine, but installed through Playonlinux on top of v1.62 [edit: woopsy, I may have been ignorant enough not to switch versions from the default one,  :-[ ], I too would recommend getting just Wine without Playonlinux, if you can't really navigate yourself in what each one does to which configuration. For some reason, alsa was stuck as the driver even for the new Wine versions.

Re: Running Foobar in Linux

Reply #509
This time it was successful, big heartfelt thanks paregistrase!
Can I ask what the line export WINEARCH=win32 in .bashrc is for? Also, now that I found you :), would you also know what to do about the stuttering when a new file starts playing (this forum has outdated info on this)?
Conclusions: it does seem to make sense to get Wine from their own repositories. KDE Neon (Ubuntu-based) are still using 1.62, which, as I read somewhere, is before the Wine people changed something to make the audio driver default to pulse.
Having also used new versions of Wine, but installed through Playonlinux on top of v1.62 [edit: woopsy, I may have been ignorant enough not to switch versions from the default one,  :-[ ], I too would recommend getting just Wine without Playonlinux, if you can't really navigate yourself in what each one does to which configuration. For some reason, alsa was stuck as the driver even for the new Wine versions.

You're welcome.

the line in .bashrc is for ensure that when you launch wine or winetrick from command line always get this variable without having to type it every time. If you remenber to type it every time that want to launch a wine32 application and make sure that your .desktop files have it too you can get rid of it without major problem.

About stuttering I don't know what to say you, I don't have this issue. Maybe any plugin automatic action when the song start to play?  I have seen small interruption in playing if I write tags in large files or perform intensive actions like calculate replaygain while playing. I try to avoid any automatic writing like write the stadistic or the lyrics in the file while playing and the "little pauses" never happen again.

About the version is always good idea to take the newest version and even better if it is from the original source
 




Re: Running Foobar in Linux

Reply #510
the line in .bashrc is for ensure that when you launch wine or winetrick from command line always get this variable without having to type it every time. If you remenber to type it every time that want to launch a wine32 application and make sure that your .desktop files have it too you can get rid of it without major problem.
Thank you for explaining this too and for the tips!
btw, I realized I must have changed wine versions through Playonlinux for Foobar, so my quasi-theory above could be kind of true. Anyway, it doesn't matter.

Re: Running Foobar in Linux

Reply #511
the line in .bashrc is for ensure that when you launch wine or winetrick from command line always get this variable without having to type it every time. If you remenber to type it every time that want to launch a wine32 application and make sure that your .desktop files have it too you can get rid of it without major problem.
Thank you for explaining this too and for the tips!
btw, I realized I must have changed wine versions through Playonlinux for Foobar, so my quasi-theory above could be kind of true. Anyway, it doesn't matter.

Yes, playonlinux let you change the wine version of any profile that create but the playonlinux version not always performs the same that the build from wine-hq and his winetricks version is a little "special" too.

But you don't need playonlinux to have diferent version of wine in your system.

There is a package that create links in the path for the wine version, it's called winehq-(stable, devel or staging). If you don't install it you can have the 3 version instaled. The only downside is that you need to type every time the complete path to the wine executable that you want to run.

The diferent versions installs in /opt/wine-(stable, devel or staging)

so you can install all and call it with the complete path /opt/wine-staging/bin/wine yourprogram.exe.

Or install only one of the winehq-(stable, devel or staging) to create simlink in the path to call it just typing wine and call the rest for the complete path.

Or make yourself links to the diferent executables and put them in any path (/usr/bin,~/.local/bin/,etc) folder...

And combine it with diferent profiles and wine32 or 64 as you want

Wine is very versatile




Re: Running Foobar in Linux

Reply #512
fb and wine usually work quite well together, but looking at the new mac port of foobar2000 makes me feel confident that a native linux version is not utopic anymore ;)


 
SimplePortal 1.0.0 RC1 © 2008-2018