Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - beatsystem

Pages: [1]
1
Hi,

I've been running the app happily every few months on Windows 10 64-bit, using the global scan on a huge collection with no problems. Full scan would run in 3-4 days, a day or so for the first half, 2-3 days for the second half.

However, running it last week, I found the first half of the scan has slowed down considerably, now taking 8-10 days just for the first half. Second half runs normally.

I looked in the log and saw these errors appearing every 10-15 seconds during the first scan:

2018-12-29 19:41:12   Process(decoder) is hang up
2018-12-29 19:41:12   CProcessLink::Read:445  [false] [995, The I/O operation has been aborted because of either a thread exit or an application request.  ]
2018-12-29 19:41:12   CAudioDecoder::Open:80  [-3] [995, The I/O operation has been aborted because of either a thread exit or an application request.  ]
2018-12-29 19:41:12   CAudioIndexer::PrepareIndex:682  [false] [995, The I/O operation has been aborted because of either a thread exit or an application request.  ]
2018-12-29 19:41:26   Process(decoder) is hang up

Previously I never saw anything in the log that gave me cause for concern.

Does anyone have any idea what is happening and how I can solve it? I'm not sure if it is the fault of the application, a windows update gone wrong or my network. It's baffling.

Any help would be much appreciated - thanks in advance!


2
Bugs / Re: Activation not working
« on: January 27, 2018, 23:04:48 »
Same problem now - What's up folks?

3
News / Re: Beta version 2.3.0
« on: March 29, 2017, 23:12:24 »
Really good job, indeed. Indexed and compared over 400,000 files in around 60 hours. Well done!

Looking forward to having the cache implemented, then I can run "new vs old" group searches super fast!

Congratulations and thank you! :)

4
Bugs / Re: hundreds of "decoder.exe"
« on: June 16, 2013, 18:29:22 »
Well, like I said, deselecting Quicktime decoder solved it.

A quick look in the log shows tons of things like this:

2013-06-11 00:00:19   Decoder hang up on file: U:\MP3\Ripped CDs\Glass, Philip\Philip Glass - 1973-5 - CD.jpg, decoder: Apple QuickTime Framework
2013-06-11 00:00:19   System error [2]: The system cannot find the file specified. 
2013-06-11 00:00:19   CProcessLink::InnerSend:174 failed [-100]

Note that I DO NOT have image comparison selected in Settings, but this explains the decoder problem, and also explains why I see decoders when running from the cache, as these files haven't been "cached", so the program will try to decode them every time and fail!!!

Despite the above I'm still having problems getting a complete scan with the latest version.I get continual crashes which seem to be out of memory. I have 4GB on a 32-bit machine, but some error causes the Similarity.exe to swell to 1.7+ GB.

Now I've solved the decoder problem, I'll start to see what can be done to solve the other problem.


5
Bugs / Re: hundreds of "decoder.exe"
« on: June 13, 2013, 17:44:04 »
An FYI update on the above, it seemed to be caused by Quicktime Decoder - disabling that in the settings stops the flood of "decoders".

6
Bugs / hundreds of "decoder.exe"
« on: June 11, 2013, 18:24:04 »
Hi,

Since the change in scanning programming, I'm continually left with hundreds of "decoder.exe" processes sitting on my machine taking up space (sometimes 1GB or more). If Similarity crashes (as it often does), they're stuck there - I have to use a taskkill command to get rid of them. Any idea why they're not closing automatically during the program's normal run?

Also when I restart, and scan using the cache, I get yet more decoder.exe files! Surely if Similarity is using the cache, it shouldn't be decoding anything?

This is all on premium version for audio only, I don't use it for pics.

Thanks,

Beats

7
News / Re: Version 1.8.0 released
« on: December 24, 2012, 10:28:57 »
I think you should add

"Warning! Incompatible with previous version cache, this version clears it."

again, folks!

Wish I'd known, I'd have made a backup.

Is there any way of running 1.7.1 and 1.8.0 on the same machine - one in standalone mode?

Pages: [1]