Page 1 of 1
Couple of issues
Posted: February 3rd, 2013, 15:06
by wasi
First of all very nice alpha release! I hope pricing will not put me off the pro release when it's here.

Here are a couple of issues I enountered:
- Windows 'Library' folders are not displayed correctly. It ignores the top-level folder in 'Libary' and only shows subfolders, ignoring any samples in the top level folder.
- I get an "unsupported file format or corrupt file" on all wav, flac and mp3 files. In other words no audio files play at all (but they display fine in the waveform display).
Again though, great work. This really strikes the balance it seems and doesn't require setting up all your folders again.
Re: Couple of issues
Posted: February 3rd, 2013, 18:16
by Tom
Hey and welcome
wasi wrote:Windows 'Library' folders are not displayed correctly. It ignores the top-level folder in 'Libary' and only shows subfolders, ignoring any samples in the top level folder.
I'll look into that.
wasi wrote:I get an "unsupported file format or corrupt file" on all wav, flac and mp3 files. In other words no audio files play at all (but they display fine in the waveform display).
Is this related to the Windows libraries only, or it it always like that?
What's your OS, your soundcard, and what's your default sound output device on Windows?
Also, are you using the latest alpha build, ie. 621?
Re: Couple of issues
Posted: February 3rd, 2013, 21:54
by wasi
wasi wrote:I get an "unsupported file format or corrupt file" on all wav, flac and mp3 files. In other words no audio files play at all (but they display fine in the waveform display).
I take that back. For no apparent reason it suddenly works now. Maybe it just needed a break.

Sorry.
The Library issue persists though.
Re: Couple of issues
Posted: February 4th, 2013, 18:15
by Tom
wasi wrote:I take that back. For no apparent reason it suddenly works now. Maybe it just needed a break.

Sorry.
No prob. Not sure what the problem was there, but I haven't experienced this issue so far.
wasi wrote:The Library issue persists though.
Yeah, I've located the issue already. Not sure how to solve this yet, but I'll be working it out.