Tweet
I've been following the threads here and elsewhere and have also been trying it myself with minor pseudo-projects. I'll make the following comments from my own and others' experiences:
1. DV Out: this seems to be the biggest complaint. I've tried it with my DVCAM tape deck and had no difficulty in recording back a DV file. On the other hand, I could not send a signal out through my ADVC-100. I never tried before installing 6.51a, so I don't know whether this is new. However, it seems clear that something must have happened to the signal, from others' comments, that simulates a Macrovision protection, and this may well be what is happening with the ADVC-100 because the deck is obviously receiving a good signal from the DV interface card. Doc's registry tweak made no difference.
2. I've seen 2 posts and have experienced the same thing myself a couple of times. You are doing things (in my case editing) and the window just disappears, no warning, no error message, just the desktop. It is possible to restart the app and carry on, although the error recovery feature does not seem reliable (one report stated lost audio requiring a complete project re-render to bring it back). In my case, as I have automatic save every 10 minutes, I just restarted the DVP file without problem.
3. One post reported that it was necessary to delete the ini file for anything to work. I did this myself after installing it, because scrubbing didn't work, although other things did.
4. One post reported jerky previews, but I haven't noticed anything specific. I don't think that it was stated whether "Instant" or "Quick" was on. I use neither, as a rule.
5. One person complained that there was incompatibility between the new codecs and a third party plug-in (ViZfx, I think, whatever that may be), but this may be O/S dependent. One person reported getting it working under XP after a complex re-install procedure.
6. These problems seem a priori to be independent of hardware (CPU type, graphics card, etc) or O/S (at least 2000/XP). However, they may have some relationship to DirectX version (I use 8.1 except for the beta 9 DV codec). This is rarely reported.
7. I've been astonished at the arrogance of certain parties who happen to have had no apparent problems and who refuse to admit that others may have had, putting all the blame on the individuals, rather than the patch. This was, IMHO, inadmissible. I thought I had the monopoly of arrogance here
My purpose in this long and difficult message is to try to crystallise our thoughts and to appeal to those with problems to help us find the common points behind them. For that, we need to have the co-operation of those without problems, as well, to act as a control. If we can collect facts, the we can tell Ulead what the problems really are. Let's start by seeing whether all those with problems are use DX 8.1 and with which O/S. In my case 8.1 with W2k SP2. Do others with 8.1 and W2k or XP have or have not these problems and do any with other versions of DX have or have not them?
1. DV Out: this seems to be the biggest complaint. I've tried it with my DVCAM tape deck and had no difficulty in recording back a DV file. On the other hand, I could not send a signal out through my ADVC-100. I never tried before installing 6.51a, so I don't know whether this is new. However, it seems clear that something must have happened to the signal, from others' comments, that simulates a Macrovision protection, and this may well be what is happening with the ADVC-100 because the deck is obviously receiving a good signal from the DV interface card. Doc's registry tweak made no difference.
2. I've seen 2 posts and have experienced the same thing myself a couple of times. You are doing things (in my case editing) and the window just disappears, no warning, no error message, just the desktop. It is possible to restart the app and carry on, although the error recovery feature does not seem reliable (one report stated lost audio requiring a complete project re-render to bring it back). In my case, as I have automatic save every 10 minutes, I just restarted the DVP file without problem.
3. One post reported that it was necessary to delete the ini file for anything to work. I did this myself after installing it, because scrubbing didn't work, although other things did.
4. One post reported jerky previews, but I haven't noticed anything specific. I don't think that it was stated whether "Instant" or "Quick" was on. I use neither, as a rule.
5. One person complained that there was incompatibility between the new codecs and a third party plug-in (ViZfx, I think, whatever that may be), but this may be O/S dependent. One person reported getting it working under XP after a complex re-install procedure.
6. These problems seem a priori to be independent of hardware (CPU type, graphics card, etc) or O/S (at least 2000/XP). However, they may have some relationship to DirectX version (I use 8.1 except for the beta 9 DV codec). This is rarely reported.
7. I've been astonished at the arrogance of certain parties who happen to have had no apparent problems and who refuse to admit that others may have had, putting all the blame on the individuals, rather than the patch. This was, IMHO, inadmissible. I thought I had the monopoly of arrogance here
My purpose in this long and difficult message is to try to crystallise our thoughts and to appeal to those with problems to help us find the common points behind them. For that, we need to have the co-operation of those without problems, as well, to act as a control. If we can collect facts, the we can tell Ulead what the problems really are. Let's start by seeing whether all those with problems are use DX 8.1 and with which O/S. In my case 8.1 with W2k SP2. Do others with 8.1 and W2k or XP have or have not these problems and do any with other versions of DX have or have not them?
Comment