dubdisciple
markyzno
Yup, I can tick all those boxes... Although I am sure this issue will be in the envelopes/Fade/Automation data that is being transferred to an OMF.
BUT....
Whats the point in bouncing to clips/bouncing when what you want to achieve is the edit points and fades for the Client in the other studio on another DAW? As surely then you may as well just make stems and be done with it?
It seems to me that Sonar has built this guide for very simple music based projects rather than a more complicated Film project
I think you hit the nail on the head. OMF is less and less effective the more intricate the project. I think anything beyond simple fades fails. I accidently picked a great project to show how it may be more work to get all these tracks in a way that Sonar will export without error than to export stems.
There must be a better way for Sonar to use OMF files. I have zero understanding of the coding behind it (God I wish i did) but I know for a fact that when I get an OMF from FCP for example that it imports no problem. Just the other day I had to deliver an AAF as a go-between between one client and another, so I got an OMF from the Director (which had extensive edits - fades and such), that imported into Sonar BUT without fades, so imported into PT NO problem WITh fades, then could export into an AAF.
So, logically, the technology is there but Sonar havent really researched too hard into this area through no fault of their own being a vastly smaller company than Avid or Adobe etc
But I really would like to strengthen my passion to Sonar that if they want to get into the Post Production "Game" then this is a KEY issue.
(p.s, btw my Javier Colon test project is still attempting to wrap itself into an OMF, I have no activity but dont dare press a click in the workspace window for obvious reasons)