On Montag, 15. November 2021 15:46:27 CET Kolja Koch wrote: > Hi, > while working with some wav-files extracted by akaiextract, I noticed that > the information for loop-start and loop-end stored in the sfinst of the > wav-files seem to be in swapped order. Example: > > MIDIUnityNote: 41 > Channels: 1 > SamplesPerSecond: 44100 > BitDepth: 16 > FrameSize: 2 > Frames: 176565 > MIDIUnityNote: 41 > FineTune: 0 > Loops: yes > LoopType: 0 > LoopStart: 175036 > LoopEnd: 113915 > LoopPlayCount: 0 > LoopSize: -61120 > > LoopStart is higher then LoopEnd, thus LoopSize is calculated wrong.
Looks like data corruption to me. Akai sounds are decades old. On what medium did you have that Akai sound stored on; HD, burned vs. pressed CDROM? In general I highly recommend to use a modern filesystem (e.g. btrfs, ZFS) nowadays with appropriate self-healing feature to prevent things like bit rotting [1], especially for long-term storage. [1] https://en.wikipedia.org/wiki/Data_degradation > I didn't see this in any other looped sample I worked with yet (e.g. when > extracted from a working gig-file using gigextract). > > Has anyone else seen this? > > When swapping those numbers, the loop plays, though glitches appear. Usually you can simply open the wave in a sample editor and literally see where the loop points are, especially with such small samples as in the Akai format. CU Christian _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
