Michael Hoogasian
Forum Replies Created
-
[George Dean] “Movie Studio has the same problem, and VP16 doesn’t have an issue with the converted file. So, it appears it is your source media.”
That may be the case, however, that would seem to implicate there is a longstanding bug in how Vegas is interpreting the file. I suppose I should file a bug report with MAGIX. Would you be interested in seeing if you can reproduce the issue if I uploaded a smaller sample clip to Google Drive?
-
[Graham Bernard] “Supply MediaInfo of that MJPEG”
See my opening post ☺
[Graham Bernard] “Supply SCREENGRAB of your Project Settings.”
See below
-
[Jackie Luffy] “WOW for anyone who has the same problem you need to switch the encoder from Mainconcept to NV encoder and the DIFFERENCE IS NIGHT AND DAY it went from like 20 hours to literally under an hour now this will be done rendering, crazy”
Keep in mind that rendering using the GPU may not produce the same quality as rendering with the CPU, due to, for example, half-precision floating point vs. full precision.
-
[George Dean] “Where is it choking, when loading the file, or during playback? Is the wait time during building the audio wave? After you start a new project and load, waiting until finished, close that project and open the project for the second time, it load time shorter and/or playback smoother?”
Even after waiting for it to load the file, it still chokes even when doing something as simple as moving to the next frame in the preview window. Out of curiosity, after waiting for it to load in a clean project, I rendered it to 10Mbps H.264, and Vegas has no issue working with the transcoded file…
[George Dean] “What has changed in your system, OS, etc.?”
I’m not entirely sure what you mean by that. Changed since I installed VP16? Nothing that I can think of really.
[George Dean] “If you have been using Vegas Pro 16 for a while, try a full reset of the program and delete the cached application data.”
To ensure this was not the issue, I tried using the clip in my old Movie Studio 12, and it suffers the exact same symptoms.
[George Dean] “This may be one of those problems you are going to need to add a lot of information about your workflow and system for members to help.”
The only other things that I can really think to add that would be relevant are: I have GPU accel turned off (as you recommended I do in a previous thread which solved the red screen issue) and that this particular MJPEG file was created by guvcview in Linux.
-
Yep. Vegas correctly detects it as 1920×1080 progressive at 30.00FPS but it still becomes unusably slow, frequently hanging 30+ seconds. Also FWIW, I noticed while it’s hanging, my disk indicator light is on, but not solid on. Rather it looks like it’s being PWMed at high speed. I wonder if Vegas is trying to read the MJPEG file one frame at a time and thus issuing a bunch of system calls to the disk rather than reading it all at once with just one system call?
-
[Dimitrios Papadimitriou] “Did you try my work around with legacy text? Unless you don’t want to use legacy text.”
I don’t think you quite understood what the problem is. I made another screenrecording so as to make it more clear what the issue is.
-
[Graham Bernard] “Good question. My advise would be to ask your contact at MAGIX. I’m sure they’d give the best reassurances. Why don’t you load it up and see?”
Well I got it loaded up today, and while I can confirm the keyframe bug is gone, it appears that the anchor point bug has not been resolved. I guess I’ll email them again with another screenrecording, since they were so happy I provided one last time…
-
[Graham Bernard] “Install VP16 and use it, you won’t look back”
The one remaining question is, does VP16 also solve the issue of the text not respecting the anchor point? I haven’t had a chance to get VP16 fired up to test that yet….
-
Well, I emailed MAGIX technical support with essentially the same message as in my opening post, and I also supplied them with the screenrecording of the problem. They were able to reproduce the issue in VP15 on their end, and while they did not say it would be fixed in an update, they did give me a free license for VP16 which they say does not have that bug 🙂
-
[George Dean] “I cannot duplicate you issue either. Perhaps performing a full reset would help. Hold down the ‘Ctrl+Shift’ keys while double clicking on the Vegas Pro 15 desktop shortcut. In the little window, check the box ‘Delete all cached application data’, then lift click on ‘Yes’. This will reset Vegas Pro 15 to it’s original installation settings, and also delete the pesky cached application data that builds up and sometimes causes Vegas to do strange things.”
Ok, I will try that. Just to be clear however, when you tried to repro, were you using VEGAS Titles and Text or Legacy Text?
