Cut Section Bug in Logic 9.0.x

Just wondering if anyone can confirm this?
If you have a region that is, say bars 1-5, and then create a cycle region that is within the borders of that locked region (say bar 2-3, and attempt to Cut Section, then subsequent regions in the song become locked, and sometimes some data can be lost in the locked region. There is something weird happening here.
This is with Logic 9.0.x on an intel machine on both 10.5.8 and 10.6.1...:(
Thanks for any advice.
Regards,
Ken

See this -> Don’t Panic
"Yesterday (09/09/09, by the way) Apple released iTunes 9. Unfortunately it has a nasty bug that prevents iVolume from analyzing songs that have been imported from a file. All other songs – that is purchased, ripped or converted songs – will still be processed fine by iVolume.
We put highest priority on this issue. All other projects have been interrupted in order to restore full compatibility with iTunes 9 as soon as possible. We already found a solution and are currently busy implementing it. Things look good so far.
So please be patient, a new version of iVolume will be released very soon"

Similar Messages

An Open Letter to Apple About Bug-Ridden Logic Pro 7.1.1

The bile rises in my throat as I write this, as it has all day struggling with the innumerable bugs in Logic. That's right, not pilot error, but de facto B U G S. Dangerous bugs.
Today's tale is about 2/4 measures. In the score I'm writing I have a 2/4 measure. Big deal, right? Problem is, I've had to re-insert this ******* 2/4 measure about 4 dozen times today, because every time I undo an edit -- one that occurs many editing-steps after I inserted the 2/4 time signature -- the time signature disappears. Oh yes, and this signature can't be retrieved with undo/redo.
This bug is akin to the one I reported previously where, after inserting numerous markers one after the other, and then undoing the next edit, all of the markers disappear (and can't be retrieved with undo/redo).
Sound familiar? See a pattern forming?
Two days ago I was working on a record for a high-profile artist. The question arose as to why, at one point in the track, the click's loud downbeat click was playing on the 3 and the soft clicks on 1, 2, and 4. The answer? Same bug! There was a 2/4 measure in that piece too, and when I undid an edit, the 2/4 measure disappeared. You want to talk about embarrassing? Want to talk about time-wasting effort?
How wonderful for us professional Logic users that my "For Apple Employees Only" thread -- which asked that someone from Apple/Logic respond to the various problems that people were posting here -- was locked. Talk about the exactly wrong response from Apple/Logic. Couldn't be more wrong in your approach if you tried harder.
So, Apple/Logic. What are you going to do about the plethora of other bugs that riddle this otherwise grand program? What are you going to do about your severe lack-of-communication problem? After spending $1K on your software, we deserve to know.

William. Sorry to hear about your troubles. At times I've been tempted at times to go back to 4.8.1! In fact I'm going to be doing just that when I do a live TV performance next week where the artist I'm working with is performing live to a few sequenced tracks.
I can imagine the difficulties that programmers may have to face in fixing bugs in a complex program such as Logic, but it's a situation that doesn't elicit my empathy for them. That's their job.
I guess I could sum it up in the form of a quasi-parable: a composer gets a gig to write a score in the style of Bach, but he's much more well-versed with Schoenberg. Despite the composer's assurances that he can do the job, the music ends up sounding like some strange hybrid of the two. It would be quite understandable if the client were upset because he was promised an authentic-sounding, baroque score. No one feels bad for the composer, because he took a job that he wasn't qualified to do, and ultimately didn't deliver what he promised.
Similarly, I feel hoodwinked by the promise of satisfaction implicit in the notion of purchasing the best that Apple has to offer, i.e., the most powerful computer (which my dp G5 was at the time), lastet OS, and expensive software published under Apple's aegis.
I agree with you that there's incompetence and irresponsibility at play here. To the latter point, any decent beta tester would have discovered some of the more basic bugs in Logic 7.1.1. And here we are, vis a vis this forum, essentially publically beta-testing Logic's latest offering with zero feedback from the company, despite the fact that our respective problems are absolutely tangible.
To the former point, I'm wondering if it's the programmers themselves who are not up to the task here, if it's management that have fallen asleep at the wheel, or some combination of the two.
I've learned that as of last year a fellow named Bob Hunt was the product manager for Logic. If he's still currently the PM, and the feedback and problem-related posts here haven't been enough to prompt him (or someone in an official capacity) to publically address our respective issues, then I'd venture to guess that there's a problem somewhere at the top.

Bug in Logic Pro?

Hello, I have experienced a strange behaviour. Please try the following things:
1. Create a project which uses Space-Designer Plugin for a Audio Track
2. Save Project and Close Logic
3. Start Logic again and open the project
4. Bounce the project BEFORE doing anything else, espacially don't start playback (PCM, Offline, whole project)
If I do that, the bounced file is rendered without the Space-Designer effect. It seems, that the Space-Designer is only rendered, if playback has been started once.
Do you have the same problem?
Thank you very much,
Tobias

Tobias wrote:
these things you describe I have not experienced till
now - but it doesn't make things better. To we have
to accept these bugs? I have paid a lot of money for
the software... the least thing is to try to "report"
the bug.
True, acknowledging the bugs doesn't make the situation any better in the immediate. But there are many benefits to posts such as yours in bringing the buggy/errant behaviors to light; I strongly believe that as important as it is for people to know how the program works, it's equally important for them to be made aware of the ways in which it is broken, unpredictable, or otherwise buggy. In this way, people can avoid invoking features or otherwise using the program in ways that are known to cause problems.
I would like to suggest that you not only file a bug report at the Logic Feedback webpage, but also post your bug on the bug report/workaround section of www.logicprohelp.com
You wrote, "we have to accept these bugs?" In a sense, yes, because Apple/Logic does not often release patches or bug-fixes, even for long-standing yet minor bugs. Assuming that your problem is indeed a problem and not pilot error, about the only thing you can do is make both users and the company aware of the problem and wait/hope for a fix.

Persistent Aggregates bug with logic - anyone else see this ?

A long while ago I posted a bug report regarding the use of aggregates with the Stealthplug guitar audio interface. I also reported this on the apple bug report system.
Basically, when using Logic8 with stealthplug and OSX Tiger ( latest 10.4 ) I configured an aggregate using AudioMIDI setup program, configuring Stealthplug as the input and the built in audio as the output.
When one creates an audio track with the aggregate name selected I Logic8
preferences INITIALLY one can get audio input to show up, the "record" button appears and one can hear audio output to the main macbook audio outputs. However on repeated use and selection/deseletion of the particular named aggregate one finds that the stealthplug input is no longer enabled ( the record button disappears).
I found out recently that if I delete the aggregate ( I only had one aggregate st up ) and create a NEW aggregate, this time with a different name, but with the same settings ( stealthplug as input, built in outputs as output ) then one can get the aggregate to work initially in logic8. However after a few sessions, or switching between audo devices in preferences, the aggregate again fails to work, by this i mean I no longer get the "R" button appearing in the channel strip for the input.
Stealthplug works fine when selected itself if one selects this as the device, but NOT when used through an aggregate. I suspect this is something to to do with aggregates and not stealthplug.
My suspicions is that it has something to do with the way logic8 or the CoreAudio system stores its aggregate preference information since I find that if I delete the original aggregate but recreate the same aggregate settings using a different name then the aggregate will work for a short time.
This really needs fixing since aggregates are potentially so useful.
Anyone else seen this with stealthplug or another audi interface ? is the Aggregates system just plain buggy? dos this problem go away in Leopard ?

Well I can say that after installing updates to QuickTime is appears I have been having a lot of trouble with Aggregate Devices as well. I use 2 896HD MOTU interfaces and after a few sessions of Logic, the Aggregate device stops working. I can either (a) reset the computer, (b) sometimes reset the coreAudio driver (works rarely) or (c) create a new Aggregate device like you have and it all starts working again.
Even worse, some of my USB MIDI interfaces like the Fantom X7 just loose connection as well. If I remove the USB and then plug back in, it's recognized again immediately.
Something is seriously broken and I have NO clue where to begin to help fix it. The only thing I could do is re-install OSX 10.5 and not do the quicktime updates and see if that helps. Unfortunately, that is a LOT of work! (I use like 146 AU plugins total).

Final Cut Studio 2 and Logic Studio on MacBook

I have a white MacBook bought in late 2008. It has a 2.1 GHz Intel Core 2 Duo processor w/ 1 GB 667 MHz DDR2 SDRAM.
My question is: has anyone run Final Cut Studio 2 and/or Logic Pro with these specs? And how was it?
I was told performance would be weak. I was also told nothing could be done to improve the performance other than buy a MacPro or at the very least get a MacBookPro. I have no reason NOT to believe this but I am interested in a second opinion.

Hi there,
Ignore the other posts, both run absolutely fine on a macbook! I use final cut studio 2 on a white macbook and so do about 10 of my friends almost without problem. Final cut works perfectly, dvd sp works perfectly, motion works perfectly, soundtrackpro works perfectly! the only problem i ever had was rendering with 'color', none of my other friends grade their videos so they have no problems at all. Are you going to do any grading?
I believe the macbook is not officially supported though, so I don't think you'll be able to get help from apple if there's any problem solving to be done. I've been using FCP and FCS for years now though and have honestly never had a problem I couldn't solve myself
Logic also runs amazingly well too.
hope that helps

"Warning! Not Enough Memory!" A bug in Logic 7.1?

Hello,
I seem to have discovered a bug in my Logic 7.1, and would like to see if this is a system specific bug, or a bug in everyones Logic. It seems to occur in the Matrix editor which results in the error ""Warning! Not enough memory! This operation cannot be undone" and follows with the mysterious deletion of random parts, and totally corrupts the file, preventing me from doing any further MIDI edits or even undo the mysterious deleated parts!
Here is how I discovered it. I selected two separate audio instrument tracks (violin and viola) and opened them in the matrix editor. To see both parts at once, I double clicked on the background, resulting in viewing all possible MIDI parts. I then selected from the "show selected regions only" from the view menu to isolate the violin and viola parts. I then copied some notes from the violin part and then double clicked on the viola part and attempted to paste the violin information I copied to the viola part. However, the information would not paste for some reason, so I decided to simply draw in the new notes, and BAM, the error message "Warning! Not enough memory" occurs.
I have been able to replicate this error on my own system on a few occasions, but it doesn't always seem to happen which is strange. I may be able to get around it by making sure I double click and isolate the part I want to copy first, before isolating where I want to copy it to, however I need to test this idea out more often to make sure. In the mean time I have tried "reorganizing memory" in logic, repairing permissions and running all maintenance scripts, Re-installed the OS 10.3.9 update (just incase something didn't install correctly), ran apple "hardware test" in which everything passed, and trashed and rebuild my preferences, and I'm still able to create this error.
I do feel something is wrong here, I was wondering if anyone may be willing to try to duplicate this on their system, just so I can be sure there is a Logic bug, or maybe there is something wrong with my personal setup. (MANY weird things have been happening lately, such as corrupted key commands in my preference files).
Thanks in advance for your help!
-Jon

Thanks for your comments Rohan. The reason this post was relatively clear headed is because I already went through my "freak out" process earlier that week! But thanks for your comments. I did try to make this post as clear as possible, in the hopes that others could potentially get the same "buggy" results. I guess the problem seems to stem from something bigger then how I arrived at it, but from what I've found researching it, the matrix editor does seem to play a consistent part.
Maybe we should send a quick note to apple, asking them to keep an eye out for this bug?
In answer to your specific questions, the size of my file before the error was 468KB, and the file after I saved the error is 544KB. Not a big enough difference to raise flags, as the error file does contain a few more seconds of music, some different parts, etc. The song itself is only 32 bars long @ 103bpm, and the total bars is set to 266. At the current tempo, the song would end at around 7min, much shorter then an hour. For the record, I have done many longer, more memory and CPU intensive pieces and experienced no such problems (except for the need to freeze a few tracks). For example, I recently scored a film that was heavy in Atmosphere, VSL, and Stormdrum, and ran an uncompressed film file and no problem. Now that I think of it, perhaps it could be an EXS problem even? For those who have experienced this error, were you editing a EXS part?
As for the Key commands problem, I will have to do more research and testing once I upgrade my system. I dont mind loosing my current key commands and preferences and starting again. In fact, I think I can do a better job customizing Logic now that I have a better idea of what it can do. However, if this seems to be a consistent problem, then I may not do too much customizing yet
Thanks again for the post Rohan. I hope everything runs soother in Tiger after a clean install. Any quick tips for optimal Tiger setups?
-Jon

How to cut a movie in Logic 9?

Hi,
I'm using Logic 9 to compose a score for a short film. I would like to cut the first few minutes of the movie, how do I do that? And secondly, I want to bounce the audio along with the video. I have read in other discussions that I should go to Options>Movie>Bounce Movie and Audio but Movie doesn't appear in my Options.
Cheers

The Movie functions are under the File menu, not the Options menu. The Export Audio to Movie function is only available in 32-bit mode, so if you want to do that, you'll have to:
Quit Logic.
Find the Logic application in /Applications.
Get info on it and check the Open in 32-bit mode box.
Launch Logic again.
When you've exported the audio to the movie, you can reset Logic to 64-bit by unchecking the box.
Logic does not edit video - you'll have to do that in other software.

Send Program Change bug in Logic 7.2.2

I recently got a Mac Pro 3.0, and installed Logic 7.2.2. In general things are
going okay, but I recently found a bug and I wonder if anyone else has run
into it. I have a fairly extensive studio setup (6 Gigasamplers, some hardware
samplers, quite a few synths, etc.) and have been working on an older G5
with few problems, still running 7.2.1. When I open up a sequence on the Mac Pro with Logic
7.2.2, it checks all the Send Program Change boxes on every midi channel of
every instrument in the environment. This plays havoc with my studio setup,
since I don't often use Logic to send program changes. I have since built a
new environment in Logic 7.2.2 with all the boxes unchecked, and I import
that to fix the problem, but I have many sequences on the old G5 I will need
to open on the new machine. Anyone else run into this? Any global fixes?
Thanks...
Mac Pro 3.0, G5 2.5 Mac OS X (10.4.7) Logic 7.2.2, 7.2.1

I've had strangeness with the global tracks during a mix. I had the "tempo" track causing notes to change pitch and cause midibog. Time signature works ok.

Anyone know how to LOAD DEFAULT sound in SCULPTURE? Bug in LOGIC?

Mine does not when I load a new instance. The reason I ask is I bought a training video from N.E.D. and he starts on all DEFAULT settings which has an instrument sound like a weird guitar.
The second question, I noticed when I booted to 10.5.2 vs 10.5.5, I think Logic on the 10.5.2 is an older version 8 (not updated) and what I noticed is, when I double click the track in the arrange window, it opens the mixer, when I do the same in 10.5.5 and double click, it thinks I want to change the track name. Is this a bug or a fix? How do I get it to act like it did in the older non updated version?
Thanks

...and the answer is indeed simpler than I thought:
As for your second question, I think you should look here:
regards, Erik.

Cut section of footage with audio out of timeline - HOW??

Hi I've tried to select a middle section of my timeline and cut it out and have the two sections join - how do I do this? I've tried cutting the back end and pasting over the middle section, but it will NOT overwrite the audio. Video will overwrite but it does not lay audio over with it.
I've Tried using Extract audio when using "Paste over at Playhead" checked and not checked. It doesn't work either way. any help please?

Hi dsafian - if I understand you correctly, removing a section is simple, but there are two scenarios and you do not give enough detail for us to know which one to describe, so here's both:
1. Cutting a section out of a single clip: there is more than one way, but here's one. Place the playhead at the start of the part you want to remove and hit Command-T. That will split the clip at that point. Now go to the end of the unwanted part, and do the same. Then select the middle part and hit 'Delete'.
2. Removing several clips: Select the first clip you want to remove, and then Shift-Click on the last clip to be removed. this will select all of the clips that you want removed. Now hit 'Delete'.
Does that help? Tell us if we have misunderstood your problem.

Shift + Enter (Play from Selection) Bug? Logic 9.1.6

Hi. Im currently using Logic Pro 9.1.6 on USA macbookpro with OSX 10.7.2 installed. Is there a known bug when selecting a region then Shift and Enter (play from selection)? Can't get mine to work.... anyone else having this issue? Ta. Ju

Hi
Function Shift Return???
CCT

Pda reproducible bug with logical shift operation when y 3 for arrays

Folks,
I have discovered a problem and wonder if this is a wider bug or if I am doing something wrong:
Labview PDA 8.0.1 - running on a Dell Axim:
I create a 2x1000 array of U32 and feed it as x into the logical shift operator. If y is between -3 and 3, the logical shift works properly. If y >= 4 or <= -4, then the array is returned with all zeros.
I have reproduced this for I32 data and smaller arrays. Logical shift works properly for scalars.
Has anyone else seen this? Is this a bug?
Thanks for any help.

It might very well be a bug. If it works differently on the PC and on the PDA then it is almost certainly one.
I suggest you post a simple example showing this so that people with current versions of the PDA module (i.e. not me) can test this. Maybe it was even fixed for 8.2?
Try to take over the world!

Have Melodyne/Rewire file bugs per Logic 8 been fixed?

I'm about to do a clean install of Leopard on my system drive (and the online upgrade to 10.5.3), followed by installation of Logic Pro 8.0.2 and Melodyne Studio 3.2.2.2. Trusted users on this forum have reported problems with Logic following installation of the Melodyne Bridge and/or Rewire files.
I'm wondering whether these bugs have been fixed and whether the Melodyne Bridge is now working and crash-free in Logic 8 -- assuming one is running Melodyne 3.2.2.2 or, according to the tech at Celemony/Melodyne, any version of Studio 3.2.2.0 or later.

The problem is nothing to do with Logic as such. The problem is with the Melodyne Rewire stuff on Leopard.
I think Celemony have a forum - might also be worth asking over there. I know they have issued an update recently, so they might have fixed it...

Final Cut Pro X to Logic Pro X....on another computer

Maybe someone here can help me. I have found many pieces of what I need to export an XML from Final Cut X & import it to Logic Pro X.....except....how in the world do I do this process if I need to get the XML AND associated files to my audio editor ******on another computer.
Your assistance is truly appreciated!

You'd need to send the other editor a copy of the original Library, so he has the media, projects, events etc.

11.5 Select Area for Section Bug

I have found what I think is a bug in 11.5 P03. I have tried this same process under 11.3 and do not experience the problem. When using the "Area Tool" or "Section Area for Section" to select a portion of a Section, the size that is selected is not the size of the newly created Section.
Here are the steps I followed with the results:
1. Start with an 8.5" x 11" Section that has margins of .250" on all sides
2. Use the Area Tool to choose an area and set the following property values:
Action = Create Section
Name = example
Check In = unchecked
Keep Objects = checked
Horizontal = 0.000 Inches
Vertical = 0.000 Inches
Width = 8.500 Inches
Height = 1.200 Inches
3. Press OK and open the new EXAMPLE FAP
4. The size SHOULD be Width = 8.5" and Height = 1.2"
However, the new Section size is the dimensions PLUS the margins. Width = 9.100" and Height = 1.7"
5. The objects are aligned according to the new Section size and cannot be easily realigned when the section is resized because 11.5 no longer offers a Align By Page that leaves objects relative to each other. (Possibly another bug.)
Any suggestions on a way to make the above steps work as expected or is this is a bug?

Hi,
It appears that both issues you raise are product issues. Please enter an SR and post the SR number here so that I can link it to some internal discovery already completed.
Thanks,
-DA

Cut Section Bug in Logic 9.0.x

Similar Messages

Maybe you are looking for