I'm sorry guys to throw a rock into the pool.
Just by coincidence I received an hour ago an Iphone6 mov file to check, as I was on my XP bootup I decided to run VSX7 and see how it's coping with the file.
Well, as long as I didn't do quick moves or rapid mouse clicks there was no problem at all. The file plays well (although vertically..) and mixes OK with the gecko that plays just as well. I added filters to the two clips and rendered to mp4.
The Iphone file is
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Rotation : 90°
Frame rate mode : Variable
Frame rate : 30.000 fps
Minimum frame rate : 28.571 fps
Maximum frame rate : 31.579 fps
The gecko file is
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 30.329 fps
Minimum frame rate : 30.090 fps
Maximum frame rate : 30.529 fps
X6 Pro started crashing. Tells 2 send in dump file. Where 2?
Moderator: Ken Berry
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
Re: X6 Pro started crashing. Tells 2 send in dump file. Wher
FWIW, I have no trouble at all with the sample gecko clip. It plays fine in both Clip and Project modes. With 'show message' selected, the Project Properties match those of the clip.
However, trying to render it to either 'Same As Project Properties' or 'Same As First Clip' produces an error message: "The Frame Size (1920 x 1080) of the Video File does not match the settings and therefore cannot be trimmed." So nothing can be produced. This is of course a bit confusing since 1920 x 1080 is part of the project settings and is absolutely standard for AVC video...
I then changed the output settings to Frame Based/Progressive NTSC AVCHD using 29.97 fps and 15 Mbps bitrate. Rendering was quick until it got to 96%, when rendering froze VS and I had to use Task Manager to close VS down.
I then tried rendering to a .mov file/mpeg-4 and this time it only got to 8% before VS froze again.
I snipped a short bit off the end of the clip, then rendered again with the above AVCHD settings, and this time the render completed without problem and the file played back smoothly. I can only assume there was something towards the end of the clip that VS did not like...
However, trying to render it to either 'Same As Project Properties' or 'Same As First Clip' produces an error message: "The Frame Size (1920 x 1080) of the Video File does not match the settings and therefore cannot be trimmed." So nothing can be produced. This is of course a bit confusing since 1920 x 1080 is part of the project settings and is absolutely standard for AVC video...
I then changed the output settings to Frame Based/Progressive NTSC AVCHD using 29.97 fps and 15 Mbps bitrate. Rendering was quick until it got to 96%, when rendering froze VS and I had to use Task Manager to close VS down.
I then tried rendering to a .mov file/mpeg-4 and this time it only got to 8% before VS froze again.
I snipped a short bit off the end of the clip, then rendered again with the above AVCHD settings, and this time the render completed without problem and the file played back smoothly. I can only assume there was something towards the end of the clip that VS did not like...
Ken Berry
- RobertOZ
- Advisor
- Posts: 2426
- Joined: Tue Jun 26, 2012 12:50 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Asus Prime B550M-A WI-FI AM4 mATX
- processor: AMD Ryzen 5 3600 3 6 GHz
- ram: 16GB
- Video Card: Asus Geforce GTX 1650 GDDR6 Driver 551 23
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 7 TB
- Monitor/Display Make & Model: Philips 32" IPS LED, Samsung 28" 3840x2160 UHD 4K
- Corel programs: VS2018/21/22/23 & MS 3D, MCC XL
- Location: Mornington, Vic. Australia
Re: X6 Pro started crashing. Tells 2 send in dump file. Wher
Exactly the same results I obtained Ken, but even with a shortened clip I still cannot edit the audio without X7 freezing. It seems that different computers are giving conflicting results, Trevor does not appear to have any issues with the clip except playback in project mode (jerky/jumping) which does not happen on my system, both clip and project mode play smoothly.Ken Berry wrote:FWIW, I have no trouble at all with the sample gecko clip. It plays fine in both Clip and Project modes. With 'show message' selected, the Project Properties match those of the clip.
However, trying to render it to either 'Same As Project Properties' or 'Same As First Clip' produces an error message: "The Frame Size (1920 x 1080) of the Video File does not match the settings and therefore cannot be trimmed." So nothing can be produced. This is of course a bit confusing since 1920 x 1080 is part of the project settings and is absolutely standard for AVC video...
I then changed the output settings to Frame Based/Progressive NTSC AVCHD using 29.97 fps and 15 Mbps bitrate. Rendering was quick until it got to 96%, when rendering froze VS and I had to use Task Manager to close VS down.
I then tried rendering to a .mov file/mpeg-4 and this time it only got to 8% before VS froze again.
I snipped a short bit off the end of the clip, then rendered again with the above AVCHD settings, and this time the render completed without problem and the file played back smoothly. I can only assume there was something towards the end of the clip that VS did not like...
Robert
-
vgribok
- Posts: 6
- Joined: Sun Oct 12, 2014 11:56 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: GIGABYTE MSQ87TN
- processor: Intel Core i3 4130T
- ram: 16GB
- Video Card: Intel HD Graphics 4400
- sound_card: High Definition Audio Device
- Hard_Drive_Capacity: 500GB
- Monitor/Display Make & Model: ASUS VH236H (1920x1080@59Hz)
Re: X6 Pro started crashing. Tells 2 send in dump file. Wher
Hi, All.
I made sure I run latest QuickTime - no difference. Other players play those MP4 files just as fine as they used to. X6 is still crashing.
The crashing of X6, I now realize, didn't start out of of blue: I simply had fewer Nexus 4 files than those shot with other cameras. Nexus 4 files were in the mix, but at the moment when X6 started crashing, I didn't realize I didn't use Nexus 4 clips before in my work. At this point I am pretty sure that X6 never worked well with Nexus 4 videos. Before this, I had sporadic crashes of X6 at seemingly random points during regular editing activities. That, why somewhat unnerving, was not annoying enough to bother others and ask for help. This one looked like t show-stopper until the WMV work-around. With WMV the problem is really only large size of clips and choppy scrubbing. Otherwise it's tolerable.
Thank you much, though, for taking time to help me and investigate the problem.
Also, for those whoa are still looking into this: I do not have X7 and can't use it as a work-around.
Thank you!
Vlad.
I made sure I run latest QuickTime - no difference. Other players play those MP4 files just as fine as they used to. X6 is still crashing.
The crashing of X6, I now realize, didn't start out of of blue: I simply had fewer Nexus 4 files than those shot with other cameras. Nexus 4 files were in the mix, but at the moment when X6 started crashing, I didn't realize I didn't use Nexus 4 clips before in my work. At this point I am pretty sure that X6 never worked well with Nexus 4 videos. Before this, I had sporadic crashes of X6 at seemingly random points during regular editing activities. That, why somewhat unnerving, was not annoying enough to bother others and ask for help. This one looked like t show-stopper until the WMV work-around. With WMV the problem is really only large size of clips and choppy scrubbing. Otherwise it's tolerable.
Thank you much, though, for taking time to help me and investigate the problem.
Also, for those whoa are still looking into this: I do not have X7 and can't use it as a work-around.
Thank you!
Vlad.
