Paul881
Look Mom, I can play!
I am now dead 
fraserhutch
Flypaper for freaks
Paul881 said:I am now dead
Paul is dead - Paul is dead!
Actually my bad, you weren't the original poster, just someone who was trying to make a funny.
Didn't work.
Nate74
HR4FREBR
Well I'm not dead... yet, so I'll take any input I can get!
The FST software used to transfer data from the HD24's hard drive to my PC is really not that deep. I do have an option between 16-bit and 24-bit, but beyond that, I just get what I get off of it.
I've scowered the Alesis site and have found nothing about Bit Rate.
I have to ask: when everybody else looks at the Summary tab under the Properties of a wav file on their PCs, don't you see a value for Bit Rate?
I just can't believe I'm the only person in the world who has recorded at 96/24 on an HD24 and then tried to import files into CW...
The FST software used to transfer data from the HD24's hard drive to my PC is really not that deep. I do have an option between 16-bit and 24-bit, but beyond that, I just get what I get off of it.
I've scowered the Alesis site and have found nothing about Bit Rate.
I have to ask: when everybody else looks at the Summary tab under the Properties of a wav file on their PCs, don't you see a value for Bit Rate?
I just can't believe I'm the only person in the world who has recorded at 96/24 on an HD24 and then tried to import files into CW...
fraserhutch
Flypaper for freaks
Aha! I think I *may* know what your problem is.
I just looked up some wavs created by my audio app. The bit rate is there, but it is exactly as I mentioned it wold be above: depth * sample rate. In my case, they are both 24-bit, 48, which gives a bit rateof 1152k.
Another wav I have is 24 bit, 48k, and has a bit rate of 2304k. Why? It's a stereo track.
This simple formula hols true for all wavs on my box.
In your first post, the first track is mono @ 24*96k = 2304k.
I don't know what the hell your second track is. 6144k / 24 bit = 256, which is suggestive, but I don't know of what yet. It's an absurd sample rate. It's as if there were a BUNCH of tracks munged into that wav.
How large is that track? Could you post a link to it?
I just looked up some wavs created by my audio app. The bit rate is there, but it is exactly as I mentioned it wold be above: depth * sample rate. In my case, they are both 24-bit, 48, which gives a bit rateof 1152k.
Another wav I have is 24 bit, 48k, and has a bit rate of 2304k. Why? It's a stereo track.
This simple formula hols true for all wavs on my box.
In your first post, the first track is mono @ 24*96k = 2304k.
I don't know what the hell your second track is. 6144k / 24 bit = 256, which is suggestive, but I don't know of what yet. It's an absurd sample rate. It's as if there were a BUNCH of tracks munged into that wav.
How large is that track? Could you post a link to it?
minofifa
New member
do they or don't they.....
Nate74
HR4FREBR
Huh, we may be getting somewhere... maybe...
The total track size is 78,385kb, which is within a few hundred kb of the other existing tracks that have the 2304kbps Bit Rate. I think the extra recorded length could easily account for the slightly larger size (the originals are all 77,880kb).
I'm wondering if the way the HD24XR records at 96kHz (by using two of it's tracks at 48 to make one final at 96) has something to do with it...? But if your logic were to hold, they would be 4608kbps rather than 6144kbps...
Also, when I convert the files down to 24/48 and then back to 24/96 and their kbps goes down to 2304, their overall size stays the same (78,385k)
As for a link, I think it's way to big to upload to anything I have access to.
The total track size is 78,385kb, which is within a few hundred kb of the other existing tracks that have the 2304kbps Bit Rate. I think the extra recorded length could easily account for the slightly larger size (the originals are all 77,880kb).
I'm wondering if the way the HD24XR records at 96kHz (by using two of it's tracks at 48 to make one final at 96) has something to do with it...? But if your logic were to hold, they would be 4608kbps rather than 6144kbps...
Also, when I convert the files down to 24/48 and then back to 24/96 and their kbps goes down to 2304, their overall size stays the same (78,385k)
As for a link, I think it's way to big to upload to anything I have access to.
fraserhutch
Flypaper for freaks
minofifa said:
Well, I suspect that the property shows up in a windows file properties viewer because variable rate encoded files have the property. I have never really heard of it expressed as a "bit rate" before for wav files. To me, it is really meaningless in the context of a wav file.
I could be mistaken. One gets in a certain mindset.........
Nate74
HR4FREBR
I just got a speedy reply from the folks at Alesis. First thing I'm gonna do is make sure that my FST Connect software is the latest and greatest version.
He also suggested that indeed it is a limitation of Cakewalk and that I contact them as well, which I have done.
fraserhutch; I too would have thought a Bit Rate would be meaningless for a wav file, but I can't see any other properties that differ between the wavs I can import and the wavs I can't import...
I'll keep everyone posted, but man I'm sure open to any other thoughts too!
He also suggested that indeed it is a limitation of Cakewalk and that I contact them as well, which I have done.
fraserhutch; I too would have thought a Bit Rate would be meaningless for a wav file, but I can't see any other properties that differ between the wavs I can import and the wavs I can't import...
I'll keep everyone posted, but man I'm sure open to any other thoughts too!
Nate74
HR4FREBR
YIPPEEE!!!!
I double checked and I was running FST1.03 (the application that takes files from the the HD24XR to my PC). The new version 1.04 had this to say:
"Bug fixes:
1. When exporting WAV format files, the nAveBytesPerSec is incorrect calculated. It causes some applications cannot read the file properly. "
Sure enough, the new version brings the 96/24 wavs over at 2304 and they go into CW no problem!!!
I'm so stoked!
BTW, here are the updates
http://www.alesis.com/index.php?id=58,32,0,0,1,0
I double checked and I was running FST1.03 (the application that takes files from the the HD24XR to my PC). The new version 1.04 had this to say:
"Bug fixes:
1. When exporting WAV format files, the nAveBytesPerSec is incorrect calculated. It causes some applications cannot read the file properly. "
Sure enough, the new version brings the 96/24 wavs over at 2304 and they go into CW no problem!!!
I'm so stoked!
BTW, here are the updates
http://www.alesis.com/index.php?id=58,32,0,0,1,0
minofifa
New member
good to see you got your setup working... its always a good feeling.
i alos love how alesis was quick to point out that it is most likely cakewalk's fault.... i guess they gotta cover all bases.
i alos love how alesis was quick to point out that it is most likely cakewalk's fault.... i guess they gotta cover all bases.
Nate74
HR4FREBR
minofifa said:
I had the same thought...
