VideoStudio 2021 - Frame is Unreadable Error

[fltsimguy]

I am using VideoStudio 2021 for the first time and trying to compile a movie.
I am experienced with movie making and have used older versions of Videostudio many years back and other software not affiliated with Corel.

This particular movie has video clips, digital photos, voiceovers, music, and lots of transitions and effects.

I have saved the file and it runs perfectly on my PC. But when I start a compilation (share) it runs for 30 seconds and then stops and gives me an error "Frame 778 is unreadable"

NOW WHAT! I have no idea what this could be nor how it might be fixed.

Any help would be appreciated.
Bryan

[tletter]

But when I start a compilation (share) it runs for 30 seconds and then stops and gives me an error "Frame 778 is unreadable"

At 30fps, frame 778 occurs at about the 26 sec mark. Hence I'd suggest that you look at the video clip there for an issue. As a test, you could simply convert the video clip to another format using HandBrake and see if that resolves the issue.

Note that you're rendering to HDV (1440x1080), but you should be able to render to FHD in a 16:9 aspect ratio if desired.

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

[lata]

Fltsimguy
And welcome to the forums

The last time I saw that message the “Frame *** is unreadable “ referred to the length / duration of the actual clip.
If ntsc, approx. 26 seconds, for pal about 30 seconds.

If I recall correctly the problem occurred using a Ntsc wmv clip on a Pal timeline and applying reverse video, It was quite a while ago.

Your image shows the error occurring at 01:16:52.009, towards the end of the project
I would explore there for clips at 778 duration, explore what editing has been applied

[tletter]

If ntsc, approx. 26 seconds, for pal about 30 seconds.

As shown in the image, the OP is rendering NTSC at 29.97fps.

Your image shows the error occurring at 01:16:52.009, towards the end of the project

The scrubber location shown is simply the location of the scrubber when the user switched from the Edit tab to the Share tab, i.e. it doesn't show where the error occurred.

I believe that VS reports these types of errors at the frame count starting from the start of the project. Hence in this case, at 30fps (actually 29.97), frame 778 occurs at about the 26 sec mark from the start. Hence that'd be the place to look for an issue.

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

[lata]

Tletter
You may be correct with the actual error time.
But the Frame 778 as far as am aware is the actual frames of the clip not the position on the timeline.
Mind you it does not take that long to check both out

[fltsimguy]

Sorry to not get back on this....I have a vertigo problem right now and it's knocked me back a bit...I will take a look at some of this input.

"tletter" is correct the scrubber position was just random and had nothing to do with this issue.

[fltsimguy]

OK, I tried a number of things just as tests.
I removed clips differing each time and my errors changes to a differing number...IE "frame 310 is unreadable".

I have tried compilations using different formats, IE AVC, MPEG4, WMV, and each and every time, I watch it process, 1%, then 2%, and then crash and a frame error.

In my view right now what is really needed with this software is a log.txt that records successful and unsuccessful compilation as it moves along so one can see what attribute is problematic.

So far I can't get any joy as to what the issue might be.

[tletter]

It would be helpful if you post the properties of your source clips.

So far I can't get any joy as to what the issue might be.

A suggested test:

1. Convert a source HDV (1440x1080) video clip to a FHD video clip using HandBrake
2. Add the converted clip to a new VSP and let VS match the clip's properties

See if that resolves the issue.

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

[lata]

when the error occurs does the progress bar indicate at what %

Explore that % position, what files are there, what type? any particular edits applied, and clip duration just in case the "frame 310 is unreadable" is the duration of the clip.

I recall another user having a similar issue where removing the clip simply caused another error in another position, in that case turned out there were several corrupt clips.

Are you using clips from mobile phones that may be using a variable frame rate.

[fltsimguy]

It would be helpful if you post the properties of your source clips.

So far I can't get any joy as to what the issue might be.

A suggested test:

[*]Convert a source HDV (1440x1080) video clip to a FHD video clip using HandBrake
[*]Add the converted clip to a new VSP and let VS match the clip's properties

My files were originally sony cam .m2ts. I found out that this software will not process audio on these, which was my first great disappointment. They are 1440x1080 29 fps

I have a commercial video file converter, Xilisoft Video Converter Ultimate, which I then used to convert all video clips to MPEG 4, all the clips in the movie are 1920x1080 29 fps.

I looked up Handbrake and see it is a freeware converter, I don't see that I would gain anything using the freeware over my payware version, but perhaps I'm wrong.

All the MPEG4 video clips look great and play nicely in the VideoStudio software.

**********************************
So I tried this, I removed all sound voiceovers, and music layers, and still they would not compile.
I wiped out the entire video and only put a couple clips into the software and I could not compile. Something major seems to be wrong.

[Ken Berry]

Just getting back to your m2ts originals for a moment, is the audio on them Dolby? If so, that is most likely the reason VS cannot process it. For some totally mysterious reason Corel has dropped Dolby totally when it comes to Win 7, which I see from your Profile you still use. I think Dolby still exists under Win 10 but only dual channel stereo and not 5.1...

[fltsimguy]

OK update on this issue.

I have just bought PhotoDirector. I have now VideoPad, VideoStudio and PhotoDirector.
I have built the same movie in VideoPad, it fully compiled....but I don't like how slow it takes to compile and some of its features.
I build a 10 minute segment of my video identical clips into PowerDirector...and it compiles perfectly.

So the issue remains VideoStudio, something is happening that I can not find a solution...this is so frustrating because I like the interface and features.

I think I will look at uninstalling and reinstall or something.

[fltsimguy]

Just getting back to your m2ts originals for a moment, is the audio on them Dolby? If so, that is most likely the reason VS cannot process it. For some totally mysterious reason Corel has dropped Dolby totally when it comes to Win 7, which I see from your Profile you still use. I think Dolby still exists under Win 10 but only dual channel stereo and not 5.1...

I just checked and yes in fact my Sony HD Video Camera records sound only in Dolby. Well, I'll be darned. Yes, I have a dual boot PC and most of my software and addons and such were accumulated through Win7 Professional Days. I am slowly building my Win10 boot and eventually most of my tools and such will Win10. However, I have so much stuff requiring upgrades and updates I have avoided the full move to Win10.

[lata]

I would suspect it is a setting using Xilisoft Video Converter Ultimate that is causing a problem for Video Studio

Have you considered using Xilisoft Video Converter Ultimate to convert the originals to the same format m2ts but changing the audio stream to LPMC, that should allow you to edit the m2ts using VS and win 7
When converting take care to retain the original frame order, the original video may be using Upper Field First.
Of course If you could install VS to Win 10 then that would avoid any conversions.

[tletter]

If you post a sample video clip that doesn't render, then others can better help you.

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