Result code -43 when bouncing Mp3 in Logic 9

Hey anyone - has anyone come across the same message when trying to bounce an Mp3 in Logic 9?
I'm running 10.9.5.
Aiff and WAVS bounce fine.

Yeah that works fine but it obviously a little annoying still as it's eating up hard disk space and given the amount of bounces I do will eat up for hard drive with uneccesary files unless I bother deleting!
Indeed! It is a bug that several people have reported and as yet it remains unfixed...
Just delete the extra file right away and it's really no bother in the future... though personally I rarely bounce to MP3 these days.... I either bounce to an uncompressed wave or aiff...  or if I must compress the file for some reason... I use M4A AAC. Any particular reason you have to use MP3? (Uploading somewhere in particular for example that requires MP3 format?)
Lesson is to never upgrade! I was coasting before I had to upgrade to get Logic X for a project and now I don't even use it anyway!
This is why several of here are still running Logic pro 9.1.5 and OS X 10.6.8... because it has been proven to be the most stable of combos... and will do so for as long as it is possible (so long as the hardware that allows that combo, continues to work) 
Anyhow.. glad I could help!
Cheers...
Nigel

Similar Messages

  • "Attempt to open locked file for writing, Result Code = -54" when importing

    I get this error box when importing audio files into a logic session over my network.
    +Attempt to open locked file for writing+
    +Result Code = -54+
    The finder is capable of copying the files over to the local machine, at which point I can successfully import them into my local logic session, but Logic is incapable of doing the same. Strange and annoying.

    Have you looked at the previous discussions listed on the right side of this page under the heading "More Like This"?

  • Result Code = -43 when cutting and pasting

    If anyone can help with this, I would be completely thankful.
    I cut a clip to paste it into a new project, so I could edit it by itself. Because of the way Garageband is designed, I had to close (and save) the first project before I could open a new one. When I went to paste the clip, I got a pop up box with the follow:
    "An error occurred.
    Result code = -43
    File = Male Voice#07.aif"
    I tried opening Audacity and pasting it in there, but there's not an option in any other program but Garageband. If I hit "OK" through the error, it pastes a completely blank clip of the same length, but silent.
    Is there any way to recover this clip, or has my Mac completely ruined my project on what should be a simple operation? I don't have time to rerecord this.
    Thanks!

    Oh my, I'm afraid you messed it up. Error code -43 means "file not found". Here's what I think happened:
    • You cut the region out of your original project. The Mac's clipboard now holds a GB region pointing to the audio file - not the audio file itself!
    • You close the original project, probably it prompts you whether you want to save it. If you click "yes", the project is saved, and since it doesn't contain the region you cut out, at this stage the audio file is deleted because it's not being used in the project (that's the way GB handles audio - otherwise the project size would grow indefinitely with all the unused audio takes).
    • Now you create a new project and paste in the region from the clipboard. But as I said, this region only has a reference to the audio file, it doesn't contain the audio itself - it can't find the deleted file, that's why you get the error message.
    If this is what happened, I'm afraid your audio is gone for good. Here's some tips how to avoid that in the future:
    • If the only purpose is editing one track, why transfer it to a new project at all? You can mute the other tracks and edit away.
    • To avoid deleting the original audio, always use the "copy" command, not "cut"!
    • If you successfully transferred an audio region to a new project, immediately use the "Save as Archive" command - that way the audio will be saved in the new project too. Otherwise it only references the old project which you might delete at some time, and then you'd be in the same position.
    Sorry, but I think the only option is to re-record!

  • Bad http result code 501 when submitting a validated feed to iTunes

    I have a podcast feed that I've validated at http://validator.w3.org as well as http://www.feedvalidator.org.  Both tests say that my feed is valid.  When I try to submit the feed URL to iTunes, I get the response: "We had difficulty reading this feed. Bad http result code: 501".  Any suggestions as to what I'm missing?

    Although your feed validates, and can be accessed in a browser and subscribed to in iTunes - and also the media files are correctly hosted on a server which can handle byte-range requests (a required facility) - the server hosting your feed is for some reason unable to handle requests specifically from the iTunes Store. This situation has arisen before but no obvious solution has been suggested (one poster with a similar problem found that it was a permissions issue on the server). This is something you will need to take up with the people running your server - their logs may possibly give some indication of what the problem is.

  • Error code  "File not found Result code = -43"  PLEASE HELP!

    I keep getting this error message: "File not found Result code = -43" when trying to load instruments from the media tab. Does anyone know why this is happening and know how to fix this problem? I'm in the middle of a project and need help! Thanks.

    So, I've narrowed down the problem to happening with the following steps (could someone possibly try this and see if the same problem is happening?)
    If I load an instrument track and its blank and select a GARAGEBAND loop from the media list, I get the error message.
    If I load a new instrument track and select any other instrument from the media list (besides a Garageband instrument) everything loads fine, AND THEN if I select a Garageband instrument from the list, it loads fine with no error.
    If I select "No plug-in" in the channel strip after this, and try to load a Garageband loop, I get the error message and all other instruments from the media lists fail to load until I select "no-plugin" again from the channel strip and select an instrument from the media list BESIDES a Garageband instrument and then go from there (and can then load a Garageband instrument).
    Is anything like this happening to anyone else? Does anyone have any ideas why this would be happening?

  • Urgent! Volume of logic pro song increased when bounced into mp3- why?

    I have tried everything I can think of (but I am new to logic and recording in general, so it feels much like I've been fumbling in the dark). I have put a limiter on the out-put channel, lowered the volume of all tracks, turned off normalization when bouncing, tried to make a new project with the bounced file...- none of that worked.

    Are you listening on exactly the same system that you're mixing on, you can be listening to Logic with the volume of the audio interface turned down and then playing back the Mp3 file on a system with the volume turned up, that's one possibility.
    Remove the limiter form the output bus and lower the master fader, that's a second possibilty.
    Is there a chance that iTunes is setting the normalization tag in the Mp3 file, then when apple playes it on another Apple device with itunes, it normalizes it anyway. Sounds like this is what it is, no matter what volume the mp3 actually is it raises the volume)  It's something new that supposedly levels output, loud songs are brought down a bit and low volume tunes are brought up so that everything is the same level.
    really dislike itunes and never use for anything resembling pro audio. 

  • Dither when bouncing to mp3?

    Back in 2008, someone noticed that Logic does not provide any dithering options on an MP3 bounce.
    To answer his questions, the lossy MP3 compression adds more noise than dither, so you really should start with a 24-bit master and convert directly to MP3 without any dither. The reason Logic doesn't offer the option is because you should not be using dither.
    I regularly use Logic to bounce a mixing and mastering session directly to MP3 or AAC so that the client can hear it with minimal bandwidth. The only issue I have is whether 48 kHz or 44.1 kHz will be appropriate for my client.
    In a little more detail, dither is basically the process of adding noise to a signal so that the bit depth can be reduced without significantly increasing the existing quantization noise. On a 24-bit file (from the 32-bit Logic mix) dither adds noise at about -144 dB, which is incredibly low. Dither on a 16-bit adds noise at about -96 dB. In both of those cases, POW-r dither uses noise shaping to hide this added dither noise behind the existing audio frequencies, hoping that you won't hear anything. When you compress to MP3, the lossy process results in noise that is much stronger than -96 dB, but it still tries to hide behind the audio in much the same way as POW-r (give or take some proprietary algorithms).
    In other words, you don't need dither because MP3 is basically an equivalent process.

    Hey all:
    To help simplify my questions: Does anyone bounce to mp3 in logic? and if so what consideration are being made regarding Dither?
    Id appreciate any comments regarding this..
    Thanks

  • Error: Logical end-of-file reached during read operation. Result Code = -39

    Hello all,
    Recently, I have been suddenly getting this error message:
    "Logical end-of-file reached during read operation. Result Code = -39."
    In my case, when it does come up, it always pops up during the recording of an audio take. Almost immediately after hitting the stop button, this error message would pop up. And then when I go to check the take that was just recorded, there is nothing but shrieking noise. As a result, this pop up error trashes any good take I may have had. It's unpredictable as to when this error decides to pop up as well. So now, when I record, I tend to just have my fingers crossed and hope that this error doesn't pop up especially right after recording a good take!
    To no avail, I have tried different I/O buffer settings, repaired permissions, rebooted, and even re-formatted my recording hard disk.
    Could this be a possible hint that my hard disk is about to physically collapse? I have had it for about 2 years. Could it be some sort of bug in Logic? Or something else perhaps?
    Appreciate any feedback! Thanks a lot!

    DamonGrant wrote:
    Thanks for those suggestions Erik...
    It's been happening for a month I guess and I don't think that anything new's been installed. I will try recording to the start up disc and to maybe to some USB discs I have.
    It seems to happen after working on a project for some time.
    After say tracking takes for 45 mins or so. Maybe it's just coincidence, but do you think that might indicate a hardware issue?
    Now there might be a clue. What happens when you then quit Logic, reboot your Mac, and reopen the active session? It might be that your disk has become a bit messy from all the traffic, and it just needs to 'settle' in OS X again. Click on the *Spotlight icon* top right of your screen and see if any indexing is taking place. Wait for it to finish before launching Logic.
    Alternatively, you could exclude your recording disk from Spotlight indexing alltogether, by dragging the disk to the Privacy field in the Spotlight Sysprefpane.
    One other thing to do: turn off Journaling , using *Disk Utility.* Select your recording volume in Disk Utility, hold the alt key while dropping down the File menu. Choose *Disable Journaling.*
    On the other hand, it might also point to a RAM issue. Do you ever suffer Kernel panics (=the darkening 'curtain' and the message "You need to restart your Mac... etc")? or 'unexplained' crashes? If not or very rarely, I'ld rule out a RAM issue. If daily, it could be. What you can try in this case is to turn of your Mac and physically take out and reinsert your RAM.
    And when you trash (=eject/unmount), physically disconnect and reconnect your recording disk? Does that help? (Logic should not be running when you do this)

  • I/O Error result code -36: Logic bug, or Mac OSX bug?

    Hello-
    I encountered a problem in Logic Pro 8 today that severely damaged one of my audio files in my session. I was working in the sample editor, and I went to copy and paste an audio fragment. When I tried to paste the audio, this error came up:
    "I/O Error, result code = -36"
    After that, the cursor turned into a black and white spinner, and the audio file that I was working with suddenly was altered in a way that somehow erased a portion of it in the song. I had to ability to undo, view the changes in the audio file, etc, etc. It was damaged irreversibly, and I had to end up re-recording that segment. Does anyone know why this happens, and is it a bug in Logic?
    BTW, I have over 500 gigs free on the external drive that I am recording to, and nothing has changed, hardware-wise on my system in over 6 months... Any help would be greatly appreciated.

    Adam Nitti wrote:
    Hello-
    I encountered a problem in Logic Pro 8 today that severely damaged one of my audio files in my session. I was working in the sample editor, and I went to copy and paste an audio fragment. When I tried to paste the audio, this error came up:
    "I/O Error, result code = -36"
    After that, the cursor turned into a black and white spinner, and the audio file that I was working with suddenly was altered in a way that somehow erased a portion of it in the song. I had to ability to undo, view the changes in the audio file, etc, etc. It was damaged irreversibly, and I had to end up re-recording that segment. Does anyone know why this happens, and is it a bug in Logic?
    BTW, I have over 500 gigs free on the external drive that I am recording to, and nothing has changed, hardware-wise on my system in over 6 months... Any help would be greatly appreciated.
    This sounds like one of two things that I have seen with this error :
    1.- your external hard drives' connection to the computer is not 100% stable (loose cable...dusty environment...)
    2.- Your audio device, is ti FireWire too? Is it daisy chained to this external hard drive? Maybe the order of the daisy chaining needs to be looked at.
    Cheers

  • Error code -50 when opening Logic virtual instruments

    I'm getting an error code -50 when trying to open any of the Logic's virtual instruments, VIs from other brands open without a glitch.
    I have searched the support forum but no results came back.
    Please help !!!
    Thanks in advance
    Marcello Azevedo
    G5   Mac OS X (10.4.8)  

    The plugins access the key to check they are authorised to run (remember, the main plugins were separate purchases once upon a time). Obviously, if you are on a USB port/hub that's not agreeing with the XSkey, then communication is unreliable and can take the form of a number of different effects on your system.
    That -50 error probably means the plugin failed to load, as the communication with the XSkey failed during the initialisation process.

  • 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 ?

  • Can anyone answer why in logic pro X I keep getting a window popping up that says Directory not found, result code= -120, followed by another window saying, Fade update failed, (error -120)?

    Can anyone answer, why in Logic Pro X I keep on getting a window popping up saying, Directory not found, result code = -120. Followed by another window saying, Fade update failed, (error -120)?
    I am running the latest version 10.0.5 through a Macbook Pro that has just been upgraded to 16GB Ram and a 960GB SSD which has made it as fast as ****. I upgraded because I was experiencing problems before and it was suggested that I didn't have enough Ram?
    I am using a Focusrite scarlett 2i4 and an Alesis Q61 midi controller. Weirdly, just trying to put a bass line down on a track using the Alesis, the bass sound goes out of tune with the track during recording only. This is very frustrating! I surely can't be the only one experiencing this?
    Many thanks
    Rob.

    Hi
    Time lost could be a problem, but.....
    Sadly, I don't think that there are any Apple docs relating to networked storgae issues with Logic. Other than a 'school' or 'business' setup, NAS/OD/AD setups are not usual circumstances for audio.
    If the issue is one of data backup & security, it may be enough to automatically backup the students local work folders to the NAS.
    If the issue is one of the Users being able to work from any Mac and pick up their files from the server, you are not likely to resolve this problem, without copying the files to the Local Mac.
    CCT

  • Logic x not synced with material in rewire app when played from start and when bounced.

    When rewiring logic x and reason, play from start in logic..(this doesn't happen when you play from start in reason) when the playhead is at 0 it kind of goes back a millisecond and plays... which makes it not synced with material in rewire application. Sure you can always hit play in Reason or Rewire app... but this is completely unsuable when bouncing the project!!!! Help please!!!!

    When rewiring logic x and reason, play from start in logic..(this doesn't happen when you play from start in reason) when the playhead is at 0 it kind of goes back a millisecond and plays... which makes it not synced with material in rewire application. Sure you can always hit play in Reason or Rewire app... but this is completely unsuable when bouncing the project!!!! Help please!!!!

  • Today I stupidly tried to install CUDA accelerator forgetting I have Intel/AMD combo graphics card and not NVidia. Now when I try to launch AE or PremierePro I get this Last log message was: 140735120521568 GPUManager 2 Sniffer Result Code: 3 Help

    Today I stupidly tried to install CUDA accelerator forgetting I have Intel/AMD combo graphics card and not NVidia. Now when I try to launch AE or PremierePro I get this Last log message was: <140735120521568> <GPUManager> <2> Sniffer Result Code: 3.  I have trashed the CUDA program and reinstalled Premiere and AE but no joy.  Same message followed by another error box with options to Retry, Send to Apple or ignore.  I have tried all 3 options but nothing works!  Every time I launch either program same message appears.

    Hi? today i too have this problem.
    I found a solution here: https://discussions.apple.com/message/25137524#25137524
    Now all good.
    Good luck!

  • I try to drag certain loops but when i drop them in i get the error:   Result code = -5000     File = GarageBand-Temp-B262E454.tmp

    I try to drag certain loops but when i drop them in i get the error: 
         Result code = -5000   
         File = GarageBand-Temp-B262E454.tmp

    Hi,
       I've been trying to solve this problem for a school my companey has set up. After some research and looking at a number of similar posts I tracked the problem down to loops that came with jam packs or with apps like soundtrack pro. These loops are located in /Library/audio/appleloops. If you give everyone read and write access to this folder and it items the loops seem to work.
    I also noticed that once the loops were working agin GB had to convert the sample rate so it's possible that it's the sample rate on certain loops that causess the issue or prehaps the need to change the rate.
    Hope this helps.
    Matt Fleming
    (ACSA)

Maybe you are looking for