Inter-DAW project translator massive price cut
-
- KVRer
- 12 posts since 4 Aug, 2009 from London UK
Short ans is yes.
Logic 5.5 for PC can export in Open TL & OMF, but to be honest there is a lot of info that is just not exported. Emagic also had a distinctly different idea to other DAW's of how these formats are structured, which we can read. We can also handle the fact that stereo files are left Interleaved.
On the Export side we can generate the XML based .Capture format which again is distinctly limited & the far more useful Steinberg Track archive XML's.
BTW what are SMF's
John L
Logic 5.5 for PC can export in Open TL & OMF, but to be honest there is a lot of info that is just not exported. Emagic also had a distinctly different idea to other DAW's of how these formats are structured, which we can read. We can also handle the fact that stereo files are left Interleaved.
On the Export side we can generate the XML based .Capture format which again is distinctly limited & the far more useful Steinberg Track archive XML's.
BTW what are SMF's
John L
John L
-
- KVRist
- 236 posts since 18 Mar, 2003 from Jacksonville, FL
Cool. SMF is my sad way of referring to standard midi files.
I saw there is a demo. Hopefully I will have some time this weekend to see what it can do. If it does even a decent job of translating the files, I'll be a customer.
I saw there is a demo. Hopefully I will have some time this weekend to see what it can do. If it does even a decent job of translating the files, I'll be a customer.
Even I was offended by what I was going to put here.
Newest Release, retro EBM, Brute Opposition - Unity of Command, released Sept '22 bandcamp link
Newest Release, retro EBM, Brute Opposition - Unity of Command, released Sept '22 bandcamp link
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
Like all the other 'audio' converters we don't cater for midi unfortunately. Audio & some video but no midi or fx.Chemik wrote:Cool. SMF is my sad way of referring to standard midi files.
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
Version 2.5 of AATranslator is currently in beta and is expected to be released before the end of the month.
This next version has numerous enhancements across all importing and exporting functions but the real bonus will be the ability to create native ProTools (v5) session files.
This means that you can move sessions to & from ProTools (v5 to v8+) as well as all the other daws we support (Vegas, Cubendo, Samplitude, Audition, OpenTL, AES31, OMF, Reaper, N-Track, Paris, etc, etc.
This next version has numerous enhancements across all importing and exporting functions but the real bonus will be the ability to create native ProTools (v5) session files.
This means that you can move sessions to & from ProTools (v5 to v8+) as well as all the other daws we support (Vegas, Cubendo, Samplitude, Audition, OpenTL, AES31, OMF, Reaper, N-Track, Paris, etc, etc.
-
- KVRAF
- 6159 posts since 4 Dec, 2004
For those of you who haven't had any one to one dealings with Michael or his company and or associate(s), I can tell you from our personal communications and from watching him serve customers and potential customers translating stuff for free...
... he's a stand up guy and the AATranslator product works well.
I know how hard he's worked (and is working) on it having myself made a brute force VB coding attempt at converting Cubase *.xml archives to Reaper projects some time ago.
I had some limited success but I can't imagine the various roadblocks they've had to jump over with the various daw formats.
... he's a stand up guy and the AATranslator product works well.
I know how hard he's worked (and is working) on it having myself made a brute force VB coding attempt at converting Cubase *.xml archives to Reaper projects some time ago.
-
- KVRer
- 12 posts since 4 Aug, 2009 from London UK
Quick update.
Michael & I have been very busy. A huge number refinements to existing formats, we start with converting what is supposed to be a given standard, then as we get more files to play with from our users make sure we can read & write to the hideous mass of incompatibility that is what DAW manufacturers actually use.
Guess what, now we are immersed in supporting the output from the "big boys" in DAW's, you know the ones that have difficulty reading their own files the latest update has involved some major re-writing. But now we reckon we can read more PT5 files than Pro Tools can.
So new stuff in the next release, is PT write (this has been major hard work) & Ardour read which has a logical well written format, so was sort of easy.
PT read can now handle way more of the variations of what a PT5 could be, plus we have better OMF, Open TL and Sony Vegas support.
Sorry, but writing OMF is still in beta & will not make the next release, which should be out in a few days.
Michael & I have been very busy. A huge number refinements to existing formats, we start with converting what is supposed to be a given standard, then as we get more files to play with from our users make sure we can read & write to the hideous mass of incompatibility that is what DAW manufacturers actually use.
Guess what, now we are immersed in supporting the output from the "big boys" in DAW's, you know the ones that have difficulty reading their own files the latest update has involved some major re-writing. But now we reckon we can read more PT5 files than Pro Tools can.
So new stuff in the next release, is PT write (this has been major hard work) & Ardour read which has a logical well written format, so was sort of easy.
PT read can now handle way more of the variations of what a PT5 could be, plus we have better OMF, Open TL and Sony Vegas support.
Sorry, but writing OMF is still in beta & will not make the next release, which should be out in a few days.
John L
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
A quick update:-
Been at it all day and I know JL has been doing an unbelievable amount of testing - with a release of this size (v3.0) with so much added or enhanced something is bound to slip through the cracks so bear with us.
The only known PT issues we have (apart from PT itself) are :-
1. haven't worked out their internal referencing method for Beat markers.
2. while ProConvert can read our PT5 generated markers (and vice versa) PT itself may not read ours in all cases
Also there are still some path issues when converting sd2 files to wav and then splitting stereo ones into seperate mono channels.
We will address these and any other issues which arise with an update soon after release.
Release won't be tonight but very very soon now.
BTW Ron has nearly got a working omf happening - no envelopes yet but hey neither has some versions of sonar
Been at it all day and I know JL has been doing an unbelievable amount of testing - with a release of this size (v3.0) with so much added or enhanced something is bound to slip through the cracks so bear with us.
The only known PT issues we have (apart from PT itself) are :-
1. haven't worked out their internal referencing method for Beat markers.
2. while ProConvert can read our PT5 generated markers (and vice versa) PT itself may not read ours in all cases
Also there are still some path issues when converting sd2 files to wav and then splitting stereo ones into seperate mono channels.
We will address these and any other issues which arise with an update soon after release.
Release won't be tonight but very very soon now.
BTW Ron has nearly got a working omf happening - no envelopes yet but hey neither has some versions of sonar
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
Well we have just put up version 3.0 and no doubt there will be a 3.0.1 soon.
There are a range of minor things yet for us to address and no doubt in the rush we probably missed something obvious but then if it was easy everbody would be doing this or impersonating Elvis (or both!).
BTW Thanks to everyone who went out of their way to test, support or just badger me into fixing things and of course thanks to JL for his doco and testing (someone please RTFM as he went to some effort with that).
There are a range of minor things yet for us to address and no doubt in the rush we probably missed something obvious but then if it was easy everbody would be doing this or impersonating Elvis (or both!).
BTW Thanks to everyone who went out of their way to test, support or just badger me into fixing things and of course thanks to JL for his doco and testing (someone please RTFM as he went to some effort with that).
-
- KVRist
- 174 posts since 6 Apr, 2005
this app looks kewlRunaway wrote:but then if it was easy everbody would be doing this or impersonating Elvis (or both!)
as all my tracks are in Tracktion, EnergyXT & XT2 format i currently have no need for it,
& my productions are 90% midi,
but if a day comes that you support any of these daws & midi export i'll be joining ship
good luck with this!
Ben
whats a sig?
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
We released version 3.1 of AATranslator last night.
It contains:-
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.
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
- Certain dialects of Steinberg omfs had missing clip offsets/indents
Certain dialects of Avid omfs had extracted media incorrectly allocated to the wrong clip.
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.
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
Probably a little premature but .....
It looks like Ron (part of our crack team not the team on crack) will have an OMF (or maybe it should be OMG) export function available for us to plug in (we already have the spot ready and greased up) probably within 24 to 48 hours. Which means that after a short but intense testing period we should have this much awaited functionality ready for release very, very soon.
Keep you posted.
It looks like Ron (part of our crack team not the team on crack) will have an OMF (or maybe it should be OMG) export function available for us to plug in (we already have the spot ready and greased up) probably within 24 to 48 hours. Which means that after a short but intense testing period we should have this much awaited functionality ready for release very, very soon.
Keep you posted.
-
- KVRist
- 73 posts since 2 Aug, 2009 from Sydney, Australia
Oops - forgot to mention we released v3.2 a few days ago.
Lots of small but useful enhancements as well as bug fixes.
Added track automation across all daw formats that we support and added support for Ardour.
Already working on the next release.
Lots of small but useful enhancements as well as bug fixes.
Added track automation across all daw formats that we support and added support for Ardour.
Already working on the next release.
-
- KVRian
- 694 posts since 6 Aug, 2002 from London, UK
When are you planning to add SONAR to the list?
-
- KVRer
- 12 posts since 4 Aug, 2009 from London UK
Yes this is true, but only tested with Ver8 so far (I'm the beta tester guy for AATranslator BTW) I/we would really appreciate any Sonar 8.5 or in fact any more Sonar OMF's from any version to test.Runaway wrote:AAT will already read an OMF produced from Sonar.
Please help us to make AATranslator better, and send us OMF's
Please say which version of Sonar you used & if at all possible a/some screen shots of (a) what your Sonar session has before export to OMF & (b)what a re-import into Sonar gives.
please e-mail to http://www.aatranslator.com.au/
John L
