Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: BeLight : a new GUI for BeSweet (Read 24802 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

BeLight : a new GUI for BeSweet

Hi,

Actually, I'm developping a new Graphical User Interface for BeSweet, one of the best audio tools for transcoding. Why a new one ? Coz some newbies can be troubled by the interface of BeSweetGUI or don't like the CLI...That's why I created BeLight.

BeLight : a new GUI for BeSweet

Reply #1 –
Very nice! Finally a non sucky GUI for BeSweet.

Quote
- Revisited the mp3 part (almost finished).

Yeah that would be my only suggestion, since the settings currently don't represent the latest LAME changes, like the merging of the presets and alt-presets, r3mix is obsolete etc.

BeLight : a new GUI for BeSweet

Reply #2 –
Thanks Gambit...

Yeah, some functions are outdated but the *big* problem is BeSweet doesn't recognize the new arguments. By example : -V 2. I'm forced to use -m j -v --vbr-old -V 2 command to have the same result.... Fortunately it works pretty good...

BeLight : a new GUI for BeSweet

Reply #3 –
WOW..looks great and not complicated as original one.
Thanks once again

BeLight : a new GUI for BeSweet

Reply #5 –
Thanks. 

For the users who want to test new things.  I've made 0.21 beta 1. But be carefull : it's only for testing. There are always some bugs which aren't resolved.

changelog :
- Added : mp3 tab completely revisited. Please read carefully explanations below.
- Now BeLight enables to ask you if you want overwrite the output file (if you have a file having the same name as your output) or not.
- Some bugs fix.

BTW, I hope to fix all bugs before Xmas.



So, some explanations about the new mp3 tab :

Some functions under BeSweetGUI are outdated. This is the case for MP3 part. We know all that BeSweet uses one of the best mp3 encoder more exactly LAME. But some people as Gabriel Bouvigne by example, one of the LAME developpers, has suggested me to involve the mp3 part to facilitate and enhance comprehension for users. That's why I follow his recommandations and some new things are appeared :



With the latest LAME releases (3.95.xx and sup), the developpers want to simplify as much as possible the using of this encoder. That's why, now we can have the choice between "Target Bitrate" and "Target Quality". This is the most important thing to know actually.
The "Target Bitrate" refers to ABR/CBR Mode. I hope everybody know what is it. So, as soon as you choose it, you can move the Bitrate slider to fix a target following your bitrate. The range is very large as you can see. By default, the bitrate is 128 kbps.
To access at CBR Mode, you must check the "Restrict Encoder to Constant Bitrate" case. In this way, you force LAME to have a constant bitrate. In other word, you can't change the bitrate. If you want to create some encode with this Mode, you must know the bitrate will be restrict to 128 kbps.

Now the second choice : "Target Quality". This Mode is equivalent to the famous VBR Mode. So, if you check this, you can choose a certain quality level (between 10 and 100). If you are used to transcode your files into Ogg Vorbis with the Q-Mode, you know it's the same idea. I think it's more easier to understand a level quality than to choose a bitrate level.
One important thing you must to know : more this quality level is low, worse the result final is. A good point could be to choose between 50-80. It's more safer. By default, it's a value of 80 which is taken. For people who know LAME command, this quality level corresponds to -V 2.
With this "Target Quality", we can have also the choice between the Fast Variable Bitrate Mode and the Standard Mode. By default, this is Standard Mode which is chosen. For information, this Mode refers to --vbr-old LAME command whereas Fast Mode is --vbr-new.

The last part concerns the possibility to active the Mono Encoding. The "Other Settings" is available but *only* for advanced users. In the most cases, the best for you is to play with "Target Bitrate" or "Target Quality".

Due to the fact BeSweet doesn't recognize some single LAME commands, I was forced to use some old arguments.That's why I put here a table to have some equivalences. I hope this help you.


Quality = 10 | -V 9 | 64 kbps |
Quality = 20 | -V 8 | 80 kbps |
Quality = 30 | -V 7 | 96 kbps |
Quality = 40 | -V 6 | 112 kbps |
Quality = 50 | -V 5 | 128 kbps |
Quality = 60 | -V 4 | 166 kbps | --(alt)-preset medium
Quality = 70 | -V 3 | 176 kbps |
Quality = 80 | -V 2 | 192 kbps | --(alt)-preset standard
Quality = 90 | -V 1 | 224 kbps |
Quality = 100 | -V 0 | 256 kbps | --(alt)-preset extreme

If some people or LAME developpers want to add something, don't hesitate.

BeLight : a new GUI for BeSweet

Reply #6 –
Some comments:

The quality scale should IMO be from 1-10, since that's how it's in LAME and you can't select e.g. 55 as the scale could suggest now. Also, I think it would be a good idea to add a describtion label with some info. Like the average bitrates one can expect and which preset it represents (to make sure that people know that they still can select aps, only it's hidden under V2 now).

And for the Bitrate mode, the user should be able to select the bitrate in 1kbps steps. Preferably also via text input (TEdit ).

Edit: Well, it's V0-V9 actually, so it's not really the same as in LAME

BeLight : a new GUI for BeSweet

Reply #7 –
Gambit, kurtnoise is just respecting Gabriel's GUI guidelines.
"To understand me, you'll have to swallow a world." Or maybe your words.

BeLight : a new GUI for BeSweet

Reply #8 –
Regarding the vbr scale, I think that 10-100 is more intuitive than 9-0 for users.
The 10-100 scale is already usable through libmp3lame.

BeLight : a new GUI for BeSweet

Reply #9 –
Quote
The quality scale should IMO be from 1-10, since that's how it's in LAME and you can't select e.g. 55 as the scale could suggest now. Also, I think it would be a good idea to add a describtion label with some info. Like the average bitrates one can expect and which preset it represents (to make sure that people know that they still can select aps, only it's hidden under V2 now).

I put some infos in the last beta.  As Gabriel said, 10-100 is more clearly I think. And it avoid to make a possible confusion between Vorbis Q-Mode and that.

Quote
And for the Bitrate mode, the user should be able to select the bitrate in 1kbps steps. Preferably also via text input (TEdit ).

It's done with the last beta but not with a TEdit

BeLight : a new GUI for BeSweet

Reply #10 –
So, I made a new beta : 0.21 beta 2.

changelog:[/u]
- Improvements concerning the mp3 tab, as Gabriel asked.
- Bug correction for the overwrite (the last beta bOrked with this).
- Quick update of the doc concerning the new mp3 part. Read 1st before to use it.

That's all...

BeLight : a new GUI for BeSweet

Reply #11 –
Quote
I put some infos in the last beta.  As Gabriel said, 10-100 is more clearly I think. And it avoid to make a possible confusion between Vorbis Q-Mode and that.
[a href="index.php?act=findpost&pid=261430"][{POST_SNAPBACK}][/a]


Well, I really don't know. A 10-100 scale just raises many questions for the user. Like, why can't I select 75 or 99. Why can't I select values < 10. Why is it called quality 80, when it's V2 from the commandline? I'm afraid it's getting really confusing for the user...

Oh, and kurtnoise, try selecting Presets -> MP3 -> Divx. It's teh b0rk now.

Edit: And I think you should be able to see the bitrate while moving the slider. That's why I suggested a TEdit control. Also for direct number input from the user. Should be easy enough to implement. Too bad it's not opensource, or I could help out

BeLight : a new GUI for BeSweet

Reply #12 –
And what's up with the Vorbis settings?
Why is q1 = 0.001, q2 = 0.100? Why can't I select quality modes above 8?
I think the way it's done in oggdropXPd would be preferable.

BeLight : a new GUI for BeSweet

Reply #13 –
Btw, if you paid any money for English classes, I would ask for money return. Don't believe anything they tell you. There really aren't any words like "recommanded" in the English language.

BeLight : a new GUI for BeSweet

Reply #14 –
Quote
Well, I really don't know. A 10-100 scale just raises many questions for the user. Like, why can't I select 75 or 99. Why can't I select values < 10. Why is it called quality 80, when it's V2 from the commandline? I'm afraid it's getting really confusing for the user...

mmmh, good point. Gabriel will answer you better than me.... 

Quote
Oh, and kurtnoise, try selecting Presets -> MP3 -> Divx. It's teh b0rk now.

Sorry, it's my fault. I didn't updated the presets...

Quote
Edit: And I think you should be able to see the bitrate while moving the slider. That's why I suggested a TEdit control. Also for direct number input from the user. Should be easy enough to implement. Too bad it's not opensource, or I could help out
[a href="index.php?act=findpost&pid=261440"][{POST_SNAPBACK}][/a]

Which slider ? For Target Bitrate you have the bitrate value in the hints. And for Target Quality, why would you see the bitrate ?? We reason with *quality* for this mode, not in term of bitrate.

BeLight : a new GUI for BeSweet

Reply #15 –
Quote
And what's up with the Vorbis settings?
Why is q1 = 0.001, q2 = 0.100?

because BeSweet uses these settings for Vorbis Q-Mode. It's not my fault.

Quote
Why can't I select quality modes above 8?

Well...on such quality level, I prefer to keep my original source.  But I can add some new quality modes above 8 for sure.

BeLight : a new GUI for BeSweet

Reply #16 –
Quote
Btw, if you paid any money for English classes, I would ask for money return. Don't believe anything they tell you. There really aren't any words like "recommanded" in the English language.
[a href="index.php?act=findpost&pid=261444"][{POST_SNAPBACK}][/a]

  sorry...I'll fix it.

BeLight : a new GUI for BeSweet

Reply #17 –
Quote
Well, I really don't know. A 10-100 scale just raises many questions for the user. Like, why can't I select 75 or 99. Why can't I select values < 10. Why is it called quality 80, when it's V2 from the commandline? I'm afraid it's getting really confusing for the user...

Perhaps it is confusing to advanced users like you, but it is less confusing to new users.
How do you explain to a new user that -V9 is the lowest quality and not the highest?
I prefer a slight confusion to advanced users, who are quickly able to understand this "change" than a big confusion to new users.

You can not select 75 or 99 because it is not available in Lame, but this might change in the future.
You can not select values <10 because in libmp3lame values <10 are already used for the legacy scale.

If the vbr slider could be shrinked a little, it could be aligned with the abr one regarding bitrate equivalences. With a "smaller files" on its left and "higher quality" on its right, it would be very nice.

note: regarding the English spelling, I am sure kurtnoise would welcome a PM with the corrections from a native English speaker.

BeLight : a new GUI for BeSweet

Reply #18 –
A link mirror to download the last beta. Sorry for the damage...

BeLight : a new GUI for BeSweet

Reply #19 –
We all know that good coders sucks at dialog design .
*hides*
Don't hit me, I'm just joking Gabriel  .

Anyway...
IMO the fact that BeSweet messes up the Vorbis settings shouldn't be represented in the BeLight GUI. I would rather think that the original Vorbis Q modes should be respected.

And here is what I imagined for the mp3 settings:
http://www.burrrn.net/TehBukkake/LAME_GUI.rar

P.S.: Merry Christmas everybody, enjoy the holidays!

BeLight : a new GUI for BeSweet

Reply #20 –
Hi Gambit, 

Quote
IMO the fact that BeSweet messes up the Vorbis settings shouldn't be represented in the BeLight GUI. I would rather think that the original Vorbis Q modes should be respected.

I modified a little bit the Vorbis Q-Mode part to respect a little better the original Vorbis Q-Mode. In fact, by example, if we choose q=2,00 from the list then q=0.200 sent to BeSweet command line. 

Quote
And here is what I imagined for the mp3 settings:
http://www.burrrn.net/TehBukkake/LAME_GUI.rar

I prefer my GUI personally...  BTW, in BeLight the target bitrate values appear into the hints. I think it's more beautiful. And for advanced users, we can see also these values by checking "View & Edit BeSweet Command Line".

BeLight : a new GUI for BeSweet

Reply #22 –
Quote
Well, it might be prettier that way, but it's less intuitive IMO. At least make the hint visible while moving, otherwise you are moving the slider "blindly". I have updated my code example if you wanna see what I mean.
http://www.burrrn.net/TehBukkake/LAME_GUI.rar
[{POST_SNAPBACK}][/a]

Thanks dude...


BeLight is hosted on [a href="http://corecodec.org/projects/belight/]CoreCodec[/url] now.  It's time tu update your bookmarks.

BeLight : a new GUI for BeSweet

Reply #23 –
A new beta for a new year... 

changes from the last beta:

- Updated : CBR mp3 part. It works great now.
- Modified : new Vorbis Q-Mode. Tell me what do you think about that....;-)
- Fixed : lot of stupid & cosmetics bugs.

BeLight : a new GUI for BeSweet

Reply #24 –
The download link doesn't work, it redirects me to https://corecodec.org/.

Edit: Using http://corecodec.org/projects/belight/ works fine.

Edit2: Since it's on CoreCodec now, will it be Open Source? There are still a lot of small things that make my hands itch, if you know what I mean.