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: mppenc/mppdec 1.01j, Winamp plugin 0.92m (Read 8828 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

mppenc/mppdec 1.01j, Winamp plugin 0.92m

APE 3.96b5, mppenc 1.01j, mppenc 1.01j, WinAMP plugins 0.92m, XMMS plugin 0.92 

http://www.uni-jena.de/~pfk/mpp/

MPC encoder: http://www.uni-jena.de/~pfk/mpp/bin/mppenc-windows-1.01j.zip
MPC decoder: http://www.uni-jena.de/~pfk/mpp/bin/mppdec-windows-1.01j.zip
Winamp 2.x plugins: http://www.uni-jena.de/~pfk/mpp/#plugins

What's new:
Monkeys Audio: Faster for Pentium classic (P5/60...66, P54/75...200) and Pentium 4
mppenc: New options --silent and --stderr
WinAMP plugin: All language versions compiled for a long time
XMMS: A lot of very important bugfixes (taken from the WinAMP improvements of the last 9 months) to make the plugin usable for XMMS users:
Album Based Replaygain can be selected
Gapless should work. Note that the old plugin never reconstructed the length exactly (like SV4...6).
Note that there are a lot of features and bugfixes in the WinAMP plugin, which are not in the XMMS plugin. A new XMMS plugin should be derived from the WinAMP plugin (best would be a unique source for both)
other unimportant changes

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #2 –
What do those 2 news presets mean?
Thanks.

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #3 –
They are not presets, they are options.
  --silent      do not write any message to the console
  --stderr x    write console messages to file 'x'

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #4 –
I'm encoding "braindeadly" because I'm sure Insane is useless (many headphones or good CD players cut over 20.000Hz).
Isn't Xtrem enough? I would like to be sure I won't have any problem about transcoding or playing my MPCs on good hardware but many people say that Xtrem is some kind of crazy preset yet and is very good for anything (even trans-trans-transcoding).
Do anyone know THE truth? Thanks.

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #5 –
Quote
Originally posted by anubis
Do anyone know THE truth? Thanks.

There's no "THE truth" in perceptual lossy audio. Everything is subjective.
Juha Laaksonheimo

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #6 –
OK but if anyone had any suggestion...

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #7 –
XMMS source
- Not supported any more. Development dropped


So far for Linux support eh?

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #8 –
Quote
Originally posted by Garf
XMMS source
- Not supported any more. Development dropped 


So far for Linux support eh?

-- 
GCP
LoL . You conveniently left out the rest.. - XMMS source (current) not supported any more. Development dropped. Will be derived from the WinAMP plugin when WinAMP plugin becomes stable.

So obviously the old XMMS plugin source won't be supported, but a new XMMS plugin will be derived from the WinAmp PlugIn, when it becomes stable.
Juha Laaksonheimo

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #9 –
I left out the rest, because it was irrelevant to my point: Windows support always comes first, and if there's some time left and we feel like, we'll try to make a linux version as well.

Just read the original announcement and look for choice statements such as:

Quote
'A lot of very important bugfixes (taken from the WinAMP improvements of the last 9 months) to make the plugin usable for XMMS users'


Make it usable!!

Quote
Note that there are a lot of features and bugfixes in the WinAMP plugin, which are not in the XMMS plugin. 


I'd at least like the bugfixes, thankyouverymuch.

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #10 –
Quote
Originally posted by Garf
I left out the rest, because it was irrelevant to my point: Windows support always comes first, and if there's some time left and we feel like, we'll try to make a linux version as well.

Just read the original announcement and look for choice statements such as:

Make it usable!!

I'd at least like the bugfixes, thankyouverymuch.


- XMMS is unusable on my computer, it takes half an hour to
read my audio files
- When loading all my files in crashs
- It scrolls like a 4-bit computer
- Although there were nasty replay bugs, I never got a bug report
- This looks like noone uses MPC + XMMS
- Bugs in the WinAMP plugins are reported within minutes or hours, often by more than 1 person.
- report a bug you find in XMMS and I will correct it
- I don't keep in mind all bugs I fixed in the WA plugin
- Testing is nearly impossible due to the slow startup of XMMS
--  Frank Klemm

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #11 –
If the Linux user base wants an MPC plugin for XMMS, the source codes for the decoder and Winamp plugin are freely available.

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #12 –
Cool, you're going to program it?

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #13 –
Nope--I don't use Linux.

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #14 –
Quote
Originally posted by Frank Klemm

- report a bug you find in XMMS and I will correct it


I'm often getting seemlingly random ' out of sync '  errors.

(I know this doesn't help much, but the 'seemingly random' part makes it kind of hard to track down. I know I'm not the only one with this problem either.)

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #15 –
Quote
Originally posted by Garf


I'm often getting seemlingly random ' out of sync '  errors.

(I know this doesn't help much, but the 'seemingly random' part makes it kind of hard to track down. I know I'm not the only one with this problem either.)


You are using XMMS + MPC ?


[span style='font-size:9']edit: suing -> using[/span]
--  Frank Klemm

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #16 –
Quote
Originally posted by Case
They are not presets, they are options.
  --stderr x    write console messages to file 'x'


Thanks Frank!

G

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #17 –
Quote
Originally posted by Frank Klemm

You are using XMMS + MPC ?


Yes. I've upgraded to the newest version of your plugin, but it's still there. (This happened with the previous one too)

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #18 –
Quote
Originally posted by Garf


Yes. I've upgraded to the newest version of your plugin, but it's still there. (This happened with the previous one too)

-- 
GCP


What must I do to genrate the error probably ?
I played 24 hours of MPC files and do not got any error message.
--  Frank Klemm

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #19 –
Hmm, I think it mostly happens just after a song changes. I can provoke it by rapidly clicking in the song list a few times, but it also happens spontaneously.

An example of the error I get:

Lost sync in file 'foo', Frame #69/8824

or

Lost sync in file 'bar', Frame #72/7874

The frame number is always small, suggesting it happens at the start of the file.

However, if click the song again, it will play without errors.

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #20 –
Quote
Originally posted by Garf
Hmm, I think it mostly happens just after a song changes. I can provoke it by rapidly clicking in the song list a few times, but it also happens spontaneously.

An example of the error I get:

Lost sync in file 'foo', Frame #69/8824

or

Lost sync in file 'bar', Frame #72/7874

The frame number is always small, suggesting it happens at the start of the file.

However, if click the song again, it will play without errors.

-- 
GCP


Is thsi possbile with evrey MPC file ? Or do it only occures with
some special MPC files which have some special properties ?
--  Frank Klemm

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #21 –
Quote
Originally posted by Frank Klemm

Is thsi possbile with evrey MPC file ? Or do it only occures with
some special MPC files which have some special properties ?


I can provoke it on all my MPC files. SV7, mix of xtreme and standard, ID3 tags

The frame number in the error dialog is nearly always around 75-80.
(On one occasion 55)

I cannot provoke the error if I set the output buffer to 1000ms instead of
default 2000ms, however, if I make it bigger/smaller, the frame number
stays in the 75-80 range.

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #22 –
Quote
Originally posted by Garf


I can provoke it on all my MPC files. SV7, mix of xtreme and standard, ID3 tags

The frame number in the error dialog is nearly always around 75-80. 
(On one occasion 55)

I cannot provoke the error if I set the output buffer to 1000ms instead of
default 2000ms, however, if I make it bigger/smaller, the frame number
stays in the 75-80 range.

-- 
GCP


How many bytes of the file are read after 55...80 frames?
Is the possible error frame the same for a given MPC file?
Probabilty ? 0.01%, 0.1%, 1% ?
Do files with loud starts have lower error frames, files
with gentle fade in higher?

It looks like it is associated with the first butterfly buffer
change.

Maybe you can reduce

#define MEMSIZE  8192

to

#define MEMSIZE  2048

and compile it. Probabilty larger or smaller ?
--  Frank Klemm

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #23 –
Quote
Originally posted by Frank Klemm

How many bytes of the file are read after 55...80 frames?
Is the possible error frame the same for a given MPC file?
Probabilty ? 0.01%, 0.1%, 1% ?
Do files with loud starts have lower error frames, files
with gentle fade in higher?


It varies even in a single file. It either reports a frame number from 75-80 (mostly) or 45-55 (less often).

Quote
Probabilty larger or smaller ?


That does not seem to have affected anything.

--
GCP

mppenc/mppdec 1.01j, Winamp plugin 0.92m

Reply #24 –
Quote
Originally posted by Frank Klemm

How many bytes of the file are read after 55...80 frames?


I added an extra BitsRead() display in the error dialog box and the number varies widely between 200000-400000 bits read.

Edit:

Err, I fiddeled more and the error does not seem to be generated by the code! The FrameWasValid var seems to get reset to 0, even if I force to code to make it -1 (I also made it signed int of course). Could this be a threading problem?

Edit 2:

Typo in the Makefile: -DREENTRANT should be -D_REENTRANT. However, this does not fix the problem.

Edit 3:

Ok, I _think_ I got it. I changed the FrameWasValid var from a global to a local in the decode thread function, and then passed it to DECODE via a pointer. I get no more errors and the files seem to play fine. Could this be some kind of race condition between closing the old decoding thread and starting a new one? That would explain the behaviour I think.

--
GCP