@Sging2 I also use the HC-X1 and the FZ2000 , the drone is a mini 3 pro
I use proxy files to edit in Vp20 no problems over here, and I use a lot of green screen.
So chroma keying , boris Mocha , color grading.
This is my media data from my HCX1
General
Complete name : E:\Konings K7\K7 en interview\01290005.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 2011.07 (qt /pana)
File size : 20.4 GiB
Duration : 19 min 23 s
Overall bit rate mode : Variable
Overall bit rate : 151 Mb/s
Encoded date : UTC 2022-11-03 15:30:53
Tagged date : UTC 2022-11-03 15:30:53
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.2
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 2 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 19 min 23 s
Bit rate mode : Variable
Bit rate : 149 Mb/s
Maximum bit rate : 158 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.360
Stream size : 20.2 GiB (99%)
Language : Dutch
Encoded date : UTC 2022-11-03 15:30:53
Tagged date : UTC 2022-11-03 15:30:53
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC
Audio
ID : 2
Format : PCM
Format settings : Big / Signed
Codec ID : twos
Duration : 19 min 23 s
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 213 MiB (1%)
Language : Dutch
Encoded date : UTC 2022-11-03 15:30:53
Tagged date : UTC 2022-11-03 15:30:53
Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 19 min 23 s
Bit rate mode : Constant
Frame rate : 50.000 FPS
Time code of first frame : 11:49:23:48
Time code of last frame : 11:49:23:49
Time code, stripped : No
Language : Dutch
Encoded date : UTC 2022-11-03 15:30:53
Tagged date : UTC 2022-11-03 15:30:53
I've been working on a project for several days with V20 and it's been quite good. Only 4 or 5 "not responding" messages during the entire day. Then yesterday I continued on the same project and it lagged horribly, not responding every couple of minutes and so on to where I just quit. Today I've been having pretty good luck again.
It seems that V20 is like a bad child that has tantrums for no reason. No reboot or anything can help. It has a mind of its own.
@Roger Bansemer Give this a try (no promises though) ...
In Vegas Hub, turn off the Create Project Collection slider switch:
What you have described has also happened to me, and turning off the Collection option stopped the lagging and normal transmission resumed. It would be preferable IMO if the switch was set to off as a default.
That is also "off" over here
@Roger Bansemer Give this a try (no promises though) ...
In Vegas Hub, turn off the Create Project Collection slider switch:
What you have described has also happened to me, and turning off the Collection option stopped the lagging and normal transmission resumed. It would be preferable IMO if the switch was set to off as a default.
I'll give that a try. Never knew that even existed and at a brief glance, I'm not sure what use it would be to me anyway.
Well... the new update 326 sure didn't fix any of the "not responding" crashes for me. Started a simple new project yesterday with only a few tracks and the "not responding" thing is having a field day every few minutes.
I see you are using NVDEC as your decoder in file I/O under Preferences... set that to QSV or Off. Any difference?
Don't forget to reboot VEGAS after changing that setting.
Roger Bansemer we have the same problem with our system. Just don't know what exactly :(
I also have this not responding crash in total random times with V19 b648. Sometimes even when i only place one H264 original camera file on the timeline and simply playback. Sometimes i edit a 1 hour 4 camera concert for 1 hour and when change some fx parameters, bumm! Vegas don't responding, i have to force close and restart app.
And these bug exist on our two totally different systems (#1 i7-32GB-1660Ti Sata SSD #2 Ryzen5-1600,16GB, RX480, M2 SSD, both use the recommended, stable vga drivers)
I would be the happiest man on Earth, when somebody could fix our problems! (of course every other apps works fine on our PC-s)
Did you try what I suggested in the post above yours?
yes, no difference
bug is somewhere else
I see you are using NVDEC as your decoder in file I/O under Preferences... set that to QSV or Off. Any difference?
Don't forget to reboot VEGAS after changing that setting.
Everything is unchecked and has been but doesn't seem to be a fix.
Please gather detailed information about your issue and post with the instructions in this link:
I keep a running log of such issues...
... but for the last few weeks I've been working on very old projects with all GPU functions turned off. My life has been pure bliss.
No QSV with i9-10900X I think, which is too bad as it has stability benefits over NVDEC in Vegas. You can try setting hardware decode to off if your CPU can handle decoding without the GPU. Not a solution but perhaps a workaround until something changes in Vegas.
Please gather detailed information about your issue and post with the instructions in this link:
I keep a running log of such issues...
... but for the last few weeks I've been working on very old projects with all GPU functions turned off. My life has been pure bliss.
Hi John, I really don't know what to report that I haven't already. V20 simply crashes quite a few times every hour I use it.
No QSV with i9-10900X I think, which is too bad as it has stability benefits over NVDEC in Vegas. You can try setting hardware decode to off if your CPU can handle decoding without the GPU. Not a solution but perhaps a workaround until something changes in Vegas.
No QSV with i9-10900X I think, which is too bad as it has stability benefits over NVDEC in Vegas. You can try setting hardware decode to off if your CPU can handle decoding without the GPU. Not a solution but perhaps a workaround until something changes in Vegas.
Where can I find "hardware decode" and I'll give it a try. Thanks
You shared a screenshot of it above : ) Preferences/ file io and set it to off for now.
@Roger Bansemer said: "Where can I find "hardware decode" and I'll give it a try. Thanks"
Hardware Decoder To Use
GPU Acceleration of Video Processing
Yeah, I see the same "Not Responding" behavior in VP20 and it really makes it annoying to use the program. All I need to do is change the focus away from VP20 and then return and it triggers the "Not Responding" behavior for 10-15 seconds. I have turned off the Hardware Decoder and GPU Acceleration and the behavior persists. This is crazy
You are lucky if you can continue the work after 10-15 sec. I have to force close Vegas and restart :(
I'm in the stage that I'm happy to pay some money who can solve my issue.
Yeah, I see the same "Not Responding" behavior in VP20 and it really makes it annoying to use the program. All I need to do is change the focus away from VP20 and then return an it triggers the "Not Responding" behavior for 10-15 seconds. I have turned off the Hardware Decoder and GPU Acceleration and the behavior persists. This is crazy
Do you have Close Video files and Close Audio files when not the active application unchecked as in the above screen shot?
Yeah, I see the same "Not Responding" behavior in VP20 and it really makes it annoying to use the program. All I need to do is change the focus away from VP20 and then return an it triggers the "Not Responding" behavior for 10-15 seconds. I have turned off the Hardware Decoder and GPU Acceleration and the behavior persists. This is crazy
Do you have Close Video files and Close Audio files when not the active application unchecked as in the above screen shot?
Both those options were Enabled (checked), which I assume is the default (certainly nothing I ever messed with), Disabling the "Close media files when not the active application" seemed to eliminate this "Not Responding" behavior when switching focus. Was enabling this parameter something MAGIX recently changed to be the default?
I also had similar sluggishness with DVD-A Build 100 when switching focus and surprisingly this seems to be better now that I made the above change to VP20 (not sure if this is real or not, but I'm mentioning it). I checked and did not see a similar DVD-A setting under its Preferences. --- Thanks @andyrpsmith
Disabling the "Close media files when not the active application" seemed to eliminate this "Not Responding" behavior when switching focus. Was enabling this parameter something MAGIX recently changed to be the default?
No. That's always been the default.
Disabling the "Close media files when not the active application" seemed to eliminate this "Not Responding" behavior when switching focus. Was enabling this parameter something MAGIX recently changed to be the default?No. That's always been the default.
That is strange Ed. I did not even know this settings existed so I never consciously would have changed them. One of life's great mysteries, LOL. Thanks to all.