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 - hsei

Pages: 1 [2] 3 4 5
16
I would not recommend to work on such a large number of files in one pass. Even with 8 GB of RAM on a 64-bit system similarity tends to get unstable between 50k to 100k files. You can work on part of your data, move them to a master directory tree, and add more chunks of files in additional trees on later passes by using the group separation feature. Keep your cache between passes, this speeds up the process drastically. If you haven't lost your cache file, similarity should run much faster after a restart even though it seems to start from 0 again. On a 32 bit system your cache file might have exhausted the 2 GB RAM limit.
If you have enough RAM and CPU power, you can run several instances of similarity parallel with the /portable switch. By that you can use more than one cache (located in your program directory). You should use parallel copies of the similarity program (with a copy of the cache of previous runs) to make full use of this approach. If one instance crashes and is not restartable, you don't lose all of your work.
It's the general idea of modularity: Break down the problem to smaller ones which are easier to handle (divide and conquer).

17
Wishlist / Re: Tag Merging
« on: September 07, 2011, 15:45:15 »
I agree that fully automatic tag merging could be a dangerous feature, but a little more automatism would be helpful. Overwriting empty fields e.g. would be a reasonable choice. Another option could be to preselect direction of replacement between groups. When you have a large carefully edited collection and you just want to replace some songs with others of better quality, that would be helpful. A very desireable option in such cases would be the possibility to switch songs between two groups (directories) after merging/replacing tags. At the moment this is a rather tedious procedure (edit - select - copy all - apply - move). Especially the "move to directory"-feature could be enriched by a switch or replace option.
The topic here is very similar to thread "Automatically complete id3 tags"

18
Bugs / No sorting in some columns of result window
« on: June 01, 2011, 21:20:51 »
Sorting by clicking in header field works for file, content and tags column, but not for precise and all further.
(1.6.0 build 1200)

19
Bugs / Re: OpenCL on ATI HD 4870X2
« on: May 22, 2011, 00:47:16 »
Just follow the download link in "news - beta version 1.6.0". It has the latest build sometimes mentioned with an addendum in that thread, but often not.

20
Bugs / Re: OpenCL on ATI HD 4870X2
« on: May 15, 2011, 20:34:53 »
Build 1141 no longer shows "calculation error" in benchmark. But calculation time and CPU load is roughly the same with and without OpenCL enabled.

21
Bugs / Re: Apply in edit window loses changes
« on: May 01, 2011, 23:01:52 »
Where is build 1134 available? Similarity.beta.zip ist still build 1133.

22
Bugs / Apply in edit window loses changes
« on: April 28, 2011, 11:33:05 »
"Copy all" does not copy file name, which could be tolerable, but when you change anything in the file name field all previous changes in the tab region are lost after pressing "Apply".

23
News / Re: Beta version 1.6.0
« on: April 28, 2011, 11:18:20 »
In order to express it in different terms:
Offline activation is for those cases where the computer on which similarity in premium version has to be started has no connection (or not always) to the internet. As a side effect online control of subscription key is no longer done at every start of similarity, which seemed to me unnecessarily over-anxious.

24
Wishlist / Re: Good default settings
« on: April 22, 2011, 17:41:12 »
To make my recommendations more clear:
If I use the precise algorithm alone I get less than 1 % false pairs at a threshold of 70 %.
If I use the standard algorithm ("content") at a threshold of about 90 % additionally, I get a few percent additional pairs (with a "precise" rating close to 0), but with a higher false pair probability.
I don't trust in auto-marking, I just use it as "click-saver".

25
When you enabled OpenCL in the corresponding options tap you better start a benchmark run first. I got an "calculation error" (AMD/ATI 5570) and most comparison results gave false 100% indication.
Only way out in this case: Switch off OpenCL (CUDA).

26
In %APPDATA%\Similarity\logs or in \logs subfolder of Similarity folder (with exe) when started with /portable switch.
Problem may happen too if Similarity is started twice inadvertantly. If you have a large cache it takes some time until Program shows up. In the meantime you may unpatiently have tried to started it again.

27
Wishlist / Re: Good default settings
« on: April 07, 2011, 21:16:56 »
I agree partially:
A "precise threshold" of 85-90% is reasonable. But I additionally use a standard threshold of 80% (they are combined by OR), since sometimes the precise algorithm completely misses similarity pairs. Of course theses "standard" candidates have to be examined by listening since the standard algorithm is much less reliable, but rather often I found "true" similar pairs.

28
Bugs / Re: Scan results not remembered
« on: April 02, 2011, 18:53:30 »
Program is inconsistent in remembering previous data after new start: Comparison results are discarded, analysis data are kept. The latter may be sometimes favorable but it may clutter the analysis window in other cases. The only way I found to get rid of them is to start an analysis run and immediately stop it thereafter.
I'd like to have a reset button for analysis data similar to that for the cache.
The same applies to ignore data (files marked to be ignored). A reset button for that is a much cleaner way than to delete an ignore file somewhere in Microsoft's program data jungle.

29
Cache indication of 0 after comparison start seems to be a bug: After restart (before comparison run) former cache size is shown again. Comparison speed is also a hint that cache is used: The fast speed at the beginning means that signatures from cache are used, slower speed appears when signature is not in cache and has to be calculated from audio source.
I agree that missing files should be misregarded. A similar annoying problem: If you mark a couple of files and try to execute an action on these (e.g. delete), execution is refused if one file does no longer exist. You have to reduce the marking range or even act on single files until you have the noexisting file no longer in your selection. If you have another nonexisting file in the rest of your selection - same procedure again.

30
Wishlist / Re: Consider different releases
« on: March 28, 2011, 17:58:38 »
I've been using Jaikoz, Picard and Classical MB Tagger for years but they give me only results for 10% of newly introduced material (off mainstream). With similarity I get a reasonable hint whether I have that song already in my collection and especially if it's of better quality.
Without clean definitions you will only get arbitrary statements, no matter how the wind blows  :-\

Pages: 1 [2] 3 4 5