davegee

The complication in understanding what is happening is compounded by the fact that Gary has (apparently) set a keyframe outside of the Slide Duration in a Non-KFSD mode project. Gary please correct me if I'm wrong? The test I refered to above: Non-KFSD Mode; Slide Duration 8 secs; Keyframes at Zero and 8 Seconds. When changing the Slide Duration to 16 seconds with Scale Keyframes Ticked I would expect that the second Keyframe be placed at 16 seconds in the same physical position at the beginning of the incoming transition (because I am in Non KFSD Mode). This, to me would be logical. However, it appears to me that when Scale Keyframes is selected the calculation is made on the basis of KFSD being set. Surely this is Logically wrong and the basis of the calculation should take into account KFSD or Non-KFSD? For example the 8 second keyframe in the above example would be 100% of the slide duration based on Non-KFSD before and after the Slide Duration change. Take a similar example with KFSD set to ON. KFSD Mode; Slide Duration 10 seconds; Keyframes at zero and 8 seconds. After a change of Slide Duration to 16 seconds the last Keyframe is now set to 16 seconds - the END of the incoming transition. Stu is correct that when Scale Key Frames is used the last Key Frame is always set to 100% of FSD and the others scaled to suit. However I don't see this as being Logical - KFSD or Non-KFSD should be taken into account. DG

Gary, Stu, There is something not quite right here. Try some tests with KFSD off and Keyframes contained within the Slide Duration i.e. not overlapping into the incoming transition time. The results cannot be right?? DG

Fun? Sure is!! I have concentrated recently on dispensing with the need (or desire) to use Masks. There are, of course, times when the mask will always be needed but there also times when I have used the mask as a first preference and whilst my "new" desktop will handle everything thrown at it the same project almost refuses to run on a lesser machine. So, no more masks unless there is absolutely no other way!! Anyway, back to the discussion arising out of Gary's suggestion..... DG

Hi Lin, I'm fully aware of what's available and I suggested something a little different back in September of last year having encountered a set of circumstances for which the present arrangements are cumbersome. The Master / Slave arrangement would allow for movement of a "block" of Keyframes by clicking on the Master Keyframe and dragging one way or the other moving both the Master and all slaves at the same time by the same amount. This facility is not presently offered? So with regard to my suggestion the method that you offered most definitely IS a workaround? (IMHO & from my perspective).B)/> DG

Hi Lin, Does your workaround allow for Clicking on a single "Absolute" keyframe and dragging it and "x" number of "Relative" keyframes all at the same time and by the same amount? DG P.S. Absolute and Relative are my terminology - they could be called Master and Slave.

DG

Great!! DG

Hi Colin, I think that you need to open your music file up in your Audio Editor and resave - making sure that it is saved CBR (Constant Bit Rate)? I opened it in Audition and it was 38 seconds - I saved it as a 160 KBPS CBR MP3 at 44100 and inserted it into the project. The new time was 41 seconds and I had to alter the slide positions a little. After that the sync was perfect from any position in the show. DG

The last two are the same thing (??). I just played the iPad4 MPEG4 on my TV (via USB) and there is no difference (that I can see) between it and the version created via the HD Video Option. By the way, you cannot create a 2048 MPEG4 for the iPad - you use 1920x1080 and put up with the (slight) upscaling. Once again I'd be delighted to hear from anyone who can show me otherwise? For JPEGs 2048x1536 works GREAT (iPad4) but for Video - no. DG

Correct Barry, As a trial I just converted my current project for which the EXE is 30Mb to MPEG4 using Igor's iPad4 Preset at Highest Quality and the resulting file is 322Mb. Reducing the quality setting to 50% gives a much smaller file so I suppose the way forward would be to find a quality setting for the iPad 4 which gives the smallest file at a quality which is better than a 1024 file upscaled? I think that Igor's presets are only to set the correct resolution and that an iPad 4 file at 1920x1080 will still play on an iPad 2. The reverse is also true but the upscaling is what "worries" me. I can judge for myself what is acceptable but I can't put myself in someone else's shoes to judge what their perceptions of the upscaling or quality settings are. If in doubt go for the highest quality? DG

Mark / Barry, 1024x576 is not going be as good on an iPad 4. Try it? You might think it's acceptable but I can see quality issues. I have yet to find a way of getting video to play at actual pixels on the iPad 4 so your 1024 wide becomes 2048 wide. Putting the 1024 wide on a 2048 "carrier" is one way forward unless someone else knows of a way to play at actual pixels? DG

Create a free account at DropBox or post at Media Fire and let us download the larger project which shows the problem. Describe the problem as accurately as you can and tell us what you think is out of sync? https://www.dropbox.com/plans http://www.mediafire.com/ I'm not a big fan of mediafire because of the suspicious adverts. DG

Just put one image up which displays the problem and let us try it out in PTE and PS etc.? DG

Colin, Do you have Synchronise Sound Track etc ticked in Project Options Advanced? DG

Colin, How big is your attachment - there is a limit? If it fits the bill then go to Full Editor - Click to Attach Files and when the file is uploaded click on the Add to Post on the right. DG

Gary, That's basically what I said here: The "gotcha" is that it only happens after a Save or Save As. DG

Gary, I will revise my post above. I agree that the first time in a new project it will require you to Browse. Thereafter it will automatically pick up the Save As folder. DG

Hi Igor, The Vimeo production was most impressive. You should have great fun with this!! DG

Gary / Ken, I think that we have to accept the current version available for download HERE as the latest. It shows up in HELP as 7.5.2. Igor was/is (?) trying to find a solution to a unique problem arising out the special circumstance of using KFSD and "Repeat Until Esc" and gave me a couple of trial versions. Until he comes up with a solution the current 7.5.2 is the best option and the KFSD problem can easily be "worked around". DG

Try 7.5.2 - it might do all that you ask for? DG

Gary, My current project is a 7.5 project and opens with the Project Folder (my Save As Folder) already open. If I now open a much older Project it does not recognize its Project Folder. Do a Save As and repeat the process and all is well - project folder recognized. This feature did not arrive with 7.5.3 so I assume that all Projects Saved after a particular Version (7.x.x) will do this - You are asking for it to be made a retrospective feature? On your second point - it does - from 7.5. On your third point - it does - from 7.5. DG

Hi Geoff, With respect to you that is surely unfair to Igor? If there is a problem (which I am not seeing) then we need to give Igor all of the info necessary to cure the problem. I have run around 8-10 shows this way from a menu and haven't seen the problem. How about reducing the number of shows (as a trial) to see if that is what is causing it and build up from there? DG

Is it that Igor made this change in a particular version and that in versions after that it does what you want and in versions prior to that it doesn't?? If you open an older project and save it as a 7.5 version it will always open the correct folder from that point onwards? DG

Lin / Jose, When Lin mentioned PS I thought he was refering to re-sizing. If you re-size an image and then reverse that process you cannot be sure of getting back to where you started (other than by using the History Pallette). Zooming into an image is different - no new pixels are made. DG

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