Trackion doesn't indicated when the drive is full

[rpc9943]

sure im not saying t2 doesnt need to have that amended, but still i stand by my point

RonC

[Lunch Money]

I don't know if the point "get a new drive" is a very persuasive one. Wait, am I in the right thread?

[rpc9943]

how about freeing more space? i mean cmon man if you expect to do music you cant work with anything less than 1gb per song

RoNC

[Lunch Money]

Sure, but that doesn't mean you throw another drive at it. It means you organize your projects and back them up to optical media.

[Mr. Tingle]

My point is about having to constantly monitor hd space, and Tracktion makes this imperative rather than casual.

[Mr. Tingle]

it took you a whole day to think of going into "my computer," right clicking on the drive and hitting "properties"?

How can I make this short?

Bearing in mind that T has a poor record with the render function of late:

The song I'm trying to render is 30 mins long and takes over 1/2 an hour to export. As Tracktion gave no reason to why it only rendered 9 mins of the track or sometimes nothing at all AND I had some automation that started at about 9 mins my thoughts were that either the automation or a vsti was playing up.

Basically it took 1/2 hour for each test as I muted tracks, rendered individual tracks and turned off vst's, this all took ages at 1/2 hour a go.

If T hadn't had problems with the render function of late I may well of thought of hd space.

[bernhardtjeff]

well, that explains why it took all day, i guess.

[Lunch Money]

I'm on your side, Mr. T (pity da fool who ain't!), but Tracktion's render doesn't have a bad track record as of late... people claiming there's a problem doesn't mean there IS a problem. Which there's not, or at least not that I'm aware of. Any outstanding problems have long-since been fixed.

Well, except for your current problem, which is legitimate.

(but easily fixed by the user. )

[Mr. Tingle]

I'm on your side, Mr. T (pity da fool who ain't!), but Tracktion's render doesn't have a bad track record as of late... people claiming there's a problem doesn't mean there IS a problem. Which there's not, or at least not that I'm aware of. Any outstanding problems have long-since been fixed.

Well, except for your current problem, which is legitimate.

(but easily fixed by the user. )

Oddly enough after I freed up some hd space and re-rendered, the new exported file complely missed one vsti synth track out I checked back and the track was not muted.

I re-rendered and it mystereously reappeared.

This is not the only time that T has given different results on consective renders.

It seem especially suseptable to mis-rendering with automated tracks.

So, still a little work to do..

[Lunch Money]

Weird.

[longimanus]

I also get those weird rendering glitches with T2, namely:

If the cursor is set after some automation changes when rendering, sometime Tracktion doesn't take the automation that happens before the cursor on some tracks. The cure seems to be to make sure the cursor is at bar 1 before rendering. Haven't found a way of replicating this, sometime it happens and sometime it doesn't.

If a render is attempted at a sample rate that's different than the audio card settings, whole section of tracks will be missing from the rendered edit; problem seems more acute with NI VSTI but also Wusikstation and some others.

Exporting (rendering) midi is problematic at best. If ONE audio processing plugins is on the midi path, including the master buss, then the directory chosen for export will be empty of midi file WITHOUT one word of warning of any kind.

Rendering edit with NI VSTI and other plugins mixed up is also a sure road to disaster. The only way I have found to safely render NI tracks is to render them totally alone in the edit and make sure the export settings matches the audio card settings. There probably is a way of making a list of which plugins used in combination with NI product causes problems (I suspect FnalMix is a contender for incompatibility with NI in Tracktion), but life is too short.

Now that I know theses things I can easily work around them, but they've been a source of aggravating frustration and time lost.

[dealwithit]

I agree that T should have (somehow) warned you, but I'm also surprised that you'd fire off a render on a 30 minute (!) song without having a clue that you were anywhere near disk capacity. Not blaming you, per say, just surprised.

[Mr. Tingle]

I have losts of drive space and lots of partitions of all the different projects in use (clients/mine/junk etc). I just have this (false) impression that I'll never run out of space.

[Mr. Tingle]

If the cursor is set after some automation changes when rendering, sometime Tracktion doesn't take the automation that happens before the cursor on some tracks. The cure seems to be to make sure the cursor is at bar 1 before rendering. Haven't found a way of replicating this, sometime it happens and sometime it doesn't.

Yes, I always do this, seems to make a difference.

I know someone (rock?) who puts the play head past the out marker, runs it for bit to clear the buffer (e-to-e) then returns to the start and then exports.

Also, if one way doesn't work then I will select all the tracks individually using ctr-track-select in the edit tab and then in the export panel choose 'only render selected tracks', this invariably works.

It never seems to be as simple as just exporting

[chimmy]

If 'only render selected tracks' is chosen, is the Master Buss included or not? I've always assumed no, because the choice specifically states 'only render selected tracks'. Does anyone know for certain off hand? Otherwise it's easy enought to test.