Where is the rendering info stored?

[Peter100]

I have tried to render the same project to different variants of the AVCHD (i.e. different bit rates ). However once the project is rendered for the fist time the Video Studio some how “remember” what it was rendered to and applies the same settings next time. As a result I am getting exactly same files size, bit rates etc regardless if I choose Mpeg optimizer or custom settings with AVCHD and 18 Mpbs, 20Mbps etc. The only way I can get true different results is when I start a brand new project, assemble it and render it for a first time.

I have tried deleting all cash and proxy files but to no avail. Do you know where this rendering information is hidden and how can I reset it or get rig of it?

[teknisyan]

Even I don't know where the render information are stored.. anyhow,

why are you using MPEG OPTIMIZER if you are trying to create an AVCHD file?

You can either just create a movie template for the different variants of AVCHD that you are creating, so that you can just use those template using the same project that you have or just go to SHARE > CREATE VIDEO FILE > AVCHD > then just select the AVCHD that you want.

You can click here for more info on Movie Template.

[Peter100]

"why are you using MPEG OPTIMIZER if you are trying to create an AVCHD file? "
Because my source files in the project are AVCHD type.

I created the template, but this does not change the situation. VS seems to have the mind of its own and applys the same setting (within AVCHD category) as the last rendering when the project was saved. For example if new project was rendered for the first time as AVCHD@16Mbps and saved, then trying to render it with higher bit rate such as 18 Mbps is producing exactly the same file.

On the same topic.... It also happened to me some time in the past where I have adjusted the volume of some clips in the project then render it and saved. Next time I try to edit my project I could not effectively adjust volume for the same clip anymore. What is interesting is that in preview I could adjust the volume no problem, but when the project was rendered it still had the old volume. Even trying to apply changes in 50% did not affect the outcome. Go figure...

Peter

[lata]

Hi Peter

The Mpeg optimiser should/will use the properties of the original video file.
Effectively it will copy the unedited portions and render the edited parts.

try as a test--place a clip in the timeline, cut the clip and apply a filter, any will do.
Now select Mpeg Optomiser
The Red bar shows the portion to be fully rendered, and the green section the unedited portion.

You can view the actual properties by clicking Show Details.

When you accept the settings you are taken to the Create Video File window.
This shows for all share create video file options.

The lower panel shows the actual properties that your file will be rendered to.
You should view these details before hitting save.
This will confirm to you that the program is doing what you want, you can check the bt rate and be sure it is 16000kbps

If you wish to render to a different / specific bit rate than the original you have to use either the Custom or Make Movie Templates Manager

[Peter100]

I am familiar with the process ... The problem is that VS is not doing what it says it will be doing.

Example:
Project 1
New project and first time rendering with selected rate of 16 Mbps creates file 87.2 Mb
Project 2
New project (created exactly the same way as #1) and rendering with selected rate 18 Mbps creates file 93.5 Mb


And here is where the problem starts ....

Opening Project 1 and rendering it to 16 Mbps creates file 87.2 MB. This part is fine, but now selecting custom template with 18 Mbps still creates file with 87.2 Mb size and 16 Mpbs bit rate despite that VS shows that it will use 18 Mbps to render it.

Even choosing different format for a change such as MPG2 rendering to it once and then going back to H.264 @18 Mbps still results with 87.2 Mb file.
It looks like this first rendering information is stuck somewhere is the VS and is effecting further rendering choices.

[lata]

Hi Peter

Very strange indeed,

when you change the data rate from 16 to 18 you are using the Custom option to modify the settings.

Can you use Settings Make Movie Templates Manager to create two new templates.
Identical properties, you guessed it, except for the data rate, 16 for one and 18 for the other..

Use these to render the projects.

I will run a few tests, but the program is burning a video at the moment

[konopkrz]

Hi Peter,

did you try to uncheck the SmartRender option? You can find it here: Share Step Options Panel => Create Video File button => Options button => Corel VideoStudio Pro window.

[lata]

Hi Peter

Have managed to run a few tests and can confirm your findings.

It does indeed seem to be associated with Smart Render as "konopkrz" mentioned.

I tried rendering to Mpeg2 at 8000, 6000, 4000, with no problems.

When I use Transport Stream do I get the problem
whether other formats show the same I don’t know.

I did a few edits to the project and it seemed to render correctly, not for long, it soon reverted to using the older bit rate.

Make Movie Templates Manager
Well I did suggest you use this but it is also showing the same problems.

Think this may be a problem for Corel Support to look at.

By the way Peter there is a recent update to X5, have you applied this to your program.
My version number is 15.0.0.258--no patchs

[Peter100]

Hi Trevor,

Thanks for doing this test. This confirms that this issue it is not my PC/setup related. In my test project I used combination of HD clips and .jpg pictures, so there was always part that needs rendering regardless if "smart rendering" was selected or not. Just for the record I do not have any patch installed.

Since it has been confirmed that it is VS issue. Could you or some other site administrators pass this on to Corel support?
The reason I am asking for this is that last time I reported to Corel issues, it took me 4 month with lots of hours spending on preparing and providing examples, explanations etc and did not lead to any resolution.

Peter