[Mike Janowski]

Well damn, better late than never to the party.

Thanks, Nick, I always wondered why simply copying a project in one fell swoop messed up the affiliate relationships. Now I know.

[Mike Janowski]

Thank you, Chris.

You’ll be happy to know that I forwarded your post about installing QT for Windows to my programming team, to forewarn them, as they were beginning to investigate the Quicktime APIs for possible use. Just about all of our clients are Windows-centric, and most of them don’t have QT. In fact a point of pride (not to mention marketing) with this product is that we’ve developed it to work without – in many cases, in spite of – in-house IT departments. So installing something seen as invasive, like QT, is probably a no-go.

My first move is going to be to re-do the compressions using more keyframes. And to learn more about GOPs vs. performance. Or at least forward the info to someone who actually understands it!

[Mike Janowski]

Thank you for your response.

And the reason I post the data about the system is to head of useless speculation like the last part of your answer, to whit:

Perhaps your computer is not capable of playing back the HD content you have created.

It is. Playback anywhere is not the problem. Accurately finding looping points is.

I own Digigami – thanks for the heads-up about its HD capability – and though I think it does an excellent job of making MPEG1 compressions, it too has problems interfacing with our software engine. I’ll try it again…

Finally, though I may have mis-quoted or mis-understood our programmer, an short declarative like “He’s wrong” really doesn’t provide me with the detail I need to solve this problem. I appreciate that you’re busy and don’t know me from Adam Ant, but if you’re gonna waste your time answering, make it worth both our whiles.