fh1805

Dave, If Violet is comparing an image in Photoshop that is set to use Adobe RGB with the same image that has been exported Save for Web and opened into PTE, will she not see a difference in colour? And I have seen post #5. The quote I used was from post #5. If the sentence that I quoted is an exact, precise and accurate statement by Violet, and if my understanding is correct (which you have neither confirmed nor denied), she is comparing apples and oranges! Tell me I'm wrong in my understanding and I'll shut up and learn from the experts! But if I am not wrong in my understanding... Peter

I'm not sure on this point but I think that would be the case if you were operating Photoshop in Adobe RGB. Someone with appropriate experience will be able to confirm this - or correct my understanding. PicturesToExe does not support different colour spaces - only sRGB. Therefore the images have to be saved using sRGB colour space. So, the correct test for you to do, is to Save for Web out of Photoshop and then compare that image as viewed outside of PTE in Windows Preview with the same image as viewed inside PTE in Full Screen Preview. The two images should look the same in both. regards, peter

Sunshine!!!!!! yah-hay! Let's call that evens, shall we?

Wot, no weather report!

John, Glad you got it sorted. That has caught others out before you. It looks as though there will be a much clearer interface to that function in the next version. regards, Peter

Don't keep rubbing it with so much glee! It's been a cold and wet day down here - with only occasional glimpses of a big yellow thing through the clouds.

This is really a suggestion for future enhancements. I will move this topic to that part of the forum tomorrow (Friday) Peter

Hi John, First point to understand is that the "Preview" button builds a temporary EXE file and then plays it. So, if your sequence isn't right in Preview it will not be right as an EXE either. So you can save yourself the effort of creating that EXE until the sequence does play correctly when Preview is used. Which exact version of v7.0 are you using (Help > About PicturesToExe). Since v7.0.0 was released there have been seven "bug fix" releases. If you are not using v7.0.7 then I would recommend going back to the WnSoft website and downloading the latest release from there. If we know you are on the latest release we know you have all possible bug fixes applied. Next, how did you add your audio? Was it only through Project Options | Music or did you add some through "Add Sound" off the top toolbar? Bearing in mind that we can neither see nor hear your system, in what way are the images and sound not in sync? Images always lag the sound by a fixed amount? Images always lead the sound? Images drift in and out of sync? To what exactly are you trying to sync the images? To the beat/rhythm of the music? To specific chords? to specific words in the lyrics? regards, Peter

John, I have zero knowledge of macs (except that if I venture outside today I'm going to need to wear one. It's tanking down here!) Let me give you my thoughts as to why it isn't working for you. Let's think, for a moment, about the Menu sequence as you would have set it up to run on a Windows machine. It would, I presume, be using either "Run application..." or "Run Slideshow..." commands to launch the next sequence from a button, a thumbnail image, a line of text, etc. Right? You can, indeed, then Publish that as an Executable file for Mac. So far so good. But what has PTE actually done in that process? Those "Run..." commands are coded in terms of a Windows environment. They worked on your Windows system when you tested them. Right? To get those commands to work on a Mac I suspect they need to be coded in a different "grammar and syntax" - one that is specific for a Mac environment. But then they would not work under Windows, would they? So you wouldn't be able to test the menu sequence on your Windows machine and know it was working correctly before you did the Publish for Mac. I think you are up against this fundamental difference between the two environments. It may not be possible at all to set up, in PTE, a Menu sequence on a Windows machine that will work on a Mac machine. As nobeefstu said, we need someone with Mac experience to contribute, someone like Tom, someone who may have actually cracked this one already; if, indeed, there is a solution. I'm now as curious as you to know what the definitive answer on this is! regards Peter

Dave, Not 100% sure how to create a video using MPEG4-ASP. What I have done is use v7.5 beta3 to Publish > Create AVI video file. I took the default values presented: 1920x1080, High quality, 30fps. The resultant file plays fine on my Samsung TV when run off a USB stick plugged straight into the socket on the TV. regards, Peter

Steven, "Show safe TV zone" is a setting found (in v7.0.7) by going into the Objects and Animation window and clicking on the "Tools" button (lower right). Placing it here suggests that it matters only for animated objects. That's not necessarily the case. It can be important even on the main image. It helps you build a sequence where all of the image that you want the user to see remains within view even if the TV technology is so dated that it doesn't always show 100% of the image. This was a real problem on the old cathode-ray tube TVs but is much less of a problem on flat screen TVs. Draw the analogy with the viewfinder of a dSLR camera. Only those models in the top end of the range show 100% of what the lens sees. Further down the range you might get only 92-95% coverage. regards, Peter

It isn't attached! Instructions for attaching files are here: http://www.picturestoexe.com/forums/index.php?showtopic=10509 Peter

Snapcam, I'm pleased to hear that you are now up and working. Percy Vere is a great chap. I'm glad he helped. regards, Peter

Hi Steven, Let's see if I can make you more comfortable! Aspect ratio This is simply the length of the long size compared to the length of the short side expressed as a ratio. It is totally independent of the units of measurement. A field that is 200 metres by 100 metres has an aspect ratio of 2:1. A postage stamp that is 2cm by 1cm has an aspect ratio of 2:1. A football pitch that has a length of 100 yards and a width of 50 yards has an aspect ratio of 2:1. Image size This is most commonly, and perhaps most usefully, expressed by the number of pixels along each side. Thus HD television has an image size of 1920 pixels by 1080 pixels. This also happens to be an aspect ratio of 16:9. My camera (a Nikon D300s) produces images with a size of 4288 pixels by 2848 pixels. This is almost, but not quite, 3:2 aspect ratio. A real 3:2 image that had 2848 pixels along the short side would have 4272 pixels along the long side. The decisions that are required When starting to create a sequence, I always begin by choosing the aspect ratio. I then choose the image size. For example: If I am going to create a sequence using only still images from my Nikon D300s, I will choose 3:2 as the aspect ratio (it is the nearest fit). I will then choose the image size. This I would set to 1080 high - because that is the height of a HD image and I expect to show the sequence on my TV to friends. I would set "Constrain proportions" in my image editor software (Photoshop Elements) so that the aspect ratio of 3:2 was preserved when I was resizing the images down to 1080 high. The sequence I am currently working on uses video clips from the D300s. These are 1280x720 pixels in size (an aspect ratio of 16:9). For this sequence I have set the aspect ratio to 16:9 and the size of slide to 1280x720. I would prefer to have used 1920x1080 as the size specified within PTE but I did not want my videos sizing upward from their original size of 1280x720. To have had them upsized by PTE would have resulted in over half the pixels not being there in the first place, but having been added by the computer. This adding of pixels is called "interpolation" and it is always accompanied by very visible image degradation - usually a very noticeable softening or lack of sharpness. I hope that has helped you. If I have been guilty of "teaching grandma to suck eggs", I apologise. If you still have questions or doubts, please go ahead and ask for further help. regards, Peter

I hope the replacement works. Keep us posted - this one could run and run... Peter

Perhaps, because the camera does not have an option for MP4? My Nikon D300s doesn't. Peter

Firstly, PTE v7.0 is only available as a 32-bit application. Its installer is correctly set up to install it into (on a Windows 7 system) C:\Program Files (x86)\WnSoft PicturesToExe\7.0 Do you have a folder structure that matches that path? It should have contents similar to this if you drill down into the 7.0 folder. regards, Peter P.S. After thought: you do have administrator privileges on your system don't you?

Ken, That's not the case. I have v4.49, v6.5.7, v7.0.7 and three betas of v7.5.0. I can launch any of those by navigating through the Windows Start button > All programs... and then pick the relevant PTE software release (and if that is v7.5, I can go on and pick the relevant beta release). I can then open any project by doing File > Open (sure, I might get a warning about conflicting PTE versions) I can have only one of those installed versions with its file associations set to the .pte and .ptv files. So if I double-click on, for example, abc.pte, the project will launch into v7.0.7 because that is the version that has the file associations set on it. When installing the v7.5 betas I check very carefully that the file association boxes are not ticked during the installation. I want a double-click always to open the project in the latest fully functional release - not into a beta with incomplete function. To open a project in v7.5 beta, I launch v7.5 beta and then do File > Open to select the project. It isn't complicated! One release, in my case the latest official release, is the one I use to do "real work". The v7.5 betas are for debugging etc. The others are for regression testing if ever needed. If I get through v7.5 beta without having to do any regression testing, I will be uninstalling all previous releases after I install the definitive v7.5. But I will still have my collection of downloads that I could call upon to install an earlier version. That collection includes: 449, 552, 564, 600, 604, 650, 651, 652, 657, 700, 701, 702, 703, 706, 707 and all 750 betas to date. Peter

Ken/Snapcam, V7.5 betas each install into their own folder. v7.0 installs into a different folder. You can have all versions of PTE co-existing with each other as installed software. Note, however, only one installation can have the file associations set with .pte and .ptv files in Windows. So only one version will react to a double-click on a PTE project file or a VideoBuilder project file. Peter

What Anti-virus do you have on the laptop and what on the desktop? Have you tried uninstall, get a fresh download and re-install? Peter P.S. (and off-topic) Will I see you at Cirencester next month?

Hi Snapcam, Brian may well be right there. If you have downloaded v7.0 from www.wnsoft.com, the program should have installed into a folder called "7.0" under a folder called "WnSoft PicturesToExe" in "C:\Program Files (x86)". If you have downloaded v7.5 beta from the forum it should have installed into a folder called "7.5" under the same parent folder structure. If it isn't in the right place, I cannot explain why. I would have to assume that you changed the destination folder during the install process. All I have ever done with PTE on my Windows 7 system is download the installer package, double-click it run it and take all of the default settings during the installation process. Peter

Your problem does not seem to be a "bug" - i.e. it does not seem to be a piece of PTE code that is working incorrectly. What you seem to have discovered is something - a particular flavour of H264 - for which there is currently no support within PTE. Therefore the PTE solution to your problem will require a change to the code of PTE. The correct way to request an enhancement to PTE is via the "Ideas and suggestions..." part of the forum. Starting a new topic in the "Ideas..." part of the forum will put your request onto Igor's radar and give you a much better chance of getting the code changed once the team have time. However, the company and programmers are fully committed to the v7.5 beta programme and don't have as much time as they might like to monitor and respond to forum posts. respectfully yours, Peter

Dave, I've moved your post as agreed. Please confirm I can now delete this topic. Peter

Thanks. I'm a bit tight on time this evening but I'll certainly do it tomorrow if I remember. Peter

DAve, Are you happy for me to move this post into the topic under "Ideas and suggestions..." that I opened at Igor's request? It would keep all this related material in one place. Peter