updated Nero Digital MPEG-4 ASP Codec out, with new quality enhancements [Archive]

SeeMoreDigital

2nd July 2004, 22:23

There's more good news too!

Nero's DSdec filter has been fixed. It now displays anamorphic AVI and MP4 encodes correctly, including ones generated by other codecs.

As mentioned on a previous thread, I was concerned that this version of NVE (like the previous version) might not work on a PC running a clean WinXP install. Well there's no problem here either now!

So to sum up so far. Nero's decoder can now cope with AAC 'audio only' streams in AVI and MP4. Mpeg4 'video only' streams in AVI and MP4. Mpeg4/AAC streams in AVI and MP4 and Mpeg4/mp3 streams in AVI and MP4, using either the ShowTime player or WinMedia Player 9.

So it would seem they have been listening. Thanks Ahead.

I shall generate some encodes and report tomorrow.

Cheers

bobololo

3rd July 2004, 02:10

For those who are interested, here are brief info about this release for the part I know (ie the video codec). So this new version of Recode (2.0.0.18) sports the latest build of our ASP encoder which has been quite improved on several points since the former december release.

Unfortunately, the current version of Recode doesn't completely exploit all these new features. But this is only a way to keep much more for the next major release of Recode expected to be released soon ;)

Firstly, the encoding speed was drastically improved. We couldn't resist to do something to compensate the speed decrease due to "extra" quality mode :) (see below) This feature was *not* enabled in the current Recode (and don't ask me why ;)) so stay tuned for the next major release to enjoy this enhancement.

Then come error resilience and streaming tools which have been updated for integration within Recode 2.1, so you won't be able to benefit from them right now.

And last but not least, the encoding quality gets a significant boost with the introduction of the well known Rate-Distorsion Optimization inherited from our work on H.264 and also further works on the rate control. All these improvements were gathered under the new "extra" quality mode. As one can guess this extra quality has a cost and therefore don't expect to encode at 100 fps with this new quality level ;)

Well, enough speech for now. So if you're curious or simply want to evaluate the extra quality, you're welcome to give it a try and feel free to comment about it.

-- bobololo

SeeMoreDigital

3rd July 2004, 09:58

Hi bobololo, nice to have you back...

I have to say my first impressions are happy ones. I generated some "extra quality" encodes last night/this morning and they do look much, much better.

In fact I'm in the process of generating a much fuller/tougher test using the "extra quality" mode to see how well this new version compares to both DivX and XviD.

I have noticed that although the decoder filter is able to display 720x480/576 anamorphic content correctly, the encoder still has problems with movies that have a aspect ratio of 2.35:1 or 2.40:1. In order for these movies to be encoded and displayed correctly the black mattes have to be cropped away. Which of course is not a problem to do but begs the question...why can't you keep them in if you want to!

The new decoder seems very clever but what exactly is "Use Line21 / Mpeg-4 SP Video Padding"?

I'm sure I could thing of more questions but hey, better let the other forum members get their foot in the door!

Cheers

LostMP4

3rd July 2004, 12:15

Originally posted by bobololo
But this is only a way to keep much more for the next major release of Recode expected to be released soon ;)

Can you translate "soon" in a more understandable and precise way? :p
(and the H264 codec? I guess it'll come out "after" that "soon")

bond

3rd July 2004, 14:00

ok here are my findings:

gui:
- no real changes/still the same: limited to only dvd input, no .avs or other input supported in recode2 itself
- still only 1 audio and 1 subs track possible (it was said that new recode2 will allow more than 1)

encoder:
- it has been said that all modes have been quality tuned ->
- i tested the new extra quality mode, which enables trellis + rdo (as also used by xvid when enabling vhq)
- new fast first analysis pass is already available (which also enables a new faster rate control, which shouldnt hurt the quality compared to the old rc) but when choosing it, the encoder doesnt want to connect to the muxer anymore => first pass still has to be done in full "extra mode" -> slow (slower than xvids fast first pass by far!) but nero's 2nd pass is faster than xvid here with the same featureset enabled (b-frames, qpel, gmc, custom quants...)
- import/export of xvid style matrices

nero mp4 muxer:
- the encoder doesnt want to connect to windows default avi-mux filter anymore (produced buggy output anyways) -> only nero muxer
- nero muxer doesnt output to .avi (so there is no way anymore to output directly to .avi)
- the nero mp4 muxer only connects to the nero encoder or .mp4 files opened via the nero parser filter (no support for the default win source filter nor .avi in any way)
- the muxer supports now the splitting of .mp4 files!!! .mp4 splitting only works with the new "nero file writer" filter (not with the default windows one) and it splits at keyframes (would not be necessary in .mp4)
- the muxer now supports the setting of chapters!!! (milliseconds are not setable tough)
- interleaving is also setable now (in ms)
- the file only gets created once graphedit is closed it seems

output/quality:
- no variable framerate (good if you want to output to avi)
- the output .mp4 has the last frame of the input stream placed 3 times at the beginning
- the output .mp4 has a f*ed up aspect ratio set on the bitstream level. the 640x256 stream get displayed as 640x640 with both neros and 3ivx' decoder

i compared the quality between xvid and nd with the following settings: 2pass (650kbps) with hvs-best, extra/vhq4/tellis, qpel, gmc, default b-frames, no-psy/no-aq, mv range 64
- definitely more details than the old version i tested (still less than xvid)
- overall very dirty picture, more artifacts than xvid, especially around borders (maybe its also due to hvs-best, which nd doesnt seem to like (still xvid doesnt show this "dirtyness"))

other comments:
- after installing nve the nero parser filter gets used for all .mp4 files, which means you cant connect other filters like 3ivx' splitter or decoders, like ffdshow to it anymore. reinstalling 3ivx helps

all in all, a great enhancement, but still we need to wait to get a commercial encoder, which is able to clearly beat xvid ;)

Sharktooth

3rd July 2004, 14:36

I was never able to run Recode.
Even with this new version i still get the same errors
It wants multichannel plugin and dvd plugin...
I tried all the possible fixes with no luck.
The nice part is:
Please pay attention:
The Multichannel Plug-in is already included in the Nero 6 retailpackage and the Nero 6 webversion.
and
Please pay attention:
The DVD-Video Plug-in is already included in the Nero 6 retailpackage and the webversion.
I will go straight for a refund request.

LostMP4

3rd July 2004, 16:14

Originally posted by Sharktooth
I was never able to run Recode.
Even with this new version i still get the same errors
It wants multichannel plugin and dvd plugin...
I tried all the possible fixes with no luck.
The nice part is:

and

I will go straight for a refund request.

These plugins use different serials than the suite: you must open Nero Burning Rom, look under the help menù and add the plugin serial number

LostMP4

3rd July 2004, 16:18

Originally posted by bond
- the output .mp4 has a fucked up aspect ratio set on the bitstream level. the 640x256 stream get displayed as 640x640 with both neros and 3ivx' decoder

Using Recode and testing abnormal crops and/or resizes I always got an Aspect Ratio close to the right one (still waiting for a manual option...)

bond

3rd July 2004, 17:25

Originally posted by bond
i compared the quality between xvid and nd with the following settings: 2pass (650kbps) with hvs-best, extra/vhq4/tellis, qpel, gmc, default b-frames, no-psy/no-aq, mv range 64
- definitely more details than the old version i tested (still less than xvid)
- overall very dirty picture, more artifacts than xvid, especially around borders (maybe its also due to hvs-best, which nd doesnt seem to like (still xvid doesnt show this "dirtyness"))ok after this comparison with the hvs-best custom matrix, where xvid kicked nd's ass i redid the same encode at 650kbps, with h263 quants and the following settings:
xvid (rc4): h263, VHQ4 (RDO), ChromaMotion, QPel, GMC, Trellis, B-vops (2, other default)
nd: h263, Extra Mode (RDO, Trellis), QPel, GMC, 4MV, B-vops (1), no psy, mvrange 128

and as a result i was pretty much surprised but i would say that on the sample i encoded (matrix1, same as doom9 uses), with the settings i used, overall nd can definitely keep up with xvid detailwise!
providing in many scenes a higher amount of details than xvid (!) from my eyes of view (i compared them with the great avscompare tool), and in some scenes (morpheus sitting with the cable attached to his head, neo standing in front of the weapon shelf and agent smith close up interrogating morpheus) less details than xvid
still nd is overall a little bit more dirty than xvid, but that also has to do with the details i assume and i used 2 b-frames in a row in xvid (nd uses only 1), which might also make a difference
also the background of the nd encode seems to be a little bit "swimming", meaning having some movement (not only in plain walls)
and the hvs-best encode didnt really look good (in contrary to the xvid one) as i wrote above already

all in all great work ateme! i would say nd is finally in the race ;)

Sharktooth

3rd July 2004, 20:50

Originally posted by LostMP4
These plugins use different serials than the suite: you must open Nero Burning Rom, look under the help menù and add the plugin serial number
It tells me it's already there...
However those plugins are included in the NVE package and they should not be installed separately.
Once i install NVE and give it MY serial it have to work.

bobololo

3rd July 2004, 22:05

Originally posted by SeeMoreDigital
I have noticed that although the decoder filter is able to display 720x480/576 anamorphic content correctly, the encoder still has problems with movies that have a aspect ratio of 2.35:1 or 2.40:1. In order for these movies to be encoded and displayed correctly the black mattes have to be cropped away. Which of course is not a problem to do but begs the question...why can't you keep them in if you want to!

The new decoder seems very clever but what exactly is "Use Line21 / Mpeg-4 SP Video Padding"?

All these issues are closely related to the applications (Recode and Showtime) that I definitely don't know enough to reply to your questions. Regarding the Line 21, if I'm correct, it's a standard for caption data encoding.

-- bobololo

bobololo

3rd July 2004, 22:20

Originally posted by LostMP4
Can you translate "soon" in a more understandable and precise way? :p
(and the H264 codec? I guess it'll come out "after" that "soon")

When it comes to deal with release date, it's always hard to be accurate you know :) So I'm sorry but I can't be more precise.

-- bobololo

BoNz1

3rd July 2004, 22:41

bond, how does it look with psychovisual enhancements enabled? I forget but wasn't ateme going to revamp the psychovisual enhancements? Anyway, at 650kbps they should do more good than harm and so it might be worth testing :).

SeeMoreDigital

4th July 2004, 11:34

Originally posted by bobololo
All these issues are closely related to the applications (Recode and Showtime) that I definitely don't know enough to reply to your questions. Thanks for the reply. It's a strange one because if you're into generating non cropped and resized encodes (like I am) Recode2 encodes look like this during playback: -

http://img33.exs.cx/img33/8348/SMD_Actual_Output.jpg

When it should really look like this: -

http://img15.exs.cx/img15/2410/SMD_Correct_Output2.jpg

What is interesting though, if you play the Recode2 encode in say the ShowTime player or Media Player Classic and capture a still, you get this: -

http://img36.exs.cx/img36/9075/SMD_Nero_capture.jpg

Which is exactly how an anamorphic capture should look before the player corrects it.

Cheers

SeeMoreDigital

4th July 2004, 12:51

Has anybody else noticed, when playing .MP4 files, Nero's video directshow filter seems to work a lot better with other media players than it does with WMP9.

I've tried NVE (the new version) on a couple of PC's. I've even tried using WMP10 beta but it was the same.

As a matter of interest I noticed that WMP9/10 uses both Nero's audio and video filters but MPC uses only Nero's video filter. I've tried forcing MPC to use Nero's audio filter but I can't make it work.

I wonder if it's Nero's audio filter that making WMP9 unstable!

Any suggestions?

SeeMoreDigital

4th July 2004, 15:18

Also,

I've just noticed that Nero have added some new DSdec filters (NeQTADec.ax and NeQTVDec.ax). Which enable Mpeg4/AAC streams in .MOV to function with the ShowTime player!

Cheers

chilledoutuk

4th July 2004, 19:28

SeeMoreDigital I have looked into the resizing problem you raised and have found that if you disable cropping then the playback aspect is screwed but however if you select custom crop and put 0 in all the cropping amount boxes then the aspect the video is played back is correct.

I suspect this is to do with the program setting a PAR on the stream when you crop and when you don’t it sets a DAR which appears to be wrong.

Apart from that I have to say that I am very impressed with the quality improvement in the encoding part of Nero digital.

However I am having major problems getting the dshow playback filter to work in WMP 8or9 it does work in mpc but that does not recognise the Nero aac playback filter. (Maybe I could try core aac)

Using the new mp4UI tool I was able to extract the avi stream from the video files. To my astonishment the quality seemed to be improved when i played it back with ffdshow with the XViD decoder when compared to Nero Showtime.
I believe that this may be because of the ffdshow filter using a better resizing algorithm than that of Nero digital. It seems obvious to me that the next thing that should be improved is the mp4 directshow playback filters.

SeeMoreDigital

4th July 2004, 20:31

You're a star chilledoutuk!

Yes, using your method does indeed solve the AR problems, for both PAL and NTSC sources. It's still not perfect though!

I've found that if you use mp4UI to strip out the video stream from the .MP4 container and then run it thru' MPEG4modifier you get the following Aspect Ratio information...

For PAL 720x576 you get this: -

http://img7.exs.cx/img7/3923/SMD_Recode2_PAL.gif

And for NTSC 720x480 you get this: -

http://img12.exs.cx/img12/9342/SMD_Recode2_NTSC.gif

Thanks very much for working that out, as that's been pissing me off for months...

Cheers ;)

chilledoutuk

4th July 2004, 23:34

thats very strange when you encode from a anamorphic source such as PAL 16:9 and do not resize the par should be identicle to that of the source stream which would be 16:11 for PAL 16:9.

also i wish you could have more than one audio stream as i think that having directors comentry is a popular feature.

chilledoutuk

5th July 2004, 00:06

Ill asume that the custom PAR's you quoted are for 16:9 aspect sources.

in that case the custom PAR's that nero seems to be setting are very close to that of the MPEG-2 standard

for PAL 16:9 PAR = 16/11 = 1.4545454545454545454545454545455
neros setting = 36/25 = 1.44

for NTSC 16:9 PAR = 40/33 = 1.2121212121212121212121212121212
neros setting = 6/5 = 1.2

orginaly i thought why are nero using custom PAR's thats when i realised it calculates the par so that the video will be resized for apropriate playback resolution. This means that it is possible to take a 720x576 source and crop it, then custom resize to what ever dimension you wish.

I decided to test this use an masively anamorphic resolution of 480x480 (square pixel would have been somit like 640x368).

....and voila video is played back in perfect aspect and it looked alarmingly good quality ok im off to make a few more tests and i must say im very impressed with this nero recode 2 just wish it could open avs files then it would be exceptionaly useful.

GlitchOfDoom

5th July 2004, 03:24

whats the difference between "h263 quantinization" and "h264"?

chilledoutuk

5th July 2004, 06:22

although thats a bit off topic h.263 quantinization simply uses a quntisation method based on the h.263 video standard to make MPEG-4 asp video streams.

H.264 or AVC is the next generation video encoding technology and is not compatible with MPEG-4 asp technologies.

napx

5th July 2004, 09:04

nero's aac encoder my preferred audio encoder, and if the video quality becomes truly comparable to xvid when these new features mentioned are enabled (next month's release?), nero digital could become the next big thing.
P.S: what about updates to the aac encoder? more efficient coding for audio always means more bits to allocate for video!

LostMP4

5th July 2004, 09:11

Originally posted by napx
nero's aac encoder my preferred audio encoder, and if the video quality becomes truly comparable to xvid when these new features mentioned are enabled (next month's release?), nero digital could become the next big thing.
P.S: what about updates to the aac encoder? more efficient coding for audio always means more bits to allocate for video!

Nothing new in this release...

SeeMoreDigital

5th July 2004, 10:21

Originally posted by chilledoutuk
thats very strange when you encode from a anamorphic source such as PAL 16:9 and do not resize the par should be identicle to that of the source stream which would be 16:11 for PAL 16:9.Yes, lets hope they sort this oddity out sooner rather than later - mind you, I've only been banging on about it since early Jan. It really needs to be fixed before the new Kiss (.MP4) player is launched.

Originally posted by chilledoutuk
also i wish you could have more than one audio stream as i think that having directors comentry is a popular feature. Agreed, this would be useful. But I think it will come soon.

After all, Nero's ShowTime player has been able to cope with multiple AAC and MP3 streams since the launch of Recode2 and does so very well IMO. I wonder how well the new Kiss player will cope with this innovation also?

Cheers

Andrey

5th July 2004, 11:10

whats the difference between "h263 quantinization" and "h264"?
To clarify this a bit to you :)
h.263 is an ITU standart (or 'recommendation').
As h.262 (seems that it is mpeg 2 or mpeg 1 video coding scheme), h.264 and so on are.
Example of official titles:
H.263 (02/98) Video coding for low bit rate communication
H.262 (07/95) Generic coding of moving pictures and associated audio information: Video
As for h263 quantinization - h.263 coding scheme uses uncommon (based not on quant matrixes, but on one cooficient - 2) quantization method to other mpeg video coding schemes.
So, becasuse this quantization method lacks officail name (or it is simply not widely used, I don't know) many people refer to it as h263 quantinization...

chilledoutuk

5th July 2004, 17:21

I think that the use of custom PAR's is intentional and as long as the display aspect is maintained then who cares what par they are using.
The main problem is the incorect display aspect when cropping and resizing is disabled but this can be worked around as i have explained earler.

I might hasten to add that i have tested the latest recode encodes on the new XBMC (Xbox Meia Center) and was impressed with the quality and compatibility.

SeeMoreDigital

5th July 2004, 18:34

Originally posted by chilledoutuk
I think that the use of custom PAR's is intentional and as long as the display aspect is maintained then who cares what par they are using.
The main problem is the incorect display aspect when cropping and resizing is disabled but this can be worked around as i have explained earler. Well this problem is getting stranger and stranger. I've just generated another PAL 720x576 encode, using a different source, where the movie has an AR of 2.35:1 and this time (after de-muxing), MPEG4Modifier showed the PAR as being 16:9 PAL. Is that weird or what?

Originally posted by chilledoutuk
I might hasten to add that i have tested the latest recode encodes on the new XBMC (Xbox Meia Center) and was impressed with the quality and compatibility. I really love the fact that the XboX can play Mpeg4/AAC in MP4 :D

Cheers

aliumalik

5th July 2004, 20:25

Any significant changes to the AAC encoder?

chilledoutuk

5th July 2004, 20:32

SeeMoreDigital I think you are a little confused PAL DVDs use 2 anamorphic frame PAR's
PAL 16:9
PAL 4:3

When a DVD movie specifies the aspect ratio on the DVD casing it refers to the actual movie image not including the letterboxing black bars.

As you will know any movie DVD that has a wider aspect ratio than 16:9 will use black letterbox bars to pad the rest of the frame to make the frame size 720x576 so that when the frame is resized proper picture aspect is maintained.

http://www.aoul98.dsl.pipex.com/chilledoutuk/tutorials/aspectratio/images/2.5in1.3framexample.gif

If you do not crop the black borders off and do not resize the video sequence then the par required to display the video with correct aspect would be the same as that of the source video.

Which in your case would have been the PAL 16:9 PAR which is 16:11

I have made a guide for calculating aspect ratio which is

>>Here (http://www.aoul98.dsl.pipex.com/chilledoutuk/tutorials/aspectratio/aspect.htm)<<

SeeMoreDigital

5th July 2004, 20:58

Nope, I'm not confused.

I'll let you into a secret. I actually helped author some of the first test PAL DVD's way back in 1996/97.

This was when some of the manufacturers were debating weather they needed to release DVD titles in two formats. ie: 'Anamorphic (16:9) Widescreen' as we know it now and 'Letterbox (4:3) Version'

Needless to say 'Anamorphic Widescreen' is the only format necessary... regardless of weather the movies aspect ratio is 1.77:1, 1.85:1, 2.35:1, 2.40:1, etc, etc....

EDIT: Here's a link to my website (www.SeeMoreDigital.net/03_Video_Only_Info/Image_Pixel_Frame_Size_Totals.html) which details the popular image pixel frame sizes together with their total pixel counts, with or without matte overlays.

Cheers

chilledoutuk

5th July 2004, 21:27

OK lets back to the point nero is not misbehaving with regards to PAR unless you chose the disable option in cropping.

Well this problem is getting stranger and stranger. I've just generated another PAL 720x576 encode, using a different source, where the movie has an AR of 2.35:1 and this time (after de-muxing), MPEG4Modifier showed the PAR as being 16:9 PAL. Is that weird or what?

Here you seem to be expecting a PAR different to that of the source when you are not resizing the video frame this is wrong.

Nope, I'm not confused.

Ok I dont particlary care whether your confused or not but you are wrong with regard to the first quote.

I'll let you into a secret. I actually helped author some of the first test PAL DVD's way back in 1996/97.

So you should Know better with regard to Pixel Aspect Ratio's

SeeMoreDigital

5th July 2004, 21:45

Oooow harsh!

Well like you now, I'm just trying to get to the bottom of why Recode2's encoder performs like it does.

You yourself have already identified one major piculiarity when attempting to generat encodes from anamorphic 16:9 widescreen DVD's.

Why, when clicking on the 'Crop' tab should selecting the 'Disable' button create encodes with a different PAR than those when selecting the 'Custom Crop' button and manually entering zero under is beyond me... but there we go!

At least XviD and 3ivX make anamorphic encoding more straight forward.

Cheers

Sagittaire

5th July 2004, 22:20

Nero want real Picture Aspect and it's 16/9 for PAL 720*576: 2.35 is the Movie AR or Picture Aspect with crop ...

-16/9 Pal for Pixel AR or 16/11 for Pixel Aspect
-16/9 for Display AR or 16/9 for Picture aspect

SeeMoreDigital

5th July 2004, 22:51

Well the sooner we move away from having to encode using anamorphic image pixel frame sizes the better.

I'm all in favour of using true 16:9 and 4:3 image pixel frame sizes - much of which is already available via some Mpeg2 HDTV platforms.

Hopefully chipsets like Sigma's EM8620L/21L, which can decode Mpeg2 image pixel frame sizes upto 1920x1080 (2,073,600 total), will make it into more and more standalone players.

Maybe we'll even get some HD digital camcorders too!

Cheers

pogo stick

5th July 2004, 23:10

The problem with remuxing (to create chapters) audio and video with Nero parser, muxer and file writer stays in new version. Video is twice slower then audio. :(
Does remuxing existing mp4 (audio+video) with Nero direct show stuff ever worked in Graphedit right? Did anyone try it?

chilledoutuk

6th July 2004, 01:04

I agree that anamorphic encoding is not ideal and I am happy that HDTV keeps pixels square (the way they ahould be).

On the note of HDTV is recode going to support HDTV and video sources?

What concerns me about HD digital camcorders is the data rate of the dv video encoded in HDTV resolutions would result in video thats very difficult to transmit and store unless your using final cut pro HDTV version.

SiXXGuNNZ

6th July 2004, 01:06

Originally posted by bond
nero mp4 muxer:
- the encoder doesnt want to connect to windows default avi-mux filter anymore (produced buggy output anyways) -> only nero muxer
- nero muxer doesnt output to .avi (so there is no way anymore to output directly to .avi)
- the nero mp4 muxer only connects to the nero encoder or .mp4 files opened via the nero parser filter (no support for the default win source filter nor .avi in any way)
- the muxer supports now the splitting of .mp4 files!!! .mp4 splitting only works with the new "nero file writer" filter (not with the default windows one) and it splits at keyframes (would not be necessary in .mp4)
- the muxer now supports the setting of chapters!!! (milliseconds are not setable tough)
- interleaving is also setable now (in ms)
- the file only gets created once graphedit is closed it seems

do I need to use graphedit to split the files?

SeeMoreDigital

6th July 2004, 09:39

Originally posted by chilledoutuk
On the note of HDTV is recode going to support HDTV and video sources? Very nice idea!

But in order to do this I reckon they would have to make their GUI more flexible... perhaps they could include inputting raw Mpeg streams as well as .VOB and .DAT and DV.avi?

Originally posted by chilledoutuk
What concerns me about HD digital camcorders is the data rate of the dv video encoded in HDTV resolutions would result in video thats very difficult to transmit and store unless your using final cut pro HDTV version. Yes, data flow is a problem especially as the current DV.avi format in (SP mode) consumes around 225MB per min. Meaning a typical 60min DV tape stores approx 13,500MB (13.2Gb)!

As we already know, there are quite a few camcorders that encode straight to Mpeg2 but the bit-rate has to be kept horribly slow because the media (MicroMV and MiniDVD) is small on data storage!

So this begs the question, why not manufacture camcorders to allow us to store high bit-rate Mpeg2 data onto DV tape.... or even hard-drives?

Cheers

Morpheus_xx

6th July 2004, 17:03

Originally posted by bond
ok here are my findings:
...
- the nero mp4 muxer only connects to the nero encoder or .mp4 files opened via the nero parser filter (no support for the default win source filter nor .avi in any way)
...

I found out that it is still possible to use avi or avs input to encode within graphedit.

As before I have renamed it to recode.exe then I can use

AVS (Asynch. FileSource) ->ND Video Enc->ND Mux->ND Filewriter
or
AVI->...->ND Video Enc->ND Mux->ND Filewriter

So nice to have the new quality mode :)

SeeMoreDigital

6th July 2004, 17:48

Something in Nero is behaving weirdly!

After changing the 4CC code of some Mpeg4 AVI's to NDIG (which is Nero's 4CC code) I've found that MPC will play the AVI's but with WMP9, it's a very hit and miss affair, ie: some do and some don't!

Can anybody else confirm?

Cheers

chilledoutuk

6th July 2004, 19:09

I have also had major problems using the nero dshow filter with wmp9 as well.
I have managed to get it working in MPC but i had to install core aac as mpc dont acept the nero dshow filter which leads me to think that the audio decoding filter is what is causing the problems.

Thinking about it im not that botherd as MPC can skip the chapters in the video and also gives insight into compatibilty between nero and FAAD 2 which Xbox Media Center uses without having to test on the xbox repetively.

bond

6th July 2004, 20:45

Originally posted by SiXXGuNNZ
do I need to use graphedit to split the files? well recode2 will do the splitting during encoding i assume
to split existing files you need graphedit

Originally posted by pogo stick
The problem with remuxing (to create chapters) audio and video with Nero parser, muxer and file writer stays in new version. Video is twice slower then audio. :(
Does remuxing existing mp4 (audio+video) with Nero direct show stuff ever worked in Graphedit right? Did anyone try it? i didnt try it. can anyone confirm this?
make sure you use all filters nero offers (parser, muxer and the nero filter writer, i assume there is a reason why they have an own file writer (for example splitting only works with the nero file writer))

Originally posted by Morpheus_xx
I found out that it is still possible to use avi or avs input to encode within graphedit.
AVS (Asynch. FileSource) ->ND Video Enc->ND Mux->ND Filewriter
or
AVI->...->ND Video Enc->ND Mux->ND Filewriteryeah it works with the encoder placed in between (meaning reencoding), but not directly to the nero muxer, meaning converting from .avi to .mp4 without reencoding doesnt work with the nero filters

bobololo

6th July 2004, 22:12

@ SMD & chilledoutuk, regarding anamorphic encoding, I had a question that may appear very dumb, but what is the use to keep the black mattes instead of cropping them ?

From a coding point of view, if these mattes aren't 16 pels multiple in height, they can involve very high frequencies at the edges which implies less coding efficiency and ringing at the picture boundaries.

This phenomenon doesn't occur when they are cropped since the internal encoding system prodives some "padding" which insures the continuity of the pixels at picture boundaries. This even works when the cropped picture isn't x16 in height.

-- bobololo

SeeMoreDigital

6th July 2004, 23:29

Originally posted by bobololo
@ SMD & chilledoutuk, regarding anamorphic encoding, I had a question that may appear very dumb, but what is the use to keep the black mattes instead of cropping them ? For me it's simply a standardisation and flexibility issue with Recode2.

In my opinion anamorphic encoding should be done using PAR signalling only, and in this respect Recode2 is nearly there.

*By the way I'm not not saying DAR doesn't have it's place, it can be very useful if you know what your doing. But it's quite a powerful tool. For instance, with DAR it's possible to encode just the video element of an 2.35:1 image using all 576 vertical pixels (instead of just the cropped 432 pixels) and use DAR to introduce the black mattes artificially.

If you use 3ivx and XviD to generate anamorphic encodes both create the same anamorphic values even if the encodes are cropped or not. So to me it would makes sense for Recode2 to follow the same example!

Anyway as I said before, "Why, when clicking on the 'Crop' tab should selecting the 'Disable' button create encodes with a different PAR values than those when selecting the 'Custom Crop' button and manually entering zero under is beyond me... but there we go!".... This isn't very consistent and is very misleading and confusing!

Cheers