Project Translator Changelog

What's new in Project Translator 0.1 Build 42

Oct 3, 2013
  • Build 42 contains a fix for issue 4. When Ardour projects are opened the region and track gain automation is merged. This is written out to the AES31 file as track gain automation since this is the only type which is supported. There is also a fix for an error when handling opaque regions in Ardour. Work around for a case where user had many items on VCS Startrack take board with the same name though different audio. Added test for usable disk free space which writing project.

New in Project Translator 0.1 Build 37 Beta (Mar 12, 2013)

  • Build 37 contains a fix for issue 2. If there are overlapping clips and also gain automation then the subordinate clips are moved to a new track.

New in Project Translator 0.1 Build 35 Beta (Dec 10, 2012)

  • Ardour writer now working. This build contains a working Ardour file writer so it is now possible to convert AES31 projects for use in Ardour. There is a possibility that gain automation could be lost if you have multiple conversions between formats. The reason for this is that the Ardour reader loads 'region' gain automation and transfers this to 'track' gain automation in AES31. Region gain automation does not seem to exist in AES31, only track gain automation. The Ardour writer preserves the track gain automation from AES31 and writes it as track gain automation for Ardour. The logical next step to resolve this potential problem for users is to merge region gain with track gain in the Ardour reader which will require some simple arithmetic. VCS reader fix.
  • This build contains a fix for clipnames which contain the '%' character, this will be replaced by the underscore '_'.