Comments

I mentioned certain "gain & mixer" problems in vegas14.

I experience similars in vegas15.

Example:

I normalise audio-files (rightclick - normalise).

But when they are played back ...the mixer shows maximum peaks at - 3dB (more or less), while the peaks, logically should be at 0dB.

Even when i push levels in the audiotrack higher above 0dB ...gain in mixer shows -3dB?

It seems to be caused by the "default position" of the output fader.

grtz

Hey Gary, here's one quick design change that should be very easy to implement and would improve productivity. There's a small amount of wasted space in the interface right now that has been bugging me, because right next to it is another item taking up screen space that could easily fit there.

The transport bar under the preview monitor. See how it sits above the info about the source and preview resolutions and framerates? Those buttons could easily fit on the right side of that information, freeing up extra space to make the preview window larger. If that preview window were too small to fit the buttons in beside the resolution/fps info, then they could automatically be moved above that info like it is now.

I appreciate the interaction with users, answering our questions and giving us insights into the development process.

@26mook For VP14 users - $249.00 (upgrade version)

I spent 199 for upgrade from 13 to 14 but I never use because crashes I don't want spend again 199 to buy V15 we should get all users upgrade from 14 to 15 for free

I don't feel entitled to an upgrade for free. I got a full year of solid productivity, running my business exclusively on VP14. Yes, sometimes it crashed. Yes, there were and still are features I want to see added. However, it made me far more money than I spent on it. I bought V15 suite on launch day because I liked how well Magix supported V14. The one time I did have a bug that threatened to make me late on delivering a project, Magix had a patch out that fixed it in time for me to deliver.

We all knew (most of us, anyway) going into it that Magix did not fully develop 14 themselves. That known, I didn't expect perfection when I bought it. I just wanted more stability, and they squashed a hell of a lot of bugs. Sony left them with a broken pile of garbage with a mountain of potential beneath it. I'd say they've done pretty well all things considered.

Now that V15 seems to be providing a solid foundation for a modern editor, let's get some better color correction tools, auto-sync for multicam, at least some form of basic motion tracking, better text generators, and 32 bit floatin point support for all plugins.

Thanks to Gary and the Team for keeping Vegas alive. Major changes won't happen overnight and I think the V15 update is amazing and look forward to the continued progress! Much love to the Vegas Family. At the end of the day, it's still the most flexible editor out there -- Let's keep pushing Vegas forward.

( É que um monte surpreendente? ...)

(Eu realmente tenho que dizer que eu tenho o mais recente .NET 4.7 instalado e operacional? ...)

((Quem eram seus beta-testers, afinal?) )

 

Atualizar:

Meus sinceros agradecimentos vão para Marco.
O problema foi provocado por Semw Auto plug-in Níveis OFX.

No caso de correr em problemas semelhantes -> renomear todo o C: \ Arquivos de programas \ Arquivos comuns \ OFX \ Plugins pasta -> e, em seguida, verificar se Vegas pode começar.

I mentioned certain "gain & mixer" problems in vegas14.

I experience similars in vegas15.

Example:

I normalise audio-files (rightclick - normalise).

But when they are played back ...the mixer shows maximum peaks at - 3dB (more or less), while the peaks, logically should be at 0dB.

Even when i push levels in the audiotrack higher above 0dB ...gain in mixer shows -3dB?

It seems to be caused by the "default position" of the output fader.

grtz

 

This sounds like you have a Limiter engaged on your Master Buss. If you have a brick wall limiter on your master fader, no matter how hard you push other audio tracks into it, the limiter will not allow anything over what it is set to. So it sounds like you have a limiter set to not allow anything over -3dB. Check into that and see.

Hi,

Vegas Pro 15 (trial) is crashing always I click on "import media", as showed in this screen-recording: https://goo.gl/9gTHnx

It also crashes (https://goo.gl/qQDXcw) when I drag&drop wmv files from Windows file explorer into timeline (sample file: https://goo.gl/kXbbDJ)

Has someone faced this issue? Any idea on how to import media without Vegas crashing?
Thanks!

@rik
I suspect this audio level problem is caused by the default pan type for the audio tracks used in VP15. Try setting the pan type to "Add Channels".

@rik
I suspect this audio level problem is caused by the default pan type for the audio tracks used in VP15. Try setting the pan type to "Add Channels".

Yes...you nailed it Marco.

That is exact the cause of the problem.

The problem solved for the future now, by changing it inthe "default track properties".

But....i cannot understand why the "pan properties" is set default to "constant power"???

This "constant power" is for using mono-sources...

I guess it is a little minority of vegas-users to place mono-files on their tracks

The panmode:"add channels" (or 0dB setting) seems therefore to be more logical imho.

I would like to know if the Panasonic V-Log L color space from Lumix GH5 it is support. I have installed the trial version, which one of these is the V-Log L?

Panasocnic V-Log-V-Gamut,
Panasonic Curve V-Log
Panasonic Linear V-Gamut

Thanks

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Iauto-sync for multicam,

I use Plural Eyes, it's expensive but time saver and compatible with Vegas Pro :)

How can I reach a simplified Chinese in Vegas Pro 15.0.

I have tested Vegas Pro 15.0 .

But I find that 15.0 can't be switched to simplified Chinese by changing

registry language ID.

In 14.0 this method is valid but it can't work in 15.0.

Someone help me！

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

I had this once, in VP12, and I figured maybe it has something to do with nested projects. And so I moved those temporarily out of the way, after which the project loaded again. Then I figured maybe I should not do nested projects anymore.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

When I get UNDO issues I clear out my Vegas Temp directory to a "keeper" directory. Often this does the trick and gives me a chance to investigate just where the problem is.

Now, keeping the Vegas Temp directory viewable as Vegas fires up and I can see the UNDOs and REDOs being generated and, hopefully, vanishing when I close Vegas. Do you see this happening or what else are you seeing?

I would like to know if the Panasonic V-Log L color space from Lumix GH5 it is support. I have installed the trial version, which one of these is the V-Log L?

Panasocnic V-Log-V-Gamut,
Panasonic Curve V-Log
Panasonic Linear V-Gamut

Thanks

I have used v log v gamut with success.

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

I had a very large 2 hour long movie project once that I worked on for two years so I have some experiences with lots of Vegas bugs. I know even before it crashes that it's working hard to. I realized that when I give instructions faster than Vegas can handle them it would crash instantly, so I realized that it doesn't matter how good the PC is, you have to take every step in "Vegas tempo". The same applies to undo, SAVE before every important undo. The golden rule is to Save you project in every 3 minutes during your editing processes and save a new project file - number them 0022 - in every 10 minutes, so any time Vegas decides to not open one or to crash you still have your work. At least this is how I work on large projects using Vegas Pro. Safety is first, since I had lots of bad experiences when I couldn't get my 3 hour work back sometimes.

Try to start Vegas in full default mode be holding left CTRL+SHIFT and open the .exe that way, then check the box that appears.

 I don't want the program to crush for a simple CTRL+Z - undo. :)

So far I test out, no issue with 'wild' undoing.

Usually it works normally but sometimes god knows why it just makes the program to crash. I can tell some situations when it's more likely to happen, but I will screen record my editing process and I will show you guys what I'm talking about in the next weeks.

Examples when it's more likely to crash: 1. When I undo more times at a time. 2. In large projects (lots of sound and video tracks) when I messed a lot with the Auto Ripple tool before. 3. When I do lots of small edits, modifications and I use more tools at a time it just happens.

I can't reproduce it intentionally, always different undo actions kill it.

Ctrl Z caused a mega crash for me. Ruined my project that I'd been working on for hours. The project freezes at 65% every time I try to load it (after a complete reboot). Even the backup of the same project won't load... same deal - freezes at 65%. Other projects from VP14 load. This was the one and only VP15 project I had and of course it wouldn't open in VP14.

HELP!

The second thing that helped me once when nothing helped is closing the Project Media Window.

Open Vegas Pro, close the Project Media Window then restart it and open your project.

I save the project with every edit. I have gotten in such a habit of doing so that it does not bother me. One time I got in a big hurry and did a flurry of 'undo's' that Vegas literally destroyed the video file on my hard drive. It did not delete it, it messed it up to not being usable at all. Good thing I had a backup. And speaking of backups, backups are NOT an option! They are a must! And I use more than one backup drive for my projects.

I noticed that when I press CTRL+SHIFT+C it hides the event header buttons with the media info. Can I somehow hide only the event buttons?