Focus on exporting!!!

[Rack Bitz]

You hear that guys?? Lets get him!!

that fuckin creased me up(for the non english im laughing my bollox off sorry nuts off)
AD80 your a bad man

[AD80]

This whole place "creases me up" . I think most Tracktion users are .

[ModuLR]

agreed! bucha professional loons!

[Aleatoric]

huh.....if you clearly read my first post I am talking about problems when "exporting" an entire song. Than I point out about a 16 bit problem as well as it is in similar nature......ie about rendering....hence the title let focus on rendering.

Let me explain.....rendering is when your Tracktion song.....all those midi files, all those audio files.....all those VST effects, all that careful mixing become 1 single audio file by exporting your entire Tracktion edit into a wav file. You cant export it to a aif file but I wont get into that. Now I and others like the post I mentioned are having issues with skips and shit in the final song file....so the outcome of all this time and work i mentioned above is one skippy sound inaccurate audio file that is useless. I simply said this should be focused on so that when I am done a song the finished audio export will sound correctly and not have errors in it. This is not a selfish me me bug but a problem others have too.....and is the most major problem to anyome who makes a Tracktion song and cant have it on a cd or in iTunes or even listen to it without opening up Tracktion cause it wont export.

Now I feel like a loop machine....I already said this but was called an asshole for it. Like I said I will just report bugs directly to Jules but having now several songs that I worked hard on (I'd say 30 hours worth of sitting in fron of Tracktion total) that I cant do shit with till this is fixed! My best bud is having the same problem and now ditched Tracktion for Logic and Live 4. I like Tracktion alot but have issues when I cant make a song with it. I dont know what else to say.....just thought this should be fixed.....or of a more upmost priority than say the font being used in Tracktion v2 or whatever. Call me an asshole.

[Aleatoric]

And the part about hiring valley and modular was joke....

[Rack Bitz]

huh.....if you clearly read my first post I am talking about problems when "exporting" an entire song. Than I point out about a 16 bit problem as well as it is in similar nature......ie about rendering....hence the title let focus on rendering.

Let me explain.....rendering is when your Tracktion song.....all those midi files, all those audio files.....all those VST effects, all that careful mixing become 1 single audio file by exporting your entire Tracktion edit into a wav file. You cant export it to a aif file but I wont get into that. Now I and others like the post I mentioned are having issues with skips and shit in the final song file....so the outcome of all this time and work i mentioned above is one skippy sound inaccurate audio file that is useless. I simply said this should be focused on so that when I am done a song the finished audio export will sound correctly and not have errors in it. This is not a selfish me me bug but a problem others have too.....and is the most major problem to anyome who makes a Tracktion song and cant have it on a cd or in iTunes or even listen to it without opening up Tracktion cause it wont export.

Now I feel like a loop machine....I already said this but was called an asshole for it. Like I said I will just report bugs directly to Jules but having now several songs that I worked hard on (I'd say 30 hours worth of sitting in fron of Tracktion total) that I cant do shit with till this is fixed! My best bud is having the same problem and now ditched Tracktion for Logic and Live 4. I like Tracktion alot but have issues when I cant make a song with it. I dont know what else to say.....just thought this should be fixed.....or of a more upmost priority than say the font being used in Tracktion v2 or whatever. Call me an asshole.

again and again and again
tell jules or mackie
the only reason people dont like these threads
is because they already pertain to a known issue
which i will gaurantee is being looked into
laugh and the world laughs with you
be pissed off and the world pisses on you
lighten up
i have issues with tracktion and they are similar to yours and worse
just go and moan at mackie
and if someone calls you an asshole f**k em
lifes too short to worry about forum chitchat
or maybe that should be shitchat

oh have you tried recording the output into your audio editor
it works for me but i aint on mac

[Aleatoric]

Good advice Rack Bitz....., part of it sounded like the Tao Te Ching.

[Rack Bitz]

Good advice Rack Bitz....., part of it sounded like the Tao Te Ching.

the tao te wot
i use taureg
http://www.brambos.com/news.html

[unknown user]

....problems when "exporting" an entire song... [snip] ...rendering is when ...
[hit-me-over-the-head newb tutorial deleted]

This is much better, I certainly don't think you're an a***ole. and it's a lot more likely to get a useful response.

Think of the forum dialog as you would a ongoing conversation amongst a group of people. You don't just walk up and blurt out "this really really sucks please fix it waaaaaah waaaaaah I want my mommy waaah waaah". You say "'scuse me, ahh, you see, rendering skips on this song, and is thus unusable, so what can be done about it?".

So in turn, I'll respond with some logical troubleshooting type questions:

Can you build ANY simple song and render it correctly? If so, then something in your songs is *causing* the skips to occur, probably by loading the CPU excessively. So then the question morphs into, "can you identify what causes skips?"

You can start at either end and work in the other direction--i.e. you can add elements to the simple song, or you can remove elements from your skippy song.

You might start by looking for CPU-hungry VSTs. Some may have nonlinear CPU loading characteristics, i.e. they might not use a whole lot during 1x playback, but get stuffed up when rendering at maximum speed. I know from experience that multi-threaded code can be prone to this sort of thing if care isn't given to proper synchronization. (Are VSTs typically single or multi-threaded? Any coders out there know?). Try deleting tracks one at a time to zero in on the offensive ones. Try deleting automation curves. Try splitting up racks if you're using them.

Now doesn't that feel better--more like two people rationally discussing something? OK, now it's your turn.

BTW, anyone else please feel free to jump right in and be friendly and helpful.

[Jeremy_NSL]

I have never got timing problems when rendering or exporting. I have got very strange 'first note' not sounding problems - but there are workarounds for those problems, as much as I hate them.

[unknown user]

floyd, aleatoric is on the mac, are you?

I happen to *own* several older macs (Logic Audio user of yesteryear, started with LAM 2.0), but these days I'm running a 2.8G P4 laptop.

I haven't seen any rendering issues on the PC, but then again I've only rendered maybe two or three songs, and these were fairly simple, no racks or serious synth VSTs. Mainly the sampler, a few one-shot wavs, and a bass guitar track. Using mostly the native T plugs, and of course the excellent kjaerhaus plugs.

[Rack Bitz]

bithead my man
theres definatly pops and glitches to be found exporting audio even on the pc
as a sample creator (a shit job but someones gotta do it)
i render all the time
it seems its related to the tempo aswell in some weird way
if i stay under 100 bpm i dontlose first note even on looping and no glitches
but if i go above i may get probs
my workaround though is to record straight into ngwave
works a treat for me
just means i have to re edit all my samples
still i think jules has all this shit under control
and i just get on with it

[Aleatoric]

Yea Audio Hijack is a sure workaround for rending problems. thanks for the advice.

[Sleepwalker]

My experiance is that absynth get a lot of hanging notes (almost on every render!) when playing tempo synced arpeggio sounds. They just continue playing, and even off-beat, but only in the render, oddly enough. And also in the freezed tracks. other synths are mostly ok, for me. I updated from Absynth 2.04, to 2.05, but the problem was still present.

About the 16bit/24bit issue, im shure we all agree that 16bit Cd quality is good enough! But when you have a 16bit track, and you keep on working on it, and messing around with it, the audio file will sound more and more crappy.
I think this is one of the things Aleatoric is trying to say. This is only a mac thing.

Hope this helps

[lshea]

About the 16bit/24bit issue, im shure we all agree that 16bit Cd quality is good enough! But when you have a 16bit track, and you keep on working on it, and messing around with it, the audio file will sound more and more crappy.

That happens to me too but I don't think it's related to bit depth, merely limited chops.

Seriously, I thought that apps like T use higher bit depths internally to avoid clipping and resolve down to say 16 bit only on output.

Does anyone's music really use 24 bit (ie 140db dynamic range)?

I agree with previous poster. Sounds like a ruse to obseletify 16 bit gear.