MSP7 - project is rendered at wrong data-rate

[DB83]

Now this is totally baffling me.

I have a 98 minute project (DV original) and am trying to encode it into mpeg at the highest rate to fit without any subsequent 'shrink'.

For my starting point I chose 5500 kbps (variable) and whilst encoding it gave the expected file size which would have been too big but anyway....

When I checked the final encode the clip had been rendered at 8000 kbps.

Even if I deleted all the files, including UPD, changed the folder for the final clip, changed to constant data-rate, I am still getting the final encode at 8000 kbps.

I'm pretty sure that this did not used to happen when MSP7 was the only version I had installed. Now I also have VS10,MSP8 plus DVDMF6 as well as DVDWS2 (had that with MSP7)

Anyone ?

[DB83]

Well I think I have solved it but the reason still baffles me.

As I said the source video was DV I created a project to edit DV (quite a lot of editing was required so I assumed that this was the best approach) - one of the Ulead defaults and they do say 'for editing DV' or words to that effect). It was only when I encoded did I select the mpeg (DVD) parameters.

So I reloaded the project (which was still using the DV files) and edited the project properties so that it was now an mpeg one. I now encoded from this and the data-rate is as selected

So I ask is there something about DV that only allows you to encode at 8000 kbps unless you are actually fooling the editor into thinking that you are actually editing mpeg files ?

[Gorf]

So I ask is there something about DV that only allows you to encode at 8000 kbps...

No

You should be able to output 5500kbps MPEG from a project that started life as a DV project containing DV source clips.

Don't forget the audio - that contributes to the eventual bitrate too.

[DB83]

So I ask is there something about DV that only allows you to encode at 8000 kbps...

No

You should be able to output 5500kbps MPEG from a project that started life as a DV project containing DV source clips.

Don't forget the audio - that contributes to the eventual bitrate too.

Which is exactly that I did when I changed the project properties to Mpeg instead of avi.

Now the only other thing I did when I originally had the project set as avi was to encode just a small part (that was done at 8000 kbps) to check the output as I was also converting the 4:3 source to 16:9. But surely the next encode should have been at the data-rate I selected - it certainly appeared that way in the progress window.

I am aware about the audio but surely that is reported separately - 8000 bkps for the video and 1536 kbps for the lpcm audio.

I will test this 'solution' again later just to see if the next encode is actually at a different data-rate and not the 5000 kbps that I actually used for the last test.

[DB83]

Just to bring this up to date.

I reloaded the mpeg project and was able to re-encode at 4500 kbps.

I then re-edited the project profile back to the original DV (the one that was causing all the grief) and this time was able to re-encode at 4000 kbps which of course is exactly what should be happening.

Why it would not before is not critical now (unless it should happen again). So maybe there was something in the edit cache (cleared by editing the project properties)