Logic Snowballing Memory bug

I am encountering the strangest bug. It seems to occur when I click on a track - that's it. It is happening so often that I just cannot work!
I click somewhere usually and then Logic freezes, I look at the Real Mem in Activity Monitor and it is growing and growing until Logic crashes at around 20 GB. I have initialized preferences, repaired disk permissions, I'm now running from a clone, but it just occurred in that!
I cannot think what could be causing this. I would appreciate any help.
Thx
Felix

I think it might have something to do with the Kontakt Memory settings?
Absolutely... if you have Kontakt's Memory Manager turned on...?
It needs to be turned off when using it with a 64 Bit Application like Logic Pro X... as OS X and Logic handle all memory..... and that setting is only needed when running Kontakt with either a 32bit DAW or.. when using Kontakt as a Standalone app....
So, if it's on, turn it off in Kontakt's settings...and restart your Mac and then test.....

Similar Messages

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&#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.

Oracle 8.1.5 Memory bug!?!

Hi !
I have a serious problem concerning the use of Oracle as db for upcoming projects.
Current situation:
- Platform: Windows NT 4.0 server
- DB: Oracle 8.1.5
- JDBC: 1.1 which comes with the Oracle 8.1.5
Problem:
- I have developed an ServletBased web-app. which has the capability to upload images (blob) and text into the db and then to stream out the images and write the text from there into a Servlet generated webpage.
After running the app. for about 10 minutes the virtual memory usage suddenly starts rising about 2-10 megs./second.
I have optimized my code and closed every resultset, statement, connection, input&outputstream, etc.
I would say that the application is fairly optimized by now but this crash still happens.
Could someone please confirm that this is actually a known problem with the Oracle db?
I have seen many messages concerning the same problem but so far have seen no good explanations.
If there is no hope for a solution I have to change the db for something else, which is no way a desirable action.
B.R. Kalle

Please refer [url http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/conditions10a.htm
]'Patterns Without % Example' on Oracle9i SQL Reference.
Here is [url http://download-west.oracle.com/docs/cd/F49540_01/DOC/server.815/a67779/operator.htm#997970]Oracle8i SQL Reference.
If a pattern does not contain the "%" character, the condition can be TRUE only if both operands have the same length.
So... there are bugs on 8.1.x, 9.2.0.4...
SQL> select * from v$version where rownum <= 1;
BANNER
Personal Oracle7 Release 7.3.2.3.1 - Production Release
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
no rows selected
SQL> select * from v$version where rownum <= 1;
BANNER
Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
COL1
xyz
SQL> select * from v$version where rownum <= 1;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
COL1
xyz
SQL> select * from v$version where rownum <= 1;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
no rows selected

Awful memory bug

A few days ago my computer started to not reuse inactive ram, which has led to incredibly low performance.
After a minute or two, the ram is usually full (and I have 4GB), and it starts to swap like mad. Sometimes it takes ten seconds or so to bring a Safari window to the front, or more than 30 sec to bring Photoshop to the front (it's running in the background!).
Strangest thing is, I have absolutely no clue why this started. I didn't install an update, and I didn't start using any new software.
Has anyone a clue how to fix this? It is immensely annoying.
Thanks, Julian

Hi, and thanks for the tips so far.
I have of course cheched the Activity Monitor (it shows all processes), and there is none using over 100MB. I didn't take the time to sum them all up, but it's obvious it's less than a GB.
Virtual memory is normal as well.
The active & inactive memory just grows huge after some time. Way too huge.
I've had a chat with the developers of Transmission, while using that app the problem is especially big, because it has so much memory throughput. (It does happen with any app though.)
They told me, that it's a bug that more Os X 10.5.5 users are experiencing... but I haven't found any reports so far.
@nerowolfe: That could also be... but it would be a very strange kind of faulty memory. Because even though it decreases my computer's speed from Bugatty Veyron to Citroen 2CV, it hasen't yet managed to crash it. (I have lots of HD space to fill :-)).
I'll just try it.
Thanks again, Julian

Logic (Finder Window Bug)

Greetings,
While most things are working well in Lion, I am starting to see its flaws little by little. Such as ichat not able to receive audio if I initiate video chat.
The more I use Lion, the more I am starting to regret it. Just out of curiousity, is anyone else getting this bug on Logic? Please let me know if you do, just so I don't feel like perhaps Apple dropped the ball only on me this time.
The bug, at least to me, seems to be on the finder window for Logic. For example, if you open a new project with (Command+O) or load samples into EXS or Ultrabeat. I get this massive space inbetween the right column and the file browser. Example below.
No matter how many times I re-adjust the columns, it always reverts back to the space. Kind of kills workflow if you really widen the window to access your drives and content. You lose a few inches of screen real estate that gets to be pretty major after several hours of working.
If you get this bug, we better start voicing it to the Logic team, as 9.1.5 did not fix the problem. I'm giving Apple one more chance with 10.7.1 or 10.7.2 before it starts to become a problem. And I'm talking about the big picture, not just a finder bug.
Here's hoping.
Cheers
LGK

You know, allot of these problems will never be addressed at this point. The workflow and intuitive usage suffers plenty with these bugs. However, at the stage its in, Logic X (Garageband pro) is right around the corner, so apple doesn't see the point in fixing obsolete software. I'm jumping the gun on expecting apple to drop the ball on Logic, but with their current "Pro Apps" track record, you'd have to be a little foolish not to think that.
In my opinion, and I must be clear, my opinion, apple no longer sees any profit in supporting their professional customers. Too many non-creative humans are fattening their pockets with plenty of cash from useless non-pro audio apps for idevices.
I don't blame apple, afterall, its all about the money if you're a corporation right? We have other choices, lets just go there. Apple won't miss us, not one bit.
As for the finder window bug. Its still there after 10.7.3 and 9.1.6. It will be there forever along with all the other bugs as it has for years now. Remember, you don't have to live with it. Lets not be lazy and start packing our bags. Its time to go.
LGK

Dreamweaver CS4 attempted to free unallocated memory bug

Dreamweaver CS4 Mac version 10.0.0.4117 has a fatal bug. It is trying to free up unallocated memory. Most likely, it is trying to free the pointer twice, which ended up attempting to free memory that does not belong to it. This corrupts the system memory, and bring down Snow Leopard, causing the notorious freeze problem in Snow Leopard.
See the system log, right after Dreamweaver crashed, it corrupted the system memory, causing Safari to freeze right after that:
Mar 30 14:08:32 Dreamweaver[505]: Dreamweaver(505,0xa0aae4e0) malloc: *** error for object 0x2fac3a90: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 14:08:32 [0x0-0x32032].com.adobe.dreamweaver-10.0[505]: Dreamweaver(505,0xa0aae4e0) malloc: *** error for object 0x2fac3a90: pointer being freed was not allocated
Mar 30 14:08:32 [0x0-0x32032].com.adobe.dreamweaver-10.0[505]: *** set a breakpoint in malloc_error_break to debug
Mar 30 14:10:23 Safari[216]: Periodic CFURLCache Insert stats (iters: 1107) - Tx time:0.285461, # of Inserts: 16, # of bytes written: 276255, Did shrink: NO, Size of cache-file: 181460992, Num of Failures: 0
Here is the log that shows the repeated error:
Mar 30 15:28:33 [0x0-0x47047].com.adobe.dreamweaver-10.0[887]: objc[887]: Class ApolloPasteboardSource is implemented in both /Applications/Adobe Dreamweaver CS4/Configuration/Flash Player/AuthPlayLib.bundle/Contents/MacOS/AuthPlayLib and /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver CS4.app/Contents/Frameworks/AdobeOwl.framework/Resources/AuthPlayLib.bundle/Contents/MacO S/AuthPlayLib. One of the two will be used. Which one is undefined.
Mar 30 15:28:34 /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[891]: Started - This service performs licensing functions on behalf of FLEXnet enabled products.
Mar 30 15:28:57 com.apple.WebKit.PluginAgent[782]: Debugger() was called!
Mar 30 15:29:33: --- last message repeated 2 times ---
Mar 30 15:29:33 [0x0-0x47047].com.adobe.dreamweaver-10.0[887]: Dreamweaver(887,0xa0aae4e0) malloc: *** error for object 0x333e5dc0: pointer being freed was not allocated
Mar 30 15:29:33 [0x0-0x47047].com.adobe.dreamweaver-10.0[887]: *** set a breakpoint in malloc_error_break to debug
Mar 30 15:29:33 Dreamweaver[887]: Dreamweaver(887,0xa0aae4e0) malloc: *** error for object 0x333e5dc0: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 15:29:57 [0x0-0x49049].com.adobe.dreamweaver-10.0[912]: objc[912]: Class ApolloPasteboardSource is implemented in both /Applications/Adobe Dreamweaver CS4/Configuration/Flash Player/AuthPlayLib.bundle/Contents/MacOS/AuthPlayLib and /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver CS4.app/Contents/Frameworks/AdobeOwl.framework/Resources/AuthPlayLib.bundle/Contents/MacO S/AuthPlayLib. One of the two will be used. Which one is undefined.
Mar 30 15:29:58 /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[916]: Started - This service performs licensing functions on behalf of FLEXnet enabled products.
Mar 30 15:30:20 Dreamweaver[912]: Dreamweaver(912,0xa0aae4e0) malloc: *** error for object 0x32bb42f0: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 15:30:20 [0x0-0x49049].com.adobe.dreamweaver-10.0[912]: Dreamweaver(912,0xa0aae4e0) malloc: *** error for object 0x32bb42f0: pointer being freed was not allocated
Mar 30 15:30:20 [0x0-0x49049].com.adobe.dreamweaver-10.0[912]: *** set a breakpoint in malloc_error_break to debug
Mar 30 15:30:37 [0x0-0x4a04a].com.adobe.dreamweaver-10.0[942]: objc[942]: Class ApolloPasteboardSource is implemented in both /Applications/Adobe Dreamweaver CS4/Configuration/Flash Player/AuthPlayLib.bundle/Contents/MacOS/AuthPlayLib and /Applications/Adobe Dreamweaver CS4/Adobe Dreamweaver CS4.app/Contents/Frameworks/AdobeOwl.framework/Resources/AuthPlayLib.bundle/Contents/MacO S/AuthPlayLib. One of the two will be used. Which one is undefined.
Mar 30 15:30:37 /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[946]: Started - This service performs licensing functions on behalf of FLEXnet enabled products.
Mar 30 15:34:58 osascript[1018]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:\n /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
Mar 30 15:35:03 com.apple.backupd-auto[1012]: Not starting scheduled Time Machine backup - time machine destination not resolvable.
Mar 30 15:35:48 osascript[1033]: Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:\n /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper
Mar 30 15:35:58 Dreamweaver[942]: Dreamweaver(942,0xa0aae4e0) malloc: *** error for object 0x3332c4b0: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Mar 30 15:35:58 [0x0-0x4a04a].com.adobe.dreamweaver-10.0[942]: Dreamweaver(942,0xa0aae4e0) malloc: *** error for object 0x3332c4b0: pointer being freed was not allocated
Mar 30 15:35:58 [0x0-0x4a04a].com.adobe.dreamweaver-10.0[942]: *** set a breakpoint in malloc_error_break to debug

If you are trying to report a bug, this is not the place for it. This is a user to user Forum. Bug reports go here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
If you are giving a heads-up to fellow Mac Users, so be it.
If you are trying to get support to extricate yourself from what looks like a really aggravating problem, go to http://www.adobe.com/support/contact/ and choose your favorite means of conversation with Adobe Support personnel.
Beth

Does Oracle occi have any memory bugs when writing blobs using streams?

The function below will produce some kind of memory corruption that will cause an exception (which cannot be identified since memory is corrupted) while doing another call:
ora::Statement stmt(__cn);
string sql("BEGIN Pckg.Sp_procA(:1, :2, :3, :4, :5, :6, :7, :8, "
":9, :10, :11, :12, ":13, :14, :15, :payload); END;");
occi::Blob payload(__cn.getConnection());
occi::Environment* tempEnv = occi::Environment::createEnvironment();
occi::Timestamp reportTime(tempEnv);
reportTime.fromText(__report.report_time), "yyyy-mm-ddH24:mi:ss.ff");
stmt.setSQL(sql);
stmt.setString     (1, "");
stmt.setString     (2, "");
stmt.setString     (3, __report.varA);
stmt.setString     (4, __report.varB);
stmt.setInt          (5, __report.varC);
stmt.setString     (6, __report.varD);
stmt.setString     (7, __report.varE);
stmt.setString     (8, __report.varF);
stmt.setTimestamp(9, reportTime);
stmt.setNull     (10, occi::OCCITIMESTAMP);
stmt.setString     (11, __report.varG);
stmt.setString     (12, __report.varH);
stmt.setString     (13, __report.varI);
stmt.setString     (14, __report.varK);
stmt.setString     (15, __report.varX);
stmt.setBinaryStreamMode(16, __report.payload.Size(), true);
stmt.executeUpdate();
occi::Stream* streamedData = stmt.getStream(16);
streamedData->writeLastBuffer(__report.payload.GetPtr(), __report.payload.Size());
stmt.closeStream(streamedData);
occi::Environment::terminateEnvironment(tempEnv);
return true;
The function below works perfectly unless the code above is executed and looks like this:
ora::Statement stmt(__cn);
string sql("BEGIN "
"Pckg.Sp_procB(:1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11); END;");
occi::Environment* tempEnv = occi::Environment::createEnvironment();
occi::Timestamp reportTime(tempEnv);
reportTime.fromText(__report.report_time, "yyyy-mm-dd HH24:mi:ss.ff");
stmt.setSQL(sql);
stmt.setString     (1, "");
stmt.setString     (2, "");
stmt.setString     (3, __report.varA);
stmt.setString     (4, __report.varB);
stmt.setInt          (5, __report.varB);
stmt.setString     (6, __report.varD);
stmt.setString     (7, __report.varE);
stmt.setString     (8, __report.varF);
stmt.setString     (9, __report.varG);
stmt.setTimestamp(10, reportTime);
stmt.setNull     (11, occi::OCCITIMESTAMP);
stmt.executeUpdate();
occi::Environment::terminateEnvironment(tempEnv);
return true;
I got the blob insert example from Oracle's documentation and can't see anything wrong with it. The second function also seems to be ok which got me thinking that Oracle's occi might have some kind of bug that corrupts memory. Anyone knows anything about this or has done anything similar?

Does anyone insert blobs this way? Or just using the "insert -> select for update" way?

Why does Logic 9 memory seem to cap out at 1.5-1.7 GB?

running in 32 bit obviously... I thought the 32 bit max was closer to 2.5-4 GB?
i start getting errors at 1.5. Is there any way to eek out that extra gigabyte?
thanks

Using iStat menu 3 to monitor memory usage. a great and cheap utility if you haven't heard of it. Basically as soon as L9 hits 1.5 I get a memory low message and then at about 1.7 functionality goes out the window. I wonder if the 4 GB cap includes some kind of virtual memory that Logic is also grabbing onto via disk space. I have 16 gigs RAM on a 2.93 octo Nehalem. I'm using VEP as well... but sometimes its nice not to have to deal with that part of the equation.
I've toyed with 64 bit a little...but I rely pretty heavily on 32 bit plugs like Waves and Soundtoys. and from what I've read stability is weak with the bit bridge although I can't confirm that.

Logic 9 - Memory Overload - Out of the blue / all of a sudden

I have been working with Logic Pro for about 4 years on a circa 2007 iMac (2 Core, 2GB RAM), 10.9.4 - and have produced about 30 projects - ranging in total number of tracks from 12-36; medium use of plug ins and always Bus Space Designer.
I would get the Overload Message intermittently over the years, but could solve that by closing anything else running on the machine, restart Logic and be back in the game. Everything seemed to work very well for years. I have not made any changes to the set up, either Logic or the machine, apart from latest software updates, etc. When I started Logic today, I can't even play a project; I have tried to Play several projects, some with very few tracks, some with heavier tracks; both crash after about 15 seconds of play.
I have run Clean My Mac2, emptied the trash, etc. I realize that my RAM is very low, but I can't work out why this has happened all of a sudden. Any advise?
Thanks.

Hi John,
1) Dont use anything.. OS X can take care of itself...
2) It's Firefox.. As you have found out it can really hog resources....I would suggest you uninstall it and use Safari... unless you have a really good reason not to do so...
2a) What is Escrow Security Alert.app? (Its part of Mavericks/Keychain and its not using any real resources of note so no worries..)
3) Ok.. so it's a System Overload and thats likely being caused by Firefox as others have reported....
4) Growl is a program that puts msgs being reported by other apps, up onto your screen. Not really needed these days thanks to OS X's own notification system...
http://growl.info
http://growl.info/documentation/growl-package-removal.php
5) Absolutely yes... Personally I'd add more if you can....(I think your Mac might actually take 6GB...) Check with OWC to find out for sure... as Apple often state low minimums for memory when the hardware can support more than is officially listed..
https://www.macsales.com
...as the more memory, the better the system operates I've found.... 2GB is the absolute bare minimum when running 10.9 and Logic.. and is going to make your Mac under perform for sure... Make sure you are running Logic Pro 9 in 64bit mode to make use of the extra memory above 4GB...
Crucial is fine for memory.. so long as it is the exact correct type for your Mac Model...
Final tip: Make sure nothing is running in the background when running Logic.. Quit all other apps.... including any apps that launch on startup....as your Mac is unpowered as it is for use with modern OS X versions.. (The modern OS X versions make much higher demands on the hardware.. which is why many of us using older Macs.. use Snow Leopard along with Logic Pro 9 whenever possible) so ensure you provide all the CPU/Memory resources you can when running Logic...
Cheers..
Nigel

Logic volume fader bug/glitch

Basically, I was on Logic Pro 9 earlier this evening. Having a bit of a jam and what not. I was happy with what I had so far so I saved it and went out. Once I got home I fancied popping back onto Logic for a bit. When I opened up the project I couldn't help but notice that one of the volume faders was up and was moving up and down a tiny bit. (Between +5 and +6). At first I thought it was dodgy automation so I went and had a look and that wasn't the problem. I started to look into other faders and what I found is that every time I clicked on a fader they would do the same bug/glitch. I've tried all sorts to resolve this issue but nothing seems to be working :/
Thanks for reading c:

ItchyDez wrote:
... every time I clicked on a fader they would do the same bug/glitch. I've tried all sorts to resolve this issue but nothing seems to be working :/
Thanks for reading c:
This usually points to a MIDI control surface malfunctioning and sending out errant messages. Unplug devices to confirm.

Have you encountered this Lion\Logic desktop switching bug yet?

This is on 1.7.1, still a bug but different than what happened on 1.7
Let's say I have 3 desktops and open Logic in desktop 3 then full screen enable it. If you now initiate mission control, you will see 3 desktops AND the full screen Logic). Now let's say I swipe to desktop 3, Logic will now be visible with the menu bar on top of Logic (still in full screen mode). Swipe to desktop 2 and Logic is not visible. Swipe back to desktop 3 and Logic is visible with the menu bar on top of Logic (still in full screen mode). Swipe back to desktop 2 and Logic is visible with the menu bar on top of Logic (still in full screen mode).Swipe to desktop 1 and Logic is visible with the menu bar on top of Logic (still in full screen mode). Swipe all the way to where the full screen app should be (to the right of desktop 3) and all you see is a grey screen (in 1.7 it would be the linen background). Now you have to swipe back all the way to desktop 2 to see Logic. Guess what? Swipe to desktop 2 and Logic is visible.
You get the point.
This does not seem to happen with the native apps in full screen mode.

facing the same epic fail issues since i bought my mac pro with Lion preinstalled and downloaded (ARGH!) Logic Pro 9 ... using an apogee rosetta as i/o and wordclock via optical .. never a problem with a G5 and Tiger... lion and logic f*** up everything (workflow?! what exactly was that?) ... constant digi-clicks tell me that the apogee clock ist ignored, logic produces a klick with constant dropouts only and no way to sync audio to the click or whatever .....
worst is: they (e.g. apple) keeps us from downgrading to Snow Leopard, no help, no support, no responsibility ...

Logic's Biggest Bug - Anyone got a workaround?

The problem is importing WAV's with Long Filenames into the Audio Window, & then EXS sampler keys.
In one of my previous posts I explained that I lost all my work since purchasing Logic Pro last year (100+ logic songs), after I formatted OSX and then setup the exact same file structure, and Logic Plugins.
HOWEVER.
Logic didn't care to reference the actual original long filenames, it just remembered the first few letters of the file, with bogus numbers afterwards for example "Longfilena#342543.Wav"
I asked around for help, and "remake it all with shorter filenames" seems to be the standard answer.
Apparently this has been a problem for years, and they will never fix it.
IS THERE A WORKAROUND??
I am really deflated into making anything new, Because KNOW I will lose it again.
Or alternatively can someone explain why i paid $1500 AUD for a program that cant do stuff garageband can do? Just kidding, but as if the Logic programmers will ever magically release an update that fixes this problem.

This is a real problem with Logic.
It's not the drive, it's not the drive format, it's not the OS.
This same problem with long file names has happned to me in the recent past. It happend to me right now with this example as I write this.
It happened with Apple's own Apple Loops from the "Jam Packs".
The drive is formatted as it was when this MBP was new =
Mac OS Extended (Journaled)
Example...
The apple loop file from jam pack 2 --> " 2- Downtempo Mellow Piano 02.aif"
has 34 characters in it (there is a space at the front and two spaces before the D)
and this is the way it was installed by the jam pack)
That file will import into LogicPro7 and it will be fine for a while.
Maybe a month later I will open that Logic Song and Logic will not be
able to find the file because it's looking for ...
" 2- Downtempo Mellow#CA4D7.aif" and I will have to locate the file manualy
and guess / try to remember if I used the Piano 02 or Piano 01 because I can't
tell what the name is because it's garbled in the logic window.
Logic seems ot support only files of 31 characters or less.
This I know from trying to save a file with more than 31, logic will tell you it can't do
it and to name yoru song (or audio take) with less characters.
To see this garble file name syndrome, simply import the file " 2- Downtempo Mellow Piano 02.aif"
(or any file with more than 31 characters) and then save that logic Song file, quit logic.
Launch Logic and open that logic Song file and in the Audio window the name
of that audio file will have chaged to this...
" 2- Downtempo Mellow#CA4D7.aif"
However, luckily logic did find the file on it's own somehow.
This is on a MBP OS 10.4.10, no external files.
Now shorten the file name to 31 characters and do the above again.
Logic then does not change the file name in the audio window.

(Un)Logic Audio Graphik Bug

Hello from Berlin.....
Need your help or advices on my big problem with Logic. The program changed from one moment to another many of the colors to black. I installed Logic new, no change. I installed OSX new - no change.
any hints ?

That is weird indeed. Maybe you should defrag the drive you're recording to. Sometimes drives can get pretty messed up and they will record a single file all over the disk resulting in a file with hundreds of fragments which will put a lot of strain on the HD heads.
Just a thought - check out iDefrag...
http://www.coriolis-systems.com/iDefrag.php

LV2012 Out of Memory Bug when Clearing Compiled Object Cache

Here is some LV2012 weird behaviour when clearing the compiled cache and having a project with source code separated from the binaries.
Steps to reproduce:
1. Open a VI in a fairly large LV project
2. With the VI open, clear the compiled cache:
3. Close the VI.
4. Open the VI
5. Watch the broken arrow and the LV Out of Memory bogus.
Br,
/Roger
Solved!
Go to Solution.

Norbert_B wrote:
Roger,
i tracked down the issue to "ExecutionBenchmark1.lvclass:Load Core.vi" and "ExecutionBenchmark2.lvclass:Load Core.vi". If removing both VIs from the main, it is compilable.
Since those VIs have their blockdiagram removed, they have to include their compilation in order to be executable. I expect this to be the source of the issue.
Can you please check if using the default VI "Load Core" for both classes work as long as LV is able to recompile those while creating the object file for the main?
thanks,
Norbert
Yep, still reproducible on my 32 bit Windows 7 home machine. Attached is the fixed code.
Also, my suspicion was right. If you try to save a project in a out of memory condition, the saved project will always display an out of memory error due to a missing block diagram.
Br,
/Roger
Attachments:
Execution_Fixed.zip ‏415 KB
Missing_BD.zip ‏419 KB

Memory Bug ?

hi, i have asha 300, and i have this problem, when i try to copy soemthing on my SD card it says "no free space"
but theres like more than 3/4 of free space, you can see that here http://prntscr.com/2aogx1, this is the message i get http://prntscr.com/2aoils
i can't save files on memory card using any program, or recieving files from another mobile via bluetooth
any solutions ?

1.
Backup all files on your memory card to PC and format it on your PC and insert it back in your phone and try again.
2.
Try with another memory card on your phone.
3.
Try to connect your phone in mass storage mode using a USB cable and try to copy some files and see.
4.
Also try to connect your memory card using a card reader and copy some files, if it doesn't copy properlly on you PC, the card might be damaged and you may need to buy a new one.
Hope this helps.
-------------------If this post helped you, click on accept as solution.------------------
-----------------------------Appreciate by clicking on white star.----------------------------

Logic Snowballing Memory bug

Similar Messages

Maybe you are looking for