One more:
The convert.conf file is the basic rule file. It will be overwritten with every update/upgrade, which makes sense, since options of the used programs such as Sox and mplayer are changing once in a while.
BTW: The Squeezebox Server Package carries some binaries, such as Sox. This way they can guarantee that the rules work. However this can also mean that the SB server is running a different binary from your distro supplied binary.
You'll find the binaries here: /usr/share/squeezeboxserver/Bin/i386-linux
Now: To avoid that your settings are overwritten all the time, you put above 3-liner "ogg pcm," rule into a new file called /etc/squeezeboxserver/custom-convert.conf
instead of putting it into convert.conf.
That should be it.
Another one: It is obvious that you could even use brutefir to run convolution in a squeeze network following the same method. You just hang brutefir into any of the
pipes/rules.
Cheers
The convert.conf file is the basic rule file. It will be overwritten with every update/upgrade, which makes sense, since options of the used programs such as Sox and mplayer are changing once in a while.
BTW: The Squeezebox Server Package carries some binaries, such as Sox. This way they can guarantee that the rules work. However this can also mean that the SB server is running a different binary from your distro supplied binary.
You'll find the binaries here: /usr/share/squeezeboxserver/Bin/i386-linux
Now: To avoid that your settings are overwritten all the time, you put above 3-liner "ogg pcm," rule into a new file called /etc/squeezeboxserver/custom-convert.conf
instead of putting it into convert.conf.
That should be it.
Another one: It is obvious that you could even use brutefir to run convolution in a squeeze network following the same method. You just hang brutefir into any of the
pipes/rules.
Cheers
wondering if anyone a bit more experienced in programming audio stuff for linux might want to comment/support linux in this thread:
http://www.diyaudio.com/forums/mini...s-your-technical-questions-2.html#post2082350
col.
http://www.diyaudio.com/forums/mini...s-your-technical-questions-2.html#post2082350
col.
Interesting product at that price level. Still it has quite some limitations. The first two that hit my eye: samplerates x*48, slopes 24db only.
This little board you could perfectly combine with a Squeezbox Receiver ( even via I2S header) to build an active crossover - if 44,1 would be supported.
Thanks for this tutorial, I was struggling with these streams before, want to report here, that I managed to make it sing on XP PC via SqueezeSlave (ASIO) as well, used mplayer executable for windows (SMplayer package), followed these instructions: SlySoft Forum - View Single Post - ReClock chitchat
Since you are such a resourscefull bunch of audio fans here, I'd like to ask you about another very related topic, is there an easy way to make SqueezePlay (and possibly Squeeze Server web interface) show cover art pictures, which are regularly being updated on radio streams? What exactly is needed, a plugin, or config tweak, more?
Let's take example of this fine swiss radio (128k mp3): LOUNGE-RADIO.COM ...this is how we lounge !
Here is the frame which updates the cover art: http://www.lounge-radio.com/code/pushed_files/now.html
If you look at the source of this frame, the images are loaded in the following format:
Code:
<div id="covercontainer"><img src="playlist_sam342/az_B7202206_dub philosophy_alpha & omega.jpg" width="125" height="125" title="Album: dub philosophy by Artist: alpha & omega"></img></div>So, what we need is just take the non-changing address: "http://www.lounge-radio.com/code/pushed_files/"
and now add the filename of covert art from the currently played track located here under id="covercontainer", for our example:
+ "playlist_sam342/az_B7202206_dub philosophy_alpha & omega.jpg"
=> so these two combined result in the full path to cover art in full available
resolution (~300x300) for a given track:
"http://www.lounge-radio.com/code/pushed_files/playlist_sam342/az_B7202206_dub philosophy_alpha & omega.jpg"
An externally hosted image should be here but it was not working when we last tested it.
Any ideas? Thank you
Last edited:
FYI, Daniel Mack is actively working on USB audio 2.0 alsa drivers, the progress is fast.
[alsa-devel] usbaudio: Support for USB audio v2.0 devices
Jaroslav Kysela has introduced an alsa upgrade script, and asks for testing the script on various distributions
[alsa-devel] alsa-compile.sh - easy testing of latest ALSA code
[alsa-devel] usbaudio: Support for USB audio v2.0 devices
Jaroslav Kysela has introduced an alsa upgrade script, and asks for testing the script on various distributions
[alsa-devel] alsa-compile.sh - easy testing of latest ALSA code
Hi Al.
I do run Mint. And promote it since quite some time.
I still consider it the best entry into the Linux world. Even experienced Linux people can pretty well live and enjoy Linux Mint - I do.
However.
Mint neither comes with a default realtime kernel nor it is optimized for audio as you'll find it with e.g. Ubuntu Studio.
What it comes with are so called non-free codecs ( medibuntu repository), which you' won't find on a basic Ubuntu system.
Regarding audio and codecs you can consider Mint Plug'n play. ( as long as your soundcard is supported)
It is no rocket science though to install features and applications and a new kernel on a Linux system, if it is available in the so called repositories.
You can easily install all software by the Software manager resp. Package Manager if available in the respective repos.
It just takes some pretty simple configurations to get Mint up to speed for rt-kernel scheduling and performing equally good ( I think even better) then e.g. Ubuntu-Studio.
To take advantage of a realtime kernel you
a. have to install it first (package linux-rt)
b. you need to grant the users rt-permissions
c. you need to have an app supporting rt-scheduling.
E.g. Jack, ecasound, VLC, pulseaudio, brutefir, xmms perform best under realtime conditions. they all support a scheduling variant called SCHED_FIFO.
Cheers
Thx for the info.
I just had a quick look at it. It seems to be done for designers from a designer.
There is only very limited use ( if any use at all) for a normal user.
From that perspective I consider it pretty useless for us. That's really a pity.
Lets hope that this is just the beginning of this exercise and of getting Alsa upgrades disconnected from the kernels. Hope that one day Alsa gives the distro maintainers reasonable tools at hand to do the upgrades easily without messing with the system.
Nevertheless, things are going into the right direction. Let see how things are developing.
(BTW: Do you know Jaroslav?)
Cheers
Thanks for your reply
I am building a new rig soon and want to dual boot windows and Linux, Windows first, I'm still researching how to dual-boot. I had openSuse 11.0 on my last rig but it wouldn't play nice when I tried to install Vista Ultimate. I have the 64 bit Vista Ultimate and will use it on my next rig. I run 32 bit for now. Any tips on dual-boot?
I am building a new rig soon and want to dual boot windows and Linux, Windows first, I'm still researching how to dual-boot. I had openSuse 11.0 on my last rig but it wouldn't play nice when I tried to install Vista Ultimate. I have the 64 bit Vista Ultimate and will use it on my next rig. I run 32 bit for now. Any tips on dual-boot?
Yes, install windoze first, then Linux.
It is windoze who doesn't "play well" on Linux (or any other OS for that matter): when you install windoze, it does forcibly and silently overwrite your MBR, thus replacing any boot-loader (such as GRUB or LILO).
Linux installers are usually much nicer and smarter. If they finds another OS, they will automatically add them to the boot loader (or at least ask you whether you want to do so).
So, just install windoze first. Of course, you must MANUALLY partition you HDD, leaving enough room for Linux.
The simplest partition scheme is as follows:
partition - type - file system - usage
# 1 - primary - NTFS - windoze
# 2 - primary - ext4 - Linux / (root fs, system & software; 5 to 20 GB)
# 3 - primary - swap - Linux swap area (size ~ 2 x installed RAM)
# 4 - primary - ext4 - Linux /home (user data - all the rest)
create the first one from the windows installer, leaving enough empty (unpartitioned) space after it.
You'll create the other partitions from the Linux installer.
P.S.:
Unless you have repartitioned/reformatted your HDD during windoze installation, if you had a working Linux install which have "disappeared" after windoze installation, likely your Linux system is still there. It's just unreachable because of the MBR problem (no boot loader able to boot different OSs in the MBR).
In such a case, you need only to reinstall the boot loader (GRUB or LILO) into the MBR.
It is windoze who doesn't "play well" on Linux (or any other OS for that matter): when you install windoze, it does forcibly and silently overwrite your MBR, thus replacing any boot-loader (such as GRUB or LILO).
Linux installers are usually much nicer and smarter. If they finds another OS, they will automatically add them to the boot loader (or at least ask you whether you want to do so).
So, just install windoze first. Of course, you must MANUALLY partition you HDD, leaving enough room for Linux.
The simplest partition scheme is as follows:
partition - type - file system - usage
# 1 - primary - NTFS - windoze
# 2 - primary - ext4 - Linux / (root fs, system & software; 5 to 20 GB)
# 3 - primary - swap - Linux swap area (size ~ 2 x installed RAM)
# 4 - primary - ext4 - Linux /home (user data - all the rest)
create the first one from the windows installer, leaving enough empty (unpartitioned) space after it.
You'll create the other partitions from the Linux installer.
P.S.:
Unless you have repartitioned/reformatted your HDD during windoze installation, if you had a working Linux install which have "disappeared" after windoze installation, likely your Linux system is still there. It's just unreachable because of the MBR problem (no boot loader able to boot different OSs in the MBR).
In such a case, you need only to reinstall the boot loader (GRUB or LILO) into the MBR.
Last edited:
It's pretty easy.
The Mint installer will install a bootloader (grub2) during the installation.
Linux will replace the Windows MBR (master boot record).
By default Linux puts itself first in the boot order list. (You'll see the list during boot)
Once you've got Mint installed you reboot and login.
You need to install an application called "startupmanager" with the "Package Manager". (Enter the string "startupmanager" in the search field of the package manager)
Once installed you'll find the program in the Administration menu.
https://help.ubuntu.com/community/StartUpManager
Just open it, change the default OS and reboot.
To revert everything ( the entire Linux installation) back to Windows.
You need to boot Windows. Write from within Windows the Windows mbr ( there is a command for it - don't ask me how it's named). Then you clean the Linux partition.
Or you just restore a full backup of your Windows system.
!!!In any case do a full backup before you start the journey first!!!
I have not studied the script, nor do I know details of your arguments. I guess you should present your points on the mailing list so that Jaroslav can act upon them.
No I don't. I think he works in Brno where the development center of RedHat is located.
I tried that before. If you bringing things like that they don't even respond. Last time you were the only one responding to my question. These guys live in a different universe.
If you present specific suggestions, I am sure people will respond. Even here you did not present a single specific argument, I have no idea why you do not like the script.
I use ubuntu 9.10 server as my main audio source. All my CDs have been ripped to FLAC files and played through XBMC. The computer is connected to my LCD TV so playlists are easily managed from the couch. Gain is controlled through XBMC, which directly controls ALSA gain.
The nice thing about ubuntu server is the absence of pulseaudio and all other applications that aren't needed on a dedicated audio/video machine.
In my current setup I run a Sweet Peach GU50 valve amplifier with built-in USB DAC directly connected to the PC, but a modded hongkong DAC is in the works.
The nice thing about ubuntu server is the absence of pulseaudio and all other applications that aren't needed on a dedicated audio/video machine.
In my current setup I run a Sweet Peach GU50 valve amplifier with built-in USB DAC directly connected to the PC, but a modded hongkong DAC is in the works.
Hi Siqdiz,
By directly connected do you mean galvanicaly connected? c'est á dire with no isolation? Soundcheck and others have recommended isolation of USB signal to prevent excess noise from PC to pollute the DAC. I obeyed and use now a simple and cheap method based on microtransformers:
USB Isolator. « Circuits@Home
It works wonderfully.
Excuses if all the above is already known.
Regards,
M.
By directly connected do you mean galvanicaly connected? c'est á dire with no isolation? Soundcheck and others have recommended isolation of USB signal to prevent excess noise from PC to pollute the DAC. I obeyed and use now a simple and cheap method based on microtransformers:
USB Isolator. « Circuits@Home
It works wonderfully.
Excuses if all the above is already known.
Regards,
M.
Hi folks, it is nice to see someone started to use Linux as a music platform. Since I am new to this PC based forum and there are more than 100 something pages, I am wondering: is there anyone tried this approach (running Ubuntu) on second generation PS-3 (not the slim)? The Cell Processor to me is almost a "perfect" CPU to do FFT and other things utilizing its 8 available CPU's. I said "perfect" because FFT is a typical example when people start learning parallel programming. With the Cell floating point operation speed (it is faster than any PC, kin of close to super computers), it "should" be quite a good platform to do Linux Audio... Please see the following link:
https://help.ubuntu.com/community/PlayStation_3
https://help.ubuntu.com/community/PlayStation_3
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.