AATranslator

[Runaway]

We are about 48 hours away from our next release of AATranslator (http://aatranslator.com.au).

We have made significant improvements and enhancements to all existing formats including Cubendo and have also added a number of additional formats including FCP.

We have already started working on the following release and while we already read omf files we have had some preliminary success with creating omf files from AATranslator.

[Runaway]

I'll post this here as it seems related.

I need some kind person to email me an example of a track archive from Cubase v5.1 - I dont need the audio file just the xml file.

I have a user who is having trouble with a conversion and I'm trying to narrow the problem down.
If you could send it via the aatranslator website (.com.au) I would really appreciate it.

BTW version 2.4 of AAtranslator is now available and v2.5 is not far off.
There are all sorts of improvements and addittional daw formats and much more to come in future versions.

Edit: As it turns out there was nothing wrong with our Cubendo export but rather something wrong at the users end. - whew :-)

[Runaway]

We have finally nailed that pesky PT5 session format!

Once tested and released this will enable Cubendo users to take their track archives (XM)L and convert them to a PT5 session format which can be read by any PT version 5 or later.

They can also take a PT omf or PT5 or later session (converted to a PT5) and convert it to a Cubendo track archive or any other daw/format we support like Reaper, Samplitude, Audition/CEP, Vegas, FCP, Capture, etc, etc.

How good is that! :-)

:icon_cool:

[TAFKAT]

Wow,

Thats going to definitely makes things a lot better for many here who have feet in both camps.., plus we won't have to keep listening to the lame excuses from Steini and co that Digi keeps breaking OMF ... LOL

Keep us up to date...

[RSE]

Well done, Congrats!

Does the software automatically separate stereo files to 2 X mono files when 'translating' a Cubendo project to PT5?

[LEX]

Unfortunately the only problem with PT5 is it doesn't support BCW files, and it SD2 files. Unless there is something I've missed. Whenever I save to PT5 sessions in PT, the audio file option is only sd2. And on windows sd2 is a nightmare.

LEX

[Runaway]

Well done, Congrats!

Does the software automatically separate stereo files to 2 X mono files when 'translating' a Cubendo project to PT5?

Just adapting that same functionality that we use when splitting for OpenTL - will be finished soon after coffee :-)

[Runaway]

Unfortunately the only problem with PT5 is it doesn't support BCW files, and it SD2 files. Unless there is something I've missed. Whenever I save to PT5 sessions in PT, the audio file option is only sd2. And on windows sd2 is a nightmare.

LEX

I assume that you are saving on a MAC and if so that is correct. However, we offer, during conversion, to convert the SD2 files to WAV - so no problemo ;-)

[RSE]

Well done, Congrats!

Does the software automatically separate stereo files to 2 X mono files when 'translating' a Cubendo project to PT5?


Just adapting that same functionality that we use when splitting for OpenTL - will be finished soon after coffee :-)


Cool, here's an idea then:

You could use the same functionality in order to add an instant 'rip a stereo track to 2 mono tracks' feature for Cubendo (and other platforms), by exporting and importing or via XML.

[Runaway]

Cool, here's an idea then:

You could use the same functionality in order to add an instant 'rip a stereo track to 2 mono tracks' feature for Cubendo (and other platforms), by exporting and importing or via XML.

Not 100% sure what you mean but if you mean to convert from the same format to the same format just to split a stereo file, well, that would work but (fleshy part at the top of your leg) I wouldn't use it that way.

Reason being that any conversion is never 100% exact. eg busses, fx, midi and lots of other stuff dont get converted.

We could just add a button to pick a file & split it i guess.

Get back to me if i have this all wrong ;-)

[RSE]

Not 100% sure what you mean but if you mean to convert from the same format to the same format just to split a stereo file, well, that would work but (fleshy part at the top of your leg) I wouldn't use it that way.

Reason being that any conversion is never 100% exact. eg busses, fx, midi and lots of other stuff dont get converted.

We could just add a button to pick a file & split it i guess.

Get back to me if i have this all wrong ;-)

A 'track' is not usually a 'file', but a collection of events edited from different takes -

Splitting each file and placing back all the pieces is not my idea of fun :D

Take an edited stereo drum overheads track for example: if only one side needs some work (editting, phase, offset, level etc.) and the plugin is stereo only, splitting it to two mono tracks is best -

Then routing the two mono tracks (panned) through the same plugins busses, fx etc.

Also, sometimes I prefer the sound of two mono plugins (not linked).

[Runaway]

Sorry my mistake my eyes saw the word 'track' and read the word 'file' - DOH

Sure something like that could be built but a fair amount of 'smarts' would need to be wrapped around it as not all daws are created equal.

Some daws only allow mono tracks, some allow mono clips as well as stereo clips on stereo tracks and some allow stereo clips on mono tracks.

Additionally this would be some thing that is used on an existing session and not one that would be used necessarily when converting.

This would mean a different approach to reading the file as you would need to maintain everything that currently existed eg fx, eq, busses, etc

Yes it could be done but certainly not at present given my current workload ;-)

Maybe it would be easier to record two mono overhead tracks rather than a stereo one ;-)

[RSE]

Maybe it would be easier to record two mono overhead tracks rather than a stereo one ;-)

:icon_lol: not for the mixing engineer... but I just got a good deal offer for upgrading to PTHD, so this won't be MY problem anymore soon :D

[Runaway]

We released version 3.1 of AATranslator last night.

It contains:-
significantly reduced conversion times
OMF to PT5 export function
Output automatically saved
Improvements to almost all formats eg xfades in Reaper, PT5 session offset, improved PT video handling and much more
Reads Paris & Lightworks omfs

We still had 2 issues prior to the release and these were :-
Certain dialects of Steinberg omfs had missing clip offsets/indents
Certain dialects of Avid omfs had extracted media incorrectly allocated to the wrong clip.

Well since that release we have finally stumbled upon the solution to the Steinberg issue. So be assured that we will have another release out probably within 24 hours.

Steinberg's Nuendo omfs are just fine - go figure!

We will continue to work on a solution to the Avid problem and hope to have this sorted out shortly.

We have also made significant progress with our OMF export function with actual omfs being written - more work to do yet though.

[Runaway]

We released version 3.1 of AATranslator last night.

It contains:-
significantly reduced conversion times
OMF to PT5 export function
Output automatically saved
Improvements to almost all formats eg xfades in Reaper, PT5 session offset, improved PT video handling and much more
Reads Paris & Lightworks omfs

We still had 2 issues prior to the release and these were :-
Certain dialects of Steinberg omfs had missing clip offsets/indents
Certain dialects of Avid omfs had extracted media incorrectly allocated to the wrong clip.

Well since that release we have finally stumbled upon the solution to the Steinberg issue. So be assured that we will have another release out probably within 24 hours.

Steinberg's Nuendo omfs are just fine - go figure!

We will continue to work on a solution to the Avid problem and hope to have this sorted out shortly.

We have also made significant progress with our OMF export function with actual omfs being written - more work to do yet though.

We are about to release v3.4 which as always is crammed full of goodies.

We are now able to read all versions of PT session files including v8.04 so expect even more from version 3.5 :D

[Runaway]

AATranslator version 3.4.04 is now available - registered users should already have been notified of the download location.

Version 3.5 (currently in beta) will convert ProTools 7 sessions to Cubendo Track archives and (fingers crossed) should have an OMF export function.
We will work on PT8 next and we are also looking to add SAW Studio to our long list of supported formats.

As mentioned on the web site the 'extended' version will rise in price in the next few weeks so if you are thinking of buying you should consider doing it soon.