Linux-audio-user

linux-audio-user@lists.linuxaudio.org

2 participants
20662 discussions

Re: [linux-audio-user] CPU clock - beware - Solved for now?

by Matthew Barber

->I run almost the same setup, except I have a Asus A7N8X mobo with the Athlon 2500 overclocked to 2100Mhz @ 200Mhz fsb on Fedora with the CCRMA 2.4.26-1.ll kernel. The problem I always run into is that my setup will not run the low latency (ll) "athlon" kernel without locking up like you described. I have found that if I manually install the i686 kernel and ALSA from the CCRMA rpms, it will boot just fine and is very stable. In other words don't use apt-get to install the kernel and ALSA because it will always pick the Athlon versions. I haven't found any problems using apt-get after the kernel,alsa rpm installation, although when a new kernel comes out you do have to install it manually.<- Thanks to everyone who responded. My friend Kevin Ernste pointed me to one of many forum threads which talk about using "noapic nolapic" (hey, that's a good rhyme!) as kernel arguments for the nforce2 chipset. Like this one: http://www.linuxquestions.org/questions/showthread.php?s=&postid=1035056#po… I did that early this morning (actually, I just passed nolapic so far), and have not had a single problem at the normal clock speed, throwing everything I could at it. I had qjackctl open running alsaplayer into a simple jack-rack amplifier into freqtweak into a rezound record, while burning a CD, encoding an mp3, and playing with Celestia. Aside from Celestia and the mp3 encoder being fairly slow and the cpu temp reaching 41C during that episode, everything seems pretty solid. Thanks, Matt

21 years, 3 months

[linux-audio-user] Mellotron

by Emiliano Grilli

Hello guys, I'm writing here because I have a large sample of a Mellotron that I have not time to convert to pat or sf2. Inside there are the 3 instruments of a real Mellotron sampled note by note (I guess). The author of the samples, a friend of mine, when asked said that we can use it like we did with the rhodes one that he made (http://www.yeeking.net/index.php?location=Sound%20Fonts), making a GPL sound font or gus patch (he's asking only a mention of his website on the README) Since the sample is 23 Mb, and I don't have so much bandwidth, I can make it available on my home pc to the ones that are really interested. You can reach me via email or on irc on #agnula #lad or #hydrogen (nick "emillo") Ciao -- Emiliano Grilli Linux user #209089 http://www.emillo.net

21 years, 3 months

Re: [linux-audio-user] CPU clock - beware

by Matthew Barber

->Something just hit me while reading this post again, check the CPU speed jumper on your mobo. It needs to be at 133/166mhz for stock operation or 100mhz if your trying to run at 200mhz fsb (overclocking)<- Don't think so. I have set the clock to 200mhz in the BIOS. When I removed the clock jumper (which is how you set it to 100mhz) it won't go any higher even if you tell it to in the BIOS. The BIOS goes up in single mhz to 300. M

21 years, 3 months

Re: [linux-audio-user] Good Studio Hearphones

by philicorda

Hiya. I use Beyer DT150 headphones. They are solid, repairable, and have a better bass end than the old DT100. They are closed, but this can be a good thing as you get less spill from the headphones onto the mic than with open cans+less level is needed. You can blow them up, but it's pretty hard, and the drivers are not too expensive to replace. The old DT100 was a bit of an industry standard, and the DT150 looks likely to follow in it's footsteps.

21 years, 3 months

[linux-audio-user] CPU clock - beware

by Matthew Barber

This might not be an appropriate place to ask this question, but I've gotten help here before on a number of things... So I have an Athlon XP 2500+ and a DFI motherboard with the nvidia nforce2 chipset. I have run it for almost a year, and it has been rock solid under linux (not as much under Windows), red hat 9 and planet ccrma kernel/drivers/software -- 2.4.26-1.ll.rh90.ccrma. RME hdsp multiface, and um... 2x512MB Crucial unbuffered DDR400. Great, except - I have never been able to set the appropriate bus clock in the BIOS without linux becoming COMPLETELY unstable. If I set it to the published specs (166Mhz bus, x11 multiplier == 1.83Ghz), I usually can't even get through the linux boot process; if it makes it through the boot process, it will usually hang at the NVIDIA screen, or at the signin... if it makes it past that, I can sign in, do a few things in a shell, but then after about 2 minutes at most, the system freezes. And we're talking about a hard freeze - no ctl-alt-del, no ctl-alt-backspace, no response at all. Windows runs as fine as it ever has. The only way I can get linux to run stably is to underclock the system at 100Mhz, which puts my CPU clock at a wimpy 1.1Ghz. Setting the multiplier higher than 11 but maintaining the 100Mhz bus clock results in the same problem. I thought for a moment that the memory clock and the bus clock weren't syncing, so I set them in 1:1 ratio - linux still hates it at any frequency. You can lock AGP at 66Mhz, still nothing doing. This is a board and proc combo that has been renowned for mega overclocking - I shouldn't have to underclock it to have things run right. Windows runs fine so I'm wondering if it's not a problem in my kernel or distro rather than the bios or hardware. I have not as yet tried to boot another kernel, but I will tomorrow when my mind is clear (I just started trying to fix it today, and I'm weary). Any ideas about it, or about where I could read to fix it? Thanks, Matt

21 years, 3 months

Re: [linux-audio-user] CPU clock - beware - Solved for now?

by Matthew Barber

->I have the same mobo and processor. I couldn't find anywhere in the Award BIOS to over clock? Where iz? And I think mine only runs at 166mhz fsb. It has 333mhz DDR RAM.<- I could be wrong, but I don't think that with that memory you'd want to clock the system bus past 166 (since it's "DDR" -- "double data rate" RAM, the actual FSB clock is half of what it says it is)... and I think that after a certain point AMD started locking the multiplier capability in their athlons since people were overclocking them so much, so you can't set the multiplier in the BIOS (I've heard of some workarounds that require a CPU modification, but I don't know if they work now). If you got some faster memory, though, you could probably overclock the bus. Am I right about this? M

21 years, 3 months

Re: [linux-audio-user] CPU clock - beware - Solved for now?

by RickTaylor＠Speakeasy.Net

Malcom, > As always, YMMV. I was able to bump my SuperMicro FSB800 P4 servers from > 3.2GHz to 3.4GHz, which passed by hardcore 7-day 100% CPU burn-in test > (which does md5sums of /dev/random filled memory) without any trouble. > Since the box lives in CPU Paradise [a datacentre, with 65F, 55% RH, and > lots of forced-air circulation, and not a trace of dust], it's quite happy. You use this commercially? For "mission critical" stuff? ... This message has been brought to you in part by a grant from Columba.

21 years, 3 months

Re: [linux-audio-user] CPU clock - beware - Solved for now?

by Matthew Barber

->I do the same on my box, although on Fedora it is "acpi=off". I didn't notice that it affected stability, I just did it to adjust my IRQ's through the bios better.<- Absolutely. I have acpi=off as well - it was totally unstable before that; it was one of the first things I changed. I would disable acpi in the bios but I need it for windows to run... and I only need windows for sibelius. But now that I know you can run score in dosemu, it might be time to bite the bullet - btw did anyone who got it to work try printing a Score score from dosemu? Thanks, Matt

21 years, 3 months

[linux-audio-user] Re: Mellotron

by Juhana Sadeharju

>From: Neil Durant <lists(a)sphere3.co.uk> > >Incidentally, would there be any copyright issues sampling the Mellotron >tapes and redistributing? After all they're recordings like anything else. Maybe. Anyone knows email address of the guy who originally made Mellotrons? www.mellotron.com guy has purchased the original tape masters but that does not mean the sounds elsewhere are his property. In any case, we want record the sounds now, before the tapes goes too bad. The recorded sounds can then be placed to public domain in a few ten years. How long is the copyright on sound recordings made at 1960-1970? I know what books have but don't know what sounds have. Most importantly. I want to take a look at the sounds because we should recreate the sounds. That would save us all the trouble with copyright issues. Because the Mellotron sounds were unusual and good (though, Mamas&Papas had their own recordings) the recreation should have similar variances and defects from the perfect recordings. Existing sounds could be altered to have similar variances. After we have the Mellotron like sounds, then people could play with LinuxSampler, or have sequencers with a plugin which converts the sequences to Mellotron sequences. User would get feedback if the sequences cannot be played back with Mellotron. Long strings could automatically be modified such that they can be played with Mellotron. Things like that. Juhana

21 years, 3 months

RE: [linux-audio-user] Good Studio Hearphones

by Polashek, Matthew

AKG make 2 levels of resistance headphones. The ones that can be "hard to drive" are 600 ohm. They now make several versions that are around 55 ohm I think which is significantly less resistant resulting in needing a less powerful amplifier. Matthew Polashek > ---------- > From: Chris Pickett > Reply To: A list for linux audio users > Sent: Wednesday, July 21, 2004 10:22 AM > To: A list for linux audio users > Subject: Re: [linux-audio-user] Good Studio Hearphones > > stefano cardo wrote: > > Hi all!! > > > > I was looking for a good Studio hearphones... > > > > I saw the sennheiser HD 555... > > > > It costs 165 EUR more or less... > > > > did you ever tried it? > > > > or... > > > > can you suggest something good? > > AKG-271S, they sound and feel great, and your ears don't get tired. > Mine have a two year warranty, which is nice. AKG's have a reputation > for being hard to drive; that's been fixed in recent models. > > Cheers, > Chris > > > > **************************************************************************** This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. ****************************************************************************

21 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user