[ddots-l] Re: Problem With Exported Audio

  • From: "Mike Christer" <christer.christer@xxxxxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Wed, 11 May 2011 20:36:34 +0100

So, why don't you let one of us check it out?  

l8r


  ----- Original Message ----- 
  From: Annabelle Susan Morison 
  To: ddots-l@xxxxxxxxxxxxx 
  Sent: Wednesday, May 11, 2011 8:27 PM
  Subject: [ddots-l] Re: Problem With Exported Audio


  I've done everything I could think of.



------------------------------------------------------------------------------
  From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Shawn Brock
  Sent: Wednesday, May 11, 2011 12:25 PM
  To: ddots-l@xxxxxxxxxxxxx
  Subject: [ddots-l] Re: Problem With Exported Audio


  Hi Annabelle, 

  Perhaps I have missed part of the thread here. 

  When exporting obviously Wav is the default, and as you tab down you will see 
a combo box where you can choose the bit depth and sample rate.  With the bit 
depth set to 16 and the sample rate set to 44.1, you shouldn't have any trouble 
playing the file in any program. 

  This is probably stuff you already knew.  And having said all of that, this 
is not the first time I have heard of this problem. 

  As a matter of fact I had this problem yesterday.  I was doing liners for a 
radio station in Florida called "Smooth 100.9".  Each time I would export the 
recorded liner, I named them "Smooth 100.9 liner 1, Smooth 100.9 liner 2, and 
so on.  When I tried playing the files, I got a message from Windows asking 
what program I wanted to open them with.  I got really freaked out, and began 
to export all files again.  After my 2nd export they still wouldn't play.  At 
this point I decided to change the name of the file.  

  The long short was, that for some reason the "100.9" in the title of each 
file screwed something up.  I don't know why, but with taking the numbers and 
the period out of the title, the files worked fine. 

  I never have experienced anything so strange before, but that was the 
problem. 

  I would recommend that you try a new title and see if that makes a 
difference.  Just call it "song 1" or something and see if you have better 
luck. 

  Best,
  Shawn Brock
    ----- Original Message ----- 
    From: Annabelle Susan Morison 
    To: ddots-l@xxxxxxxxxxxxx 
    Sent: Wednesday, May 11, 2011 6:41 AM
    Subject: [ddots-l] Re: Problem With Exported Audio


    It won't even play in ITunes, or Goldwave, or Audacity. And no, I don't 
have Sound Forge.



----------------------------------------------------------------------------
    From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Mike Christer
    Sent: Wednesday, May 11, 2011 12:50 AM
    To: ddots-l@xxxxxxxxxxxxx
    Subject: [ddots-l] Re: Problem With Exported Audio


    Have you got SoundForge?

    l8r


      ----- Original Message ----- 
      From: Annabelle Susan Morison 
      To: ddots-l@xxxxxxxxxxxxx 
      Sent: Wednesday, May 11, 2011 7:52 AM
      Subject: [ddots-l] Problem With Exported Audio


      Hi, it's Annabelle.
      I've tried exporting a project's Audio as a .wav file, but for some 
reason, I've recently run into a situation where when I go to play it in my 
music player, I get an error message saying:
      Windows Media Player cannot play the file. Windows Media Player may not 
support the codec that was used to compress the file." It seems a bit strange, 
because I've exported other projects as Audio .wav files, and they seem to play 
just fine. I've tried exporting it as a Broadcast Wave, but that didn't work. 
I've tried numerous times to export the audio, with all the tracks selected, 
but that didn't work. I've tried recreating the project, but that didn't work. 
And all those attempts, when I go to test the file in Windows Media Player, I 
get the same error each time! What do I do next?

--------------------------------------------------------------------------

      No virus found in this message.
      Checked by AVG - www.avg.com
      Version: 10.0.1325 / Virus Database: 1500/3629 - Release Date: 05/10/11

Other related posts: