Importance of 64 bit

I have a MacBook Pro 15 inch (Core Duo 2.16). I have 2 gigs RAM as well. Am I correct that this computer does not support 64 bit? How important is 64-bit technology, does it increase speed of the computer or does it enhance the look of the general GUI?

... How important is 64-bit
technology, does it increase speed of the computer or
does it enhance the look of the general GUI?
products...,
I realize that I did not address the later half of your question in my previous post since the first part was answered by others. You might look at the following Wikipedia link:
http://en.wikipedia.org/wiki/64-bit
64-bit technology does have certain advantages that you may or may not see as a user. As to the look of the GUI, there is no direct relationship. When Leopard is released I believe it will support systems like your own and as such you should be able to enjoy what it has to offer just as those with 64-bit compatible hardware will.
MBP C2D 2.33 Mac OS X (10.4.9)

Similar Messages

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

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

Adobe Encore DVD: Importing 96k/24-bit PCM Audio

I seem to be unable to import a 96kHz 24-bit stereo PCM audio file in to Encore 2.0 - Is there a special way of doing this? Is it even possible?
Thanks for your help

Hi
Thanks for the replies. Most of the people who view my videos probably have a DVD-Audio player or a decent DVD-player so I'm not really worried about the audio sounding ugly. Many of the new lower mid-range players have 96kHz DACs in them. I think a few years ago using 96kHz/24-bit for DVD-Video wouldn't have sounded as good. With the newer HD and BluRay players coming out I think they also have 96kHz/24-bit DACs as well.
For Adobe it would be one way to say Encore handles audio up to 96kHz etc... I haven't even looked at CS3.

Importance of LUT Bit Size

My apologies if my question is a bit off-track. However, I suspect that the most reliable source of information will lie with Mac users.
I plan to purchase an external display for post processing & print matching. The contenders are: Dell U2410 (12 bit LUT) & NEC EA231WMi (8 bit LUT). In real-world terms, how important is the diference in LUT bit size in image processing?
Thank you kindly for your help.

Thank you, David. My own research confirms your comments. In fact, I am now looking seriously at the NEC P221W (10-bit LUT). The only question is whether the Eye One Display 2 hardware will work accurately with the wide gamut NEC. I understand that the NEC SpectraView II hardware is an Eye One Display 2 unit specifically tuned for wide gamut. Some people apparently are using the SpectraView II software with the standard Eye One Display 2. I need to clear up this concern.
Thank you again for your help.

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.

Why does HDV ProRes422 import as 8-bit?

Just wondering...when checking the 'internal pixel format' in Setup/User Prefs, only 8-bit is highlighted and all others are ghosted (except floating point). My original footage is HDV (8-bit native) but I digitized it as ProRes422 via a Kona LHe card. According to the Kona folks, this is supposed to allow me to process the footage in a 10-bit workflow, which would be ideal for Color. My timeline settings seem to be in order, so why isn't Color seeing this as 10-bit material, after the sequence is sent from my from my FCP timeline? Thoughts? Anecdotes? Bueller?

You're right about the LHe handling full HD to ProRes conversion. We run a Quad with an LHe and a RAID50 SCSI setup and capture 1080i/50 via HD SDI to ProRes422 HQ (230 Mbps) without problems.
Our original Quad, and a 2nd recent purchase, have the G5 ATI X1900 cards (ex OWC) to replace the single Nvidia 4500 that with Color 1.0 was limited to 8 bit, although I think it's a bit faster than the G5 ATIs - with 8-bit or FP being the only really options we need, I think I'd have the 4500 back in both given the choice. But the ATIs are workable enough.

Importing 44100kHz 24-bit audio into 48kHz 16-bit project...

Can I do this or should I do some sort of conversion first? What are the implications?
Thanks

Hi Jim,
I wasn't clear. I'm referring to synchronization and clocking issues more than duration. I don't think that the sample rate matters if one is just using music for a soundtrack, but if one is , for example, recording audio and video at a concert, independently of each other, then it could matter depending on the answer to this question. I have heard (and I don't know whether its true), that even some timecode synchronization systems don't do a perfect job at synchronization. From personal experience, I have seen that two different digital recorders (they were different brands) will not necessarily stay in sync with each other when recording at the same sample and bit rates.
Thanks,
Steve

I imported uncompressed 10-bit 4:2:2 to DVDSP

and when I simulate it, i see the horizontal lines. What can I do ?
When I play it in QT it looks fine..

when i burned to a disc and watched it and it looks fine..
i guess it was just a preview problem..

Import 16 bit tiff files in premiere pro cs5 ?

When i try to import a 16 bit tiff sequence I get an error message "The video bit depth of this file is unsupported.".
I could not find how to set bit depth in project, however I understand from the help files that 16 bit workflow is supported.
What I am doing wrong?

Hi again Salazaroo....
Thanx for your answer...
I am working in a project shot with RedOne and the output will be 35mm and DCP.... we´ll made the prints with Cinevator system as well... same as yours...
What I did is open the Pr project in After effects and from there export the R3d as DPX to work in the compositings... I am trying different ways to do this... change the R3D settings to RedLog and RedSpace before to export as DPX OverRange, or PDLog985 and RedSpace before to export as DPX Standard (as Mark Christiansen says in THIS SITE) ...
Once I do it, I import the DPX to start the composition... so I change the Cineon Settings to OverRange or Standard (depending of the settings at export) and apply the Cineon Converter LogToLin... but then everything looks too overbright to work... I am working with the DPX and .psd and tiffs together so it is like crazy to match everything together...
I tried to export as PDLog985, RedSpace and OverRange Cineon Settings (instead of Standard) and it looks much better... I check the picture looking at the Info panel and everything is Ok, or close the 'Iris simulator' and detail appear in the image, ...but when I check different elements coming from matte painters and 3d artist, whites clip at 1... how can i match everything together in the same space color to work and then apply the Cineon Converter LintoLog before export???
This is the first time I work with DPX and I am reading a lot about it, but I could´t find a step by step explanation... and it is like there are many ways to deal with it... some people says to use a general Working Space, some people says don´t (See this Article) ...
Thank you man.... I really appreciate your help....

Importing 16 bit file into 24 bit project

Whats up guy's
When importing a 16 bit file into a 24 bit project
should I convert the file to 24 bits or keep the
original 16 bit depth?
I'm aware that the sample rate is converted to the
projects sample rate when importing files as long as
the corresponding checkbox is enabled in the project
settings - assets pane.
I'm also aware that conversion can be done at a later
state after importing, but I'm curious about the best
or proper approach. Should this be done prior to importing
or should the file be kept in it's original state (16 bits)?
PS - If you could provide the chapter or page of the manual
this information is on that would be extremely helpful.
Thnx in advance

Qstn wrote:
When you say "alter the file's sample data" are you referring to
edits done in the sample editor or sample rate conversion?
both would qualify. there are some corner cases where bit depth does not matter when destructively editing sample data (as I outlined in my initial post).
If you're talking about the sample editor do you mean converting by
saving a copy as 24 bits and making edits to the copy might show tiny
improvements?
yes.
At this moment I don't intend on destructively editing the file but
you never know how processing and mixing might go until your done.
ok. if your file is read and processed in realtime (or via a frozen track) then there's no loss - logic will convert audio samples during playback to a 32 floating point representation as it is read from disk, before it enters the mixer, or is processed by your plugins.
i'm not sure if source bit depth determines bounce in place format- if so, and if you use this feature, then you should convert the source to 24 bit.
the end point is: unless you are desperate for disk space, just convert it to 24 bits. 16 bits is very 'last millennium' in modern production stages - there are a few exceptions to that (e.g., if the files are used by a software sampler, or if the format is required for compatibility with other hardware or software) but... most of the strong arguments for 16 bit died years ago. so, i'd say it's best to consider 24 bits as the minimum during production unless you have very specific reasons to go below that (and you fully understand the tradeoffs). if you want to know the 'whys', that's fine, of course. curiosity and knowledge don't hurt. if you're only looking for a recommendation, that's my recommendation.

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.

Logic pro 7 cannot import 32 bit file

i was trying to import a 32 bit audio file but logic cannot read it and cannot play it.
this is weird because in cubase and protools i can do it.
is there any way i can do it in logic.
if not please apple make it happen its basic.

visit:
http://www.logicprohelp.com/viewtopic.php?t=1442
bob hunt explains a little about developments and reasons for some of logics limitations. if logic had been developed from the ground up then we would be better able to complain about some weird limitations. but logic is deep - really deep. i think some of these limitations are to do with inhereting a vast and complex programme. as it says in the report, they have to balance commercial needs (ie new features) and engineering "challenges" and stability. sounds like there are trade offs, and this makes sense.
i don't think we'll have too long to wait before logic will support 32 bit.
personally it hink there are much higher prorities than 32 bit support if 32 bit support meant a complete redesign of the audio engine.

Moving a 32 bit Oracle 9i database to 64 bit on a different server

Hello,
We have a 24 GB database with Oracle 9.2.0.7 (32 bit). As the hardware of this server is getting obsolete, it is planned to move this instance to another server, which has 64 bit Oracle software of same version (9.2.0.7). In this scenario what is the best way to move the instance?
Is it only the full export from 32 bit server and import into 64 bit server(after creating the instance there)?
Since this is a 24 GB database, and target server is 8 gb of ram, any pointers on how long the import process can take?
There is a documentation to change word size, I can run utlirp.sql as suggested here:
http://www.orafaq.com/forum/?t=rview&goto=258668#msg_258668
But I have some doubts as I mentioned in that post. Can you please share your suggestions?
Thanks,
Nirav

Hi
Is there some document or steps to follow when creating the instance on the new server The database move is easy, and here is one way to move the schema, fast:
http://www.dba-oracle.com/oracle_tips_db_copy.htm
And then, you just run the script to change the wordsize for 64-bit:
Also, after your migration, watch out for common performance issues:
http://www.dba-oracle.com/t_bad_poor_performance_upgrade_migration_32_64_bit.htm
Also, note that Oracle has changed the optimizer costing model from "IO" to CPU" in 10g, and shops that combine an upgrade to 64-bit servers with a 10g migration may want to look at changing the new default for _optimizer_cost_model.
Going 64-bit means that you can now allocate very large RAM data buffers and increase your shared_pool_size above two gigabytes. However, it is important to remember that there are downsides to having a super-large db_cache_size. While direct access to data is done with hashing, there are times when the database must examine all of the blocks in the RAM cache. These types of database may not always benefit from an upgrade to a 64 bit server:
Systems with high Invalidations: Whenever a program issues a truncated table, uses temporary tables, or runs a large data purge, Oracle must sweep all of the blocks in the db_cache_size to remove dirty blocks. This can cause excessive overhead for system with a db_cache_size greater than 10 gigabytes.
High Update Systems: The database writer (DBWR) process must sweep all of the blocks in db_cache_size when performing an asynchronous write. Having a huge db_cache_size can cause excessive work for the database writer. Some shops dedicate a separate, smaller data buffer (of a different blocksize) for high-update objects.
RAC systems: Oracle RAC and Grid does not perform optimally with super-large data buffer RAM, as available in 64-bit systems. You may experience high cross-instance calls when using a large db_cache_size in multiple RAC instances. This inter-instance "pinging" can cause excessive overhead, and that is why RAC DBA's try to segregate RAC instances to access specific areas of the database. This is why Oracle 10g grid server blades generally contain only 4-gig RAM.
Hope this helps. . .
Don Burleson
Oracle Press author
Author of “Oracle Tuning: The Definitive Reference”
http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

Error while importing CD's in ITUNES

I got the the flowing messages while importing cd's to my network disk.
System failed to parse media metadata of file [/volume1/music/iTunes/iTunes Media/Music/Compilations.
In Itune, I changed the setting to the pas you see in the message. For a couple of CD's the import went well, bit after a couple more I see this message in the logbook of my NAS(network assessable storage). Itune resets the pas to the Imac hard drive without asking. Anyone know about this problem and how can you resolve it.
Please help.
Regards Frank

Look at the fine print on the CD or on the CDs case to see if there is any mention of it being "Protected" or having DRM (Digital Rights Management) on the CD.
Usually protected CDs will have either there own "Player" software on the CD you have to use to rip the songs to the PC, or you have to use Windows Media player to rip it. Most record companies find it easy on them to make you rip with windows media player since it will protect there songs and roughly 95% of the world has a PC with WMP on it.
If you can use Windows media player to rip the songs, you have to use Windows Media player to burn them to a CD, then use the CD in iTunes to import them to iTunes.

Importance of 64 bit

Similar Messages

Maybe you are looking for