Won't import at 320 bit rate?

HI
I'm running the latest ITunes software on windows xp home and want to import audio cd's at 320 bit rate. I select this option in the custom settings and it appears to stick, but when I check the song's after importing has finished they have imported at 128 bit rate.
I've tried deleting the 2 itunes.pref files as stated else where but no luck..
Can somme one pleeease help me?

Hi Guys
Thanks for the info, I gave it a go and changed the screen resolution and the weird thing is that I could already see the apply buttton on the original screen resolution BUT when I changed the resolution it worked!!
I don't see the logic in how window's screen resolution effects the importing bit rate of Itunes?
I suppose that's what you get when yoou throw apples at windows, Broken glass!
Thanks for the help

Similar Messages

Will itunes move up to 320 bit-rate downloads?

i am a bit of an audiofile and was wondering will itunes move up to 320 bit-rate downloads?

We are just fellow users on here - until if/when Apple announce something nobody on here will know.

Transferring CDs at 320 bit rate

I'm transferring several CDs to iTunes (7.5). For a few of the classical ones, I've set iTunes for AAC and custom (320 kbps and 48 kHz) and Variable Bit Rate unchecked. I presumed this would produce the highest quality (?). After transferring, most of the songs are listed at less than 320 (i.e. 311, 309, 298, etc).
1. Why is this?
2. Should I be using different settings?
Thanks for any suggestions. HNick

I think you will find that at certain bit rates with the AAC encoder, the variable setting is a default setting and cannot be changed.
To see what I mean, go to your import preferences and select the 320kbps setting.
Now put a check mark in the variable box and the kbps setting will immediately change to 128.
Now try to select 320kbps from that list and you will see it's 'greyed out' and cannot be selected.
It's one of the reasons I am still using the mp3 encoder.

Importing Problems. Bit Rate Variations

I've customised my CD importing bit rate to 192kbps. However, when importing songs they can be anything from 180-195kbps when stored. This started all of a sudden - I have 4000 songs at 192kbps. Any ideas?

I just noticed in that after updating to 7.6 that if you're attempting to import discs to AAC using VBR that it shows up as a constant bit rate now. It seems to be the flip problem that constant bit rate users had with 7.5. I'm kind of annoyed by this because I'd been importing my entire library (A thru S) using the VBR settings and now everything seems to be coming in flat when I start ripping. Or are they VBR and just showing as constant? Either way, I hope it gets fixed. I hate having 3/4 of my files showing VBR and the rest CBR.

Logic X won't import a 64 bit .wav file. Why?

I'm trying to import .wav files created with FF Tools into Logic for some editing, but it says the audio file is "in a 64 bit format and cannot be used". Why is this? I thought Logic X was 64-bit friendly?
Any help on this would be greatly appreciated.
Thanks

There is also no point in using 64 bit audio files. Even 32 bit floating point is already overkill. The best choice for recording is 24 bit, for internal processing 64 bit floating point does make sense, but not for storing.
In any case, your mac comes with a very capable audio file format converting utility that can be used from the command line and reads/writes practically any audio file format you will encounter, including 64 bit wav. Type "afconvert" on your command line in terminal.app to see the options it offers. If you're not used to using the command line you might find this very uncomfortable, but it's really worth getting into it.
Let me know if you need help,
Jazz

320 & 128 bit rate in iPhone.

I haven't found an option that lets you choose the bit rate you want to convert your music to in my iPhone. All my music is 320 bit rate or lossless... So it's going to take a chunk of space. I'm converting the music I want on my iPhone to a 128 bit rate and throwing that in a playlist to sync to my phone... which I really don't want to do because now I have the same albums twice and it's makes my library messy. Any quick fix or solutions?

I can't speak for iPods cause I never bought one. I've always been the kind of person who rather have one device (Moto Razr V3i w/ iTunes) then two devices (reg. phone and an iPod). My phone would covert the music to 128 bit rate to optimize space. It would make sense that apple would give us an option to convert the size of our music files to optimize space as well. This making duplicate albums in two different bit rates is a hassle! Unless you've gone into Edit > Preferences > Advanced > Importing... the music you rip on your computer is going to be a defult ACC 128 bit rate format. Which there is nothing wrong with. If you share music with friends and they don't have iTunes there's going to be an issue. So I changed my encoder to MP3 and also adjusted the audio quality. You tend to lose lower frequencies when music is ripped at a low bit rate.

Import songs at selected bit rate

i thought when i set the preferance for importing music say at 128 kbs as a mp3 that was how all the songs would be imported.so why do they still import at differant bit rates and how can i get them to 128 kbs?

I see missing burn settings, too, & I'm getting a message about it each time iTunes is started. I have one (actually more than 1) unburned purchases from Apple Store, which downloaded as protected media (unplayable outside iTunes, even in my registered & paid for version of QuickTime - & that's a first). So, the repair needs to be done, at least temporarily, to burn out the purchases.
But, after the update the optical devices were no longer in the UI, so, I removed some things, manually, one of which is shown in the iTunes credits section as related to their burning software, at which time the optical drives again seem to be available to me, the owner, if not to iTunes when I authorize it for my usage. Clearly, this is an issue with Windows, DRM or some, other malicious software, otherwise, iTunes' use of MS approved software for burning would be no issue.
However, the import settings remain. They could be useful if one used iTunes to sync to iPod, I suppose, although other software is also capable of syncing to iPod. Other features of iTunes should also be unaffected, like the radio or podcasts or books or other feeds.
Browsing the Apple store is almost pointless under these conditions unless one turns on the option to see only DRM free media --- & there is precious little of that. I was actually beginning to use iTunes & the Apple store almost exclusively for that (& considering a Mac laptop) because of that reliability; apparently, my choice to never give up my freedom of choice to one provider is not without wisdom, since we just never really know what to expect.
Anyway, this looks more & more like some server side mal-usage of DRM.

Fixed bit-rate varies from song to song

after importing a cd (bit-rate set to 256 kpbs (stereo), 48 000 kHz, NOT checked the Use Variable Bit Rate Encoding box) i see thet the songs have been imported with bit-rates that change from song to song (like first song 258 kbps, second - 257 kbps, third - 251, fourth - 237 and so on).
could anyone please explain why so?
thanks in advance!

thenewdawg wrote:
Thanks for the thread, though it's an iTunes for Windows thread. Any info. for Mac?
Meg is correct, the issue is not specific to Windows, it is specific to QuickTime 7.3, on both platforms.
After reading through the thread, and others that it points to, I get the impression that the changes are supposed to be improvements. And probably are for the majority of people.
On the other hand, there are a number of specific cases where the new behavior is actually a problem. If you're using Doug Adams's excellent Join Together script (http://dougscripts.com/itunes/scripts/ss.php?sp=jointogether), with varying bitrates between tracks, you can no longer use the Pass-Through option, which means that the script can take much, much longer to complete.
And I've gotten reports from some people that at low bit rates, e.g., 64kbps and lower, imports using QuickTime 7.3 have some kind of static noise, that is not there when the same disc is imported / transcoded with QuickTime 7.2. So I think there are some software defects to work out, too.

Bit rates : "good" in mp3 is "high" quality in ACC ?

When I got my Mac in late March, and commenced w/ the importing, I knew nothing of bit rates. Don't know much more now.,.,...but a friend recently pointed out the rate of 128 being lossy.
Checking preferences, we see that in mp3, 128 is indeed the lowest of 3 choices_yet in ACC encoding, it's listed as "high".
I'm sick to the bone at the thought that the nearly 10,0o0 items I've imported into iTunes are now ALL in need of a re-do !!
Is 128 in ACC actually inferior ?
I'd imagine that converting the entire library to mp3's doesn't do more then slightly "expand" tracks that were encoded lossy to begin with !
==oY!==
TIA,
~~~=Dave

Is 128 in ACC actually inferior ?
Not if you play back using a 'standard' audio system. On high end systems you may notice lack of 'depth' compared to playback of an original (store bought) CD. AAC 128 kbps is good quality for general purpose.
Importing your CDs is always a choice between the available space on your HD (and/or iPod) and the audio quality.
The best audio quality is achieved by importing your CDs in AIFF, WAV or Apple Lossless.
The first two are uncompressed formats, having all audio information, but they result in huge files (about 10 MB per minute).
Apple Lossless is a compressed file format, still has all audio information (it's lossless as the name implies), but results in smaller file sizes (about 5 MB per minute).
MP3 and AAC are lossy compressed file formats, resulting in small file sizes (about 1 MB per minute at 128 kbps). Both compressing methods 'throw away' certain, less important parts of the audio.
AAC is considered to have a better algorithm (calculation method).
As a result AAC at 128 kbps is as good as 160 kbps mp3.
If you're happy with the audio quality of AAC 128 kbps (same format as songs sold in the iTunes Store) there's no need to redo them.
Converting these songs to 160 (or 192) kbps mp3 will not improve sound quality, but worsen it.
Omitted parts of the audio cannot be recovered (only calculated).
As AAC and mp3 use different calculation methods, some of the audio information will be omitted again and worsen the quality.
If you are unhappy with the audio quality, import a few tracks in losless formats (AIFF, WAV or Apple Lossless) or AAC and/or mp3 at higher bit rates.
Listen to them on your system and determine which quality sounds good for your ears.
Remember though, importing at high bit rates or uncompressed formats requires lots of disk space.
Hope this helps.
M
17' iMac 800 MHz, 768 MB RAM, 200 GB HD, DL burner Mac OS X (10.4.8) iTunes 7.0.2

Why duel bit rates after importation?

I imported my shared music folder. It shows duel titles & bit rates for SOME songs. (128 & 160)
Should I keep both, or, rid myself of one or the other?

If you have duplicates, I would keep those at the
higher bit rate. There won't be much in it between
128 kbps and 160 kbps but the 160s will be of a
slightly higher quality. It's really up to yourself
but there is no reason to keep both as you are just
using up disc space with duplicates
Thank you!
My thoughts exactly. Needed an expert opinion. Thanks again

Can no longer change bit rate in AAC custom import settings

I've been re-ripping all my CDs at the new higher bit rate. My import settings were AAC Encoder -- custom, originally set to 256 kbps, VBR, and auto for the other two settings. However, some CDs I wanted at a lower setting, so I would go change the bit rate to either 192 or 224 (just so I'd have more room on my ipod) and there wouldn't be a problem. But now it's stuck -- the pop-up box no longer opens when I choose import settings, AAC Encoder, Custom, so I can't change the bit rate or anything else, and it's stuck on 224 kbps. I can still change bit rate and other settings in the custom menus for MP3, WAV, etc., just not AAC. A repair install of iTunes did not fix the problem.

Hi, Ed. I am running iTunes 9.0.3.15. When I click custom, the settings description in the details box display what they were before this thing happened = 112 kbps (mono)/224 kbps (stereo), VBR, optimized for MMX/SSE2. The pop-up dialogue box that used to appear (where you could choose the specific bit rate from the drop down menu) does not appear at all.
However, when I choose anything other than AAC Encoder, and then pick custom, the pop-up box appears and I can choose the bit rate and adjust the other settings as usual. It's just not happening for AAC Encoder anymore. Since the total un-install (following Apple's specified order) and reinstall didn't work, I'm baffled how to fix this .... (If it makes a difference, I changed the bit rate in the custom box while a CD was being burned...Apparently that was stupid, but I had done it previously without incident.) Thanks.

Variable bit rate audio assets cannot be imported

Extracted some ac3 files from personal content DVDs I authored and burned myself (using DVDSP) to make a compilation. When I try to import these 5.1 ac3 assets, DVDSP is refusing stating: "Variable bit rate audio assets cannot be imported." These ac3 files play fine in QuickTime and other programs that handle ac3 files.
Can anyone help?

Hi:
Please give us some info about the original movie/audio formats and what encoding presets you used in Compressor.
Alberto

Imported .m2v bit rates in Encore 2.0

Hello,
I've noticed that whenever I import an .m2v into Encore, the bit rate reported in Encore is 2Mbps lower than that reported by other programs (e.g. AVICodec). For example, I'm trying to make a DVD from an .m2v created to have a bit rate of 7.7Mbps in Apple's Final Cut Pro/Compressor, but imported into Encore as an asset, its bit rate is listed as 5.7 Mbps. I need this DVD to be of the highest quality possible, so I figure that by creating an .m2v with an outside bit rate of 10Mbps, it will come into Encore with a bit rate of 8Mbps. Is this the right way to approach this problem?
In the past, I've run into the same issue with importing .m2v's into Encore and have opted to import .avi's instead and let Encore do its own transcoding. (Importing .m2v's into Encore sometimes creates weird blips in the video too.) The problem is that this time I want to create a DVD from an uncompressed HD Quicktime. (Since I'm a PC guy, a friend with an Apple computer is doing me a favor by converting the uncompressed HD Quicktime into .m2v for me.)
Any suggestions or advice will be greatly appreciated. Thanks.
-R

>Even if things have been changed on my system why should Encore do all the transcoding, write the files to disk and then hang on this issue? Even after a fresh re-install with all registries cleared etc?
An uninstall/Reinstall will almost certainly *not* clear out the registry, or even all the common files installed. Otherwise, you would be able to install a trial version, then uninstall it, and re-install again for another 30 days. This obviously doesn't work - so uninstalling is not removing all the relevant files.
Another common problem is that badly written 3rd party apps often reset the merit order of DirectShow related codecs, and this can mean that even when you think you're using one codec, the system (not Encore, but the OS) will use another one altogether. This can mean that what you
i think
is one type of AVI file is actually a different one, with perhaps an older version of a codec used to create the AVI being used because a codec pack installed/overwrote the good one.
I have had this happen to me - and it is a pig of a problem.
I could be completely wrong though.

Compressor 3.5 won't let me reduce the MPEG2 program file average bit rate

Compressor 3.5 won't let me reduce the MPEG2 program file average bit rate less then 10Mbps. I just installed this new version and it is giving me this problem. I have been delivering an 1hr MPEG2 program streaming at 6Mbps average to 7.1Mbps Max output with Compressor 1 for a year now. Here is my workflow;
Drop the 1440X1080 into NTSC timeline and DO NOT conform so it will be rendering as 720X480 then shoot that sequence to compressor to above settings. It worked just fine for a year. Now, this new compressor wont let me do less then 10Mbps which is the lowest bitrate for HD. The network can not run any bigger file than 6Mbps. I checked my settings restarted and all that. IS this a bug that needs to be fixed? Any help would be appreciated since my deadline is tomorrow.

Sorry, meant to say that this only happens with court databases. As far as I can tell, I can download from other sites with no trouble.

Issue with playing 320 k bit rate files on iOS 5

I was able to successfully update my iPhone 4 with the iOS 5 however to my (unpleasant) surprise I realized that all the music files of 320 K Bit rate that I had could not be played with this new OS. All other music files (of 128 K bits rate) was able to play normally.
When I attempt to play the higher bit rate ones, it doesn't give any warning or crashes. The Play symbol at the bottom changes to "Pause" indicating it's playing and when clicked again it changes to "Play" indicating it's paused. But the time slider stays at 0:00
It may be noted that the high bit rate files plays normally on the latest iTunes software on my PC running windows 7.
I haven't yet tried to remove all the paylists first and then add them back when syncing it next time. That might solve this problem but I am not sure. Even if it does, this is a major defect with iOS 5 that has gone un-tested. with the previous version, I had no problems playing the same high bit rate music files.

After I faced the above problem, I did the following:
1. Sync the iphone after unchecking the playlist having the 320 K Bit rate music files. As expected the playlist was removed from the iPhone.
2. Checked the playlist and then re-sync the iphone. This time when the music files were copied to the phone, all the files having a bit rate higher than 128 K were automatically converted to 128 K Bits.
The above process made these high bit rate files convert down to 128 K bits and playable on the iOS 5.
The question is why is iOS 5 not able to play the bit rate higher than 128 K Bits while the older version could? Does playing the high bit rate files offer any better sound quality on iPhone?
I have played the high bit rate on my car's audio system (Harmon Kardon premium speakers) and it definitely sounds better than it's 128 K bit equivalent.

Won't import at 320 bit rate?

Similar Messages

Maybe you are looking for