Tracktion Software

magnax · Post by **magnax** » Fri Jan 20, 2006 12:52 pm

Hi list! In the release notes for 2.1 it says "Fixed AIFF compatibility on the Macintosh". Yes, but for the worse! When I open a project created with 2.0.2.8, my .aiff files are gone. I the clips themselves it says "Error reading file", in the property pane I'm told that Tracktion "cant't read this file". When I try to re-import them it says "Couldn't handle this file format". They're ordinary aiff, for God's sake!

I've always had problems before when attempting to open files rendered in Tracktion with Bias Peak, which was annoying but work-aroundable, but this isn't good at all. Has anyone else experienced something similar?

Otherwise the upgrade looks cool, with Hide Control Section feature and whatnot.

/magnaX

dry bones · Post by **dry bones** » Fri Jan 20, 2006 1:47 pm

Any other Mac users experiencing this? I haven't downloaded the update yet, and I'm not willing to 'lose' all my AIFFs.

magnax · Post by **magnax** » Fri Jan 20, 2006 1:55 pm

dry bones wrote:Any other Mac users experiencing this? I haven't downloaded the update yet, and I'm not willing to 'lose' all my AIFFs.

Download it, install it but keep the old install in a safe place. It'd be interesting to hear what happens.

/m

classic dave · Post by **classic dave** » Fri Jan 20, 2006 3:14 pm

[quote="magnax"]Hi list! In the release notes for 2.1 it says "Fixed AIFF compatibility on the Macintosh". Yes, but for the worse! When I open a project created with 2.0.2.8, my .aiff files are gone. I the clips themselves it says "Error reading file", in the property pane I'm told that Tracktion "cant't read this file". When I try to re-import them it says "Couldn't handle this file format". They're ordinary aiff, for God's sake!

I've always had problems before when attempting to open files rendered in Tracktion with Bias Peak, which was annoying but work-aroundable, but this isn't good at all. Has anyone else experienced something similar?

Otherwise the upgrade looks cool, with Hide Control Section feature and whatnot.

Yes I had the same problem for a long time. Aiff files created in Tracktion will not open in Logic Pro. Mackie told me they were aware of the problem and were ''working on it''When I asked why a universal and widely used format like aiff was causing problems They told me that the problem was much more difficult to fix than you could imagine. So from what you say the issue is still there. Have not downloaded upgrade yet all my files are aiff so I may wait until I hear more or a fix comes through.

classic dave · Post by **classic dave** » Fri Jan 20, 2006 5:41 pm

magnax wrote:Hi list! In the release notes for 2.1 it says "Fixed AIFF compatibility on the Macintosh". Yes, but for the worse! When I open a project created with 2.0.2.8, my .aiff files are gone. I the clips themselves it says "Error reading file", in the property pane I'm told that Tracktion "cant't read this file". When I try to re-import them it says "Couldn't handle this file format". They're ordinary aiff, for God's sake!

I've always had problems before when attempting to open files rendered in Tracktion with Bias Peak, which was annoying but work-aroundable, but this isn't good at all. Has anyone else experienced something similar?

Otherwise the upgrade looks cool, with Hide Control Section feature and whatnot.

/magnaX

Yes I had the same problem for a long time. Aiff files created in Tracktion will not open in Logic Pro. Mackie told me they were aware of the problem and were ''working on it''When I asked why a universal and widely used format like aiff was causing problems They told me that the problem was much more difficult to fix than you could imagine. So from what you say the issue is still there. Have not downloaded upgrade yet all my files are aiff so I may wait until I hear more or a fix comes through.

Lagrange · Post by **Lagrange** » Fri Jan 20, 2006 5:52 pm

My company uses both Aiff aif & wav (etc) formats across both pc and mac os's. I was wondering if a batch converter would work for youz? Maybe go from aiff to aif?? Let me know what happens here so I can report back to my team. thx

bradkvr · Post by **bradkvr** » Fri Jan 20, 2006 6:23 pm

I had a similar issue with 2.1. Opened a project that had a file called, for example, xzy.aif. Tracktion couldn't find the file, and trying to re-load didn't work either. Re-importing the file didn't work (file wasn't recognized). Changing the extension to .aiff solved the problem.

B

FigBug · Post by **FigBug** » Fri Jan 20, 2006 6:40 pm

I think this is just a file extension bug. Rename all your *.aif to *.aiff and it'll work.

mapper · Post by **mapper** » Fri Jan 20, 2006 7:23 pm

yep i'm experincing the exact same thing..check out my posts on this thread.
http://www.kvraudio.com/forum/viewtopic ... 02#1627902
I dont reccomend this upgrade AT ALL for mac users.
we've been sidelined yet again.
I've not only had error missing file but said has turned into white noise.
luckily I have a back up in an archive but somethings telling me I cant upack this archive.
be afraid be very afraid.
If your systems stable leave it for now this upgrade is a dog.

frankvg · Post by **frankvg** » Fri Jan 20, 2006 10:54 pm

FigBug wrote:I think this is just a file extension bug. Rename all your *.aif to *.aiff and it'll work.

Clever of you! Cheers.
Apart from the 'error reading file' all seems to be working fine on OS 10.3.9

Lunch Money · Post by **Lunch Money** » Fri Jan 20, 2006 11:39 pm

mapper, did you try what Figbug mentioned? Hardly a dog. Just human flubbery.

mapper · Post by **mapper** » Sat Jan 21, 2006 12:06 am

yes i did lunch..

it's wasn't just that it did some very weird things like turning said aif file into very loud white noise..a whole 4 min acoustic guitar take meticulously recorded on a hired pre-amp and mic at great expense..
It then wouldn't let me expand an archive of the edit to try and replace said file.
It did lots of other things too which I dont have the time to iron out.
I dont take kindly to being an unwitting beta tester thats all.
of course I had back ups but spent a couple of hours sorting several songs out.
I like some of the improvements but I cant risk it at the moment i have a big project for an advertiser that aint chump change.
Will mackie re-imburse me if I lose out on a deal..i think not.
They would'nt eben give me the reverb and EQ...
i'm knackered i've had enough today fookin computers.
wheres my guitar?...

Lunch Money · Post by **Lunch Money** » Sat Jan 21, 2006 3:55 am

Not that this helps, but nobody upgrades mid-project... do they? As for the rest of the problems, as far as I can see you're the only one having them. Or am I insane? Seems to me that the file extension problem cured it for everyone else...?

Greg

Steve Prince · Post by **Steve Prince** » Sat Jan 21, 2006 4:21 am

FigBug wrote:I think this is just a file extension bug. Rename all your *.aif to *.aiff and it'll work.

I had the same issue, changing the extension to aiff solved it.

mapper wrote:it's wasn't just that it did some very weird things like turning said aif file into very loud white noise..

I've experienced something similar to this, before the update, in that if I tried to edit the initially recorded file in my 'default' editor (Amadaeus) I used to get the loud white noise thing. However, if the track were rendered in Tracktion first, then I could edit it normally (no white noise). It was a minor inconvenience but only took one extra step ie. when I was happy with the take I'd render and replace it if I needed to clean it up or whatever with my external editor.

But with the latest update of T2 this is now a thing of the past

Steve

bradkvr · Post by **bradkvr** » Sat Jan 21, 2006 4:23 am

I'd call it more of a work-around than a cure. Tracktion should be reading files with either extension.

Tracktion Software

KVR Audio

AIFF compatibility on the Macintosh???