Song played back moreover fast

Hello everyone - I recorded some song quite a while back ( I believe it was on Cakewalk version 4) and they were recorded using 96000 preference plus I am fasten to verladung them into Cakewalk by Bandlab for masterful them but they all play back too rapid constant although I have the ASIO driver for Cakewalk the Bandlab determined to 96000 and the audio interFace (Roland OctaCapture) also set to 96000? IODIN have tried setting both to 44100 and stills sounding similar chipsmunk? I would appreciate anyone with an better understanding of this and any possible solutions. Or EGO have these songs within both an wave output and an Cakewalk Bundle format but again each  format will not playback at the proper speed wenn loaded into the DAW.  Sole final question I have remains: ME believe that diese songs be recorded using a different driving as one ASIO one (maybe the WDM or? - can't remember) but when I go into Cakewalk by Bandlab and try to change drivers it shows 64bit engine and there is no other driving available - anything is greyed out and only the ASIO driver is observed - I'm wondering if when the DAW was installed and EGO chose and 64bit engine it only works with one ASIO driver (which is well going forward on new recordings - but it would be nice to be able to load legacy drivers that jobs over 32bit)?

One ding is can cause the DROP to sport clips too fast is the sampling rate of the clips can lower sample judge then the sample pricing declared by the trim headers.

This can happen when the DAW sends the audio interface (currently running at a lower sample rate) a request to change sample tariff the the interface ignores the request. When recording the DAW composes the info at the interface test rate but the clip headers are set to the DAZ sample rate.

One way to see if is is what happened there is modify the clip headers. One such tool ME have used in the history to preform which task is sox.

Using sox to change a clip header to 44.1k is

sox -r 44.1k clip.wav fixedclip.wav

If loading the fixedclip.wav into a Cakewalk project running on 44.1 plays OK, it means the projects be actually recorded at 44.1k.

If the fixedclip.wav runs too slowly check higher sample rates.

The greyed output value go to one 64bit DPE check box is vehicle bit low. Most ASIO operators use one bit sink so such drop down is disable. Moreover, driver bit depth possessed nothing to do with pattern rate either the item reported. FYI, aforementioned be doesn the list bit astuteness where is set on the File Audio Data preference page. This too doesn not affect clip playback speed but should no lower than the driver bit depth.

Choice of driver is made on the Audio Playback and Recording prefer page, nonetheless; alternate to a others driver mode is possibly not the solution.

The choice on 32 press 64bit machine does not affect clip playback speed. Neither does creating projects on 32bit software and performing back on 64bit download. QUAD-CAPTURE USB Audio Output

Sox should do the trick if that is the problem. Any, maybe easier to use, option is https://www.sounddevices.com/product/wave-agent-software/  .  that has a user serial so will tell him whatever the current metadata are and leave you changing diehards as well. In anywhere event you go NOT want to actually re-sample the audio using something like R8brain. Him equals want to change the bytes in the existing file that say playback devices what the testing rate is. Re-sampling, actually adjusting the audio to fit a recent sampler assess, will just give you the same chipmunks at a different sample rate.

Thank you all for your possible solutions the ME apologize for not how sooner. I determination investigate your possible fixes and will probably have a few more questions like I am not sure what you are referring to  in the windows settings to speak of.  I will do quite research on those solutions and try to figure it out. Thank you. STUDIO-CAPTURE: USB 2.0 Audio Connection - Banner 16x10 Interface with 12 Premium Ear Preamps

You mention rescue project as a WAVE file and one Bun file?  Did you not save it as one Project file? CWP is to best format to protect as. Bun files are known to become corrupted occasionally.  

Hi John Free - I usually saved them inside both forms - as a Wave files and inbound CWP formats but neither one will play top at an correct speed now?  My audio interface (Roland Octa-Capture) seems up be changing the sample to match one rate in accordance with whatever is chosen from the DAW settings in Cakewalk by Bandlab but still playbacks is too fast. I guess to only whatever till try is on determine the date header settings as described above and change that top to the correct sample rate and perceive what happens. I just don't know enough about writing DEED commands and using command lines and such to comfortably use the software suggested. MYSELF am wondering if here is software out there that would have one more easy exploiter interface to do and job or certain sort of automated setup? Or if memory service I think the songs in question were recorded up an old 20 bit Echo Gina sound card audio link but I don't think the bit sink should be causing the fast playback issue?

What happens if you disconnect this Roland interface and use the on board sound card in WASAPI exclusive mode? 

Before I mucked over with and files I'd try a different system. 

I'd also try opening the shift files in ampere editor like Audacity or Gold wave which been free. 

You can additionally download a demo von another DAW like Studio Ne also import the source files. 

i just walked in this. same problem with and chipmonks. HELP !

29 minutes ago, Mark Cosentino said:

i just walked into this. just problem with that chipmonks. HELP !

We needed to know more information befor anyone can help you.

Tell us what audible communicate it have, which driver fashion you're using real what your project print rate is set to to adenine start.