Tech Preview: Hive Wavetables

[Dasheesh]

So far taking one of the dune 2 WT and changing the extension to .uhm results in hive seeing it, but it's not able to read it.

[fmr]

Yes, that's how PPG was.

I don't think what I have in these wavetable is just half waves. Otherwise, the last four ones (all PPG wavetables ended the same way) would be halved too. If you open the file in a wave editor, you see that those last four are the four basic synth waves (triangle, pulse, square, saw) and they are complete.

The PPG created the waves that way, yes, but these wavetables have the full waves - you can clearly see that each have a complete cycle, with positive and negative portions.

[pdxindy]

So far taking one of the dune 2 WT and changing the extension to .uhm results in hive seeing it, but it's not able to read it.

.uhm is for scripts... not wavetables

[Dasheesh]

So far taking one of the dune 2 WT and changing the extension to .uhm results in hive seeing it, but it's not able to read it.

.uhm is for scripts... not wavetables

oh, I saw the files in both subfolders of the wavetable folder were labeled .uhm . It didn't surprise me. I thought I would have to eventually dig into the scripting to convert. Which BTW, is WAAAAAYYYYYYYY geekier then ACE.

[PietW.]

I think that's the Force Loop Classification.
OK. Start AT, click Utility, and scroller to the entry "Force Loop For Single Cycle Classification." Try Yes or No.

Please let me know if it works for you.

[pdxindy]

So far taking one of the dune 2 WT and changing the extension to .uhm results in hive seeing it, but it's not able to read it.

.uhm is for scripts... not wavetables

oh, I saw the files in both subfolders of the wavetable folder were labeled .uhm . It didn't surprise me. I thought I would have to eventually dig into the scripting to convert. Which BTW, is WAAAAAYYYYYYYY geekier then ACE.

The scripting does not convert existing wavetables... it generates wavetable mathematically...

[Dasheesh]

I think that's the Force Loop Classification.
OK. Start AT, click Utility, and scroller to the entry "Force Loop For Single Cycle Classification." Try Yes or No.

Please let me know if it works for you.

I'll be happy to let you know if I get it to work, but it won't be an immediate response. I have to learn to script first. I'm not a computer scientist, I'm a keyboard player. LoL. I'm going to take a look at it though. check back later.

[fmr]

Now that the "extension" thing is clarified, I think i found another strange thing in Hive wavetable, and a bug too.

Strange behavior: Somehow, the cycles are not read as in other synths. I added the -256 "extension" to the Reaktor files, and they were working, but that seemed to be because that "extension was being ignored.

After messing with the WT "extension", I found that the PPG wavetables, in fact, had to be named with -WT256 (not 64).

I tried to change the "extension" in the Reaktor wavetables to -WT256, and Hive crashed on loading the wavetable (which, IMO, is a bug). I then changed the "extension to -WT512. The files are read more or less as they are supposed to be, but somehow sound strange. Yet, they have 256 cycles... strange.

If I remove the estensions at all, the files are well read, and recognized as having 33 frames. PPG wavetables are read as having 64 frames (which is consistent with the number of cycles). I am confused with this frames /cycles relation.

Besides, the PPG wavetables, although they have only 64 cycles, to be read as they should, I have to use -WT256.

What's wrong in here?

[fmr]

I think that's the Force Loop Classification.
OK. Start AT, click Utility, and scroller to the entry "Force Loop For Single Cycle Classification." Try Yes or No.

Please let me know if it works for you.

I'll be happy to let you know if I get it to work, but it won't be an immediate response. I have to learn to script first. I'm not a computer scientist, I'm a keyboard player. LoL. I'm going to take a look at it though. check back later.

This is an answer to my question regarding making Audio-Term recognizing single cycle wave files

[pdxindy]

I think that's the Force Loop Classification.
OK. Start AT, click Utility, and scroller to the entry "Force Loop For Single Cycle Classification." Try Yes or No.

Please let me know if it works for you.

I'll be happy to let you know if I get it to work, but it won't be an immediate response. I have to learn to script first. I'm not a computer scientist, I'm a keyboard player. LoL. I'm going to take a look at it though. check back later.

You don't have to learn the scripting... you can just sit back and let all the geeks create cool scripts and then make use of them

[Dasheesh]

So far taking one of the dune 2 WT and changing the extension to .uhm results in hive seeing it, but it's not able to read it.

.uhm is for scripts... not wavetables

oh, I saw the files in both subfolders of the wavetable folder were labeled .uhm . It didn't surprise me. I thought I would have to eventually dig into the scripting to convert. Which BTW, is WAAAAAYYYYYYYY geekier then ACE.

The scripting does not convert existing wavetables... it generates wavetable mathematically...

yeah, I'm seeing that now. first time looking at it. But, I can use a wave file if I can convert it to .wav with 64 frames/cycles right?

[Dasheesh]

hmmmm... prolly not because of the interpolation. :/. alright, well... i'll think on it.

[Dasheesh]

audioterm! ... damn it, now I'm behind in the conversation. carry on.

[fmr]

audioterm! ... damn it, now I'm behind in the conversation. carry on.

No need to feel abandoned

It's this: http://www.kvraudio.com/forum/viewtopic ... AudiotermA

@PietW.

That preference was already at YES. So, I changed it to NO, and now things work. It seems that if the setting is marked YES, the audio files need to have a loop defined.

[PietW.]

Have the waveforms loop points at the beginning and end?

Did you already try No?