using VS 2018 sp2 under windows 7.
I'm making a DVD of several small mini-movies, and the 1st step is to create an iso file to check it's all OK before burning.
The 4 content clips (an intro, used on past DVD with no problems, and 3 video clips all rendered OK as mpg files) were inserted in the disk composition, a menu selected, menu text edited and music added, and this is the build image
The preview played OK. But at step 3 (configuration to create an iso file in the background) I got this vague error message (see screenshot) as soon as the 'it will take some time advisory' was OK'd
I've tried a number of things to fix this, including
- run with the default menu music in lieu of preferred
- change the preferred menu music file from .wav to mp3
- convert one of the clips from wmv to mpg - so they are all mpg
- run the same disk file under x10
without any success at all: same message at the same point in the process. And since that message is so vague, I have no idea what might be causing this. Especially since everything including the preview stage was fine.
Can anyone make any suggestions what might be causing this?
Making a DVD iso file - convert step problem
Moderator: Ken Berry
- Davidk
- Posts: 2090
- Joined: Wed Nov 26, 2008 12:08 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASUS Prime B660M-K D4
- processor: Intel core i3-12100 3_3ghz quad core processor
- ram: 16Gb
- Video Card: on-motherboard Intel UHD 730 graphics chipset
- Hard_Drive_Capacity: 6Tb
- Monitor/Display Make & Model: HP E240c video conferencing monitor
- Corel programs: VideoStudio: 2022, 2023
- Location: Brisbane Australia
-
sylwester
- Posts: 35
- Joined: Thu Nov 28, 2013 11:52 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Location: Warsaw Poland
Re: Making a DVD iso file - convert step problem
If you use Hardware acceleration , make it of

maybe some problem as mine

maybe some problem as mine
- Davidk
- Posts: 2090
- Joined: Wed Nov 26, 2008 12:08 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASUS Prime B660M-K D4
- processor: Intel core i3-12100 3_3ghz quad core processor
- ram: 16Gb
- Video Card: on-motherboard Intel UHD 730 graphics chipset
- Hard_Drive_Capacity: 6Tb
- Monitor/Display Make & Model: HP E240c video conferencing monitor
- Corel programs: VideoStudio: 2022, 2023
- Location: Brisbane Australia
Re: Making a DVD iso file - convert step problem
Hmmmm.
There's 3 hardware acceleration items for file creation in the preferences\performance tab. Turned them all off, re-loaded the disk vsp, progressed thru each step to make sure nothing in the composition had changed, and tried once again to create a disk image file.
Fail, same result.
Even tried changing the menu theme (smartscene menus: at first I had selected one I'd not used before. When that failed, switched to one I'd used several times successfully). That as a bust too, same result.
There's 3 hardware acceleration items for file creation in the preferences\performance tab. Turned them all off, re-loaded the disk vsp, progressed thru each step to make sure nothing in the composition had changed, and tried once again to create a disk image file.
Fail, same result.
Even tried changing the menu theme (smartscene menus: at first I had selected one I'd not used before. When that failed, switched to one I'd used several times successfully). That as a bust too, same result.
- Davidk
- Posts: 2090
- Joined: Wed Nov 26, 2008 12:08 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASUS Prime B660M-K D4
- processor: Intel core i3-12100 3_3ghz quad core processor
- ram: 16Gb
- Video Card: on-motherboard Intel UHD 730 graphics chipset
- Hard_Drive_Capacity: 6Tb
- Monitor/Display Make & Model: HP E240c video conferencing monitor
- Corel programs: VideoStudio: 2022, 2023
- Location: Brisbane Australia
Re: Making a DVD iso file - convert step problem
Thinking on this overnight, I decided I would have to start again.
VS 2018 made a lot of changes, but the burn module did not look like it was one of them - but you never know. So, I began with X9 - a package I've built more than few disks with.
Created a new author file, same content as before, and the iso file rendered OK. But I did notice that the build total in Mbytes was some 200Mb different to the one I'd used in 2018. The X9 burn Ok screenshot with the space consumption bar is here and note that the estimate is around 411Mb including the menu etc.
Back in 2018, the screenshot of the build that failed did not quite include the consumption bar, so I ran it again to include that detail, here I've been over the clip properties in this build to make sure they are the same items as I used for the X9 file, and they are. Why there is a 200mb discrepancy is not obvious, but in the editing of the original 2018 timeline script to make sure the clips were all the same format I replaced an mp4 file with mpg and an wmv file with mpg, the difference would have been about 200mb. Having said that, why the final composition which failed is still showing as 645Mb rather than 411mb is inexplicable; removing files from the time line script should do just that, not leave inconvenient sizes and formats behind.
Using 2018, I built a new authoring file from scratch - the same as the X9 file, no time line script edits, and it rendered OK.
So, sorted. But confusingly
VS 2018 made a lot of changes, but the burn module did not look like it was one of them - but you never know. So, I began with X9 - a package I've built more than few disks with.
Created a new author file, same content as before, and the iso file rendered OK. But I did notice that the build total in Mbytes was some 200Mb different to the one I'd used in 2018. The X9 burn Ok screenshot with the space consumption bar is here and note that the estimate is around 411Mb including the menu etc.
Back in 2018, the screenshot of the build that failed did not quite include the consumption bar, so I ran it again to include that detail, here I've been over the clip properties in this build to make sure they are the same items as I used for the X9 file, and they are. Why there is a 200mb discrepancy is not obvious, but in the editing of the original 2018 timeline script to make sure the clips were all the same format I replaced an mp4 file with mpg and an wmv file with mpg, the difference would have been about 200mb. Having said that, why the final composition which failed is still showing as 645Mb rather than 411mb is inexplicable; removing files from the time line script should do just that, not leave inconvenient sizes and formats behind.
Using 2018, I built a new authoring file from scratch - the same as the X9 file, no time line script edits, and it rendered OK.
So, sorted. But confusingly
