"Playback NOT ENABLED for this device"

j-v wrote on 8/31/2018, 4:50 PM

I think this is a minor bug.
With me it happens most with the use of nested Vegs or copy/paste timeline events from VMS 15.
Saving and reopening the project solves it.

I can trigger this so often I want, look

Trying the same on my laptop will not give this error message, so I assume it only happens on my desktop.

Carl-G wrote on 8/31/2018, 6:12 PM

I think this is a minor bug.
With me it happens most with the use of nested Vegs or copy/paste timeline events from VMS 15.
Saving and reopening the project solves it.

I can trigger this so often I want, look

Trying the same on my laptop will not give this error message, so I assume it only happens on my desktop.

The bummer is this happens every single time .so closing down and reopening the project every small file I render (and check) is a huge time consuming hasstle.

ajay wrote on 9/18/2018, 5:42 PM

This has been happening to me in Vegas 15 Movie Studio,. It can be with a very basic clip only a few seconds long - nothing nested, a single video track. It will preview fine but once I render even one second of it the error comes up when I hit preview. Makes Vegas almost unusable. I can't spend the time to close and reopen the project every time I check something.

j-v wrote on 9/18/2018, 6:34 PM

For only checking there are other preview options:

ajay wrote on 9/19/2018, 10:22 AM

Thanks for the suggestions and I can see some of that as a workaround, but I don't see that as a long-term solution. When I build a sequence I render it so I can check performance outside of Vegas. Then I make adjustments and preview quickly to see if they're right.

Prerendering or rendering to a new track is not a practical approach for this. It's a job, so efficient workflow is important - rendering to a new track (for example), and exporting (which will break preview) or previewing that track (which won't take it out of Vegas, which I need to do), and then muting or deleting that track to get back to the "real" project is just a bit kludgey. Granted, it's always possible I'm making this more difficult than it needs to be.

Something's broken - either due to an update or something I did inadvertently. Reading back, this seems to happen in a lot of versions, so I am surprised there's not a clear answer anywhere. The closest suggestion I've seen was related to audio codecs being in use for the render and then somehow not being available for preview. I've tried a number of different project profiles and audio settings, though, and I'm still getting the error. If there's no fix for Vegas I'll probably just have to do more of my stuff in Premiere.

Musicvid wrote on 9/19/2018, 10:32 AM

You never mentioned rendering an image sequence. That is a SCRIPTED action, involving none of the volatile driver traps Marco and I suspected.

I suggest you remount your issue in the Scripting forum; it may be a bug, but no one in this life will know until you post full details of your workflow, media, and product, ... Please?

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Relaunching Vegas to flush the buffers before and after rendering is still stock procedure, and it "may" become part of a durable workaround for you. "Virtual" memory is not boundless...

Good luck.

j-v wrote on 9/19/2018, 10:45 AM

This bug is not the minor bug as I said before.😞😞😞
To me it happens more and more.
First time today when I was working on a new small ( few minutes) HD project.
In order to open the explorer I probably touched with my mouse the already made Veg in the explorer for that small project and Vegas began rendering the swap0 file ( less than 30 sec).
After that I could not play the imported HD file with this error message.
Very irritating after les than a minute I began that project.👎

Musicvid wrote on 9/19/2018, 10:55 AM

@Carl-G

You are both now telling us you have similar issues when rendering an Image Sequence, although we did not necessarily understand that before.

Scripting forum is here, and there may be something in your build that is incompatible with the script. They will not know without you providing complete details first, however...

https://www.vegascreativesoftware.info/us/vegas-pro-forum/scripting+video/

Carl-G wrote on 9/19/2018, 9:26 PM

@msuicvid (and all others)

My original post said clearly this is with video on the time line (not images).

This bug happens with video on the time line. It is extremely inconvenient (and unproductive) to close down a whole project and reopen it again, everytime you want to check a rendered piece from it. This does *not* happen in Vegas 15. It only happens in Vegas 16 (and also in the most recent 9/3/18 update even with the Vegas Sample project).

I would appreciate helpful input to that, or better yet, a Fix (update) of it from Sony development.

(see my original post)

vkmast wrote on 9/20/2018, 2:15 AM

Sony development is not involved any more.

Carl-G wrote on 9/20/2018, 2:31 AM

Thank-you. Of course I meant, Vegas Creative Software development.

awfulTHEmovie wrote on 10/21/2018, 1:11 AM

at my machine (win10-build 17134, i7, 64gb, audio: usb extern) the error startet around the vegas pro 15 build 361. (maybe 216, i dont know the exact start).
recherche via google showed me other users with the same errormessage in lower versions (vegas 12).
so it seems that this error is something more different than an version bug of the new 16.

edit:
other users in this forum did a clean reinstall with windows to clear out the error.. mmh:
https://www.vegascreativesoftware.info/us/forum/can-t-preview-after-rendering-in-vegas-movie-studio-15--113023/

edit2:
changing the "audio device type" in the settings of vegas from "Microsoft Sound Mapper" to "Windows Classic Wave Driver" solved the problem for me. preview start working again and no error msg.

edit3:
oh.. after working a while, the error happened again. i changed the "audio device type" back to "Microsoft Sound Mapper" and the preview works again - but without picture - oO! after a restart of vegas the preview works again.
strange things happening ...

j-v wrote on 10/27/2018, 9:59 AM

After Vpro 16 update 2 (build 307) I tried to force this error and even in a long ( more than 5 h) project with a lot of nested vegs and vf's I was not able to trigger it again as with build 261 on my laptop.

Carl-G wrote on 10/27/2018, 12:45 PM

Wonderful news, I will check it out and report back.

j-v wrote on 10/27/2018, 1:01 PM

I'm curious about your findings, on my laptop I could not trigger it, but now I'm on desktop and there it was again , untill now I'm glad to see it once on a big trial project.

43jimcr wrote on 11/13/2018, 8:38 PM

at my machine (win10-build 17134, i7, 64gb, audio: usb extern) the error startet around the vegas pro 15 build 361. (maybe 216, i dont know the exact start).
recherche via google showed me other users with the same errormessage in lower versions (vegas 12).
so it seems that this error is something more different than an version bug of the new 16.

edit:
other users in this forum did a clean reinstall with windows to clear out the error.. mmh:
https://www.vegascreativesoftware.info/us/forum/can-t-preview-after-rendering-in-vegas-movie-studio-15--113023/

edit2:
changing the "audio device type" in the settings of vegas from "Microsoft Sound Mapper" to "Windows Classic Wave Driver" solved the problem for me. preview start working again and no error msg.

edit3:
oh.. after working a while, the error happened again. i changed the "audio device type" back to "Microsoft Sound Mapper" and the preview works again - but without picture - oO! after a restart of vegas the preview works again.
strange things happening ...

43jimcr wrote on 11/13/2018, 8:39 PM

This did not work for me.

43jimcr wrote on 11/13/2018, 8:54 PM

However, Magix Low Latency 2016 did work!

43jimcr wrote on 11/13/2018, 8:59 PM

However again. I lost sound on playback,

Carl-G wrote on 11/14/2018, 2:00 AM

I am on Vpro 16 update 2 (build 307), and this playback error is still happening as described in my original and subsequent posts above. This seems to be a major dysfunctionality (in that the program ceases to function after a simple rendering).

So my bigger question is: Do the programmers at Vegas see this error on their Windows 10 Desktops (not laptops)? If so, surely they have enough at their deposal to begin to fix the error. If not, then what do they need from the many of us who have this issue (no playback after rendering) to help fix this error? And *who* do we submit it to?

NickHope wrote on 11/14/2018, 2:53 AM

...If not, then what do they need from the many of us who have this issue (no playback after rendering) to help fix this error? And *who* do we submit it to?

Submit a support request here, including as much information about the problem and your system specs as you can: https://support2.magix.com/customer/en/vegas/form

Carl-G wrote on 11/14/2018, 2:13 PM

Thank you Nick. I appreciate the link.

zliko-z wrote on 12/20/2018, 6:10 AM

Hey Carl, have you figured out a fix for this? Same thing happening to me (V16).

j-v wrote on 12/20/2018, 6:39 AM

I could also easily trigger this popup in former builds, but in the new build 352 I did not see it (yet?), also not after a lot of tests.