I have a project where I was given jpg's to work with. I know, I know. I broke a cardinal rule by not converting them to tga files before import into Edius. Now Edius shows them as missing when I've reopened the project. The restoration box shows them in the correct location but when I try to complete the restoration, the "open" button is greyed out and the file cannot be restored. Is this a bug, or is there some nifty work around for this?
Announcement
Collapse
No announcement yet.
Restore Jpeg not allowed?
Collapse
X
-
Select the all shft click and point the restore to the folder. It will search the folder and restore them.
No need to transfer to tga. We use them all the time without any problem.Steve
EDIUS Trainer, Grass Cutter Gold
A proud EDIUS EDITOR
For more information on the Grass Cutter program please visit: http://www.grass-cutters.net
-
Originally posted by SRsupport View PostSelect the all shft click and point the restore to the folder. It will search the folder and restore them.
No need to transfer to tga. We use them all the time without any problem.
Comment
-
I am not directing you to restore them at file level. In the restore box you have folder. Tell the restore dailogue to use folder not file. That way your not opening them (restoring them file by file) but telling the restore to look in the folder.
Can your try that?
@your picture that is so not what I am telling you to do.
when the restore comes up
1 shift select all the pictures that are off line in the restore box
2 go to restore method choose RELINK SELECT FOLDER
3 you'll see a different picture then the one you posted
4 choose the folder
5 look if edius restoresLast edited by SRsupport; 08-04-2007, 07:55 AM.Steve
EDIUS Trainer, Grass Cutter Gold
A proud EDIUS EDITOR
For more information on the Grass Cutter program please visit: http://www.grass-cutters.net
Comment
-
Originally posted by SRsupport View PostI am not directing you to restore them at file level. In the restore box you have folder. Tell the restore dailogue to use folder not file. That way your not opening them (restoring them file by file) but telling the restore to look in the folder.
Can your try that?
Comment
-
Ok copy the folder and put it on the root .
Then try the restore from folder.
If that doesn't work rename the folder (on the root) and try restore select folder again.Steve
EDIUS Trainer, Grass Cutter Gold
A proud EDIUS EDITOR
For more information on the Grass Cutter program please visit: http://www.grass-cutters.net
Comment
-
OK then I'll have to see If I can reproduce it. Unfortunately I don't have edius on this notebook.
One suggestion go to the auto save folder at open the project 1 version before the one you have problems with now. The back up also has copies. At least you can get up and running then.
Sorry that we could not solve this :)
SRSteve
EDIUS Trainer, Grass Cutter Gold
A proud EDIUS EDITOR
For more information on the Grass Cutter program please visit: http://www.grass-cutters.net
Comment
-
If file sizes don't match Edius won't restore.
We all want Edius to be less strict about that. ( for now it is very strict)
If you had the jpegs bigger and you did something that changed the file size you have a problem. Well let me be clear on that: It was a problem at some point I'm not 100% sure it changed.
SRSteve
EDIUS Trainer, Grass Cutter Gold
A proud EDIUS EDITOR
For more information on the Grass Cutter program please visit: http://www.grass-cutters.net
Comment
-
Yeah. I've been with Edius since version 1. I've been held hostage in the past with projects that demanded the exact original file. I didn't change any sizes. One more thought though as I rack my brain, I did do a system restore a day ago to a point before the project was created. Could that have any bearing?
Comment
-
The restore was not to any time before I installed Edius. In fact, I've been waiting to update directly to 4.5, so I 've been running the same version for quite a while without any problems. I uninstalled completely twice, with registry edits and still had the same problem. I finally updated to 4.24 and the problem disappeared. Thanks for the tip.
Comment
Comment