Garageband seeing 16 bit wav files as 8 bit.

I am using Garage band 11.  I have a session with speech and music.  I came back to edit it and it would not open saying the audio was 8 bit. It was not it was wav and 44.1/16 bit.  I opened the package contents and checked the wav files and they played fine.  So how and why did Garageband suddenly see then as 8 bit?
I lost my whole session.
And ideas

this is my username wrote:
It was not it was wav
aiff not wav
this is my username wrote:
So how and why did Garageband suddenly see then as 8 bit?
I lost my whole session.
i don't know the "why," but all is not lost yet.
create a new project and drop the audio file into the timeline of the new project. if it really is a 44.1k 16-bit aiff file, then it should import into the new project.

Similar Messages

  • HELP - 88.2 k 24-bit wav file is slowing down when imported to garageband

    i have an 88.2 k 24-bit wav file that is slowing down when imported to garageband. How do i get around this problem?

    You need to convert it to 44.1 16 bit. You can do that with iTunes.

  • Can't use my 32 bit wave files

    hej,
    I switched to Mac not long ago.
    I now have Logic express and it can't import the 32 bit wave files i recorded with my mackie onyx, back when i was working on PC with Samplitude.
    Is there an easy way to make it work fine, straight from Logic Express...? Or any other way using another programm ?
    Thanks helping...
    macbook pro   Mac OS X (10.4.9)  

    Hi, you should use a samplerateconverter to convert to 24 Bit.
    A nice free Batchconverter is AudioMove v1.14:
    http://www.lcscanada.com/audiomove/
    best wishes..
    Roland

  • Logic X won't import a 64 bit .wav file. Why?

    I'm trying to import .wav files created with FF Tools into Logic for some editing, but it says the audio file is "in a 64 bit format and cannot be used". Why is this? I thought Logic X was 64-bit friendly?
    Any help on this would be greatly appreciated.
    Thanks

    There is also no point in using 64 bit audio files. Even 32 bit floating point is already overkill. The best choice for recording is 24 bit, for internal processing 64 bit floating point does make sense, but not for storing.
    In any case, your mac comes with a very capable audio file format converting utility that can be used from the command line and reads/writes practically any audio file format you will encounter, including 64 bit wav. Type "afconvert" on your command line in terminal.app to see the options it offers. If you're not used to using the command line you might find this very uncomfortable, but it's really worth getting into it.
    Let me know if you need help,
    Jazz

  • I need a vi which converts a text message to mono 8 bit wave file

    i want to convert text message to 8 bit mono wave file
    i m using labview 8.2

    http://forums.ni.com/ni/board/message?board.id=170&thread.id=304917

  • 16 bit WAV file

    Hi everyone. Im trying to understand something about WAV files (or rather about how 16 bit audio works).
    a 16 bit sample has values from -32768 to 32767.
    If 0 is the zero crossing then what do you do with this asymmetry?
    There are 32767 "pos" values but 32768 "neg" values.
    Wouldnt it have been better for them to throw out that last 32768th value?
    Sorry if i have this all wrong. Im just imaging a waveform and wondering why the values above and below the zero crossing arent equal.

    no worries Jon I was dragging the destination into the window when there was no need cheers

  • Why won't Logic split imported 24 bit wav files?

    I've got "Force Interleaved files to split" checked but Logic won't do it with 24bit wav files,( it will with 16bit). Also, it won't let me use the crosssfade tool until I copy the file and change it to a split 24 bit file.
    I've got the driver set to SDII, 24bit, 44.1.
    What gives?

    ...anybody?
    This can't only be happening to me.

  • 64 bit setup file installs 32 bit itunes?

    I downloaded the itunes 64-bit setup file from the apple website for my windows 7 64-bit laptop. During the install I received a message telling me to download the 64 bit version of itunes because this was the 32-bit.
    I restarted my laptop and I uninstalled all apple software and tried again; the same occurred. Nothing I tried works. How do I get the correct setup file if that is what I did wrong? Otherwise, how do I set up the itunes without such controversies?

    If you're using a 32-bit browser you may be offered the 32-bit version of iTunes despite the fact that your machine is 64 bit. See the Further Information area of Troubleshooting issues with iTunes for Windows updates for download advice and direct links if required.
    tt2

  • Camera Raw only offers to open 16-bit raw files in 8-bit mode

    I am using a windows CS6 Bridge => Camera Raw (8.2) => CS6 Photoshop (13.0.1 x64) to try to open various 16-bit raw files (.dng, .nef, .arw) which Bridge sees as 16-bit, but only an 8-bit version makes it into photoshop.
    How do I convince Camera Raw to do its job?
    Lightroom (4.4) is able to export a 16-bit .psd which sort-of-works but shouldn't be necessary.
    Thanks in advance,
    Steve

    You set the bitdepth in your work options dialog box, which you access by clicking on the line that looks like a link right under the ACR preview:
    Don't be afraid to read the Help files or other documentation that came with Photoshop (otherwise known as Read The Fine Manual).

  • Is there a way to convert 24 bit tTIFF files to 8 bit JPEGS

    Many months ago I scanned several hundred slides into TIFF format. When I look at the details of the file, they have a bit depth of 24. Is there any way to use Elements 6 to save these files to JPEG format with only an 8 bit colour depth?

    24 bit is 8 bit. When a file says it is 24 bit they mean 8 bit x three color channels=24 bit. Most scanners say it that way. Adobe is more honest and just calls it 8 bit.

  • PS-CC 2014 (latest) - changing 32-bit depth file to 16-bit

    I opened a file, happened to be 32-bit depth (I don't have too many, not even sure how that one got to be 32-bit), and because a lot of filters don't work with that, I changed it to 16-bit, but when I did that, the HDR toning dialogue appeared, and I HAD to click OK on it to get the image to convert to 16-bit (CANCEL on the dialogue leaves it at 32-bit). So you have to choose a METHOD that you can set so there's no change to the image. Weird & wrong . . .

    Sorry, no solution to the problem, but a confirmation. I do have the same problem (Intuos Pro and Pen & Touch) showing the problem with ACR 8.5 and Photoshop (2014, CC and 6, these were updated with ACR 8.5) . No such problem before ACR 8.5 and no problem with LR 5.5 (also containing ACR 8.5).
    I hope there will be a solution from Adobe soon, since sems to be caused by the ACR update.
    Windows 8.1 in my case and latest Wacom Intuos driver installed.
    Thomas

  • 24-bit audio files converted to 16-bit in Logic Pro 7

    Hello,
    I'm working on producing my band's demo and this is my first project in Logic Pro 7. The tracks were originally recorded into a Fostex D2424LV hard disc recorder as 24-bit wave files, then imported into Logic. At this point, I've done the editing and effects processing in Logic and exported the tracks as individual wave files, with the intent to put the tracks back on the Fostex and run them through a Yamaha 24-channel analog board for the final mixdown.
    Everything has gone smooth until now. When I play the exported tracks back on the Fostex, most of them are peaking on the meters, while the same tracks played back in Logic don't even come close to peaking. I've tried re-exporting the tracks with reduced fader levels and still get peaks on the Fostex.
    Given that the reduced levels still cause tracks to peak on the Fostex, I'm suspecting a bit-depth issue. I didn't realize at the time that the files were converted to 16-bit when they were imported into Logic. The Fostex only works with 24-bit files and I'm wondering if exporting the 16-bit tracks in Logic as 24-bit wave files might be causing the problem.
    If this turns out to be the cause of the peaking tracks, is it possible to re-import or replace the converted 16-bit files with the original 24-bit files and apply the editing and efx processing that I've done to the 24-bit files?
    I'll greatly appreciate any help you folks can give me on this one.
    Kevin
    Dual 2.0 Ghz G5 Powermac   Mac OS X (10.4.1)   RME Multiface
    Dual 2.0 Ghz G5 Powermac   Mac OS X (10.4.1)   RME Multiface

    i am very surprised that the fostex doesn't work with 24-bit files.
    your peaking is not likely to be due to bit depth, although i can see why you might think so. maybe you're right.
    logic has inbuilt -6db of head room you should know.
    your suggestion of reimporting the original tracks from the fostex is exactly the thing you should do. remove the 16-bit files from the system and re-import the fostex files. open the logic project and it will look for the old files. for greatest ease make sure your fostex imported files have the same names as the ones you are removing. when it finds the files with the same name it should come up with an error message. select use anyway.
    what's happening is logic stores information about the file, its length, bit-depth and so forth. so just get logic to use anyway and the files "should" playback alright.

  • 12- and 14-bit Raw file conversion to 16-bit tiff

    Does anyone know how Camera Raw converts the 10, 12, or 14 bit RAW file data(14-bit D3 .NEF here) into the 16-bit tiff files it can produce. I assume it either manages to leave empty space in the file, or interpolates by some means. If interpolation is the answer, is it by a method analogous to one of the spatial resizing methods(nearest neighbor or bilinear)?

    Keep in mind that a 16bit image format (eg, TIF) is actually a container, and I've seen many variations on putting lesser bit depths in the format. EG, 10bits may only be stored in the first 1024 bins, or the same 10bit data may instead be stored in every 6th bin - the latter of which is the most common and best way. When I look at the 16bit histogram after ACR has converted 12bit RAW to 16bit TIF, it is as if 12bits has been converted to 16bits (actually 15bits), because every bin appears to have data in it.
    As to how it's actually done, it may be proprietary ... but someone else may be able to draw conclusions from the open algorithms that are available (eg, dcraw).

  • HI, I am having trouble when importing .wav files into logic.

    Everytime I import this .wav file of a DJ set i recorded, it shows me the waveform but no sound comes out when its played. I have tried converting the bitrate to 16bit and the filetype to aiff as I saw it had helped people with similar problems but when i do this its boosts the gain massivly and the recrding becomes very distored? Really dont know what to try??
    Also the reason I am trying to get the Wav in was bevause i need to normalise it as it had to be recorded very quitely to avoid distortion on the recording. I recorded it by using the imput on the back of my monitors as they are usb, and th programme i used to record it is "audio recorder tool" from the app store
    Thanks for your help, Joe

    I think the problem is you're recorded 32-bit wav files which Logic doesn't support.
    (don't convert to aiff, unless you have the right program, that understands converting little endian 32 bit wavs to big endian aiff format, you will get distortion)
    I think your best bet is to download "Audacity" the free audio editor and convert to 24-bit WAV files. Re-save the audio file under a different name after converting. In Audacity this is done using the Export function, selecting other non-compressed formats.
    http://audacity.sourceforge.net/download/mac
    The reason you want 24-bit WAVs to work with is you're going to be raising the volume of the file, 24-bit files will suffer less damage when editing with plugins, normalizing...etc.

  • How to return Firefox to playing .wav files without the vlc plug-in?

    Win XP, Firefox 33.11. In an html document are links to PCM, 16 bit .wav files and
    other links to .mp3 files. Opening the document with Firefox and clicking on an .mp3 link
    plays in the `native' Firefox player OK. However clicking on a .wav link seemed to fail to
    play. Using Tool/Options/Applications, wav files were associated with VLC. Now clicking
    on a .wav link plays OK in a Firefox screen displaying the vlc logo.
    However, later the following was found this under the Firefox help information
    "Firefox can play the WAV container format (.wav, .wave file types) containing uncompressed
    audio in PCM at 8 or 16 bits per sample".
    It seems the .wav files should play with the `native' Firefox player.
    How can the link to vlc be removed. Removing the plug-in is not a solution as it is used
    for many other file types.

    Firefox will only use the HTML5 media player when the AUDIO tag is used.
    If EMBED or OBJECT is used then Firefox will always use a plugin.
    *http://developer.mozilla.org/Apps/Build/Audio_and_video_delivery

Maybe you are looking for