Does the "Warning! Not Enough Memory" bug still exist in Logic 8?
Hello everyone,
I'm wondering if the dreaded "warning, not enough memory" bug still exists in Logic 8. Here is a detailed account of the bug from Logic 7: http://discussions.apple.com/thread.jspa?messageID=767597򻙭
If this is fixed, I'm seriously considering upgrading mid-project! The film score I'm working on has many doubling parts that I'd like to edit at the same time in the matrix editor. However, editing multiple parts in the matrix editor seems provoke the little bugger, and I've already been bitten a few times in this project already. The only solution I've found is to stay clear of editing multiple parts at once (i.e. edit each parts individually, which obviously takes more time) or save before editing and hope I dont get bit.
I would LOVE to hear a report that this bug has been exterminated, and perhaps may upgrade mid project if thats the case.
Thanks in advance for your reply!
Heya,
I'm not familiar with the bug you're talking about. But would, as a fellow film composer, strongly urge you against the mid project switch.
I loaded in LP8 and ofcourse had a look at what it was all about, and it's really really fantastic. It also seems very stable. I fortunately have a side project that I am working on so switched to LP8 for that. Whilst I'm thankful to get my head around a very new approach for logic, I'm also thankful that I have this side project as it has illuminated a multitude of problems that exist with LP8 that would make any scoring process a bit of a headache to say the least. The main one being that if you don't have a very very powerful mac (I'm prepping a really fully loaded 8 core) you are not going to get anywhere near the performance out of Logic as you do with 7. This is a bottom up overhaul and it needs hardware to match. Heck even my 30" cinema display seems cramped and insubstantial on this new version. I would be so bold to say hold off until you have a hearty new mac and at least 8.2 is released IMHO but maybe try and get on it onto a smaller project to familiarize yourself before hand.
Similar Messages
-
With every second or third file I want to export I get the remark "Not enough memory"
After I have edited an image in Lightroom CC I always export my files to an external hard drive. Lately I get the remark "Not enough memory with every second or third file. Sometimes even with the first file I want to export.
My RAM memory is 4.00 GB and I stil have 3.25 GB available. I have cleaned my C-drive. When I look at the specifications of LR CC I see that there is a fysical memory available of 719 MB, but LR is using more than that, so it is probably using virtual memory. Could that be the problem and how do I solve the problem.
I never have any of this problem with other software.I have LR 5.3 installed on 2 partitions on the same PC and same HD:
Partition 1 has Win 7 32bit 4GB RAM
Partition 2 has Win 7 64bit 8GB RAM
On the 32bit partition, now that I am using larger raw files from a Nikon D610, I find LR not fit for purpose. I get numerous problems while editing and also get "Not enough memory" when exporting.
On the 64bit partition, everything works as should.
AS I've said before: With image files getting increasingly larger, Adobe are way too optimistic, and dare I say - disingenuous, when stating in their System Requirements: "2GB of RAM (4GB recommended)". This can only lead to dissatisfied customers.
So, as dj_paige says: "The best solution, almost guaranteed to work, is to have both a 64 bit operating system AND 8 GB or more of memory. Upgrading only one or the other probably won't work, you need both."
Works for me! -
Windows Photo Gallery Warning - Not enough memory
I am currently going through holiday pictures and deleting a fair few. I have folders that consist of around 1500 pictures, which includes both jpegs and NEFs. When I view these I have no problem for the first say 50 or even 100 at times. Eventually it gets to a state where pretty much every second picture reveals the following warning:
'This photo can't be displayed. You might not have enough memory available. Close some programs or if your hard disk is almost full, free some disk space and try again.'
The odd thing is that if I go back to a previous picture and then to the one that hadn't worked, it works most of the time. If not, I keep clicking left and right and eventually it works again. I only bought the laptop today, so the space isn't the issue. It's got 8GB of RAM too, so I should be fine.
My model is: HP 15-G092SA
I am thinking it could have to do with the limited 2MB cache that the graphics card has. Could that be the problem? If so, how do I solve it. Google doesn't seem to reveal many answers.
Thanks to anyone that tries to help in advance.Hello Yasumy, welcome to the HP Forums.
I see that you're having an issue with Windows photo gallery warning you of not enough memory to view your pictures. I will try to assist you with this.
"I am thinking it could have to do with the limited 2MB cache that the graphics card has" - This is very valid, as you mention loading 50 - 100 photo's a time, there could just be too much data on the page to be processed at that time.
A few suggestions that may help:
view a smaller number of files
Separate file types into their own folder
Create additional sub folders with catagories. (1 folder with 1500 images is a lot of data to load at once)
A few questions:
Are you loading these to view off the notebook directly or are you loading the from another source? (Flash drive, SD card, Sky drive etc.)
What's the operating system running on the notebook?
Thank you for posting on the HP Forums.
I worked on behalf of HP. -
Warning: "not enough memory to create shadow map vertice"
Hi,
First of all I am not too technically minded and not a great expert at after effects so keep this in mind when answering
I will post as much info to give a comprehensive idea of my setup and issue.
What I am basically asking is if I have after effects setup correctly for the spec I am running to achieve maximum benefit and performance?
And Is this perhaps a project composition error?
I have an after effects project that fails about 2.5 hours into rendering with this warning:
Now just a bit of background. I had 4gb and have upgraded to 8gb. The reason I upgraded was due to this error however I still have same issue (to be honest I dont see any improvement with ram previews etc).
This is my current PC spec:
I have changed virtual memory to double the RAM which I believe is what is recommended?
Now this is what after effects looks like on start up: Should it not utalise the 8gb?
When rendering it also just says using 4gb also:
Here are my multi processing and memory settings:
I hope this is detailed enough for someone to troubleshoot and help me out.
Kind Regards,
jmcall10CS4 is 32bit. It will never use more than 4GB. Basic computer math. Simply consider turning off MP rendering to free up more RAM for the primary render instance. Shadow map size defaults to "comp size", but of course you may be able to reduce it. Check the advanced comp settings. Beyond that simply render to an image sequence so you can resume from the point of the crash/ hang without losing all your rendered stuff, then assemble the iamges to a clip file in a second pass.
Mylenium -
Help
What request did you make?
Seriously, what did you try to do that yielded that message? Also, please give some details about your system besides how much RAM it has. For starters, what OS and version of Photoshop?
-Noel -
'Not enough memory' + 'Internal error' x 'Could not render the database' = Parting of company :(
I can’t believe the amount of concern / disappointment / frustration spread across every associated Fireworks forum re: CS5’s
"An internal error occurred"
"Could not render the database"
"Not enough memory"
"Crash without notification"
Etc.,
We installed the CS5 trial – being more than wary about Adobe’s past releases – and lo and behold, all of the above beared ‘true’!
This is nothing new of course, we’ve all been experiencing this since CS3 – but hoping against hope - a newer release would solve the poor memory management and general ‘bug-ridden’ code; alas - as per usual, Adobe has not responded with any pro-solution based action, but successfully furthered our frustration with a couple of fresh gimmicks without strengthening the core software.
As an avid fan of adobe software […and a Fireworks freak] working in a design house that has many different employees with widespread software tastes – I eventually said ‘enough is enough’ after the umpteenth crash [as of 3 weeks ago] and have revisited the Rebel Alliance; ‘yes, CorelDraw’! No I’m not going to go into some tirade about how much better Corel is etc. - as it has its own strengths and weaknesses, too […but without the hourly crashes] – so to be honest, we figure the time increase in some projects due to using Corel […time is diminishing with each project’s acquired experience] are negated by the downtime of Fireworks; so far, this is holding true.
This may seem drastic, but it has been a long time coming – that is, implementing a move from our decade invested workflow to a ‘somewhat’ new schema, but due to the disappointing aforementioned, eventually principal / expenditure comparisons / sanity / lack of support all culminate to such, and if there’s no support for the competition, well – then there is ‘no’ competition; a luxury Adobe has taken for granted way too long.
I truly hope Adobe turns around and fixes their ways, until then – we’ll be supporting those that do – and hopefully along the way, just maybe, with the added funds from disgruntled adobe x-pats – the software will far exceed what I used to love and adore […how I miss macromedia]; honestly, it would be near on impossible to argue which suite was better ‘either way’ – so it may not be such a distant future. Besides, with the market-door Adobe is opening due to such poor software, the new player sniffing around the edges will be welcomed by many with open arms; I know my/our allegiance will go straight to the company with the greatest software stability and sound support, whomever that maybe.
So here’s to hoping no more, and actually doing! Very sad...I am also getting this error message. It happens randomly. Adobe help told me to close and reopen FW and then it stopped happening. Does this sound like a good solution to anyone?
-
Not enough memory to load the tiff file
I did a search for this problem and there were two threads about it but I can't post to them. I think they are archived. Unfortunately, there was no answer to this problem in there.
The error "not enough memory to load tiff file" has been occuring in our shop on various computers with different resources. I believe that it has happened on our Mac as well. All are running Illustrator CS2 except the Mac which is running Illustrator CS3 and Leopard.
Has there been any progress on what the problem is? Has anyone found a solution that doesn't involve having to resave tif files as other formats to get them into the original Illustrator document? Or a solution that does not involve a huge work around?
I don't know the specs of all the computers in our shop but the one that I'm working on has the following specs:
Pentium 4, 2.8 GHz with 2.5 GB of RAM
Windows XP Pro Version 2002; service pack 3
Any help would be appreciated.
J.Photo Scaling for Video
http://forums.adobe.com/thread/450798?tstart=0
-Too Large = Crash http://forums.adobe.com/thread/879967?tstart=0 -
Not enough memory to initialize the system??
Hi,
I am trying to write a little MIDlet but have experienced some trouble with starting the MIDlet. I use the phone S55 and the MIDlet has about 12KB.
There are about 9 displayables all extending List but one, which is just a string item. All runs fine up to that time, but then when I add two other displayables each including one text filed in order to add and save some info in a recordstore (the record store is even commented out) the mobile just show the message "please wait" and runs for some minutes. Once it also showed the message "not enough memory to initialize the system". But that can`t be because of two new displayables with text fields, can`t.
I appreciate any help.
ThxIt actually really seams, that the problem occures as soon as I create an Object:
private SaveLP saveLP = new SaveLP();
and the Class looks like this:
import javax.microedition.lcdui.*;
public class SaveLicencePlate extends Form implements CommandListener {
private LicencePlate licencePlate = new LicencePlate();
private TextField textField1;
/**Construct the displayable*/
public SaveLicencePlate() {
super("Car Licence Plate");
try {
jbInit();
} catch(Exception e) {
e.printStackTrace();
/**Component initialization*/
private void jbInit() throws Exception {
// set up this Displayable to listen to command events
textField1 = new TextField("", "", 15,TextField.ANY);
textField1.setLabel("Neues Autokennzeichen");
textField1.setMaxSize(10);
setCommandListener(this);
addCommand(new Command("Zur�ck", Command.EXIT, 1));
addCommand(new Command("Save", Command.OK, 1));
this.append(textField1);
/**Handle command events*/
public void commandAction(Command command, Displayable displayable) {
if (command.getCommandType() == Command.EXIT) {
MIDlet1 midlet = MIDlet1.getInstance();
Display.getDisplay(midlet).setCurrent(licencePlate);
}else if (command.getCommandType() == Command.OK){
I mean, I wrote MIDlets before and never had a problem with a textField. Or do you see anything else that has the mistake? -
Illustrator CS3 - "Not enough memory to place the file." Help!!!???
I have a new machine running XP Pro 64. Intel i7 processor, 12 gb ram.
I am trying to place a fairly small Photoshop image (with layers) into Illustrator CS3. I have done this countless times with XP 32 bit os.
But now, I cannot place even a small Photoshop image into Illustrator... I keep getting the error "Not enough memory to place the file."
I tried the suggestion of 'right-clicking' the Illy launch icon and going to properties/compatibility and then selecting "Run this program in compatibility mode for..." and then I check marked Windows XP.
Someone else said this worked in Vista 64.....but it DID NOT work for XP 64.....dang it.
Any suggestions???
ThanksOn Mon, Oct 26, 2009 at 04:37:08PM -0600, Todd-sta uttered:
Well..... I just tried the same function on my 64 bit Leopard operating system on my MacBook Pro just for kicks. Worked flawlessly!!
So, why won't it work on XP 64 bit? Is this a case of 'the mac os is just better?"
Talk about flame bait -- You trying to start the platform wars again? ;-D
Can anyone tell me if they can place a Photoshop image from WINDOWS 7 64 bit OS into Illustrator without issue? We're talking 'PLACE' .... not paste.
Don't know about Windoze 7; but that operation works in Vista x64. XP x64 is
quite flaky at times. It was never finished IMHO.
Sure would like to know. I'd upgrade if it made the difference.
LOL
end -
Not enough memory to print this document
Hello all,
I am trying to print tax forms, something I have done for years with no problem. I used a popular tax program to create a PDF file, copied this file to my G3/266 running Mac OS 9.1, and opened it using Acrobat Reader 4.0. Several pages show X's in boxes where the characters should be. I assume this is a font problem with Acrobat Reader 4.0, so I opened the file using Acrobat Reader 5.0, and all pages are rendered properly.
Once I tried to print, I remembered why I have been using Acrobat Reader 4.0: I've never been able to print from version 5.0. When printing from version 5.0, it spools to disk for background printing, then gives a warning: "Not enough memory to print this document". I tried printing the first page of Acrobat Reader's help pages - same problem. Here's a list of what I've tried:
Background printing on & off
Acrobat Memory: 12,288 KB (Suggested), 24 MB, 128 MB
Print Monitor: 16,384 KB, 128 MB
Always the same error.
My G3/266 has 768 MB of RAM
The printer is a LaserWriter Select, which is why I use Mac OS 9.1 to print.
Any ideas how to fix the font problem so I can print form Acrobat Reader 4.0 or how to make Acrobat Reader 5.0 print properly?Hello Robert,
Thanks for the reply.
In Mac OS 9, the minimum and preferred memory allocation limits may be set by the user. By selecting the application's icon and selecting "Get Info", a panel provides these fields. The application always shows a suggested memory size. Acrobat Reader 5.0 has a suggested memory size of 12,288 KB, I tried raising it to 24 MB, then again to 128 MB. My computer has 768 MB of RAM.
I used TurboTax 2012 running under Mac OS 10.6.8 to create the PDF file by selecting the "Print Returns to Mail" button. It pulls up a system print window with the PDF button, from which I select the "Save as PDF..." option. On my Mac OS 10.6.8 system, the only printer listed in this window is the "Photosmart C4700 series [B6D0EB]", but this has always been the case, and is what I have always used to print.
I have opened the PDF file, created as described, using Preview, and used "Save As..." to save a new copy, using the "Black & White" Quartz filter, since this version of TurboTax wants to use colored tax forms. This should give me a PDF that is entirely created by Mac OS 10.6.8. I have also opened that PDF file again, and done a "Save As...", using the "Create Generic PDFX-3 Document" Quartz filter. I get the same errors when I try to print either PDF file.
How does one ask the moderators to move a post?
Scott -
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 SP1Yes! 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 -
Not enough memory to save file.
I am getting this message when I try and export an AI file as .psd file. Illustrator is the only app open on a new 24" iMac running 10.5.4. The illustrator file itself is only about 5 mb. Yet . . .I get the message "Not enough memory to save file." Any thoughts, gang?
I know this is an old thread, but anyone trying to export large files out of Illustrator CS5 (maybe even CS6 and CC) still face this "not enough memory" challenge.
To summarize the above comments, this is what worked for me...
1. Using Windows 7 or Windows 8, and Illustrator CS5
2. Close Illustrator (if open)
3. Right click the Illustrator application > Properties > Compatibility (tab)
4. "Run this program in compatibility mode for:" > Windows XP (Service Pack 3)
5. "Run this program as an administrator" (optional, but recommended)
6. Apply (or "OK")
7. Open Illustrator > Open your Illustrator file
8. File > Export > (DO NOT CLICK SAVE YET...)
9. (File Save Dialog Box) > At the bottom of the dialog box, tick to select "Use Artboards" > Range "1"
10. (name your file) > "Save"
11. (Photoshop Export Options) > Select color mode > Select Resolution > Select "Flat Image" > Select "Anti-Alias
12. Click "OK"
Doing everything above allowed me to save a very large Illustrator file as a 300ppi RGB Photoshop file and avoid the "Not enough memory..." problem.
I hope this helps, but as usual: your mileage may vary... Shalom! -
Data stream from OEM device, TCP/IP "not enough memory"
Hi Everyone,
I'm trying to catch a data stream from an OEM device over a TCP/IP link. I can start the data stream, or pause/resume it, but the OEM device determines when the data stream has ended. The data stream begins, and within 20 seconds, I get the famed "not enough memory" error. Once this happens, data is lost from the stream, and quite often the final message indicating completion is missed. I see two solutions to this. 1) Watch how many bytes are backed up on my TCP/IP port, and issue a pause command until I can process the backed up bytes at which point a resume will be issued. ...or 2) Use my application's memory usage in the same manner. Does anyone know how to do either of these things?
Thanks muchHi Toader,
Thanks for your response.
1) I'm not sending any data. I'm trying to consume an incoming data stream which is being driven by an OEM device. This device basically has an FPGA hooked up to a 100Mbit/s hose. You can start it, pause it and resume it. Those are the available operations related to consuming the data stream. I think the crux of the problem is deciding when to pause the OEM device to give the LabView app a chance to process and store the accumulated portion of the data stream.
2) Sure, but it's not my program and is large and complicated. I guess I could write my own program within a program, but I would rather use the existing architecture. I might write my own micro app, but I doubt it will keep up with the FPGA driven hose. If I could detect the condition leading up to the "not enough memory" error, which it seems many LV developers have encountered, but not really solved, then I could issue a pause to the OEM device.
3) Well using a LabView application under a 2Ghz Windows box may not be sufficient hardware. But I really think it's the Windows operating system that I'm having trouble with, not the hardware platform.
I've tried several counters in the LabView application, watched task manager before/during/after the "not enough memory" error, and downloaded an interesting app called taskmanager.vi in an attempt to get something to correlate with the error message. I've not succeeded yet. Here's what I think is happening. The Windows OS is managing my wireless hardware, when it receives a TCP/IP packet, it puts it in the Windows Message que of my LabView application. I think the "not enough memory" error relates to a Windows OS allocation for my message que which is being exceeded. Any Windows programmers out there who would know how to look at the application's message que during runtime?
Thanks for your classic suggestions Toader, I may try a micro app which is spawned by the main app when its time to grab the data. My intuition is that no software limited by the Windows OS is going to keep up with single minded FPGA hardware.
I thought this very interesting discussion was the answer and it may still be, but after trying 30+ various counters under Memory, System, Process, TCP, and Server, none correlated to the error.
http://forums.ni.com/t5/LabVIEW/System-monitor-counter/m-p/1653448/message-uid/1653448/highlight/tru...
I also tried a taskmanager.vi, but none of the various flavors of memory tracked by that little gem correlated with the error either. At this point, I started to wonder "what memory was there not enough of?".
Terry -
Building exe file fails (not enough memory) in LV 2011
Hello,
I have a project with about 900 VIs. I'm using Win7 32 Bit with 4 GB RAM (a 32 Bit OS can address about 3,3 GB) with LabVIEW 2011 SP1.
When trying to build an executable, I allways get the error "Not enough memory to complete the operation" (or something like that).
My RAM is full at this time.
Without building the exe file I can start the project without any problems and with only half RAM usage.
What can I do to generate the exe file with my system?
Are there any options I can set, that the application builder will not use so much memory?
Regards
MatthiasHello
"how much memory do those 900+VIs take on disk????"
53 MB
"Ctrl+Run Button is a force compile for a single VI"
I used Ctrl + Shift + Run
I also tried the mass compilation tool itself and it doesn't change anything.
"If the source distribution also plows the memory, you want to split the distribution into several packages"
That sounds very coimplicated ...
Did I understand it correctly? I have to create several source distributions (option "directory" and not "llb"). And in my build specification for my exe file, I can chose these source distributions?
Do I need to prepare my VIs or can I directly create the source distribution with the option "remove block diagram"?
"I had that problem several times in a large project. I did a mass compile, saved all the VIs, then closed out of the project and LabVIEW. I opened up LabVIEW again and loaded only the main VI. I performed a build and it worked successfully."
I tried it and a still get the same error.
My customer need to get the update because it a critical one. And I can't build it.
An update to Win7 64 bit on my machine is also not a solution because all our customers use Win7 32 bit and the 64 bit executable won't run on a 32 bit operating system.
Regards
Matthias -
Lightroom 5 "not enough memory" error message
After using Lightroom 5 for several months I started to have the message "not enough memory" during the export action. It started to appear ones in a while, then it became more frequent and now it comes in every single photo exported.
I wonder if it is related to the library size as the only thing that changed in my computer since I started to use Lightroom is that I have increased the amount of pictures.
I run Lightroom out of my hard disk and I store the raw files as well as the modified jpg pictures in an external hard disk. Both have enough space and the core memory size has not changed since the beginning. I try not to run any other program at the same time.
I have seen that there are several discussions on this subject but it goes normally to increasing the size of the memory but it doesn’t explain why at the beginning the export was done very quickly and without problem and why the problem increased with the time (and with the size of the library°
Is there a way to manage the library size?I have found a Work Around without changing or revamping my computer.
As I have noticed that the problem came slowly after several months of using Lightroom I suspected that there was something accumulating in the memory space needed for the program. From the left menu bar where I had all of the imported files, I deleted the folders that I'm not using currently; this action didn't erase the files in the hard drive but deleted them from the program's memory.
I noticed that now the program needs less memory space during normal use (developing) and when I do an export, the peak of memory usage that is needed for the operation does not reach the available memory space.
Maybe you are looking for
-
Bridge Help | What's new in Adobe Bridge CC
This question was posted in response to the following article: http://helpx.adobe.com/bridge/using/whats-new.html
-
'iTunes has stopped working' error message on iTunes startup with vista
Today i downloaded iTunes 7.1, i opened it and all seemed well, i played a few tracks etc. but, when i plugged my ipod in i was told that iTunes has stopped working, i tried to open it again, but the same message pops up. so i restarted the computer,
-
How can you tell if a thread can't get a lock on an object immediately?
A thread wishes to synchronize on an object called obj. When it hits the line synchronized (obj) it has to wait as another thread holds the lock. I want some code to behave differently if it cannot get the lock immediately. Is there a way to tell if
-
Dreamweaver template not updating Contribute pages
Currently I'm trialing Dreamweaver (MX) and Contribute (3.11), to check that it's a workable solution for my company, in terms of editing and auditing, but right now I'm having a problem. I have some templates (.dwt files) that I create in Dreamweave
-
How to turn of the display (ThinkPad Edge E540)
Hi, I bought a new Lenovo ThinkPad Edge E540. My Question is, how can I turn off the display? There is no FN-hotkey for it. Or is it possible to change the functions of the FN-hotkeys because I don't even need two of them? I hope someone has an answe