Using VS X7 under Win7 on a quad processor box. Have had NO recent problems - produced several DVD's over recent months with no issues.
I have NOT changed any settings to my knowledge.
Suddenly, 2 versions of a Project (same content - one produced as MPEG2 for DVD burning, and one produced as H.264 for Blu-ray burning, have both created files that have a "frame" black border all around (not letterbox) and I cannot understand what is causing this.
I never go near the Project Settings - I do usually amend slightly the Project Preferences options - never had any problems with doing that.
When trying to work out what might be going on I tried to access Project Settings and I keep getting an ERROR MESSAGE "ecountered an improper argument". Following this error message, when the Project Settings window then appears, The "format" for DVD appears to have NO entry (the others for HD and all the other formats ALL have several choices in the way I would expect - but DVD has NO content nor options).
I cannot see any SET UP attributes anywhere which might control this BLACK FRAME/BORDER appearing.
Can anyone offer any guidance on this mystery - at the moment ANY clip file I try to produce comes along with a black border - I cannot see what might have caused this and I don't think I have clicked anything that might cause this effect.
I am a fairly experience and regular user of X7 and I have tried to explore all the avenues within the software before posting this issue for the forum.
Am I missing something basic ?
Thanks for any comments ?
Black BORDER/FRAME on my Produced MPEG2 and H.264 files ?
Moderator: Ken Berry
-
jowauk
- Posts: 71
- Joined: Sat Jul 11, 2009 12:26 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- processor: DELL Intel QuadCore
- ram: 32GB
- Video Card: NVIDIA GeForce 7100 NVIDIA nForce 630i
- sound_card: Realtek HD Audio
- Hard_Drive_Capacity: 1 TB SSD
- Monitor/Display Make & Model: ASUS 28inch
- Corel programs: VideoStudio 2022
- Location: Lichfield, UK
- Contact:
Black BORDER/FRAME on my Produced MPEG2 and H.264 files ?
John
| Staying Alive To Drive | Mari Jimages Video Productions | BizCeeVeeTV |
| Staying Alive To Drive | Mari Jimages Video Productions | BizCeeVeeTV |
- 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: Black BORDER/FRAME on my Produced MPEG2 and H.264 files
Hi John
First of all I have had that error message “Encountered an Improper Argument”
Actually during Beta testing of X7, unfortunately only my program showed the problem, and as far as I know Corel, could not replicate the problem.
A fix, not really, re-installing the program o re-setting by re-naming the 17.0 folder seems to clear the problem, but it does happen again, I have not found a cause for the error.
You can simply ignore it and set the project properties to use AVCHD rather than DVD Mpeg2.
Sorry but running out of time at the moment my grandson needs help with a gigsaw, hes only 3…. will reply later…….
First of all I have had that error message “Encountered an Improper Argument”
Actually during Beta testing of X7, unfortunately only my program showed the problem, and as far as I know Corel, could not replicate the problem.
A fix, not really, re-installing the program o re-setting by re-naming the 17.0 folder seems to clear the problem, but it does happen again, I have not found a cause for the error.
You can simply ignore it and set the project properties to use AVCHD rather than DVD Mpeg2.
Sorry but running out of time at the moment my grandson needs help with a gigsaw, hes only 3…. will reply later…….
- 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: Black BORDER/FRAME on my Produced MPEG2 and H.264 files
Hi John
Have you used the Fast Flick option.?
I have viewed my e-mails from last year and it appears the Improper Argument occurred after running FastFlicks
At the moment you program is ok, but will run a few more tests to replicate the problem.
As I say you can set the project properties to another format that works, so long as it supports 16:9.
From Share do not use Same as project properties.
Create your own template or use one of the defaults.
back to the Jig-saw
Have you used the Fast Flick option.?
I have viewed my e-mails from last year and it appears the Improper Argument occurred after running FastFlicks
At the moment you program is ok, but will run a few more tests to replicate the problem.
As I say you can set the project properties to another format that works, so long as it supports 16:9.
From Share do not use Same as project properties.
Create your own template or use one of the defaults.
back to the Jig-saw
-
jowauk
- Posts: 71
- Joined: Sat Jul 11, 2009 12:26 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- processor: DELL Intel QuadCore
- ram: 32GB
- Video Card: NVIDIA GeForce 7100 NVIDIA nForce 630i
- sound_card: Realtek HD Audio
- Hard_Drive_Capacity: 1 TB SSD
- Monitor/Display Make & Model: ASUS 28inch
- Corel programs: VideoStudio 2022
- Location: Lichfield, UK
- Contact:
Re: Black BORDER/FRAME on my Produced MPEG2 and H.264 files
Many thanks Trevor. NO I have not used FastFlicks - indeed I have done nothing other than what I have been doing successfully for many months.
I have looked deeper and concluded with some certainty that the Project has somehow decided that it is based on 4:3 despite all my processes and clip productions being in 16:9 which I ALWAYS use - have never set up for a 4:3.
So it seems that the error message I have seen and the absence of a DVD Format in Project Properties is the root cause - but I cannot see any way to correct those issues - I have checked for UPDATES and I appear to be running the latest patches OK. The only way I have been able to resolve this is to AMEND the settings during SHARE to DVD - the settings options bottom left of the dialogue. I have never had to touch these before and its a pain that I cannot set up a default for DVD Format as the error message I described is preventing me from doing any changes to the "blank" DVD Format.
For now I at least have a workaround - but such issues all make me nervous and on this occasion have cost me about half a days work re-doing DVD's that came out 4:3 resulting in the black border I started this post with.
Thanks again for your time in responding.
I have looked deeper and concluded with some certainty that the Project has somehow decided that it is based on 4:3 despite all my processes and clip productions being in 16:9 which I ALWAYS use - have never set up for a 4:3.
So it seems that the error message I have seen and the absence of a DVD Format in Project Properties is the root cause - but I cannot see any way to correct those issues - I have checked for UPDATES and I appear to be running the latest patches OK. The only way I have been able to resolve this is to AMEND the settings during SHARE to DVD - the settings options bottom left of the dialogue. I have never had to touch these before and its a pain that I cannot set up a default for DVD Format as the error message I described is preventing me from doing any changes to the "blank" DVD Format.
For now I at least have a workaround - but such issues all make me nervous and on this occasion have cost me about half a days work re-doing DVD's that came out 4:3 resulting in the black border I started this post with.
Thanks again for your time in responding.
John
| Staying Alive To Drive | Mari Jimages Video Productions | BizCeeVeeTV |
| Staying Alive To Drive | Mari Jimages Video Productions | BizCeeVeeTV |
- 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: Black BORDER/FRAME on my Produced MPEG2 and H.264 files
Hi John
First I think the only way to correct this issue is to re-install the program.
Resetting the program has not worked for me, by that comment you can assume I did replicate the problem, and stuck again with the Improper Argument
However the project properties are not that essential and we have alternatives to use, provided we set the aspect ratio as 16:9 try AVCHD
As for the error showing 4:3 it may also show the frame size as 720 x 480, that’s ntsc not pal
View the project name top right.
FastFlicks although not directly responsible, the option File – Export As Template may be to blame.
I use that option to use the template in FFlicks. I don’t recommend using Fast Flicks, don’t like it at all.
If I find any fix I will let you know
First I think the only way to correct this issue is to re-install the program.
Resetting the program has not worked for me, by that comment you can assume I did replicate the problem, and stuck again with the Improper Argument
However the project properties are not that essential and we have alternatives to use, provided we set the aspect ratio as 16:9 try AVCHD
As for the error showing 4:3 it may also show the frame size as 720 x 480, that’s ntsc not pal
View the project name top right.
FastFlicks although not directly responsible, the option File – Export As Template may be to blame.
I use that option to use the template in FFlicks. I don’t recommend using Fast Flicks, don’t like it at all.
If I find any fix I will let you know
