VS 2018 bugs

[blahemy]

We've been using VS for three years and encountered multiple bugs and faults, but the latest version is far beyond worst expectations.
- AAC input is advertised, but in fact it doesn't work. Similarly 2 years ago XAVC input was advertised, but VS didn't recognise such files. They simply don't exist in the software's file browser.
- MP4 videos downloaded from Facebook appear without sound after being added to the timeline. Shortly after VS crashes. Support guys suggest you should 'simply' convert a file in a third party convertor and only then will you hear the sound in VS. (proof screen https://yadi.sk/i/iL6o0o_BJGW96A)
- Random clicking noise appears in MP4 videos shot even on DSLRs. Sometimes they migrate to the final, rendered video files, although output file properties are correct.If they don't migrate, it's still a torture to edit a video with this rubbish.
- Working area collapses during titles editing. This is outrageous, you can't work properly like this. See for yourselves:
https://www.youtube.com/embed/qqgycOAVTnk
But what shocked us even more, is that the support guys first ignored this question, and after some persistence finally answered that they know it's happening and they hope to cure it in the next SP. Seems they don't care people need to make titles all this time until the new service pack. (proof screen https://yadi.sk/i/U61_JZIQ8DwwgA)
- Almost no Russian fonts for titles.
- Not only is the product revolting, but the quality of the support is also digging the rock bottom. Instead of assuring people that there really is a bug and they'll try to fix it ASAP (and actually doing it) they try to make you believe that bugs aren't really bugs and if some other software works better - it's no advantage, but a drawback of that software (!) (proof screen https://yadi.sk/i/DnT-NwuUALyJZw)
Lately they've even stopped answering. This is totally appalling for the yearly $70.

Have you encountered something like mentioned above?
Did you have similar experience with the support team?
Is this OK to you?

[lata]

Hi blahemy
and welcome to the forums

1 / The first link from the reply Corel Support does seem to cover the problem.
XAVC the complaint was 2 yeas ago, do they work now? You may have to provide a sample.
Downloading files from the internet can be troublesome as the download managers can recode the files, thereby not receiving the original uploaded files.
Different download managers do give different results, I find the Torch Browser pretty good.
As recommended the only option is to convert the files to a more editable format.

2 / The second link seems to indicate an unusual UI layout, unless you have set and saved that as one of the Custom options
Yes I have experienced my UI reverting to this layout followed by a crash of the program, I do not get as far as your video as VS simply closed
I have to say that since SP3 I have not experienced that UI issue?
I had also reported this to Corel.

3 / The third link refers to focus area boxes and also ACC audio.
Not fully explained and taken out of context, so do not fully understand the issues here.?

4 / again does not explain the original problem only your disapproval to Corels reply to you.?
Random clicking with clips placed on the timeline, not experienced that, but there was an issue of clicks after rendering, was quite difficult to replicate.
MP3 audio using the Lame Codec has / is a cause for concern

Hopefully the next update will address these and other issues.

[Scubbie]

I have on occasions had a problem with the UI change in an unexpected manner, but never when editing titles in the way you have shown in the 2nd issue video.

My resolution has been:

1. Move the video preview so that it floats above the main layout
2. From the menu at the top of the screen select <Settings> <Layout Setting> <Switch to> <Default Layout>
3. Alternatively press <F7> after floating the preview section (1.)

Like Trevor, I haven't had this issue with the current version of 2018.

VS will use a variety of different fonts, but I have found that some do not work correctly. This isn't something that is limited to VS for those specific fonts. Although I don't currently have them all installed, I do have access to a large library. Typically for me, it is specific symbols, such as the (c) symbol for the videos I use.

• If I were experiencing a specific issue with a font set I would look at the following:
• Is it just this font set?
• Is the issue restricted to just VS? Check my Windows settings and the keyboard and language settings. I would also consider looking at adding a batch file (autoexec.bat) to utilise the keyboard.sys file, just in case.
• This can be removed later if it proves not to resolve the issue
• Is there a similar one available which I can use instead?
• Search the Internet for an alternative font set (there are many around)
• Contact Corel's tech support with specific details of which fonts are having the problems and consider sending the files so that they can try them

I know that my issues are not the same as your own. Hopefully, the list above may prove to be helpful.

All the preset titles come with their own fonts. However, they are ALL able to be tailored to your specific needs. You can then save them as your favourites. I would also suggest that you put them all into the timeline and save that as a project (.vsp) file so that you can import them easily at a later date should you need to. I have done this with a few titles which I've personalised in the past and have benefited from this action on many occasions.

Personally, I've not had a problem when I've contacted Corel's support team in the past. I haven't needed to contact them recently. I can't comment on your own experiences as I'm not party to the entire exchange and it wouldn't be appropriate for you to share it with me anyway.

[tletter]

- Random clicking noise appears in MP4 videos shot even on DSLRs. Sometimes they migrate to the final, rendered video files, although output file properties are correct.If they don't migrate, it's still a torture to edit a video with this rubbish.

VS adding blips in the audio track is a well known problem - see viewtopic.php?f=1&t=61761&p=352602

- Almost no Russian fonts for titles.

Have you tried adding Russian fonts to your Windows OS?

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

[Scubbie]

Strange things happen I guess...

Yesterday I experienced the issue mentioned above. It's the first time I've seen it and I wasn't editing any titles at the time. I was trimming a clip in a project's timeline.

I did try the workaround solution I mentioned above and it worked first time.

[MikeA]

i have encountered a number of bugs in this 2018 VS version. Things happen that never used to happen before and make working with VS irritating. However, overall, I can still get what I want, with a bit of a struggle. Please fix them.
The things I see are:
1. Random crashes of the program for unknown reasons. This is a new one to me. Never used to happen.
2. If you delete a thumbnail in a library and then go out of that library and back, the thumbnail re-appears. I have had thumbnails disappear from the library too.
3. The layouts are still unpredictable. I can save a layout and later it doesn't apparently exist.
4. I get random 'corrupted video' file messages for no obvious reason, even when the clip is a still and not real video.
5. Relinking doesn't work very well. Certainly not intelligently (link a file but other files in the folder are not relinked automatically).

M

[blahemy]

Thanks for a warm welcome, Trevor!

Downloading files from the internet can be troublesome as the download managers can recode the files, thereby not receiving the original uploaded files.
Different download managers do give different results, I find the Torch Browser pretty good.
As recommended the only option is to convert the files to a more editable format.

Seriously, I'm very much certain no VS-user should be bothered by things like this. MP4 is the most common format nowadays, people download videos like crazy. Problem with audio within the downloaded mp4 files is simply a plain defect of the product which ought to be fixed. It's rather strange that some people would suffer but still try 'to look on the bright side' of a faulty product they've bought. I understand when somebody from support tries this with an unsatisfied client (although doubtful tactic for company's public image), but users loving their torture and trying to justify it - sounds like Stockholm syndrome or possibly BDSM-club and is something quite unusual for the software market...sorry, I'm really surprised.

2 / The second link seems to indicate an unusual UI layout, unless you have set and saved that as one of the Custom options
Yes I have experienced my UI reverting to this layout followed by a crash of the program, I do not get as far as your video as VS simply closed
I have to say that since SP3 I have not experienced that UI issue?
I had also reported this to Corel.

Lucky you! As far as people further explain, this still is quite a problem even after SP3. Someone experienced UI layout fluctuations in different situations (not editing titles), but the fact itself is quite important.

3 / The third link refers to focus area boxes and also AAC audio.
Not fully explained and taken out of context, so do not fully understand the issues here.?

Yeah, the problem is pretty much there: AAC audio is still not recognised by VS. It just wouldn't show it in the library although the AAC-file is in the same file with something else. (images: https://yadi.sk/d/YYGqCoVbEsiBpA)

4 / again does not explain the original problem only your disapproval to Corels reply to you.?
Random clicking with clips placed on the timeline, not experienced that, but there was an issue of clicks after rendering, was quite difficult to replicate.
MP3 audio using the Lame Codec has / is a cause for concern

The problem is that support people could react differently - report the problem to developers, so the latter could eliminate it. Instead of tales about other video editors 'being bogged down' by their ability to read everything correctly.

[blahemy]

So guys, I’d like to finally share what surprised me most in this whole story. It’s DISAPPOINTMENT. This is the right word that springs up in my mind concerning this Corel product.
I remember how in 2016 we shot an MXF video using really expensive camera, and just a couple of days before we’d bought Video Studio Pro.
At that time product’s website colorfully advertised its perfection and functionality. One of the advertised 'achievements' was the ability to work with MXF files. We were glad and looking forward to editing process. So we finished filming and were about to start editing, when suddenly it turned out, that VSP just wouldn’t show the source videos. It just wouldn’t recognise MXF. I remember well sending support guys those MXF files and that very member of support team Auz trying to convince us, that those MXF files were kind of wrong, but should they be right - VSP would allegedly work properly, which already sounded like lies at the time. It seems, they just took us for idiots.
See for yourself his 2016 letter: https://photos.app.goo.gl/wr9KHYWbUeFUhyiF6

Some people claimed here, that MP4 files I download from Facebook for editing later are special in some way, and that this is the reason why VSP wouldn’t work properly with them: sound vanishes from the file placed on the timeline and the editor crashes shortly afterwards. You’ve written something about converters and containers. But can you tell me, just why all these files are correctly played by built-in Windows Media Player? Why are those files perfectly fine for Adobe Premiere?

Now I’d like to address sound ‘scratches’ and ‘blips’ emerging after placing DSLR-shot MP4 files on the VSP timeline. This bug is already several years old. It migrates from one version to another and nothing changes. Just consider this: source file with a high quality sound, which can be very well recognised by Windows Media Player turns faulty after being placed on the VSP timeline! How is this even possible? Why wouldn’t the support fix this tremendous bug? What is Corel charging money for? This is total shame.

Let’s proceed further. It was advertised that VS 2018 would work with AAC files, but in fact they are not recognised. The file browser of the program simply wouldn’t show any files of this format. They initially can’t be worked with as the editor simply can’t recognise them as a file!

And last but not least, comes this random working area ‘collapse’ of the whole program (see again how it happens https://youtu.be/qqgycOAVTnk)
You won’t believe it, but the support guy Auz suggested to close the ticket on this problem - as if the incident is resolved and the problem solved! How is this possible? Why does the support answer some ridiculous mumble-jumble - instead of fixing obvious major bugs? Do they realise they ruin their company’s reputation? Aren’t they afraid of being sued for false advertising?

[lata]

Hi
The image you attempted to attach to the post does not download?

As for the YT video showing the unusual UI layout and finally followed by a silent crash, yes I have experienced that and indeed reported to Corel.
I do not have a solution nor understand why as I am unable to replicate each instance.
Just a random behavior that I cannot explain.

I do know that a new service pack is on the cards SP4, hopefully that will address some outstanding issues, I do not have privy to what the next SP will actually address.

[Scubbie]

Hello blahemy,

I am sure that the team at Corel will have picked this up.

I know that there is a huge range of Codecs out there and I too have been having some issues with some videos which I downloaded from Facebook for a club project I'm in the process of editing together.

Rather than wait for a fix, I have been using VLC to convert the videos to MP4. In most cases, this has resolved the issue. In a few others, I've used Pinnacle Studio. I guess that this proves that there is the knowledge within Corel and that we need an implementation within VS.

However I look at it, it is annoying and there are some quick and simple methods available out there to help get us through them.

What I dislike more is FB changing the format of the videos that have been uploaded in the first place. In a few cases, I have now got hold of the original video that was uploaded in the first place. I had no such issues with them and was able to add them to the timeline in place of the lower quality version I had downloaded from FB in the first place.

I guess that FB will constantly battle to convert our videos into something more friendly for its platform. This means that all producers will face a constant battle as FB keeps adjusting to being optimised the latest mobile phone technology in every country possible.

Yours,
Robyn

[Ken Berry]

It was advertised that VS 2018 would work with AAC files, but in fact they are not recognised. The file browser of the program simply wouldn’t show any files of this format. They initially can’t be worked with as the editor simply can’t recognise them as a file!

This is really only a footnote to your other problems, but if you are talking about audio AAC files, then I am puzzled. In my case, VS 2018 and earlier versions all recognize, play and output mpeg-4 H.264 file with "MPEG AAC Audio" -- see attached screenshot showing output properties of a newly rendered clip. And I have any number of other mpeg-4 files from my smartphones and a 4K camcorder which include AAC audio which I regularly use, edit and reproduce -- indeed, taking it for granted. So perhaps I have not understood what your exact problem is with AAC...

[cdoughertycd]

I've been having the audio blips and cracks since VS7. VS6 and versions before didn't cause this problem. Something happened in the software. I'm shooting in MP4 and still have this audio problem, also had it when I shot in AVCHD. The original files when played outside of VS are fine. I've tried everything I can think of for all these years including taking computer to two computer guys. Reading this thread has helped though, in that it's not just me. When I called support last year they say to update the drivers. I did that but still have the problem.

Thanks for talking about this issue.

Candy

[Scubbie]

Hello cdoughertycd,

Are you able to provide more information about the files? For example, which camera are you using, what are you recording at (i.e. 1080 30p)?

Also, could you provide an image showing the file properties from Windows Explorer?

Whilst annoying and not ideal, have you tried using something to convert the clips prior to using in VideoStudio 2018? Occasionally I've had issues with content I've downloaded from Facebook and have used something to convert it so that I can get some audio. VLC can be useful in some cases.

[lata]

Hi Candy
I have ran a quick test using 2018 using new projects I cannot replicate the blip issue
However running the old test blip vsp still show the blip so could be part of the old project files.

Scubbie
A long ongoing issue, back using X7 there is no problems, after which all versions suffered.
A lot of reading here.
viewtopic.php?f=1&t=61761

I know Corel were involved with a lot of tests and brought a hot fix for CVSX 10.5 which was not conclusive.
I found replicating the blips quite a challenge but once you get the hang of it easy to do.
I used the audio clip from one of the Instant Projects T_02.VSP

There are some samples on my one drive, will give you an idea of the issues.
viewtopic.php?f=1&t=61761&start=30#p344231

[weaver]

Here. Are my recent experiences with VS2018:

viewtopic.php?f=1&t=64932