orizaba
-
Posts
503 -
Joined
-
Last visited
Posts posted by orizaba
-
-
Hi Dave,
But that's not what's actually happening. You are not returning "the image," you are zooming out the zoomed-in image until the original (which is the only image actually stored inside the program) is displayed. The image after the zoom in and return to regular 100% size (assuming you began with the original) is the "identical" image you started with. All intermediate images are math computations derived from the original. When the zoom is returned to 100% the original is again displayed. The original is never actually changed in any way. Likewise with Photoshop. Photoshop loads your original and any zooms out or in have no real essence until a save is done. The original remains as you loaded it unless you overwrite.
Dave, from a programming perspective inside both PTE and Photoshop and other image editors other than Photoshop are electronic "pointers" referencing the original file. This is how they know where it all starts and/or ends. So when zooms are done and the pixel dimensions reference the original, the actual original is returned as the value.
Best regards,
Lin
So, this clears my only doubt (as per my last post).
Thanks,
Jose
-
Lin,
I am not sure that the Photoshop example is correct? If you make an image 150% bigger you are introducing intermediate pixels. If you then return the image to 100% I am not sure that you would necessarily lose all of the exact pixels that you gained in the upscaling process?? Something to think about?
DG
DG, Lin and Xaver,
Thanks so much, all of you understood my question quite well, and now everything is clear for me!
I mean... almost...!
Regarding PTE methodology, as DG and Lin explained, things are quite clear for me and I agree: no degredation. Period!
But this last post from DG, concerning Photoshop process...
Does this mean that Photoshop does not follow the PTE process? Always using the original picture?
I do not work with Photoshop, so I am away of this problem, but I would find curious (at least) that Photoshop use "a less clever process" than PTE! Even beeing PTE not an image editor.
Regards,
Jose
-
Jose,
Since the same image is zoomed in and out to whatever percentage is required and is never saved how can there be any degredation?
The deciding factor is the percentage zoom at any moment in time i.e. if the (overall) zoom percentage is 150% (given a 1920x1080 image in a 1920x1080 project) then upscaling is taking place but when the zoom percentage is returned to 100% (overall) then the upscaling ceases and the image is represented pixel for pixel.
Downscaling is always preferable to upscaling and Igor said (a long time ago) that PTE is better at downscaling than upscaling.
If you can determine the (overall) zoom percentage that an image is going to be subjected to then it is possible to calculate the exact pixel dimensions to size the image at in order to gain maximum efficiency in terms of project size.
Or you can do as some people do if their computers are powerful enough - feed it with full sized 36Mp Jpegs at the highest quality - you can't do better than that :rolleyes:/>/>.
DG
DG,
Thanks for your explanations.
Anyhow, I think I am not still convinced...!
You say "... zoomed in and out to whatever percentage is required and is never saved how can there be any degredation?"
This is the point:
You zoom in. Result is "degredation" (even if you don't save the project at this time), is this so?
After this, you zoom out (even to the original percentage). Image which will be zoomed out is not the original one, but it is already a degretaded one instead, is this so?
I say this because PTE (and almost all video editing softwares) execute successive "operations", one after the other, according to "up-to-down" order, is this so?
This is my doubt... Can you clarify?
Of course, I always use original picture size (36Mp), but problem (and doubt) above still exists.
Regards,
Jose
-
Jose,
The "What's New" for v7.5 made no mention of Unsharp mask. However, the "What's New" document for v7.0 had this to say:
"Unsharp Mask for Sharp Picture
This feature dramatically increases sharpness of picture. PicturesToExe adds unsharp mask for entire screen in real-time, even for slides with animation."
I interpret the statement "...even for slides with animation" as meaning that unsharp mask is applied to each rendered frame.
regards,
Peter
Peter,
Thanks.
I had never tried to apply Unsharp, neither to slides nor to video.
Just now, I applied Unsharp = 200 (maximum) to video and difference is great!
Such video is an old Hi8 video, which I digitalized (AVI file).
Original quality in terms of sharpness is not so good, mainly when we are already used to Full HD quality... so, this Unsharp Mask helps a little bit to quality image.
Regards,
Jose
-
Jose,
Have you done a test to investigate? In the attached, do you think the third slide is the same quality as the second?
regards,
Peter
Thanks Peter,
In your example, in a first glance, I can not really see any difference.
I never made a test like yours, in order to compare.
I just should like to know, under a pure technical point of view, if there is any reason for a quality degradation.
I compare this situation with audio hi-fi:
Human ear can detect a maximum 20 KHz, however, we can not notice any difference between 19 Khz and 20 KHz, but difference is really there!
So, I insist: what happens with PTE? Is there degradation or not? Even if we can not notice.
Regards,
Jose
PS: By the way: does "unsharp mask" (in Project options) apply to video, or only to pictures (slides)?
-
Just a question:
1. As an example, let us suppose we have a slide (or video). In O&A it is with zoom = 100.
2. Let us put it inside a Mask Container, beeing this with zoom = 70
3. Let us put this Mask Container inside a Frame 1 with zoom = 200
4. At last, let us put this Frame 1 inside another Frame 2, with zoom = 120
5. Let us "imagine" that final result for the slide (or video) is an "equivalent" zoom = 168 (just an example).
My question is:
- Is the final image quality 100% equal to the quality we would obtain if we would apply only one zoom = 168 directly to the slide (or video)?
- Or, each time we apply a zoom (mainly a zoom in, as I think) picture quality is reduced?
- This point has to do with usual down sequence processing of several effects (from top to bottom).
So, I think that quality reduces each time a zoom is applied, I mean, PTE does not process a sort of "counter balance" of successive zooms.
Is this so?
Jose
-
Hi Jose,
I don't know if this might be useful to you as a temporary work-around or not. I just made a show which runs 96 different separate videos simultaneously, and duplicates this five times plus a six video rotating, zooming cube all running on a single slide. That's a total of 486 simultaneous videos on a slide.
Since your final project will be in a video format, you might proceed like I did. I never added more than 12 videos at a time, then I created a MP4 h.264 video, loaded it as the project and added another dozen videos, and repeated this process until I had the initial "video wall" built. Then I loaded this video wall (as a video) five times to create my Video Room and created yet another MP4 h.264. Then I added that as a project and created my rotating video cube and once again saved as an MP4 h.264.
By doing this in increments in an iterative fashion, I was able to avoid out-of-memory issues and the finished show actually runs pretty good as an executable as well as a video.
If your project can be created in this fashion, you might get on with it while Wnsoft is working on the errors. Just a thought...
Best regards,
Lin
Hi Lin,
Thanks for your help.
By the way, do you really think that WnSoft is working on this...? I am not so sure, as per their silence!
I think I understood your solution and, as a matter of fact, that is exactly what I have done with my project in order to overpass the situation.
However, it was a lot of stupid work because project was not thought for that from start.
After such project I already made another one including lots of video as well, and I structured it from start for this purpose, which made things a lot more easy.
However, I insist: WnSoft made possible the use of video (even Full HD video!) in the projects, what is of a great interest indeed! But Full HD demands a lot of memory and processing. I think that WnSoft should have made a 64-bit native software at the same time in order to allow, in an effective way, the use of video.
As I said before, they have a pitbull inside a caniche case...
In relation to this, did you ever noticed that "publishing" HD H.264 mp4 files is not possible when included video is very large?
I mean, I had a 51 minutes AVI video (PTE converted), 2 GB, and tried to publish. MP4 resulting file is truncated after 14 minutes!
It happened several times, truncating at diferent times.
Solution: divide the video in several slides (around 13 minutes video each) and publish several mp4 files.
Then, using YAMB 1.6.0, I joined all mp4 files (no recoding).
Thanks again and regards,
Jose
-
Jose,
Do not worry, my previous post is not an answer to freezing, crashing and other bugs. It was just a suggestion how to make your slideshow faster. I didn't know your final goal is mp4 file, not exe; in this case my suggestion might be irrelevant.
Regarding those bugs, as I said, we're working on them.
Artem
Artem,
Still "working on them"...?
It must be a big, big bug!
Jose
-
Jose,
I've noticed you have a lot of independent (not linked) video clips inside one slide, but the source file for them is the same. Are you aware of 'link video clip' option? It can greatly increase performance in such cases. For more details, see User Guide, pages 48-49.
Anyway, having tens of video clips inside one slide will make your slideshow really slow. Try separating them into several slides.
Artem
Hi Artem,
I hope that this is not your answer to freezing, crashing, unhandled exceptions, "D:Wnsoft" and other error situations which I am dealing with.
In fact, I am aware of "link video clip option" but I am not using it because, from User Guide, video objects (on one or several slides) linked with
one video track share common parameters: Start time, Duration, Offset, Mute audio.
As you may have noticed, my "not linked" clips have diferent start times, diferent durations, diferent offsets, besides the fact that in some of them I use their own audio and "mute" in others.
So, in general, I can not use this option.
Yes, I can imagine that having tens of video clips inside one slide is hard for the computer, despite the fact, as you may have noticed as well, that I am using the smallest possible video segments (not the full original video track). I get such segments from the original video using my video editing software.
Separating/spliting, that's what I am doing now, whenever adequate and whenever possible, but it's not so easy, as my final goal is to produce a final mp4 file of the whole project, not to show the project using the "enchaining method". So, such spliting, originating several mp4 files, forces me to use again my video editing software in order to join the pieces.
At last, I would say, PTE would make it possible to build more complex projects if it was a native 64-bit program using all own 64-bit resources. That's what I am sorry for in present moment.
In the meantime, I keep waiting for your support related to all ERRORS occuring.
Regards,
Jose
-
I have wondered if the D reference is to the D drive on a WNSOFT computer and not the user's computer.
Maybe that's why the error comes up?
DG
My computer has 3 HDDs:
Disk 2 (1TB) with 4 partitions: C, D, E, F
Disk 1 (2TB) with 3 partitions: G, H, J
Disk 0 (2TB) with 1 only partition: K
XP and PTE (and other programs) installed in "C".
My PTE project now running on "E" from clean. When problems started it was running on "K". Problems continue on "E".
- DG - What, or how, could be a WNSOFT computer?
I think that "D" reference reports to my computer (user's computer).
- potwnc - In "D", no directory at all called Wnsoft neither nothing related to PTE. Amazing!
With my project running, Task Manager Processes only show 1 "PicturesToExe.exe" (not PicturesToExe.exe *32)
What kind of problem could be with my XP ("putting" some PTE files in an invisible local in "D")?
- Tom - When working in my project I save as it several times a day.
Now I am in "version" PTE 543-2.pte, meaning "Part 2 (after splitting), 542 previous savings as".
So, project name is always changing.
Anyhow, I will try to see about these wptypes.pas error message in older forum postings.
- nobeefstu - Today I opened a support ticket in PTE SUPPORT and I sent link to download my PTE project, Part 2,
and some thumbnails of error messages over my frozen project.
I asked them to go to this topic/thread and take good noticed of what I am saying from day one,
instead of asking questions which may be already answered.
Yes, if PTE has a project debugging tool, this could be nice and quick.
Let us see what happens in the next 24-48 hours!
By my side, working on solutions you suggested, it's too much hard and anoying...
and at this moment I am not in the mood, on the contrary.
Since more than 3 weeks that I can not work in peace in my project. Too much!
- Gary - You refer that your error came when trying to save the EXE file over the existing EXE file.
If I understand, such EXE file is the executable file, is it?
Point is that I never produced any EXE file of my project, I only am saving as successive ".pte" files.
So, may be your situation does not apply to my case.
What was I doing when first crash occured?
It was, of course, before spliting the project into Part 1 and actual Part 2.
Part 1 is most complex (I have saved it and already made final mp4 file).
Part 2 is not so much complex, so I splited here.
But, before spliting, I mean, before errors started, one day I added 1 more picture somewhere in Part 2.
A JPG picture, 2,38MB, big format (see former posts).
Problems started. I have already changed such picture several times from new (I am now in version 5) but problems continue.
I "refuse" to resize this picture or low down the JPG quality. I need it as it is.
- LAST MINUTE - Using O&A, I just removed such big picture from my project and tried to run the project.
Freeze and crash at once!
First, came the old OUT OF MEMORY ERROR, then a new one (thumbnail attached).
Thanks very much to all of you for giving me your time and thoughts.
Jose
-
Just installed PTE 7.5 from new.
Another error message show, while running my project:
APPlication Error
Exception EoutOfMemory in module PicturesToExe.exe at 000A305B
This time, no reason for an Out of Memory problem, I think, as I had run the project several times in the timeline and didn't add nothing.
In any case, v7.5 seems to show more difficulties to run the project than v7.0.7.
This situation is turning quite impossible to deal with.
If this was my very first PTE trial, PTE had already been in the recycle bin forever.
But I hope to recover my confidence...
-
Today, a new Error message, after the first one concerning the "562 line":
PicturesToExe
Access violation at address 006620C4 in module "PicturesToExe.exe"
Read of address 00000000
I tried to send a link to Igor but he can not receive more private messages.
I hope Igor can see this.
-
Jose,
Have you tested this project with v7.5 current release to see if the same issue exists ?
* Bug fixes usually apply to latest current version, as older versions are a thing of the past and dont warrant further bug fixes.
* Its quite possible your project file has become corrupted since your PC is constantly Out of Memory while working/saving this project. If thats the case ... then the project file will also most likely not work correctly in v7.5 either.
Yes, I've tested it with actual 7.5 and problem still exists.
A detail: running the project in v7.5, I noticed that some (at least, one or two) photos show with small differences in terms of framing, I mean, as if a different zoom has been applied, which was not the case. Very misterious!
Yes, may be the project file got corrupted. If it is the case, is it possible to locate the corruption in order to fix it? What is the solution in such cases?
I don't consider v7.0.7 a thing of the past. On the contrary, new v7.5, as I see in the Forum, still is not 100% reliable, as is normal.
Thanks for your time.
-
If you mean the .PTE file then right click it in Windows Explorer & Open With Notepad.
This will show you the text contained with the PTE project.
Jill
Thanks Jill, it's exactly this, I've forgotten.
-
I can't say for sure whether this is related to the 32-bit/out of memory problem you've had before - we'll have to wait for Igor to return. But line 562 does not mean line 562 in your project (.pte) file. It is a line in the code of the PTE program (or one its the modules) that hasn't been coded to handle some error condition you've encountered. Igor will probably want a copy of your project so please back it up for him as soon as you can so he has the best chance of recreating - and fixing - this.
Do you have PTE 7.0.7 installed to your "D" drive?
No, my PTE 7.0.7 is installed in "C", as usual.
In "K" I have everything related to my project, folder by folder, and one only folder containing saved PTEs, audio (mp3), and all JPG pictures and PTE converted movies which ara part of project.
And I have already re-installed 7.0.7 from new several times.
This is not understandable!
Do you know how can we see the "list" of "orders" which constitue the PTE project? I think that some years ago I could see it, now I can not remember.
-
Windows XP SP3 32-bit
4 GB RAM
Clean Registry
Defragmented HDDs
No virus, no malware
PTE 7.0.7
Minimized video card usage
Working on HDD "K"
More than once PTE freezes and a message comes:
PTE
Unhandled Exception at "TPteEngine" Disposing
(D:\Wnsoft\PicturesToExe\PTE\WnLib\Win32\wpTypes.pas, line 562)
I think it refers to HDD "D".
Point is that HDD "D" is a physical different disk from HDD "K" where I am making my PTE project.
In HDD "D" I have nothing related to PTE or my project, not even to any other PTE project.
So, why something is going wrong with HDD "D" in order to freeze my actual PTE project in "K"?
How and why PTE "gets in touch" with "D"?
I remember that there is a way in PTE to see all the project line by line.
I tried to find such mode but I couldn't.
The idea was to find such line 562, but I couldn't.
Concerning the OUT OF MEMORY past problem, I splitted my project into pieces and am working now almost slide by slide.
Much annoying!
Anyhow, I succeed working for 30 minute's periods, than FREEZE, REBOOT, start again, and so on...
No way!
Someone has an idea what is going on?
Thanks,
Jose
-
Here's another reason for a 64-bit PTE (and an example of the trend for PTE's competition). I use Sony Vegas Pro version 10 for all my final video editing/rendering/authoring to DVD and Blu-ray. Sony just released version 12 and I would like to upgrade. However (from Sony's web site): "64-bit operating systems are the best choice for high-end performance. By focusing exclusively on 64-bit operating systems, Vegas Pro 12 overcomes many of the limitations of legacy 32-bit software/hardware architecture, enabling users to enjoy superior performance and improved stability for memory-intensive projects and formats." In other words the product is no longer available as a 32-bit application.
I just confirmed that the virtual AVI output from PTE 7.5 cannot be read by Sony Vegas Pro version 10 64-bit edition. I'm quite sure the same would be true for version 12. All of which means if I upgraded to version 12 I would have to stop using PTE - not a wise move!
Another member, today, in another thread, found himself in the same OUT OF MEMORY situation with his PTE 7.5 on Win7 64-bit, so I understood.
Suggested solution was to split his project in smaller parts.
That's what I am doing, but each time I do it I can't avoid to claim against this 32-bit PTE version.
I think that Igor and his team, despite beeing the brilliant authors of this fantastic and unique software, still didn't really get the enormous potentialities of PTE.
Because, it's my opinion, if they would, the native 64-bit version would be already under way.
This would be a must since FULL HD video got generalized, years ago.
So, I even think that "PTE video version" could be the moment to develop it under 64-bit.
Let us wait for better news.
-
For we "purists," PTE already has nearly everything we need...
Hi Lin,
For sure I am not a "purist" and I am very much missing a 64-bit native PTE!
What do you think on that (besides that Igor and his team are producing the very best slideshow software ever)?
Regards,
Jose
-
Jose,
Try to turn on "Minimize video card usage" option in the Preferences | System tab. It will close 3D engine in mini-player and Slide list when you go to O&A editor and thus provides more available memory. When you finish work in O&A editor the program will automatically re-activate mini-player and Slide list.
Thanks Igor, not enough memory yet.
But never mind, as I said above I already overpassed this problem keeping my "limits" untouched and still working in my XP 32-bit.
In the meantime, let us wait for PTE native 64-bit, avoiding tricky solutions and giving PTE all its well worthy freedom.
You are keeping a Pitbul in a Caniche case...
Regards,
Jose
-
Ken,
Spot on!
I, too, was a software developer and technical support guru; in my case, for 30 years. No matter how powerful the computer is, there will always be some users who "push the envelope" up to its limits. All hardware has finite resource. Once that hardware is used up - CRASH! (or, to be more precise: error!). The only short term solution then lies in the hands of the user: either reduce the requirement for all that resource, or increase the resource.
Jose's problem is that his hardware has insufficient memory for the demands he is making of it. Furthermore, even if he gave it more RAM, his operating system could not use the extra RAM. Installing Windows 7 (even at 64-bit capability) has not increased the RAM. It is likely that it has, in all probability, reduced the available RAM since I would expect that Win 7 64-bit probably needs more memory for itself than does XP SP3 32-bit. Even if Jose purchased a new PC using Win 7 64-bit and 8GB or more of RAM, I think there is a chance that he might still hit a limit. But then that limit would be in PTE. At present his limiting factor is not PTE. It is his hardware and operating system combination.
I know that's bad news for you, Jose, but I'm sorry - I think that is the truth of your situation.
regards,
Peter
Peter,
You are "almost" right!
You only missed that I created a Dual Boot (XP 32-bit and WIN7 64-bit).
Besides, I increased RAM from 4GB to 16GB.
So, as you said, "... that limit would be in PTE." Correct, the limit is in PTE because it is a native 32-bit software.
Another point: in my opinion, "push the limits" is what makes the difference! No more comments on this...
You are right: working on WIN7 64-bit, PTE shows a more bad behavor. Reason is that WIN7 64-bit eats more RAM than XP 32-bit, so PTE limits go down. I verified this.
Final thought: it is amazing that PTE still is a 32-bit native program!
I am the first to confirm that PTE is the best!
But, in my opinion, it's no worth to invent such astonishing capabilities of PTE, if it only can work in a system which offers such strong limitations, as 32-bit offers.
I only faced it now, not before, I've never worried on this.
By the way: I found a way to over ride such limits... And I am going on pushing...! May be my project will be ready for Christmas...
Reduce the requirements as a short term solution? Never!
Thanks for your thoughts and best regards,
Jose
-
Jose,
There have never been any announcements that WnSoft had introduced a 64-bit version of PTE. There is still one installation file that works for all kinds of Windows systems (XP or newer, 32 or 64 Bit). The PTE application only exports one type of executables that run on all Windows systems. How could you come to your conclusions? By the way, this is a forum for user discussions rather than a portal for the manufacturer's user support.
Regards,
Xaver
Xaver,
How could I come to my conclusions?
I tell you: loosing my money and patience!
Because I asked Igor, yesterday, if my "solution" (installing PTE on WIN 7 64-bit) was reasonable, and had no reply at all.
Anyhow, afterall, my conclusions are correct, no?
Concerning the "portal":
Is it not? Please note that it was Igor who replied to my first post, and I am replying to him. Is it forbiden?
By the way, just one of my recent conclusions: PTE is very, very good indeed... Not for projects a little bit more complex. And this should be clearly announced in specifications.
In fact, in case we push a little bit harder... CRASH is the result.
Anyhow, I insist, I don't know better than PTE, I only regret that it is not a 64-bit program in order that more than 2GB memory can be used.
Regards,
Jose
-
Igor,
I am now uploading to GOOGLE DRIVE a Backup-Zip of my project. It is 1,1 GB.
This backup is project as actualy is running in Windows XP SP3 32-bit.
In these 2 days I installed a DUAL BOOT with Windows 7 Ultimate, 64-bit, in which I installed PTE 7.0.7.
I must say that I am not very happy...
I only run my project once (fullscreen), and I could see some "flickerings" on more "dificult" parts, which I didn't expect to see (same as XP).
Anyhow, when slide 36 came, system didn't crash. This is positive.
My surprise was when came slide 38: fade-in transition to a single photo (JPEG with only 2,85MB) starting with a big and slow zoom-out.
PTE crashed, everything crashed, and I had to reset the computer, no way with Task Manager.
May be the reason is the photo to be 5616x3159 pixel (from RAW HD), and I need it because zoom out starts from a big close up.
Of course, I could downsize the photo to 1920x1080, but close up would be bad quality.
And I found it very strange because PTE in Windows XP does not put any problem, photo runs smooth and clean.
Why this happens in Windows 7 64-bit?
Is PTE 7.0.7 really prepared and configured to 64-bit, or only "adapted"...?
Another point: I am also uploading 2 snapshots of same slide, one running in XP, the other in WIN7.
In WIN7, spaces between words of the text got longer, and text runs out of the "paper".
Do you have any explanation for this? How will come out final MP4 file which I will make?
Please, let me know a private email address to send you the links for backup and snapshots.
Regards,
Jose
Igor,
Problem seems more serious than I thought.
PTE 7.0.7 is crashing and crashing, always OUT OF MEMORY, and it is impossible to edit anything. 100% inoperational.
PTE is not a native 64-bit program, it only runs in 64-bit systems but with all limitations of 32-bit systems (mainly 2 GB memory possible).
That was my above question: Is PTE 7.0.7 really prepared and configured to 64-bit, or only "adapted"...? to which you didn't reply.
By the way, you didn't send neither an email address in order that I can send you the backup-zip you asked for.
In this meantime, because I intended to finish my project for Christmas, as you didn't inform me of the really situation, I spent a lot of money installing Windows 7 Ultimate 64-bit, and increasing my RAM memory from 4 GB to 16 GB.
That was the "solution" I asked you if it was reasonable. As I can now conclude, it was tottaly unreasonable.
Bad support!
I thought that new version 7.5 (Beta 14, I suppose) could "solve" the situation and I installed and run it.
What a disapointment! Still a native 32-bit program!
So, my Christmas project finishes here.
I regret very much that PTE, beeing the best I could find to make super-quality slideshows, couldn't see that actual systems demand more program's performance (64-bit), and I also regret that PTE doesn't clarify that its 64-bit running possibility does not correspond to specifications of a 64-bit operating system.
Today, PTE made my day!
Regards,
Jose
-
Jose,
Please can you send me this project in ZIP archive? I'll check up for possible problems in PTE. Also probably I will find a way to optimize it.
You can use Mediafire, Dropbox, or Google SkyDrive to upload a file.
About memory usage. PicturesToExe several times loads a project:
1. One copy for Slide list.
2. Another copy for mini-player.
3. One more copy for O&A editor.
Igor,
I am now uploading to GOOGLE DRIVE a Backup-Zip of my project. It is 1,1 GB.
This backup is project as actualy is running in Windows XP SP3 32-bit.
In these 2 days I installed a DUAL BOOT with Windows 7 Ultimate, 64-bit, in which I installed PTE 7.0.7.
I must say that I am not very happy...
I only run my project once (fullscreen), and I could see some "flickerings" on more "dificult" parts, which I didn't expect to see (same as XP).
Anyhow, when slide 36 came, system didn't crash. This is positive.
My surprise was when came slide 38: fade-in transition to a single photo (JPEG with only 2,85MB) starting with a big and slow zoom-out.
PTE crashed, everything crashed, and I had to reset the computer, no way with Task Manager.
May be the reason is the photo to be 5616x3159 pixel (from RAW HD), and I need it because zoom out starts from a big close up.
Of course, I could downsize the photo to 1920x1080, but close up would be bad quality.
And I found it very strange because PTE in Windows XP does not put any problem, photo runs smooth and clean.
Why this happens in Windows 7 64-bit?
Is PTE 7.0.7 really prepared and configured to 64-bit, or only "adapted"...?
Another point: I am also uploading 2 snapshots of same slide, one running in XP, the other in WIN7.
In WIN7, spaces between words of the text got longer, and text runs out of the "paper".
Do you have any explanation for this? How will come out final MP4 file which I will make?
Please, let me know a private email address to send you the links for backup and snapshots.
Regards,
Jose
-
Jose,
Please can you send me this project in ZIP archive? I'll check up for possible problems in PTE. Also probably I will find a way to optimize it.
You can use Mediafire, Dropbox, or Google SkyDrive to upload a file.
About memory usage. PicturesToExe several times loads a project:
1. One copy for Slide list.
2. Another copy for mini-player.
3. One more copy for O&A editor.
Hi, Igor and Peter,
Yes, Peter, that's exactly this. PTE reached 2GB authorized by XP 32 bit to run any program!
In this meantime I asked to my "computer advisors" and they confirmed it.
So, no solution inside XP 32 bit.
Yes, Igor, I will send you a ZIP archive as soon as possible.
I understood that you said that PTE loads about 3 copies of "samething" to run different components (slide list, mini player and O&A) and this may explain why 2GB are reached if project is a little bit more complex.
As you said, this should be optimized!!! I never imagined...
After asking my "computer advisors", as said before, I will try NOW to get around this situation:
- Keep XP as it is (installed on "C" drive)
- Create a DUAL BOOT system (XP and WINDOWS 7)
- Install WINDOWS 7 in another HDD "E", which I have available and clean.
- In WINDOWS 7 I will only install PTE 7.0.7
- In XP, all my other programs will remain installed as they are.
- In XP I will continue to edit and prepare all my slides, movies, etc., etc., using my actual editing software as it is now. When components (files) are ready to go to PTE, I will do it in WINDOWS 7, and edit them there, where there is no memory usage limitation.
- A little bit more complicated, but better than "remake" my project which will increase complexity from mow on...!
- All this because I do not want to "replace" XP by WINDOWS 7, because I would have to install from new all my software, and configure it as it is, which would take about 2 or 3 weeks... and I am trying to have my project ready for Christmas...! Impossible, such replacement!
Do you think this reasonable?
Thanks,
Jose
IMAGE QUALITY DEGRADATION?
in General Discussion
Posted
Igor,
Thanks, that is good.
That is even better because I already noticed, since long time ago, that quality of PTE zoomed images is far better than same zoomed pictures using a video editor like SONY VEGAS or ADOBE PREMIERE, which I also use.
You know, as you already understood, I work with film and video since more than 50 years.
When PTE introduced video in slideshows I started using PTE to "edit" my films and videos! No more, no less!
With PTE I can frame, zoom, fade, etc., with better quality, that's my conclusion.
That's why I am very sorry indeed that PTE is not a native 64-bit program... I told you before.
Because 32-bit is very much limitative and forces me to have a lot more of a long (and stupid) work not to follow in an out of memory situation.
Please, tell me that you will produce a native 64-bit version VERY, VERY SOON! I have dozens of films and videos to edit... and I am not so young...!
Best regards,
Jose
PS: By the way, can you provide exact parameters of your PTE video converter? I mean, video and audio codecs used, bitrates, etc., which real values - of what? - correspond to quality percentage (from 0% LOW, to 100% HIGH), etc..
At, last, a suggestion: is it too difficult to introduce in PTE (video section) an immage stabilyser? Almost all video editors have this feature. My experience shows that SONY VEGAS stabilizer is far better than any other, it has 3 stabilization degrees and it is very much effective in each degree. This feature in PTE would avoid at least 1 video conversion and consequent quality loss, because, as you say, stabilized immage should be the original one, and after zoomings, fades, etc., it would be rendered only once (on the PTE converted video file). Is this so?