04-04-2006, 04:10 PM
CQC uses J.River purely as a ripping and metadata retrieval system. You can rip your CDs and get the metadata, using J.River, and then you can export that informationto CQC which imports it. So CQC has no control over J.River as a player or anything of that nature. We are just getting data from it.
You can continue to use J.River to do whatever you want, and it won't affect CQC's access to the ripped media files or anything (unless you try to update a file while some other player has it open, in which case JR wouldn't be able to write to the file.) But we cannot tell JR to do anything or access any of its functionality related to interfacing to portable devices or anything like that.
You can continue to use J.River to do whatever you want, and it won't affect CQC's access to the ripped media files or anything (unless you try to update a file while some other player has it open, in which case JR wouldn't be able to write to the file.) But we cannot tell JR to do anything or access any of its functionality related to interfacing to portable devices or anything like that.
Dean Roddey
Explorans limites defectum
Explorans limites defectum