Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JimH]

A couple of people reported the problem in the 9.1.245 thread.  Both were using Firewire drives.

We have tried to duplicate this problem (not with Firewire until today) without success.  

If you have also had the problem, are you using a Firewire hard drive?  If not, what kind of drive do you use?

[escaflo]

I encountered this problem just today. Tried to analyse 1600 songs. Crashes around 1100+.

I am using a Maxtor 80Gb 7200rpm IDE hdd.

Have been encountering this problem quite often.

Even after I just change my system from AMD AthlonXP 1700+ to Pentium 4 2.26Ghz.

[StFeder]

I have the same problem with audio analysis since I first used Audio Analysis (MJ 8.0.x).
It's diffrent, how many files are beeing analysed (seems to have neither a relative nor a absolut number), and it crashes somewhere between 100 and 900 files. I always thougt it could be something with my system (I'm a bit happy zo be not alone  ), but I re-installed it twice in this period.

I have two 80 GB IDE UDMA 2/4 Drives (Seagate ST380020A, 2MB Buffer; IBM ICL35L090AVV207-0, 1821kb Buffer). One was and one is containing all my mediafiles and with both I have the audio analysis crash bug. I'd like to, but I am using NO FireWire devices.
Hope this helps.


---
Media Center Registered 9.1.243 -- C:\Programme\Audio\JRiver Media Center\

Microsoft Windows XP  Workstation 5.1 Service Pack 1 (Build 2600)
Intel Pentium 4 1799 MHz MMX / Memory: Total - 261 MB, Free - 36 MB

Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1106 (xpsp1.020828-1920) / Shell32.dll: 6.00.2800.1106 (xpsp1.020828-1920) / wnaspi32.dll: 4.60 (1021) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1999 Adaptec, Inc. / Aspi32.sys: 4.60 (1021)

Ripping /   Drive X:   Copy mode:ModeBurstBigBuffer   CD Type:Auto   Read speed:Max
 Drive Y:   Copy mode:ModeBurstBigBuffer   CD Type:Auto   Read speed:Max
 Drive Z:   Copy mode:ModeBurstBigBuffer   CD Type:Auto   Read speed:Max
 Digital playback: Yes /  Use YADB: No /  Get cover art: Yes /  Calc replay gain: Yes /  Copy volume: 32767
 Eject after ripping: Yes /  Play sound after ripping: No  

Burning /  Drive Y: SONY     CD-RW CRX1611      Addr: 1:0:0  Speed:16  MaxSpeed:16  BurnProof:Yes
 Test mode: No /  Eject after writing: Yes /  Direct decoding: Yes /  Write CD-Text: Yes
 Use playback settings: No /  Normalization: None

[LonWar]

I am not sure if this is related, But I used to have this problem, then I figured out it was my Screensaver. When I disabled that I had no more problems.

[msc3]

I have experienced this problem as well. I have a Maxtor ATA/133 "C" drive on which MC resides and an IBM 60GB ATA/100 drive on which my mp3s reside.

[Mysticeti]

Does the problem only occur with MP3 files?

Maybe it has something to do with what app encoded the files being analyzed?

[StFeder]

I always had the screensaver disabled. Also no energy save options are enabled (like shut down my harddisk after x Minutes or Standby Monitor after x minutes). Screensafer cannot be the only reason.

[Ingo]

I had this problem since aa came up....
I even had this on two different computers.

one beeing a W2k German system which was more or less continuously updated via windowsupdate.com.
Hardware:
Abit KT133-Raid (not using raid mode)
Duron 700
Changing amount of RAM: 128-224MB
16GB IBM harddisk
Matrox mystique, Ati Mach64 or Ati Rage II+ graphics card
SB128
Different CDRoms
Sometimes a Symbios SCSI controller was installed
RTL8139 or SMC netcard

The other was more or less staying the same (apart from windowsupdate.com):
Media Center Registered 9.1.246 -- C:\Programme\Media Center\

Microsoft Windows XP  Workstation 5.1 Service Pack 1 (Build 2600)
AMD Athlon 1200 MHz MMX / Memory: Total - 654 MB, Free - 176 MB

Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1226 / Shell32.dll: 6.00.2800.1233 (xpsp2.030604-1804) / wnaspi32.dll: N/A
Ripping /   Drive G:   Copy mode:ModeBurstBigBuffer   CD Type:Auto   Read speed:Max
 Drive I:   Copy mode:ModeBurstBigBuffer   CD Type:Auto   Read speed:Max
 Digital playback: Yes /  Use YADB: Yes /  Get cover art: Yes /  Calc replay gain: Yes /  Copy volume: 32767
 Eject after ripping: Yes /  Play sound after ripping: Yes  Soundfile:   C:\WINDOWS\Media\ding.wav

Burning /  Drive G: RICOH    DVD+RW MP5120      Addr: 1:0:0  Speed:12  MaxSpeed:12  BurnProof:No
 Test mode: No /  Eject after writing: Yes /  Direct decoding: No /  Write CD-Text: Yes
 Use playback settings: No /  Normalization: None


Ingo

[gpvillamil]

I've been having this problem pretty much constantly - I reported it before. I use an external Firewire drive. However, my latest audio analysis run seems to be doing OK, I've processed 1500 of 2600 songs without problems so far.

Perhaps the problem occurs with very large file lists? Maybe the reason why it was reported by people with FW drives is that these are people with very large MP3 collections?

[BlueGlow]

I've consistently had problems trying to analyze my 7000+ songs with many, many builds since v8. Sometimes MC just exits with no message, recently I get an "Errors on the last few songs" message. I just started a new attempt last night and it completed over 3000 songs before the error message. I exited MC and started at the same point and no errors, 2-300 songs later the same message popped up again. I will launch a new attempt again tonight and see how far it is by morning.

[Shelly]

I've consistently had problems trying to analyze my 7000+ songs with many, many builds since v8. Sometimes MC just exits with no message, recently I get an "Errors on the last few songs" message. I just started a new attempt last night and it completed over 3000 songs before the error message. I exited MC and started at the same point and no errors, 2-300 songs later the same message popped up again. I will launch a new attempt again tonight and see how far it is by morning.

Exactly the same experience here.  I might be able to analyze 200 files before it errors out or as little as 20 files.  Once the error is received, analysis cannot be completed on any files.  Closing and restarting MC allows it to analyze the same files that errored out before closing.  

I'm not using a firewire drive.