View Full Version : BeLight 0.22 beta 8 released
Brother John
5th December 2004, 13:58
I don't care about where additional lame settings are placed. Who needs more than "alt presets" anyway? But better leave azid options where they are. BeLight tabs are meant to be encoder tabs, while azid is a decoder.
There's an issue with OTA's gain settings and AAC encoding. I thought this has been mentioned here already, but I can't find it; so sorry if I'm repeating known things.
When encoding to AAC (using BeLight 0.19) and "View command line" is disabled OTA's gain always jumps to "PostGain" when pressing "Start". Also the logfile shows that BeSweet indeed uses "PostGain" in this case.
When "View command line" is enabled the GUI still jumps back to "PostGain" (including the command line string) but according to the logfile "PreGain" (or "hybrid", depending which you chose) is used.
For other destination formats (I only tested mp3) BeLight doesn't display this behaviour.
Kurtnoise
5th December 2004, 14:28
Heyaaaa...
Sorry for the delay guys.
Originally posted by WinsomePix
On main screen, however, it's gotten even more truncated at the bottom when viewing at 1024x768 resolution -- the entire start button and everything below is now cut off.
Ok, I see. I'll try to fix it. But why did you have a pretty low resolution ?? :D
Originally posted by absinthe
Sort of a funny thing, though. I would think the whole point of calling it "BeLight" is that it is somewhat simplified. You starting adding in everyone's requests and it becomes more and more complex ...
Well...for my point of view BeLight is somewhat simplified in the form but not in the core...coz BeSweet is very powerful, isn't it ?? ;)
Originally posted by nexus
I think so too. You should first fix the bugs before implementing new functions.
Sure...but if nobody send me some feedback or bugs report then I can try to implement new things.
Originally posted by nexus
I dont't know if these bugs are known:
-Settings arent't saved correctly (I don't know if this is true, but if I check Delay and save the settings, next time I load the settings and "Delay" isn't checked. Same for "normalize" e.g.). It isn't stored in the settings.ini, but I can edit it maually.
-Language isn't saved
It's not bugs....it's not yet implemented. :p But, yes...I can do that.
Originally posted by nexus
-Command line only shows chosen parameters if I choose them _after_ clicking "View & edit command line", however parameters will be correctly delivered to besweet.exe.
Are you sure ?? Well...I know that I forgot to check something...
Originally posted by Pacemaker
It would be better to split the "advanced settings" section.
The lame section should be placed in the "MP3" tab as an advanced section --->button
The azid section should be placed in the "AC3" tab as an advanced section --->button
The other sections "Soundtouch, Partial Encodings, External Plugins and others" should remain where they are.
Is this a good idea ?
It's a good idea for sure...but like Brother John said, I prefer to keep the tabs for the encoders. And in the most cases, the Lame and Azid Settings in "Advanced Settings" are much more for advanced users. ;) So, if I add some other things in the tabs, it could be too complicated for some newbies...:)
Originally posted by Brother John
When encoding to AAC (using BeLight 0.19) and "View command line" is disabled OTA's gain always jumps to "PostGain" when pressing "Start". Also the logfile shows that BeSweet indeed uses "PostGain" in this case.
When "View command line" is enabled the GUI still jumps back to "PostGain" (including the command line string) but according to the logfile "PreGain" (or "hybrid", depending which you chose) is used.
For other destination formats (I only tested mp3) BeLight doesn't display this behaviour.
Yep....I know. I'll try to fix that in the next release.
nexus
5th December 2004, 18:43
Oh, I forgot something: Another good thing would be if settings are automaticly loaded with starting the prog. :)
Originally posted by Kurtnoise13
Sure...but if nobody send me some feedback or bugs report then I can try to implement new things. *searching for more bugs* :P
nexus
10th December 2004, 15:36
*Can't find any more bugs, so waiting for new bild *g*
Which programming language do you use for this GUI?
Kurtnoise
10th December 2004, 16:06
Hi,
Originally posted by nexus
*Can't find any more bugs, so waiting for new bild *g*
/me found others bugs... :D I'll post a new build in few hours. ;) But no new things, just bugs fix release.
Originally posted by nexus
Which programming language do you use for this GUI?
Delphi.
nFury8
11th December 2004, 15:24
Excellent work with the new GUI, Kurtnoise13.
I just noticed one thing though. The old version supported DTS input. This one doesn't seem to support DTS input. I tried selecting 'All Files' at the input then chose my DTS file but when I hit Start it crashed. Anyway, just ignore this if its too much trouble. You must have your own reasons why you didn't add DTS input support. I'll just use the old one for DTS inputs and use BeLight for AC3 inputs. Nice job.
Alxemi
11th December 2004, 15:59
And a feature request:
When you open a file with the "open file with" windows dialog, and choose belight, belight opens but the input file box is empty instead with the file you opened.
Kurtnoise
11th December 2004, 19:28
Originally posted by nFury8
Excellent work with the new GUI, Kurtnoise13.
Thanks...;)
Originally posted by nFury8
I just noticed one thing though. The old version supported DTS input. This one doesn't seem to support DTS input. I tried selecting 'All Files' at the input then chose my DTS file but when I hit Start it crashed. Anyway, just ignore this if its too much trouble. You must have your own reasons why you didn't add DTS input support. I'll just use the old one for DTS inputs and use BeLight for AC3 inputs. Nice job.
Yes, it's intentionally. ;) First, BeSweet doesn't support dts. On the other hand, I would like to create a new tool especially for transcoding dts files when BeLight will be finished. That's why dts as input file isn't support in my GUI.
Originally posted by Alxemi
And a feature request:
When you open a file with the "open file with" windows dialog, and choose belight, belight opens but the input file box is empty instead with the file you opened.
mmmh ok...I put it on my todo list.
Anyway, I hope to finish to finalize the new release tomorrow...sorry for the delay.
Kurtnoise
12th December 2004, 22:40
As I said yesterday, here's a new build : 0.20 beta 1 (http://atlas2.tgv.net/~media-video/forum2/download.php?id=1565). ;) It's just bugs fix release. A lot of internal/external bugs have been corrected...I hope everything is ok.
Just one note : BeLight now saves/load your own options as soon as you close/open it. So, the loading & saving manual settings has disappeared from the Menu. ;)
@WinsomePix : I tested on 2 different PC with a 1024x768 resolution and all seems to work fine (no cut off, etc...). Please, tell me if all it's ok for you too.
[edit]--typo
Kurtnoise
14th December 2004, 09:20
2 bugs detected in this last release :
- problem with plugins part.
- Languages aren't saved.
I'll correct these bugs as soon as I can...
guru1968
14th December 2004, 12:19
Hi Kurtnoise13,
I am pretty new to BeLight - used BeSweetGUI til now and got quite used to it's overloaded GUI; but as I am always looking for new challenges I decided to give BeLight a try...
What I can't find at first sight is where to enter the path to BeSweet.exe -- or does besweet HAS to be in %PATH% ?
Or does BeLight _need_ to be in the same directory?
- there was no readme.txt/install.txt or whatsoever in "BeLight-0.20b1.zip"
Next thing is when clicking on 'Input' and dropping down the 'Files of type' list, there are entries like " --- BeSweet List Files ---" and " --- Container Files ---"; the first include .lst and .mux and the second .avi and *.*
What I am missing is an entry for the sound formats as such (the types above " --- BeSweet List Files ---").
Furthermore this does not work at all:
If I have a test.lst and a test.mux in one directory and select "LIST Files (*.lst)" only test.lst is shown; so is only test.mux shown when I selected "MUX Files (*.mux)". That's what I expected -- but when I select " --- BeSweet List Files ---" as Type NEITHER of both is shown while I expected BOTH...
-- I thing You only ment those entries to be separators but then You also should prevent those to be selected at all...
gr33tz,
guru
nexus
14th December 2004, 13:31
Originally posted by guru1968
What I can't find at first sight is where to enter the path to BeSweet.exe -- or does besweet HAS to be in %PATH% ?
Or does BeLight _need_ to be in the same directory?
- there was no readme.txt/install.txt or whatsoever in "BeLight-0.20b1.zip" It has to be in the same directory.
Next thing is when clicking on 'Input' and dropping down the 'Files of type' list, there are entries like " --- BeSweet List Files ---" and " --- Container Files ---"; the first include .lst and .mux and the second .avi and *.*
What I am missing is an entry for the sound formats as such (the types above " --- BeSweet List Files ---").
Furthermore this does not work at all:
If I have a test.lst and a test.mux in one directory and select "LIST Files (*.lst)" only test.lst is shown; so is only test.mux shown when I selected "MUX Files (*.mux)". That's what I expected -- but when I select " --- BeSweet List Files ---" as Type NEITHER of both is shown while I expected BOTH...
-- I thing You only ment those entries to be separators but then You also should prevent those to be selected at all... I think so too. ;)
Kurtnoise
14th December 2004, 13:43
Originally posted by guru1968
What I can't find at first sight is where to enter the path to BeSweet.exe -- or does besweet HAS to be in %PATH% ?
Or does BeLight _need_ to be in the same directory?
- there was no readme.txt/install.txt or whatsoever in "BeLight-0.20b1.zip"
Well...the 0.20b1 it's just a beta release, that's why I don't add a Readme or anything else...but I suppose you don't have read my first post in this thread. BeLight must be in the same directory as BeSweet. That's all.
Originally posted by guru1968
Next thing is when clicking on 'Input' and dropping down the 'Files of type' list, there are entries like " --- BeSweet List Files ---" and " --- Container Files ---"; the first include .lst and .mux and the second .avi and *.*
What I am missing is an entry for the sound formats as such (the types above " --- BeSweet List Files ---").
Furthermore this does not work at all:
If I have a test.lst and a test.mux in one directory and select "LIST Files (*.lst)" only test.lst is shown; so is only test.mux shown when I selected "MUX Files (*.mux)". That's what I expected -- but when I select " --- BeSweet List Files ---" as Type NEITHER of both is shown while I expected BOTH...
-- I thing You only ment those entries to be separators but then You also should prevent those to be selected at all...
Yeah, but I didn't miss something. Theses lines (" --- BeSweet List Files ---" and " --- Container Files ---") are just there to separate the different choices from the list, not to choose or select the files. If you want to have .lst/.mux together, select "All files" at the end.
guru1968
14th December 2004, 17:34
Originally posted by Kurtnoise13
Yeah, but I didn't miss something. Theses lines (" --- BeSweet List Files ---" and " --- Container Files ---") are just there to separate the different choices from the list, not to choose or select the files. If you want to have .lst/.mux together, select "All files" at the end.
Okay - but if these entries were only ment as separators then you should not make them selectable...
On the other hand (and/or if this is not possible) it should be a piece of cake to associate ALL the filter-types of one section to the according separator, or not?
- i.e. selecting " --- BeSweet List Files ---" sets the filter to "*.lst or *.mux"
Just a suggestion ;)
guru
dOpiate
14th December 2004, 18:00
Am I missing the option to select 2 Pass for SSRC conversion?
BeSweet Example:
"C:\audio\BeSweet\ssrc\ssrc_hp.exe" --rate 44100 --twopass "x:\shabhot\audio.wav" "x:\shabhot\audio-New.wav"
thanks
OMINUS
14th December 2004, 18:54
is it possible to add support for adding jobs?
btw your gui rulez-its the reason i start using besweet ;)
Kurtnoise
14th December 2004, 20:34
Originally posted by guru1968
On the other hand (and/or if this is not possible) it should be a piece of cake to associate ALL the filter-types of one section to the according separator, or not?
- i.e. selecting " --- BeSweet List Files ---" sets the filter to "*.lst or *.mux"
ok...I'll add it. It's easy. ;)
Originally posted by dOpiate
Am I missing the option to select 2 Pass for SSRC conversion?
BeSweet Example:
"C:\audio\BeSweet\ssrc\ssrc_hp.exe" --rate 44100 --twopass "x:\shabhot\audio.wav" "x:\shabhot\audio-New.wav"
mmmh...all seems to be right. What's happen exactly ??
Originally posted by OMINUS
is it possible to add support for adding jobs?
Yes...it's on top on my todo list.
BTW, I need you to have your point of view. ;) I'm preparing some Presets for transcode processing. That's why I would like to have some feedbacks or suggestions for these things.
I post 2 pictures :
http://atlas2.tgv.net/~media-video/forum2/files/presets2.png http://atlas2.tgv.net/~media-video/forum2/files/presets1.png
and 0.20 beta2 (http://atlas2.tgv.net/~media-video/forum2/download.php?id=1571) (with the 2 bugs corrected) to see how we can manage the different presets. So, what do you think about that ? Is it ok or not ?? Thanks guys ....;)
dOpiate
14th December 2004, 20:42
Originally posted by Kurtnoise13
mmmh...all seems to be right. What's happen exactly ??
where is the option to turn on the two-pass for SSRC in your prog???
am I just missing it?
Longinus
14th December 2004, 22:35
Kurtnoise13, nice program!!
Just one small bug I found...
The LAME alt-preset for 128 CBR is not right, it's using ABR instead..
lame( --alt-preset 128 ) instead of lame( --alt-preset cbr 128 ).
Palikrovol
14th December 2004, 23:20
Originally posted by Kurtnoise13
BTW, I need you to have your point of view. ;) I'm preparing some Presets for transcode processing. That's why I would like to have some feedbacks or suggestions for these things.
I post 2 pictures :
http://atlas2.tgv.net/~media-video/forum2/files/presets2.png http://atlas2.tgv.net/~media-video/forum2/files/presets1.png
and 0.20 beta2 (http://atlas2.tgv.net/~media-video/forum2/download.php?id=1571) (with the 2 bugs corrected) to see how we can manage the different presets. So, what do you think about that ? Is it ok or not ?? Thanks guys ....;)
Why not both? I mean "Radio (40/50 kbps)", "Streaming (50/70", and so on.
And i think all the presets for all the speakers config. would be better (tape, radio, internet and streaming for 2.0 and 5.1 in HE)
Anyway it looks great.
Go on with the GUI Kurtnoise13
nexus
15th December 2004, 00:14
Originally posted by Palikrovol
Why not both? I mean "Radio (40/50 kbps)", "Streaming (50/70", and so on.
And i think all the presets for all the speakers config. would be better (tape, radio, internet and streaming for 2.0 and 5.1 in HE)
Anyway it looks great.
Go on with the GUI Kurtnoise13 DITO :D
Bug: Encoding priority is not saved.
Kurtnoise
15th December 2004, 08:23
Originally posted by Longinus
Just one small bug I found...
The LAME alt-preset for 128 CBR is not right, it's using ABR instead..
lame( --alt-preset 128 ) instead of lame( --alt-preset cbr 128 ).
Yep...thanks for the bug report.
Originally posted by dOpiate
where is the option to turn on the two-pass for SSRC in your prog???
Sorry, BeLight haven't SSRC 2-pass option...But you can check "View & Edit BeSweet command line", then delete the lines and copy & paste you own command. It should work great. ;)
Originally posted by Palikrovol
Why not both? I mean "Radio (40/50 kbps)", "Streaming (50/70", and so on.
And i think all the presets for all the speakers config. would be better (tape, radio, internet and streaming for 2.0 and 5.1 in HE)
Ok for both but I'm not sure about bitrate range for VBR/5.1. If someone could be tested the different presets quality...could be interesting. :)
Originally posted by nexus
Bug: Encoding priority is not saved.
not a bug yet...it's not implemented. :D BTW, the different priorities encoding work well ??
nexus
15th December 2004, 11:39
Originally posted by Kurtnoise13
not a bug yet...it's not implemented. :D BTW, the different priorities encoding work well ?? [/B] :D I think "normal" should work (because it's standard), I'll test with "idle" and "High" and post the result later.
Another bug (?) postet in the german Doom9 forum: You can't change normalization method, it's always PostGain (only AAC).
Edit: Encoding priority: It seems that it doesn't work correctly. I started BeSweet (idle) and VDub (normal), BeSweet uses 20% CPU, VDub the rest. It should be 0% for BeSweet, I think.
Edit2: Same with "normal, BeSweet: 20%, VDub rest.
I guess priority only affect on BeLight, not on besweet.exe
Kurtnoise
15th December 2004, 12:34
Thanks for the tests.
Originally posted by nexus
Another bug (?) postet in the german Doom9 forum: You can't change normalization method, it's always PostGain (only AAC).
It's not a bug...Read the AAC FAQ (http://forum.doom9.org/showthread.php?s=&threadid=68300#post424070) (n°15). That's why I choose PostGain.
nexus
15th December 2004, 12:50
Originally posted by Kurtnoise13
It's not a bug...Read the AAC FAQ (http://forum.doom9.org/showthread.php?s=&threadid=68300#post424070) (n°15). That's why I choose PostGain. [/B] But HybridGain is not recommended at the moment, so why can't I choose PreGain?
JoeBG
15th December 2004, 13:00
Originally posted by Kurtnoise13
It's not a bug...Read the AAC FAQ (http://forum.doom9.org/showthread.php?s=&threadid=68300#post424070) (n°15). That's why I choose PostGain. [/B]
You mean PreGain
"15. What gain setting should I use to encode AAC with BSN/Oagmachine?
Eventhough BeSweet/Bsn has implemented Hybrid gain, there are no Directshow filters capable of using the hybrid gain information at this time. So it is not recommended at the moment. Instead use normalization or pregain"
Pregain works fine with the normal GUI and I´m really looking at every release of your GUI if it works wit AAC. In the moment it does not ;(
Kurtnoise
15th December 2004, 13:38
PostGain ( -G 1) is equivalent to Normalization ( --maximize)...but I can manage to switch between PreGain & Normalization if you want. ;)
JoeBG
15th December 2004, 13:44
Originally posted by Kurtnoise13
PostGain ( -G 1) is equivalent to Normalization ( --maximize)...but I can manage to switch between PreGain & Normalization if you want. ;)
This would be great, thank you very much. Most people prefer Pre Gain for AAC Encoding and not the Azid method.
OMINUS
15th December 2004, 15:28
there seems to be a bug when i try to encode from .ac3 to .mp3
when i click start ,using the belight's default settings,an error message appears sayin that i must have the aacenc32.dll and aac.dll in the belight directory in order to transcode my file in aac!!
(i have put the belight in the besweet folder)
therealjoeblow
15th December 2004, 16:30
Originally posted by Kurtnoise13
BTW, I need you to have your point of view. ;) I'm preparing some Presets for transcode processing. That's why I would like to have some feedbacks or suggestions for these things.
I post 2 pictures :
snip)...
to see how we can manage the different presets. So, what do you think about that ? Is it ok or not ?? Thanks guys ....;)
I prefer the kb/s descriptions - 'radio' and 'tape' just seem too subjective to me to mean anything.
nFury8
15th December 2004, 16:33
Originally posted by OMINUS
there seems to be a bug when i try to encode from .ac3 to .mp3
when i click start ,using the belight's default settings,an error message appears sayin that i must have the aacenc32.dll and aac.dll in the belight directory in order to transcode my file in aac!!
(i have put the belight in the besweet folder)
I got the same error message when i tried to encode AC3 to 6 wavs for this latest version 0.20b2.
Kurtnoise
15th December 2004, 17:53
@ nFury8 & OMINUS : yes...sorry for this stupid bug. I had forgotten to uncheck something in my code...:o
Kurtnoise
15th December 2004, 17:57
Originally posted by therealjoeblow
I prefer the kb/s descriptions - 'radio' and 'tape' just seem too subjective to me to mean anything.
Yes...that's why I chose to put both information. Everyone will be happy..;)
Brother John
15th December 2004, 19:15
Originally posted by Kurtnoise13
PostGain ( -G 1) is equivalent to Normalization ( --maximize)
That's not correct. In fact PreGain is equivalent to --maximize.
PreGain and maximize use a 2-pass approach. First the file is scanned for the peak sample, then the appropriate gain value is calculated and applied to the file while transcoding.
PostGain looks for the peak value while transcoding and afterwards applies a gain tag to the file. The actual normalizing is done by the decoder, that needs to read the gain tag.
HybridGain uses both gain methods depending on source material. First a fixed pregain value is added to the file (0db for 2.0 sources, 10db for 5.1 sources). While transcoding the still missing rest gain value ist looked for using PostGain and stored in the gain tag.
Unfortunately aac decoders can't read gain tags, so an aac file encoded with post gain or hybrid gain will have a too low volume. For that reason PreGain "-ota( -g max )" or --mazimize should be used for aac.
edit: wrong command line for pregain corrected
Taurus
15th December 2004, 22:23
Originally posted by Brother John
Unfortunately aac decoders can't read gain tags, so an aac file encoded with post gain or hybrid gain will have a too low volume. For that reason PreGain "-ota( -g max )" or --mazimize should be used for aac.
Thank you for clearing up the sky for me. Always wondered why hybrid and post gain do not show the desired effect on aac's.
Cheers
Taurus
rondo
16th December 2004, 14:43
Hope this bug (at least I think it's one) hasn't already been corrected, as I can't test it in v20 cos of the Ominus issue.
I'm coding to MP2.
If you check the VBR Mode box & then uncheck it again, the option remains set at VBR, & the program needs to be restarted to unset it again.
Regards
Kurtnoise
16th December 2004, 16:09
It has been corrected with the latest beta. ;)
I'll post a new build tonight...
Kurtnoise
16th December 2004, 19:20
Finally...I've got a free time this afternoon. ;) So, 0.20 beta 3 (http://atlas2.tgv.net/~media-video/forum2/download.php?id=1574) is out.
changelog :
- Enhancements for Presets.
- If AAC output format is chosen, then PreGain or normalization is available. In other word, Hybrid Mode is not present for this format.
- if "-- BeSweet List File --" is chosen, then *.lst and *.mux files can be loaded.
- bug correction if the dll from Nero aren't available in the BeLight directory.
JoeBG
16th December 2004, 20:44
@ Kurtnoise
It works, thank you very much. Now a lot of manuels have to get changed :)
Kurtnoise
18th December 2004, 15:38
Hi guys,
Before to add new things, I managed the 0.20 Final (http://atlas2.tgv.net/~media-video/forum2/download.php?id=1577). :)
Changes from 0.19 to 0.20 :
- Added : Presets.
- Added : Bitrate equivalence for Vorbis Q Mode.
- Added : Possibility to select either lst or mux files in the input list.
- Fixed : PreGain available for normalization if AAC is chosen.
- Fixed : Languages can be saved now.
- Fixed : Plugins part when it's saved.
- Fixed : Some problems with LFE and Output Mode in Azid Settings.
Digga
18th December 2004, 19:59
hi there.
first of: nice gui Kurtnoise13 :)
I have a suggestion for the LAME (MP3) setting tab.
presets like r3mix are hopeless outdated and should not be used anymore. there are newer and better presets available. so r3mix should be removed IMHO.
second, all stereo modes besides joint-stereo are not as good! (mono may come handy sometimes though). it would be a good idea to remove that section too.
Gabriel, an active member at the HydrogenAudio forums (http://www.hydrogenaudio.org/index.php/Main_Page) and a LAME developer had made a very simple but nice and recommended interface for the average user, available here: http://lame.sourceforge.net/lame_ui_example.html
please note: my intention is not to bitch around here, but to try to help make this nice gui maybe even better.
cheers,
Digga
Kurtnoise
18th December 2004, 22:26
Yes...Gabriel Bouvigne himself has suggested me the same idea. ;-)
It's on my todo list.
Digga
19th December 2004, 02:37
Originally posted by Kurtnoise13
Yes...Gabriel Bouvigne himself suggests me the same idea. ;-)
It's on my todo list. :D I see.
so this is another thing you could work on if you got too much free time ;)
daphy
19th December 2004, 08:44
Hi Kurtnoise,
I would like to set up a download mirror for this file but your link is dead :(
Edit:
mirror (http://www.needfulthings.webhop.org) is online.
Kurtnoise
19th December 2004, 09:04
:( Sorry for the damage, but I don't know why...The board where I hosted the file is down at the moment. I sent you a mail to mirror the last build.
Kurtnoise
19th December 2004, 09:34
http://www.videohelp.com/tools?tool=BeLight :: A link mirror.
Happygolucky
19th December 2004, 15:19
Originally posted by Kurtnoise13
http://www.videohelp.com/tools?tool=BeLight :: A link mirror. Unfortunately, their mirror link (to free-codecs.com download site) is dead, too. Their main link points back to here on doom9.org, so no way to download the util using that site. I was able to download the .20 Final from daphy's link.
Kurtnoise
20th December 2004, 01:05
Just for info, the link (http://atlas2.tgv.net/~media-video/forum2/download.php?id=1577) from the french board is again available. :)
BTW, the new mp3 tab is almost finished...:p Stay tuned.
Bluedan
22nd December 2004, 13:48
Wanted to do a personal listening test of AAC and wanted to compare different encoding/profile settings.
Then I found out that BeLight stopped changing command line display according to manual changes made to the output file field after the second file! :confused:
Also if PNS is enabled for output the file won't play in winamp 5, but no problems with direct show players such as bsplayer (CoreAAC installed).
It seems that the latter hasn't been documented anywhere else, which suprises me...
As far as I understood PNS reduces filesize by replacing different noise occurences with the same pattern.
So, I really wanna use that feature...
Kurtnoise
22nd December 2004, 14:57
Originally posted by Bluedan
Then I found out that BeLight stopped changing command line display according to manual changes made to the output file field after the second file! :confused:
Yes you're right. It's my fault. It's fixed now.
Originally posted by Bluedan
Also if PNS is enabled for output the file won't play in winamp 5, but no problems with direct show players such as bsplayer (CoreAAC installed).
Maybe your plugin is outdated...
Originally posted by Bluedan
It seems that the latter hasn't been documented anywhere else, which suprises me...
As far as I understood PNS reduces filesize by replacing different noise occurences with the same pattern.
So, I really wanna use that feature...
Much more info about PNS here (http://www.audiocoding.com/modules/wiki/?page=PNS). ;)
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.