Taperssection.com
Gear / Technical Help => Recording Gear => Topic started by: Myco on December 06, 2006, 08:41:22 PM
-
So I recorded a show at 24/96 and I can play it fine on my HD-P2, but it was recorded as four different "takes" in actuality. When I go to transfer it to my pc all I get is the first file "take00". I can't access the other 3 "takes" that make up the rest of the show from my pc. Actually none of the "takes" are listed in the conform box, just the entire project folder. Can anyone tell me how to transfer this all as one complete file? I've heard that others have had this problem also, but I haven't found a remedy for it yet. thanks
-
hmmm.
i always just copy the folder to a harddrive... cant you just copy the audio files directory from your hardrive..? if you can, are the other WAV files readable individually in a wav editor or player (like foobar)..?
as for conform, i have never used it... i use samplitude, and join them from there...
-
hmmm.
i always just copy the folder to a harddrive... cant you just copy the audio files directory from your hardrive..? if you can, are the other WAV files readable individually in a wav editor or player (like foobar)..?
as for conform, i have never used it... i use samplitude, and join them from there...
Thanks macdaddy, I just copied them like you've mentioned. I don't have samplitude so I guess I'll use wavmerge to join them. The conform program didn't produce a readily readable file anyway. +T
-
Tascam provides an application for the P2 called "Conform" which I run on Windows.
It can be obtained from the Tascam web site. Conform concatenates the "takes" into a single wav file on transfer.
I use it every time to transfer.
Once the P2 is connected via Firewire, open the Conform app and select the project, then whether you want it as 24 bit of 16 bit...
/Ken
-
Addawav is a great freeware program. Mends wav files seamlessly, with no pops. Really easy to use and doesn't hog the CPU. I mended two 24/48 files with no problems.
-
goldwaves file merger tool works great as well although now i will try that conform soft and see how i like it
-
Tascam provides an application for the P2 called "Conform" which I run on Windows.
It can be obtained from the Tascam web site. Conform concatenates the "takes" into a single wav file on transfer.
I use it every time to transfer.
Once the P2 is connected via Firewire, open the Conform app and select the project, then whether you want it as 24 bit of 16 bit...
/Ken
This is what I tried to do Ken. I installed the Conform program from the included cd-rom, but when I go to conform the project, it only recognizes the first take in the folder and ignores the other three. The program doesn't give me an option to choose all of the files, so I choose the project folder and only the first take in the folder gets conformed. Any ideas? Thanks :)
-
Tascam provides an application for the P2 called "Conform" which I run on Windows.
It can be obtained from the Tascam web site. Conform concatenates the "takes" into a single wav file on transfer.
I use it every time to transfer.
Once the P2 is connected via Firewire, open the Conform app and select the project, then whether you want it as 24 bit of 16 bit...
/Ken
This is what I tried to do Ken. I installed the Conform program from the included cd-rom, but when I go to conform the project, it only recognizes the first take in the folder and ignores the other three. The program doesn't give me an option to choose all of the files, so I choose the project folder and only the first take in the folder gets conformed. Any ideas? Thanks :)
let me guess, did you run at 24/96 with auto split at 1.5gb? that is probably the problem as WAV files can only be 2gb, so when it tries to deal with take01, it reaches maximum size right away. i'm not sure why anyone would use the conform with 24/96, as it is not possible to work with files +2gb (in wavelab) i think i'm pretty sure linux can handle larger WAV file sizes, but that's it.
-
Tascam provides an application for the P2 called "Conform" which I run on Windows.
It can be obtained from the Tascam web site. Conform concatenates the "takes" into a single wav file on transfer.
I use it every time to transfer.
Once the P2 is connected via Firewire, open the Conform app and select the project, then whether you want it as 24 bit of 16 bit...
/Ken
This is what I tried to do Ken. I installed the Conform program from the included cd-rom, but when I go to conform the project, it only recognizes the first take in the folder and ignores the other three. The program doesn't give me an option to choose all of the files, so I choose the project folder and only the first take in the folder gets conformed. Any ideas? Thanks :)
let me guess, did you run at 24/96 with auto split at 1.5gb? that is probably the problem as WAV files can only be 2gb, so when it tries to deal with take01, it reaches maximum size right away. i'm not sure why anyone would use the conform with 24/96, as it is not possible to work with files +2gb (in wavelab) i think i'm pretty sure linux can handle larger WAV file sizes, but that's it.
I think you hit it on the head. I thought that maybe this might be the problem, but I wasn't sure. I changed the system settings for 2gb files, but it didnt take because it broke at 1.5 anyway. Thanks alot for your input, I'm not going to use the conform program any longer, I'll just copy them to my hard drive and go from there.
-
Hmmm, never had a problem w/ Conform, nor files > 2Gb. I use Audacity and CD Wave to master, neither of which has any issues w/ large files. Both are also freeware.
I've only recorded w/ the P2 at 24/48, so far. I've also installed the latest firmware and latest upgrade for Conform from the website.
/Ken
-
Hmmm, never had a problem w/ Conform, nor files > 2Gb. I use Audacity and CD Wave to master, neither of which has any issues w/ large files. Both are also freeware.
I've only recorded w/ the P2 at 24/48, so far. I've also installed the latest firmware and latest upgrade for Conform from the website.
/Ken
Yeah, I have the latest firmware and the upgrade for Conform also, the only diff is my files are 24/96.
-
I have a different problem when I transfer. It doesn't affect anything, but it is kind of annoying. EVERY time I transfer from my card reader I get a message from cdwave saying that the file size is different than what the header reports. It stays the same size whether I choose the option to keep the header information or resize the file. I am unmounting the card with the P2 software as prescribed. Any thoughts?
-
I have a different problem when I transfer. It doesn't affect anything, but it is kind of annoying. EVERY time I transfer from my card reader I get a message from cdwave saying that the file size is different than what the header reports. It stays the same size whether I choose the option to keep the header information or resize the file. I am unmounting the card with the P2 software as prescribed. Any thoughts?
every file from the HD-P2 will say this in CD Wave. basically, it's because there is some junk in the header. it's not a big deal and I wouldn't worry about it. also, the HD-P2 is not the only recorder that does this, I know that all files recorded on the MicroTrack also have extra stuff in the header, and I think some other recorders as well.
-
I have a different problem when I transfer. It doesn't affect anything, but it is kind of annoying. EVERY time I transfer from my card reader I get a message from cdwave saying that the file size is different than what the header reports. It stays the same size whether I choose the option to keep the header information or resize the file. I am unmounting the card with the P2 software as prescribed. Any thoughts?
every file from the HD-P2 will say this in CD Wave. basically, it's because there is some junk in the header. it's not a big deal and I wouldn't worry about it. also, the HD-P2 is not the only recorder that does this, I know that all files recorded on the MicroTrack also have extra stuff in the header, and I think some other recorders as well.
I don't get that message as I usually work in SoundForge, but what it is are the files that would house "markers" and (project) "settings" information. When I do a "save as" if I edit and want to keep my original .wav file, I am prompted as to whether I want to save that information. I always say no, although I always think that maybe someday I'll try to put a marker after each song and see if it will make the cutting up of the tracks a no brainer. Then again someday never seems to come... ;)
If you open the project up in windows, you will see the extra "stuff" accompanying the wave file.
I am surprised about the MicroTrack comment, I have an MT too, but I have not ever had any extra data or anything, just the wave file, same size, no extra information. It may just be something resulting in whatever process is being used in the post process.
-
If you open the project up in windows, you will see the extra "stuff" accompanying the wave file.
we're just talking about the WAV files. not the extra files that have the project settings info. the actual WAV files have non-standard headers. some programs open them up with no warnings. SoundForge, as you note, is one of them. WaveLab also opens up the files with no message or warning. CD Wave, however, does give a little pop-up saying that the expected file size differes from the actual file size. and that's because of the non-standard header. even so, all the files open up just fine in CD Wave.
I am surprised about the MicroTrack comment, I have an MT too, but I have not ever had any extra data or anything, just the wave file, same size, no extra information. It may just be something resulting in whatever process is being used in the post process.
as far as the MircoTrack files doing the same thing, I owned a MT from Sept '05 through April '06. every single file recorded on the MicroTrack that I opened with CD Wave gave me that message. maybe in the most recent firmware, the MT writes a standard header, thus no message. I no longer own a MicroTrack, so I can't really comment on that. but, like I mentioned, if you are just opening up in SoundForge, than no, you won't see any message about the header when you open up the files.
-
for the record, samplitude v8.1 adds chunks in the headers...
you guys do know that command/ shntool strip *.wav gets rid of all of that, right..? (hopefully the srip comand will show up in xact for windows ('cos that is a terrific shntool frontend, and all in one proggie)...
the ability to strip the wav files of this extra junk is essential to me, 'cos the program (samp v8.1) i use adds this stuff; aside from editing, i can track and split on sector boundaries, but each of the tracks comes out with shntool len WAV output of --e which means there is [e]xtra data in the header. this is also why the original md5s dont match anymore - the shntool md5s are the same, so no wav data is being changed, but samplitude puts its own info in the header, which affects the md5 signature of the files. i assume this is what these other programs, and devices, are doing, too...