lethalrush

More importantly, is there a solution? Maybe there is a swap file that Logic writes these settings to during loading and unloading of project data when multiple projects are open. Can I trash this swap file? If so will it restore my initial settings?

Okay so I had a project file open. Then I opened another project file to quickly render out something from it. When I returned to my original project file, all of my Kontakt and softsynth settings were completely changed. Both project files use a custom template that I created with my sampler and softsynths all pre-loaded into autio instrument channels. I didn't save the project and closed everything, then re-opened my project file, and still the settings were messed up. I opened an older version of my project and the plugin settings were still messed up! (??) I came here looking for answers. I found this. http://www.logicprohelp.com/viewtopic.php?p=240360#240360 Is that what's happening? Anyone else have this problem? I just permanently lost a massive project and its backup too. 10.4.11 8.0.2

Logic is really slowing down a lot, especially lately. In a brand new project file it's fine (10% sluggish, which unfortunately I now consider "normal"), but after working for a while, and adding a modest amount of plugins, Logic slows to a crawl. Sometimes it actually gets in the way of my workflow. I have to press down to click for almost a second to get logic to respond to anything; buttons, faders.. if I want to rename a channel, that takes about 2 seconds of wait. Scrolling around a page, zooming in, out, all slow... Is there any way I can speed this up? Seriously, I LOVE Logic, but lately, it's been showing me way too much of it's bugs... like muting all channels *every single time* I add any insert/send/instrument when in solo mode, necessitating unsolo+re-solo to wake it up. Or incorrectly displaying the contents of an arrange page, necessitating manual screen refreshes (like zoom in+zoom out)... but i digress I'm running Logic 8.0.2 w/ MOTU UltraLite; dual 2.3 G5, 10.4.11, and 3GB RAM. I have a decent amount of free space on my drives. I haven't installed too many extra system plugins.. have the standard OSX optimizations considered, like disabling dashboard, etc...

When I add a new insert in a channel or create a new bus, and I am in Channel-Solo mode on a bus (yellow solo button on strip), that soloed bus/track suddenly stops producing output. A solution is to solo/unsolo that track, or any other track whatsoever. Is this my set-up or is this just an incredibly annoying bug? This happens to my friend's Logic setup as well, and we use entirely different templates. Logic 8.0.2

Thanks!

I have a rock album to mix + master. Should I load all the multitracks into one massive Logic project file, or each into separate project files? If into one big Logic file, how would I set them up? (i.e. sequential in time, or each track has it's own set of channels (thus ending up in 160+ channels in the project file) facts: - every 2 songs out of the 12 are recorded with the same mic placement / room setup; which means 6 different mic placements for 12 songs. (which means i need at least 6 different EQ / dynamics insert sets per mic/group) - all songs must sound similar in terms of overall master since it's an album (obviously) - benefits: sharing of buses / sends for fx for uniformit across songs in the album - drawbacks: may lead to extremely disorganized and confusing layout (using Logic 8) Thanks!

Yeah, this exact thing has started happening to me too. Not as frequently as you. It's extremely aggravating - totally kills your flow. It also doesn't respond to apple-S, which I keep being reminded of when restarting Logic and realizing my last few changes were NOT saved; thus forcing me to not only stop my workflow but redo some of it. Good times.

I would personally re-record everything if possible, and do it all in one session. That way you won't get tonal difference from the two takes with two physical setups.

Or create a new track in the arrange page and then drag the Bus object from the Environment over and drop it onto the track, to replace it.

Okay thanks a lot; But won't there most definately be phase issues with two takes as well? It's the same instrument playing the same notes. Yes there will be many subtle variations between each, but ultimately they are the same general waveform. I recorded two takes of the same part, panned them, and then Guitar Rigged them with the same preset on Left, and then another channel with exact same preset on Right, and it sounds super-phasey... ?? Great description of your reaction from a string section.

I have a single DI guitar take pumped into a bus feeding three auxes. The auxes each have a different Guitar Rig config on them and together I have a really good sounding tone. one aux is dead center, one panned left 25 pts, one right 25 pts. However, listening in the car reveals extremely weird phase issues, and examining the waveform verifies this (though I'm not certain what an acceptable difference in phase between left and right channels for a distorted guitar tone would be). Sliding the right channel a few samples here or there doesn't solve the problem. Any suggestions?

In terms of CPU load and memory, how does Logic manage? I am currently working on a project which is so big it is composed of two completely separate Logic files. In one I manage the bass, vocals, and strings, and the other file the drums and atmospheric fx. I can't have them all in one file; I can barely play back both separate files without crackles and CPU overloads. I constantly make adjustments in one, bounce down the whole track, close, and open the other file, import, and then press play to see how it sounds. Then close, go back, readjust, bounce, go back..... One solution I can think of is to bundle all the sections (drums, bass, vocals) into folders, and then mute those folders in the arrange and simply play an audio track of the bounced contents of those folders, to make having to make changes more quick - within the folders. But muting these folders barely reduces the CPU load. The only other solution is to actually bypass all the plugins and softsynths on the tracks within the folders when not in use, then enable them again when in need. Is there any other solution? my question is, when does logic disengage CPU/memory for tracks? Obviously when you bypass stuff - but what about when you mute the fader in the environment? or in arrange? or in solo mode? muted folder.. etc.. I don't necessarily want to freeze tracks because there are a lot of audio tracks as it is, and adding more causes Disk throughput failures.

Logic Pro keeps suddenly refusing to respond to keyboard messages. I'm working with a huge project file. The only way to fix it is to close the project and reopen it. And then the keyboard stops responding in about 30 seconds, so I have to close and repoen it again, over and over. I can't mute, solo, record, start, stop, nothing... What's going on? The only thing that is different then other times when I use Logic is that this project file is huge - lots of audio tracks (not many plugins though.) -- Logic 7.1.1 OSX 10.4.9 Dual 2.3 G5, 3GB RAM.

Yes...

^bump?