jsynthlib-devel — Mailing list for developers and users interested in improving the JSynthLib.

[Jsynthlib-devel] Re: Roland MT32 files ready for inclusion in JSynthLib source tree

[Fred J. K. <fj...@xs...>]

Bill Zwicky <wrz...@in...>  wrote:

>Fred, I can't test the driver as I don't have that keyboard.  I thought 
>you were asking for someone to check in the source code, but you don't 
>seem to have made the code available.  I can check in your MT32 source 
>if you want, though it would be better if you could do it yourself.
>  
>
I do not have permission to check it in. This was on purpose as I didn't 
plan to make more than two drivers: Roland MT-32 and Lexicon LXP5.
Testing is not required, just making sure it compiles without problems 
(the previous version had obsolete code).
The current java classes version 0.10 can be found at: 
http://electrickery.xs4all.nl/digaud/mt32/

Fred Jan

AW: [Jsynthlib-devel] Roland MT32 files ready for inclusion in JSynthLib source tree

[Joachim B. <jba...@pi...>]

Hi,

> 1 - Even though the old-style loading and saving code is=20
> still included,=20
> I made some non-trivial changes to the code that interacts=20
> with it (so=20
> that it can also load XML libraries if it needs to), and I haven't=20
> tested my changes very thoroughly.

Sounds interesting but I think we should wait for the "core" developers
to state their opinion (a week or so?).

How does the XML format look like?
Can you post an example?

> 2 - I've also changed the way sysex messages are delivered to the=20
> drivers. I think that this new design is much better and more=20
> flexible.... but, again, my *implementation* of it might have=20
> some bugs.

Can you explain the changes a bit deeper?

Or maybe post a "diff" between the old and new files?

> I fear that JSL has slipped into a development=20
> "coma".=20

Oh, that's normal in the JSynthLib project. ;-)
We need some core developers with a little bit more time. ;-)

Regards,
Joachim


> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...=20
> [mailto:jsy...@li...] Im=20
> Auftrag von Joe Emenaker
> Gesendet: Sonntag, 9. Oktober 2005 00:50
> An: jsy...@li...
> Betreff: Re: [Jsynthlib-devel] Roland MT32 files ready for=20
> inclusion in JSynthLib source tree
>=20
> Fred Jan Kraan wrote:
>=20
> > Can any of the current maintainers of the JSynthLib source=20
> tree test=20
> > the current version of the Roland MT32 driver set? It works=20
> OK on my=20
> > machine and Eclipse doesn't complain about it. The set is not yet=20
> > complete, but workable. Some user input would be useful.
>=20
> I can do it, but my current development set differs from the=20
> current CVS=20
> code in a non-trivial way. Some months back, I did a bunch of work on=20
> putting in support for saving libraries in XML format. I got=20
> it to the=20
> point where it could load either format (old serialization=20
> style or new=20
> XML format) and, when you save, it saved in both formats.
>=20
> I have a few thoughts about whether I should commit the changes:
>=20
> 1 - Even though the old-style loading and saving code is=20
> still included,=20
> I made some non-trivial changes to the code that interacts=20
> with it (so=20
> that it can also load XML libraries if it needs to), and I haven't=20
> tested my changes very thoroughly.
> 2 - I've also changed the way sysex messages are delivered to the=20
> drivers. I think that this new design is much better and more=20
> flexible.... but, again, my *implementation* of it might have=20
> some bugs.
> 3 - We haven't discussed the XML format of the libraries.=20
> Back when we=20
> last discussed it, nobody seemed to really care, so I just created an=20
> XML format that I thought was fairly flexible. I don't want=20
> to commit my=20
> code and then have some people start asking for us to change the XML=20
> format. So, if you care at all about the XML library format,=20
> speak now.
> 4 - Countering all of these reservations I've just listed,=20
> I'd like to=20
> point out that I've seen *no* activity on the JSL-CVS mailing=20
> list for=20
> months. I fear that JSL has slipped into a development=20
> "coma". In light=20
> of that, even though committing some of my changes might cause a few=20
> bugs here and there, maybe the new changes will also spur a renewed=20
> surge in development.
>=20
> Thoughts?
>=20
> - Joe
>=20
>=20

Re: [Jsynthlib-devel] Roland MT32 files ready for inclusion in JSynthLib source tree

[Bill Z. <wrz...@in...>]

p.s. I just added Ton Holsink's Yamaha UB99 too.
-Bill


Bill Zwicky wrote:

> I'm still here, believe it or not.  I used this opportunity to check 
> in someone's TCElectronicGMajor driver I had sitting around.

Re: [Jsynthlib-devel] Roland MT32 files ready for inclusion in JSynthLib source tree

[Bill Z. <wrz...@in...>]

I'm still here, believe it or not.  I used this opportunity to check in 
someone's TCElectronicGMajor driver I had sitting around.

Fred, I can't test the driver as I don't have that keyboard.  I thought 
you were asking for someone to check in the source code, but you don't 
seem to have made the code available.  I can check in your MT32 source 
if you want, though it would be better if you could do it yourself.

Joe, I agree, JSynthLib is pretty much dead, I don't think anyone would 
mind if you had your way with it.  I suggest creating a tag before you 
begin so we can roll back if we need.  In Eclipse, use Team->Tag as Version.

-Bill

Re: [Jsynthlib-devel] Roland MT32 files ready for inclusion in JSynthLib source tree

[Joe E. <jo...@em...>]

Fred Jan Kraan wrote:

> Can any of the current maintainers of the JSynthLib source tree test 
> the current version of the Roland MT32 driver set? It works OK on my 
> machine and Eclipse doesn't complain about it. The set is not yet 
> complete, but workable. Some user input would be useful.

I can do it, but my current development set differs from the current CVS 
code in a non-trivial way. Some months back, I did a bunch of work on 
putting in support for saving libraries in XML format. I got it to the 
point where it could load either format (old serialization style or new 
XML format) and, when you save, it saved in both formats.

I have a few thoughts about whether I should commit the changes:

1 - Even though the old-style loading and saving code is still included, 
I made some non-trivial changes to the code that interacts with it (so 
that it can also load XML libraries if it needs to), and I haven't 
tested my changes very thoroughly.
2 - I've also changed the way sysex messages are delivered to the 
drivers. I think that this new design is much better and more 
flexible.... but, again, my *implementation* of it might have some bugs.
3 - We haven't discussed the XML format of the libraries. Back when we 
last discussed it, nobody seemed to really care, so I just created an 
XML format that I thought was fairly flexible. I don't want to commit my 
code and then have some people start asking for us to change the XML 
format. So, if you care at all about the XML library format, speak now.
4 - Countering all of these reservations I've just listed, I'd like to 
point out that I've seen *no* activity on the JSL-CVS mailing list for 
months. I fear that JSL has slipped into a development "coma". In light 
of that, even though committing some of my changes might cause a few 
bugs here and there, maybe the new changes will also spur a renewed 
surge in development.

Thoughts?

- Joe

[Jsynthlib-devel] Roland MT32 files ready for inclusion in JSynthLib source tree

[Fred J. K. <fj...@xs...>]

Hi everyone,

Can any of the current maintainers of the JSynthLib source tree test the 
current version of the Roland MT32 driver set? It works OK on my machine 
and Eclipse doesn't complain about it. The set is not yet complete, but 
workable. Some user input would be useful.
A zip with the latest java files is at: 
http://electrickery.xs4all.nl/digaud/mt32/JSynthLib_mt32_010.zip
A screenshot is at: http://electrickery.xs4all.nl/digaud/mt32/

For now, development is stalled as I started with the Lexicon LXP5 driver.

Fred Jan

[Jsynthlib-devel] Roland MT-32 Synth Driver

[Francis B. I. <nar...@ya...>]

Hi,
 Has anyone made a JSynthLib.jar file with the latest MT-32 synth driver included?  
Thanks, Narfman

		
---------------------------------
Yahoo! for Good
 Click here to donate to the Hurricane Katrina relief effort. 

[Jsynthlib-devel] Roland MT32 driver 0.80

[Fred J. K. <fj...@xs...>]

An updated version of the Roland MT32 driver is available at: 
http://electrickery.xs4all.nl/digaud/mt32/.
This version is compatible with 0.20 and/or 0.21alpha (at least Eclipse 
3.1 is not complaining :-))

Fred Jan

[Jsynthlib-devel] Re: Sending parameter changes

[Rob T. <rob...@ya...>]

> Hi,
> don't you have the Owner' manual ? I think you can
> found it on the web.
> 
> there are two parameter change sysex : one for a
> standard parameter and another 
> for a matrix parameter (modulation matrix).
> 
> F0 10 06 06 <param> <value> F7
> 
> F0 10 06 0B <path> <source> <value> <dest> F7
> 
> --
> Denis

Thanks Denis, I was able to find one online, and am
all straight now. Appreciate it.

Rob


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Jsynthlib-devel] Editing Matrix 1000 patches

[denis q. <dqu...@fr...>]

Hi,

I've made two editors for the Matrix 1000, one for MacOS9 in Java and another 
for MacOSX in Cocoa, and sending a parameter change to the Matrix is simple, 
don't you have the Owner' manual ? I think you can found it on the web.

there are two parameter change sysex : one for a standard parameter and another 
for a matrix parameter (modulation matrix).

F0 10 06 06 <param> <value> F7

F0 10 06 0B <path> <source> <value> <dest> F7

--
Denis


> Hello,
> 
> I'm interested in writing my own editor for the Matrix
> 1000. It's looks like you've done a great job on
> yours, but I'm doing mine for practice. In addition, I
> want mine to read midi cc data, convert it to a sysex
> message, and send that to the Matrix.
> 
> What I don't understand is the basic process for
> sending parameter changes to the Matrix. Is it the
> case that for each parameter change I make, I need to:
> 
> 1) Get the current state of the patch from the Matrix
> 2) Change whatever parameter I'm adjusting.
> 3) Edit the patch with this new parameter info.
> 4) Send the new edited patch back in its entirety to
> the Matrix.
> 
> Is is not possible to simply send parameter change
> info to the matrix?
> 
> Any info on editing the Matrix 1000 would be greatly
> appreciated!
> 
> Thanks,
> Rob
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
> 
> 

[Jsynthlib-devel] Editing Matrix 1000 patches

[Rob T. <rob...@ya...>]

Hello,

I'm interested in writing my own editor for the Matrix
1000. It's looks like you've done a great job on
yours, but I'm doing mine for practice. In addition, I
want mine to read midi cc data, convert it to a sysex
message, and send that to the Matrix.

What I don't understand is the basic process for
sending parameter changes to the Matrix. Is it the
case that for each parameter change I make, I need to:

1) Get the current state of the patch from the Matrix
2) Change whatever parameter I'm adjusting.
3) Edit the patch with this new parameter info.
4) Send the new edited patch back in its entirety to
the Matrix.

Is is not possible to simply send parameter change
info to the matrix?

Any info on editing the Matrix 1000 would be greatly
appreciated!

Thanks,
Rob

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Jsynthlib-devel] Waldorf Pulse - Importing patches

[stephen c. <sc...@ho...>]

Hello All,

I have recently downloaded JSynthLib and attempted to load patches for my 
Waldorf Pulse from the Waldorf ftp site:

http://waldorf.electro-music.com/pulse/sounds/

These are a mixture of single sounds and collections of sounds, mostly in 
.mid format.

I have had great success importing one file with a collection of sounds 
(rob_papen/pulse_rp.mid) by using File -> import and changing the file type 
to 'All files'. This gives me each sound in the set, listed individually in 
the currently open Library. Each of these patches can be opened successfully 
in the Edit window. I also get a couple of entries like: 
"Device/Sysex/Probably a Waldorf Electronics Patch, Size: 12", but I am 
ignoring these as all the individual patches have loaded and that's what I 
care about.

I have also had success Importing some individual patches:
/markus_monnerjahn/da_bass.mid, rotor.mid and marilsaw.mid.

Most of the other patches on the ftp site however have given me problems:
- Attempting to load /spike/drums.mid, I get the following entry in my 
Library view:
Synth=Device
Type=Sysex
Patchname=-
Comment=Probably a Matsushita Communication Industrial Patch, Size: 836

If I then try Reassign on this entry, I get: "Oops, no driver was found 
which supports this patch! Nothing will happen"

- Attempting to load /paul_nagle/pulsepn1.mid, absolutely nothing happens 
(including in my DOS window)

I am using the files in JSynthLib-0.19-pre1.zip, as this release contains 
the driver files for the Waldord Pulse. I found that these files were not in 
the other version I downloaded: JSynthLibversion018.zip

I would imagine that these .mid files (being hosted as they were for many 
years on the official Waldorf site) are error-free so find it strange that I 
should get inconsistent behaviour between them.

Any help that anyone could give me on this would be very greatly 
appreciated.

Congratulations on what looks to be a pretty cool little app, btw.

Thanks,
Stephen.

_________________________________________________________________
Find the coolest online games @ http://xtramsn.co.nz/gaming

Re: [Jsynthlib-devel] a sense of disappointment

[denis q. <dqu...@fr...>]

I agree with dom, that's why I've started my own editors on Mac OS X with Cocoa.

I was so disappointed by the slow GUI with Java (eMac 800) that I can't use it 
when working on a music, too slow to start, too slow to switch between panels etc.

I've made two editors with Cocoa, one for the Matrix 1000 (quite older than the 
one on Apple site...) and a Micro Q one. I've started a FS1R (again !).

A simple thing that I have made is to save a patch as a file, not in a bank so I 
can make my own sort with simple folders.

To compare Cocoa (ObjC) with Java I have found an editor for the micro Q in 
Java, well, it is VERY slow to start and VERY slow to tweek, so I've started my own.

-- 
Denis

> hi all
> 
> you guys are all working so hard on this, but as a user i have to say  
> that synthlib has so far been hard to use and understand.  maybe mac  os 
> x java support is still pretty poor, but the whole thing is  sluggish 
> and uncooperative.  however, i use a line 6 variax guitar  and i'm 
> pretty sure the 'workbench' software is java, and that works  very well.
> 
> if you check out apple.com > mac os x > downloads > audio, you'll see  a 
> new matrix 1000 editor.  it's max/msp; it looks good, launches  quickly 
> and is easy to use.  in fact i bought a second hand matrix  1000 by 
> coincidence almost the same day.  if jsynthlib were as user- friendly as 
> that, i'd continue to follow its development.
> 
> i have never before been offered the chance to try motu software on a  
> 30 day basis, but the UK distributor is sending me a copy of unisyn.   
> it seems to do what synthlib promised.  for 200 GBP [around 300USD].
> 
> only once did i ever sit down and make a new patch for a synth with  
> synthlib, for my tx81z.  it's still on the synth [appropriately  titled 
> 'moody f**k'], but that's my only success.
> 
> i don't like to sound negative, but synthlib looks as if it will only  
> ever be useful to synthists who are also pretty competent  programmers.  
> take it from someone who looks from the musician's  viewpoint [i'm 
> avoiding calling myself a musician, that would be  grandiose];
> 
> synthlib is just too unfriendly.
> 
> if you want to make it a popular, open source, easy to use editor,  you 
> need to radically rewrite it.  i'm afraid my only contributions  to this 
> project have been criticism, from the muso's viewpoint, but  surely 
> that's the target 'market'?
> 
> i'll keep checking it out from time to time, but for the time being,  i 
> give up.
> 
> sorry
> 
> dom
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
> 
> 

Re: AW: [Jsynthlib-devel] JSynthLib & Roland XV-5050

[Mika S. <mik...@wi...>]

Hello,

  Managed to get the XV-5050 to work with ported XV-5080 code after I
changed to use the Tritonus Audio Lib  instead of LinuxCharDev.jar. Now
slowly trying to create the patch editor with Eclipse & VA to XV-5050,
seems to be a bit huge task and shall tease the forum with stupid
questions time to time.

  Thanks for answer !

	-Mika
> Hi,
> 
> do you have the SysEx documentation of both the XV-5050
> and the XV-5080?
> 
> I guess they differ a bit, at least the SysEx identification
> string is different. That means the XV-5050 doesn't recognize
> that it should respond.
> 
> E.g. the XV-5080 could be identified by 
> 05 AA
> and the XV-5050 by
> 05 AB
> so you have to change the "05 AA" to "05 AB".
> (That's just an example, the values are not correct!)
> 
> Hope this helps.
> 
> Regards,
> Joachim Backhaus
> 

AW: [Jsynthlib-devel] a sense of disappointment

[Joachim B. <jba...@pi...>]

Hi,

> it seems to do what synthlib promised.  for 200 GBP [around 300USD].

Ehm, where did JSynthLib promised to do something and what?

> synthlib is just too unfriendly.

OK, what would you specifically change?

If you have an idea of such a better Graphical-User-Interface
please tell us how it should look like or draw it.

Just saying it is user-unfriendly is not much helpful!

Regards,
Joachim Backhaus

PS: I think after a learning-curve it is easy to use! ;-)
(Depends also on the synth driver, of course)


> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...
> [mailto:jsy...@li...]Im Auftrag von dom
> Gesendet: Dienstag, 16. August 2005 12:29
> An: jsy...@li...
> Betreff: [Jsynthlib-devel] a sense of disappointment
>=20
>=20
> hi all
>=20
> you guys are all working so hard on this, but as a user i=20
> have to say =20
> that synthlib has so far been hard to use and understand.  maybe mac =20
> os x java support is still pretty poor, but the whole thing is =20
> sluggish and uncooperative.  however, i use a line 6 variax guitar =20
> and i'm pretty sure the 'workbench' software is java, and that works =20
> very well.
>=20
> if you check out apple.com > mac os x > downloads > audio,=20
> you'll see =20
> a new matrix 1000 editor.  it's max/msp; it looks good, launches =20
> quickly and is easy to use.  in fact i bought a second hand matrix =20
> 1000 by coincidence almost the same day.  if jsynthlib were as user-=20
> friendly as that, i'd continue to follow its development.
>=20
> i have never before been offered the chance to try motu=20
> software on a =20
> 30 day basis, but the UK distributor is sending me a copy of=20
> unisyn.  =20
> it seems to do what synthlib promised.  for 200 GBP [around 300USD].
>=20
> only once did i ever sit down and make a new patch for a synth with =20
> synthlib, for my tx81z.  it's still on the synth [appropriately =20
> titled 'moody f**k'], but that's my only success.
>=20
> i don't like to sound negative, but synthlib looks as if it=20
> will only =20
> ever be useful to synthists who are also pretty competent =20
> programmers.  take it from someone who looks from the musician's =20
> viewpoint [i'm avoiding calling myself a musician, that would be =20
> grandiose];
>=20
> synthlib is just too unfriendly.
>=20
> if you want to make it a popular, open source, easy to use editor, =20
> you need to radically rewrite it.  i'm afraid my only contributions =20
> to this project have been criticism, from the muso's viewpoint, but =20
> surely that's the target 'market'?
>=20
> i'll keep checking it out from time to time, but for the time being, =20
> i give up.
>=20
> sorry
>=20
> dom
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development=20
> Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *=20
> Testing & QA
> Security * Process Improvement & Measurement *=20
http://www.sqe.com/bsce5sf
_______________________________________________
Jsynthlib-devel mailing list
Jsy...@li...
https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

[Jsynthlib-devel] a sense of disappointment

[dom <do...@ma...>]

hi all

you guys are all working so hard on this, but as a user i have to say  
that synthlib has so far been hard to use and understand.  maybe mac  
os x java support is still pretty poor, but the whole thing is  
sluggish and uncooperative.  however, i use a line 6 variax guitar  
and i'm pretty sure the 'workbench' software is java, and that works  
very well.

if you check out apple.com > mac os x > downloads > audio, you'll see  
a new matrix 1000 editor.  it's max/msp; it looks good, launches  
quickly and is easy to use.  in fact i bought a second hand matrix  
1000 by coincidence almost the same day.  if jsynthlib were as user- 
friendly as that, i'd continue to follow its development.

i have never before been offered the chance to try motu software on a  
30 day basis, but the UK distributor is sending me a copy of unisyn.   
it seems to do what synthlib promised.  for 200 GBP [around 300USD].

only once did i ever sit down and make a new patch for a synth with  
synthlib, for my tx81z.  it's still on the synth [appropriately  
titled 'moody f**k'], but that's my only success.

i don't like to sound negative, but synthlib looks as if it will only  
ever be useful to synthists who are also pretty competent  
programmers.  take it from someone who looks from the musician's  
viewpoint [i'm avoiding calling myself a musician, that would be  
grandiose];

synthlib is just too unfriendly.

if you want to make it a popular, open source, easy to use editor,  
you need to radically rewrite it.  i'm afraid my only contributions  
to this project have been criticism, from the muso's viewpoint, but  
surely that's the target 'market'?

i'll keep checking it out from time to time, but for the time being,  
i give up.

sorry

dom

AW: [Jsynthlib-devel] JSynthLib & Roland XV-5050

[Joachim B. <jba...@pi...>]

Hi,

do you have the SysEx documentation of both the XV-5050
and the XV-5080?

I guess they differ a bit, at least the SysEx identification
string is different. That means the XV-5050 doesn't recognize
that it should respond.

E.g. the XV-5080 could be identified by=20
05 AA
and the XV-5050 by
05 AB
so you have to change the "05 AA" to "05 AB".
(That's just an example, the values are not correct!)

Hope this helps.

Regards,
Joachim Backhaus

> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...
> [mailto:jsy...@li...]Im=20
> Auftrag von Mika
> Saari
> Gesendet: Mittwoch, 20. Juli 2005 19:48
> An: jsy...@li...
> Betreff: [Jsynthlib-devel] JSynthLib & Roland XV-5050
>=20
>=20
> Hello,
>=20
>   I checked that Roland XV-5080 and XV-5050 midi commands seems to be
> pretty same kind. So I took the 5080 synthdriver, replaced XV5080 with
> XV-5050, compiled with make, java core/DeviceListWriter, added new
> XV-5050 device (also added some System.out.prinln("Debug"),=20
> so I can see
> that the driver actually is added to the software), and last=20
> I tried if
> I could get the patch listing. But nothing happens, what I=20
> mean is that
> the Roland XV-5050 doesn't show any data transfer between machine (no
> led is indicating that communication is done). I tested that "amidi -p
> hw:1,0 -S <something here>" sends the command and Roland=20
> indicates with
> led that command is received (even it would be nothing clever). Also I
> can use the Roland through Rosegarden.=20
>=20
>   Possible problems: 1) Totally wrong channel & ID in Window-
> >Properties->Midi. What kind of numbers should I have there since the
> Roland is the second midi device (hw:1,0) ? 2) I haven't installed the
> MIDI jar correctly, though if I remove the LinuxCharDev.jar, I can not
> change any MIDI parameters anymore.
>=20
>   Ah yes and I tested this with own account and root account.=20
>=20
>   Anything I could try / test ?
>=20
>   Humble thanks for everybody,
>    -Mika
>=20
>  =20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>=20

[Jsynthlib-devel] Resizable knobs in KnobWidget and KnobLookupWidget

[Joachim B. <jba...@pi...>]

Hi,

yesterday I commited my changes to KnobWidget and KnobLookupWidget.

I added some constructors to be able to create a knob with
any size you need/want and I added some javadoc comments.

I hope I didn't break anything. ;-)

Would it make sense to do the same with the slider widgets?

Regards,
Joachim Backhaus

AW: [Jsynthlib-devel] Re: novation k-station / akai sg01v

[Joachim B. <jba...@pi...>]

Hi,

> As a newcomer, would I be better tackling a simple synth from=20
> scratch, or a more complex one, but  where there was a very=20
> similar driver already written to use as a starting point? =20
> Some helpful advice from the old-timers would be welcome.

I think the simple synth from scratch is better.

You can also write support for a complex synth at first
as it would be a simple synth by leaving out more complex
parameters. If it works, you can add them later.

Usually it is not important for the librarian support
whether the synth is complex or not.
That will basically affect the editor support.

Regards,
Joachim Backhaus


> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...
> [mailto:jsy...@li...]Im Auftrag von
> nx...@li...
> Gesendet: Donnerstag, 4. August 2005 12:53
> An: jsy...@li...
> Betreff: [Jsynthlib-devel] Re: novation k-station / akai sg01v
>=20
>=20
> Hello All
>=20
> I am new to this project.  I am a software developer in my=20
> day job and like to muck about with synths after hours.  I=20
> don't have a lot of time to devote to it, but I was thinking=20
> of getting involved and helping with a driver or two.  The=20
> synth I was thinking of starting with was the akai SG01v as=20
> it is not too complex.  Has anyone else done anything for=20
> this or similar?
>=20
> I also have a novation a-station (currently stored away).  I=20
> haven't used it recently, but I could get it out and make an=20
> attempt.  I imagine that from a midi point of view there=20
> would be virtually no difference from the k-station.  Maybe=20
> there would also be common ground with the nova which is=20
> already supported.  Would that be a good starting point?
>=20
> My final question is has anyone written a driver for the korg=20
> x5d?  I imagine the X3 driver would be just about good=20
> enough, maybe with a few tweaks.
>=20
> As a newcomer, would I be better tackling a simple synth from=20
> scratch, or a more complex one, but  where there was a very=20
> similar driver already written to use as a starting point? =20
> Some helpful advice from the old-timers would be welcome.
>=20
> Nicolas
>=20
>=20
> >From: Jonny <jo...@te...>
> >Subject: [Jsynthlib-devel] Novation K-station support
> >
> >Hi, I just saw this project while browsing the net for=20
> patches. The other day I was looking for >a patch editor just=20
> like this! One problem - synth support. Would anybody be=20
> able/willing to add >support for a Novation K-Station? If=20
> somebody can start the ball rolling I'd be more than happy=20
> >to help test the software for them.
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development=20
> Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *=20
> Testing & QA
> Security * Process Improvement & Measurement *=20
http://www.sqe.com/bsce5sf
_______________________________________________
Jsynthlib-devel mailing list
Jsy...@li...
https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

[Jsynthlib-devel] Re: MT32

[<nx...@li...>]

Thank you very much for sending me the code Fred.  My time is also a bit limited, but I will do some testing over the next couple of weeks and let you know how I get on.  My interest in seeing how the MT32 driver works is, like you, because it is a reasonably simple synth and doesn't retain settings so mistakes can be fixed by simply switching it off.  I have some other gear that I would like to move on to once I have got the hang of JSynthLib.

Cheers,
Nicolas



  
>
>The attached version is more op to date but untested. Currently my time 
>is quite limited, so little work is done on JSynthLib.
>Most problems were solved, but probably not all. If you want to take it 
>over, it is ok with me. The MT32 editor was merely a proof of concept 
>for me (and it worked :-) ).
>
>Alas is my site very unreliable (provider fault, not mine).
>
>Greetings & success,
>
>Fred Jan Kraan

[Jsynthlib-devel] Re: Roland MT32

[Fred J. K. <fj...@xs...>]

Nicolas wrote:

>Hello
>
>If Fred Jan Kraan (or Hiroo Hayashi or anyone else who has a copy) is reading this, would it be possible for me to have a copy of the latest MT32 driver code.  The latest in CVS is not 
>
A copy of the latest version of the driver is sent.

Fred Jan

[Jsynthlib-devel] Roland MT32

[<nx...@li...>]

Hello

If Fred Jan Kraan (or Hiroo Hayashi or anyone else who has a copy) is reading this, would it be possible for me to have a copy of the latest MT32 driver code.  The latest in CVS is not up-to-date because of compilation issues and Fred's web page is not responding for me.  I would be happy to help with sorting out the deprecated stuff if that is what is holding it up.  Email me off list if you like.

Thanks,
Nicolas

[Jsynthlib-devel] Re: novation k-station / akai sg01v

[<nx...@li...>]

Hello All

I am new to this project.  I am a software developer in my day job and like to muck about with synths after hours.  I don't have a lot of time to devote to it, but I was thinking of getting involved and helping with a driver or two.  The synth I was thinking of starting with was the akai SG01v as it is not too complex.  Has anyone else done anything for this or similar?

I also have a novation a-station (currently stored away).  I haven't used it recently, but I could get it out and make an attempt.  I imagine that from a midi point of view there would be virtually no difference from the k-station.  Maybe there would also be common ground with the nova which is already supported.  Would that be a good starting point?

My final question is has anyone written a driver for the korg x5d?  I imagine the X3 driver would be just about good enough, maybe with a few tweaks.

As a newcomer, would I be better tackling a simple synth from scratch, or a more complex one, but  where there was a very similar driver already written to use as a starting point?  Some helpful advice from the old-timers would be welcome.

Nicolas


>From: Jonny <jo...@te...>
>Subject: [Jsynthlib-devel] Novation K-station support
>
>Hi, I just saw this project while browsing the net for patches. The other day I was looking for >a patch editor just like this! One problem - synth support. Would anybody be able/willing to add >support for a Novation K-Station? If somebody can start the ball rolling I'd be more than happy >to help test the software for them.

[Jsynthlib-devel] Novation K-station support

[Jonny <jo...@te...>]

Hi, I just saw this project while browsing the net for patches. The other day I was looking for a patch editor just like this! One problem - synth support. Would anybody be able/willing to add support for a Novation K-Station? If somebody can start the ball rolling I'd be more than happy to help test the software for them.

[Jsynthlib-devel] JSynthLib & Roland XV-5050

[Mika S. <mik...@wi...>]

Hello,

  I checked that Roland XV-5080 and XV-5050 midi commands seems to be
pretty same kind. So I took the 5080 synthdriver, replaced XV5080 with
XV-5050, compiled with make, java core/DeviceListWriter, added new
XV-5050 device (also added some System.out.prinln("Debug"), so I can see
that the driver actually is added to the software), and last I tried if
I could get the patch listing. But nothing happens, what I mean is that
the Roland XV-5050 doesn't show any data transfer between machine (no
led is indicating that communication is done). I tested that "amidi -p
hw:1,0 -S <something here>" sends the command and Roland indicates with
led that command is received (even it would be nothing clever). Also I
can use the Roland through Rosegarden. 

  Possible problems: 1) Totally wrong channel & ID in Window-
>Properties->Midi. What kind of numbers should I have there since the
Roland is the second midi device (hw:1,0) ? 2) I haven't installed the
MIDI jar correctly, though if I remove the LinuxCharDev.jar, I can not
change any MIDI parameters anymore.

  Ah yes and I tested this with own account and root account. 

  Anything I could try / test ?

  Humble thanks for everybody,
   -Mika