Logic 7.2.x Bugs

Hi. I've decided to put up a topic where I post any bugs I encounter when using Logic 7.2.x on our brand new iMac 2 ghz. Anyone is welcome to contribute.
I'll try to remove listed bugs that get fixed.
These bugs where encountered on Intel macs.
• Guitar Amp Pro
The Tremolo effect doesn't work as it should.
When turning on Tremolo it sounds more like a "Bit Crusher" and seem to even cause kernal panics. This doesn't happen when using the plug-in in stereo. It seems to be a bug only in Mono mode.
iMac Intel 2 ghz   Mac OS X (10.4.6)   1.5 gb ram

You should be able to use the Guitar Amp Pro at low bufferrates. I've tried it on 256 as well and it still is there. I definetely shouldn't need to go higher in buffer size when I got a brand new intel 2 ghz dual core, 1.5 gb ram and a professional sound interface (Motu Traveller). It's a bug and it's bad of Apple not noticing it before shipping 7.2.1.
The bug is there only when you use it in Mono mode (not mono->stereo).
This is still a bug since you should be able to use Guitar Amp Pro in mono with out flaws. This seem to only occur on intel macs.

Similar Messages

  • Binary Data type in Logical - Is it a bug?

    Binary Data type in Logical - Is it a bug?
    Hi ,
    I am using SQL DM 3.0.0.665. I need your thoughs on following.
    I have an attribute in logical model with binary datatype. As I generate physical, SQL DM putting the column in BLOB data type. I thought binary means 1 bit ON/OFF type.
    What is the interpretation?
    Thanks in helping us out.

    I thought binary means 1 bit ON/OFF typeYou can check mapping of logical type to native database types in "Tools>Types administration". Data Modeler comes with set of predefined logical type and their purpose is to cover all native types in supported databases.
    Nothing can stop you to change predefined types if you don't like them or/and to create your own types.
    In the case of "Binary" - it's introduced to cover "binary" type in MS SQL Server - it's sequence of bytes not bits or bit.
    Philip

  • Data Guard Logical Standby Skip Handler bug

    Does anyone know of a documented bug concerning the skip handler not skipping a grant on a view in a schema with a SCHEMA_DDL skip handler defined?
    Here is my test case.
    On Primary:
    Create table scott.junk (x number) tablespace users; (created successfully on logical standby)
    On logical standby:
    exec dbms_logstdby.skip('SCHEMA_DDL','SCOTT','%'null,true,'\'); (created skip handler on all SCOTT objects)
    On Primary:
    grant select on scott.junk to public; (successfully skipped due to missing object)
    On Primary:
    create view scott.v_junk as select * from scott.junk; (successfully skipped on logical standby)
    On Primary:
    grant select on scott.v_junk to public; (received 'ora-00942 table or view does not exist' on logical standby and SQL Apply stopped).
    I'm running version 10.2.0.4 but have not applied the recommended patch bundle for logcal standby #7937113.8.
    If anyone knows whether this has been documented or not, please let me know. If not, I will submit an SR to get this documented.
    Thanks,
    Michael Anderson
    OCP - Bank of the West

    When I look at the syntax for the package
    http://www.morganslibrary.org/reference/dbms_logstdby.html
    what I see is:
    dbms_logstdby.skip(
    stmt        IN VARCHAR2,
    schema_name IN VARCHAR2 DEFAULT NULL,
    object_name IN VARCHAR2 DEFAULT NULL,
    proc_name   IN VARCHAR2 DEFAULT NULL,
    use_like    IN BOOLEAN  DEFAULT TRUE,
    esc         IN CHAR1    DEFAULT NULL);So looking at your code:
    exec dbms_logstdby.skip('SCHEMA_DDL','SCOTT','%'null,true,'\'); (created skip handler on all SCOTT objects)
    'SCHEMA_DDL' is your statement.
    'SCOTT' is your schema name.
    '%' indicates all objects
    and ... shouldn't there be a comma before the NULL?
    In the future don't provide values where the default's will suffice. It makes thing's far simpler.

  • Logic Pro X - workaround bugs

    Hi!
    Logic Pro X is still a new release (10.0.3 when writing this) and there will of cource be updates to fix bugs. But meanwhile, why don´t share some workarounds for bugs that occur?
    My first tip which for problems with recording audio is to bounce what you have and go back into Logic Pro 9 and do the recording and then cut/edit all the takes before taking it back to Logic Pro X and continue to work.
    Does anyone else having problems with recording? My LPX just quits after some time of recording when I hit the rec-button.
    My first workaround for this was to use the command "Save a copy as..." since it seems to work some more minutes before crashing.
    It clears unused memory in the file in some way I think.
    Before saving as a copy the file is always about 100Mb bigger.
    Any more workarounds?

    Does anyone else having problems with recording? My LPX just quits after some time of recording when I hit the rec-button.
    No, not here.. I finished a 10 track  1 hour live recording this weekend without issue..
    If Logic just quits, do you get an error msg, a crash log or failing that look in your console logs to see what is causing the problem.. and post up what you find/see

  • Logic windows loosing "link" bug?

    Hello everyone,
    My Logic windows are loosing their "link" ability, and I'm wondering if its a bug. In my main screenset I have 5 windows that are used: Arrange, movie as float, global mixer, event editor, and an environment window on a 2nd monitor used for selecting instruments. In my setup, I use midi instrument tracks to trigger exs instruments, and use channel splitters to select different articulations per instrument, allowing for my instrument parts to play multiple articulations on a single track.
    Now, in the course of my work I consistently switch between the event editor, global mixer, environment, and arrange page, and sometimes my "link" between the environment page and my arrange page becomes dead. i.e. I can switch between tracks in my arrange page, but it no longer switches instruments in my environment page. The only solution I've found is to click on the environment to "refresh it" and then click on my arrange page, and they are now back in sync. However, it seems that once I click on the global mixer, the environment is once again out of sync with the arrange page.
    Is there anyway to fix this behavior and have the environment always be in sync with the arrange page? Is this a flaw in dual monitor operation or a bug in Logic? Note: my environment uses the "pink/purple" link where my event editor uses "golden link." All windows, except my movie and transport, are non-float.
    I'm guessing this is a bug, but would like to make sure. Thanks again for your help!

    I figured out what I do sometimes that causes that (maybe this is what's happening to you guys - at least some of the time?). Try this:
    While the song is playing, use the scrollbar to scroll ahead to a part of the song that isn't on the screen. As soon as you scroll off-screen, the Link button goes out. The song stays where you put it, but you lose the Link.
    A better behavior would be that when you release the mouse, the song snaps back to where the SPL is and keeps the Link button enabled. Alternatively, the song position could stay where you left it (with the SPL finally catching up), but keep the Link button enabled. The next time you start the song, it would snap to the SPL. The way it is just doesn't work well - at least for me.
    Dual 2.5Ghz 2004; 2.5GB RAM   Mac OS X (10.4.8)  

  • Logic Pro 8 graphic bug inOS X 10.9

    Logic Pro 8 has a graphic bug since update to OS X 10.9. The the position tracker turns everything behind it into black in the the arrangement window while playing or recording - Is there a possibility to fix this bug?

    Blueberry wrote:
    Well, Logic Pro 8 was shipped 2 OS versions before Mavericks and is many years old. I don't think this is a push to force you to spend money, otherwise they would have done the same for Logic Pro 9 (which does work on Mavericks just fine)
    That is, the very last update of Logic Pro-9,  9.1.8.

  • Logic 8 Content Link Bug?

    I have found a bug, I think, in Logic 8, as far as Content Link is concerned.
    A screenset with only a Piano Roll
    window in it, and with the link checked yellow, does not update
    when you select a different region in the Arrange page in another
    screenset.
    For instance, I have screenset #1 as an Arrange page,
    and screenset #6 as a Piano Roll only page. Selecting a midi
    region on page #1, and switching to page #6 should show the
    midi region that is selected. That is how it works in Logic 7.
    It does not work in Logic 8, however. But, if I uncheck
    the yellow link and recheck it, it updates. Also, a Piano Roll
    window follows the region selection fine if both the Arrange and Piano
    Roll window are on the same page. Can another Logic 8 user on
    a mac intel machine verify this? I've got verification on non-intel
    macs that the problem exists there too. I've tried all kinds of settings
    on the Arrange page and nothing seems to matter. Yes the Piano Roll
    at the bottom of the Arrange page will update, but I like working
    on a full screen Piano Roll, and it works fine in 7.

    Apple are aware of the issue. Hopefully it should be fixed in the next release (I'm pretty confident it will be).
    And yes, it's an annoying one...

  • Is Logic 9 full of bugs?

    I started with logic express 7 years ago, upgraded to 8 when it came out, just upgraded to 9. Using it on a new MacBook Pro. Getting ready to dump it and reinstall 8. Anyone else having trouble with merging tracks? Sometimes it works, sometimes I get a message that says "can't delete ... is being used by an open project" It also re-names my tracks at random, real cute, just a minute ago the miserable thing renamed 25 tracks. When I try to add a marker it it adds at least two, the second one being about 100 measures ahead. One time I added a marker it scattered about ten around the project. This is only the second day of use and I'm about ready to flush it.

    I hadn't installed the updates when I posted, but when I looked at some of the issues that had been addressed I did it.
    After installing the updates, I renamed the tracks that Logic had screwed up, then I made an edit to a track, and it promptly renamed every track in that project to the name of the one I had edited, somewhere in the range of 75 tracks.
    So I rebooted, reopened the project, and the tracks all had their incorrect names, but at least the record enable button on the individual track had disappeared!
    Tried reconfiguring the track header, but record enable was selected, just was not appearing.
    At that point I called support, and he had me empty the trash folder and then go to library>I don't remember>com.logic.plist (or something similar) and delete the .plist
    The record enable button is back. Don't have any idea about anything else. Almost afraid to open it.

  • Logic 9.1.5 bug?

    ok.
    today, i'm work on logic 9.1.5, using a lion.
    recording the guitar and checking the sound.
    but, it's terrible.
    and i cheking original recording file.-aif- it's fine.
    I am not sure why it’s so.
    however. new recording section -rec on logic 9.1.5- sound very bad. only play on the logic.
    what's happen?

    BUMP

  • How well does Rewire work in Logic Pro 7.2?

    Has anybody who got 7.2 tried Rewire? What do you think of it? Any visible improvement?

    probably thats gonna be a no no as well
    this was not a bug fix
    it was more loops for the GARAGEBAND users, and an intel base LOGIC
    not necessary a bug fix
    i swore to god, i have a feeling after this update (7.2) apple is gonna make another update saying they have fix the real problems and we have to pay for it again
    then you'll get some idiots from this forum who tell us not to blame apple but to wait and buy and try to see if the problem is still there
    get a hint "LOGIC 7" was cool but useless, also 7.0.1 which was useless because it was for free and didn't really fix much bugs
    then 7.1 which fix a few bugs but not the most important ones and it also introduced more bugs and they added more loops just to make us happy
    now there is 7.2 .GOD!!
    again the most important problems haven't been fix
    I bet you, you'll get some appleASS licking user who is gonna tell us not to worry and wait for the next update and hope they fix it
    why won't they just listen to our problem so they know how it is in the real world
    you testing logic on a clean INTEL mac doesn't mean thats how it is all around
    hopeless!!!!

  • Logic Pro - Massive response delay / freeze in mountain lion

    hi there, ive read quite a lot of people are having problems with Logic in ML on other forums and wondered if anyone knows if theres an accepted problem with Logic 9.1.7 in ML?
    My problem seems to relate to the graphical interfaces of logics naitive plugins (mostle chain eq) but isnt alway restricted to these. This problem is not 100% repetitive but often enough that i now dont trust Logic in ML.
    Typically what i experiemnce is that when im in Chain EQ with analyse switched on, the track continies to play but the functions within eq and any other command within logic dont respond. I continiue to see the analyser moving with the music, the transport window moves with the track, just wont stop the track etc.
    After between 30 - 90 second is usually catches up, and the track stops. But today in space designer, it did it to the point where i had to force close the program losing a ton of progress on a track.
    Reading oter peoples post, this isnt a hardware issue, theres a myriad of users with 20+gb ram on massive systems which have this problem. Im on a 17inch 2010 mbp i7 w/8gb ram.
    This didnt happen in Lion, and nothing in my setup has changed. Ive done a full reinstall and that doesnt make a sidderence.
    This needs addressing. ML is great but its now interfering with what i need to do.
    And no, Logic X isnt the answer, Logic 9 needs this bug fixing properly.

    kcstudio
    Must be my chipset then, although another Mainstage board told me otherwise. (that it was the OS)
    When I upgraded my Duo2Core MBPro to Mavericks, I too lost Logic 9.
    I'm pretty much done with Logic 9, and pretty happy about the new Logic X, and happy that it works on ALL of my machines.

  • LR3 Smart Collection Bug

    Hey everyone,
    I'm having issues with my smart collections in LR3.
    When I set a rating to "is not" it only includes ratings higher than that. It doesn't include photos, not rated or rated lower.
    Anyone else with this issue?
    Cheers

    Change the logic:
    And report the bug.

  • HT1338 just bought a 27" iMac quad core i5 and when I try to install Logic 8 it tells me that its not supported by power mac

    Just bought a 2011 imac 27" to upgrade from my MacBookPro 17" to run Logic 8, but when I try to install Logic 8 on the new Mac I disappointingly get a message to say that the application is not supported on power mac, that cannot be right, or can it. If so what do I need to do to get it to install?

    Logic 8 has a "bug" in its installer program that makes a newer Mac (Lion, and thereafter) think that it is PowerPC, but it is not PowerPC.
    Try using Pacifist to install Logic 8 in Mavericks:
    http://www.charlessoft.com/
    If you cannot get Pacifist to work, you can partition your hard drive and install Snow Leopard into that new partition, install Logic 8 and then upgrade to Mavericks.
    As Barney correctly points out, the 2011 iMacs require a minimum of 10.6.6 to boot, so that you need to install Snow Leopard with one of these three options:
    1)  As Barney points out, the original grey Restore DVD that came with that iMac (or a replacement provided by Apple if you call with your model and serial number);
    2)  The slipstreamed version of the Mac OS X Snow Leopard Install DVD at 10.6.7; or
    3)  Install Snow Leopard on a new partition on another older Mac, update it to 10.6.8 and then clone the partition and move the cloned partition over to your 2011 iMac.

  • Logic freezes when attempting to bounce.

    Logic is freezing when I attempt to bounce one of my projects, a music sequence using VSL sampled instruments. It doesn't even give me the bounce options window, but starts "thinking" (pinwheel, big CPU spike) as soon as I select "Bounce" from the menu, and remains unresponsive until I force quit.
    It seems possible that this one project was somehow corrupted, but everything except the "Bounce" feature still works fine, which is rather bizarre.
    It also seems possible that this is a result of the 8.0.2 update (since I had bounced this project with no trouble before the update), but of course all my other projects are fine as far as I know...
    Ideas?
    --Conor

    I'm having that same issue today in a large piece (first half of an opera) using vienna ensemble.
    I've already rebuilt the entire piece once, due to problems transferring the piece from logic 7 to logic 8. The thought of another rebuild.....
    Bought a new 8 core machine to do this piece, now using logic 8.0.2 with os 10.5.2.
    I've been a logic / notator user for the past 20 years. I used to love using logic-- great program -relatively bug free. But logic 8 is so full of problems it makes you crazy. If there was a serious altenative I'd be looking at it....

  • Getting Leopard and Logic running

    Hey folks I thought some of this might help, so I'll post it here so others can benefit.
    I got Logic 8 and Leopard rockin' in fact better than on tiger.
    Things to watch out for...
    PACE installer for iLok. Go to the pace site and get the latest installer. DON'T install the one what comes with the Waves plugins. I use the Waves SSL 4000 plugin and it works great, just install the PACE software FIRST and when the Waves plugin says it wants to install its own just quit.
    MELODYNE - DO NOT INSTALL THE REWIRE CRAP. Do a custom install. If you didn't do a custom install, go into /Library/Audio/Plug-Ins/Components and remove the Melodyne Bridge plug. Also go into /Library/Application Support/PropellerHead Software and remove the ReWire stuff that's in there. (This will prevent logic from crashing.
    SYMPHONY ENSEMBLE - Get the latest drivers from Apogee. As posted in another thread, if you install that and have a MACKIE MCU IT WILL WORK AGAIN! Wohoo!
    So right now I have all my plugins working, everything authenticated and is running like a champ in Leo. I was thinking I might have to keep Tiger, but nope, everything is running for me... BUH BYE TIGER!
    Plugs that I have which work and tested:
    LiquidMix (using latest beta)
    Waves SSL 4000
    Symphony
    DUY (all of them)
    URS S Series
    UAD-1 v4.8
    GuitarRig 2
    Melodyne Studio and Plugin (3.2)
    (Did not install BFD it has issues with Logic 8 nothing to do with Leopard)
    R

    Yeah get Logic 8. I would be very surprised if 7.x worked on Leopard, but maybe it will, however just like any company if there is a new version of software chances are that the previous version will no longer get updates, and if it's not working now, they're not gonna fix it.
    Since you're on Leopard, you can't use the 'but I have a session that is important' argument, or I don't want to go to Logic 8 because of bugs You crossed the bleeding edge line
    R

Maybe you are looking for