Hello everyone, I created this topic to see how many people would like the VEAI team to return to the old GUI for version 3. As I mentioned on the GUI V.3 release topic, it is Clearly, I don’t really appreciate this new interface, which is very messy and not really easy to use. Why would you want to start from scratch, when we had a nice graphical interface since version 2, why didn’t you want to deepen this already existing interface even more? The developers of VEAI could have simply added new options that would complement the old original interface even more. However, they could also have added the new export codecs to the old interface. Why start from scratch and recreate an interface? This will make you waste time, for you developers, adding things and things each month and so on… Me in your place, I will have continued with the interface that already exists while adding new ones options, to complete it even more.
Afterwards I don’t know if I’m the only one who thinks it’s better to stay on the original interface, but for me the new interface is really not great, great… I’m sorry to tell you inform but at least I said my opinion. Hoping that this one will really serve to make you think about the developers, to be able to come back to the old one and complete it. You will lose, waste a lot of time recreating a new GUI. Please stay on the old one.
I have yet to test the new v3, but based on screenshots I’ve seen, it looks like a downgrade in a lot of aspects. I’m personally a fan of continuity, where all AI Topaz apps share a similar design, but of course, VEAI is a bit different, because it offers more control over the end result.
Yes v2 GUI is much better as of today. Once we start refining the GUI and get into beta territory with v3.0, I hope you would agree that 3 > 2.
The fundamental reason for a new GUI design was to allow simultaneous workflows. The v2 GUI has processing baked into it, leading to scaling/background processing issues. Anyone who noticed a difference in processing speed when the GUI is in foreground vs background or needed to run multiple instances of VEAI to max out GPU usage has encountered the issue.
The 3.0 GUI backend separation allows us to add features faster, allow remote processing flows, enable background processing etc.
Lets see how you guys feel when we get close to the release.
I was about to post a reply to this but yours covers it 
Thanks @suraj
I understand your answer. I will give my full opinion as soon as version 3 is stable in the coming weeks or months. 
For the moment I will stick with 2.6.4 and alpha 3.
What do you hate the most, the way it looks or is there something you could do with 2.6.4 you cannot do with 3.0?
the encoding speed is faster on the old version, and the GUI of version 2 is more simplistic. Your new interface I find more messy. and less easy to manage. Like I said above, it’s just my opinion. 
The good news is the v2 GUI is a subset of the v3 GUI, so it should be possible create a basic user mode and have it behave exactly like v2.
I prefer by far the old preview system when we could see the frame by frame rendering now why does it have to render a MOV video file and wait until it has finished
I think GUI v3 much better than v2
For you maybe, but don’t for me.
It’s an alpha. It would be unfair to compare a fully-featured, released product to an early preview.
The v3 GUI so far is not that bad, although it needs some refinement. Somehow the look & feel is a little off, but nothing a new font and polish will not change. The major drawback currently is the odd action selection on the right column, ironically less intuitive than just having the preset menu already opened.
Except for that I think it’s going in the right direction, and I’m fairly sure that the final product will not look much better anyway.
Coming from GUI v2 it took me some time to get familiar with GUI v3. Now being used to it, I prefer the logic of the new layout, and vote to stay with that, because it is clear and easy to handle.
The UI of v2 is much better than the v3… But it’s still too early to tell since it’s probably just a mockup for now.
Bad: Having to wait for a preview to finish rendering before seeing anything. With v2, I can stop the preview after a couple of frames if it doesn’t look right.
Bad: Not having the option of single view (much easier to see the ‘before/after’ difference).
at least they can make this old preview option optional, so we can turn it on or off because the new preview render is considered a bad downgrade, unfortunately.
The option to save multiple previews is nice and a welcome improvement, but they’re hard to compare without single view mode so I hope that that returns in a future version.
Would also like the option to jump to specific frames again too instead of only having timecodes.
I guess I’ll decide if I can use the new 3.0 after the alpha stage is over and it’s in beta. As it is the GUI is way too different and makes no since with my work flow. Once the beta is ready then maybe I can make a better decision on spending the money to update to VEAI 3 but right now it’s just so different that it slows me down. It reminds me of going from Windows 7 to Windows 8 and that didn’t work out too well.
For now, I’m sticking with the latest version 2 because it’s much better than alpha 3. I really regret that the VEAI team doesn’t want to continue developing VEAI 2. It’s unfortunate because this version was well and deserved to be further developed for the years to come.
Farewell VEAI 2 it’s very sad 
