Used Multi-Cam to combine 4 videos from 4 different cameras (Lumix digital 1- MTS - 1920x1080, Canon digital 2 - MTS - 1440x1080, Hero5 GoPro 3-MP4 2704x1520, Sony HDR CX210 4-MP4 1280x720).
Saved edited Multi-Cam and it showed up on my samples folder.
Drag it into a new project set for 1920x1080 and it warns it must reformat, ok.
Plays fine in editor. Go to Share MGEG-4 AVC (1920x1080, 30p, 15Mbps) standard format.
VS on C 512GB SSD and videos on 2TB 7200 HDD. Length of the compilation is 16 minutes.
Click 'Start' and rendering starts and continues until 85% complete. Then error:
Unable to load library
19151:3:3
Only option is 'ok'. Attempted twice. Exited VS. Rebooted computer.
(For reference, for the same event I had 3 of the above cameras (no GoPro) and 24 minutes of Multi-Cam compiled length. A different issue occurred with Multi-Cam, but in the end, I rendered to the same format with no issues.)
Rendering Error: Unable to load library 19151:3:3
Moderator: Ken Berry
-
larsonmw
- Posts: 2
- Joined: Tue Jan 28, 2020 3:44 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Asus P8Z77-V Ivy Bridge
- processor: Intel i7-3770K 3.50GHz
- ram: 16GB DDR3
- Video Card: nVidia GeForce GTX 670 2GB GDDR5
- sound_card: Realtek Digital Output
- Hard_Drive_Capacity: 4.5TB
- Monitor/Display Make & Model: ViewSonic VX2255wm-4
- Corel programs: VS 6SE, VS9, CVS X4, X8, 2018, 2019
- Location: US
- lata
- Site Admin
- Posts: 14280
- Joined: Thu Jan 19, 2012 6:21 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASUSTeK COMPUTER INC A88XM-A USB 3 1 Rev X 0x
- processor: 4 10 gigahertz AMD A10-7890K Radeon R7
- ram: 16 gb
- Video Card: on board
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 500 SSD
- Monitor/Display Make & Model: LG W2242 [Monitor]
- Corel programs: CVSX, 19, 20, 22 PSP2023, PI, MS3D
- Location: UK
- Contact:
Re: Rendering Error: Unable to load library 19151:3:3
Hi
And welcome to the forums
I don’t understand the warning to “reformat” after dragging to the timelines? But would assume is the cause for the fail at 85%
I can only assume the program does not like the mix of at least one of your video files
What is on the timeline at 85%, if it is lets say the 1440 x 1080 then are you able to convert that video to 1920 x 1080 (your output settings) then use in MCE
And welcome to the forums
I don’t understand the warning to “reformat” after dragging to the timelines? But would assume is the cause for the fail at 85%
I can only assume the program does not like the mix of at least one of your video files
What is on the timeline at 85%, if it is lets say the 1440 x 1080 then are you able to convert that video to 1920 x 1080 (your output settings) then use in MCE
-
larsonmw
- Posts: 2
- Joined: Tue Jan 28, 2020 3:44 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Asus P8Z77-V Ivy Bridge
- processor: Intel i7-3770K 3.50GHz
- ram: 16GB DDR3
- Video Card: nVidia GeForce GTX 670 2GB GDDR5
- sound_card: Realtek Digital Output
- Hard_Drive_Capacity: 4.5TB
- Monitor/Display Make & Model: ViewSonic VX2255wm-4
- Corel programs: VS 6SE, VS9, CVS X4, X8, 2018, 2019
- Location: US
Re: Rendering Error: Unable to load library 19151:3:3
Thanks Trevor - I did some investigating last night and it is SOLVED now. Here's the story for anyone else interested in this issue. BTW, this is in VS 2019 Ultimate (sorry I forgot that in my original post).
I started by like you said examining the content at around 85% of my timeline. My third camera was my Hero5 GoPro and I ran it at '2.7K wide' instead of 4K to avoid having to correct for lens distortion later but even at that resolution and the duration of the video it created two video files. I thought maybe some small 'break' between videos was the problem. I trimmed off the 'back end' of the performance before that second video and the first 2/3 rendered okay. So then I more closely examined the multi-cam in that area.
I like the multi-cam editing and ability to add transitions (all crossfades at this point but can be changed later) so I added crossfades at each camera change. When I was scrubbing along the timeline and I came to the area where the second GoPro video file was available but the timeline still showed I was on camera 1. HOWEVER, as I scrubbed along there was a transition on my output screen to the GoPro video! This was not shown graphically on the timeline. So, my conclusion is that I had added camera changes initially and then went back to clean up the amount of time on camera 1 and camera 3 (GoPro) and somehow, VS allowed me to OVERLAP, the two camera feeds with NO graphical indication and it 'buried' the transition leaving the graphic on the timeline looking like only camera 1 was active. So, the rendering engine probably got confused by this and didn't like it!
Lesson here: be careful after selecting cameras and creating transitions if you make ANY changes to the length of a 'clip' created by a camera change. This issue cost me 12 hours of debugging the last 3 nights and made me miss my due date to my customer - my wife
!!
Side comments - VS 19 is VERY buggy - as you can see in my profile, I've been using VS many years. Early versions capturing VHS-C or DV was touch and go but now with higher resolutions and bigger files, rendering is iffy. Those issues are expected. But, 'crash out of the blue', 'crash on file save', 'hang during editing' issues have really made me question the future of VS with this 2019 version. I upgraded earlier than usual from 2018 to 2019 to add morph and seemless transitions as well as MCE but if the software won't run, the added features don't mean much. I don't want to 'cross streams' here but just comment that I am struggling with other issues than just this one with this version. I may post more details separately if I find they continue, are repeatable and avoidable.
I started by like you said examining the content at around 85% of my timeline. My third camera was my Hero5 GoPro and I ran it at '2.7K wide' instead of 4K to avoid having to correct for lens distortion later but even at that resolution and the duration of the video it created two video files. I thought maybe some small 'break' between videos was the problem. I trimmed off the 'back end' of the performance before that second video and the first 2/3 rendered okay. So then I more closely examined the multi-cam in that area.
I like the multi-cam editing and ability to add transitions (all crossfades at this point but can be changed later) so I added crossfades at each camera change. When I was scrubbing along the timeline and I came to the area where the second GoPro video file was available but the timeline still showed I was on camera 1. HOWEVER, as I scrubbed along there was a transition on my output screen to the GoPro video! This was not shown graphically on the timeline. So, my conclusion is that I had added camera changes initially and then went back to clean up the amount of time on camera 1 and camera 3 (GoPro) and somehow, VS allowed me to OVERLAP, the two camera feeds with NO graphical indication and it 'buried' the transition leaving the graphic on the timeline looking like only camera 1 was active. So, the rendering engine probably got confused by this and didn't like it!
Lesson here: be careful after selecting cameras and creating transitions if you make ANY changes to the length of a 'clip' created by a camera change. This issue cost me 12 hours of debugging the last 3 nights and made me miss my due date to my customer - my wife
Side comments - VS 19 is VERY buggy - as you can see in my profile, I've been using VS many years. Early versions capturing VHS-C or DV was touch and go but now with higher resolutions and bigger files, rendering is iffy. Those issues are expected. But, 'crash out of the blue', 'crash on file save', 'hang during editing' issues have really made me question the future of VS with this 2019 version. I upgraded earlier than usual from 2018 to 2019 to add morph and seemless transitions as well as MCE but if the software won't run, the added features don't mean much. I don't want to 'cross streams' here but just comment that I am struggling with other issues than just this one with this version. I may post more details separately if I find they continue, are repeatable and avoidable.
