After playing video with Windows movie player, can't preview video

Digital-Larry wrote on 4/10/2020, 6:20 AM

After rendering a video, I click on "Open" which launches the rendered video in Windows default movie player. After doing this, trying to preview video in Vegas fails. If I quit and restart Vegas it's OK until the next time I do this. I scanned the known issues and didn't see this. It's pretty annoying. Any way to stop that from happening?

Vegas Pro 17

Windows 10

Ryzen 2600 CPU

16 GB RAM

Comments

EricLNZ wrote on 4/10/2020, 6:30 AM

In what way does it fail in Vegas?

j-v wrote on 4/10/2020, 6:38 AM

After rendering a video, I click on "Open" which launches the rendered video in Windows default movie player. After doing this, trying to preview video in Vegas fails.

When I click on "Open" iI get the location where that file was saved and I have to click on that file tp play it. After closing the screen of that location I'm back in Vegas where I can do all I want do do in VPro 17

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

EricLNZ wrote on 4/10/2020, 6:55 AM

@j-v Don't you get two options "Open" and "Open Folder"?

j-v wrote on 4/10/2020, 7:29 AM

Yess sorry my fault , but it is normal that when closed that player Vegas is normal available

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Digital-Larry wrote on 4/10/2020, 10:34 AM

@EricLNZ

An error occurred while starting playback.

The request is not enabled for this device.

click on "Details"...

The record device does not support the current input format.

j-v wrote on 4/10/2020, 10:45 AM

Maybe you have to try to use another audio device to overcome this happening?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Digital-Larry wrote on 4/10/2020, 11:29 AM

Seems like using the "Movies and Videos" app or whatever it's called leaves some device, audio or video, in some state that Vegas does not recognize or try to re-initialize. I can close and reopen Vegas in maybe 10 or 15 seconds. It just seems stupid. It also seems like many people would hit this problem, unless it has something specifically to do with my audio device (which is a Behringer XR18 mixer).

j-v wrote on 4/10/2020, 11:36 AM

I meant the audio device that is stated in your Vegas software, where you had the problem at

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

EricLNZ wrote on 4/10/2020, 7:15 PM

@Digital-Larry This has cropped up a few times. Search the forum for the posts. The remedy is usually to change your audio device as @j-v suggests.

Musicvid wrote on 4/10/2020, 9:11 PM

Do not have two apps open that utilize the audio driver at the same time.

This is important times 10 if you are using MS Mapper. You should use your audio device's ASIO driver iinstead, often called Direct or HD Audio.

Digital-Larry wrote on 4/11/2020, 12:49 PM

OK, confirming that if I swap the audio device to my Behringer XR-18 and back (to MS mapper) that I don't need to stop/restart Vegas. The Behringer is a little picky because you have to set the sampling rate explicitly for whichever app you are using. Generally speaking if I am editing video then that's all I am doing, although sometimes I leave Ableton Live open. Anyway now I know the workaround, thanks.

DL

RonB_USA wrote on 8/13/2020, 10:31 AM

I have experienced this over the years with VPro. I simply switch the Audio Device to ANY other setting (using Preferences | Audio Device) and it works immediately. It happens when I go to other audio-related programs (internet TV, internet radio, various media websites, etc.) and then come back to VP. It won't play but puts up that error. It doesn't seem to matter what Audio Device that I use. I can switch right back to the original one and it works the second time. It just requires going to a different one than the one causing the error.

It is doing it in my new VP18 right now (the reason that I checked this thread). My three choices are: Microsoft Sound Mapper, Direct Sound Surround Mapper and Windows Classic Wave Driver. I just close my eyes and choose one when it happens (infrequently). I never have to restart VP. And I almost never have a second Windows 10 program running while editing.

Last changed by RonB_USA on 8/13/2020, 11:04 AM, changed a total of 3 times.

RonB_USA

Operating System: Windows 10 Pro

Dual Monitors: Now have TWO Samsung 4K 27-in (3840x2160) monitors both using DisplayPort

Desktop Sound: Stereo speakers with sub-woofer. Headphones. Earbuds.

VEGAS Pro 21.0, version 208. Have used VEGAS Pro since Sony days. Movie Studio also.

Voukoder 1.7.1.0

Source Footage: Mostly XAVC-S 4K MP4 with some MTS HD at times. Have used Samsung S21Ultra 5G footage.

Some upscaling of older videos. Many videos are more than 10 years old. Trying to learn more color correction and grading techniques. Any help with flicker reduction without motion blur is welcome!

Motherboard: ASUS PRIME X299-A II (3.7GHz)

CPU: Intel i9-10920X 12 Core 24 Thread

GPU: Quadro RTX-4000 8GB

RAM: 64GB DDR4

C-Drive SSD: M.2 2TB + Video SSDs: Two M.2 2TB + Internal HDDs: Several TB + External HDDs + External SSDs

michael-harrison wrote on 8/13/2020, 10:50 AM

fwiw, I've worked around this by setting my audio devices to not allow exclusive access (in the driver control panel).

While that's worked fine for me, others have reported that because of their devices and/or workflow, they can't do that. I've got a pretty vanilla audio setup.

ymmv

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

JJKizak wrote on 8/13/2020, 10:59 AM

Windows Media player will with Windows 10 "AI" switch/flop codecs around faster than you can whistle Dixie.

JJK

Musicvid wrote on 8/13/2020, 11:49 AM

@RonB_USA

"Direct Sound Surround Mapper" is generally preferred, although not for the same reason. You see, they are full duplex ASIO. allowing simultaneous record / monitor, and have low latency. The settings shouldn't change in Vegas when another process has control.

RonB_USA wrote on 8/13/2020, 12:06 PM

@Musicvid, (FYI) when I select Default All in Audio Device Preferences (VP18 Suite) it goes to Microsoft Sound Mapper. But I will set it to Direct Sound Surround Mapper right now. Thanks.

PS - I tried to get it to "error" for Audio Device by going to other media programs and it won't. So perhaps it is not other media causing my infrequent errors, but some other reason. Time will tell...

Last changed by RonB_USA on 8/13/2020, 12:11 PM, changed a total of 1 times.

RonB_USA

Operating System: Windows 10 Pro

Dual Monitors: Now have TWO Samsung 4K 27-in (3840x2160) monitors both using DisplayPort

Desktop Sound: Stereo speakers with sub-woofer. Headphones. Earbuds.

VEGAS Pro 21.0, version 208. Have used VEGAS Pro since Sony days. Movie Studio also.

Voukoder 1.7.1.0

Source Footage: Mostly XAVC-S 4K MP4 with some MTS HD at times. Have used Samsung S21Ultra 5G footage.

Some upscaling of older videos. Many videos are more than 10 years old. Trying to learn more color correction and grading techniques. Any help with flicker reduction without motion blur is welcome!

Motherboard: ASUS PRIME X299-A II (3.7GHz)

CPU: Intel i9-10920X 12 Core 24 Thread

GPU: Quadro RTX-4000 8GB

RAM: 64GB DDR4

C-Drive SSD: M.2 2TB + Video SSDs: Two M.2 2TB + Internal HDDs: Several TB + External HDDs + External SSDs

Musicvid wrote on 8/13/2020, 12:19 PM

Yes, Microsoft Mapper pools older high-latency WDM drivers exclusively, I believe.