Igor

Ray, We always encode H.264 (MP4) video with variable bitrate. The peak/maximum bitrate now about 40 mbit. There are many and many settings of H.264 video. You can look at mp4presets.dat file to see how many settings it includes. I'm afraid we will not change it more. In fact quality of created MP4 video already high. In next Beta 7 we even improved it more.

Thanks for news! As I remember re-installing of video drivers helps in all similar cases.

Thanks, we'll explore this problem.

Mary, Thanks, we've fixed that text message. Tom, Thank you, it's also will be fixed.

There is a problem with Vimeo and Youtube for us as developers. They don't provide examples how to upload video from Windows applications. They suggest SDK and examples only for web/online applications. So we have to use HTML based requests instead good reliable API. It's sad.

Probably it is some kind of moire? Or you see pulsing on edges of white framed photos? How you think the problem visible only in dynamic and can't be seen on static picture if you will make shot by digital camera?

Just single about 100 KB DLL file. PicturesToExe will perform this checking not more often than one time per day, or after failed attempt to upload file to Vimeo/Youtube. Process of checking is just reading of small .ini file from WnSoft's server (something like "CurrentVimeoVersion=1.00") and if server contains newer version, PTE will download new 100 KB file of configuration DLL file after user confirmed it. All described above applicable only when you use PicturesToExe for uploading of slideshow to Video/Youtube. In other case (presets for iPhone, video for PC/Mac) - no internet connections.

Vimeo changed settings for uploading in external programs (as PicturesToExe). Please download and install updated Beta 6: http://www.wnsoft.com/apr/apr-deluxe_beta.zip To solve this problem in future we will realize auto-updating in next betas. And before uploading to Vimeo/Youtbe, PicturesToExe will automatically check WnSoft's server for fresh configuration file with settings for Vimeo/Youtube.

Beta 6: http://www.wnsoft.com/apr/apr-deluxe_beta.zip * Fixed problem with uploading of created video to Vimeo. * Fixed bug of previous betas when there were no music in created video files if music in WMA/OGG format. * Small improvements.

Probably there is a recent program which works in background with high CPU loading. It deserves to try update the sound drivers.

I'm sorry to speak about this problem. I'm getting more and more questions and suggestions in emails and on the forum and regrettably I'm not able more reply in time on each request. I'll reply on all bug-reports, probably with delay. And add suggestions/ideas to my TODO list mainly without replies. Thanks for understanding! And I'd like to say thanks to all users and beta-testers who help me every day with replies to other users on various raised questions related with PicturesToExe!

Gary, By default "Pan and scan" option enabled to avoid black strips if your choosed video format (say 1280720 = 16:9) not equal your project's settings (4:3). Choose "Custom" in video output window and untick "Pan and scan".

There are two kinds of sizes: - Native size (adjustable in Properties tab for Frame/Rectangle and non-adjustable for Images created in Photoshop); - Visual size on the screen (Animation tab, Size/Position tool window). Why we need to specify native size for Frame (in Properties tab)? Because it's possible to put another object to Frame. If you change only height of Frame it will stretch sizes of all embedded objects. If you change Native size it doesn't happen. See attached screenshot. Both Frames have same visual size, but different native size.

I posted Beta 5 which fixes the bug with values in Size/Position tool window for Frame object.

It looks great, Dominique! Very dynamic.

Beta 5: http://www.wnsoft.com/apr/apr-deluxe_beta.zip + You can use 2-pass encoding of video (in preset for PC and Mac). + Improved speed of creating of video when "Pan and scan" option enabled. + Various small improvements. * Fixed old bug with visual defects in Slide list after pressing of Win+L key, or after locking of PC. * Fixed bugs with error message on attempt to delete a slide (if "Random show of slides" option was enabled). * Fixed problem when creating of H.264 video for PC and Mac didn't start. * Fixed bug with incorrect proportions of slide when "Pan and scan" option unchecked in creation of video for PC, iPhone, Vimeo. * Fixed bug when values in Size/Position tool window (O&A editor) were not actual.

According Jean-Pierre suggestion, we can try develop one united system of sizes in next version to replace Fit and Cover modes. In true percents for width and height of parent/slide.

Peter, Where I can download this project in ZIP backup? Size in pixels shows in tool window is equivalent of percent size of Zoom values in Animation tab and it's visual size of an object. I really just found one bug - when user change Size values in Properties tab for Frame/Rectangle object we don't see updated values in Size/Position tool window. You have to deleselect and select the object again to see right values. I'll fix this bug. That's all I discovered.

Sorry, but I don't understand what a bug related with Frame/Rectangle? Please could you prepare test project with two slides. One slide has Frame as parent, another slide - real image as parent. Both frame and image has same size (say 1920x1080). If position or size of insered child objects are different on both slides - it can be a bug and I'll explore this problem. Thanks in advance. One important moment. When you add image it already has own size (say 1024x768 and aspect ratio as 4:3). Impossible to change this size in O&A editor, but we can transform image with Zoom parameter making image larger/smaller or distorting aspect ratio. When you add Frame/Rectangle object we don't have its size - it's an abstract object. So we have to assign virtual size say 1920x1080 and then this object acts as an Image object with same result - we can tranform it changing Zoom values.

Thanks, Geoff. I think if problem with v4.48 and v5.5 slideshows, it's can be problem of laptop. In these two versions we even use different sound engines.

Geoff, Including created with previous 5.5? And same slideshow play sound without problem on another PC/laptop?

I just posted my article on this issue: http://www.picturestoexe.com/forums/index....ost&p=58255

Replacement of "Original size" mode in v5.6 This subject is of interest chiefly to the more advanced and professional users of PicturesToExe. The features being discussed are not normally used by beginners and less advanced users. This topic is a continuation of: http://www.picturestoexe.com/forums/index.php?showtopic=8594 and provides: Detailed explanations of the reasons why I removed Original size mode of objects An explanation of the new replacement feature Advice on how to use the new feature Firstly I must thank Jean-Pierre for his detailed suggestions written here and here. These suggestions raise several issues. It is difficult to discuss all questions simultaneously and so I'll concentrate on the main question now. This topic discusses only the difference between v5.5 and v5.6: between Original size mode and its replacement. Also thanks to Peter for his comments, additions and help with improving of this text. Why we added Original size mode: - Initially "Original size" mode for objects was added because some users asked for the ability to disable scaling of images to fit the screen. (By default all objects use relative size in percents which changes according slide/screen size.) - A second way of using Original size mode then developed in the user community to create complex slides with many objects. So we now have two different usages of Original size mode. Problems of Original size mode 1. The first major problem for authors and viewers of their slideshow comes from the incorrect positioning of objects that are defined in Original size mode when the sequence is played on a device of different display resolution: This problem is all the more serious because it is a “hidden” problem. If the author doesn’t change his display to another screen resolution he will not even know that the problem exists. This problem can also appear when creating DVD video disc for this slideshow, or video for Youtube. Jean-Pierre devised a special technique ("Cale") to solve the problem shown on the screenshot. He puts all Original size objects not directly onto the slide, but onto a special image (the “Cale”). This technique solves this problem but not all authors know about this trick (even I didn’t until Jean-Pierre told me). Original size mode in its pure state has logical problems and this worries me. If a feature exists it must work correctly in all situations. 2. The second problem is that we have significant difficulties supporting Original size mode with every new version when we add new features related to the use of objects. The code of Original size mode is very complex. It causes new bugs during beta-testing. So, in summary, it's a complicated mode with unsolvable logic problems. And it hinders us in making future improvements to PicturesToExe. Suggested replacement for Original size mode: In version 5.6 I have provided a replacement feature. 1. For those users who just used "Original size" mode to avoid resizing of images, they just need to enable "Fixed size of slide in pixels" and set particular slide size, say 1024x768. They can then use image files prepared in Photoshop as 1024x768 JPEG images. There is no need to change anything else. It remains a very simple solution. Image objects use "Fit to slide" 100% mode, but because the image file size and the displayed size are now, in this example, both 1024x768 there will be no resizing and the image will look very sharp. 2. For Jean-Pierre and other users who used Original size mode for complex slides with many objects I added a special new tool window. See "Size/position in pixels" button in "Common" tab of Objects and Animation editor. You can work with percents as earlier or with pixels for Size/Position. Please watch this video where I show how to use new Size/Position tool window for exact placing of several objects to create one united large picture (for special purpose or effects). Say there are 4 pieces 960x540 to make one 1920x1080 image. You can see how easy it now is; when you can define simple pixel values: http://www.wnsoft.com/apr/help/5.6/SizeTool.zip (5 MB) The source project and the images are here: http://www.wnsoft.com/apr/help/5.6/ComplexObjects.zip (700 KB) Please explore this new feature and try to understand my suggested solution. I think it's much easier than the old "Original size" mode. What about old projects created with Original size objects? When you open an old project file in version 5.6, PicturesToExe automatically converts the pte file to a new format. The EXE file and/or the video file created from this project using v5.6 should look the same as that created using the older version of PicturesToExe. If you want to continue making changes to this project you will need to work with the new Size/position tool window. Accuracy of calculations from pixels values to percent values After discussion with Jean-Pierre, in Beta 5 we will increase accuracy for internal calculations when you enter pixel values for Position and Size in the new tool window and that should be quite enough.

There is a speed problem with "Mipmapping" option (used in this demo) in current betas. I recompilied it with future Beta 5 and I think it should work more smooth now. Please try modified Mask2 demo: http://www.wnsoft.com/test/Masks2.zip P.S. 300_2310.jpg image had too big size 4288x2412, better to reduce it to 1920x1080, because no need in larger size and slides already are heavy with four FullHD images on each.

Umberto, We just reworked mipmapping option and it should work much better when mipmapping enabled. I'm sure it will fix the problem you've described. Please try Beta 5 when it's done.