Logic 9 messing up 8?

I've been experimenting after installing L9 on my laptop, and in addition to its own mysteries, it seems to have coincided with some new weirdness in L8 on the same machine.
Just one small example - I cannot toggle Transport view with key command in L8.
Another - function buttons on Transport either don't illuminate, or stay lit all the time in L8.
And to repeat a word of caution posted by another - if you open and save an L8 song while L9 is running, next time you open it in L8 you get a warning that it could be messed up, and you must upgrade to L9.
Also, L9 seems to erase the Undo History with song closure.
All of this, and more, makes me very glad I have not, and will not, install L9 on my studio computer.
Although L9 has a few nice features, some of these should have been an L8 upgrade anyway (like auto-naming recorded files with the song name - about time!). Not nearly worth the risk to upgrade at this time if you use Logic 8 professionally, IMHO. Can Apple or someone reassure me?
I doubt it. Maybe down the road.

no it seems more than this, i left it for 15 minutes and still nothing, whats even more odd if i load another project it asks me if i want to close the current one (the one that never loaded) i click know and when the new one begins to load so does the initial project/template???

Similar Messages

Logic is messing up imported audio

In Logic 8, when I try to import an audio (aif) file exported from Ableton Live, Logic slows down the audio file significantly. It also lowers its pitch.
The track from Ableton Live was at 160bpm, and even when I set Logic's project tempo to 160bpm, the audio file plays back at less than half that tempo. I feel like I'm overlooking something really obvious, but I'm having trouble finding the solution anywhere. How do I import the audio file without Logic messing things up?
Also, Quicktime or any other music player plays the exported audio back fine, at the proper pitch and tempo. It seems like the problem is only with Logic.

I think Jim is on the right track--sounds like sample-rate mismatch. Try setting Logic to automatically convert the rate. Or, of course, set your Logic project to the same rate as Live.
Does this work?

Problem with Logic Pro and Soft eLicenser on Mountain Lion?

Hi!
I have a bunch of Arturia synths, which requires the Soft eLicenser to work. This has always worked great with Lion, never any problems with eLicenser (never had to open it etc.)
Now - I upgraded to Mountain Lion, and tested my synths to make sure everything was OK, experienced a bunch of problems, and did a full recovery to clean Mountain Lion.
After installing the Arturia synths, and adding my licenses, I installed Logic. Everything worked fine!
BUT!
When I closed an Arturia synth within Logic, or closed Logic after running a project with one of these synths, I couldn't reopen any of these synths within Logic afterwards - In fact, I couldn't open the stand-alones either! And when I tried to open the eLicenser Control Center, it would just say "Reading eLicensers" forever. After a reboot, everything is OK.
I can open and close eLicenser Control Center and standalone synths as many times as I want, as long as I don't open Logic, and then Arturia synths as an AU in Logic.
I found a workaround: Open the eLicenser Control Center, and let in run in the background (cmd+H), and then open Logic. Then I could open Arturia synths and close them, close Logic and reopen etc. without any problems at all. NO PROBLEMS.
Until I close the eLicenser Control Center, then I have to reboot to be able to start it again.
I hope you understand what I mean here. It's a bit hard to explain.
In short terms: Logic makes Soft eLicenser crash when a eLicenser synth has been opened as an AU.
The same problem is when scanning the AU with AU manager. eLicenser window should be open before scanning.
Does ANYBODY have the same problems? Can anyone who has these applications test it out?

So it definitely seems to be a issue with Logic.
I can't force this error in 10.7.X no matter how hard I try, but in 10.8.2 it's definitely Logic messing things up.
Could it be auvaltool which has a bug? Or is that only run with AU manager on validation?
Hopefully this discussion can get some attention, and maybe it could be corrected. I guess a lot of Logic Pro users also has eLicenser Control Center for validation of their products.

Final cut pro 5 with logic pro 7

Does anyone know if running final cut on the same computer as logic messes up logic at all. Since installing final cut i have had unbelievable problems with logic. When i open up a project, almost everything in it has changed, the time signiture seems to be different with every track. The most annoying problem is the audio tracks have actually changed key slightly, how on earth is this possible? I really need help.

A different time signature on each track? Wow. Consider yourself lucky with that. I have been requesting that feature for over a decade.
As far as FCP and LP7 residing on the same machine... I have had FCP and LP on the same machines (G5s) for years and running very smoothly.
The day I can line up 11/8, 23/32, 99/64 and 19/16 without employing over-the-barline phrases will be really, really great.

How do I get LP7 to treat OMFs like PT does?

I've been working with student films recently and they all use Avid for their video editing. They deliver their projects to me for mixing as a Quicktime file and an OMF from Avid. We have tried exporting it from Avid with different options. Protools opens them flawlessly, but I prefer to use Logic and I don't want to have to purchase that overpriced OMF import tool for PTLE. Also, getting VTC sync going in PT is $$$ but all I need to get for logic is a Unitor8 to go with my AMT.
How can I get Logic to open OMF files correctly? When I open one, it doesn't seem to do the timing correctly on it and ignores the "handles" that most of the files have. When I go to play the file it's a real mess and the director is looking at me like "What is wrong with this studio?".
So how to I get the OMF's to work in Logic correctly? I'd like to have the volume/pan automation and the mutes/handles work correctly. I don't see any settings to change this behavior, and there is little in the manual about it.

When I get home i'll post some screenshots of what i'm seeing. I'll make sure they are OMF 2 files also.
It just seems that Logic messes everything up on the import. By "handles" I mean that each audio file generally has up to about 30 seconds of sound muted at the beginning and end of the region, but the area has been pulled in and muted so that only the desired part plays. You keep them around so that you can catch the click cue to the video when they snap the board on set, but of course you don't want to hear them all of the time. In protools you can just grab the Region Size tool and stretch out the beginning or end of the region to hear them. Fairly standard in post work I believe.
When I import the file into Logic, all of the regions are playing, with no mutes, no "handles", nothing. It's really annoying and basically I have to manually go through every single sound and resize it for it to work, which is hours of work for every revision of the film. Sometimes its downright impossible.
Whatever i'm doing, Protools opens it flawlessly when I click "import OMF" but Logic gives me junk.

The Chopping Block (sort of 2 questions)

Logicians,
I regularly import big sample files from digital audio workstations (mostly the korg D1600). The file will be one long waveform with a bunch of small recordings (words, notes, etc) that I want to turn into individual samples. Sometimes I have upwards of 200 samples in a day to cut up.
Let me preface this question with the fact that I very much understand why Logic is treating the waveform cuts the way it is treating them, I just want to figure out how to do this process with that in mind.
What I would like to be able to do is label the first file something unique to it's waveform "A5-SYNTHHIT-1". Then, as I cut, I would like each individual sample to become "A5-SYNTHHIT-1.2" "A5-SYNTHHIT-1.3" etc.
What happens is: Logic, after I make each cut, relabels things just fine. The problem is, the file that it relabels contains EVERYTHING after the cut, and now when I cut again, I am just making progressively shorter and shorter files that contain everything after the cut. So instead of having 1 second samples, I have a 57 second sample, then a 56, then a 55...What I would like to learn how to do, is how to get it to update the sample in front of the cut, so that the sample before the cut only contains UP TO the cut.
This is very difficult for me to explain. Sorry!
Example: Lets say file1 looks like this
ABCDEF
I cut accordingly, hoping to solo out AB, and then CD, and then EF. I want the file to look like:
AB
CD
EF
Instead, sometimes they look like this after those 2 cuts:
AB
CDEF (this middle sample, since it was cut after B but before anything else, contains all of the following data. LOGIC doesn't update the file after I cut the EF off to just contain CD.)
EF
Now...The logic of how this process is working makes a lot of sense. I can totally understand why it would do this. I just want to learn how to do this more efficiently as opposed to having to label every individual sample.
I know this was an amateurish explanation. I hope that someone can help explain a better process.
-mike
P.S. when editing these samples, what does everyone use to efficiently line up the samples on the grid? Anchor points are super helpful, but what tool do you use to cut samples accurately? I am trying to use the marquee or scissor tool in the arrange window zoomed in and it's fairly effective but not accurate. Any ideas?

I'd really like to see an aswer to this one as well...it's terribly annoying that you can't just cut and copy in audio files without logic messing up your project.

Logic 7 Songs all messed up in Logic 8

Hi everyone,
I've just upgraded to logic 8 from 7 and I'm having some problems with songs made in 7. They play back in Logic 8 but they are all over the place. Some Instruments, Loops and Audio files are said to be "not found", yet I can find them my self using spot light. Tempo of some tracks are also all over the place. I thought this transition would have been much easier.
Any help or a point in the right direction would be much appreciated
Thanks
Pauli

I had similar problems with some of my L7 projects. Lots were absolutely fine, even some quite complex ones. But a few just got completely messed up just like you describe: moving regions, lost files, lost tempo/key changes, levels all over the place. Some tracks with Logic plugins even sounded completely different (and I'm not talking about subtle compressor changes, I'm talking drastically changed).
In the end I ended up exporting the midi and bouncing all of the individual audio tracks in Logic 7 for these projects, the putting them back together in a fresh project in L8. Not ideal, but better than wasting time wrestling with it.
If there's a better solution then I would be keen to hear it. Would also be good to know what causes songs to get messed up in this way; like I said, many of mine were absolutely fine, and I couldn't spot anything consistently different about the ones that got corrupted.

!!! Statements of Logic Deleting Files and messing with System are True !!!

This morning I answered some guys post about Logic deleting everything in the same level as the project folder under certain circumstances. I Tried trouble shooting for him but could not recreate it.
Then this happened to me today:
When working in Logic 8 in Leopard all of a sudden it stopped communicating with my Unitor8 via USB. I restarted but the Unitor 8 Which I reset twice would NOT communicate with L8 anymore. It would remain in patch mode (red light lit though CPU is running)
I've had this erratic behavior many times since the past years on many computers so it wasn't really new. All one needs to do is reinstall the Unitor Family driver.
So I decided to do so:
I inserted my Logic Studio DVD and opened the installer and checked ONLY the Unitor family Drivers. After completed install I restarted the Mac. Everything went fine. So I booted L8. While booting I saw my hardrives on the right side of the desktop flash once. I thought that to be strange and took closer look.
Now my boot drive was missing from all the drives on the desktop and in the sidebar window...
I tried to Apple+Click on a Application in the dock. The finder opened the applications folder and showed me the app I had clicked on. But I could not navigate to the root of my System Drive even via the "path" sysmbol in the toolbar. So I hit shiftappleg and entered /Volumes/MySystemVolume - it showed my volume "Grayed Out" in the finder window...
I tried repairing the disk and permissions but nothing was wrong with my boot drive apparently besides the fact that the finder (and all other applications when wanting to open or save) could not "see" my system drive... I could launch all the apps normally that were residing on the SystemDrive in the AppFolder... So this kept getting weirder...
So I opened my favorite application Tinkertool System and went to the Tab Files and chose the underlying tab "Attributes" which shows me Macintosh HFS and Finder Attributes... I pulled my SystemDrive onto the Drop Area and discovered something VERY amazing: The Display in Finder option had mysteriously been altered to "INVISIBLE"
I changed it to Visible and there it was - My System Drive... Showing up in the finder...
I made a restart to make sure everything was OK....
After the restart the following settings had VANISHED:
1) Pixadex = ALL ICONS (I had 230 MB) of sorted icons stored in my Application Support Folder
2) All my Safari Book marks were gone - They were still in ~/Library/Safari - but the Bookmarks.plist was UNREADABLE even with a text editor and XML editor
3) Numerous other applications had LOST their authorization preferences so I had to re-authorize many of my Audio Unit plug-ins...
4) My Dock had been reset
5) My Monitor arrangement had been reset...
6) My date and time had been reset
7) My energy settings had been reset.... (I had NOT zapped the P-RAM)
Since installing Leopard 2 weeks ago - I have CAREFULLY monitored ANY activity after INSTALLING anything in order to be able to troubleshoot - and this problem definitely occurred right after installing the USB Family Drivers and launching L8....
There was really NO HARM done other than the sweating that I did troubleshooting but if L8 is capable of doing what happened to this other guy loosing his whole folder and now doing this to me - where are the limits? When is someone going to get REAL hurt.
Please Apple - I am sending you this post as a BUG report as well - could you PLEASE look into this as there has to be some kind of VERY dangerous MALFUNCTION within Logic or its Installers.

Wow, I was just joking with the medication thing. I didn't actually think it was seriously a mental health issue. Sorry.
In any case, though, if he has full access to the Mac, mental health issues or no, there's not a whole lot to do about it. If it is possible to take away administrative privileges without causing a huge fuss, then you can limit his access to certain things. However, you can't mess with privileges on a Time Machine backup (doing so breaks it), and that means he's going to have access to at least parts of the backup. Which means he can trash at least some of the backup data, and if he deletes files from the TM backup using the Finder, he'll have essentially trashed the whole backup. He might as well have the ability to delete all the files on the machine if he has the power to delete backups.
Honestly, in this situation, he should either only be allowed to use an account with Parental Controls on, which may not be an option (I don't know how offended he would be at such a suggestion), or he should be using a different computer entirely and have no access at all to his wife's computer. Alternately, have his wife keep a backup that is hidden - ie, connect the backup drive periodically and then remove it and hide it so he can't mess with it. That will at least secure the backup.

Messed up tracks in Logic

I spent hours working on a project in Logic. I saved the project and quit Logic. I came back an hour later, and the settings of every one of my instruments were completely messed up. I've tried reverting to other saved versions, but they are all messed up too. I have no idea what happened.

I'm assuming you're recording with some sort of soft synth (if not the drum kits that come with Logic).
If so, the proceedure is very simple. Record the MIDI onto the Audio Instrument track that contains your drum kit instrument. After you've recorded the MIDI, select Region>Demix>Demix by Note Pitch, and the MIDI will be split into separate tracks in the Arrange window. This will isolate the snare, kick, hats, etc). This is documented on page 113 of the Logic Express manual. Keep in mind that you might want to go back and MERGE the hats tracks, since open, closed, and pedal hats will go onto different tracks (despite being from the same physical instrument). Do this using Region > Merge > Regions, also on Page 113.
NOTE: Doing the above does NOT assign each of the tracks to a different instance of the soft drum kit. That is, you will NOT be able to put different effects on the different kit components in this way. To do this, you must make separate instances of your drum kit, and manually drag the split MIDI to the individual track; don't worry though, Logic is smart enough not to load multiple copies of the actual samples. To do this, simply create new instrument tracks for each element of your kit that you'd like to separate out, and manually drag the individual MIDI regions to the correct track.

Did Apple mess up my logic board? (Fan always 4000 rpm!)

So I just had my logic board replaced because I was having sleep/wake problems and I think that problem has resolved, but now I have noticed a new problem. My fan seems to jump directly to 4000 rpm during start up and sits there always despite low activity. I have installed smcFanControl and it is reporting a CPU temp of 39-40 ˚C, so this can't be a normal fan setting at that temperature. I am sure Apple could have messed something up installing my logic board but I was wondering if there was anything else to try to fix this problem before giving them a call. I hate sending this thing in because I really need it for class. Anyway, I have tried an SMC reset and that did not do anything. I will try booting from an external HD to see if that resolves problem (I'm sure it won't). Anyone have advise on what to do? Thanks!

Apparently smcFC was the culprit. I noticed it had a crash log in my console and when I booted from my external my fan was fine. Uninstalled smcFC and the problem has resolved.

ISight/Logic Board Mess

i bought a macbook off of craigslist. i replaced basically everything in the macbook short of the cd drive and ram. i never have been able to get the isight to work, so i bought a new one and installed it today. i still cannot get the computer to recognize the isight camera.
as i was putting the macbook together i noticed that a small gold or copper metal piece that is located above the airport card was broken off. it's a metal piece that bends and curves almost giving it a spring-like function....if that makes any sense.
i ran a hardware test to see if i could find the isight problem and i got the error: 4SNS/1/40000000:TBOT. I have tried resetting everything on the computer, i have followed all the support pages that apple has to offer. does anyone have any ideas? could the gold piece have something to do with the error or would that be what is messing with the isight?
obviously my cpu is not under warranty. i'm not sure where to go from here. any suggestions would be appreciated.

UPDATE:
Apparently the error that I was receiving was fixed when I put the battery back on. Upon retesting, with the battery on, I could not get the error code. However, when I tested without the battery the error came back.
Here is the current situation. The iSight is still not being recognized. I have done everything suggested by apple, this forum and other forums as well. I then reinstalled Leopard...nothing. I also noticed that the battery is not being charged. The weird thing is that when you click the battery, in the top-right-hand-corner of the screen, it states that a battery in not connected...but, when I go to the System Profiler under the Power section it tells me the charge information (in which there is not a charge), cycle count and the condition of the battery. So obviously something is recognizing the battery. The cycle count and condition is good which eliminates that as a problem.
So, here is what I am wondering:
a.) How can the battery be recognized in the System Profiler, but not in the task bar?
b.) If there is a problem in the cables (or whatnot) between the battery and logic board or the iSight camera and logic board, would that show up on a hardware test?
c.) Would starting over by wiping the hard-drive, reinstalling the OS with the original disks I got with the CPU, updating, reinstalling Leopard and updating help? Maybe there is some missing files or drivers?
d.) Could there be a problem with the iSight portion of the display inverter without it interfering with the actual screen portion?
I bought the Macbook used (cheap) and have replaced everything in the computer (logic board, power supply, hard-drive, bluetooth, etc) minus the cd drive and original RAM.

Help with code...Logic is kinda messed up...

Modify the file copy program so that the copy is encrypted (encoded). Each byte of the source file is altered by reversing each bit. For example,
input byte
output byte
00110101
11001010
00000000
11111111
10000000
01111111
This operation is sometimes called a bit-wise complement. "Bit-wise" means that each bit is treated independently of all the others. "Complement" is just another word for reversal.
All the bits in an integer can be reversed as follows:
int value;
value = ~value;
The "~" (tilde) is the bit-wise complement operator. Visually it looks like a reversal of up and down. It reverses all the bits in value, even though you may be interested in only the low-order byte. But since the operation is bit-wise, the result for the low-order byte is the same no matter how many others are affected.
And here is my logic..I kno its a mess...so excuse me.
int tempo;
try
source = new DataInputStream (new BufferedInputStream(new FileInputStream( filename )));
catch ( IOException a )
Errors.setText (String.valueOf("Problem opening " + filename) );
try
dest = new PrintWriter( new BufferedWriter(new FileWriter( filename2 ) ) );
catch ( IOException b )
Errors.setText (String.valueOf("Problem opening " + filename2) );
try
try
while ( true )
tempo += source.readInt();
tempo += ~tempo;
dest.println(tempo);
catch ( EOFException c )
source.close();
catch (IOException d )
System.out.println( "IO Problems with" + filename2 );
I need to modify this logic so that it encrypts the file through the damned bitwise thingy...TIA.

This code:
tempo += source.readInt();
tempo += ~tempo;
dest.println(tempo);Needs to change to this:
tempo = source.readInt();
dest.println(~tempo);Or,
dest.println(~ source.readInt());

Is quicktime 7.5 messing up logic studio??

After upgrading to Quicktime 7.5 logic studio(logic 8) has redefined all rewire setup from aux tracks til midi tracks and my rewire component (reason) won´t play together with logic. Also I can´t make new rewire tracks
anyone?
soebx

If it were me I'd close out every program running on the computer, firewall etc.
Then see if you have any luck running QT. If not. What was the last change to the computer before this problem surfaced?
All problems I've expierenced in the past four and a half years, that I have been using a windows computer have been hardware related. Either not installed correctly or a failure of slots or video cards.
You might want to take a look in Device Manager or go to Start>Run>type in>dxdiag and click OK, to get some info, and also check out the video card driver! That's about all I can offer you.

HT201199 why is logic x messing up my plugins

i tried load a waves plugin but logic x is launching another plugin...........any idae of the issue?

What version and sub version of LPX and OS X are you running?
This sort of issue was resolved in an earlier version of LPX for most people.
However, note.. make sure you have correctly run the Waves AU Reg Utility to ensure OS X's Audio stuff can properly use and see the Waves plugins.. (and don't just manually copy them across to the compenents folder but use the proper installer to install them) and make sure your Waves plugins are fully up to date....

Logical Test (/SAPAPO/OM03) fails with liveCache-test on LCA incorrect mess

Hi All,
On SCM 5.0 instance, when running logical test transaction (/n/SAPAPO/OM03), I get the following message at the end of the test:
liveCache-test on LCA incorrect.
There is no shortdump or any database errors I can see. Please advice.
Many Thanks,
Regards,
Nisch

Hello Nisch,
You are running SCM 5.0 system, therefore you are SAP customer. Please create the SAP ticket concerning this issue => we could logon via OSS and check the status of your system.
-> If you are running the SCM 5.0 installation, you have to follow the liveCache installation guide and finish all post installation steps, run //om13 -> checks , click on the info box of the red semaphores u2026
     Review the system logs in /nsm21.
     Then you could run /SAPAPO/OM03, it is the test Program for liveCache and LCA, in the liveCache relevant client.
     If it's failed & you don't know the reason of the failure => create the SAP ticket to the component 'BC-DB-LCA'.
Thank you & best regards, Natalia Khlopina

Logic 9 messing up 8?

Similar Messages

Maybe you are looking for