-
1. Re: Vanishing Point - Operation Could Not Be Completed
Chris Cox Jun 9, 2009 1:53 PM (in response to craig cheatham)Does it really stick to the file? Something might be corrupt in the metadata that VP adds to the image.
Could you send me a sample file (or two) that shows this?
-
2. Re: Vanishing Point - Operation Could Not Be Completed
craig cheatham Jun 9, 2009 4:31 PM (in response to Chris Cox)I really would appreciate it if you could look at this file and we could start to sort out the issue. At the moment this project is proprietary. When it goes public in a few weeks I can send you a copy of the file, but I can't put it in the forum. I'd need an ftp address.
Yes, the problem sticks to the file. As a test I just moved the file to another computer and tried VP, same error.
Since this is an intermittent prob, I can't lay my hands on another file with the same issue at the moment.
Thx,
Craig
-
3. Re: Vanishing Point - Operation Could Not Be Completed
Chris Cox Jun 10, 2009 11:04 AM (in response to craig cheatham)Just contact me at ccox at adobe {dot} com.
-
4. Re: Vanishing Point - Operation Could Not Be Completed
craig cheatham Jun 11, 2009 11:16 AM (in response to Chris Cox)Thanks Chris.
-
5. Re: Vanishing Point - Operation Could Not Be Completed
E Diane King Aug 7, 2009 6:46 AM (in response to craig cheatham)Was anything figured out regarding this problem? I am also struggling with the error. I would like to create a VP template to use over and over again, but after the first transformation the file errors out no matter which computer/ Adobe version I open it in.
-
6. Re: Vanishing Point - Operation Could Not Be Completed
Richard Hudd Aug 14, 2009 7:02 AM (in response to craig cheatham)No solution yet, then!
As Craig Cheatham suggests, I think that this is a program bug, made worse by a meaningless error message. I do not think it has anything to do with corrupt files. Also, it is not specific to Macs - it also happens in Windows. I encountered it on a Vista machine with 4 CPU cores and 3GB of RAM.
In my experience, the first context when the error can arise is when you try to copy OUT from a Vanishing Point window if the block that you marquee is 'too big' - which you may not think is very big at all - about 4 megapixels of an 8-bit (24-bit) colour file was about what it could manage in my case. When this happened to me, I started at about 8 megapixels and tried again with progressively smaller blocks, and it worked.
If you then succeed in pasting the block INTO a destination VP window (not a foregone conclusion, as that might fail as well) you may have trouble if you try to transform it. (In my experient, all I was doing was scaling it.) The first, second, third, etc., transform might work, maybe ten do, and then the next transform does not, and then the next does not, and so on. But quite often, if you hit it lucky - e.g. reduce the block's size enough (making it bigger never seems to work), or by the right amount, or whatever mysterious thing its takes - it might start working again, at least for a few more transformations. After a few rounds of this, though, it seems to lose its grip completely and the error becomes permanent. There is nothing then to do but hit 'cancel' and start again.
I was a system software writer for may years, and that gives you a nose for bugs. I'd say straight away: 'they have messed up the memory allocation'. You really can't tell, and this may be wrong, but it's what it smells like. I'd guess wildly that some clever scheme is in place for managing the blocks of RAM that they are using to carry out the tasks, and they have programmed it wrong. (The first mistake seems to have been not allowing enough RAM for a basic copy of the source.) When you start transforming, it looks as though some different, but doubtless closely related, problem cuts in.
There's additional evidence for RAM problems. Vanishing Point works better with 8-bit colour that with 16-bit. It still fell over when I tried it, but not as soon, and you can use bigger blocks. This is what you would expect, as the memory needed is smaller.
I am glad that Craig only suffers from this problem with a quarter of his files. For me it affects everything I want to do at the moment and the VP facility might as well not exist. I do hope they fix it - and make it available.
If anyone wants the files, let me know.
Richard
-
7. Re: Vanishing Point - Operation Could Not Be Completed
bonanza3 Sep 11, 2009 2:41 PM (in response to craig cheatham)I have the same error on a Core i7 computer with 6 gb of RAM and an ATI Radeon HD 4800 Series graphics card. I'm running Windows Vista 64 bit operating system. Here's my work areound:
Before using VP, save then duplicate your image.
Run VP on the duplicate as many times as you need to or until you get the error.
Duplicate the VP layer.
Create a new blank layer below the duplicated VP layer.
Merge the duplicated layer down into the new blank layer.
Duplicate the merged layer and specify the original image in the location drop down box so the merged VP layer is in the correct location.
Pitch the duplicate image -- or hold onto it until you are sure you won't want it.
I know this sounds weird or at least unnecessarily complicated and you lose the grid you created (I haven't tried exporting that), but it does work. I tried just duplicating the VP layer directly and also duplicating a copy without merging it but neither worked. Not the most elegant solution, but I hope it helps until this gets fixed!
-
8. Re: Vanishing Point - Operation Could Not Be Completed
bonanza3 Sep 11, 2009 3:07 PM (in response to Chris Cox)Hi Chris
I can send files if you need them. They're pretty big, so I can either transmit through an upload or downsize them -- I don't think changing the resolution will affect VP.



