Logic 7.1.1 & error -39

I am still getting end of file error -39 with the 7.1.1 update. i get this irregularly whenever i delete snippets of audio in the wave editor. really irritating and inconsistent. and it seems to create porblematic clicks and pops later in the file from time to time (i.e. NOT where i made the edit)
I sure wish apple would fix this.
my setup fyi:
g5 dual 2.7
4gb ram
logic 7.1.1
os 10.4.2

THE PREFERENCES FILE IS LOCATED IN YOUR PREFERENCES FOLDER
~/LIBRARY/PREFERENCES/
THEN DO A SEARCH FOR 'LOGIC', DRAG THOSE FILES BEGINNING WITH COM.APPLE.LOGIC-DRAG THEM TO THE DESKTOP-YOU MAY WANT THEM LATER TO RESTORE YOUR KEYS. GET PRO APP SUPPORT FROM APPLE (FREE DOWNLOAD). GET 10.3.9. FIX YOUR PERMISSIONS. UPDATE TO LOGIC 7.1.1.

Similar Messages

  • Logical end of file error

    I am getting a "logical end of file error =39" message when trying to export audio to SDII for making a time stamped (BWF) . Any ideas?

    How long is the wedding video?
    My standard list of things to do first...
    Run MacJanitor (free download) to do all the Unix Cron Maintenance scripts.
    Run Disk Utility (Applications -> Utilities) and repair disk permissions on your start up drive (typically your internal drive). Also verify any other drives mounted on the system.
    Run Preferential Treatment (free download) to check for corrupt/damaged application and system preference files.
    Run Cache Out X (free download) to clear all system and application caches.
    Reboot your Mac.
    If you still can not get it to run correctly, next thing to try is to throw out the iDVD preference file (don't forget to change back those preferences you want different from the defaults next time you run it). If it still doesn't work, then I would suggest you reinstall iDVD.
    Patrick

  • Logic board has an error code running A.H.T.

    I ran AHT 2.0.1 on my MDD Dual 1.25 OS10.4.11
    It said the logic board had an error code.
      2PFW/2/3:Firewire
    The test stopped.
    I this serious?
    What should I do?
    Shamus

    Firewire external DVD & HD work fine for me in 10.4.11.  Never tried target disk mode.  
    Anyway, if AHT found an error with your firewire port, I'd say you have a hardware problem with the firewire port not a software problem.   If you have lived with it this long, you can live with it a while longer.
    I guess the question it how do you skip the firewire hardware test???   I do not know. Anyone know?
    Robert

  • LSMW LOGICAL PATH not set error

    Hi,
        when i save an lsmw the error is coming as logical path not set. I guess this is for the CONV and READ files. Can ne one tell where can we speicfy this path. Right now we have to manually store the paths for these. Where in the settings can we defualt this path for these files.

    Check the Specify Files Step:
    Files
            Legacy Data          On the PC (Frontend)
                Input File                     D:\Documents and Settings\file4.txt
                                               Data for One Source Structure (Table)
                                               Separator Tabulator
                                               Field Order Matches Source Structure Definition
                                               With Record End Indicator (Text File)
                                               Code Page ASCII
            Legacy Data          On the R/3 server (application server)
            Imported Data        File for Imported Data (Application Server)
                Imported Data                  /usr/sap/tmp/ZHR.lsmw.read
            Converted Data       File for Converted Data (Application Server)
                Converted Data                 /usr/sap/tmp/ZHR.lsmw.conv
            Wildcard Value       Value for Wildcard '*' in File Name

  • Logical Standby - Log Apply Error

    Hi All
    I have configured a 10.2.0.4 logical standby database (single instance) for RAC primary by LOG APPLY process stopped with this error:
    ORA-01422: exact fetch returns more than requested number of rows.
    Now I did run this command before creating logical standby: EXECUTE DBMS_LOGSTDBY.BUILD;
    And I know that there are 80 tables which cannot be uniquely identified, which is fine by business.
    Could you someone please tell how can I deal with this problem.
    Regards
    Amit

    I have configured a 10.2.0.4 logical standby database (single instance) for RAC primary by LOG APPLY process stopped with this error:
    ORA-01422: exact fetch returns more than requested number of rows.
    Now I did run this command before creating logical standby: EXECUTE DBMS_LOGSTDBY.BUILD;
    And I know that there are 80 tables which cannot be uniquely identified, which is fine by business.
    Could you someone please tell how can I deal with this problem. It looks like a Bug too, check this below note
    *Bug 5889516 - Intermittently ORA-1422 logical standby errors [ID 5889516.8]*

  • Xml files from logic to fcp. translation error

    using final cut pro 5.1.4 and logic 7.3.2. creating a slide version of a musical show i wrote. sent the fcp file to logic as xlm, in order to record the singing along with the prerecorded music aif file. did the vocal record in logic, but when i try to send the xlm back to fcp i get a message: translation error, critical error. so now i have no way to get the file back to fcp, after all that work in logic 7.3.2. alas!! previously i got that same error message and discovered that in logic i had been working in 48,000 sample rate files, but this time around i was careful to avoid that problem, and checked the audio window to be sure everything is in 44,000 files. alas! alas! moan, sigh . . .

    Welcome to the bizarre world of XML.
    Given that you're on Logic 7 then I'm sorry to say that these formats have never been particularly reliable (same with L8), but I heard it's better in L9 but I've not tried it yet.
    Some report no problems, others can't get it to work at all. I can't offer a workaround as I'm not sure what you want to achieve exactly, but I can tell you it's one of those things that's totally unreliable.

  • Derived Logical Column throws an error

    Hello
    I get the 46036 error from Answers when I add a field that I created in the BMM of the RPD. We are on OBIEE 10.3.4.2. I added a logical column to a table and applied a filter for a particular age band. I can check the change in without any errors but when I use that field with that expression I get the nQSError.
    *[nQSError: 46036] Internal Assertion Condition pExpr->IsValueExpr(), file*
    Ahsan/Naveen, any ideas on this? You guys have been always helpful with my questions.
    Thanks,
    Dan

    Not sure if this helps but found a few things online on this..may just require a resave or re-import of the specific report (http://tipsonobiee.blogspot.com/2009/06/error-nqserror-46036-internal-assertion.html). If you are on Solaris 64 there is also a bug associated with this. "[nQSError 46036] Internal Assertion Error" After Upgrading to OBIEE 10.1.3.3.2 [ID 566463.1] suggesting to change the following parameter:
    A workaround is to make only off line changes.
    The bug states the following:
    "The solution was to set the following in NQSConfig.INI
    SERVER_THREAD_STACK_SIZE = 1024 KB"
    This is not the same exact OBIEE version. Try these 2 suggestions and let us know how it goes.

  • BPC Script Logic - XDIM_FILTER results in error

    I am writing a Script Logic in BPC and I need it to include all records where the DESTINATION dimension member has the Dimension Property of PLANDEST = "Y"
    This approach works:
    *SELECT(%DestinationMbrs%,"[ID]","Destination","[PlanDest] = 'Y'")
    *XDIM_MEMBERSET DESTINATION = %DestinationMbrs%
    This approach does not work:
    *XDIM_MEMBERSET DESTINATION = <ALL>
    *XDIM_FILTER DESTINATION=[DESTINATION].PROPERTIES("PlanDest")="Y"
    It results in the error message at runtime:
    Error in step 1 of QueryCubeAndDebug: -2147467259 Query (1,156) The PLANDEST dimension attribute was not found.
    The reason I would like to use the second approach is that the first approach relies on the SELECT statement.  The documentation on the SELECT statement says:
    The *SELECT statement is executed at the time the logic is validated, and the expanded result is
    written in the LGX file. This means that if the related dimension is modified, it may be necessary
    to re-validate the rules.
    So if I change the DESTINATION dimension members PLANDEST flags, I need to re-validate the script logic.  That is a maintenance nightmare and a problem waiting to happen.
    How do I solve this so that the dimension attribute is evaluated at runtime, not at logic validation time?

    As Yuan Said, if you are using MDX logic and want to use property, you should check Inapp at the 'manage property' menu of admin console.
    Usually, InApp sholud not be selected for better performance of MDX query. (SAP recommendation)
    But. Here are two cases that you should select.
    1. MDX logic in the logic script.
    2. Dimension formula.
    I hope it will make clear for all.
    James Lim

  • Logical Standy - create table error

    Hi,
    I have a primary database from which i create a new table as:
    create table abc as select * from xyz;
    On the logical standby the table is NOT created and I get lots of PL/SQL errors in the alert_log created via the STDBYLOG session. The table cannot be created and I have to skip it manually.
    should the create table statement work on the logical standby automatically? Has anyone else used this with success.
    Thanks,
    Steve.

    By default, DDL on the primary should be replicated on the logical standby (at least in Oracle 9.2-- haven't looked into earlier versions). There is a section in the Oracle Data Guard Administrator's Guide on how to skip applying DDL to the logical standby http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96653/manage_ls.htm#1017328. Is it possible that the standby system was configured to ignore new tables?
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Logic Pro X - an error has occurred

    Hi,
    I bought the new LPX yesterday, started downloading and left my MBP. When I got back I had a message saying "Can not get Logic Pro X". Among my programs in App Store I find LPX and after that it says in red letters "An error has occurred" (well, in Swedish). When I click install it says "650 MB of 650 MB - 1 minute", but then the same message comes back. "Can not get Logic Pro X". I also bought MainStage and that is working fine. I can find LPX among my programs but the file is only 351K...
    Any solutions?

    Having struggled with this over some days, I tried safe mode. It worked. Good tip!

  • Logic Pro 8 Issues, Error Messages

    Hi all.
    I've been having a variety of problems with my home recording studio, which i have neglected to post about until now- from what i've read it seems no-one knows how to fix them. I'm turning to the MacTalk community to resolve my woes... First things first, here's the gear:
     MacBook Pro (mid-2008), 2.4GHz C2D, 4GB RAM, OS X 10.5.6.
     I use Logic Pro 8 primarily, and this is where all the errors are popping up. I record to WAV, 24-bit, 48KHz (for the sake of diagnosing errors, I have tried 16-bit, 44.1KHz and noticed no difference).
     All audio-related work is handled on a WD MyStudio External FW800 HDD.
     My audio interfaces are an Apogee Duet, and an M-Audio ProFire 2626 (both running latest drivers).
    Now, there are 3 (possibly related) problems i'm having with my setup.
    ✖ Problem #1
    I receive an error message indicating a 'System Overload' at random times during playback and occasionally recording.
    It halts the audio, and I need to click play or record again. Sometimes it happens again and again, other times it’s just a one-off. This problem can occur with either the Duet or ProFire interface. Apparently the number of tracks I’m recording or playing is irrelevant, as it happens under many different circumstances.
    ✖ Problem # 2
    I receive an error message telling me that the “Drive is too slow, error -10004”, and this happens only in recording (I think; oh and it looks like the previous dialogue box). As mentioned above, I use a FW800 external HDD, so it shouldn’t be a hardware requirements issue – it SHOULD be fine as far as I know. It was particularly bad when I was recording 5 channels of audio into the ProFire 2626. Like the previous issue, it halts the recording, and sometimes recurs. It may not happen with the Duet.
    I may be imagining things, but I think it records fine indefinitely when I’m recording near-silence, i.e. not playing my drums. It almost seems as though the problem is triggered when I get particularly loud. Perhaps it’s clipping, I’ll have to check. Still, it shouldn’t cause an error that halts recording should it?
    ✖ Problem #3
    This one only occurs with the ProFire. I get minor crackles and little bits of distortion and ugly tearing sounds in some channels occasionally. They each only last a fraction of a second, and usually aren’t particularly loud, but they spoil takes. Can occur during silent passages OR loud parts.
    For the record, I typically record to WAV, 24-bit, 48KHz, with a 128 or 256 sample buffer, Medium Process Buffer Range, and Software Monitoring enabled. However, I have tried up to 1024 sample buffer, Large Process Buffer Range, 16-bit, 44.1KHz WAV, and turned off Software Monitoring – none of this made a difference.
    So, if anyone thinks they can help me out here, please do so! I’ll greatly appreciate any input ☺
    Cheers,
    Chris

    1. http://support.apple.com/kb/TA24535?viewlocale=en_USy
    This problem points to a buffer that is set too low. Make it one step bigger, but leave the I/O safety buffer OFF.
    also: you can disable the warning message.
    2.
    CAN also be buffer-related, but it may be the disk. Is it a 5400 or 7200 RPM disk?
    It may also be that memory is too full. I would recommend installing Menumeters (freeware) http://www.pure-mac.com/diag.html#menumeters
    You can monitor CPU-use, disk activity, memory use, paging activity and network activity with it.
    Another thing to consider is to Freeze all Software Instrument tracks before recording. Also freeze heavily 'insert-pluginned' audio tracks. This may free up a lot of CPU power.
    3. This problem might benefit from the above tips as well, but I think you can win the most by NOT using software monitoring when recording (for all three issues); it brings extra latency and puts much more strain on the CPU. Through which plugs do you monitor? And why?
    I'ld recommend using the direct monitoring capabilities of both your interfaces, and avoid Software Monitoring when recording. Also being aware of what is going on (by using both Menumeters AND Logics' own CPU-meters) can be crucial - especially Paging (when active RAM is written to or read from disk) can disturb Logic, as well as background OS X applications that kick in during a session.
    I also recommend turning off Journaling before a recording session. To do that, open *Disk Utility*, select the recording disk from its' list, hold down the ⌥ key and choose the menu *File>Disable Journaling*.
    To turn it back on after recording, same actions, only now the menu item will say *Enable Journaling*.
    regards, Erik.

  • Logic Pro 8 launch error

    My O/S was corrupted so we installed it again, now Logic pro 8 files won't open & I get this error message
    'This version of Logic Pro requires Pro Application Support 4.0 (687.0) or newer ProKit: 591.0'
    Any idea what I can do ?

    Download and install pro application support 4 then:
    http://www.apple.com/downloads/macosx/apple/application_updates/proapplicationsu pport402.html

  • Logic Pro 8 Licensing Error

    Whenever I open Logic Pro 8, It asks me to enter my name and my serial number, which I do. It then gives me a warning saying "Licensing Error" And then "The license file will not be written to disk because the user does not have enough privileges." Logic then operates perfectly normally after that, but it reoccurs every time I open Logic. I would like to get this resolved before I install Logic Studio 9.
    Any help would be greatly appreciated.

    I have the same problem. I have an original copy of Logic Express, but this problem only started after I re-installed Leopard. It is really frustrating. Can anyone help?

  • Logic 9 Quartz Extreme Error

    Hi,
    I just bought a brand new mac pro (quad core with Nvidia graphics card) and also a brand new copy of logic studio 9. When i click on the installation icon it says i dont have 'quartz extreme' and can not install logic?! It did not mention any of this on the system requirements on the package. any idea of what to do?
    cheers

    thanks for the response guys.. I ended up fixing the problem late last night.. I do have the latest version of OSX and i still dont know why that error message came up.
    however, what i did do, i went to the system preferences and changed the resolution, and then changed it back to the default resolution and it worked no problem. then i t took me like 3 hours to install the 456 DVDs for logic LOL..

  • Logic Pro X 10010 error - Disk too slow

    Hey,
    I installed the most recent OSX update and now Logic Pro X is giving me the 10010 error quite often. This didn't happen much at all before installing that OSX update. Highly annoying and gets in the way of my workflow. Here's my set up:
    OSX 10.9.4
    32 gigs of DDR3 RAM
    Logic Pro X 10.0.7
    SDD 1 - OS (400 gigs free)
    HDD 1 - Project files (635 gigs free)
    HDD 2 - Samples/SFX Source (1.04 TB free)
    HDD 3 - Samples/SFX Source (1.09 TB free)
    MOTU - up to date with the latest drivers as well
    I/O Buffer size: 512 samples
    Process Buffer Range: Medium
    Everything was running super smooth for a long time before updating my OS. This error happens when I'm running Logic sessions of only audio, or only samples and doesn't seem to matter which drive I'm referencing. It happens when I'm working to video and when I'm not. Other DAWs, such as Reason, don't seem to have this issue at all and their samples (or refills) are located on the same HDDs. Any help would be greatly appreciated. If you guys need any additional info - just ask.
    Thanks,
    Nate

    Let me preface this by saying I'm no kind of expert, so protect yourself accordingly.
    I have been having the same problem. It appears that the new update, as part of its energy/battery life savings, is more aggressive about  spinning down and parking the hard drive. I haven't timed the interval, but my sense is about 5 minutes. I've developed the habit of, after any pause more than a couple of minutes, clicking on "Play," watching the beach ball for a few seconds while the drive spins back up, and then when the playback head starts to move, you're good to go. I've not gotten the error in any situation without the pause.
    Good luck.
    Larry

Maybe you are looking for