Mark..have . You checked to see if it is a codec conflict yet?

Well, for all the complaints with nasty adjectives, I'd like to suggest that it is 'best practice' to export time stamped BW, and match that up in in a video editor. Otherwise, I'd suggest just handing the client the BW.
 
Don't get me wrong...
 
The ability to import video into Sonar is a very welcome feature. The ability to export video from Sonar is really handy for a one-off knock outs. I don't expect neither DirectShow nor MediaFoundation to be broadcast ready, nor do I have a problem with that, nor Sonar using it. 
 
I would think that clients contracting for a score, get just that - a time stamped music track, and maybe a reference only video with a music track applied (as a suggested mix) by the composer. The client is going to import the music track in their video edit system anyway.
 
Now, if somebody is expecting a scored and finished video, trusting you to compose a music track, mix it together with any video audio, and produce a finished video product, you're talking a while 'nother animal, because you're talking about a two more workflows than you agreed to. You might just be leaving money on the table.
 
You can certainly ask for a specific format for you to score to. Of course, if the client insists on giving you a format that isn't easily supported by Sonar (and using .mov's on a PC certainly qualifies), you have an opportunity to charge a tad extra for conversion. It's certainly not an unreasonable thing, the client is just as capable of doing that as you are, and he may save himself a few bucks by doing it himself. If he is imperious, does not want to give you a format you can work with, it is more than likely he can easily afford a conversion charge - getting your way cost money and he's used to it.
 
 

For anyone else who has installed codec paks, these tools may help you to sort potential conflicts:
 
http://www.raymond.cc/blo...y-removing-bad-codecs/

dubdisciple
For anyone else who has installed codec paks, these tools may help you to sort potential conflicts:
 
http://www.raymond.cc/blo...y-removing-bad-codecs/

+1

Ok, here's a new one...
Just working on some SFX cutting in x3d and I'm noticing that the timecode in the video window is not matching the timecode in the transport; frames are being skipped and not lining up correctly.  The difference is never more than 2 frames, but those 2 frames can be crucial.
The issue is worse with H264 but still there with AVI.  It almost seems like it's getting confused with dropframe vs ndf?
The video properties also show (confirmed) 29.97 videos as 29.96, if that's a clue...
Any one else experiencing this?

gswitz
Noel,
 
If I understand correctly, it is possible to get AAF working correctly with a codec we buy from somewhere. This is new right? I think that we couldn't do that before X3d... ?

Noel Borthwick [Cakewalk]
In retrospect AAF it seems like it is intended as an interchange format between different video editing systems - it uses structured storage internally. As such its not likely to be a good format for streaming and its unlikely you will find a source codec for it. I don't know a whole lot about it but I assume a host would need to unpack an AAF file and write to a new format more suitable for streaming. Microsoft would be unlikely to support it out of the box in Media Foundation.
 

Correct. AAF works almost exactly the same as OMF, you unpack it. I *think* AAF just has added avid compatibility support....

As with OMF's you'll get them from your Video Editor and then you unpack the project so you can work on the sound edit / score /design etc

One thing I have noticed as it goes with OMF's in Sonar is that Sonar wont read fades on clips  whereas Pro Tools does. This would be a nice feature in Sonar as currently I have to unpack the OMF in PT and then export the stems / tracks into Sonar and work from there. Slightly annoying... I'll fire in a feature request.

Biscuits
Ok, here's a new one...
Just working on some SFX cutting in x3d and I'm noticing that the timecode in the video window is not matching the timecode in the transport; frames are being skipped and not lining up correctly.  The difference is never more than 2 frames, but those 2 frames can be crucial.
The issue is worse with H264 but still there with AVI.  It almost seems like it's getting confused with dropframe vs ndf?
The video properties also show (confirmed) 29.97 videos as 29.96, if that's a clue...
Any one else experiencing this?

We have a bug in our system concerning this but could you please also file a problem report detailing this as clearly as possible. It will be important to include a link sample video to replicate since often these issues can be related to a specific format. It may turn out that the issue is not format related however.

markyzno
 
One thing I have noticed as it goes with OMF's in Sonar is that Sonar wont read fades on clips  whereas Pro Tools does. This would be a nice feature in Sonar as currently I have to unpack the OMF in PT and then export the stems / tracks into Sonar and work from there. Slightly annoying... I'll fire in a feature request.

We could implement clip fades - however they won't necessarily sound exactly the same as what they did in PT since their curves won't match ours exactly. Feel free to log a request however.
 
Did you resolve your issue with video's not loading properly? In our testing switching to the DShow engine behaved identical to earlier versions of SONAR. The code has a few fixes but otherwise is pretty much the same as before. So unless we have a bug you should not see different behavior. A couple of things to check - make sure you are doing the ini setting exactly as outlined in the article. Also keep in mind that you need to reload config defaults and then close and reopen the existing project or restart SONAR. i.e. Once a video is loaded in with the MF engine it won't switch. You can tell which engine is being used for a project by going to the first tab in the video properties. 
If you are still having trouble after this please log a bug report with a link to a sample video that shows this problem. The problem as you describe is very unlikely to be related to codecs on your system since if it worked in X3C it should continue to work in DShow.

Noel Borthwick [Cakewalk]

markyzno
 
One thing I have noticed as it goes with OMF's in Sonar is that Sonar wont read fades on clips  whereas Pro Tools does. This would be a nice feature in Sonar as currently I have to unpack the OMF in PT and then export the stems / tracks into Sonar and work from there. Slightly annoying... I'll fire in a feature request.

We could implement clip fades - however they won't necessarily sound exactly the same as what they did in PT since their curves won't match ours exactly. Feel free to log a request however.
 
Did you resolve your issue with video's not loading properly? In our testing switching to the DShow engine behaved identical to earlier versions of SONAR. The code has a few fixes but otherwise is pretty much the same as before. So unless we have a bug you should not see different behavior. A couple of things to check - make sure you are doing the ini setting exactly as outlined in the article. Also keep in mind that you need to reload config defaults and then close and reopen the existing project or restart SONAR. i.e. Once a video is loaded in with the MF engine it won't switch. You can tell which engine is being used for a project by going to the first tab in the video properties. 
If you are still having trouble after this please log a bug report with a link to a sample video that shows this problem. The problem as you describe is very unlikely to be related to codecs on your system since if it worked in X3C it should continue to work in DShow.

To be honest Noel I just rolled back to X3c as that was working perfectly for me (I love X3c), so when i'm in the mood for a good ole thorough tinker and I dont have a project on I'll move on to D again and report back my findings.

I did do the above amends to the .ini file yesterday to no avail I'm afraid and until the export options are a bit clearer for the video export I am pretty reluctant to switch away from my workflow of using Premiere to remarry my audio with the picture to send to clients.

As far as the clip fades were concerned and the OMF, what I was talking about was an editor sends me an embedded OMF exported from Final Cut Pro, Sonar opens the OMF just fine but doesnt read the fades on the audio clips whereas Pro Tools does. This is mission critical to me as usually the dialogue tracks amount to hundreds of clips and if I just used Sonar I would have to re-implement all these fades on the clips which takes hours and hours. Sonar reading fades on clips after unpacking an OMF would be immensely useful.

Sorry if I came across a bit gnarly yesterday but I was pretty dissapointed in the update. Its nice to see Sonar moving towards video but I feel its a bit half baked for my professional needs at present. of course I would be more than happy to test X3D further but only when I havent got a project on the go.

So as far as I can see (as an outside observer) there are no reproducible bugs at present I guess...