T6 track recording wtf..

[whyterabbyt]

this is one of the things audioprograms should reliably be able to do in any case. hope this gets sorted soon for you whyterabbyt!

cheers. as I say, i do have other software that can do it (albeit on my DAW which is a different PC) , but it was a bit of a surprise that I would have problems with something so basic with T6.

There's nothing in the log files, so unfortunately not much info to send to TSC. Short recordings havent caused it, so I think it might be related to the length of the recording but I cant be absolutely sure. Might be a tedious thing to confirm, to be honest.

[Kang]

There's nothing in the log files, so unfortunately not much info to send to TSC. Short recordings havent caused it, so I think it might be related to the length of the recording but I cant be absolutely sure. Might be a tedious thing to confirm, to be honest.

Interesting, could you tell us more detail about the length of the recording that is getting deleted? I'd be happy to check it out on my setup.

[m_a_t_t]

Fwiw, I recorded long stretches of audio (for tape conversion, actually) way back in T3 days, and had no issues. And, I agree, basic audio recording (of any length) is something than any DAW should be able to perform flawlessly.

[whyterabbyt]

There's nothing in the log files, so unfortunately not much info to send to TSC. Short recordings havent caused it, so I think it might be related to the length of the recording but I cant be absolutely sure. Might be a tedious thing to confirm, to be honest.

Interesting, could you tell us more detail about the length of the recording that is getting deleted? I'd be happy to check it out on my setup.

Both the recordings which disappeared were about 15-20 minutes long ie one side of a vinyl LP (not the same LP; after redoing the first one, I did another 3 sides successfully before it happened again)

[gigazaga]

Stereo recording is a fundamental thing that Tracktion should do extremely well. I think I will set up a long recording test myself and see if I can duplicate the issue.

I would say that DirectSound is not a good choice for Windows 7. DirectSound is only properly supported through Windows XP. You will be much better off with Windows Audio for the driver type.

DirectSound was virtualized starting with Vista and is often problematic on anything other than XP.

[fedexnman]

I'd try the asio4all if your on Windows 7 or wasapi , I bet something in Windows 7 may have interrupted Directsound driver , especially if you lost your inputs on T6 . It could be something as simple as unplugin headphones or something . Maybe someone can duplicate this .

[secretkillerofnames]

Out of curiosity have you tried T5 for this? It might narrow it down. I know I've recorded 30+mins with T5 on Win8.1 just recently with no issue. Avoiding T6 on Win for now due to the Melodyne issues.
I'm using the Asio drivers provided by Focusrite for my Sapphire interface. Recommend you look into using Asio4All at minimum as fedexman suggests. Better to use an audio interface and provided drivers.

[fedexnman]

They just released another T6 update 6.0.19 March 1st . So, TSC are hard at it . I'm gonna mess with it tomorrow .

[whyterabbyt]

Out of curiosity have you tried T5 for this? It might narrow it down. I know I've recorded 30+mins with T5 on Win8.1 just recently with no issue. Avoiding T6 on Win for now due to the Melodyne issues.
I'm using the Asio drivers provided by Focusrite for my Sapphire interface. Recommend you look into using Asio4All at minimum as fedexman suggests. Better to use an audio interface and provided drivers.

I'll give T5 a go, and 6.0.19, but as I say its 15-20 minutes per attempt to test. And sorta leaves me unable to do anything else on that system, which is my main 'work' home PC. (not that it cant do, just that there's no room left on the desk)

As for drivers, I was using one of those cheap-and-cheerful USB record decks, so basic class-compliant drivers. I do have ASIO4all on the system, but didnt want to delve into trying to fudge it so the input was from the USB device while the output was via the existing soundcard, its was being a PITA. Windows Audio was being a little bit fussy too. DirectSound worked first time, and despite being legacy, 'should just work'.

I could sorta think driver issues might relate to the track inputs disappearing (though Tracktion didnt lose them) but generally I'd expect a more serious crash from them. Plus I'd personally have thought that since the track was still armed, Tracktion wasnt changing the state of the driver in any way; stopping recording to a file wouldnt be an operation that interacted with the audio driver. I could be wrong on that, obviously, but if you drop out of recording with a track still armed, your monitoring continues, so 'recording' what's being monitored seems like a DAW-side operation only.

Thinking about that, though, its almost as though what happened was an accidental Abort and then Tracktion hiccuped on talking to the driver and trashed the track inputs as a result. Not saying that's what happened, just describing the behaviour.

BTW does anyone else agree with me about the Abort buttons. Seems kind of risky having them that close to 'safe' operations that dont trash what you just did. I mean I know that's not what happened here, but now Im worried that they're close enough for me to do that accidently as well.

[aMUSEd]

Yes I have never liked them being next to the play and record buttons, too easy to accidentally press instead of stop (especially with them highlighted red).

[whyterabbyt]

Okay, while I was typing that last reply, I had T6 6.0.18 recording in the background on this system; a totally different PC entirely, but still x64 on Win7 x64 and DirectSound drivers.

First attempt, let Tracktion record for about 11 minutes, back to the Tracktion UI, hit spacebar.... and poof. Clip gone and inputs gone.

Now trying 6.0.19.

[secretkillerofnames]

OK I can confirm this is some kind of bug - not a driver issue. Just then on OSX 10.9 T6.0.19 I recorded the input from my Focusrite Sapphire 18i8 for 12mins. Hit space. It wiped the recorded audio, does not appear to have saved it and removed the input.
EDIT: Pressing the stop icon causes the file and inputs to disappear also.

[Peter Widdicombe]

I've hit issues back in the T5 days where long recordings (i.e. > 15 minutes) would cause weirdness / locking up. I had always assumed it was that I didn't have enough memory on that machine, and just recorded shorter clips.

Yeah, Audacity being much simpler did a better job at THAT kind of thing.

[whyterabbyt]

Now trying 6.0.19.

6.0.19 did it on my first attempt, but not on the second.

[Kang]

Just recorded two tracks for 20 minutes, twice, and had no issues on OS X, but I will try with my interface tonight and on a PC as well since I really want to make sure this doesn't happen when it's important.

BTW does anyone else agree with me about the Abort buttons. Seems kind of risky having them that close to 'safe' operations that dont trash what you just did. I mean I know that's not what happened here, but now Im worried that they're close enough for me to do that accidently as well.

The 'abort' and 'abort and restart' buttons are one of my favorite things about Tracktion and I don't think I ever had a problem accidentally hitting them. Although a few times I used them when I thought a take was bad and the talent then says, "let's hear that one!"

My only wish is that the files would be sent to the TRASH. Then they wouldn't be in the session files, you could delete them later as you wish, plus you can get them back if there was an accident.