Audition CS6 - "An error was encountered: Not enough memory to perform operation"

When I try to export my entire session using the "Multitrack Mixdown" I get this error message: "An error was encountered: Not enough memory to perform operation"
To give context:
• Audition CS6
• All other applications are closed
• 26 audio tracks
• Approx. 22 seconds long in total
• Average of 2 effects per track
• I've reinstalled the program twice now
My computer:
• iMac (2010)
• 3.4GHz Intel Core i7
• 16 GB 1333 MHz DDr3
• Flash and HDD storage (which are not full)
• OSX 10.8.2
If anyone can offer any advice, that would be great!
I have to get this done by this Monday (May 6, 2013).
So I really hope Audition won't fail me, since it has always been successul until now (which is why I'm stumped).

'Not enough memory' hasn't got anything to do with your HD, but the amount of RAM available to Audition at the time it needs it. All DAWs, to work efficiently and successfully, need most of the machine to be free from running other apps. The reason for this is simple; If another app trys to hog a machine that's running a process in real time, it inevitably hiccups the machine. And if this other app has reserved RAM addresses for its own use, they aren't available until it's stopped.
Typical nasties involve anti-virus software, and the machine doing things like repeatedly polling a wireless connection, but there are plenty more, and this applies equally to Macs and PCs.
So the 'update' you need to rectify most of these problems is one you have to carry out yourself. Audio editing is a bit of an oddball from this POV - you invariably need a very lightly loaded machine for it to be reliably successful. The machine I use as a DAW doesn't do anything else at all; all unnecessary services are stopped whilst it's in this mode, and the physical spec of it is similar to yours - except it's a PC running W7-64Pro.

Similar Messages

Multiplexer error. Not enough memory to perform operation? iDVD crashes!!

Everytime I try to burn a DVD it gives me the same error and the program automatically shuts down. I have tried going into preferences and switching
the preferences everytime this window pops up.
"Your project exceeds the maximum allowed content duration. You will not be able to burn your DVD while your Encoder Setting is Best Performance. This can be changed in your iDVD Preferences."
The preferences are now set for best quality performance. iDVD shuts down saying that there is not enough free space to perform operation....Can someone help???
best,
Alejandro

Hello!
Welcome to discussions!
First, we need much more information regarding your mac, RAM, Disk Space, etc.
See how I have my specs written at the bottom? Go to your right and click on 'My Settings' and fill it out. That will help us here!
thanks!
Sue

When I try to import, I receive the following message: "An internal error has occurred: not enough memory". I always download my photos onto an external hard drive.

Yesterday,I downloaded an update for Lightroom 5. Now when I try to import, I receive the following message: "An internal error has occurred: not enough memory". The message comes up right after I click import, before I choose a file to upload.Here is the information I can think of that might be needed to answer this question:
- I always download my photos onto an external hard drive.It is about 10 % full.
- It says I have Lightroom 5.6 64 bit
- I am working from a newer laptop (Windows). The internal drive on the laptop has 289 gb and I am using 61 gb total memory.
- I have edited 2794 photos in Lightroom and it is all in one catalog.
- I did not have this problem until I made the update. I did have my first "bug" earlier this week when one of my photos had a line show up through the middle of it when I exported it. I was able to export it a second time without the line.
If there is more info. needed, let me know. I do photography as a hobby and know enough about Lightroom to edit out blemishes and adjust color balance, but not too much more, so forgive my ignorance if this is an obvious fix.
Sincerely,
Adrianne

Not Enough Memory typically refers to RAM. How much RAM do you have on your 64-bit OS computer? Do you have other programs running that may be using most of the memory?

Help Needed REP-1800 Formatter error VGS-1701 Not enough memory

Hi. Gents
Help needed
I’m working on a Report, it gets some 2 million records and the report pages are approximately 52,000
It works fine if the pages are lesser then 48,000 or the data is less let say one and half a million, the problem occurs only after 48000 + pages formatted.
Report is generated successfully when trying to go to the last page it throw an error.
REP-1800 Formatter error
VGS-1701 Not enough memory
I have already gone through the metalink DOC Id 95505.1 as well as OTN
But all in vain,
Any comments or help much appreciated.
Details are:
Reports 6i (Clients/Server) on Windows platform
(Windows XP Professional with SP 2)
Database: Oracle9i Enterprise Edition Release 9.2.0.5.0
Computer:
Pentium(R) 4, CPU 3.00GHz, 1 GB of RAM
Still 20 GB free space
Thanks & Regards

I don't see the point in making a report with more than 48,000 pages, I think Al Gore will not be happy when you start printing it...
The problem might be caused by the fact that Reports needs to format all output at once, and then even 1GB of memory will probably be not enough. Formatting all pages at once is needed if you use pagination with displaying total number of pages. If you have this, try to get that out of the report definition and try again.

Getting " Not enough memory for the operation error " in BOE

Hi,
We are using BOE 11.0.
we try to schedule a new report with multiple database logins for testing in BOE. When we run the report we are getting error like "Not enough memory for the operation error"
The same report has been executed successfully when we run using Crystal reports developer. The report is fectching less than 10K records from all the databases together.
Please let me know which is causing the issue and also let me know is there any limit in the number of databases connecting for a single report.
many thanks in advance for all your help.
Cheers,
Suri ;-)

Hi Sarthan,
Sorry. I'm new to BOE. We know only scheduling the reports creating folders etc. :-)
I've seen one parameter "Maximum Cache Size Allowed (KBytes)" and the value for this parameter is 5000.
If we change it to a big number whether we can solve the issue ? Please suggest.
Cheers,
Suri ;-)

Downloading itunes, I receive the error "there is not enough memory". How do I fix the memory issue?

When dowloadning tunes, I receive the error "there is not enough memory. I've deleted tunes from my library & ipod and I still get the error. How do I get around this?

It could be the newer version of iTunes requires more physical memory than your computer currently has available.
Do a right click on "My computer" and check out your computers memory/RAM specifications.
Windows XP is a bit bloated in the latest updates, trying to get people to upgrade to Windows 7, might be little room for other programs, especially one as huge as iTunes.
If you finally do choose a new machine, I have some tips:
For 3D gaming laptops, I wouldn't pick any graphics card scoring less than 1000 on this sites scale. Not scoring less than 2000 for towers.
http://www.videocardbenchmark.net/high_end_gpus.html
I would also choose a quad core processor scoring 5000 or better on this scale, 64 bit, Windows 7 Pro (so you can virtualize your XP programs) or OS X, and 4GB of RAM expandable to at least 8GB or future proofing your investment.
http://www.cpubenchmark.net/high_end_cpus.html
I would also choose 7,200 RPM hard drives for both towers and laptops for performance. On laptops while using the battery, set the energy savings to stop the hard drive spinning when not in use. Only choose the slower 5,400 RPM drive option if your always on battery and need maximum life as you lose about 20% with the faster drive, but gain 20% or more in performance.
Dual cores and 32 bit processors/OS with their 4GB RAM limit is soon to be old news.
For laptops, I highly recommend anti-glare displays for maximum use in any environment.

My brand new MBP 13"got the error "there is not enough memory or disk space to convert this document". What gives? Help please!

I am trying to use mail merge in Word for Mac on My brand new MBP 13". And I get the error "there is not enough memory or disk space to convert this document". What gives? Help please!

Why do I get there is not enough memory...: Apple Support Communities
Error message in MS Word opening a .docx file "There is not enough - Microsoft Community

MSword2003: error-"there is not enough memory or disk space to complete the operation"

One of my files can't be opened because of the error"there is not enough memory or disk space to complete the operation"
i have tried every thing....
renaming the template from normal.dot to old.dot...
disk cleanup
deleting all the temp,%temp,internet files, cookies.
but nothing working .....
please help

This forum is for questions and discussions about the TechNet Wiki. I will try to move your question to a more appropriate forum, dealing with Office technical issues.
Richard Mueller - MVP Directory Services

Not enough memory to complete operation

I've looked through the forums for the "not enough memory to complete operation" error and despite following the advice I found, the error still occurs.
I'm using LabVIEW 2012 to try and continuously monitor our system, recording temperature, power, etc vs time (values obtained from USB-6008 DAQ). The data being saved to file, is done every 60 seconds using a small array (no problems here). The typical run/time memory allocation to LabVIEW is about 180MB (4GB RAM on computer).
The issue I feel is related to our wish to display this data on graphs for extended periods of time. The current iteration of the code works as follows.
1) we have 2 XY graphs with 2 plots each.
2) for each plot, I am initializing clusters of 2 arrays of 100,000 (XY pairs) which are wired to shift registers. I know this is larger than can be displayed on a graph but I am currently more concerned with reducing the number of data copies.
3) Every 10th data point is added into the arrays using an In Place Element Unbundle/Bundle along with a "Replace Array Subset". This means there are approximatly 8640 points per day. (A single day is the shortest time span typically viewed)
4) For two plots on an XY graph, two clusters are combined in an array (using Build Array). I think this is my problem right here. Since everytime I update the graphs Labview has to allocate memory for the 4 XY plots. ( Am I correct here?)
Decimating the data further when looking over multiple days will reduce the amount written to the plots. However this operation creates data copies. Is it worthwhile in this case?
Instead of initializing 4 clusters (1 for each plot) and combining into arrays later, would it be better to initialize Array of cluster of arrays (2 plots per graph) and update the data by "index / unbundle / replace array subset / bundle replace array subset" series of operations?
Solved!
Go to Solution.

Hooovahh wrote:
But what I think is more important is your middle loop is unbounded in size for its arrays. Memory will continue to grow until it crashes. You removed the write VI but I'm guessing you are essentially overwritting the old file with all the same data but with 1 extra data point. Why not just write that one extra data point by appending to the existing file? Look at the Write To Spreadsheet which shows how to append to file (it is an optional input).
If you'll notice the section where I comment that the save VI is deleted, there is a null array wired to the shift register. While this probably isn't the best practice, the array builds to 60, appended to the text file, and overwritten with the null array. This is to avoid opening/closing the file every second.
The other array there stores power and time for every data point when the sun is up for the day (probably near 50,000 data points). This is done to calculate the days insulation by integration. This array could probably stand some improvement using an initialized array. (i got tunnel vision on the other part of the code and missed this).
In regards to the graphs containing multiple days worth of data to be viewed at any time, yes this is a requirement (the more the better). This is for monitoring a solar array at our University and, once free from bugs, will be linked to a web page using the Web Server. So individuals may view data within the past 1,2, or even 3 weeks. Normally, I would just have a separate VI for viewing data when desired but 24/7 access to view the updated data is a requirement.
Am I correct in that the Build Arrays (just prior to the graphs) makes a data copy of each cluster? Could it be this large data copy that's the cause of the error? My understanding from other posts is that this error is generally linked to non-continuous memory allocation for arrays/clusters.

Not enough memory to complete operation when writing TDMS file.

Hello,
I am new to Labview and having a bit of trouble. I attach some code here. What I want to do is sample from a NI 9220 DAQ from 16 channels at 20kHz, while from a second NI 6009 sample from 4 channels at 1000 kHz. I want to append these together and then write to a TDMS file.
I have tried to write this code using NIDAQmx VIs but when I have it has resulted in the two DAQs not having the right timing with each other. The 6009 samples for a longer time.
I have now tried instead to use the DAQ assistant to read from the two VIs and it works in that TDMS files produced have the correct timing between the two DAQS. However, if I record for more than 2 minutes, in the end I want to end up recording for a much longer time, I have the "Not enough memory to complete operation" message appearing. This still happens even if I get rid of my charts to display the data, and also if I get rid of the NI 6009 completely and just keep the 9220 sampling at 20kHz. It happens even if I repalde my TDMS write and put a write measurement assistant in which I tell it to write a series of files that are each less than 2 minutes long.
I think it is something to do with the amount of data I am reading and is being held in memory. What can I do about this? Also, my charts display very slowly, basically evey second when the 20k are read in. However if I lower the amount of data read the charts don't display all the data points.
I attach my code, thanks for your help!
Alfredo
Attachments:
03_02_15.vi ‏688 KB

alfredog wrote:
Hello,
I am new to Labview and having a bit of trouble. I attach some code here. What I want to do is sample from a NI 9220 DAQ from 16 channels at 20kHz, while from a second NI 6009 sample from 4 channels at 1000 kHz. I want to append these together and then write to a TDMS file.
I have tried to write this code using NIDAQmx VIs but when I have it has resulted in the two DAQs not having the right timing with each other. The 6009 samples for a longer time.
I have now tried instead to use the DAQ assistant to read from the two VIs and it works in that TDMS files produced have the correct timing between the two DAQS. However, if I record for more than 2 minutes, in the end I want to end up recording for a much longer time, I have the "Not enough memory to complete operation" message appearing. This still happens even if I get rid of my charts to display the data, and also if I get rid of the NI 6009 completely and just keep the 9220 sampling at 20kHz. It happens even if I repalde my TDMS write and put a write measurement assistant in which I tell it to write a series of files that are each less than 2 minutes long.
I think it is something to do with the amount of data I am reading and is being held in memory. What can I do about this? Also, my charts display very slowly, basically evey second when the 20k are read in. However if I lower the amount of data read the charts don't display all the data points.
I attach my code, thanks for your help!
Alfredo
As far as your charts updating very slowly - the way your code is designed, your charts only get data when both 20K samples & 1M samples are done collecting. Have you tried setting up DAQ assistant for continuous sampling instead of 20K samples or 1M samples?
-BTC
New Controls & Indicators made using vector graphics & animations? Click below for Pebbles UI

Error 83::8 (not enough memory to initialize PSL) when use layer styles in AEF

Hello!
Have error in AEF CS6 when i try to use layer styles in AEF. Error is "not enough memory to initialize PSL 83::8"
It works good if i start programm as Administrator.
My PC is: Windows 7, Intel core 7 with 2.7 Ghz, 6 Gb RAM, Nvidia GeForce 240.
I think i already know what the problem is:
After i bought my new SSD in need to change all temp files and scrathes disks to another HDD. And in conflicts with AEF ....
How can i fix it?

How can i fix it?
Check your file and folder permissions. Moving stuff around may invalidate old security tokens for user-specific folders. You may simply need to reclaim them and "Take Ownership" in the Security tab --> Advanced of your file properties dialog.
Mylenium

File Error - FCP-6 - "not enough memory" ---DVDPro disk is slightly jerky..

I have a macbook. 2GHz Intel Core Duo, 1 GB 667 DDr2 SDRAM. Final Cut Pro 6.0.1
OS 10.4.11
I have a project file - HD that has worked fine up until now. And wouldn't you know it - it's just
when I need to be able to burn to quicktime that this occurs.
There appears to be a continuing "file error: not enough memory" - anytime I open a sequence - now in any project.
I have done a disk repair with disk utility. I zapped the P-RAM. I've tried dragging the project files to my laptop desktop. Nothing works.
I have a Lacie external drive with over 150GB of memory left. Another project was shot in HDV -
and it seems this started to occur after working on that project.
What else is there? Why is it doing this - of all things, now?
Please advise - ASAP!?
Also, one other small detail. If I have my sequence settings in FCP at DVCPRO-HD720p60, and I set my compressor file at 23.98fps - could that be responsible for a subtle jerking in the DVD Studio Pro Disk print? When I pull up the file in DVDpro - and play it on the simulator, the jerking is not present, only in the disk burn.

The memory that FCP is referring to is RAM. If you're running with less than a couple of gigs, larger projects will report that there's not enough memory... a gig isn't really enough to run FCP anymore. Tiger and Leopard use a LOT of it up so you probably need more RAM.
The other things that can use up RAM fast are graphics from photoshop, and if they have a blank layer in them, you'll get an out of memory error too. So might check that out, but my guts say you need more RAM for your laptop.
Jerry

Not enough memory to perform...Error

Hi,
I previously used PS CS on XP Pro and all was fine. I then upgraded to Vista. Since I reverted back to XP Pro I keep getting error messages.
When I use the 'Open as' command, I get:
"Could not complete your request because it is not a valid Photoshop document" (yet it's a JPG) - works ok if I just usen File >Open.
When I try and shut/close down the file/program, I get:
"Could not complete the Close command becuase there is not enough memory (RAM)"
Strangley enought these messages then just disappear. Really stuggling to use this software due to the annoying pop up messages. Appreciate any advice. Thank you!

First, when you say you 'reverted' to XP Pro, I will assume you did a complete uninstall/reinstall of ALL software. If not, start there.
After that, try trashing your Prefs file (second item in the FAQ folder) http://www.adobeforums.com/webx/.ef4a07f/0
If that doesn't do it, check your preferences in Adobe itself to see how much memory, etc. you are allowing it. Increase as necessary.
Beyond that, I'm just a minor wizard, junior grade. We'll have to hope that one of the Yodas will help.

Photoshop CS6 unusable -interface freezes and not enough memory message - on a specific hardware

I usually speak french but I'll try to be as clear as possible.
I work as a technician in a school and we're experiencing a major issue with Photoshop CS6.
We have 3 differents computer's hardware. Photoshop CS6 works fine on 2 of them.
On the other though, Photoshop CS6 is unusable. With this specific hardware, Photoshop has the same weird behavior on each machine (around 50), so it's not related to an hardware malfunction (like bad ram) I suppose.
Our problem is this: Once Photoshop is opened and you minimize it in the task bar, as soon as you maximise it to use it again, the interface doesn't respond well at all, the interface is all messed up, some windows are missing and most of the time Photoshop freezes. And after that, whatever we try to do, like selecting whatever option, we have the ''not enough memory'' message. So we can't do nothing with the program after that, from selecting another tool to saving a file.
Even when no file is opened and we have plenty of RAM that can be used, the problem is there.
The same problem occurs if we open a window above Photoshop (internet, word, everything). As soon as we go back to work in Photoshop, the interface freezes and windows are missing, and we get the same not enough memory message every time.
We already tried to change/desactivate each performance settings in Photoshop, we already installed the latest Photoshop CS6 update.
We've updated BIOS, processor driver, graphic card driver, etc.
We have this problem with Photoshop CS6 64 bits and 32 bits.
We dont have this problem with any other program in the CS6 suite.
We dont have this problem with Photoshop CS5.
We have the same graphic card and driver on the others computers where Photoshop CS6 works perfectly well.
What's bugging us is everything else in the production suite works fine!
Please, do you think of anything else we can try?
We're hopeless!
Here is the specific hardware where the problem occur.
Hardware:
Dell Inspiron T3500
Intel XEON e5220 2.27 ghz
6 GIGS (RAM)
Quadro FX 1800
Plenty of available hard-disk.
VRAM: 768 MB
OPEN GL: Version 3.3
Windows 7 Professional SP1

Yes! There it this (sorry our Photoshop version is in french since we are a french school, I hope it's still useful to you) .
Please note that it's not with the latest Adobe update available, but we've tried it on an other computer but I can't access it right now. But the adobe update did'nt solve the problem either.
Version Adobe Photoshop : 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x64
Système d'exploitation : Windows 7 64 bits
Version : 6.1 Service Pack 1
Architecture système : UC Intel Famille :6, modèle :10, niveau :5 avec MMX, SSE Entier, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Nombre de processeurs physiques : 4
Nombre de processeurs logiques : 8
Vitesse du processeur : 2266 MHz
Mémoire intégrée : 6142 Mo
Mémoire libre : 4316 Mo
Mémoire disponible pour Photoshop : 5361 Mo
Mémoire utilisée par Photoshop : 60 %
Taille de la mosaïque d'images : 128K
Niveaux de mémoire cache de l'image : 4
Dessin OpenGL : Activé.
Mode de dessin OpenGL : Standard
Mode OpenGL normal autorisé : Vrai.
Mode OpenGL avancé autorisé : Vrai.
Anciens GPU OpenGL autorisés : Non détectés.
Fournisseur de la carte vidéo : NVIDIA Corporation
Module de rendu de la carte vidéo : Quadro FX 1800/PCIe/SSE2
Affichage : 1
Limites d'affichage : = haut : 0, gauche : 0, bas : 1200, droite : 1920
N° de la carte vidéo : 1
Carte vidéo : NVIDIA Quadro FX 1800
OpenCL Non disponible
Version du pilote : 8.17.12.9573
Date du pilote : 20120209000000.000000-000
Pilote de la carte vidéo : nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Mode vidéo : 1920 x 1200 x 4294967296 couleurs
Nom de la carte vidéo : NVIDIA Quadro FX 1800
Mémoire vidéo : 768 Mo
Taille de la texture rectangle vidéo : 8192
Numéro de série : 92278706405826761289
Dossier de l'application : C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Chemin des fichiers temporaires : C:\Users\elebel\AppData\Local\Temp\
Le disque de travail de Photoshop comporte l'E/S asynchrone activé.
Volume(s) de travail :
C:\, 405,5 Go, 363,7 Go libres
Dossier des modules externes obligatoires : C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Dossier principal des modules externes : C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Dossier des modules externes complémentaires : non défini
Composants installés :
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   6,0,29,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Modules externes obligatoires :
   3D Studio 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   ADM 3.11x01
   Aérographe 13.0
   Aplatissement 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Aquarelle 13.0
   Asymétrie 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Barbouillage 13.0
   Bas-relief 13.0
   BMP 13.0
   Camera Raw 7.0
   Carrelage 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Cisaillement 13.0
   Collada 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   CompuServe GIF 13.0
   Contour accentué 13.0
   Contour déchiré 13.0
   Contour encré 13.0
   Contour lumineux 13.0
   Contour postérisé 13.0
   Contraction 13.0
   Coordonnées polaires 13.0
   Correction de l'objectif 13.0
   Couleurs NTSC 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Couteau à palette 13.0
   Craie/Fusain 13.0
   Craquelure 13.0
   Crayon Conté 13.0
   Crayon de couleur 13.0
   Cristallisation 13.0
   Croisillons 13.0
   Découpage 13.0
   Demi-teintes couleur 13.0
   Désentrelacement 13.0
   Diagonales 13.0
   Dicom 13.0
   Dispersion 13.0
   Eazel Acquire 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Ecart type 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Effet mosaïque 13.0
   Effet pointilliste 13.0
   Emballage plastique 13.0
   Enregistrer pour le Web 13.0
   Entropie 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Eponge 13.0
   Etalement 13.0
   Extension WIA 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Extrusion 13.0
   Fibres 13.0
   Filtre Collection d'images 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Filtre Rogner et désincliner les photos 13.0
   Flash 3D 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Flou de l'objectif 13.0
   Flou optimisé 13.0
   Flou radial 13.0
   Fluidité 13.0
   Format IFF 13.0
   Fresque 13.0
   Fusain 13.0
   Galerie de filtres 13.0
   Google Earth 4 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Grain 13.0
   Grain photo 13.0
   Grand-angle adaptatif 13.0
   Halo 13.0
   HDRMergeUI 13.0
   Insertion filigrane 4.0
   JPEG 2000 13.0
   Lecture filigrane 4.0
   Lueur diffuse 13.0
   Matlab Operation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Maximum 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Médiane 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mezzo-tinto 13.0
   Minimum 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Moteur 3D Photoshop 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Moyenne 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Moyenne 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Multiprocesseur 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Néon 13.0
   Noir/Blanc 13.0
   Noyau de mesures 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Nuages 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Nuages par différence 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Océan 13.0
   Onde 13.0
   Ondulation 13.0
   OpenEXR 13.0
   Papier gaufré 13.0
   Papier humide 13.0
   Pastels 13.0
   Patchwork 13.0
   PCX 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Peinture à l'huile 13.0
   Photocopie 13.0
   Pinceau à sec 13.0
   Pixar 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Placage de texture 13.0
   Plâtre 13.0
   Plume calligraphique 13.0
   PNG 13.0
   Point de fuite 13.0
   Pointillisme 13.0
   Portable Bit Map 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Portée 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Radiance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Réticulation 13.0
   Rogner et désincliner les photos 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Routines FastCore 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Routines MMXCore 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Solarisation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Sommation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Soufflerie 13.0
   Sous-couche 13.0
   Sphérisation 13.0
   Sumi-e 13.0
   Support de script 13.0
   Tampon 13.0
   Targa 13.0
   Tourbillon 13.0
   Tracés vers Illustrator 13.0
   Trame de demi-teintes 13.0
   U3D 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Variance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Variantes 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Verre 13.0
   Vitrail 13.0
   Wavefront|OBJ 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Wireless Bitmap 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Zigzag 13.0
Dossier des modules externes tiers et facultatifs : SANS
Modules externes dont le chargement a échoué : AUCUN
Flash :
   Mini Bridge
   Kuler
Modules TWAIN installés : AUCUN

Import errors with numbers, not enough memory

Import errors with numbers, not enough memory

Hi heiko,
From your system profile line, it appears you should be asking this question in the iWork For iOS forum, not this one, which deals with Numbers for Mac OS X. I'd also suggest being a bit less cryptic in writing your question.
The link will take you to the iWork for iOS forum.
Regards,
Barry

Audition CS6 - "An error was encountered: Not enough memory to perform operation"

Similar Messages

Maybe you are looking for