Good idea - but why waste space to hundreds of meaningless icons when everybody knows how to do a simple right click ?

I'm editing on two 40 inch 4K monitors - and doing a lot of track compositing with many tracks I can not waste the space for the new headers - which anyway do not add any new functionality

They do add new functionality, just like instant freeze frames at cursor or selective paste event attributes.

... and which could not have been implemented using the right click ?

I was referring to the statement it would not have added new functionality, not to what could have been added elsewhere.

Anyway - using the new header icons the workflow is always one click faster than using the right-click menu. Also the right-click menu is somewhat overblown meanwhile. I have to search within 30(!) functions there.

I prefer that faster solution which also is more intuitive for me.

Anyway - using the new header icons the workflow is always one click faster ...

That's always the case. Consider you want just temporarily minimize a track. You need one click with the old design and at least two per track to fill the hamburger.

Generally enjoying finding my way around new features in V15, but two disappointments:

Just like V14 and V13, the last second of the last track of Audio CDs burned from the Timeline is getting cut off.   The final Red track marker is definitely one second after audio finishes, but on the burned CD, the ending of the last track is cut off – I have to move the final track marker a couple of seconds to the right and re-burn.    I can’t believe this only happens to me.

Also – we can still only create Timeline Markers in “rust” colour.     I remember requesting many years ago that we be given a choice of Marker colour.  I’m not a programmer, but I’m sure this would take very little time to implement, and the benefits would be considerable.     Here are a few possible reasons I use Markers – I’m sure there are many more - and each could have its own colour for easy recognition:

·         Chapters for DVD or Blu-Ray

·         To show where a new section of video begins

·         To show places where I want to insert Titles

·         To show places I need to do Audio work

·         To show places where voice over should start

·         Indication of a change in location

·         Places for sound effects

·         Places for Music

To be able to right click on a Marker and change its colour – it already has a property to make it a particular colour – this just needs to be made variable by user.

In addition, I just saw where the 0 dB line lies in the audio track, not in the center of the waveform but in the center of the track including the border, and so this is kind of a mess isn't it?

That has to be a symptom of very limited beta testing with people who are actually using the application in projects that actually matter. I would have noticed that in seconds. Knowing me I probably would have spent a few hours trying to work out where I was getting DC bias from before thinking "Hang on, is the meter in the right place?"

"Consider you want just temporarily minimize a track. You need one click with the old design and at least two per track to fill the hamburger."

The main purpose is to individualize your button line so you needn't touch the hamburger menu for each process. So in the end it is always only one click only. Also exactly that minimized track handling is much better now because you now still have access to the Event buttons (which isn't the case in earlier Vegas versions).

Also – we can still only create Timeline Markers in “rust” colour.     I remember requesting many years ago that we be given a choice of Marker colour.  I’m not a programmer, but I’m sure this would take very little time to implement, and the benefits would be considerable.     Here are a few possible reasons I use Markers – I’m sure there are many more - and each could have its own colour for easy recognition:

Yes, I wanted this as well for many years but I never requested this. I am using this for sound content marking to make music videos, and extract, beats, melody, etc. I also wanted colors for that, now I use labels like B:1 for beat 1, M:1 for music note one, etc .. I get a few hunderd of those when I do sound content marking, and then import them into Vegas for easy or precise positioning of timeline events, on the beat, music note, etc

The main purpose is to individualize your button line so you needn't touch the hamburger menu for each process.

This is still possible with a transparent top area using the whole track heights for the thumbnails. I do not want to get rid of the hamburgers but of the vertical space wasting topline.

In addition, I just saw where the 0 dB line lies in the audio track, not in the center of the waveform but in the center of the track including the border, and so this is kind of a mess isn't it?

That has to be a symptom of very limited beta testing with people who are actually using the application in projects that actually matter. I would have noticed that in seconds. Knowing me I probably would have spent a few hours trying to work out where I was getting DC bias from before thinking "Hang on, is the meter in the right place?"

That's what I have been thinking as well. In addition, as it shows Vegas has not really been designed for this, and so if you introduce this, the borders, you need to track down every inconsistency you created with this new, incompatible introduction, which can be a lot of work. And as it shows is hard to keep under control. Every piece of code that had not been adjusted will go on working like there are no borders at all, like we see...

My source video has two audio tracks, but in VP15 appear 4... Why?

Make sure that 'Import Stereo as Dual Mono' box is not ticked in Preferences/General.

My source video has two audio tracks, but in VP15 appear 4... Why?

Make sure that 'Import Stereo as Dual Mono' box is not ticked in Preferences/General.

It's already unticked so it must be doing it by default for some reason?

I was referring to the statement it would not have added new functionality, not to what could have been added elsewhere solution which also is more intuitive for me.

That is kinda turning the discussion upside down - but I still claim that the Hamburgers are/were not necessary to add the functionality you mention that they do.

Let us stick to the facts - and then stop the discussion here.

That said I will still buy the v 15 upgrade - but be grateful that we got the last v 14 update which seems to have improved its stability - and then hope for a future v15 update or v16 upgrade with a possibility to opt out the -IMHO - quite unnecessary and space consuming headers and hamburgers.

The main purpose is to individualize your button line so you needn't touch the hamburger menu for each process.

This is still possible with a transparent top area using the whole track heights for the thumbnails. I do not want to get rid of the hamburgers but of the vertical space wasting topline.

exactly my thoughts. The hamburger idea is OK, but not sacrificing valuable thumbnail space! I also find we need far more color options than just 8.

My source video has two audio tracks, but in VP15 appear 4... Why?

Make sure that 'Import Stereo as Dual Mono' box is not ticked in Preferences/General.

It's already unticked so it must be doing it by default for some reason?

See my reply on your dedicated post.

My source video has two audio tracks, but in VP15 appear 4... Why?

Make sure that 'Import Stereo as Dual Mono' box is not ticked in Preferences/General.

It's already unticked so it must be doing it by default for some reason?

See my reply on your dedicated post.

That fixed it thanks Nick!!

That fixed it thanks Nick!!

Don't forget you've changed that internal preference! You will probably want to change it back in the future!

All those ACES output transforms including 2020/2084 at 4000 nits, and still no HDR flag even for HDR-capable viewing hardware like Decklink?!!! Or am I missing sth...

Piotr

Has Resolve HDR metadata by now?

I meant preview; encoding is another matter and yes - even with Resolve export, the HEVC HDR flag I still add using ffmpeg....

Piotr

As usual, I'm blown away by the passion you all show for VEGAS Pro. I sincerely appreciate those of you who contribute here in a constructive way. I'm sorry for your frustrations when you discover something that disappoints you. That's the nature of development and the very prioritization balancing act that I have been working through. Sometimes I suppose I get it wrong, but hopefully we got some things right, too. I'd like to make a few specific comments that can hopefully remove a couple topics from this thread.

First, I am distressed that this thread has taken a turn toward disparaging the developers and our beta testers. The developers have done a great job implementing what I have asked for. If you don't like what has been delivered, blame me, not them. They are an amazingly talented team, and they deserve nothing but respect for what they accomplished for VP 15. As for our beta testers, this was far and away the most valuable and productive beta testing cycle I have ever been involved with. We had testers--yes, extremely talented and proven professional everyday editors--giving us feedback months ago when the application was still in the alpha stages. They helped us make huge improvements and found many bugs that you will never have to experience thanks to them taking time out of their busy production schedules to help give you a better product. They deserve thanks and tremendous credit instead of remarks questioning their skills and abilities. Again, if you don't like what you see, it is my responsibility, not the beta testers' fault.

Re: Hamburger menus. Some of you are missing the point. As Marco pointed out, these are about giving you the freedom to totally customize your workspace with the tools you use most often front and center. I am quite stumped to understand how giving you this type of workspace flexibility is in any way a bad thing, but I could be wrong. Yes, if you want a one-click path to minimizing your tracks, it take a couple extra clicks, the first time. But once you customize your track headers to show your minimize button, it is one-click from there on out. Forever. Unless you change it. The hamburger systems seems to me to be far superior to cramming yet more into the bloated right-click context menus. It is completely configurable so you can get exactly what you want instead of what we shove down your throat. I don't get how that is in any way a bad thing.

Re: Event headers. The beta testers gave us great feedback on these. Among them there was virtually a 50/50 split on whether they loved them or hated them. Based on their feedback, we have already coded the option to turn them off into the first free update to VP 15. For those of you who land on the "hate them" side, I'm sorry I can't get this option to you sooner, but in the not-so-distant future you will be able to turn them off and still have complete access to the hamburger menu system.

Re: the new PinP and Crop plug-ins. I can't tell you the number of requests we've gotten over the years for the ability to manipulate your video directly on the Video Preview window. As we investigated how to do this, it became clear that attempting to force the rather convoluted Track Motion and Event Pan/Crop code into doing this would be a huge effort that in the end would not provide the quality of result you demand. These new plug-ins are flexible (you are no longer restricted to creating a PinP only at the track level), and simple. How many of you even ever figured out how to do a true crop with the Event Pan/Crop tool? Did you even know you can create a true crop with the Event Pan/Crop tool? Those tools are clunky and about as non-intuitive as could be. The new plug-ins are easy, flexible, and do exactly what you'd expect them to do.

Re: "Why did you waste time on things like freeze frame when there is so much other stuff to do?" You have to understand a little about how development works. We have a talented, but small, team of developers. Each of them has a particular area of expertise, even as they are extremely flexible and willing to work wherever the code needs them. We have experience ranging from senior developers to junior. A couple of points to be made: #1 they can't all be working on the same area of code at one time. #2 a more junior developer may not yet be capable of working in complicated areas of the code. The freeze frame and selective attribute paste features are perfect examples. Some have complained that we "wasted" our time doing those. On the contrary, those were great features for our most junior developer to tackle, and both of those features have been requested countless times by you users. He did a fantastic job, you got two additional features that the more senior guys didn't have time to do, and because of the experience, our junior guy is now considerably closer to being able to work on more complicated tasks in the future. Any way you look at it, these features are a great win for you in the end.

Well, I'll stop now. I hope I cleared a couple things up for you even as I understand that some of you will now follow up by saying, "Fine, but you did not answer _my_ question." I get it, and sometimes I just need to ruminate on the issues before I comment further. Other times--particularly when the tone is rude and it seems that there is no answer that I can give that will stop the rudeness--I just need to let the discussion play out a bit before I jump in. In the end, here's a tip: being rude, disparaging our developers or beta testers (or anyone else involved), and posting endless threats to jump to a different tool are not nearly as likely to get you a measured response as is respectfully asking a question or stating your frustrations.

Thanks for listening...sorry for the long post.