LiFe
24th January 2004, 11:18
Allright. Herewith come my long sting of complaints (and I've been using the proggie for 15 minutes).
1) It should have been called Beta not Preview. I've managed to crash it 3 or 4 times now and I've done nothing complicated. BTW do you guys get the feedback when we upload the crash data to MS?
2) You need to sort the Audio Codecs by type (as it's done at the top of the list) and not by bitrate. Mixing up Real Audio Surround, Real Audio 10 Surround, Real Audio 10 Stereo (sorted by bitrate) makes for a very complicated list. It would be much easier to navigate with codecs by type then sub-sorted by bitrate.
3) Where's lossless?
4) You need to call Cook and raac surround codecs by the same terminology. They should both be Stereo Surround (as they are matrixed). Not one Stereo Surround and one Surround Audio (which does not make it clear that it's matrixed stereo content).
5) Rename '5.1 Multichannel Surround' to '5.1 Channel Surround'. If it has 5.1 channels it's pretty retarded saying 'multi'.
6) CMD Line lets you fiddle with playback size in the 'job media profile' section so that it doesn't actualy resize but plays back at that size (allowing you to encode non-square extra-large 'enhanced' content for resize on playback). Let us do this in the GUI.
7) We want file rolling in the GUI
8) We want Multiple Outputs in the GUI
9) There are still no VBR by Q recomendations/guidelines in the docs.
10) On the topic of VBR by Q - Who changed all the mapping? Encoding at 63 - 69 now seems to get me 60, and 70+ gets me 70. What the hell happened? I had just figured out all the qualities I wanted in RM9!
11) FPS cannot be set over 30, when you mentioned in here that RealPlayer and .rm can easily encode both fields of a frame.
12) C'mon guys, keep up with the coupe over MS and add in HE-ACC to the GUI. Else I'll be rooting for MS to get the case moved to Washington : )
Overall it is so incredibly slow I was in shock for a moment. It also seems to hog windows resources as I needed to set it to 'below normal' priority before windows GUI started responding normally again.
Had no chance to compare quality because it crashes before I encode anything. Oh look at that. I've crashed it again. Well that's enough wasted time for a night!
LiFe.
1) It should have been called Beta not Preview. I've managed to crash it 3 or 4 times now and I've done nothing complicated. BTW do you guys get the feedback when we upload the crash data to MS?
2) You need to sort the Audio Codecs by type (as it's done at the top of the list) and not by bitrate. Mixing up Real Audio Surround, Real Audio 10 Surround, Real Audio 10 Stereo (sorted by bitrate) makes for a very complicated list. It would be much easier to navigate with codecs by type then sub-sorted by bitrate.
3) Where's lossless?
4) You need to call Cook and raac surround codecs by the same terminology. They should both be Stereo Surround (as they are matrixed). Not one Stereo Surround and one Surround Audio (which does not make it clear that it's matrixed stereo content).
5) Rename '5.1 Multichannel Surround' to '5.1 Channel Surround'. If it has 5.1 channels it's pretty retarded saying 'multi'.
6) CMD Line lets you fiddle with playback size in the 'job media profile' section so that it doesn't actualy resize but plays back at that size (allowing you to encode non-square extra-large 'enhanced' content for resize on playback). Let us do this in the GUI.
7) We want file rolling in the GUI
8) We want Multiple Outputs in the GUI
9) There are still no VBR by Q recomendations/guidelines in the docs.
10) On the topic of VBR by Q - Who changed all the mapping? Encoding at 63 - 69 now seems to get me 60, and 70+ gets me 70. What the hell happened? I had just figured out all the qualities I wanted in RM9!
11) FPS cannot be set over 30, when you mentioned in here that RealPlayer and .rm can easily encode both fields of a frame.
12) C'mon guys, keep up with the coupe over MS and add in HE-ACC to the GUI. Else I'll be rooting for MS to get the case moved to Washington : )
Overall it is so incredibly slow I was in shock for a moment. It also seems to hog windows resources as I needed to set it to 'below normal' priority before windows GUI started responding normally again.
Had no chance to compare quality because it crashes before I encode anything. Oh look at that. I've crashed it again. Well that's enough wasted time for a night!
LiFe.