Casio CZ/ VZ/ FZ - Pro Series

Okay people, so I wrote this new piece of software for CZs.  It's
called CZWIGOUT, and it makes random patches for all CZs.  It's
different than other random patch creators because it takes advantages
of all hidden features I know about, and can randomize all of the
parameters of a CZ-1. (Most stuff I've seen was made for CZ-101, and
didn't do hidden features.)

Ready for use on Windows, though it hasn't been tested on many
systems. Try it and let me know.  It doesn't have to be installed,
doesn't have any dependencies, doesn't touch the registry.

The executable is too big (2.7 Mb) because it's written with Python,
and so there has to be a mini Python interpreter bundled with it.  It
works fine though, just a little bigger than you might expect.

It's easy to use and I wrote a bunch of documentation for it, it's in
the menu under "Tips".

Anyway, give it a try if you're interested and let me know what you
think.  I've already had a lot of fun with it!

http://www.kasploosh.com/11872/11872-CZWIGOUT.html

wow, this is seriously genius stuff :)
this is exactly what I was hoping somebody would make for the CZ!
I tried and didn't have much luck with the Midi Quest randomize function
(mostly cos my CZ101's WRITE button is borken) but this looks perfect!
can't wait to try it out after work tonight - will let you know :)
thx for putting the hard work in!

greetings from south west France
Erwan

On Thu, Feb 21, 2008 at 1:55 AM, Fulfil Objective <kasploosh@...> wrote:

> Okay people, so I wrote this new piece of software for CZs.  It's
> called CZWIGOUT, and it makes random patches for all CZs.  It's
> different than other random patch creators because it takes advantages
> of all hidden features I know about, and can randomize all of the
> parameters of a CZ-1. (Most stuff I've seen was made for CZ-101, and
> didn't do hidden features.)
>
> Ready for use on Windows, though it hasn't been tested on many
> systems. Try it and let me know.  It doesn't have to be installed,
> doesn't have any dependencies, doesn't touch the registry.
>
> The executable is too big (2.7 Mb) because it's written with Python,
> and so there has to be a mini Python interpreter bundled with it.  It
> works fine though, just a little bigger than you might expect.
>
> It's easy to use and I wrote a bunch of documentation for it, it's in
> the menu under "Tips".
>
> Anyway, give it a try if you're interested and let me know what you
> think.  I've already had a lot of fun with it!
>
> http://www.kasploosh.com/11872/11872-CZWIGOUT.html
>
>
>
>
> Yahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]

Thanks for creating and sharing CZWigOut. I don't have a CZ hooked up 
to the computer, so I can't test the patches, but I like the ease and 
simplcity of the User Interface.

Are you open to suggestions? (I hope so.) 
If so, here's just a few that immediate reactions:

1. Add a check all button
 a. for all
 b. for each section

2. Allow users to set allowable ranges for each parameter.
3. Allow the check states and allowable ranges to be stored in user 
named files [parameter profiles].
4. Allow users to load parameter profiles.
5. Have banks (8, 16) for parameter profiles so users can create a 
set with patches based on different parameter profiles.

Please note, this is just an initial wish list, not intended to 
detract from the work you have done. I think its great that you did 
this and hope you can develope it further, perhaps with other Casio 
user wish lists.

And if you want to do a VZWigOut, I'd be interested in that.

Again, thanks for sharing this.

--Steve

just perfect! thanks so much for creating this :)
Erwan

On Thu, Feb 21, 2008 at 3:19 PM, steve_the_composer <smw-mail@...>
wrote:

> Thanks for creating and sharing CZWigOut. I don't have a CZ hooked up
> to the computer, so I can't test the patches, but I like the ease and
> simplcity of the User Interface.
>
> Are you open to suggestions? (I hope so.)
> If so, here's just a few that immediate reactions:
>
> 1. Add a check all button
>  a. for all
>  b. for each section
>
> 2. Allow users to set allowable ranges for each parameter.
> 3. Allow the check states and allowable ranges to be stored in user
> named files [parameter profiles].
> 4. Allow users to load parameter profiles.
> 5. Have banks (8, 16) for parameter profiles so users can create a
> set with patches based on different parameter profiles.
>
> Please note, this is just an initial wish list, not intended to
> detract from the work you have done. I think its great that you did
> this and hope you can develope it further, perhaps with other Casio
> user wish lists.
>
> And if you want to do a VZWigOut, I'd be interested in that.
>
> Again, thanks for sharing this.
>
> --Steve
>
>
>
>
> Yahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]

De rien. :c] 

I'm glad you will be able to use it.  Let me know if you notice anything that's not working on it.  What CZ are you using?

--- In CZsynth@yahoogroups.com, "Erwan Bezie" <lebonze@...> wrote:

>
> just perfect! thanks so much for creating this :)
> Erwan
> 
> On Thu, Feb 21, 2008 at 3:19 PM, steve_the_composer <smw-mail@...>
> wrote:
> 
> > Thanks for creating and sharing CZWigOut. I don't have a CZ hooked up
> > to the computer, so I can't test the patches, but I like the ease and
> > simplcity of the User Interface.
> >
> > Are you open to suggestions? (I hope so.)
> > If so, here's just a few that immediate reactions:
> >
> > 1. Add a check all button
> >  a. for all
> >  b. for each section
> >
> > 2. Allow users to set allowable ranges for each parameter.
> > 3. Allow the check states and allowable ranges to be stored in user
> > named files [parameter profiles].
> > 4. Allow users to load parameter profiles.
> > 5. Have banks (8, 16) for parameter profiles so users can create a
> > set with patches based on different parameter profiles.
> >
> > Please note, this is just an initial wish list, not intended to
> > detract from the work you have done. I think its great that you did
> > this and hope you can develope it further, perhaps with other Casio
> > user wish lists.
> >
> > And if you want to do a VZWigOut, I'd be interested in that.
> >
> > Again, thanks for sharing this.
> >
> > --Steve
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> 
> 
> [Non-text portions of this message have been removed]
>

Steve,

Those are all great ideas, so thanks for the suggestions. Here are a few thoughts on those suggestions:

1a & 1b are already implemented.  The check all button is the mascot button.  And the heading at the top of each section is also a button that will toggle all of the checkboxes in that section.

3 and 4 are things I thought about and decided not to do, at least for now.  I didn't want to get involved with file save and file open dialogs.  It's certainly possible, but I'm a little worn out of it at the moment.  But these are not out of the question for future versions.

2 and 5 are things that might be out of the scope of this project.  The goal of this project was randomness and simplicity.  When you get down to specifying ranges for parameters, that would almost be designing a patch editor.  So there's the philosophical question of whether it should become more like a patch editor or remain like a patch droid.  In my mind I was thinking of this as just a randomizer, but I guess there's no reason to add more precision if it's not too difficult.

Thanks for your ideas.



--- In CZsynth@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:

>
> Thanks for creating and sharing CZWigOut. I don't have a CZ hooked up 
> to the computer, so I can't test the patches, but I like the ease and 
> simplcity of the User Interface.
> 
> Are you open to suggestions? (I hope so.) 
> If so, here's just a few that immediate reactions:
> 
> 1. Add a check all button
>  a. for all
>  b. for each section
> 
> 2. Allow users to set allowable ranges for each parameter.
> 3. Allow the check states and allowable ranges to be stored in user 
> named files [parameter profiles].
> 4. Allow users to load parameter profiles.
> 5. Have banks (8, 16) for parameter profiles so users can create a 
> set with patches based on different parameter profiles.
> 
> Please note, this is just an initial wish list, not intended to 
> detract from the work you have done. I think its great that you did 
> this and hope you can develope it further, perhaps with other Casio 
> user wish lists.
> 
> And if you want to do a VZWigOut, I'd be interested in that.
> 
> Again, thanks for sharing this.
> 
> --Steve
>

Fulfil
I'm using a worn out CZ101.
I must say that the CZwigout works beautifully. All i did was click the
mascot button, and I got some really, really, mad sounds :)
thx again!
Erwan

On Thu, Feb 21, 2008 at 11:46 PM, Fulfil Objective <kasploosh@...>
wrote:

> Steve,
>
> Those are all great ideas, so thanks for the suggestions. Here are a few
> thoughts on those suggestions:
>
> 1a & 1b are already implemented.  The check all button is the mascot
> button.  And the heading at the top of each section is also a button that
> will toggle all of the checkboxes in that section.
>
> 3 and 4 are things I thought about and decided not to do, at least for
> now.  I didn't want to get involved with file save and file open dialogs.
>  It's certainly possible, but I'm a little worn out of it at the moment.
>  But these are not out of the question for future versions.
>
> 2 and 5 are things that might be out of the scope of this project.  The
> goal of this project was randomness and simplicity.  When you get down to
> specifying ranges for parameters, that would almost be designing a patch
> editor.  So there's the philosophical question of whether it should become
> more like a patch editor or remain like a patch droid.  In my mind I was
> thinking of this as just a randomizer, but I guess there's no reason to add
> more precision if it's not too difficult.
>
> Thanks for your ideas.
>
>
>
> --- In CZsynth@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
> >
> > Thanks for creating and sharing CZWigOut. I don't have a CZ hooked up
> > to the computer, so I can't test the patches, but I like the ease and
> > simplcity of the User Interface.
> >
> > Are you open to suggestions? (I hope so.)
> > If so, here's just a few that immediate reactions:
> >
> > 1. Add a check all button
> >  a. for all
> >  b. for each section
> >
> > 2. Allow users to set allowable ranges for each parameter.
> > 3. Allow the check states and allowable ranges to be stored in user
> > named files [parameter profiles].
> > 4. Allow users to load parameter profiles.
> > 5. Have banks (8, 16) for parameter profiles so users can create a
> > set with patches based on different parameter profiles.
> >
> > Please note, this is just an initial wish list, not intended to
> > detract from the work you have done. I think its great that you did
> > this and hope you can develope it further, perhaps with other Casio
> > user wish lists.
> >
> > And if you want to do a VZWigOut, I'd be interested in that.
> >
> > Again, thanks for sharing this.
> >
> > --Steve
> >
>
>
>
>
> Yahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]

Yeah, that's the same thing I've been doing with it.  If you end up making some crazy sounding recordings using CZWIGOUT patches, maybe you could send me an MP3 or something.  The more crazy sounding the better!  I would like to put some demos on the project page.

For that matter, people could post things to this group.  You know, for this group being a music group, there is surprisingly little music posted here!  Almost all the topics are about how to repair the things or make them work!

--- In CZsynth@...m, "Erwan Bezie" <lebonze@...> wrote:

>
> Fulfil
> I'm using a worn out CZ101.
> I must say that the CZwigout works beautifully. All i did was click the
> mascot button, and I got some really, really, mad sounds :)
> thx again!
> Erwan
> 
> On Thu, Feb 21, 2008 at 11:46 PM, Fulfil Objective <kasploosh@...>
> wrote:
> 
> > Steve,
> >
> > Those are all great ideas, so thanks for the suggestions. Here are a few
> > thoughts on those suggestions:
> >
> > 1a & 1b are already implemented.  The check all button is the mascot
> > button.  And the heading at the top of each section is also a button that
> > will toggle all of the checkboxes in that section.
> >
> > 3 and 4 are things I thought about and decided not to do, at least for
> > now.  I didn't want to get involved with file save and file open dialogs.
> >  It's certainly possible, but I'm a little worn out of it at the moment.
> >  But these are not out of the question for future versions.
> >
> > 2 and 5 are things that might be out of the scope of this project.  The
> > goal of this project was randomness and simplicity.  When you get down to
> > specifying ranges for parameters, that would almost be designing a patch
> > editor.  So there's the philosophical question of whether it should become
> > more like a patch editor or remain like a patch droid.  In my mind I was
> > thinking of this as just a randomizer, but I guess there's no reason to add
> > more precision if it's not too difficult.
> >
> > Thanks for your ideas.
> >
> >
> >
> > --- In CZsynth@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:
> > >
> > > Thanks for creating and sharing CZWigOut. I don't have a CZ hooked up
> > > to the computer, so I can't test the patches, but I like the ease and
> > > simplcity of the User Interface.
> > >
> > > Are you open to suggestions? (I hope so.)
> > > If so, here's just a few that immediate reactions:
> > >
> > > 1. Add a check all button
> > >  a. for all
> > >  b. for each section
> > >
> > > 2. Allow users to set allowable ranges for each parameter.
> > > 3. Allow the check states and allowable ranges to be stored in user
> > > named files [parameter profiles].
> > > 4. Allow users to load parameter profiles.
> > > 5. Have banks (8, 16) for parameter profiles so users can create a
> > > set with patches based on different parameter profiles.
> > >
> > > Please note, this is just an initial wish list, not intended to
> > > detract from the work you have done. I think its great that you did
> > > this and hope you can develope it further, perhaps with other Casio
> > > user wish lists.
> > >
> > > And if you want to do a VZWigOut, I'd be interested in that.
> > >
> > > Again, thanks for sharing this.
> > >
> > > --Steve
> > >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> 
> 
> [Non-text portions of this message have been removed]
>

Looks great! i've been trying the generator with crossover in leopard
10.5.2....but under this emulation there is no midi...:(

So how are things at the moment?

will there be a mac version? or will the linux version be x11 based?

cheers!

The Linux version will run on X11. It runs fine on my Linux system but I need to find a way to package it.  A Linux version is more likely to happen than a mac version, because I don't have a mac to build things on.

--- In CZsynth@yahoogroups.com, "bjotok" <bjorn@...> wrote:

>
> Looks great! i've been trying the generator with crossover in leopard
> 10.5.2....but under this emulation there is no midi...:(
> 
> So how are things at the moment?
> 
> will there be a mac version? or will the linux version be x11 based?
> 
> cheers!
>

A Linux version?  Great!

Why not look into Click 'n Run (CNR), originally created for Lindows
(now Linspire) but also being adopted for Ubuntu future releases. 
Plus, they will distribute open source from the 'CNR Warehouse' so
anyone with CNR access can find and install your program!

I happen to be a fan of Lindows/Linspire.  It will actually install
faster then Windows on any box I've loaded it on, it has good support,
and the CNR Warehouse has a HUGE selection of free and Pay-To-Download
software.  (Linspire is the best way to salvage older computers that
will not run current Windows versions in a usable manner that I've
found.  And so far, no matter what CPU, it will outperform the
'correct' version of Windows for the system you put it on!)

Linspire: www.linspire.com (also check out:
http://www.linspire.com/products_linspire_whatis.php?tab=compatibility )
Direct link to CNR: http://www.cnr.com/index.seam

If it's free standing, you could just create a 'tar' archive.

Larry T.

--- In CZsynth@yahoogroups.com, "Fulfil Objective" <kasploosh@...> wrote:
>
> The Linux version will run on X11. It runs fine on my Linux system
but I need to find a way to package it.  A Linux version is more
likely to happen than a mac version, because I don't have a mac to
build things on.

> 
> --- In CZsynth@yahoogroups.com, "bjotok" <bjorn@> wrote:
> >
> > Looks great! i've been trying the generator with crossover in leopard
> > 10.5.2....but under this emulation there is no midi...:(
> > 
> > So how are things at the moment?
> > 
> > will there be a mac version? or will the linux version be x11 based?
> > 
> > cheers!
> >
>

--- In CZsynth@yahoogroups.com, "Fulfil Objective" <kasploosh@...> wrote:
>
> The Linux version will run on X11. It runs fine on my Linux system
but I need to find a way to package it.  A Linux version is more
likely to happen than a mac version, because I don't have a mac to
build things on.

Did you use a widget library like wx or tk for the interface? If so, a
Mac port might not be difficult, and I'd be willing to look into
helping with it...

It's done with Python 2.5 and Tkinter 8.4.

I did it that way on purpose, so it could be cross-platform.  So the barriers to getting the other versions done are not very high at all.  Help with a mac port would be appreciated because I am kind of clueless about macs.  From the little I've read, there could be some problems with the GUI not looking native on a mac.

--- In CZsynth@yahoogroups.com, "westoncann" <wlists@...> wrote:

>
> --- In CZsynth@yahoogroups.com, "Fulfil Objective" <kasploosh@> wrote:
> >
> > The Linux version will run on X11. It runs fine on my Linux system
> but I need to find a way to package it.  A Linux version is more
> likely to happen than a mac version, because I don't have a mac to
> build things on.
> 
> Did you use a widget library like wx or tk for the interface? If so, a
> Mac port might not be difficult, and I'd be willing to look into
> helping with it...
>

--- In CZsynth@yahoogroups.com, "Fulfil Objective" <kasploosh@...> wrote:
> It's done with Python 2.5 and Tkinter 8.4.

> I did it that way on purpose, so it could be 
> cross-platform. So the barriers to getting 
> the other versions done are not very high at all. 
> Help with a mac port would be appreciated because 
> I am kind of clueless about macs. From the little 
> I've read, there could be some problems with the 
> GUI not looking native on a mac.

There appears to be a native Aqua Tcl/Tk, and if I'm
reading right, it looks like it's included with Mac
OS X 10.4 / Darwin 8.x. 

http://tcltkaqua.sourceforge.net/tiger

Looks like Tkinter is there as well, and I know
that Python has been installed on Mac OS X by default
since 10.3 at least. 

So UI may not be a big issue. If you want to send the
source or bytecode files, I'd be happy to test it.

(Unfortunately, my CZ1 is about 700 miles away right now,
so I can't test the actual results. But the UI, yes. :)