-
Posts
8,206 -
Joined
-
Last visited
-
Days Won
12
Everything posted by Lin Evans
-
Hi Melanie, Export them from Audacity at the defaults as mp3's then put them back in your show and I will wager that everything will work perfectly. Melanie, check your email.... Best regards, Lin
-
Hi Melanie, I think Dave is probably right - there is a slight difference in the way "Preview" and the completed executable files are processed. It's been discussed and is something Igor is looking into. This plus a possible single one of the multiple mp3's making up your sound track (I'm assuming you made it from multiple audios) having a variable bit rate could cause this issue. Even though you are using the identical audio settings you have used before, if you "sourced" one or more audio tracks rather than created them yourself, it's possible that one of them had a variable bit rate. I've had these kind of issues myself in the past, but have always used Audacity to run "each" audio through and export so that they are all identical in format. This has always corrected the issue. As strange as it may sound, sometimes one faulty audio track can totally disrupt an entire slideshow. The offending audio may play "perfectly" by itself in other players and "may" even play by itself in PTE, but when placed in a show along with other audio selections, it can cause similar difficulties. Best regards, Lin
-
Hi Melanie, Just so we are on the same page, if you click on the "help" then on About PicturesToExe, the version is 7.5.0 or is it a later iteration? If it doesn't say 7.5.10 (that's seven point five point ten) it's isn't the latest version. Just to be safe, if it's not, please install the latest version so we are all on the same page.... There have been ten updates since 7.5.0 So the sound track consists of a "single" mp3 which was constructed with Cool Edit? In the Project Options, Audio Tab, what does it give as the exact time length of the audio? When you click on the "Timeline" look at the ending time for the images. Is it identical to the length of time for the audio and does the waveform appear to end in the proper place in relation to the last slide? When you say the time is "out by an image" what is the display time for the image? In other words in "seconds" how far out is the synchronization. How large is your total project? If feasible, it might be a good idea to zip the entire PTE project and post a link so perhaps we can take a look and see if we can find a solution. If you can do this it might make it much easier and quicker because several of us can check it using different systems.If you go to "file" "Create Backup in Zip" the entire project can be zipped to a single archive. Best regards, Lin
-
Could you give us a little more information. Which version of PTE are you using? Which operating system, how many slides, how many audio tracks and how many separate audio selections? Does the video portion consist of only still slides, or do you also have videos in your show? Does the audio consist of only mp3's or are there other audio types? There are several variables which "might" impact the final playback. Does it start in sync and then go out somewhere along the time line or is it out of sync from the first slide? The more information you can provide, the more likely a quick solution. Best regards, Lin
-
Hi Dom, Are you using the latest version of PTE? The reason I asked is that I "think" you would: 1- Go to "Project Options | "Advanced" tab | ........... Excellent solution - one I didn't think of ....... As long as you don't need to modify or change the mask during the show the "mask as an Icon" would result in a smaller and more compact show than doing it via creating a video then loading the video as a single slide. Best regards, Lin
-
Hi, Masks are designed to work with a single slide. It would only be possible to apply a mask to an entire slideshow if that show were output as a video and then loaded back into pte as a single slide. Only in such a case it would be possible to run the entire "sequence" inside a mask. If the show consists of multiple slides which have not been converted to a single sequence such as a video, then to apply a particular mask to the entire sequence it would have to be duplicated for each slide. Best regards, Lin
-
To get what you want, choose Curling of Page transition, click on Folding (so there is a dot), Click on the "Left facing Arrow" - leave the default Roll up to Pipe, Radius 40 percent and the check in 3D volume. This should do what you are asking for. Best regards, Lin
-
Hi Robert, In answer to your first question - yes, the limit for data for PTE is two gigabytes. If a file is larger than this or really even "approaching" two gigabytes then it "may" exceed the limits for 32 bit functionality. How I would approach this is to take the file into another program such as Kantaris Media Player and see if it plays normally. Assuming that the file plays normally in another media player, they I would temporarily duplicate it and place it in a new folder. Next "attempt" to "replace" the blue error with the one in the different folder. If that still doesn't work, I would zip the file and send it to Wnsoft to let Igor and the development team have a look and see what's wrong. Unfortunately, there isn't a simple answer sometimes. It's actually the same with audio. Sometimes an audio will play properly in another player, but fail with PTE. The solution is to take it into an audio editor such as Audacity and output it in a very standardized (default) fashion which almost always results in a resolution to the problem. Likewise with a video which doesn't want to play. By taking it into your favorite video editor and outputting it as an AVI or MP4 it almost always results in a resolution to the issue. It's really difficult sometimes to get a handle on just what is causing the difficulty, but most likely there is "something" about the file which is not compatible with the library used by PTE. I've found videos which absolutely will not play in one of my several players, but will play normally in another. It's really not an issue "just" with PTE, but an issue with the complexity of video and audio encoding and compression. Best regards, Lin
-
Hi Eric, There are two ways to look at this. The first is that a particular version has everything you care about using - so no need to keep up with the latest changes and such because you are quite content with what you have and it serves your purposes. There's nothing wrong with that logic, except that when something new does come along that one might like (like video support, for example) and they decide to update their version, their learning curve is steep and complex because many "other" things have changed as well with various versions separating what one presently uses and the one needed for the new feature(s). Then, it gets a bit more convoluted. The person who has missed all the intermediate changes then has many, many questions which need to be answered. Their first recourse is then to read the manual, but manuals and user guides are virtually "never" completely thorough enough that they can substitute for practical "experience" with using the newer features. This is somewhat analogous to the new purchaser who first buys the product and is somewhat lost about how to do the things they have seen done. To solve this issue, the PTE forums have been, in my opinion, a godsend. When the developers and users come from many different countries with differing languages, cultures, etc., it is doubly difficult to convey subtleties in use via the user guide, so members who use the features daily fill in the gaps and help keep things running smoothly. As more and more new users are drawn to this great product, this task becomes more time consuming for those who help with tutorials and advice. Then comes the issue of users who have been using PTE for many years, but have not kept up with changes. They too are unfamiliar with new terms, interfaces, menu choices, positions and such and they also need lots of "hand-holding" to get on track. But they are even more difficult to help because unlike the new customer who had never used PTE and never formed use "habits," the "experienced" user - one experienced with different versions, has to "unlearn" much of what they are already familiar with. This makes the task of those supporting the learning process even more taxing. Eric, you say your are "still on 7.07 as you prefer it," but how do you logically "know" you prefer it when you haven't used the multiple versions above it? I'm not saying that there is anything wrong with staying with version 7.07, but there have been "many" features added and numerous changes which are all beneficial for the user which you "might" find very useful. It's difficult to give useful "advice" to someone who asks about upgrading and say that when someone says it's a good idea that this is only an "opinion." Of course it is an "opinion," but it's an opinion based on "experience," and therefore perhaps a more useful opinion to the petitioner than one from a user who has not worked with the new versions and new features. Don't you think that is a logical assumption? Spreading the learning curve over multiple upgrades rather than trying to absorb all the changes in one large "gulp" might be a useful strategy. Just saying..... Best regards, Lin
-
Amazing Technological Changes in Past 18 Years
Lin Evans replied to Lin Evans's topic in Equipment & Software
Hi Tom, Indeed it was a lot of money for a digital camera. At the time it was all by itself - a true 6 megapixel pro-body jewel - the closest thing to it was about one megapixel and the DCS model Kodak which was built in cooperation with both Nikon and Canon so that either could purchase the respective body model camera and use their existing 35mm lenses, was an incredible innovation for its time. It had an optional removable AA filter (which I bought), came with its own very good software and took amazingly good low ISO images. It was the first "truly" professional level digital camera. Fortunately, the prices began to drop WAY down when Sony introduced their first "so called" professional model in 1997- the DKC - ID1 (about $1800) which I also bought. It was "less" than a megapixel but did take very good images and great macros. Then in 1998 Sony introduced a dynamite 1.5 megapixel model called the DSC D700 followed almost immediately by an improved model, the DSC D770 - I bought both. They were about $1700 originally. Then they made a model with a "had picked sensor" which was otherwise identical and sold for a bit over $2600 originally. I couldn't see the difference so I waited until the prices dropped to buy one. I still have the D770 and the DKC I D1 - LOL. These old 1.5 megapixel Sony's actually took great images - see below: http://s194715615.on...y/s/sony110.jpg It's been an interesting ride.... Best regards, Lin -
Just keep in mind that there are two ways to reduce file size. If you use greater compression which is one way, you "may" end up with artifacts if you go too far. On the other hand, changing the "dimensions" of the image by resampling will not affect the "quality" as long as you don't change compression. About as far as I would suggest going with compression is the Photoshop equivalent of level 6. If you use more compression you will find jpeg artifacts in nearly every file. Best regards, Lin
-
Immersive 360 Degree Panoramic VIDEO !!!
Lin Evans replied to Lin Evans's topic in Equipment & Software
-
Hi Mur, Maybe try with another browser - it's "possible" that you clicked on the link "before" the last update and that the browser is trying to find the wrong file name. If you clear the cache in the browser you are using and try again it probably will work. I've just tested it with three browsers and it work fine for me at the present time. Best regards, Lin.
-
Kolor - the inventors and developers of Autopano Pro stitching software, etc., are breaking new ground here - I just signed up as a beta tester for their new technology.... Check out this video: Link To Demo by Kolor in Iceland.... Lin
-
Back in late 1995, I purchased my first dSLR, a Kodak DCS 460 built on a Nikon frame with a six megapixel CCD sensor, a soldered-in battery, removable AA filter, weighed a ton and cost me a bit over $30,000 USD without a lens. It was actually a "good" investment, because it paid for itself in less than a year and I sold it for nearly what I paid for it a year later. By 2000, I bought the first "Canon" dSLR introduced, for about $3600, which was the EOS D30. This was a 3.3 megapixel CMOS sensor, a "tiny" LCD and some very advanced (for the time) features. One of the features I think "should" still be available was an access port on the bottom where one could simply put a coin in the slot, turn the "button" about 10 degrees and gain access to the auxiliary battery which kept the memory alive for menu choices and kept the date and time of day active. Interestingly, today I charged up a battery from my Canon 40D and placed it in my D30, switched it on for the first time in 12 years and the time and date and all menu choices were there and up to date. Amazing to me that this old battery was still providing sufficient power to keep these settings. I inserted a one gigabyte CF type ! card (the camera accepts CF Type I or Type II cards), pressed the button to release the internal flash and took the image below, an oil painting by a close friend.: Today, one can purchase a Nikon 24 megapixel dSLR "with" a nice zoom lens for $550.00 USD. The new cameras have relatively "huge" LCD's, can take beautiful still images or high definition video, shoot and focus in near darkness and cost less than 1/55th of what it cost for much less capability 18 years ago.... The times they are a changing..... Best regards, Lin
-
Updating an slide show exe to the latest version (7.5.8)
Lin Evans replied to Ronniebootwest's topic in General Discussion
Hi David, I really don't know whether using the undocumented features will or will not affect the ability to open and create exe file with later versions. I agree with you that it "probably" wouldn't be an issue except that the actual exe created probably would not be identical to the one created with the original version because the feature would not be recognized. I only offered it as a "possible" explanation for a failure, but I certainly can't say because I haven't tried to do that. I think I still have 7.0 on my system so I could try it and see what happens and get back.... I really have no other explanation for a failure of a later version to open and create and exe with an older PTE file. Best regards, Lin -
Hi Barry, Unfortunately I'm running it on XP so can't use the latest versions. When I've run into that situation, the only solution has been to exit from Lightroom entirely and reopen. I suspect it's a memory leak issue. Best regards, Lin
-
Updating an slide show exe to the latest version (7.5.8)
Lin Evans replied to Ronniebootwest's topic in General Discussion
Hi Ron, I think it's the other way around. A "newer" project created with PTE will not open with an older version. All "older" PTE projects "should" open with newer versions. The software is backward compatible. If you have an older PTE project (dot PTE file) - just open it with a newer version of pte and output as an exe file. It "should" work just fine. The only possible exception I can think of is if you may have used an undocumented feature such as the conversion from color to sepia or to B&W. Later versions of PTE did not have that feature as far as I know, so may have problems running slides handled that way. Otherwise older pte files can be opened normally with later versions of PTE and EXE files "should" be able to be created. If you have one which won't work, send the PTE file to Igor for analysis. Best regards, Lin -
Hi Bert, Thanks for the feedback.. PTE makes it much easier to do than competitive products for sure... Best regards, Lin
-
This is an experiment in the effectiveness of the web for tutorial use. I have had several questions about "realism" in PTE animation scenes and this is in response to those. This is not a "tutorial," but rather a "how it was done" explanation of what is at least the minimum requirements to get realism in an animation. This animation is titled "Waltzing" from the title song, Waltzing's For Dreamers by Richard Thompson. The scene is a room with windows and a fireplace. The purpose was to get a realistic fire complete with synchronized sound and reflections in the fireplace. Minor other changes were made to the room. I just want to know if this is a viable way to describe the basics of creating such a scene with PTE: Any comments for improvement or change are welcome: As indicated in the web page - click on image to see video of original after reading information. I realize that the text size and color along with background color could have been better chosen - it was a really "quick" and dirty experiment. My Link to web presentation Best regards, Lin
-
PTE Made Easy tutorials - Continuously Updated
Lin Evans replied to Lin Evans's topic in Tutorials & Video Lessons
HI Mike, I doubt that there is any way to convert from video to PDF in any sensible way. I use the video format because many find it more convenient to actually see the keystrokes being performed rather than read from a written form. If I created them in a written format they might be easy for English speakers to follow, but many of our forum users are not English native speakers and perhaps find the video's easier to learn from. The other issue I have is that I would not be able to quickly produce them if I had to create them in the written format. I'm set up for video presentations, but what I can do in a half hour with video would take me perhaps a day to do in writing and the time I have to devote to them is limited. Best regards, Lin -
Hi Dom, A year away from PTE hasn't caused you to lose your "touch" LOL Great demo and neat effects! Best regards, Lin
-
Hi Bert, Not necessarily, although when using mp3's of unknown background, I generally run mine through Audacity to normalize them just as a matter of practice. In the past we have a number of examples of cases where there was absolutely "no sound" which was caused by only "one" particular mp3 with an issue. Best regards, Lin
-
Hi Peter, It may or may not have anything to do with bitrate - the important thing is for it to "work" and exporting unknowns from a known often solves myriad issues. The one with the higher bitrate is more likely the one which has been "tinkered" with the most - hence my suggestion to take it into Audacity and export it at defaults. Best regards, Lin