Ok, Im done with a project...now what?

Discussion about: tracktion.com
RELATED
PRODUCTS

Post

My specs are

Win XP sp2
SATA HD 60 GB(with a ton of space left)
P4 2.8 ghz
Abit MB with intel 865PE northbridge chipset
512k ram
256 mb 8x ATI Radeon AGP graphics card
SB Live 5.1 with Kx drivers(I suspect this might be a culprit, I know, I know SB live sucks) I gotta invest in a Audiophile 24/96 or an Echo MIA Midi

I did my homework before investing in these components, there's plenty of power under the hood.

That's what burns me up about the weird illogical problems I've dealt with(which no one else seems to experience)

To date here's what I've dealt with:
A strange midi note cutoff problem which no one responded to and all of sudden stopped happening.
The manystation install which spit out one folder to a strange directory
An error with Traktion trying to load the ASIO 16bit and 24bit drivers that go with my Tascam US122 interface.(This happened after I updated to US122 3.0 drivers)
and now this refusal to render a stupid 28 bar tune.

Post

--UPDATE---
I tried choosing the lowest sample rate and I clicked render at 1x and same damn thing. rendering stops at about 10% and I have to ctrl-alt-delete to get out of the frozen Traktion


I was able to render one of the three tracks individually with no problem and very quickly I might add.

So maybee I can higlight and render all three tracks together?

I shall try this.

Post

This brings up a basic question if someone can answer.

My three tracks are green colored midi clips on tracks 1,2,3 each outputting into manystation vsti.
Now if I render let's say track one. I get a blue audio waveform on track one and the three midi clips are bounced down to tracks 2,3,4.

Do i have to render each midi clip to an audio wave to where it lays out like this:
Track 1: Audio clip of midi clip 1
Track 2: Audio clip of midi clip 2
Track 3: Audio clip of midi clip 3
Track 4: midi clip 1
Track 5: midi clip 2
Track 6: midi clip 3

Do I then mute tracks 4,5,6 and THEN use the export> render to audio file function?

This seems to be a round a bout way of doing it. Or is this how it should be done?

Post

Hi, Dimwit.

When you render a single track you are given the option to keep the original midi or not. Keeping the midi will cause it to move down to make room for the audio clip.

Normally, one wouldn't render anything before exporting the project as a wav file. If you do render first, it might be a good idea to mute the unwanted tracks.

More likely, one would freeze a track or several tracks if memory is a problem--then export.

Meanwhile, if you still are having trouble creating the wav file, try using a different synth than the Manytone--it's brand new and who knows?

Tom

Post

Thanks a lot everyone for your help, but I think I figured it out.

Here's what I did.

Forst I went to settings and picked a different driver
(DirectSound driver) I went back to the edit screen and saw that the cpu meter was going nuts. Red all over the place. So then it clicked in my head "Ahh I had DirectSound driver set at 80 somthing k sample rate so that I could play my manystation at 17.4 ms latency."

I lowered sample rate to 44k sample rate and I raised the samples to 2560(which was a latency setting of 58.0 ms) Then I tried rendering again with render at 1x enabled BOOM :party: :party: :D :D :shock: :party: :party:
It worked GREAT, my three tracks were rendered in about 20 seconds. So I realized you have to tweak with the sample/latency settings when you render to audio. They need to be higher than when your playing or recording in real-time in order for it to go off without a hitch.
Sorry to drive you guys crazy

Post

Dimwit (feels weird calling somebody that), Manystation is the same engine as Wusikstation and WS has a known problem when trying to render something in T with a different sample rate than the audio settings. WilliamK knows about this and is working on a fix AFAIK, but it might take some time.

Meanwhile, rendering at the same sample rate and bit depth as the audio settings does the trick for me, I then use Voxengo R8brain(free, but high quality) to downsample if I need to.

[edit] Oh, and yeah, the Lame dll coupled with the razor lame front end is a very good choice for mp3 encoding; it does batch encode also.
Quote of the day: "If you can't answer a man's arguments, all is not lost; you can still call him vile names."--Elbert Hubbard 1856-1915

Post

Thanks for the tips Ezy, I've bookmarked the home pages of those programs you mentioned. I DL'ed a program yesterday called MkWActII for .wav to .mp3 conversion(it also does .wav to .shn although I think .shn is giving way to .flac)

Ahhh... so the wusik engine has known problems with rendering in Tracktion.
I'm glad I stumbled upon the solution.
I'm new at this game but I'm starting to develop a problem solver mentality which I'm sure is natural for anyone who takes on computer audio.

I have a ton to learn still, but in a way I'm glad I'm having problems in my initial stages. What doesn't kill me makes me stronger right? :)

Post

Right :)

Post

or leaves you in a coma ...

slainte :shrug: rob

Post Reply

Return to “Tracktion”