Tweet
Peace.
I hope you will excuse if my english is not perfet since I am from germany.
My usage of CD-Ripper:
I use the CD-Ripper in a rather strange way, opening one instance of the programme for each of my 7 optical drives (3 installed in my tower and 4 connected via USB 3.0 to S-ATA adapters externally).
Why? Because I am a mad man with more CDs than you can handle with standard solutions. That is the reason why I think my questions will not affect a lot of people. Nevertheless, here they are.
1)
Since I use an Intel i7 5820K which has 12 threads it is quite a shame to see that the CD-Ripper only uses one to four of them.
Each of the 7 instances of the programme starts by assigning the encoding of the first ripped track to cpu0, the second ripped track (if the first is still encoding) to cpu1, etc..
Worst case:
Assuming I started ripping the same CD (7x "Yes - Fragile" for example) in 7 identical drives at the same time they would therefore finish the first track after the same amount of time.
Then, they would all assign the encoding to cpu0, leading to 1 thread encoding 7 tracks simultaneously, while the other 11 threads would be idle at that time.
Would it be possible to integrate something like a thread-offset configurable for each instance of the CD-Ripper? For example instance 1 assigns encoding tasks to cpu0 - cpu11, instance 2 to cpu2 - cpu11, instance 3 to cpu4 - cpu11 etc.?
In my case with the 6 cores and 12 threads that would lead to a better load balance and the first few threads would not be overloaded whilst the other cores mostly chill.
Binding each instance of CD-Ripper to one specific thread would also be fine for me. My 6 cores run at 4,2GHz and therefore almost always finish encoding the previous track before the drive finishes ripping the next.
In my experience the programme becomes a little bit unstable if more than lets say 4 encoding tasks at a time are done by core0. It then needs more time than usual to detect newly inserted CDs and to obtain the related metadata.
Or could the instances surveille/communicate with each other and assign encoding tasks only to threads which are not already used to encode? That would be best.
2) My seven instances of CD-Ripper change their window positions under windows 10. Sometimes the first instance (drive "I" in my case) which used to be left in the task bar, suddenly is in last position at the right, where drive "O" used to be.
The amount of switched window positions increases with the number of ripped CDs, which sometimes puzzles me a bit (handling this many drives simultaneously is mad enough without them switching positions). Are the reasons for this behaviour known?
3) This one intermingles with question 1. Is it possible to create for example "special desktop links" which open a specific configuration of CD-Ripper?
Example: link 1 opens CD-Ripper scanning drive "I" and encoding with cpu0 - cpu11, link 2 scans drive "J" and uses cpu2 - cpu11 and so on.
PS: I do not want to sound unhappy or something like that. I LOVE CD-Ripper. I used to rip my CDs with Mediamonkey and only a single drive.
Today I rip more CDs in a day than I could possibly have ripped with Mediamonkey in a week. And the quality of the rips is equal/better.
The performance of the programme and its reliabillity are outstanding and yet not perfect.
In a perfect world I would have 7 desktop links of CD-Ripper. Each opening the programme scanning a specific drive, encoding with specific threads, not switching their window positions in windows even after 100 ripped CDs in a row.
PPS: If my problems are too special or not important enough, just let me know. I am already doing a fine job with the setup I use today.
I hope you will excuse if my english is not perfet since I am from germany.
My usage of CD-Ripper:
I use the CD-Ripper in a rather strange way, opening one instance of the programme for each of my 7 optical drives (3 installed in my tower and 4 connected via USB 3.0 to S-ATA adapters externally).
Why? Because I am a mad man with more CDs than you can handle with standard solutions. That is the reason why I think my questions will not affect a lot of people. Nevertheless, here they are.
1)
Since I use an Intel i7 5820K which has 12 threads it is quite a shame to see that the CD-Ripper only uses one to four of them.
Each of the 7 instances of the programme starts by assigning the encoding of the first ripped track to cpu0, the second ripped track (if the first is still encoding) to cpu1, etc..
Worst case:
Assuming I started ripping the same CD (7x "Yes - Fragile" for example) in 7 identical drives at the same time they would therefore finish the first track after the same amount of time.
Then, they would all assign the encoding to cpu0, leading to 1 thread encoding 7 tracks simultaneously, while the other 11 threads would be idle at that time.
Would it be possible to integrate something like a thread-offset configurable for each instance of the CD-Ripper? For example instance 1 assigns encoding tasks to cpu0 - cpu11, instance 2 to cpu2 - cpu11, instance 3 to cpu4 - cpu11 etc.?
In my case with the 6 cores and 12 threads that would lead to a better load balance and the first few threads would not be overloaded whilst the other cores mostly chill.
Binding each instance of CD-Ripper to one specific thread would also be fine for me. My 6 cores run at 4,2GHz and therefore almost always finish encoding the previous track before the drive finishes ripping the next.
In my experience the programme becomes a little bit unstable if more than lets say 4 encoding tasks at a time are done by core0. It then needs more time than usual to detect newly inserted CDs and to obtain the related metadata.
Or could the instances surveille/communicate with each other and assign encoding tasks only to threads which are not already used to encode? That would be best.
2) My seven instances of CD-Ripper change their window positions under windows 10. Sometimes the first instance (drive "I" in my case) which used to be left in the task bar, suddenly is in last position at the right, where drive "O" used to be.
The amount of switched window positions increases with the number of ripped CDs, which sometimes puzzles me a bit (handling this many drives simultaneously is mad enough without them switching positions). Are the reasons for this behaviour known?
3) This one intermingles with question 1. Is it possible to create for example "special desktop links" which open a specific configuration of CD-Ripper?
Example: link 1 opens CD-Ripper scanning drive "I" and encoding with cpu0 - cpu11, link 2 scans drive "J" and uses cpu2 - cpu11 and so on.
PS: I do not want to sound unhappy or something like that. I LOVE CD-Ripper. I used to rip my CDs with Mediamonkey and only a single drive.
Today I rip more CDs in a day than I could possibly have ripped with Mediamonkey in a week. And the quality of the rips is equal/better.
The performance of the programme and its reliabillity are outstanding and yet not perfect.
In a perfect world I would have 7 desktop links of CD-Ripper. Each opening the programme scanning a specific drive, encoding with specific threads, not switching their window positions in windows even after 100 ripped CDs in a row.
PPS: If my problems are too special or not important enough, just let me know. I am already doing a fine job with the setup I use today.
Comment