Logic corrupts DS_Store file?

I have some really strange behavior on my machine:
I upgraded today from 10.4.1 to 10.4.2 and everything went smooth. After the install and the permission repair, Logc 7.1 launched with no problem and everything seemed to be fine. A little bit later when I did some work in the FInder, I noticed that I couldn't opened some folders. I got the spinning beach ball and the system seemed to be locked up even if there was no significant CPU, disk or network activity. If I were lucky, I could open the Force Quit window and relaunch the Finder. After some testing I found out that the hidden ".DS_Store" file seemed to be corrupted. If I encountered any folder which I couldn't open, I deleted its DS_Store file inside the Terminal and the folder opened again.
After I deleted all those files from the problematic folders, everything seemed to be stable again. I continued to work with Logic and found out later that some folders had the same problem again. After a tedious process of trial and error, I found that all the folders which encountered the open-folder-spinning -ball issue were folders with Logic files:
~/Library/Application Support
~/Library/Preferences
~/Library/Caches
This is my conclusion so far: I Logic writes a file (most likely .plist files) to a folder and corrupts the DS_Store file, or the Finder doesn't update the DS_Store file with the new information from Logic.
Maybe something went wrong during the OSX 10.4.2 upgrade? I did the upgrade on a second G5 (same Dual 2.5GHz with similar configuration and Logic 7.1) a few weeks ago when it came out and I don't have any problem there.
Anyone with a clue what is happening here?
Thanks

AJD1170 wrote:
A .DS_Store file keeps appearing on my desktop. It returns seconds after I have moved it to the trash.  I have deleted the .DS_Store files (hidden) from wherever I have found them, but like the desktop icon, they immediately reappear.  I some time ago stumbled upon the solution, but it evades me now. How do I get rid of this nuisance permanently?
You want and need those .DS_Store files.
You need to hide hidden files in terminal,  copy and paste:
defaults write com.apple.finder AppleShowAllFiles FALSE ;killall Finder
Finder will create a .DS_Store file in every folder that it accesses including your Desktop folder. You witness this everytime you try and delete it.

Similar Messages

  • How do I create a new .DS_Store file for the Desktop?

    I have an account, in this case it is the System Administrator account (which I seldom use), where the Desktop icons all scrunch up to the right side of the screen. I can re-arrange them, but when I log out and sign back on, the icons are shifted back to the right side of the screen. I thought perhaps I had a corrupted .DS_Store file that needed to be removed. However, it turns out that I can find no .DS_Store file to remove for this account. Finder just doesn't seem to be able to create a new one. I'm not sure how or when the old one disappeared.
    Any suggestions how I can get the Finder or something else to create a new .DS_Store for the Desktop so that icons will stay put?

    I think I found an answer (not a solution) to my problem. Consulting with Apple Support, there is no way for the System Administrator's desktop to "remember" the positions of icons from one session to the next. They will always move to the right-hand side of the screen when you log back in. Apparently this is a change that occurred with OS 10.6.4. No reason by Apple given for the change, nor is it readily apparent to me why the Desktop or Finder in the System Admin account should work any differently than in any other account. Might simply be an oversight or a bug.
    If anybody has a fix, I would appreciate learning about it.

  • Corrupt audio file prevents me from opening Logic project file

    Hello,
    I've been running Logic 8 for a couple years off my MacBook and have never encountered any significant problems of file corruption until recently.
    The issue I encountered is this:
    I've been producing a lengthy track in an on-going Logic project file for some time and after completing a recording session I saved and started deleting excess track copies to clean up my arrange window. Upon doing so Logic unexpectedly crashed.
    After attempting to reopen the project file, it started its normal process of loading its respective audio files, but now it hangs on one particular audio file indefinitely (I'll refer to it as 'audio file x' for ease of reference), freezing and crashing Logic as a result. All of this project file's auto backup files are also incapable of being opened without giving me the same result and crashing Logic.
    I have no way of opening this project file and getting at my most recent saved sequence!
    I've tried removing this corrupt 'audio file x' from the project's audio folder and dragging it to the desktop, but this had no effect and I still can't open any recent version of the project file.
    Older saved copies of the current project file do still open though (most likely because they were saved prior to the corruption caused by this suspect 'audio file x.') When opening an earlier iteration of the project, I get a message '1 invalid audio region found' (I assume referring to the corrupt suspect 'audio file x' that I removed to the desktop) but the project file is still able to open.
    I realize I could import the audio files from the most recent version of the crashed file to an older project version and reconstruct things back to the way they were, but it would take me a lot of time and I'm hoping there may be some way to recover the un-openable project file by getting it to stop looking for this corrupted 'audio file x' on startup.
    When I click 'show package contents' of the Logic Project file, I notice two items labeled 'displayState' and 'documentData.' From my troubleshooting I've come to the basic understanding that the 'documentData' file contains all the sequence data and settings for its respective Logic Project file.
    I think the 'document data' of the unopenable project file in question may be corrupt because whenever I replace it with the 'document data' from an earlier Project file version, the file is able to open. This doesn't do me much good though, because it's document data from an earlier iteration of the project and I need to be able to get at the current sequence I had right before my file crashed.
    Is there anyway to open a project file without letting it load its audio files? Or is there anyway I could get inside the 'document data' file to delete the reference/pathway in its audio bin to the corrupt 'audio file x' its hanging on?
    Any insights would be greatly appreciated. I'm hoping there's some way I won't have to repeat a couple days worth of work. Thanks for your help!

    stooby3535 wrote:
    After further troubleshooting I've realized that the suspicious audio file that prevents the project file from opening is actually not corrupted itself. I can still play the audio file in other media software like Quicktime, etc. with no problem.
    This leads me to believe the problem opening the project file lies solely with the corrupted 'documentData' file.
    Does anyone have any ideas about how I could somehow open this project file and delete the reference of the troublesome audio file from the project's audio bin?
    Well... it really sounds like the project itself is corrupted, that's one of the reasons all project files won't load from a certain point on.
    Try this.
    Reboot the Mac.
    Open the Applications folder and boot Logic from it's icon.
    As soon as the Logic Logo/graphic window appears on the screen hold down the control key. You will see a message pop up that says something like "Launch the Core Audio Driver" there will be yes/no choice available... select NO.
    Go to the File menu and selct "open" go find your project file and see if it will open. If it does.. delete the audio file in question... however.. I would also look at any plugins you recently installed and are possibly using in this project...this sounds more like a plugin problem rather than an audio file problem, but that's just a gut feeling.
    Anyway, if it opens delete whatever you suspect and save under a different name.
    Reboot Logic and see if it can load the project.
    pancenter-

  • Logical end-of-file reached during read operation

    Hi,
    Something strange happened to my Logic a couple of days ago - all of a sudden. When I start Logic up it gives me the following error message:
    *Error reading/writing file “com.apple.logic.pro.cs”: Logical end-of-file reached during read operation.*
    I have re-installed Logic, as well as updated it (8.0.2), I have repaired disk permissions in Disk Utility, and it still keeps popping up. I cannot get on with my projects and I have deadlines!
    I found an IT support site, according to that I don't have enough space on my HD. However, I do... I'm confused, and desperately need help.
    Thank you so much, I'm looking forward to hearing from somebody.
    Agnes

    I am not opening any files, just launching Logic.
    I know. And when you launch Logic, it loads its preferences files - and it seems this is failing - most likely due to file corruption. So delete the file, as I said, and Logic should load fine.

  • 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

  • Logical corruption in datafile

    what is logical corruption.
    How this can occur in datafile , is it related caused due to disk.
    how to avoid this.
    Is it possible to check the this on regular interval. with some job script .. any idea what command how to do it .. does dbverify will do.
    Any good reading/url is most welcomed.
    Thank You Very Much.

    user642237 wrote:
    what is logical corruption.
    How this can occur in datafile , is it related caused due to disk.
    how to avoid this.
    Is it possible to check the this on regular interval. with some job script .. any idea what command how to do it .. does dbverify will do.
    Any good reading/url is most welcomed.
    Thank You Very Much.What's the db version and o/s? Where did you read the term logical corruption in datafiles? AFAIK, datafiles get physically corrupted only. The logical corruption happens within the blocks , for example some index entry pointing towards a null rowid. I am not sure that I have come across any situation/reference where this corruption is mentioned for files as well. To check it, the best possible tool is RMAN which can do the job by some simple commands.
    HTH
    Aman....

  • Logical corruption found in the sysaux tablespace

    Dear All:
    We lately see the logical corruption error when running dbverify command which shows the block corruption. It is always on the the sysaux tablespace. The database is 11g and platform is Linux.
    we get the error like:error backing up file 2 block xxxx: logical corruption and this comes to alert.log out of the automated maintenance job like sqltunning advisor running during maintenance window.
    Now As far as I know,we can't drop or rename the sysaux tablespace. there is a startup migrate option to drop the SYSAUX but it does not work due to the presence of domain indexes. you may run the rman block media recovery but it ends with not fixing since rman backups are more of physical than maintain the logical integrity.
    Any help, advise, suggestion will be highly appreciated.

    If you let this corruption there then you are likely to face a big issue that will compromise database availability sooner or later. The sysaux is a critical tablespace, so you must proceed with caution.
    Make sure you have a valid backup and don't do any thing unless you are sure about what you are doing and you have a fall back procedure.
    if you still have a valid backup then you can use rman to perform a db block level recovery, this will help you in fixing the block. Otherwise try to restore and recover the sysaux. In case you cannot fix the block by refreshing the sysaux tablespace then I suggest you to create a new database and use aTransportable Tablespace technique to migrate all tablespaces from your current database to the new one and get rid of this database.
    ~ Madrid
    http://hrivera99.blogspot.com

  • Keep getting message pop up "Error reading/writing file  "com.apple.logic.pro.cs": Logical end-of-file reached during read operation," and "The Preferences are not loaded completely. Save them to "com.apple.logic.pro.cs" anyway?" Using Logic pro 8. ???

    Logic froze while I was working on something so I forced quit.  Now every time I open LOGIC a message pops up that says:
    "Error reading/writing file
    “com.apple.logic.pro.cs”:
    Logical end-of-file reached during read operation."
    The only button option is cancel so I press it and another message appears that says:
    "The Preferences are not loaded completely.
    Do not save them, as you would overwrite the Preferences file with incomplete data."
    Then when i close logic a box appears saying:
    "The Preferences are not loaded completely.
    Save them to "com.apple.logic.pro.cs" anyway?"
    There are 3 button options to press; ok, cancel or dont save.
    I press "don’t save" cuz I don't want to ruin anything.
    I found a discussion located here: https://discussions.apple.com/message/9564253#9564253 that says if I delete the file "com.apple.logic.pro.cs" it will resolve the problem.  If I do this will I loose or mess anything up at all, automation, saved channel strips customizations, saved effects, synth, or ultrabeat customizations etc? Or especially will I loose any work I've done?  I have hundreds pieces of music files I've created.  I'm scared to mess anything up with all the hours and months of work I've done.  Is there anyway to fix this without loosing anything?  I'm using Logic Pro 8.
    Thank you

    You can safely delete this file - its the preference file for control surface settings - you haven't said whether you're actually using a control surface or not, if so, you will have to set it up again. A new file will be created when you fire Logic up again, but of course it will contain default settings. If you have a complicated control surface setup, remember to keep a backup copy somewhere in case any future problems arise.
    Other than that, you really have nothing to be scared about - hopefully your problem is as simple as that and there isn't an underlying problem (a corrupt hard drive, for example). You seem concerned about losing work, so I guess you want to think about backing that up on a regular basis too. If you're saving your projects to your system drive, do get an external one for this. And also check that you have plent of free space on your system drive - you need to keep about a quarter or third of it free for your OS and programs to run properly (some temporarily stored files can be quite large).

  • Error "logical end of file reached during read operation"

    I am trying to burn a dvd of a wedding I did, and this is the error I am getting. After 5 hours of it trying to burn when I click cancel this it says " logical end of file reached during read operation". Does anyone know what this means, and how I can fix it? I am anxious to get this wedding finished and out to the customer. Any help would be greatly appreciated.

    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

  • EXS 24 Logical end-of-file reached during read operation Result code = -39

    EXS kit Trip Hop Remix will not completely load. Upon trying to load it I get the error, Logical end-of-file reached during read operation Result code = -39. The kit ends up lacking samples. It worked at one time but now it will not load up. To try and fix I extracted two kits with the same name but oddly they are slightly different sizes and have different creation dates, one 2004 the other 2007 hmmm (one goes in Garage band for remix tools the other gets placed in 02 Electronic Drum kits) from the install disks using Pacifist hoping to replace corrupted files. NG. I also reinstalled all the samples from the LP8 install disk, still NG. Anybody have a solution. THanks.

    To further clarify, the samples are all located in the folder Garage band/.../.../.../Sampler Files/Treated Percussion Sets/Perc-DnB+Triphop. They are used in the EXS24 Trip Hop Remix kit.exs. The 3 samples that seem to be causing the error are, YT2BGLRHTX02_3ue.aif, YT2BGLRHTX03_3ue.aif, YT2BGLRHTX04_3ue.aif. The kit is useless and my song is screwed up now that the kit will not load. Any ideas for a fix out there ?

  • What mean "logical end-of-file reached" messaage ? (screen attached)

    I see that when loading project. Is all ok after i press OK but what is that means ?

    Not seeing a picture... are there audio files associated with this project?
    Logical-end-of-file-reached usually refers to a corrupt audio file where the data header file end does not match the actual file length. In other words, the audio file it truncated or the file header describing the file is corrupt.
    It could also be an audio file has been marked "read only" but that is less likely.
    Are you sure all of your audio files are working correctly.

  • Backup and Logical Corruption

    Hello,
    I am running a backup and checking for any logical corruption -
    RMAN> backup check logical database;
    Starting backup at 03-MAR-10
    allocated channel: ORA_SBT_TAPE_1
    channel ORA_SBT_TAPE_1: SID=135 device type=SBT_TAPE
    channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
    allocated channel: ORA_SBT_TAPE_2
    channel ORA_SBT_TAPE_2: SID=137 device type=SBT_TAPE
    channel ORA_SBT_TAPE_2: Data Protection for Oracle: version 5.5.1.0
    allocated channel: ORA_SBT_TAPE_3
    channel ORA_SBT_TAPE_3: SID=138 device type=SBT_TAPE
    channel ORA_SBT_TAPE_3: Data Protection for Oracle: version 5.5.1.0
    channel ORA_SBT_TAPE_1: starting full datafile backup set
    channel ORA_SBT_TAPE_1: specifying datafile(s) in backup set
    input datafile file number=00014 name=/oracle1/data01/TESTDB/TESTDB_compress_test_01.dbf
    input datafile file number=00006 name=/oracle/TESTDB/data01/TESTDB_shau_01.dbf
    input datafile file number=00015 name=/oracle/product/11.1/dbs/ILM_TOOLKIT_IML_TEST_TAB_A.f
    channel ORA_SBT_TAPE_1: starting piece 1 at 03-MAR-10
    channel ORA_SBT_TAPE_2: starting full datafile backup set
    channel ORA_SBT_TAPE_2: specifying datafile(s) in backup set
    input datafile file number=00003 name=/oracle/TESTDB/data02/TESTDB_undo_01.dbf
    input datafile file number=00013 name=/oracle/TESTDB/data01/TESTDB_roop_01.dbf
    input datafile file number=00012 name=/oracle/TESTDB/data01/TESTDB_example_01.dbf
    input datafile file number=00005 name=/oracle/TESTDB/data01/TESTDB_sysaud_tab_1m_01.dbf
    channel ORA_SBT_TAPE_2: starting piece 1 at 03-MAR-10
    channel ORA_SBT_TAPE_3: starting full datafile backup set
    channel ORA_SBT_TAPE_3: specifying datafile(s) in backup set
    input datafile file number=00004 name=/oracle/TESTDB/data01/TESTDB_users_01.dbf
    input datafile file number=00001 name=/oracle/TESTDB/data01/TESTDB_system_01.dbf
    input datafile file number=00002 name=/oracle/TESTDB/data01/TESTDB_sysaux_01.dbf
    input datafile file number=00025 name=/oracle/export_files/TESTDB_users_02.dbf
    channel ORA_SBT_TAPE_3: starting piece 1 at 03-MAR-10
    channel ORA_SBT_TAPE_3: finished piece 1 at 03-MAR-10
    piece handle=5ul7ltsd_1_1 tag=TAG20100303T204356 comment=API Version 2.0,MMS Version 5.5.1.0
    channel ORA_SBT_TAPE_3: backup set complete, elapsed time: 00:05:15
    channel ORA_SBT_TAPE_2: finished piece 1 at 03-MAR-10
    piece handle=5tl7ltsd_1_1 tag=TAG20100303T204356 comment=API Version 2.0,MMS Version 5.5.1.0
    channel ORA_SBT_TAPE_2: backup set complete, elapsed time: 00:06:56
    channel ORA_SBT_TAPE_1: finished piece 1 at 03-MAR-10
    piece handle=5sl7ltsd_1_1 tag=TAG20100303T204356 comment=API Version 2.0,MMS Version 5.5.1.0
    channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:08:16
    Finished backup at 03-MAR-10
    Starting Control File and SPFILE Autobackup at 03-MAR-10
    piece handle=c-2109934325-20100303-0c comment=API Version 2.0,MMS Version 5.5.1.0
    Finished Control File and SPFILE Autobackup at 03-MAR-10
    Question: By looking at the output, how can I say that RMAN did an Logical Check for the corruption? This output looks same as a simple backup without logical corruption check. Please advice how to check about this?
    Thanks!

    hi
    I think you won't see any summary on this, only when corruption is found.
    There is also one related setting that can be incorporated here - see example:
    Example 2-25 Specifying Corruption Tolerance for Datafile Backups
    This example assumes a database that contains 5 datafiles. It uses the SET MAXCORRUPT command to indicate than no more than 1 corruption should be tolerated in each datafile. Because the CHECK LOGICAL option is specified on the BACKUP command, RMAN checks for both physical and logical corruption.
    RUN
    +{+
    SET MAXCORRUPT FOR DATAFILE 1,2,3,4,5 TO 1;
    BACKUP CHECK LOGICAL
    DATABASE;
    +}+
    use this to see clear output:
    -- Check for physical corruption of all database files.
         VALIDATE DATABASE;
    -- Check for physical and logical corruption of a tablespace.
         VALIDATE CHECK LOGICAL TABLESPACE USERS;
    eg.
    List of Datafiles
    File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
    +1 FAILED 0 3536 57600 637711+
    File Name: /disk1/oradata/prod/system01.dbf
    Block Type Blocks Failing Blocks Processed
    Data       1              41876
    Index      0              7721
    Other      0              4467

  • Ocrcheck shows "Logical corruption check failed"

    Hi, I have a strange issue, that I am not sure how to recover from...
    In a random 'ocrcheck' we found the above 'logical corruption'. In the CRS_HOME/log/nodename/client/ I found the previous ocrcheck was done a month earlier and was successful. So, something in the last month caused a logical corruption. The cluster is functioning ok currently.
    So, I tried doing an ocrdump on some backups we have and I am receiving the following error -
    #ocrdump -backupfile backup00.ocr <<< any backup I try for the past month
    PROT-306: Failed to retrieve cluster registry data
    This error occurrs even on the backup file taken just prior to the successful ocrcheck from a month earlier. The log for this ocrdump shows -
    cat ocrdump_6494.log
    Oracle Database 11g CRS Release 11.1.0.7.0 - Production Copyright 1996, 2007 Oracle. All rights reserved.
    2010-08-18 12:57:17.024: [ OCRDUMP][2813008768]ocrdump starts...
    2010-08-18 12:57:17.038: [  OCROSD][2813008768]utread:3: Problem reading buffer 7473000 buflen 4096 retval 0 phy_offset 15982592 retry 0
    2010-08-18 12:57:17.038: [  OCROSD][2813008768]utread:4: Problem reading the buffer errno 2 errstring No such file or directory
    2010-08-18 12:57:17.038: [  OCRRAW][2813008768]gst: Dev/Page/Block [0/3870/3927] is CORRUPT (header)
    2010-08-18 12:57:17.039: [  OCRRAW][2813008768]rbkp:2: could not read the free list
    2010-08-18 12:57:17.039: [  OCRRAW][2813008768]gst:could not read fcl page 1
    2010-08-18 12:57:17.039: [  OCRRAW][2813008768]rbkp:2: could not read the free list
    2010-08-18 12:57:17.039: [  OCRRAW][2813008768]gst:could not read fcl page 2
    2010-08-18 12:57:17.039: [  OCRRAW][2813008768]fkce:2: problem reading the tnode 131072
    2010-08-18 12:57:17.039: [  OCRRAW][2813008768]propropen: Failed in finding key comp entry [26]
    2010-08-18 12:57:17.039: [ OCRDUMP][2813008768]Failed to open key handle for key name [SYSTEM] [PROC-26: Error while accessing the physical storage]
    2010-08-18 12:57:17.039: [ OCRDUMP][2813008768]Failure when trying to traverse ROOTKEY [SYSTEM]
    2010-08-18 12:57:17.039: [ OCRDUMP][2813008768]Exiting [status=success]...
    NOTE: an 'ocrdump' of the active ocr does work and creates the ocrdumpfile
    The corruption in the ocr seems to be two keynames pointing to the same block.
    Oracle Database 11g CRS Release 11.1.0.7.0 - Production Copyright 1996, 2007 Oracle. All rights reserved.
    2010-08-18 13:22:54.095: [OCRCHECK][285084544]ocrcheck starts...
    2010-08-18 13:22:55.447: [OCRCHECK][285084544]protchcheck: OCR status : total = [262120], used = [15496], avail = [246624]
    2010-08-18 13:22:55.545: [OCRCHECK][285084544]LOGICAL CORRUPTION: current_keyname [SYSTEM.css.diskfile2], and keyname [SYSTEM.css.diskfile1.FILENAME] point to same block_number [3928]
    2010-08-18 13:22:55.732: [OCRCHECK][285084544]LOGICAL CORRUPTION: current_keyname [SYSTEM.OCR.MANUALBACKUP.ITEMS.0], and keyname [SYSTEM.css.diskfile1] point to same block_number [3927]
    2010-08-18 13:23:03.159: [OCRCHECK][285084544]Exiting [status=success]...
    Since one of the keynames refers to the votedisk, that is not appearing correctly on a query -
    crsctl query css votedisk
    0. 0 /oracrsfiles/voting_disk_01
    1. 0
    2. 0 backup_20100818_103455.ocr <<<<this value changes if I issue a command that writes something to the ocr, in this case a manual backup.
    My DBA is opening an SR, but I am wondering if I can use 'ocrconfig -restore' if the backupfile I want to use cannot be 'ocrdump'd?
    Also, is anyone familiar with the 'ocrconfig -repair' as a possible solution?
    Although this is a developement cluster (two nodes) rebuilding would be a disaster ;)
    Any help or thoughts would be much appreciated!

    Hi buddy,
    My DBA is opening an SRWell.... corruption problems, no doubts that it's better work with support team
    , but I am wondering if I can use 'ocrconfig -restore' if the backupfile I want to use cannot be 'ocrdump'd?No, that is not the idea...if Your backup is not good, it's not safe restoring it. ;)
    Also, is anyone familiar with the 'ocrconfig -repair' as a possible solution?This is for repairing nodes that were down when some kind of change on the configuration (replace OCR for example) has been executed while it was "off", so, I guess it's not Your case.
    Good Luck!
    Cerreia

  • 8 bit / corrupted audio files on re-opening a song

    See the post below. I'm having this exact problem with the latest version of Logic Pro on my intel mac. Is there a solution for this mentioned somewhere already? Please let me know soon.
    Joshua Brown
    Posts: 7
    Registered: Aug 18, 2005
    "8-bit" Corrupted Audio Files On Reload?
    Posted: Aug 18, 2005 10:45 AM
    A day after a recording session with my band the other night, I re-opened the song and recieved an error message "What kind of file is this?" and then another... something about the file being "8-bit" and unusable. This is the bass track from a very good session with my band and I'd like to try and recover it. Does anyone know how this happened, how to recover the file, and how to prevent it from happening in the future? Any help would be greatly appreciated.
    More info: When opening the file in SoundHack, it says that it is a "Headerless" file. Setting the header to 24 bit linear and saving a copy results in an extremely distorted and unusable file, but you can kind of hear the recording in the background... sped up.

    Hello and thanks to all for your replies. Oh and I did in fact copy somebody else's post. Sorry for the confusion.
    I had a backup of the song on another disk with which I continued with my mixing. I am not worried about that particular song now. I am just worried that this might happen again.
    About my sound/sample library, I just deleted the folders which had corrupted files and copied back from my backup disks.
    Dropping corrupted file in a new .lso doesn't work. Haven't tried moving preferences yet but will do. I didn't have a mac before I bought an intel mac.
    Can someone explain why this happened in the newest version when this was supposed to have been resolved in an earlier version? Isn't the latest version a cumulative one?
    There's one other thing that also happened with me this week. I think it's related:
    I had a Logic project open which was set at 96/24 and I had some audio done in it. I tried to open Reason rewired to Logic because I wanted a drum beat from Dr.Rex. Reason was set at 44/16. I tried to open some of the samples from my sound library. The files played just fine but later on when I checked, the folders which I went into looking for that drum beat got corrupted. In fact, it corrupted everything under root folder. It shouldn't have touched my samples at all, right? Why should this happen when I'm trying to just read samples or files?

  • Logic Crashing on File- Open Workaround... Sort of.

    This subject has gotten a bit of attention over the weekend with no real explaination or resolution.
    I have managed to find a partial workaround though that at least allows me to record:
    1) Open Logic
    2) Choose File->New...
    3) Select no Template, and name your file.
    4) Close current song before -> Close
    5) The new file opens and you can record and save as usual.
    However, attempting to insert Audio crashes Logic badly without the nice little message that tells you it crashed.
    It seems that any function that brings up an Open or Save dialog causes the crash to happen. Don't select any option that requires you to choose a Save or Open file and it won't crash. If you need to import an audio track, drag it from the Finder and do not use the Import Audio feature.
    There's no telling what else will make Logic crash in this state, but if you've been not recording all weekend like me, this might get you doing something useful.
    Anyone else have any useful workarounds to this serious problem?

    No shapeshifter installed.
    I worked on solving the problem using my main account, trying to figure out what files were causing the conflict. Things that I found and removed are:
    ~/Library/Save Preferences (with some Logic related files in it)
    Don't know what this is/was, but I didn't create it, and I don't think it was contributing to the crashing.
    ~/Library/InputManagers/ViInputManager
    Someone suggested I remove any input manager I had installed. This was the only one that I found.
    ~/Library/MIDI Drivers/MIDI Monitor.plugin
    Can't remember what this is or why its there. So I removed it.
    These VST Plugins:
    BIAS Freq4
    Bouncy (OS X)
    bs-spectrum.vst
    Carbon MDA VST Effects
    Cyanide 2
    freeverb-c
    Freq-2
    Frohmage_VST2Carbon
    H2O
    Inspector
    mda JX10
    Ohm Force
    PlogueRebuilder.vst
    PolyFractus Resonator 1.01b
    S(m)exoscope
    SupaPhaser
    vbox SE 1.21
    I wasn't ever really using these, but they did seem to pass the initial scan by Logic. Perhaps something in the scan causes a problem. I didn't need them and didn't feel like doing the "conflict catcher" swap all night. I doubt they were causing the problem anyway.
    Components:
    ExSlAugustusLoop.component
    ExSlMeringue.component
    MadShifta.component
    Wasn't using these either so I removed them too.
    The thing I think really resolved the problem, and I tried this before when running through Apple's troubleshooting list, was removing the logic cache files from:
    ~/Library/Caches/Logic
    Perhaps something in here was corrupt from having the 3rd party AUs and VSTs installed. More than one person mentioned they had numerous problems with 3rd party extensions, and even though I didn't really use them, they were apparently installed and possibly in the way somehow.
    There are many more files that I removed that may or may not have been the actual resolution. I find it inconclusive to simply remove everything and have it all working again, considering I could have actually helped Apple diagnose, resolve, and document this particular issue.
    Yes, my question has been answered. Mostly by me and my own determination, and in no way that is particularly useful to anyone except to know they aren't the only person having this kind of problem.

Maybe you are looking for