Mac OS 9 Lives

Classic Mac OS Software => Digital Audio Workstations - General Discussion => Topic started by: dr bu on September 29, 2016, 12:18:12 PM

Title: delicate bending
Post by: dr bu on September 29, 2016, 12:18:12 PM
who thinks 127 is a good range for a gissando? whitch vstis got 14 bit pitchbend? and if you have to do it sysex, where is the easy to use compiler?
Title: Re: delicate bending
Post by: GaryN on September 29, 2016, 04:51:13 PM
I assume you're referring to 127 as half of a 256-bit pitchbend range using 8 bits.
127 is not a range but rather the resolution.

If the maximum bend range is defined as 1 step (1/2 sharp or flat) the resolution is 1/2 step ÷ 127 which, if resolved properly by the plugin or whatever should be pretty darn "delicate".

14-bit bend would be ludicrous overkill… but you probably already know that.
Title: Re: delicate bending
Post by: dr bu on September 29, 2016, 09:06:34 PM
thats right "resolution" - not range. pitchbend-range is of course expressed in semitones.
 
ok, so pitchbend is sent to the vsti or a hardware synth via so called MSB and LSB (most and least significant bytes) sysex messages. most synths only read the pitchbend-MSB so the resolution is then 127. some can read LSB as well an viola! resolution becomes 16384 or 14 bit. now 127 may seem like a high enough number but lets say you want to carry out a glissando over 12 semitones. i often feel like it. this is not uncommon for a voice or violin. you will then end up with an ear training exercise, not a smooth glissando. on some synths the pitchbend-range can be set to 36 semitones or 3 octaves, maybe more. you will then be looking for some LSB.
or what if you are into exotic tunings. a 127 resolution is not sufficient when you want to play your JV-1010 like LaMonte Young.
the midi-implementation-chart will tell you how to change the resolution, if possible, but it has to be done in Hex. its tedious!
 
anyway, i was thinking maybe someone had walked this path before me.
Title: Re: delicate bending
Post by: GaryN on September 30, 2016, 04:05:20 PM
You're analysis of pitchbend is pretty accurate. The issue is actually revealed in what you just posted. You're looking for a 12-semitone PORTAMENTO. That's not a pitchbend. Glissandos of the nature you describe are generated by triggering more that one note and the synth engine portamentoes (if there is such a word) from the 1st to the 2nd at a predetermined rate.

The resolution of that is determined internally rather that having to calculate and respond to a constantly varying external control signal.

I'm sure others have "walked this path before you". I suspect they have better success with actual analog hardware (no MSB LSB issues at all that way) and they probably don't try to play a JV-1010 (or most other mass-produced MIDI synths) that way.

I think you're wanting the MIDI 1.0 spec to perform like some future 5.0 spec that's not here yet.  The reason that pitchbend spec only carries 8 bits is because it's a spec. As such, it's designed as a careful compromise between ultimate performance and practical implementation across an entire industry that includes instruments ranging from $50,000 all the way down to $79.95.

The data density of a theoretical 14-bit pitchbend stream is well beyond the capacity of the control paths and circuits involved. It's also probably well beyond the resolution of what you actually need (I'm thinking 10 bits) to get the "smoothness" you want anyway.
 
At the end of the day, you're wishing for something that doesn't exist. Nothing wrong with that at all, that's how things improve.
Title: Re: delicate bending
Post by: dr bu on September 30, 2016, 11:56:40 PM
ok thanks Gary. but we are clearly getting our wires crossed here  ;)
http://www.midikits.net/midi_analyser/pitch_bend.htm
http://en.wikipedia.org/wiki/MIDI_controller#Use_in_a_data_stream

relevant as my questions seems to me, maybe noone at this forum uses pitchbend  ;D
Title: Re: delicate bending
Post by: widdly on October 01, 2016, 06:54:40 AM
All of the synths I know respond to the full resolution  14bit pitchbend.  What synth only uses the MSB of pitchbend messages?  I wonder if you are sending the messages properly.

I like a +/- 1 octave bend range which would be VERY stepped with a 7 bit bend resolution.
Title: Re: delicate bending
Post by: dr bu on October 01, 2016, 01:07:13 PM
Right! I dont know how i missed that :-[ Thanks!

I like a +/- 1 octave bend range which would be VERY stepped with a 7 bit bend resolution.
Good for you  :)
Title: Re: delicate bending
Post by: GaryN on October 01, 2016, 06:16:12 PM
OK. I apologize for my lack of clarity…it was late.
The point I'm ultimately trying to make is: Although the pitchbend spec provides two bytes per message to provide 16-odd thousand discrete steps, can you actually ever get that in a practical way?

Example:
I go into my sequencer and graphically draw a loong, straight PB line over enough measures to assure max visible resolution. I then look at those messages in a list and they are indeed, although not precisely 1-bit increments (more like 2 or 3 but close enough) I do now actually have a long string of 14-bit PB commands showing - lots and lots of them.

However…
Try as I might I cannot generate massages like that from any controller I have (admittedly, NOT $10k keyboards, but good common Yamaha & Roland stuff). The best I can get is 127 (rounded to 130) bit steps.
The controllers simply refuse to resolve and send anything finer that that.
I can actually push a PB wheel very slowly and see the message output blink on my Studio 5 each time a PB message is generated.
No settings, adjustments, hammer-smashing I can do will cause a finer, thicker, higher resolution of pitchbend data to be output and sent.

This is what I was so poorly trying to say yesterday… Although the controllers do send 14-bit numbers, they don't send enough of them. Rather, they seem to send no more than they would in an 8-bit mode.
Actually, the numbers they do send, seem to very much correspond to 14 bits quantized down to 8.
I believe this is simply because if they did, you'd have a good chance of choking an entire sequenced MIDI stream every time you implemented a bend unless there were NO other instruments / data in the sequence. None of this applies to a self-contained instrument of course, where the relationship between engine and controller can be as precise as the designer wants. But, we're talking about controllers, synths, VSTi's and such here that communicate via the MIDI stream. So, although the resolution is in the spec, I don't see it actually being implemented effectively in practice. It seems to be just another one of those things they consider to be a fringe situation that you get to go in and edit / improve after recording if necessary.

God knows, my name is NOT Oppenheim and there's a whole helluva lot I don't know about the tiny details of electronic musical hardware and software, but this is my experience. If I'm out to lunch here, I'd love to have somebody educate me a little. I'm not yet too old to learn something…
Title: Re: delicate bending
Post by: IIO on October 25, 2016, 03:23:20 PM
I assume you're referring to 127 as half of a 256-bit pitchbend range using 8 bits.
127 is not a range but rather the resolution.

hm, yeah, he mixed up range and resolution, but if we start like that then i would like to point out that a 256-bit pitchbend also does not exist.

nor does 8-bits play a role here.

or 7.

nothing of that exists.

pitchbend always was using 14 bit numbers made out of two 7 bit words.

Quote
14-bit bend would be ludicrous overkill… but you probably already know that.

and i wholeheartly (or however that word is supposed to be written) disagree that 8 bits over 7 bits is a sufficient solution for pitch bend.

for "bend" maybe - because most signal generators would interpolate the parameter input anyway - and the parameter input has a very low time rate - but not for "pitch".

you probably know that some people are using the pitch bend controller to do microtuning with devices which dont support it in another way. for tuning frequencies for music 32 bit floating point would be nice - and 64 bits would be what you´d like to have.
Title: Re: delicate bending
Post by: IIO on October 25, 2016, 03:31:36 PM
...
Title: Re: delicate bending
Post by: GaryN on October 25, 2016, 08:44:18 PM
I assume you're referring to 127 as half of a 256-bit pitchbend range using 8 bits.
127 is not a range but rather the resolution.

hm, yeah, he mixed up range and resolution, but if we start like that then i would like to point out that a 256-bit pitchbend also does not exist.

nor does 8-bits play a role here.

or 7.

nothing of that exists.

pitchbend always was using 14 bit numbers made out of two 7 bit words.

Quote
14-bit bend would be ludicrous overkill… but you probably already know that.

and i wholeheartly (or however that word is supposed to be written) disagree that 8 bits over 7 bits is a sufficient solution for pitch bend.

for "bend" maybe - because most signal generators would interpolate the parameter input anyway - and the parameter input has a very low time rate - but not for "pitch".

you probably know that some people are using the pitch bend controller to do microtuning with devices which dont support it in another way. for tuning frequencies for music 32 bit floating point would be nice - and 64 bits would be what you´d like to have.

I gotta admit llO, as is so often the case, I have NO friggin' idea what you're talking about, but i think it is not what I'm talking about.

Dr bu was wanting 14-bit pitchbend. I was pointing out that I can't get a controller to generate anything finer in 14-bit than one could get if the bend spec was 8-bit. The damn things send big 14-bit numbers but skip so many that having 14-bit numbers is a waste of data.

We all know there's no such thing as 256-bit pitchbend. 256 is the maximum number generated with 8 bits. (as -127,0,127)

The MIDI spec for pitchbend is 14 bits for 16384 maximum. (as -8192,0,8192)

The reality however, seems to be that all that is commonly generated, transmitted, resolved and acted upon is the equivalent resolution you could get with just 8 bits.

Title: Re: delicate bending
Post by: dr bu on October 26, 2016, 05:44:37 PM
in Max we have one object: bendout~, for 7-bit and another: xbendout~, for 14-bit. the difference between them is obvious to any ear.
since this is programming and not wheelbending i can with the latter oject sit on any of 16384 steps, which is delicate enough for my needs.
and yes, as can be examined in a listeditor, 7-bit pichbend is actually 14 (LSB is always zero).
Title: Re: delicate bending
Post by: IIO on October 26, 2016, 08:38:18 PM
I gotta admit llO, as is so often the case, I have NO friggin' idea what you're talking about, but i think it is not what I'm talking about.

...

The reality however, seems to be that all that is commonly generated, transmitted, resolved and acted upon is the equivalent resolution you could get with just 8 bits.

the reality often seems to be quite different from what we think how it is.

hardware controllers are only one of many options how to generate data, and in conjuntion with software plug-ins the relevance to software-generated controller data is raising from year to year.

the fact that most hardware controllers would not allow to produce data of a higher range or precision than what 7 or 8 bit offers does not automatically mean that 7 or 8 bits is sufficient for tuning audio material for music.

as someone already pointed out, you might want to use up to 1 or 2 octaves for a "pitch bend controller", and if you do so, you wil be happy to have the full 14 bit range, or even floating point at your hands.

since bu is using host applications such as max/msp, it will be normal for him to generate 32 bit data - and that is why it is a pity that most vst plug-ins only support some form of virtual midi with the usual shit resolution of midi.

unless you are using logic audio, you will control plug-ins with 32 bits data anyway as soon as you access the VST parameters directly.

and there are various usb controllers which can send up to 10 bits, and there are network protocols which support whatever you want, too...
Title: Re: delicate bending
Post by: GaryN on October 26, 2016, 09:27:56 PM
And as usual, we now come to that familiar crossroads where performance and programming meet and then diverge. Where your inspiration takes you outside of the "norms" and so you have to find a way to create / generate / program what you hear in your head to force your non-compliant mediocre hardware into reproducing your artistic vision.

Some of us will take the path less trodden and gradually become number-crunching, bit-tweaking, precision seeking tech / musician hybrids seeking a way to get that subtle little "thing" we desire to actually happen despite the lack of commercial product available to help.

Some of us will just say "Fuck it" and write the damn song.
Title: Re: delicate bending
Post by: IIO on October 27, 2016, 12:00:08 PM
it is an interesting question if those who stopped using what the market gave us as "norms" and asked for more or migrated further are somehow more progressive or if they are just to dumb to properly use a modwheel.

in my case you would be right; i haven´t played live for 20 years and i am not even producing anymore, instead i am working on a totally different field.

but it is not like noone would be using 10 or 12 bit controller hardware or programming language scripts in a live situation.

in my opinion there is always at least two branches or (different forms?) of "technological progress", one of which i would agreee with you that you dont need it for productivity or fun.

most professional players of medieval crooked horns will ask you why you are using keyboards with mod wheels instead of just playing the danmed song, too, these things are always a matter of perspective.
Title: Re: delicate bending
Post by: GaryN on October 27, 2016, 05:03:39 PM
Amen
Title: Re: delicate bending
Post by: dr bu on October 27, 2016, 08:02:21 PM
I gotta admit llO, as is so often the case, I have NO friggin' idea what you're talking about, but i think it is not what I'm talking about.
Amen
:D
Title: Re: delicate bending
Post by: dr bu on December 23, 2016, 10:26:56 PM
in Max (still 4.1 ofcourse), is it possible to send sysex-data to the vst~ object?
i think not.
according to the manual a vst~ oriented midievent-message is supposed to be followed by 2-4 numbers.
the first 2-3 numbers happily send regular note and control-messages.
(the fourth number is a 7-bit pitchbend-message which doesnt seem to be implemented correctly btw)
anyway, importing a midifile containing sysex into the seq-object i notice (textview) it splits the array into chunks of 4!
thats why i came up with this idea  ::)
(in re-saving, this data get lost.. seq:s midi-textformat seems to be max-only)
i had a look at cycling 74s forum about this, no luck...
Title: Re: delicate bending
Post by: IIO on December 24, 2016, 08:42:43 AM
note that "midievent message" is already something totally different than MIDI in max.

where you would send "midievent 144 64 60" to [vst~] you would send something like "x90 x3C x40" to a midi device.

so nope, there is no midi-in at all in the vst object, even when there is a midi implementation in the plug-in. instead you can send a quasi vst controller data to all parameters of the plug-in (which you cant do in cubase and protools)

"midievent" only handles note on and note off (and fake-"all notes off") properly, i wouldnt use it for controller messages at all.

incoming midi data should be caught by [midiin] and formatted properly by yourself - exactly the way you want it to work.

the fourth argument, btw, is note number microtuning, not wheel, and to my knowledge there is no VST plug-in on OS9 which would support it (eventually native instruments stuff, havent testet those, but otherwise midi microtuning in vst~ is a windows OS thing.)

in my opinion it is far easier to check the the plug-ins architecture by the "get" messages to vst~ and then convert incoming MIDI to vst controller data: "5 0.7"

have you worked with the "get" stuff yet? i have made a nice overview once, will see if i find it.

in addition it can also be "better" because it raises the controller resolution from 7 to 32 bit, so that you are for example able to interpolate the incoming data from a hardware controller - or set it to an exact value of your choice.
Title: Re: delicate bending
Post by: IIO on December 24, 2016, 09:04:25 AM
sysex isnt supported at all, not from the host, not from plugins. there are for sure better ways to do what you want.

to come back to your original question i would also like to suggest to create such a synthesizer right in max/msp or use VST plug-ins which have a good internal glissando/portamento effect (there are plenty)
Title: Re: delicate bending
Post by: dr bu on December 24, 2016, 11:50:35 PM
well, im using the roland VSC and it doesnt have a pitchbend-range controller/parameter. the only way to change this - is sysex.. if used as stand alone this can be done from Max via the IAC-bus..

also the VSC doesnt get the "get" message (or the other way around), it has 1330 params but only 31 of them will show up (without name, just the letter p), in a get request. (Roland HyperCanvas and HQ Orchestral will make my Max freeze when loaded into vst~ btw).

into the cheep GM concept as i am, i would have used the Quicktime synth if i knew a way to route its audio into Max (spigot~ doesnt work) and a more convenient way to change the pitchbend-range than going into OMS setup every time... 
Title: Re: delicate bending
Post by: IIO on December 25, 2016, 04:50:24 AM
uh, VSC!
Title: Re: delicate bending
Post by: dr bu on December 25, 2016, 06:29:07 AM
Hey! hangin out with Chris these days?
Title: Re: delicate bending
Post by: IIO on December 25, 2016, 02:07:10 PM
dont remind me
Title: Re: delicate bending
Post by: dr bu on December 28, 2016, 01:47:58 AM
...bending reached a new level of delicacy some days passed.
my old sawtooth s`got a soul.
 
maybe its because i put my own into it? living in the fridge all by itself...i opened it, heeding die hards advice about exactly 1 gig of ram, not a sign of dust.

twang! all guitars in my neighborhood pale. a few by love, others by pure envy. success is revenge.
 
bu turns to his friends: [thresh~], [line~] and [seq]. well, [seq] is pretty stubborn.. by the book he should obey a written message appended by a simple path - not so.
also he is one of the most reliable sources for a program hiccup, so dr bu, whos whole life is a workaround tells [capture] to record the singing in the cold; temporary, in the crowd. [capture] is feed with seqformat-text, so anytime later [seq] can have a try without fucking up docs workflow.

more maxiana: [thresh~], expects a low and a high threshold obviously, much like hysteresis, thus reading from left to right like a good westerner, but the MSP reference example has it reversed. checking the online documentation this typo still exists 15 years later.

no, i think [delta~] is me best friend. all creatures will stumble before her beauty simplistiq. shes got the photographer always ready and when her husband speeks she sparkles the samples softened only by her lowpassed cutoffed arm.
oh yes.
Title: Re: delicate bending
Post by: IIO on December 28, 2016, 07:19:09 PM
by the book he should obey a written message appended by a simple path - not so.

i know this well from [vst~] and [text]

sometimes the workaround of using loadbang solves the problem - in rare cases not even that.

Quote
whos whole life is a workaround

:)

Quote
checking the online documentation this typo still exists 15 years later.

the collective, which is a completly different collective from the one 15 years ago, is not very good at fixing known bugs.

i found major bugs in meter~, degrade~, peakamp~ and several other issues and wrong documentations and sometimes i tend to think that the original developers of the objects and the company as such obviously dont speak to each other. i should know better, but thats what it feels like.

the advantages of using the same app for 15 years are still running out the disadvantage of finding more and more problems. :)

Quote
oh yes.

if you are finished with the poetic part, why not try detonate or an audiobuffer to record your pitch data?

of course, storing 24-bit values in detonate requires a complex transformation algo^^ but if you try hard enough...
Title: Re: delicate bending
Post by: dr bu on December 29, 2016, 04:45:05 PM
i looked at detonate now and then. did not know you could record that amount of data to it..audio buffer, that was my idea a few years ago. never came home. also seq~...gave up.
Title: Re: delicate bending
Post by: dr bu on December 29, 2016, 10:52:44 PM
..what do you mean loadbang can solve the problem with the bug in seq?
Title: Re: delicate bending
Post by: dr bu on December 30, 2016, 08:13:17 AM
off topic, but its my thred *)

max crashed as i was recording. 5 minutes 24bit/44.1 aiff.
size 58.9mb. waveform blank. is there header or something that can fix?


*) any comment boosting my ego or serious issues about Max is considered: on.
.whats "common sense" about this, or forum standard?

nevermind
talking to myself...
Title: Re: delicate bending
Post by: IIO on December 30, 2016, 11:47:13 AM
"solving" means you you use [loadbang] -> "read myfile.mid" instad of typing the argument for the source file into the object box.

i guess it is rather a workaround, but it does wonders when you have trouble with using arguments.

you could also make yourself a "wrap" for seq which does this:

max v2;
#N vpatcher 226 62 826 462;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 235 169 85 9109513 prepend read;
#P newex 235 137 85 9109513 t $1;
#B color 14;
#P newex 235 105 85 9109513 loadbang;
#P outlet 192 234 15 0;
#P outlet 117 234 15 0;
#P inlet 117 143 15 0;
#P newex 117 189 85 9109513 seq;
#P connect 6 0 0 0;
#P connect 1 0 0 0;
#P connect 0 0 2 0;
#P connect 0 1 3 0;
#P connect 4 0 5 0;
#P connect 5 0 6 0;
#P pop;

this usually makes sure that your files are found and loaded at the right moment.

unless you are trying to load sprites into lcd, this is a bit more complicated to initialize things.


Title: Re: delicate bending
Post by: dr bu on December 30, 2016, 02:57:54 PM
ok. sorry
the problem with my poetry,

its not
specific
enough

the mission
is saving
a midifile
like so:

max v2;
#N vpatcher 155 174 785 628;
#P newex 37 143 71 196617 prepend write;
#P message 37 120 175 196617 Music_disc:Max_recordings:etyde_2001;
#P newex 37 182 27 196617 seq;
#P connect 1 0 2 0;
#P connect 2 0 0 0;
#P pop;

now the standard
savedialog window
keeps
popping
up
 >:(

if i dont have a crash
and my recording
get lost
 :'(


ive noticed that
this was corrected by
Max 4.6
Title: Re: delicate bending
Post by: IIO on December 31, 2016, 08:06:07 PM
moin ;)

that is simply not implemented.

detonate can do it...
Title: Re: delicate bending
Post by: IIO on January 01, 2017, 10:05:45 PM
sie diskuiteren gerade mal wieder, dass auch das curve~  object in max 7.3 immer noch die bugs und anomalitäten von vor 16 jahren enthalten, es ist zum weinen.
https://cycling74.com/forums/topic/curve-doesnt-work-with-exact-same-messages-as-line/#.WGnlULn86Tk
Title: Re: delicate bending
Post by: dr bu on January 02, 2017, 02:15:16 PM
..that might be overreacting  :)
Title: Re: delicate bending
Post by: IIO on January 02, 2017, 10:21:54 PM
one day i finally learn this C++ shit and redo all OS9 objects until they actually work.
Title: Re: delicate bending
Post by: dr bu on January 18, 2017, 10:15:30 AM
Formants in voice is very important to our image of who the character behind it might be.

You who read this, obvious as it may seem, and me being into the bending business and all, the problem, ever since Disneys chipmunks, is, shifting a (human) voice will also shift the formants. And these animal formats (i dont know how many, 3 at least, to distinguish vowels) dependent as they are on the vocal tract and not on the vocal cords, do not shift because we are not anatomically built like that.
 
I can tell the difference of an "o" from an "a", and so can you, most of the time, but as much as these (3 or more) resonating bands then, make a clear vowel at (almost) any pitch in human singing, i dont understand why plugins like the Waves UltraPitch, Steinbergs UltraVoice and Melodynes Formantshifting all should be controlled by one (1) control/parameter only.  >:(

Remedy: at Ircam they made the fof~ and the fog~, (luckily before OSX). and Miller Puckette made paf~ and formant~. i love this guys haircut/approach.
Title: Re: delicate bending
Post by: IIO on January 18, 2017, 03:38:15 PM
i´ve lost the thread... but i try to follow you... there was a thread at c74 recently where someone pointed to an article by miller puckette... where he suggested to correct the position and size of the formants of  an input to an fft pitch shifting algorithm by interpolating the result of the upsampled freqshift curve.... something like that.

because when you only move a spectral envelope for 50%, both the bandwidth and the relation between filter frequencies will be too broad.

or, the other scenario, you often watn to pitch shift but leave the formants as is, just like a singer does it...

so with 7-30 days of nerve killing work you will be able to do that right in max/msp using pfft and some fft related factory objects. but i wouldnt do it!

it is interesting that you often can still easily identify a known human voice - one among hundred - when it is properly pitch shifted (incl formant correction) for an octave or more ... this experiment proves very well how important formants are for human voices, musical instruments, and other forms of known sound events from our daily life... and it that order.

p.s. i am big fan of PAF, have you used it to make music?
Title: Re: delicate bending
Post by: IIO on January 18, 2017, 03:43:11 PM
actually i dont think i have fof~ & co for OS9, that was ircam forum only, right?

i shall put up my collection here at anytime soon.

metrophage already helped me to complete it for 2 cool things.
Title: Re: delicate bending
Post by: dr bu on January 18, 2017, 08:36:51 PM
I am a singer but i hate my own voice - at least i hate recognizing it. so i get into manipulating. a pulsetrain , some filters, resonators, a touch of white noise..i have had fun with plugins in cubase creating my own paf~.  sometimes i can't tell if the result sounds like dr bu inhaling on soar throat.
you can do some cool things in Praat as well, but its got an irritating interface.
Title: Re: delicate bending
Post by: dr bu on January 19, 2017, 10:02:51 AM
After rebuilding the desktop all my Max-files have Max 3 icons (the cross eyed nerd). :( No other files seams to be affected.  ???
Title: Re: delicate bending
Post by: dr bu on January 19, 2017, 04:19:50 PM
That should have been a thread by its own. Solution could be of general interest.

Tried a small app called Save a BNDL. Nope.
This apps readme tells me to make desktop DB and desktop DF visible and trash these. Tried that.
Title: Re: delicate bending
Post by: IIO on January 20, 2017, 12:46:12 AM
you were looking in the right direction, file icons indeed are coming out of the BNDL resource and are linked via desktio file.

but your solution was the wrong attempt. :)

you have max 3 icons most likely because there is a max 3 app somewhere on your harddisk - that includes apps made with max 3.

in casre there is a problem with the max 4 info on your disk, it should be enough to crreate afresh copy of you max 4 and max 4 runtime executables. copy, keep copy and delete original, empty trash, reboot.

Title: Re: delicate bending
Post by: dr bu on January 20, 2017, 05:15:57 AM
right. i knew that! >:( forgot to empty trash. thanks.

this is fof~ co os9  :)

ive got 500 mb Ircam stuff. i think so big because of audio. i can upload somewhere.

p.s. are you on caffeine? your spelling is deteriorating.
Title: Re: delicate bending
Post by: IIO on January 20, 2017, 01:09:10 PM
ok i will post you a link to my place later ;)
Title: Re: delicate bending
Post by: dr bu on March 07, 2017, 08:01:36 AM
Att göra en fyrkantsvåg av en sinuston är en bit av en kaka.. [<~]
Tvärtom är ett helvete.  ???
Title: Re: delicate bending
Post by: IIO on March 07, 2017, 03:50:46 PM
yes of course, because you dont know what the phase is.

in gen you can do it by finding zerocrossings, in max everything you do will only be a workaround.

p.s. are you aware of trunc~ ?
Title: Re: delicate bending
Post by: IIO on March 07, 2017, 04:02:13 PM
on a PPC machine the most cpu friedly approach should be this:

bitor~ 0 1

:)
Title: Re: delicate bending
Post by: dr bu on March 07, 2017, 11:42:18 PM
how? i dont get. my stupid math brain would check the amount of samples between the previous 2 zerocrossings in the squarewave and copy that to the sinewave, thus lagging 180°. of course this will create a slight interference between the two if the squarewave alters in frequency, but that would not be a problem for me at this point.
Title: Re: delicate bending
Post by: GaryN on March 08, 2017, 12:04:32 AM
You guys really need to get a room…
Title: Re: delicate bending
Post by: dr bu on March 08, 2017, 10:39:27 PM
No need to get jealous Gary. Obviously you got far more rooms to make out in - than me at least. :)
Title: Re: delicate bending
Post by: dr bu on March 08, 2017, 11:04:04 PM
...simply put 110, i want to let the output of weave~ drive lookup~  ;)
Title: Re: delicate bending
Post by: GaryN on March 09, 2017, 04:54:06 PM
(Sigh) Just because I have room doesn't mean I'm getting any…
Title: Re: delicate bending
Post by: IIO on March 11, 2017, 03:27:06 AM
eventually i just lost you, but your idea of zerocrossings is probably a misconception. the exact point of a zerocrossing will not be exactly at the beginning one sample.

the first sample could have a value 0.70 and the second sample a value of -0.11 - now when does the crossing happen? right: it even depends on the waveform.

best practice when you need to snyc "oscillators": start from a master phasor~ and start to generate everything else right from this.

cycle, cos, and basic arithmic and maybe also obejcts like zigzag are your first starting point for useful transfer functions controlled by a master phasor.
Title: Re: delicate bending
Post by: IIO on March 11, 2017, 03:28:27 AM
...simply put 110, i want to let the output of weave~ drive lookup~  ;)

uh oh. no percolate on windows. i am checking that tomorrow. :)
Title: Re: delicate bending
Post by: dr bu on March 12, 2017, 04:21:20 PM
tricky?  ;D
Title: Re: delicate bending
Post by: IIO on March 13, 2017, 04:27:10 AM
...i simply never used weave :)
Title: Re: delicate bending
Post by: dr bu on July 01, 2017, 06:36:43 AM
whats wrong with my paf~ ?

max v2;
#N vpatcher 283 64 1110 966;
#P newex 455 601 45 196617 loadbang;
#P newex 459 376 44 196617 +~ 100.;
#P newex 455 647 42 196617 uzi 200;
#P newex 487 679 27 196617 - 1;
#P newex 487 801 51 196617 peek~ foo;
#P newex 487 772 49 196617 pack 0 0.;
#P newex 549 707 100 196617 expr ($f1-100) /25;
#P newex 549 730 100 196617 expr exp(-$f1*$f1);
#P newex 272 570 83 196617 clip~ -0.99 0.99;
#P comment 488 425 62 196617 waveshaper;
#P newex 547 801 105 196617 buffer~ foo 4.512472;
#P newex 459 403 110 196617 lookup~ foo;
#P comment 304 522 45 196617 ring mod;
#P comment 507 379 115 196617 offset to middle of table;
#P comment 593 318 75 196617 range for table;
#P comment 589 270 63 196617 divide by F0;
#P newex 550 280 27 196617 *~;
#P comment 306 249 82 196617 cf relative to F0;
#P newex 272 519 27 196617 *~;
#P newex 459 347 101 196617 *~;
#P newex 459 324 29 196617 cos~;
#P newex 459 301 43 196617 -~ 0.25;
#P newex 459 275 39 196617 *~ 0.5;
#P newex 290 287 29 196617 sah~;
#P newex 290 139 30 196617 line~;
#P newex 550 316 39 196617 *~ 25.;
#P newex 550 243 30 196617 line~;
#P comment 542 102 59 196617 bandwidth;
#P newex 550 170 52 196617 pack 0 50;
#P newex 550 147 29 196617 mtof;
#P number 550 126 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 290 116 52 196617 pack 0 50;
#P newex 290 94 29 196617 mtof;
#P number 290 73 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 311 206 60 196617 expr 1/$f1;
#P newex 180 143 29 196617 mtof;
#P number 180 122 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P user meter~ 297 606 310 727 100 0 168 0 247 247 247 255 153 0 255 0 0;
#P user gain~ 272 606 24 100 158 0 1.071519 7.94321 10.;
#P toggle 255 803 15 0;
#P newex 272 803 50 196617 dac~;
#P comment 176 89 41 196617 freq F0;
#P comment 284 46 59 196617 center freq;
#P newex 289 406 29 196617 cos~;
#P newex 289 383 27 196617 +~;
#P newex 272 485 27 196617 +~;
#P newex 289 460 45 196617 *~;
#P newex 289 435 27 196617 -~;
#P newex 248 406 29 196617 cos~;
#P newex 248 382 27 196617 *~;
#P newex 290 348 27 196617 -~;
#P newex 290 228 31 196617 *~;
#P newex 180 233 44 196617 phasor~;
#P newex 324 326 65 196617 pong~ 1 0. 1.;
#P connect 17 0 18 0;
#P connect 18 0 1 0;
#P connect 1 0 4 0;
#P connect 4 0 5 0;
#P connect 3 0 4 1;
#P connect 5 0 8 0;
#P connect 8 0 35 0;
#P connect 35 0 45 0;
#P connect 45 0 15 0;
#P fasten 15 0 13 0 277 765 277 765;
#P hidden connect 14 0 13 0;
#P connect 4 0 9 0;
#P connect 9 0 10 0;
#P connect 10 0 6 0;
#P connect 6 0 7 0;
#P connect 7 0 8 1;
#P connect 42 0 35 1;
#P connect 20 0 21 0;
#P connect 21 0 22 0;
#P connect 22 0 29 0;
#P connect 29 0 2 0;
#P connect 2 0 30 0;
#P connect 30 0 3 0;
#P hidden connect 15 0 16 0;
#P connect 1 0 9 1;
#P connect 5 0 6 1;
#P connect 0 0 3 1;
#P connect 1 0 30 1;
#P connect 18 0 19 0;
#P connect 19 0 2 1;
#P fasten 15 0 13 1 277 765 317 765;
#P connect 30 0 0 0;
#P connect 0 0 7 1;
#P connect 53 0 51 0;
#P connect 1 0 31 0;
#P connect 31 0 32 0;
#P connect 32 0 33 0;
#P connect 33 0 34 0;
#P connect 34 0 52 0;
#P connect 52 0 42 0;
#P connect 51 2 50 0;
#P connect 50 0 48 0;
#P connect 48 0 49 0;
#P connect 46 0 48 1;
#P connect 50 0 47 0;
#P connect 47 0 46 0;
#P connect 23 0 24 0;
#P connect 24 0 25 0;
#P connect 25 0 27 0;
#P connect 27 0 37 0;
#P connect 37 0 28 0;
#P connect 28 0 34 1;
#P connect 19 0 37 1;
#P pop;
Title: Re: delicate bending
Post by: IIO on July 03, 2017, 07:11:35 AM

all i see is that i dont hear anything.

you cant just replace samphold~ with sah~ i guess, samphold~ is more.

save this as 110.pd.samphold~

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 139 181 53 196617 >~ -1;
#P newex 217 199 53 196617 gate~;
#P outlet 343 217 15 0;
#P inlet 61 148 15 0;
#P inlet 139 73 15 0;
#P newex 260 164 53 196617 sah~;
#P newex 343 164 53 196617 gate~;
#P newex 428 146 53 196617 ==~ -1;
#P newex 139 128 53 196617 change~;
#P connect 0 0 8 0;
#P connect 0 0 1 0;
#P connect 5 0 3 0;
#P connect 5 0 2 1;
#P connect 7 0 6 0;
#P connect 2 0 6 0;
#P connect 1 0 2 0;
#P connect 1 0 3 1;
#P connect 3 0 7 1;
#P connect 8 0 7 0;
#P connect 4 0 0 0;
#P window clipboard copycount 9;

another trap to check for is floating point. in pd there is only float. so in max one have to add a 0. in some cases. except for mtof of course :)
Title: Re: delicate bending
Post by: IIO on July 03, 2017, 07:17:52 AM
Title: Re: delicate bending
Post by: dr bu on July 04, 2017, 05:05:16 PM
ok. done. still, does not seem right. preset 1 sounds ok, but changing values like the other presets does not. i suspect something is wrong with the lookup~/bufferwindow settings...

max v2;
#N vpatcher 166 61 1338 1000;
#P flonum 450 285 35 9 0. 100. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 364 387 35 9 0. 100. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;
#N vpreset 8;
#X append 1 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 59 \; 20 57 161 number int 65 \; 23 110 421 number int 60 \; 55 387 364 flonum;
#X append 1 2 float 0. \; 56 285 450 flonum float 0.25 \;;
#X append 2 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 61 \; 20 57 161 number int 71 \; 23 110 421 number int 89 \; 55 387 364 flonum;
#X append 2 2 float 0. \; 56 285 450 flonum float 0.25 \;;
#X append 3 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 61 \; 20 57 161 number int 71 \; 23 110 421 number int 122 \; 55 387 364 flonum;
#X append 3 2 float 0. \; 56 285 450 flonum float 0.25 \;;
#X append 4 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 61 \; 20 57 161 number int 71 \; 23 110 421 number int 139 \; 55 387 364 flonum;
#X append 4 2 float 0. \; 56 285 450 flonum float 0.25 \;;
#X append 5 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 31 \; 20 57 161 number int 83 \; 23 110 421 number int 59 \; 55 387 364 flonum;
#X append 5 2 float 0. \; 56 285 450 flonum float 0.25 \;;
#X append 6 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 31 \; 20 57 161 number int 83 \; 23 110 421 number int 59 \; 55 387 364 flonum;
#X append 6 2 float 100. \; 56 285 450 flonum float 0.25 \;;
#X append 7 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 22 \; 20 57 161 number int 83 \; 23 110 421 number int 59 \; 55 387 364 flonum;
#X append 7 2 float 100. \; 56 285 450 flonum float 25. \;;
#X append 8 2 14 787 126 toggle int 1 \; 15 590 143 gain~ list 87 10. \; 17 106 51 number int 22 \; 20 57 161 number int 61 \; 23 110 421 number int 34 \; 55 387 364 flonum;
#X append 8 2 float 100. \; 56 285 450 flonum float 25. \;;
#P preset 540 192 47 27;
#P newex 596 81 45 196617 loadbang;
#P newex 330 409 44 196617 +~ 100.;
#P newex 596 129 42 196617 uzi 200;
#P newex 628 161 27 196617 - 1;
#P newex 628 283 51 196617 peek~ foo;
#P newex 628 254 49 196617 pack 0 0.;
#P newex 690 189 100 196617 expr ($f1-100) /25;
#P newex 690 212 100 196617 expr exp(-$f1*$f1);
#P newex 143 554 83 196617 clip~ -0.99 0.99;
#P comment 359 458 62 196617 waveshaper;
#P newex 688 283 105 196617 buffer~ foo 4.512472;
#P newex 330 436 110 196617 lookup~ foo;
#P comment 177 504 45 196617 ring mod;
#P comment 386 412 115 196617 offset to middle of table;
#P comment 464 309 75 196617 range for table;
#P comment 460 254 63 196617 divide by F0;
#P newex 421 264 27 196617 *~;
#P comment 177 233 82 196617 cf relative to F0;
#P newex 143 503 27 196617 *~;
#P newex 330 331 101 196617 *~;
#P newex 330 308 29 196617 cos~;
#P newex 330 285 43 196617 -~ 0.25;
#P newex 330 259 39 196617 *~ 0.5;
#P newex 161 271 89 196617 110.pd.samphold~;
#P newex 161 123 30 196617 line~;
#P newex 421 307 39 196617 *~ 25.;
#P newex 421 227 30 196617 line~;
#P comment 413 86 59 196617 bandwidth;
#P newex 421 154 52 196617 pack 0 50;
#P newex 421 131 29 196617 mtof;
#P number 421 110 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 161 100 52 196617 pack 0 50;
#P newex 161 78 29 196617 mtof;
#P number 161 57 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 182 190 60 196617 expr 1/$f1;
#P newex 51 127 29 196617 mtof;
#P number 51 106 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P user meter~ 168 590 181 711 100 0 168 0 247 247 247 255 153 0 255 0 0;
#P user gain~ 143 590 24 100 158 0 1.071519 7.94321 10.;
#P toggle 126 787 15 0;
#P newex 143 787 50 196617 dac~;
#P comment 47 73 41 196617 freq F0;
#P comment 155 30 59 196617 center freq;
#P newex 160 390 29 196617 cos~;
#P newex 160 367 27 196617 +~;
#P newex 143 469 27 196617 +~;
#P newex 160 444 45 196617 *~;
#P newex 160 419 27 196617 -~;
#P newex 119 390 29 196617 cos~;
#P newex 119 366 27 196617 *~;
#P newex 161 332 27 196617 -~;
#P newex 161 212 31 196617 *~;
#P newex 51 217 44 196617 phasor~;
#P newex 195 310 65 196617 pong~ 1 0. 1.;
#P connect 17 0 18 0;
#P connect 18 0 1 0;
#P connect 1 0 4 0;
#P connect 4 0 5 0;
#P connect 3 0 4 1;
#P connect 5 0 8 0;
#P connect 8 0 35 0;
#P connect 35 0 45 0;
#P connect 45 0 15 0;
#P fasten 15 0 13 0 148 749 148 749;
#P hidden connect 14 0 13 0;
#P connect 4 0 9 0;
#P connect 9 0 10 0;
#P connect 10 0 6 0;
#P connect 6 0 7 0;
#P connect 7 0 8 1;
#P connect 42 0 35 1;
#P connect 20 0 21 0;
#P connect 21 0 22 0;
#P connect 22 0 29 0;
#P connect 29 0 2 0;
#P connect 2 0 30 0;
#P connect 30 0 3 0;
#P hidden connect 15 0 16 0;
#P connect 1 0 9 1;
#P connect 5 0 6 1;
#P connect 0 0 3 1;
#P connect 18 0 19 0;
#P connect 19 0 2 1;
#P fasten 15 0 13 1 148 749 188 749;
#P connect 30 0 0 0;
#P connect 0 0 7 1;
#P connect 1 0 30 1;
#P connect 1 0 31 0;
#P connect 31 0 32 0;
#P connect 32 0 33 0;
#P connect 33 0 34 0;
#P connect 34 0 52 0;
#P connect 52 0 42 0;
#P connect 55 0 52 1;
#P connect 23 0 24 0;
#P connect 24 0 25 0;
#P connect 25 0 27 0;
#P connect 27 0 37 0;
#P connect 37 0 28 0;
#P connect 28 0 34 1;
#P connect 19 0 37 1;
#P connect 56 0 28 1;
#P connect 53 0 51 0;
#P connect 51 2 50 0;
#P connect 50 0 48 0;
#P connect 48 0 49 0;
#P connect 46 0 48 1;
#P connect 50 0 47 0;
#P connect 47 0 46 0;
#P pop;
Title: Re: delicate bending
Post by: IIO on July 05, 2017, 02:16:51 AM
have you compared against my paf-modulator yet?
Title: Re: delicate bending
Post by: IIO on July 05, 2017, 02:19:58 AM
https://cycling74.com/forums/re-patching-old-externals/
Title: Re: delicate bending
Post by: dr bu on July 05, 2017, 02:29:26 AM
Like to see it very much. Do you happen to have it in 4.1? :)
Title: Re: delicate bending
Post by: IIO on July 05, 2017, 02:34:01 AM
i mostyl post in 4.x to the forums. you only need to remove the .mxb file extension.
Title: Re: delicate bending
Post by: IIO on July 05, 2017, 02:40:35 AM
your bell curve looks ok and there ius also signal output at your lookup table. no idea why the frequecnies would be wrong.

the only thing i noticed is that your buffer doesnt initialize on load. i am also unsure why, the patch seems right.

Title: Re: delicate bending
Post by: IIO on July 05, 2017, 02:42:26 AM
i found out that macminis make a great standalone synth when you know max. :)
Title: Re: delicate bending
Post by: dr bu on September 17, 2017, 10:02:31 AM
 :o
Title: Re: delicate bending
Post by: IIO on September 17, 2017, 07:11:23 PM
time to reboot.
Title: Re: delicate bending
Post by: dr bu on September 18, 2017, 11:46:32 AM
Guess so my friend ;) ..but what does it imply technically?  I've never seen this message regarding any other program. Is there a way to avoid this type of crash?
Title: Re: delicate bending
Post by: IIO on September 19, 2017, 09:27:44 AM
it should (i.e. unless something went really, really wrong) imply that the MacOS thinks the app is still open.

i have seen that once, but cant remember in what context or with which program it was.

quitting an app with a third party process killer which doesnt work right could cause that, or maybe faulty RAM, i am not sure what in OS9 is whatching open processes and i dont think one can refresh that info other than rebooting.

it´s ok now or did it come back?
Title: Re: delicate bending
Post by: IIO on September 19, 2017, 09:35:22 AM
in osx there is a "list of open files" which doesnt make a difference between executables, documents and for examples disk images (you may have seen that before when putting a file from a toast image or dmg into the trash and attempt to empty it)

in OS9 i think it is different, there must be something like a "process watcher".

next time you see this, check what system profiler & co say about currently running processes.
Title: Re: delicate bending
Post by: dr bu on September 24, 2017, 01:15:59 PM
.. its OK.  My Titan Mactron recover cd system SSD is inclined to this.  Not the Gigabit Ethernet swedish 9.2.2 15 years IDEATA whatever though. So what to look for in System profiler i don't get..
Title: Re: delicate bending
Post by: IIO on September 24, 2017, 04:52:06 PM
as long as it is not your max patch all is good.
Title: Re: delicate bending
Post by: dr bu on September 24, 2017, 09:58:01 PM
hmm...
Title: Re: delicate bending
Post by: dr bu on October 02, 2017, 09:47:55 PM
...what would be the best setup for running Max do you think?  or which is yours?
Title: Re: delicate bending
Post by: dr bu on October 03, 2017, 03:04:14 AM
Got myself new glasses today.
Title: Re: delicate bending
Post by: IIO on October 11, 2017, 11:34:28 AM
hard to tell.

since dual processor support started with 4.6 for OS) only any single processor G4 with cache should be fine.

the machines without cache such as the 733 and some powerbooks get deep in trouble with some FFT tasks and certain third party objects.

my main computers are a 933 and a dual 1.25 "native". i use mostly the single processor machine.

when you have GUI stuff runnning and the high priority thread is on, it feels fine up to 25% CPU for audio processing, and imagery and jitter stuff stops working at about 80% audio CPU.

at a vectorsize of 32, that is.

...

my reference machine for pluggo projects / single DSP applications used to be the titanium powerbook 400.

90% there is like 20% on the 933.
Title: Re: delicate bending
Post by: dr bu on February 21, 2018, 09:03:31 PM
...
Title: Re: delicate bending
Post by: IIO on March 31, 2018, 02:21:56 PM
hjälp, hjälp! :P
Title: Re: delicate bending
Post by: Protools5LEGuy on April 03, 2018, 11:55:32 AM
...what would be the best setup for running Max do you think?  or which is yours?
1.25GHz Mini yet to arrive and already considering
overclocking to 1.5 and a larger than 80mb HD. :o

i´ve got a 1,25 1,33 and 1,42 here, the 1.5 silent upgrade is hard to find (and i am not sure if 5.5% are worth the hassle.)

the 1.5 is aboputt as rare as the mini server and sellers asking for fantasy prices.

Cant wait to see what that MAX Farm running can do !

 :o
Title: Re: delicate bending
Post by: IIO on April 03, 2018, 12:05:16 PM
my current "max farm" is an XServe 8x2,25 Xeon and i can tell you it can do a LOT (compared to a G4!)

with its dual gigabit network you can control it with OSC or IPMidi easily when used a music instrument - but of course i mostly use it to render stuff offline.

first thing i will do with a working-audio OS9-mini is releated to tokio rather than max. or a combination of both? :P
Title: Re: delicate bending
Post by: dr bu on April 04, 2018, 12:43:18 AM
hjälp, hjälp! :P

Right, thats the hotline IIO-button/menu. Not fully implemented yet.
Title: Re: delicate bending
Post by: IIO on April 08, 2018, 05:08:58 PM
tomorrow a bunch of small audio IOs arrive here, and i will start setting up an OS9 mini with max & co.
Title: Re: delicate bending
Post by: IIO on September 08, 2018, 01:14:42 PM
i deleted the above paf patches.

1. the naming scheme was weird; the phase is not the carrier, it is the phase.
"carrier" and "modulator" are now properly used as specified by the ucsd.edu tutorial.

2. phase of master phasor can be reset at audio rate now, so that you can synchronize many oscillators of the same (or different) frequencies.

3.  included alternative layout using single connections between the modules in the "-x" versions of the patches. see example file.

use the "-x" ones as default; only go back to the multiple-inlet versions when you have trouble with the "-x"  stuff.

(the zip is made in OS9 using stuff it - for OS9 pls remove the .mxb)
Title: Re: delicate bending
Post by: dr bu on September 09, 2018, 12:04:53 AM
Ok.. interesting  :)
Title: Re: delicate bending
Post by: IIO on September 09, 2018, 01:34:57 AM
eventually it is a bit confusing to use note numbers (or actually: numbers of notes) for the bandwidth. you might want to use octaves instead.
Title: Re: delicate bending
Post by: dr bu on September 09, 2018, 04:16:21 AM
puckette made [formant~] back in `95 (found in IRCAM PMA-lib) presenting "live formant tracking"!
i want to feed its output (3 formants) into pafs and fofs but helpfile is way over my head.   >:(

your nomenclature is impressive. it does not always suit my needs, but i steal what i can.   ;D
Title: Re: delicate bending
Post by: IIO on September 09, 2018, 07:29:32 AM
i dont think i ever used that, if it is for the FOF object then it is very oldschool.

however, i have tried to make the two available vowel libraries work with the PAF long ago - and it is not so easy.

the IRCAM one only works with partials and has no bandwidth parameter, and the CSound database has bandwidth - but less vowels.

you can try to use my new helpfile and apply 3-formant vowel data to it, you will see that it doesnt work until you start to freely scale the data.

and of course, if you apply soprano vowels to you filters/partials/fof/paf, make sure you only play base frequencies in the correct range. :)

Title: Re: delicate bending
Post by: IIO on September 09, 2018, 07:32:12 AM
oh, i misread, that was for recording/analysing? i´ve used praat once but it feels like trial and error.
Title: Re: delicate bending
Post by: dr bu on September 09, 2018, 10:04:47 AM
i´ve used praat once but it feels like trial and error.
sure does. and its not real time.

[formant~] comes in PD too. if i were not so shy and lazy i would ask those guys to explain it..
Title: Re: delicate bending
Post by: IIO on September 09, 2018, 11:45:05 AM
i´ve made up this data by averaging the values from dozens of different sources.

russian 28 48
black 36 51
basso 38 63
baritone 43 68
tenor 48 70
alto 52 75
mezzo 55 78
soprano 60 81
falsetto 52 89

only when you stay in this frequency range, applying vowel formats will "work" as supposed to.



Title: Re: delicate bending
Post by: IIO on September 09, 2018, 12:04:04 PM
installed formant~

probably not difficutl to tell whart the output is - but i dont get the output data to change at all (when testing with the FM) wtf?

however, i think it´s LPC. i.e. not so much "fiddle" at all here, rather its own class.

on OSX you have plenty of alternatives... FTM, rtcmix, the zsa stuff...

p.s.
there is also an object called lpc from ircam, which is OS9 only. but it only does the lpc itself and leaves you with a bunch of IIR coefficients.

p.p.s
while you probably understand what my "justine" does :) , since the helpfile is missing i should add that you have to add the key as argument in order to get the right ratios (0-11 for C-Bb)
Title: Re: delicate bending
Post by: dr bu on December 01, 2018, 07:07:31 AM
So yhis guy: https://www.cycfi.com/2018/03/fast-and-efficient-pitch-detection-bitstream-autocorrelation/ appearently found an interesting way to grab f0. I dont know phyton so pondering if it possible to realize in old squarebox Max?

https://github.com/cycfi/bitstream_autocorrelation/blob/master/bcf.py
zerox/weave, + bit operators + ??
Title: Re: delicate bending
Post by: IIO on January 20, 2019, 06:35:20 PM
when i remember correctly, correlation analysis patch is difficult in OS9 because it requires an object we dont have.