Quote:
Originally Posted by kk@jamsync.com  It's not about blame...it's about portability of the format. It's about making it easier for the users to transport data among various setups instead of making it HARDER for the user. Data transport formats shouldn't be user hostile and users shouldn't suffer when attempting to load a simple audio file into a DAW. Project files are a different animal, but this problem with incompatibility of multichannel files has gone on far too long.
I won't even go into the havoc that it is wreaking in the BluRay authoring community. People want to simply use multichannel 48kHz files, but can they with most commercial BluRay authoring packages? NO. While claiming to be "transparent", they, in fact fail because of this very problem, so a lot of the packages really only support stereo. |
Again this is not pyramix fault.
The manual is quite clear and it is more a matter of which format a project is exported in. i recently had a problem with xml export that I would have avoided if I had read the manual more carefully.
Frankly, when it comes to handling a huge variety of formats and even different samplerates within a project, pyramix is a leader.
So lets be fair here and complain about general problems of interchange between all leading DAWs rather than complain about Merging.