Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: Music Files Stored on NTFS

  • Subject: Re: Music Files Stored on NTFS
  • From: Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx>
  • Date: Sun, 20 Aug 2006 08:18:37 +0100
  • Newsgroups: alt.os.linux.suse
  • Organization: schestowitz.com / ISBE, Manchester University / ITS
  • References: <1156013140.770509.54820@i3g2000cwc.googlegroups.com>
  • Reply-to: newsgroups@xxxxxxxxxxxxxxx
  • User-agent: KNode/0.7.2
__/ [ nikoli ] on Saturday 19 August 2006 19:45 \__

> I have Suse 10.1 running KDE
> AMD x64 2500+ (2.2 GHz) w/ 512 RAM
> 
> I also have about 40 gigs of mp3s on an NTFS partition... seperate hard
> drive actually.
> 
> The issue I'm having is that amarok "skips" all the time. It seems like
> everytime I call up another process, the music skips. Starting Firefox
> can cause it to skip. Mostly it's larger tasks that cause the problem
> though... like installing software starting an online update. Not only
> is it a problem for amarok, but it seems like my entire system is over
> tasked during larger tasks.
> 
> For instance, if I start "software management" in YaST, my entire
> system will become basically useless until it's done reading the
> package informantion... about 2 or 3 minutes! My mouse skips all over.
> I can't switch between windows, no music plays, etc. CPU usage is at
> 100% the entire time.
> 
> So two questions:
> 1. Does playing music from an NTFS partition cause CPU overhead?


It should not. AmaroK (used to be) is buggy. I use version 1.2.x (old) and it
causes system-wide problems on occasions.


> 2. Is this just a limitof my hardware?


It sounds like there is something terribly wrong with the software, unless
there is some issue reading from disk (physical). It's very unlikely though
as it would not have affected the system in such a way. It would have just
spewed out an error and stop the reading operations. It's probable to assume
that some rotten process is running and causing the issues. Try doing some
profiling. System monitors, KSysGaurd, gnome-monitor etc. (CTRL+ESC if you
are using KDE... AmaroK seems to sugget so).

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index