Ok so I recorded a whole session on PT 8 at 48 khz as opposed to 44.1. I have tried creating a new session and importing tracks to no success. When I recorded the clock source was my Digimax FS, so Pro Tools thinks it is a 44.1 session when it's actually a 48 khz session. Sucks that the sample rate button is right next to the power button, must have pushed it when I was turning the Pre-Amp on or off... Any suggestions?
Comments
A thought occurred to me while I was cursing gateways and access
A thought occurred to me while I was cursing gateways and access points today. Do you have massive digital artifacts on your recording? You should if the sampling rates were truly mismatched. If that is the case then nothing you can do is going to fix it. On the other hand. Maybe PT automatically recorded it at 44.1 when you switched the interface asio driver.
AscensionStudios wrote: It sounds fine in Pro Tools but if I pu
AscensionStudios wrote: It sounds fine in Pro Tools but if I put it on iTunes or something it's just slowed down. :(
Are you using the same audio driver you use in PT to listen to your samples in iTunes?
maybe you need to switch your audio driver from 48 back to 44.1
it starts and ends with that external clock " Sucks that the sam
it starts and ends with that external clock
" Sucks that the sample rate button is right next to the power button, "
so the track can only sound right when the
" Pro Tools thinks it is a 44.1 session when it's actually a 48 khz session. "
the Digimax FS is providing the clock at 48 while the PT session is listed at 44.1
yes it will sound fine while the situation above remains in tact
but if you try to put it to Itunes or an AudioCD or another system without the clock source error ...etc
you will have the problem
as was said above
HACK the header
OR
while the system is in the above mode
do an ANALOG bounce to a system with the correct settings
I used XVI32... worked well enough. The 2 columns of code are t
I used XVI32... worked well enough.
The 2 columns of code are the same contents, I found it easier to work with the hex display though (the left side).
Edit: ARGH, the site with the header details that I worked from last time, appears to be down. I didn't copy any details either, nuts.
Hopefully I can find it again.
Edit 2: found the list I need.
Also I found this program you might want to try, but you can still copy the header here, or PM it or something.
[[url=http://[/URL]="http://www.railjonr…"]WAV Header Investigator[/]="http://www.railjonr…"]WAV Header Investigator[/]
This is a link to a screenshot of the screwed up file.. (couldn'
This is a link to a screenshot of the screwed up file.. (couldn't copy and paste..)
http://img338.imageshack.us/i/screenshot1amt.png/
This is a link to a good file...
http://img44.imageshack.us/i/screenshot2afs.png/
I really appreciate your help, I've been trying to fix this for weeks. :(
Header Inverstigator did the trick!!! I looked for days for a pr
Header Inverstigator did the trick!!! I looked for days for a program to just edit the header and not the audio because I figured it would be waaaaaaay easier! Just switched the sample rate to 48000. Where the heck did you find that? I searched every possible keyword.. Well I guess not but yeah, THANKS A TON! Life saver.
This problem seems...no turning back... most expecially when you
This problem seems...no turning back... most expecially when you can't call the artist for vocal recording once again. Some audio engineers get that mistake too! and some ends up re-doing again the takes and re-record once again.
One of possible solution for this is to re-route audio manualy to your tie lines in studio. It will be good for you if you have to computers with DAW with the proper audio interface. Copying everything in real time. This is only recommended when the audio is not very obvious that it was adjusted.
I tried this once. the producer did not noticed. You can try your luck.
but some ends up " it a must to re-take" Good luck!
Hope this one helps!
Edit the header of the file. Codemonkey was doing something lik
Edit the header of the file. Codemonkey was doing something like this several weeks ago.