On 28.10.2018 02:27, Carl Eugen Hoyos wrote:
2018-10-28 0:47 GMT+02:00, Markus Laaja :
Could you do the conversion with FFmpeg or VGMstream and if so, how did
you do it?
I don't even know what VGMstream is, I forced the codec and block_align
in a random existing demuxer to be able to test.
As
2018-10-28 0:47 GMT+02:00, Markus Laaja :
> Oh my. Almost bitwise identical file with the one I converted using PSound.
> Could you do the conversion with FFmpeg or VGMstream and if so, how did
> you do it?
I don't even know what VGMstream is, I forced the codec and block_align
in a random
Oh my. Almost bitwise identical file with the one I converted using PSound.
Could you do the conversion with FFmpeg or VGMstream and if so, how did
you do it?
VGMstream apparently only supports file formats with known headers and
cannot be forced to decode "broken" files.
The file comes from
2018-10-27 17:14 GMT+02:00, Markus Laaja :
> Excuse me for attaching the file directly.
> Successful conversion should yield 21840 samples in 22khz, mono.
Is it supposed to be (similar to) the attached file?
Can you tell us anything about the file? It looks hard to auto-detect,
where does it
On 10/27/18, Markus Laaja wrote:
> Excuse me for attaching the file directly.
> Successful conversion should yield 21840 samples in 22khz, mono.
> The first two bytes might be (non-standard) header info, but omitting
> them from the file doesn't seem to help here.
>
> Here's the configuration
Excuse me for attaching the file directly.
Successful conversion should yield 21840 samples in 22khz, mono.
The first two bytes might be (non-standard) header info, but omitting
them from the file doesn't seem to help here.
Here's the configuration output by ffmpeg just in case.
> Am 26.10.2018 um 21:12 schrieb Markus Laaja :
>
> Greetings.
> In short, I'm running into constant input errors when trying to decode from
> different adpcm formats.
> Compiling ffmpeg on a linux environment to see if it helps, is way beyond my
> reach just to solve this, unfortunately.
>
