Comments

johnebaker wrote on 10/18/2016, 2:24 PM

Hi

Where the program starts playing from depends on which method you are using to stop start play ie:-

Play button (1 in image below) playback will start from the current cursor position and stop at the new position.

Play range button (2 in image) one of two things will occur

     With a Range selected, indicated by a blue bar above the timeline - that selected range will play

     With no Range selected, no blue bar, playback will start from the beginning

 

Up arrow key playback will start at the current timeline cursor position, stopping with either the Stop button or the Up arrow the play cursor will return to the timeline cursor. 

Spacebar playback will start from the current timeline cursor position.

The spacebar can also be used to stop with any of the options above, and, depending on the setting of the option  Program settings, Playback tab, Spacebar stops at current playback position, the playback cursor will either return to the current timeline cursor (option not checked) or the timeline cursor will jump to the current playback position when the spacebar was pressed to stop playback (option checked).

HTH

John EB

Last changed by johnebaker on 10/18/2016, 2:24 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 10/18/2016, 6:30 PM

Hi

This looks like a bug that has been in MEP for many years. Ralf from support suggested this solution:-

Here's something to try if you get locked into this situation with one of your projects that might save you some hassle: Simply use the function to optimize the timeline view in the lower right-hand corner of the screen (timeline - double headed arrow next to the zoom button). This should fix it.

The reasons why this problem is happening are somewhat obscure. So, if anybody manages to figure it out and comes up with a reliable way to produce this problem situation in a project, we'd be glad to hear about it. It seems to be our observation that this problem is already not as prevalent anymore in the current version, which seems to be confirmed by some of your observations as well.

As Ralf suggests, it does not seem so prevalent in the last few versions of MEP.

Something else you can try is to copy the whole timeline and paste it into a new project.

Ss

Last changed by Scenestealer on 10/18/2016, 6:30 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

Les2 wrote on 10/19/2016, 3:44 AM

I closed the project last night and reopened it today and everything is back how it was.  Amazing what a reboot can do.  There is a computer saying "if all else fails re-boot"!

johnebaker wrote on 10/19/2016, 4:40 AM

Hi

. . . There is a computer saying "if all else fails re-boot"! . . . .

Before I retired we always used this as the first tactic - Have you rebooted the computer?

It is surprising how many people think hibernating it is the same as turning it off!

Pleased to hear you are sorted.

John EB

 

Last changed by johnebaker on 10/19/2016, 4:40 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 10/20/2016, 3:42 PM

It is surprising how many people think hibernating it is the same as turning it off!

Something else that I read on a Microsoft site that surprised me was that a restart is not the same as a shutdown and restart - not sure why?

Ss

Last changed by Scenestealer on 10/20/2016, 3:42 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.