Exporting problems in aiff and wav formats

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hello all, I have been workin on a long score for a motion graphics colaberation useing a Mac 667 tibook tracktions newest update and four vst synths in tracktion. i am here to find out how many people are exsperienceing the same problems i am when exporting to aiff and wav. now what i get with wav is a true audio file playing back but with skipping going on like on a scratched cd. with the aiff i get massive feedback and distortion. now i am forced to us another app ..(logic) I would love to use this app for projects but i cant realy trust it. if anyone that may have a good idea of what it is from i am all ears. it is not my computer as it works perfict with apps like logic and cubase. reason ect.. trying to find some answers on this ..

-c
667 ti book maxed out
tracktion
logic
reason
NI
max/msp
reaktor

Post

Yo monkatron,

The aiff 24 bit export causing feedback and distortion is a known bug........the typical solution is to simply export your song as a wav file. I do not expierence any skipping with any of the wav's I have exported with Tracktion. I had probs a few builds ago with Tracktion rendering a wav and midi sequences lost synch some how and the render was inaccurate to what was being played/heard in the Tracktion arrangement. The only thing I could suggest would be to try rending your song as a wav again but this time freeze or render all midi tracks. Hopefully in the future Tracktion will get rendering down pat as there is nothing more frustrating than making an entire song in Tracktion and than not being able to finish it do to exporting problems. Hope this helps.

Post

yo stoney.....
here is the thing I have trouble shooted the whole deal. freeze un freezed
coverted midi to audio ect ect. same thing happens. its not only in 24bit witch you cant realy export much to that bit rate due to a number of reasons that do not matter at this point. it will not export smoothly.. i am stumped.. maybe the next update should focus on this bug....that might be a good start. for now tracktion sits in the dock un noticed...
-c
667 ti book maxed out
tracktion
logic
reason
NI
max/msp
reaktor

Post

hi,

I don't actually have tracktion, but I'm thinking of buying it and thus testing the demo. The first thing I've tested was freezing a track with EWQLSO Silver and it was all pops and clicks, so I left it fast. Then it bugged me so I asked on the techsupport forum and they told me the dfd extension was pretty buggy in NI products, so I turned it off and it now freezes nicely.
Now I'm thinking of buying tracktion again, but is it not going to work when rendering a track as it should?

Post

no man it wont work as it should....not yet. Maybe after you pay more cash for version 2 Tracktion will work correctly with rendering and exporting.......and oh yea reporting bugs will get you yelled at on the forum, sorry to tell you the truth.

Post

I'm not sure if this helps but try exporting/rendering the mix at 16 bit.

To be clear, did you actually prerender each midi track as an audio file and select "replace existing track"?

Maybe these aren't the answers you're looking for but It's what I've been doing and I haven't had anything like the problems I've seen described by some on the forum. I also don't use many vsti's so that could be part of it.

I'm using OS 10.2 on a powerbook g3 266 with built-in audio. Primitive but effective for recording at 16 bit and very stable.

Post Reply

Return to “Tracktion”