Sayonara Corel 2019, Hello 2018

[tletter]

Where are the bombs ?

As you seem oblivious to what you've written, one of your "bombs" in viewtopic.php?f=1&t=64958 is:

I will inform my credit card company not to pay the bloody blackguards.

However, it sounds like insulting people is just the way you roll if you don't immediate satisfaction for whatever is bugging you.

tletter
https://www.youtube.com/user/tletter

[canuck]

I did some more testing...

If you have 2 clips adjacent to each other and you add a clip between them, a transition is added since the clip being added overlaps the right hand clip.
If you open the gap between the two clips so that the gap is longer then the duration of the clip you are trying to insert, no transition is added since there is no overlap involved.

I guess what should happen is that the right clips should be moved to the right by the length of the clip you are trying to insert. Basically some sort of "remapping" is required.

[Ken Berry]

I think pepegota's point is that this didn't happen in VS 2018 and earlier versions. So it is an unwelcome new addition to VS 2019. Unfortunately, with the introduction of gaps in the main timeline, this is only one of several unexpected and unwanted "novelties"!

[pepegota]

tletter, I guess you did not read on.
"It was not deception by Corel but, a problem with the software download which later was resolved. Their technical support did not solve the problem-not too good. I recant and apologize my statements about Corel, as I was just POed with the first result. I have been with them since Ulead days and should have known better."

[lata]

Thanks Pepegota
We all get frustrated it some time, the change to the top timeline and the use of gapping seems to be affecting the function of the timelines of which Corel are aware.
As all issues seem to be related, fix one and all others should follow.
Nick from Corel has replied to your other post, we await his update here.

viewtopic.php?f=1&t=64965&p=365437#p365437

[tletter]

We all get frustrated it some time

The odd thing in in this case is that VS2019 is a new version so any bugs do not affect existing VSPs rather it only affects folks who want to be first adopters. On the other hand, current users of VS2018 have experienced bugs that do affect the rendering of existing VSPs, i.e. VideoStudio 2018 Update 2 using SmartProxy files instead to source video files whilst rendering. Hence all this VS2019 sturm und drang seems over the top as very major software release has issues, e.g. Windows 10 initial release, that are sorted out over time. Whilst these bugs are addressed, VS2019 early adopters can still use VS2018 to render VSPs.

tletter
https://www.youtube.com/user/tletter

[Desertsweeper]

I just got offered the 2019 version and am downloading it as I type. Yup I am jumping into the deep end and yup I struggled with 2018 as an early adopter. I probably bitched about it too. But at the end of the day it all worked out. And here goes again...keeps you occupied and out of worse trouble

[RobertOZ]

Desertsweeper, I notice that you are using Win 7 Pro, it might not affect you, but are you aware that VS2019 no longer supports AC3 Dolby audio codec

[Desertsweeper]

Hi RobertOZ, actually I need to update my profile. Yes i am still using Win7Pro (Die hard) but I am now on a Core i7-7700K using iGpu - which never worked with the first release of VS2018 - used to crash on render. But they fixed that and it works great now. I do not use that audio codec so not an issue for me. Anyhow my initial reaction to 2019 is WTF happened to "split" in the right-click fly-out menu on the timeline...gone! I sucked in some 4k Drone footage shot in D-Log and played with the colour-correction - awesome!

[lata]

Hi
As far as I am aware the Split Clip from the drop down menu will be replaced, I do not believe that was intentional to omit that.

Shift + S is the keyboard short cut for Split Clip
Other options on that context menu have been re-arranged

[iNate]

We all get frustrated it some time

The odd thing in in this case is that VS2019 is a new version so any bugs do not affect existing VSPs rather it only affects folks who want to be first adopters. On the other hand, current users of VS2018 have experienced bugs that do affect the rendering of existing VSPs, i.e. VideoStudio 2018 Update 2 using SmartProxy files instead to source video files whilst rendering. Hence all this VS2019 sturm und drang seems over the top as very major software release has issues, e.g. Windows 10 initial release, that are sorted out over time. Whilst these bugs are addressed, VS2019 early adopters can still use VS2018 to render VSPs.

tletter
https://www.youtube.com/user/tletter

Honestly, if you can't even edit UHD H.264 with QSV Decode Support, then you need to upgrade your PC. The Accelerated Decoding makes this about as easy to edit as 1080p with CPU Decoding. I would never edit HEVC directly, it's the worst delivery CODEC to edit (along with VP9). I wouldn't even bother using smart proxies, as the quality is too bad for decent finishing (Color Correction, Chroma Keying, Compositing, etc.). I'd just transcode that stuff to HQX and install the Grass Valley CODEC to make it editable in VideoStudio. IMHO, they don't give us enough control over the types of Proxies the application creates.

In 2019, the application really should be proxying to 720p low bitrate H.264. PCs that can't edit that fluently with HW Decoding need to go to the landfill. That was hard to edit like 15 years ago.

Can anyone say whether or not you need QT installed to Export Alpha Channel Videos from VideoStudio 2019?