When I sync my iTunes library with iVolume it scans the files adding the note "Adjusted by iVolume", plus date and hour, in the "Comments" field of every song, and that's ok. I've understood that iPod needs to read this script in order to recognize the volume adjustments.
The problem is that every time I update iTunes Match (i.e. after adding new songs), almost half of the library loses the comment: the fields become empty! Note that in the info window of the songs, the volume adjustment is still there, but iPod won't be able to use it, I fear.
Furthermore, if I run iVolume once again, it just bypasses those tracks, as if they were ok, but the comments fileds remain empty. It is almost half of the albums, curiously the second half, from about L to Z, while the first half of the library remains ok with the "Adjusted by iVolume" comment visible.
What makes you believe that ipod needs to read this script. My understanding that this is a comments field and lets you know the date and time that ivolume made its change. The Comments field has no effect on the sound level.
iVolume is based on the Sound Check feature of iTunes. So you have to make sure to turn on Sound Check in the Playback Preferences of iTunes to get the desired effect. The same applies to any iPod, iPhone, iPad or Apple TV that you may have. Apple provides the Sound Check option on all its solutions.
evidently what I've read about iPod and the comment field was something old, when the volume used to be set by tags. What you say makes me think that vlume information is now written in the itunes library file, and not in the tags, is this correct?
As long as sound check is on, ivolume changes will work. With sound check off computer reverts to default. My understanding is that Ivolume changes will still be there when sound check is reactivated. This is borne out by the fact that tracks are bypassed when ivolume runs again.
beaTunes allows you to perform the ReplayGain analysis and adjust the standardized, track-specific id3 tags as well as the proprietary iTunNORM tags used by iTunes. It does not however, change the actual gain. This is left to your music player (in iTunes Sound Check needs to be enabled). "
"Once iVolume makes volume adjustments to your library, it also updates the comment data for the adjusted songs to ensure that these songs get updated on attached devices (such as an iPod or iPhone). Basically, iVolume "tricks" iTunes into detecting a change to a track by adding a comment to the song. iVolume only writes the comment if there is a volume adjustment made. iVolume uses the date and time in the comment, so that if there are any subsequent changes made in iVolume, it will trigger another update.
You can also choose to "Forget Analyzing Results" or "Remove iVolume Comments". This option will remove iVolume comments from your library. When choosing Remove iVolume Comments, a dialog box is displayed that says "Please note that the volume adjustments may not be synchronized automatically to the iPod if you remove the iVolume comments from the selected tracks". If you have already synchronized your devices, then they have already been updated. When selecting Forget Analyzing Results, the volume adjustments are reset in iVolume. If you've already performed adjustments on your iPod or iPhone, and you want your device to be reset to the default Sound Check volume adjustments, then select both of these options and synchronize your device. The removal of a comment will trigger a "difference" between the songs in your library and your iPod/iPhone, and those songs will then be updated."
- after a while all albums with titles from A to F have remained unchanged, the other albums have had their comment fields changed: someone blank, someone returned to the script with the date of the first time I ran iVolume. No change by single tracks, all by albums.
From the notes provided by Jim, would suggest that iVolume using this technique will at best be unreliable with iTunes Match - it is common for Song metadata to take some time to update across all devices.
Actually it doesn't work period. iTunes Match renders the iVolume adjustments useless. Test it with your ATV, or iOS devices and you'll hear that the settings do not take at all. As long as the music is streamed and not played from a downloaded file, the ivolume settings fail. I believe the Developer is aware of this. Check macupdate site for the reference.
iVolume calculates the volume perceived by the human ear for each song of your Apple Music (formerly known as iTunes) music collection. Therefor iVolume gets the most out of the approved Replay Gain algorithm and adjusts your songs accordingly.
iVolume calculates the volume perceived by the human ear for each song of your Apple Music (or iTunes) music collection. Therefor iVolume gets the most out of the approved Replay Gain algorithm and adjusts your songs accordingly.
The behaviour of the Start button can be configured in iVolume's preferences to fit your needs. If you're a long time customer and prefer the usage philosophy of iVolume 2 you can make iVolume 3 to behave just like that, besides other modes. By the way, you can also right click (or Control-click) the Start button to choose the action to perform ad hoc.
Please note that iVolume is based on the Sound Check feature of Apple. So you have to make sure to turn on Sound Check in the Playback Preferences of Music/iTunes to get the desired effect. The same applies to any iPhone, iPod, iPad or Apple TV that you may have. Apple provides the Sound Check option on all its solutions.
Sound Check is a feature that is intended to play back all of your songs at approximately the same volume. However, Sound Check is very limited out of the box and often fails to calculate the correct perceived volume of your songs. iVolume replaces the computed volume information of your songs so that Sound Check actually works perfectly.
With groups and their settings there are some nice advanced usage patterns possible. If you want to completely ignore all songs that were already processed by iVolume to speed up the processing even more, just do the following:
To begin adjusting your songs with the specified settings, click the Start button. In its default configuration, iVolume ensures that every song is adjusted to the perfect volume level. However, only those songs that are new to iVolume have to be analyzed, making the adjustment process as fast as possible.
Create groups to apply individual fine tuned settings to any specified subset of your songs. You can specify if the songs in a group should be automatically or manually adjusted or even completely ignored by the adjustment process.
iVolume's album modes permit to adjust albums as a whole while keeping the relative loudness of each album track intact as intended by the artist. Therefore iVolume calculates the average perceived loudness for all songs of an album and then applies the same adjustment value to each song. iVolume offers various options to precisely specify which songs should be combined to albums. When changing any of the album combining options, the track list immediately reflects the new settings.
Is there a brief discussion somewhere of the setting in iTunes: Volume: +/- 0dB? What is accomplished by using iVolume (or other) app to increase or decrease the dB settings of a single music file? Please don't reference some scientific treatise. There are plenty of those on the web.
The only reason I could imagine is if you use Sound Check to normalize volume. Changing the volume on specific files would ensure that they are louder, even after normalization. If you don't use Sound Check, and want volumes to be more consistent in a specific playlist, such as if you are DJing, then it might also be useful.
Being slow to grasp things, I have spent much of the weekend trying to figure out what the db setting on music files is, and how did they get there. Is it volume, is it loudness, can a files dB be manipulated? Maybe I have it, maybe not, anyways, I think an engineer or sound mixer assigns a specific loudness (hopefully amplification without a lot of clipping) to each digital music file when it is created. When I import the music file into iTunes, an Apple algorithm measures its loudness and assigns an average dB value for standard listening on a device. Usually all music files vary in loudness, so rather than constantly forcing me to adjust my device volume as I play my files, I can turn on Sound Check to average all dB settings into one loudness setting, saving me having to adjust the volume for each tune. iVolume allows me to manipulate a single music file, groups of music files, or a total library setting, and even beyond the Apple assigned dB setting. Please correct me if I have misunderstood.
As to why you may want to correct volume, it's because in some cases recordings are released at fairly low (read: normal volumes) and others are quite high (read: compressed), creating a disparity. The lower volume tracks are probably more "correct" than the higher volume tracks.
I thought about trying to switch to foobar2000 mobile but was a bit intimidated with having to ftp transfer tracks to my phone. Since m4a works I think I'm just going to convert the mp3 tracks...not an ideal solution but then I don't have to mess around with it anymore. Thanks for trying to help!
I transfer the files to my iphone using itunes on windows and connecting my phone, just as if I was going to use the apple music app. But once the files are on the phone, I can play them with foobar2000 mobile.
Just to follow up on the foobar2000 mobile side issue, I recalled that I had recently purchased TuneFusion (from the maker or dbpoweramp). It turns out that TuneFusion can automatically transfer songs/albums etc. to an iphone/ipad and other portable devices (including over WIFI). I played with it a bit last night. It has several interesting functions. The two best I've found for me are that (1) it can automatically convert lossless files to a lossy format upon transfer to my iphone, retaining all tag and art info, and (2) it has a "smart" sync function which will transfer only certain items based on user customization.
b1e95dc632