![Smile :-)](./images/smilies/icon_smile.gif)
I'll just wait for the bug fix firmware and try again, particularly if there is some help with the navigation included.
Thanks for playing with this alongside me.
Nathanael
Moderator: Solaris Moderators
This is indeed a most interesting thread! I like the idea of adding wavetables to the Solaris just by putting them on the CF-card - that would be the ultimate open ended synth!John Bowen wrote:Yes, I wanted to add folders for the WAV Osc type, as I have also encountered the problems of organizing as you mention. This will be one of the items to be fixed.
We also want to have a multisample .WAV object. It's not clear to me if we need a new Osc Type or if we can stay within the .WAV type. I have to talk to Klaus again to clarify.
hello Nathanael, when you write that the Solaris Sample Pooler app gave you an error, what was the error message?niversen wrote:I picked one of the first waves in the set.... Originally called BinAdd Arth 00000001.wav I converted it using Audacity. SamplePooler made me a .txt of the same name. This gave me an error, which I assumed was due to the filename. I changed it to BinAdd.raw on the CF card and also edited the TXT file to match the new name. This gives me a different error. Any ideas?
the files that Galbanum supplies in their Architecture Waveform product are single cycle samples that are meant to be looped (by you and whatever sampler or app that you use) but the files themselves contain no loop data. you (and your sampler or app) need to loop the data from first sample to the last.John Bowen wrote:Yes, the error is because the loop start and the loop end points look swapped. The loop start should always be at zero (or near the front of the sample at least), and the loop end point somewhere down the line (at the end I would guess in your case - which is the length of the sample -1). I thought Bernard had fixed this issue in his SamplePooler app, but apparently not!
Yes, well, actually both start and end loop points are offset and not being read correctly. Sometimes it’s not noticeable, because the loop is ‘silent’, but other times you will hear strange noise, or even portions of other samples. The addresses for the loop points are just not being read in correctly. There is the possibility of it loading correctly if your CF card is of the older format type, before the data format was changed; in that case, the data is in the correct location, and no loop problems are found.amongstmyselves wrote:Having fun with samples. After reading through this thread though am I correct in understanding that the bug is in end point as I do seem to get a small squeak of static at the end of a sample I've been playing with.
Steve
Users browsing this forum: No registered users and 4 guests