Finally had a project, found cripple-ware and a crash
Posted: Sun, 23rd May 2010, 7:09am
Post 1 of 6
Well, I'd been saving the demo download I had of VisionLab for a while now, waiting until I had a real project to do so I could actually exercise it and test it out. I hope you can imagine my disappointment when I realized it wasn't a demo version at all, but cripple-ware.
Why do this? Do you realize the only people it hurts? The honest people who refuse to install cracked/pirated versions of software on their machines. Everyone else will just find a way. And you are mistakingly thinking you're selling software... you're not, you're selling service and support; and this software seems to have some of the best. Why refuse to allow honest people a chance to really use it before they throw out $500+ ? Especially when you allow people to register online for the forums with serial #s, just don't provide support for a product unless they have the little icon.
For now, I will find a product that doesn't assume I'm a vagrant to do what I need I guess. When I finally have some time to just play with something as much as VisionLab requires for no particular reason, I'll explore it some more. If I can get this problem resolved:
I have an easily reproducible crash with it. A pretty basic windows 7 64bit installation. I have 7.6.6 of Quicktime, which according to the 'clean install' thread link is the most recent. I have the latest DirectX installed, the February SDK; I'm working on a plug-in for Vegas, so I know that part is recent. And as far as un-installing/deleting, this was freshly installed today so that is about as clean as one gets.
The problem manifests itself consistently when I right click on the track window and select 'Apply Preset' and click on a few choices, frequently only one or two is required. The error displayed is simply "Macromedia Projector has stopped working".
I'd really like to get this resolved, as I do _like_ the VisionLab product and the forum/support especially and will play with it when I have time to waste.
Posted: Mon, 24th May 2010, 8:57am
Post 2 of 6
'Cripple-ware'? I don't quite follow your post, I'm afraid. The demo is fully functioning, the only limitation being the watermark. You can use it for as long as you want, though, and the features are all there to be tested and tried out.
Do you get this error if you right click the VisionLab shortcut and choose 'run as administrator'?
Posted: Wed, 26th May 2010, 4:28am
Post 3 of 6
Cripple-ware is defined as something that has crippled functionality. This is a VFX rendering app, the rendering is (for almost all intents and purposes) crippled, and that's a pretty key component.
Time limiting these things is a necessity, obviously. But anything more is just encouraging people to find "alternative methods".
I don't know how other people evaluate software as creative and complex as this, but I sit down with something I need to accomplish, and accomplish it. I just don't have the time to "play around with it" with the kind of depth and extent that an evaluation would require. But not being able to use what I've accomplished means it would be just that, time spent playing around. Some specialized functionality (such as the editing presets) missing is understandable, but the core work-flow should be unhindered.
For the time being, I've found the CS5 After Effects is a proper evaluation version, only without the third-party add-ins, so I'm using that. It does have so much in it, it might be worth the extra money; I'm just not sure yet. When I have a chance to just play around I will spend more time with VisionLab and try and get a feeling for it.
However, not being able to run it is a problem. so on to that issue.
I tried running it with "Run as Administrator" but it made no difference. I uninstalled it (removing all Documents and AppData content) and tried the first run as Admin, but the same result. FWIW, I've noticed (but not rigorously tested) that it seems some presets, "Warmish" for example, seem to crash consistently, while others don't (I think).
I would like to get this resolved, cause as I indicated, one buys the community/support as much as the software, and I like this one. Let me know if enabling the debugger and providing anything else would be beneficial.
Posted: Wed, 26th May 2010, 8:17am
Post 4 of 6
The watermark demo method is one we've used for about 10 years now and haven't really ever had any complaints about it. I'm sorry this isn't the case for you. I should note that the demo isn't time limited at all, though.
Do you only encounter the error when using the 'Apply preset' option? What happens if you try to apply presets from the Effects browser? For example, if you go to the Grade Object and apply the Warmish preset that way?
Posted: Thu, 27th May 2010, 2:51am
Post 5 of 6
I realized it's not time limited. I guess for me, the effort I put into evaluating something, I expect to be able to use what I was working on. This programs are complex, and everyone's tastes are different. You only get to know it but really using it, and that takes time. I'd just rather spend that time productively, which I can't in this case.
I'd much rather have it time limited so I can sit down and use it intensively/exclusively for 30d and then be able to decide, than have it available for months but not able to do actual work on it.
However, on to my issue.
Choosing Warmish (and any other it seems) from the toolbox window works OK. However, I started clicking the "Info" icon in the presets, about 5 worked, then Warmish again caused the same crash.
I should note, I've had the same error before on rendering, just it happens much less frequently there.
And, all these tests are on the examples provided. Although the problem occurs on my own MiniDV imported footage also.
Thanks for you help Tarn, hopefully we can figure this out.
Posted: Mon, 7th Jun 2010, 8:51pm
Post 6 of 6
ChillyZebra wrote:I realized it's not time limited. I guess for me, the effort I put into evaluating something, I expect to be able to use what I was working on. This programs are complex, and everyone's tastes are different. You only get to know it but really using it, and that takes time. I'd just rather spend that time productively, which I can't in this case.
One note on this; if you put a lot of work into a project and you decide to buy the software, you can use your project from the demo in the full version, so you don't end up wasting your time.
Read this knowledgebase article for more details:Will projects I saved in the demo open in the full version?