[László Kovács]

Hi John,
[John Rofrano] “It’s important to note that, this will only work if the MOV file contains AVC/H.264 MPEG4 video. You cannot copy without encoding unless the codecs match so, for example, this will not work if the MOV file contains Apple ProRes 422 video.”

I agree it won’t work with a codec that Vegas does not support.
But with any of supported codecs should work.
At least I guess so, because I converted this way a MOV which contained mpeg2 video 2 or 3 years ago.
The only one and single mov file I ever met over the years… :))

Kind regards

[László Kovács]

Hi Eric,

Good to see someone here from Magix 😉

I tried the setting you mentioned. Unfortunately does not help.
It was set to best, I set it to good. Nothing changed regarding this phenomenon.

Kind regards

[László Kovács]

Just to put my 2 cents 🙂
I used ffmpeg to convert mov to mp4.
ffmpeg -i input.mov -vcodec copy -acodec copy output.mp4

That’s done in seconds, because there’s no reencodigng.
Only the container format is changed.

[László Kovács]

Hi,

Right here and now it works for me.
Right click audio/open copy in soundforge XP
An the Vegas creates a Take2.wav, opens SF. After processing in SF I have the audio as another take on the timeline.

Note, that I have only Soundforge Audio studio 10.0 build 245.
Not the real Soundforge.

Best Regards

[László Kovács]

Thanks for all your support!
That means I’m not alone, and the problem is not only in “my device”.

Here’s a veg, so anyone can test easily:
10372_2dglowzeroblurtest.veg.zip

Unfortunately Sony border FX does work only for images with a matching aspect ratio to the project aspect, and that’s rarely the case 🙁
Otherwise empty, transparent areas appear between the image and the border.

Best regards

[László Kovács]

Thanks. Can you test please, if you have 5 minutes, if you have this problem with GPU support enabled?
Just put something on the timeline, crop a bit, use track motion to reduce size and place it, then put a thin border around with “2D glow” blur set to 0, and move it on the screen.
On my machines these simple steps reproduce the problem.
If it works as it should, could you please tell me what GPU with what drivers you have?

Kind regards

[László Kovács]

[Marco Baer] “Did you try turning GPU support off in “Options/Preferences/Video”?”

No, I didn’t. Now I tried.
You saved my life, friend!
Thank you! Thank you very much!
By turning off GPU support, Vegas started to work normally. So the bug is in the GPU support.

Now I can finish my project this week, so I can keep my head 🙂
…but I’m still unhappy.
The point of upgrading to VP13 (beside that I’ll get VP14 for free from Magix) was to start using openCL.
Now it seems that I was wrong…

[László Kovács]

Hi, thanks for your input.
There are no special effects used, only few that came with Vegas.
All objects are on different tracks. (Lady full screen, lady talking in small, the presentation itself, and the graphic.)
The most below layer is a color gradient. The topmost containing the lady talking full screen, full_HD AVC, recorded with my JVC HM600. Only a color curve is assigned as FX.
The presentation in the middle layer is exported from a ppt, for which I used the Lagarith losless codec (resolution 1440*1080 (aspect 4:3)). There’s no crop, just placed it via track motion. The lady talking “in small” is cropped via pan&crop to 1:1, then placed via trackmotion.
The picture below the lady is just a png, a bit cropped via pan&crop, but with no “stretch to fill” and placed via track motion.
The machine Vegas is running on is irrelevant. I encountered this thing first on my desktop (i5-3570 / NVidia 9600GT / 8GB RAM), and blamed my ancient video card, but checked on my notebook, and is present there too (Lenovo Z51-70 – i5 5200 / AMD Ati R9-M375 / 8 GB RAM).
The common points are Windows 7 64 bit and 8GB of RAM. None of them I could blame…

This is painful for me now. I started a new project with my new VP13, did a lots of edit, and I can’t finish it.
The problem is not with this already done project, I just took it for demonstrate the bug.
This is here in VP10 format, and I can open it, and edit if I’d need, and render of course.
But the new project is only available in VP13, as I started with it.
🙁
Already tried to play with dynamic ram preview (increased, decreased), did not help.

[László Kovács]

Oh, and it’s on the render too.
With Vegas 10: https://www.youtube.com/watch?v=gKfJmyit1Io
And with Vegas 13: https://www.youtube.com/watch?v=O6MFRPFg16U

:(((

[László Kovács]

I’m not a native english speaker, so please excuse me if I type something with wrong words, or am not clear.
I think hungarian, just try to write in english 😉
Second, I’m few versions behind you, I still use Vegas pro 10, so if some of my ideas are implemented in V 11..13, just ignore it.

So, my whishes (I start with the most important to me, and the last one is the least important):

– If just current features of Vegas would be kept, but with increased stability and reliability, I’d be happy with it.
– +1 for the crossplatform thing, if Linux would be supported… (offtopic) Linux itself is free, but it does not mean all programs running on it have to be free – I use both Linux and Windows, and on Linux I already have one paid application. It’s an office pack, also made by a german firm 😉 (/offtopic)

– In some projects I use a lot of keyframes. When it’s about effect properties, sometimes the keyframes disappear. They are there, because they do their job, just are invisible. In this case I have to close the effect properties dialog and reopen it, then the “missing” keyframes appear. When it’s pan/crop or trackmotion I never saw this problem, maybe the culprit is behind the redesigned UI of the effects keyframe handling?
– Event velocity envelope: please, please, be it available for audio too…
– Event velocity envelope: please increase the boundary limits.
(Currently -100%…+300%, could it be -1000%…+1000% ?)
– I would like to see a consistent UI in the whole application with consistent controls, sliders, etc.
– I’d appreciate some kind of “delta” keyframes, which wouldn’t specify a direct value of a parameter, but a change to that parameter, or the speed of change to that value. For example, if trackmotion had a keyframe with a “speed (x,y)” parameter, it would move the track on the screen with only one keyframe. The benefit would be if using more such keyframes, a path could be defined, on which the track would move smoothly. That would make a lot easier to move something on the screen smoothly. (Currently a lot’s of position keyframes are needed with different interpolations to achieve a similar moving effect.)

Kind regards