166
preenfm2 and preenfm3 / Re: More Effects
« on: August 05, 2014, 07:42:59 PM »
Thanks. I am still playing around and am not sure I have it quite right. But it does sound cool.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
167
preenfm2 and preenfm3 / Re: More Effects
« on: August 02, 2014, 12:27:19 AM »
I posted it on gihub as a branch off the original, which I believe I did correctly. you can just download and compile.
or pm me with your e-mail and I'll send you the compiled os file.
or pm me with your e-mail and I'll send you the compiled os file.
168
preenfm2 and preenfm3 / Re: idea: More waveforms
« on: July 31, 2014, 12:59:11 AM »
Hi teevee,
I had added a formant waveform and compiled my own copy of the os. It was super easy, and everyone on this forum was extremely helpful.
see this post:
http://ixox.fr/forum/index.php?topic=63412.0
I had added a formant waveform and compiled my own copy of the os. It was super easy, and everyone on this forum was extremely helpful.
see this post:
http://ixox.fr/forum/index.php?topic=63412.0
169
preenfm2 and preenfm3 / Re: preenfm2 Editor: 0.4 (osx/win win32/x64 standalone/VST)
« on: July 18, 2014, 02:08:05 AM »
Xavier,
Thanks for all the awesome work!!!!
I am on OSX 10.9.4 and it works great. Although, when I hit "Pull" I get a high pitched whine for a half second or so if I was playing notes. If I understand, there is no OSX VST yet, correct?
Thanks for all the awesome work!!!!
I am on OSX 10.9.4 and it works great. Although, when I hit "Pull" I get a high pitched whine for a half second or so if I was playing notes. If I understand, there is no OSX VST yet, correct?
170
preenfm2 and preenfm3 / Re: operator feedback
« on: June 24, 2014, 02:08:13 AM »
Is that DC filter similar to http://www.musicdsp.org/archive.php?classid=3#135
also, unrelated, but what does "localv0L" and "localv0R" do?
also, unrelated, but what does "localv0L" and "localv0R" do?
171
preenfm2 and preenfm3 / Re: operator feedback
« on: June 17, 2014, 08:45:21 PM »
awesome. thanks. That site was great. I found it a while back while looking to code a sample rate/bit rate reducer.
Are there any other good sites or books to read about coding in C for music applications such as the PreenFM2? Are there any differences when coding for an ARM vs the ATMega?
How much ram do we have remaining in the PreenFM2?
Also, to remove the DC offset created by operator feedback, would we subtract the mean from the signal?
Thanks,
John
Are there any other good sites or books to read about coding in C for music applications such as the PreenFM2? Are there any differences when coding for an ARM vs the ATMega?
How much ram do we have remaining in the PreenFM2?
Also, to remove the DC offset created by operator feedback, would we subtract the mean from the signal?
Thanks,
John
172
preenfm2 and preenfm3 / Re: operator feedback
« on: June 17, 2014, 01:52:41 AM »
Thanks.
In code what is the difference between PM and FM? Are there any good articles on this?
I had thought that an instantaneous change in phase caused an instantaneous change in frequency?
In code what is the difference between PM and FM? Are there any good articles on this?
I had thought that an instantaneous change in phase caused an instantaneous change in frequency?
173
preenfm2 and preenfm3 / operator feedback
« on: June 14, 2014, 02:21:21 PM »
I was just looking over the DX7 algorithms and noticed that some allowed an operator to have feedback. I was wondering how we could do this on the PreenFM2?
Assuming we had a FEEDBACK parameter, would it be something like:
oscState1.frequency = freq1 * voiceIm1 + oscState1.mainFrequencyPlusMatrix;
float car1 = currentTimbre->osc1.getNextSample(&oscState1) * FEEDBACKValue * currentTimbre->mix1 * div2TimesVelocity;
Assuming we had a FEEDBACK parameter, would it be something like:
oscState1.frequency = freq1 * voiceIm1 + oscState1.mainFrequencyPlusMatrix;
float car1 = currentTimbre->osc1.getNextSample(&oscState1) * FEEDBACKValue * currentTimbre->mix1 * div2TimesVelocity;
174
preenfm2 and preenfm3 / Re: waveforms
« on: June 14, 2014, 03:51:04 AM »
Awesome!! got it working. added the new waveform.
heads up, on my mac, when I went to add the name to the oscShapeNames list in SynthState.cpp:189, my text editor kept on changing the character used for " and it would not compile. it took me a while to figure that the character was being changed.
So basically what I did was sample a waveform I liked to use as raw material on audacity. Trimmed it to one cycle. Made it mono. used sample data export. I made sure that the single cycle was 1024 samples based on the sample rate and the frequency/pitch of the sound. Then I added a space and commas after every single entry using Excel.
Then I added this data to the waveforms.c. I then changed #define NUMBER_OF_WAVETABLES in Common.h to 9.
The I edited waveforms.java. Then added the type to enum OscShape in SynthState.h (before _LAST) and the name to the oscShapeNames list in SynthState.cpp:189.
I compiled. . . and yay!! lots of fun.
heads up, on my mac, when I went to add the name to the oscShapeNames list in SynthState.cpp:189, my text editor kept on changing the character used for " and it would not compile. it took me a while to figure that the character was being changed.
So basically what I did was sample a waveform I liked to use as raw material on audacity. Trimmed it to one cycle. Made it mono. used sample data export. I made sure that the single cycle was 1024 samples based on the sample rate and the frequency/pitch of the sound. Then I added a space and commas after every single entry using Excel.
Then I added this data to the waveforms.c. I then changed #define NUMBER_OF_WAVETABLES in Common.h to 9.
The I edited waveforms.java. Then added the type to enum OscShape in SynthState.h (before _LAST) and the name to the oscShapeNames list in SynthState.cpp:189.
I compiled. . . and yay!! lots of fun.
175
preenfm2 and preenfm3 / Re: waveforms
« on: June 12, 2014, 03:55:19 AM »
Same here.
overclocked, no waveforms in CCM. no filter. Algo 27 and 28. held down 2 keys.
I did not notice any glitches either.
I started adding my own wave and got this when I compiled. Any ideas?
src/synth/Osc.cpp:108:1: error: too many initializers for 'WaveTable [8]'
overclocked, no waveforms in CCM. no filter. Algo 27 and 28. held down 2 keys.
I did not notice any glitches either.
I started adding my own wave and got this when I compiled. Any ideas?
src/synth/Osc.cpp:108:1: error: too many initializers for 'WaveTable [8]'
176
preenfm2 and preenfm3 / Re: waveforms
« on: June 11, 2014, 02:54:57 AM »
after some trial and error I got it to compile. I am still getting some errors while compiling, but I still seem to get my bin file, and it installs fine and seems to run fine.
I started with just removing "__attribute__ ((section(".ccm")))" to get the current waveforms to run in regular memory.
How many simultaneous notes should I try and play before expecting a drop out?
I started with just removing "__attribute__ ((section(".ccm")))" to get the current waveforms to run in regular memory.
How many simultaneous notes should I try and play before expecting a drop out?
177
preenfm2 and preenfm3 / Re: waveforms
« on: June 11, 2014, 12:05:53 AM »
I am installing the tool chain right now and should compile tonight. I'll let you know how it goes.
178
preenfm2 and preenfm3 / Re: waveforms
« on: June 10, 2014, 02:17:27 AM »
Quick question, what is the tool chain that is required?
I am on OSX.
I am on OSX.
179
preenfm2 and preenfm3 / Re: waveforms
« on: June 10, 2014, 12:44:18 AM »
No there's no python script.. What i do is i create directly the c arrays in java based on some series of sinusoid.
I'm afraid you'll have to find by yourself how to create your own arrays.
The waveforms are in the fast memory access of the STM32F4 (CCM). There's only 64Kb here and almost all is used.
So what you can do is to replace an existing waveforms (keep the sinusoid one for FM ;-).
Or you can add one or two in the regular memory... just remove the "__attribute__ ((section(".ccm")))" in the declaration in the wave.c file..
Will be slower and could produce some audio glitch when access in full polyphony with effects...
Xavier
Thanks. I have my table now, normalized to +/-1. 1024 values. I am adding them to waves.c, but I have one quick question, do I need to format in 5 rows of equal size like you did? For my first attempt, I am going to load it into regular memory, and see what happens.
180
preenfm2 and preenfm3 / Re: waveforms
« on: June 08, 2014, 04:59:57 PM »
Thanks. That link was great. I started looking at the tables and I see that they are normalized to +/-1 and that the values are float. How does one take a single cycle wave file and create a table of 1024 to 2048 entries from it? I am assuming I would have to start with a raw format file, but is it 8, 16 or 32 bit?
Is there possible a python script? I will definitely start searching.
Is there possible a python script? I will definitely start searching.