recording 2GB+ wav's in traction (title edited)
-
- KVRist
- Topic Starter
- 35 posts since 19 Mar, 2005
wow... active forum! Thanks for the input guys. Going backwards here... yes I know I have a ~$2500 rig and not a $65000 rig. I still want it to work. That is still a lot of money to me.
I have a 65GB 7500/8mb internal drive on the lappy, and same results with that... that and a 1GB ram stick were the upgrades I did to the lappy. The cpu meter on the traction program doesn't even register 1 bar for cpu useage... I have ben using the highest latency setting.
By allowing traction to not stop when the program minimizes (options setting) I can look at the folder on the drive where I am writing. All tracks show up. Hit stop and they dissappear. This is a REALLY wierd bug. I tried the adobe freebie thingking it would get me through for a month, but I couldn't get it to recognise the aiso driver.
The auto save saves the edit settings (I believe, and not the wav itself)
You are close with the phish anology... I tape primarily jambands (never was a big phish phan though), and while many break sets up into 1-2 hrs, many also do a single set for over 2. Sure there is a break but not long enough to let traction run nits' paces and do a reboot. The recordings I make are meant to be "archival" stye recordings and with rare exceptions, the chatter and tunning etc. are a part of this.
I defrag religoulsy, and one my final tweaks was to create 3 partitions on my 200 GB external so I didn't have to defrag between sets/bands. Each partition is also as a ntfs so file sizes over 4GB will not be a problem.
Thanks again, keep the suggestions comming
Matt
I have a 65GB 7500/8mb internal drive on the lappy, and same results with that... that and a 1GB ram stick were the upgrades I did to the lappy. The cpu meter on the traction program doesn't even register 1 bar for cpu useage... I have ben using the highest latency setting.
By allowing traction to not stop when the program minimizes (options setting) I can look at the folder on the drive where I am writing. All tracks show up. Hit stop and they dissappear. This is a REALLY wierd bug. I tried the adobe freebie thingking it would get me through for a month, but I couldn't get it to recognise the aiso driver.
The auto save saves the edit settings (I believe, and not the wav itself)
You are close with the phish anology... I tape primarily jambands (never was a big phish phan though), and while many break sets up into 1-2 hrs, many also do a single set for over 2. Sure there is a break but not long enough to let traction run nits' paces and do a reboot. The recordings I make are meant to be "archival" stye recordings and with rare exceptions, the chatter and tunning etc. are a part of this.
I defrag religoulsy, and one my final tweaks was to create 3 partitions on my 200 GB external so I didn't have to defrag between sets/bands. Each partition is also as a ntfs so file sizes over 4GB will not be a problem.
Thanks again, keep the suggestions comming
Matt
Last edited by mmmatt on Sat Mar 19, 2005 9:31 pm, edited 1 time in total.
-
- KVRian
- 1112 posts since 17 Jul, 2003 from Kauai, HI
Hi chico--
You took my meaning perfectly. If my four-hour project went belly up at two hours, I'd feel a lot better if I had two hours rather than none. I'm sure mmmatt would be able to spot a giant file there somewhere, but if it can't be opened at all, then what's the use of autosave?
It's a very strange bug all right.
Tom
You took my meaning perfectly. If my four-hour project went belly up at two hours, I'd feel a lot better if I had two hours rather than none. I'm sure mmmatt would be able to spot a giant file there somewhere, but if it can't be opened at all, then what's the use of autosave?
It's a very strange bug all right.
Tom
-
- KVRian
- 1112 posts since 17 Jul, 2003 from Kauai, HI
Hi Matt--
Sounds like you've found a good one there! I think we'd be glad to hear about any ongoing talks you have with customer service. Best of luck with the problem and especially with your new business! Where you from?
Tom
Sounds like you've found a good one there! I think we'd be glad to hear about any ongoing talks you have with customer service. Best of luck with the problem and especially with your new business! Where you from?
Tom
-
- KVRAF
- 2009 posts since 9 Apr, 2003 from Cornwall, UK
blimey! Can't believe this one slipped through the net!
I would be sooooo greatful if this is fixed, it has only been be shear chance that I've not had a session go over an hour in a single take.
Well spotted Matt, but keep us informed what Mackie say as I'd be greatful of any updates. Also Tracktion is a great product that totally deserves to be taken seriously as a professional recording tool.
Have you heard about this Beno?
I would be sooooo greatful if this is fixed, it has only been be shear chance that I've not had a session go over an hour in a single take.
Well spotted Matt, but keep us informed what Mackie say as I'd be greatful of any updates. Also Tracktion is a great product that totally deserves to be taken seriously as a professional recording tool.
Have you heard about this Beno?
- KVRAF
- 25036 posts since 12 Jul, 2003 from West Caprazumia
kiddin'?Traction2 wrote:
I have a Stephens Analog 40 track recorder in perfect condition, less than 15 hours record and playback time for $65,000. if you are interested.
- KVRAF
- 25036 posts since 12 Jul, 2003 from West Caprazumia
correct - but afaik wavs don't need to be finalised - so they should be there in any case...chico.co.uk wrote:Surely it must save the actual wav files? If you look in the directory where you were trying to save the project, are they there?
It's obviously not possible for your pc to store over an hour's worth of even a single wav file in memory, so tracktion must stream them to disk, no? So presumably the files are actually there, even if they're not showing in the tracktion project?
unless T doesn't finalise the wavs properly for some reason, if they're over 1 hour long, and under 4 hours long (sounds a bit of a weird bug ...)
-
- KVRist
- 88 posts since 10 Aug, 2003 from New Zealand
Hi Matt
I have done a few sessions of live recordings including one about a year ago of up to 12 tracks and some 4 hours in total. What I did was to stop the recording after each number and recommence recording almost immediately on the same edit. It really only took Tracktion a second or so to be prepared for recording again. Mind you these numbers were probably only 10 minutes long for each and it is possible that the longer the track the longer Tracktion (or your hardware) needs to be ready for recording again.
The other good thing was that all the recordings were named differently in the file structure so were easily imported into individual edits later on for mixing.
Cheers
Graham
www.lakesiderecordingstudio.co.nz
I have done a few sessions of live recordings including one about a year ago of up to 12 tracks and some 4 hours in total. What I did was to stop the recording after each number and recommence recording almost immediately on the same edit. It really only took Tracktion a second or so to be prepared for recording again. Mind you these numbers were probably only 10 minutes long for each and it is possible that the longer the track the longer Tracktion (or your hardware) needs to be ready for recording again.
The other good thing was that all the recordings were named differently in the file structure so were easily imported into individual edits later on for mixing.
Cheers
Graham
www.lakesiderecordingstudio.co.nz
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
If you're going to try that, try unticking "show waveforms" in the options menu, as that may speed up the turn-around.. (as there will be no need for Tracktion to calculate the waveform display)LRS wrote: What I did was to stop the recording after each number and recommence recording almost immediately on the same edit. It really only took Tracktion a second or so to be prepared for recording again. Mind you these numbers were probably only 10 minutes long for each and it is possible that the longer the track the longer Tracktion (or your hardware) needs to be ready for recording again.
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
Actually thats probably worth trying anyway.. the waveform display for a 4 hour file must be pretty large: maybe Jules didn't anticipate them getting so big..?
-
- KVRist
- Topic Starter
- 35 posts since 19 Mar, 2005
Thanks Graham,LRS wrote:Hi Matt
I have done a few sessions of live recordings including one about a year ago of up to 12 tracks and some 4 hours in total. What I did was to stop the recording after each number and recommence recording almost immediately on the same edit. It really only took Tracktion a second or so to be prepared for recording again. Mind you these numbers were probably only 10 minutes long for each and it is possible that the longer the track the longer Tracktion (or your hardware) needs to be ready for recording again.
The other good thing was that all the recordings were named differently in the file structure so were easily imported into individual edits later on for mixing.
Cheers
Graham
www.lakesiderecordingstudio.co.nz
I will give that a try. I usually have at least a small space I can sacrifice if traction won't require a reboot. Since my first failure, I've been running a backup (2chan 16/48 20 GB HD recorder) off the mains of the mixer so I can throw a 16/48 patch in during post... talk about postproduction hell though... If I can get it to go an hour per shot, then do a couple of small patches I'll be good.
I'm going to try the whole scenario again at 14 chan of 16/48 and see if it holds together that way. In truth, up untill I bought the firewire card and lappy, I was mixing on the fly to a 2track HD recorder and had nice sounding (though not very well ballanced) recordings, so I will survive. I will be rolling the dice though, and I don't like that when there is $$$ involved. If I don't get my software issues handled by then, I will be going with a 2-chan board feed off the FOH console, two room mics, and two stage mics to fill in the instruments. Both gigs I have next week are smaller venue size/PA so the board feed will be mostly vocals anyways. I can usually live mix 6 chan and make it a keeper... just a little pressure!
If anyone has time to run this test, I would love to hear results. I think I was successfull at 3hr 15min on 1 ocassion, 4hrs at time-out has been consistently acurate, and 1 hr or less has been good. Try to stop it at the 2hr mark... that seems to always fail. 2 hrs should be about 25-30 GB per my scenario posted above.
Matt
-
- KVRist
- Topic Starter
- 35 posts since 19 Mar, 2005
that is one thing I hadn't tried... I know even after an hour recording it takes a good 10 minutes for all the wave forms to display.platinumears wrote:Actually thats probably worth trying anyway.. the waveform display for a 4 hour file must be pretty large: maybe Jules didn't anticipate them getting so big..?
I'll try that one tonight. Testing new gear used to be fun...
Matt
-
- KVRist
- 88 posts since 10 Aug, 2003 from New Zealand
There you go! I didn't even realise that function existed.platinumears wrote:If you're going to try that, try unticking "show waveforms" in the options menu, as that may speed up the turn-around.. (as there will be no need for Tracktion to calculate the waveform display)
Cheers
Graham
www.lakesiderecordingstudio.co.nz
- KVRist
- 426 posts since 14 Apr, 2003 from Switzerland
Recording such long sessions will be a problem for ALL DAWS when you record in wav format. The header of wave files is 32 bit which translates in roughly 2 GB worth of data - anything beyond this will lead to failures. That's why Sonic Foundry developed the Wave64 format which has a 64 Bit header.
Tracktion at this point does not support wave64. Make a feature request.
Cheers, Pädy
Tracktion at this point does not support wave64. Make a feature request.
Cheers, Pädy
-
- KVRAF
- 1949 posts since 21 Mar, 2003 from Labrador
What were you using before Tracktion? You could go back to it until you get the Tracktion problems sorted. Since you're already familiar with the old software, you know what it can do.mmmatt wrote:wow... active forum! Thanks for the input guys. Going backwards here... yes I know I have a ~$2500 rig and not a $65000 rig. I still want it to work. That is still a lot of money to me.
At least that way you won't lose any gigs!

