More > JRiver Media Center 32 for Mac

Features Available?

<< < (2/3) > >>

EnglishTiger:

--- Quote from: soongsc on January 26, 2024, 05:15:58 am ---Is there any way to convert the polarity of individual files? If I can do this, then I won’t need the different polarities/Zones to do the job.

--- End quote ---

soongsc - can you please explain what you mean by "the polarity of individual files" as that is a term most MC Users would not use in conjunction with Media Files.

soongsc:

--- Quote from: EnglishTiger on January 26, 2024, 05:50:22 am ---soongsc - can you please explain what you mean by "the polarity of individual files" as that is a term most MC Users would not use in conjunction with Media Files.

--- End quote ---
It is basically like flipping the positive and negative connection at the speaker.  This can also be done in MC by setting this up in the DSP features for a zone.  Normally I have to set up two zones, one is 0 polarity, and the other is 180 polarity.  So every time when I listen to music, based on which company released the album, I will choose one for best playback experience, and usually the polarity is consistent within the same label like EMI might have 180, and RCA releases might have 0.  In order to avoid changing when I change albums played, it would be much more convenient to convert the 180 deg ones to 0, so when I create a playlist from multiple albums, there will not be a problem during playback.

A more obvious difference audibly is listening to a drum or percussion instruments, if the polarity is right, the drum will have a realistic punch, if the polarity is wrong, the drum will sound more muffled.  This of course depends on the audio system design, but in most cases, it is clearly audible.

Hope this is understandable.

EnglishTiger:
I'm guessing that it would be almost impossible for any Media Player to determine the "polarity" a track was set to use, or the polarity of the speakers attached to the player, so the only way of handling the problem would be to continue to manually assign them to different zones.

This link - https://wiki.jriver.com/index.php/Release_Notes will give you access to page/pages where every change, improvement and new feature that have been implemented in MC28, 29, 30, 31 and 32.

soongsc:
I was hoping to edit and convert the files.

bob:

--- Quote from: soongsc on January 26, 2024, 05:15:58 am ---Okay, I think I just noticed display of Chinese characters on the machine with MC29, my other one running MC21 is problematic, so I need to upgrade all my machines to MC29 first
...

--- End quote ---
The database had some fields previously stored in the Mac filesystem format of decomposed UTF-8 (the filesystem is the only place it's used on Macs). The Name field was synthesized from that for example.
Starting in MC 30.0.28 we determined the best approach was to convert everything in the database to precomposed UTF-8 (what everyone else uses). This makes the library compatible with linux as well. There is a one time function that runs on unconverted databases when they are first loaded to do that conversion. Every build of MC from then will check to see if the database has been converted and if not do this one time conversion.

This was added in MC30 and tweaked a few times. It's also available selectively as an added function under Library Tools->Clean File Properties.

I don't know for sure if that has anything to do with what you are seeing. It's also possible that other ripping tools, programs put decomposed utf-8 into your tags.

Navigation

[0] Message Index

[#] Next page

[*] Previous page