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: Command-line editing (Read 3976 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Command-line editing

Pardon my ignorance, I am new to this arena.
I actually have two questions:

1) Does anyone know of a command-line tool (pref windows) that will let me convert an mp3 file to a OV file?

2) I am also looking to edit the OV starting point, length AND quality on the command-line (again, windows).  Am I asking too much?

Thanks,
Ketch(ing)up

Command-line editing

Reply #1
Quote
1) Does anyone know of a command-line tool (pref windows) that will let me convert an mp3 file to a OV file?

Do you absolutely have to do that? It's called transcoding, and it's bad. (At best, it will sound exactly the same. Otherwise it will sound worse than the MP3.)

If you have to, you could probably use SoX.
"Facts do not cease to exist just because they are ignored."
—Aldous Huxley

Command-line editing

Reply #2
Based on my simple need and the fact that "this is bad", what are my options?

Command-line editing

Reply #3
It's true that this will result in a loss in quality, but BeSweet is capable of everything you mentioned.

Command-line editing

Reply #4
So the conversion is accomplished through OggMachine and the length/starting point piece is done with BeSplit??

Command-line editing

Reply #5
How hard can this be?

BeSweet -input test.mp3 -output test.ogg -ogg( -b 128 )
is not working...

Any BeSweet experts??

Command-line editing

Reply #6
OK, I figured it out.

Thanks tons for the reference!

BTW, has anyone ever heard of the "-split" portion of BeSweet
misreading the -start and -end parameters?

For some reason I am having to double the time parameters  eg.  to split a file at :59 and :89 I am having to specifiy -split( -start 118 -end 178 ).

Weird...
Anyone...?
Bueller...?

Command-line editing

Reply #7
Quote
OK, I figured it out.

Thanks tons for the reference!

BTW, has anyone ever heard of the "-split" portion of BeSweet
misreading the -start and -end parameters?

For some reason I am having to double the time parameters  eg.  to split a file at :59 and :89 I am having to specifiy -split( -start 118 -end 178 ).

Weird...
Anyone...?
Bueller...?

Strange.  Could you post your logfile? Add a '-logfile besweet.log' to the core section.

Command-line editing

Reply #8
Quote
Strange.  Could you post your logfile? Add a '-logfile besweet.log' to the core section.

Here's the log:

BeSweet v1.5b25 by DSPguru.
--------------------------
Using hip.dll v1.19 by Myers Carpenter <myers@users.sf.net>
Using lame_enc.dll v1.32 (8/8/2003), Engine 3.90 <http://www.mp3dev.org/>.

Logging start : 01/29/04 , 20:36:29.

besweet -core( -input test.mp3 -output test30.mp3 -logfile besweet2.log ) -lame ( -b 192 ) -split( -start 118 -end 178 )

[00:00:00:000] +------- BeSweet -----                         
[00:00:00:000] |  Input : test.mp3
[00:00:00:000] |  Output: test30.mp3
[00:00:00:000] |  Floating-Point Process: Yes
[00:00:00:000] |  Source Sample-Rate: 44.1KHz
[00:00:00:000] +-------- LAME -------
[00:00:00:000] |  Bitrate method  : CBR       
[00:00:00:000] |  MP3 bitrate    : 192
[00:00:00:000] |  Channels Mode  : Joint Stereo
[00:00:00:000] |  Error Protection: No
[00:00:00:000] +---------------------
[00:01:00:028] Conversion Completed !
[00:01:00:028] Actual Avg. Bitrate  : 95kbps
[00:00:04:000] <-- Transcoding Duration

Logging ends : 01/29/04 , 20:36:33.