I would have thought that with the python opcodes and Tkinter's canvas,
you'd be able to do a nice one in no time at all.

Victor
----- Original Message ----- 
From: "Oeyvind Brandtsegg" 
To: 
Sent: Sunday, January 27, 2008 10:20 AM
Subject: [Csnd] Re: prototype FLTK based ftable "graphic" editor


> This is interesting,
> however, I find it a bit hard to edit graphically without seeing the
> result displayed.
>
> For a Wx implementation of something similar, have a look at the
> graph.py module that comes with PartikkelExplorer. It's a general data
> plotting module, but in PartikkelExplorer it is used for editing
> csound ftables with the mouse.
> It has a simple test build in if you run it as main (that is, just
> double click the file, or type "python graph.py" on the commandline).
> The graphics are ugly as hell, I am the first to admit, but it works.
>
> Oeyvind
>
> 2008/1/27, Tim Mortimer :
>>
>> AS crappy as this is, i have attempted to write a ftable editor using 
>> only
>> FLTK widgets!
>>
>> The aptly named FLjoy proved to be about the best fit for the job in the
>> end.
>>
>> unfortunately FLsetVal doesn't seem to work for sliders that have 
>> inverted
>> min / max values...
>>
>> in this example illustrative csd attached, the x axis is pitch, & the y 
>> axis
>> is keyscaled db values
>>
>> The left mouse button in the FLjoy target zone plays back the appropriate
>> index at the appropriate dB
>>
>> the right mouse button allows for rewriting of the current target ftable
>> index.
>>
>> So with the right mouse button held down you can quickly, easily, (albeit
>> roughly) fashion some sort of whimsical ftable shape -
>>
>> i mainly designed this with parameter mapping in mind, rather than 
>> drawing
>> oscillator shapes - & as such, it's also meant to be an editing rather 
>> than
>> performance interface element (i'll be unleashing them en masse in my
>> planned "ambient supersyn"
>>
>> selecting Index Lock allows for fine tuning of the currently selected 
>> index
>> (by depressing the right mouse button) without the worry of accidently
>> slipping over into a neighbouring bin
>>
>> The value is displayed in the text box, & also in the slider to the right 
>> of
>> the joystick space.
>>
>> Don't alter the text boxes, they are for display purposes only
>>
>> I look forward to suggestions for improvements - or even better
>> demonstrations of improvements - or even better yet the WXPython realtime
>> ftable editor that someone else is now going to go away & write, wherein 
>> the
>> tables fields are all displayed & responsive to changes within the mouse
>> editing space itself!
>>
>> & to think it only took me about 16 hours! (he said sarcastically, 
>> thinking
>> it might take 3 or 4 at the most...)
>>
>> http://www.nabble.com/file/p15117478/fljoy.csd fljoy.csd
>>
>> happy hunting
>>
>> T.
>> --
>> View this message in context: 
>> http://www.nabble.com/prototype-FLTK-based-ftable-%22graphic%22-editor-tp15117478p15117478.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

...and it might be easier to start from tabdes or linseg

I don't know what tabdes is. it shows up on nabble search but couldn't find
in the manual. is it documented?

linseg wouldn't work in a realtime way would it? (in you couldn't define new
points on the fly..) how would that work?

& this is mainly to map against keys (or "temprament") but obviously has
broader application (particularly re what i was saying about sound design &
reducing it to pitch, time, & amplitude continuums....as all you domains
here become an editing continuum ... but feed a phasor in on the time axis &
you have "playback"......

but individual tone colours on each key now also becomes a hopefully easy to
edit & achieve realtime possibility...(once i feed the midi in,..) + i have
all my python control i made for garritan just waiting to be hooked up to
csound

i'll look at tkinter too - i was wondering why i couldn't find "canvas" in
wx....

but what this says to me is that just one or 2 additions to the in house
fltk set could be all that's reqd to do something quite useable & totally
"in house" to csound... (basically if fljoy could somehow have a refreshable
graphics background. monochromatic fine...)

what about the new image opcodes?

i'm def ready for 5.08..... 




root-77 wrote:
> 
> ...and it might be easier to start from tabdes or linseg
> 
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/prototype-FLTK-based-ftable-%22graphic%22-editor-tp15117478p15118484.html
Sent from the Csound - General mailing list archive at Nabble.com.

http://www.nabble.com/3rd-party-function-generators-tt7987932.html#a8030340

found tabdes info... thought we'd been there before...

not sure any of that's gonna fit in with my realtime editing with sonorous
feedback situasheeun! but i'd love to hear to the contrary....

thanks & more feedback & discussion welcome 
-- 
View this message in context: http://www.nabble.com/prototype-FLTK-based-ftable-%22graphic%22-editor-tp15117478p15118533.html
Sent from the Csound - General mailing list archive at Nabble.com.

Done some research this morning. More likely to try tkinter at this stage -
there is more direct documented tutorial info for the actual canvas object.
wx looks a bit daunting to pick up without a lot of patience (wish i was
able to come to Michels New York Csound group for Boa Constructor demo top
of the list! - i'd never leave though once i got onto Silence though, would
i.....), & csound & python proper are already giving me enough reason to
exercise plenty of patience for the mo...

I noticed in my csd that the label under fljoy is wrong. i was going to
rotate the axes at one point, but then realised didn't have to, & forgot to
change the label back...

So Oeyvind if you were saying "i can't see the tables values" based on that,
well, you can - the value slider at the right indicates the current value -
x is index, & y therefore is value (but assumedly you had worked this out)

i'm going to put a value slider either side of the display for immediate
neighbour comparison, & thats about it. For what it provides with so few
elements i'm reasonably happy, & thus felt it was worth sharing -
particularly if like me, you are impatient & are just wanting some way to
get started...& this is a subject that continually crops up from novice to
intermediate level users.

the capacity to align the fljoy crosshair with the existing value to the
right of the joystick area i think is quite a cool way to edit once you get
into it.

so much of what i have done to this point with csound has been about geting
basic processes happening. this will open the door to designing sounds with
diverse but related parametric dependencies, which i always knew had to be
the next step. 

a deceptively complex domain begging for simple insightful solutions....  

haven't you got something like the tkinter solution your proposing already
then victor? i'd be very keen to study, learn, & make use of it if that's at
all possible...

so i'm definately discovering a realtime dimension to working with csound.
but it's concerned more with design than performance....


Oeyvind Brandtsegg-2 wrote:
> 
> I think wx.BufferedDC is what you'd call "canvas"  in wx.
> The DC is for Device Context, a generic interface to a buffer that can
> be used for drawing onto the screen or for printing, and probably for
> a lot of other things.
> Oeyvind
> 
> 2008/1/27, Tim Mortimer :
>> i'll look at tkinter too - i was wondering why i couldn't find "canvas"
>> in
>> wx....
>>
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-- 
View this message in context: http://www.nabble.com/prototype-FLTK-based-ftable-%22graphic%22-editor-tp15117478p15126775.html
Sent from the Csound - General mailing list archive at Nabble.com.

Try reading the table in the "normal way" (some sort of oscillator or table
opcode -- oscil1 may be good) and sending the signal to the fout opcode.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

Brian Wong wrote on 1/28/08 7:13 PM:

> The opcode ftsave saves a version of an ftable that is NOT compatible with a
> WAVE file. How would I go about  saving a version that IS compatible with a
> wave file?

Maybe you want fout instead of ftsave?

Cheers,
Andrés

El lun, 28-01-2008 a las 20:13 -0400, Brian Wong escribió:
> The opcode ftsave saves a version of an ftable that is NOT compatible
> with a WAVE file. How would I go about  saving a version that IS
> compatible with a wave file?
> 
> 
> ______________________________________________________________________