[Jsynthlib-devel] release 1.0 promotion

Firstly, excellent work getting the project into a good shape and getting a release out there. Do we need to announce the release anywhere? I've updated freshmeat.net with the release details (if anyone still uses that website these days). Any other ways to let people know that jsynthlib is open f

Re: [Jsynthlib-devel] Change project structure

There is some stuff in the old user guide here: http://sourceforge.net/p/jsynthlib/wiki/User%20Guide/ On 22/10/2013 09:47, Packe wrote: > terrorise.me.uk> > To: Frankie Fisher , > "chrisware...@chriswareham.demon.co.uk" > > X-Mailer: Apple Mail (2.1510) > &g

Re: [Jsynthlib-devel] Change project structure

We've got a release that is kind of ready to go that has multiple new synths since the last official release which was about 5 years ago. There was pretty much 1 reported issue that could block a release, which was that JSL hasn't worked on some versions of macs. There recently were some patches t

Re: [Jsynthlib-devel] Problem with DeviceListWriter

I can run it from ant update-drivers with no problem: $ ant update-drivers Buildfile: /home/frankster/jsynthlib/trunk/JSynthLib/build.xml init: build-code: [javac] Compiling 2 source files to /home/frankster/jsynthlib/trunk/JSynthLib/build/bin [javac] Note: /home/frankster/jsynthlib/trun

Re: [Jsynthlib-devel] Re : Re: OS X Midi Provider

#x27;t work on OSX at this > time. > It was direct calls to the Java OSX MIDI API. > I don't know if the code still exists. > As I think Java is no more maintained by Apple, I think my old code is > useless anyway. > > -- > Denis > > - Mail d'origine

Re: [Jsynthlib-devel] OS X Midi Provider

I think this would be very useful - I'm pretty sure that noone has done this already. On 19/03/2013 18:43, Packe wrote: > Hi, > > As discussed with Frankie in the support forum the OS X Midi Provider > (CAProvider) doesn't work on later versions of Mac OS X. > > I have already implemented a JNI

[Jsynthlib-devel] copied across pages

I've copied across the main pages from the old jsynthlib.org website - the user guide, programmer info, supported synth list and the contribute page. They need a bit of tidying up and some of the info looks a bit out of date so I've only linked the synth list from the main page of the wiki. --

[Jsynthlib-devel] screenshots on wiki

The front page of the wiki has a link to [[project_screenshots]]. I have got the old screenshots from jsynthlib.org although I can't see how to add them to the wiki - possibly its a project access thing? Anyway I have attached them to this email so can someone put them onto the project? And I guess

Re: [Jsynthlib-devel] Upgrade is done

Cool. Can you make the sf project page link to the wiki directly? It currently just links to the source forge project page (i.e. back to itself). See attached image. frankie On 16/02/2013 19:37, Joachim wrote: > The upgrade is done and the Wiki is now accessible at: > https://sourceforge.net/p/

Re: [Jsynthlib-devel] Upgrading the Sourceforge project to Allura?

Probably worth it as the basic commands are the same for svn and git so the learning curve isn't too bad On 15/02/2013 00:07, David Griffith wrote: > > Let's switch to git then. > > On Thu, 14 Feb 2013, Frankie Fisher wrote: > >> One other thought - do you think

Re: [Jsynthlib-devel] Upgrading the Sourceforge project to Allura?

One other thought - do you think "Trac will no longer integrate with svn" will cause any problems? On 14/02/2013 20:08, Joachim wrote: > No other thoughts on the upgrade. > If no one else cares I tend to just make it. > > Joachiim > > Am 01.02.2013 00:00, schrieb Frank

Re: [Jsynthlib-devel] Upgrading the Sourceforge project to Allura?

The only thing that sounds worrying is the loss of ticket stats. Does this potentially mean a loss of bug reports/patches? Or is it much more mundane, like a loss of "bug reports per month"? On 31/01/2013 22:34, Joachim wrote: > Hi there, > > I totally missed this but as a project admin I have the

Re: [Jsynthlib-devel] Using JSynthLib for my Kawai K4

Sounds like a good idea to me! On 25/01/2013 19:53, "Andreas Rückert" wrote: > Hi! > > After some problems, I finally managed to subscribe to the list > (sf wouldn't let me subscribe with my old account, so I had to > create a new one). > > I'm a software dev from Germany and use JSynthLib to crea

[Jsynthlib-devel] contacting brian klock re website

Hoping to discuss getting some access to the jsynthlib.org website arranged, I tried to send an email to bkl...@users.sourceforge.net, however after a few days I got a bounce back with the following message: : host mx.sourceforge.net[216.34.181.68] said: 451 Could not complete recipient verify

Re: [Jsynthlib-devel] test refactor branch

On 29/12/2011 11:29, Martin Tarenskeen wrote: > > > On Thu, 29 Dec 2011, Frankie Fisher wrote: > >> However I don't have any of the other synths so its not really >> possible for me to do this for any of the other devices as its >> impossible for me to test i

Re: [Jsynthlib-devel] test refactor branch

On 29/12/2011 09:37, Martin Tarenskeen wrote: > I am not completely happy with the TX81Z and DX100 drivers anyway. In the > (I hope not too far) future I hope to be able to develop drivers > that should work on the complete TX81Z "compatible" 4-op FM synths: > > A driver to support: DX21/27/100,

Re: [Jsynthlib-devel] Looking for Kawai K1 advice or pointers

On 07/12/2011 22:21, John McCabe wrote: > > 2) would you treat the 'pair' of banks as one, in which case, you'd need > to send and receive two separate sysex messages to download the data, or > treat them as separate bank? > It sounds like 2 banks might be the more convenient way to treat it, a

Re: [Jsynthlib-devel] Changes I'd like to commit.

just whack it in On 04/12/2011 17:02, Chris Wareham wrote: > Chris Wareham said on 04/12/11 13:15: >> Hi folks, >> >> I'd like to commit the following changes if that's OK. >> >> Regards, >> >> Chris >> > > I've also reworked the byte array manipulation methods from the Utility > class to use Syste

Re: [Jsynthlib-devel] Code submissions and suggested changes

On 01/12/2011 19:39, Chris Wareham wrote: > > In the meantime I'll take a look at Joe Emanaker's re-factoring branch, > and continue familiarising myself with the code base. Is there a need > to support versions of Java prior to 1.5, or can I assume that Generics > support is a pre-requisite for ru

Re: [Jsynthlib-devel] Code submissions and suggested changes

These changes sound fantastic. I'll give you a little idea of what's going on at the moment. We're currently have a release candidate available for release 0.21 although there are still some administrative issues to do with getting the website updated, and possibly a MacOs bug that may need resolv

Re: [Jsynthlib-devel] Mac problem posted in the UCapps forum

On 23/11/2011 22:08, Joachim wrote: > Hi there, > > does anybody here have a Mac OS? > > In the UCapps forum someone posted a problem with using a Mac and JSynthLib: > http://midibox.org/forums/topic/14981-jsynthlib-update/page__view__findpost__p__143389 > > Would be nice if we could help him. > >

Re: [Jsynthlib-devel] Inquiry ID Requests

I actually did a little bit of work tidying a few drivers up last month because a number of them claimed ownership of pretty much any device id that they were passed. Anyone know how other software like this such as sounddiver etc deal with detecting synths that don't support the standard midi enq

Re: [Jsynthlib-devel] Getting started...

hlib-devel] Getting started... >>> >>> Frankie >>> >>> Thanks for that. >>> >>> I've just done a checkout from SourceForge SVN in to Eclipse and managed >>> to get it to build. The only thing that seems odd is that the project

Re: [Jsynthlib-devel] Getting started...

Hiya, First you should look at the programmer's guide http://jsynthlib.org/programming.html or in fact the latest version from svn: http://jsynthlib.svn.sourceforge.net/viewvc/jsynthlib/trunk/JSynthLib/doc/programming.html Then there is also some good information here on a wiki that a guy cal

Re: [Jsynthlib-devel] 0.21 ready for testing

n the website which is hosted by Brian Klock? > That one can only be changed by Brian and I think he doesn't > monitor this list. > > Didn't someone write him an email in regard to the expiration > of jsynthlib.org? > Has there been any response? > > Joachim > &

Re: [Jsynthlib-devel] 0.21 ready for testing

> Joachim > > Am 08.11.2011 10:07, schrieb Frankie Fisher: >> On 09/10/2011 08:44, William Zwicky wrote: >>> And if one of you has the *ability* to publish this, please speak up, cuz I >>> don't. >>> >> Are we still without anybody who has access

Re: [Jsynthlib-devel] 0.21 ready for testing

On 09/10/2011 08:44, William Zwicky wrote: > > And if one of you has the *ability* to publish this, please speak up, cuz I > don't. > Are we still without anybody who has access to publish the file? frankie -- RSA(R) Con

Re: [Jsynthlib-devel] patch for YamahaCS2x and RolandSPD11

ky > > > On Mon, Oct 10, 2011 at 1:57 AM, Frankie Fisher < > jsynthlib@terrorise.me.uk> wrote: > >> Bill, do I have to do something to update the 0.21 tag when I put this >> patch in? What command do I use? >> > -

Re: [Jsynthlib-devel] patch for YamahaCS2x and RolandSPD11

On 09/10/2011 10:50, Peter Geirnaert wrote: > Hi > > I've uploaded a > patchto > SourceForge with support for YamahaCS2x and RolandSPD11. > I think InitPerf.syx is missing from the patch because its a binary file.

Re: [Jsynthlib-devel] patch for YamahaCS2x and RolandSPD11

Hi, Thanks for the patch; I'll have a look at it tonight. As we're doing release candidates now, we would ideally only takes patches to fix bugs, but its only been since yesterday and its probably better to get the synth support in because who knows when the next release will be ;) Bill, do I have

Re: [Jsynthlib-devel] best way to discard some sysex?

On 27/09/2011 00:00, Frankie Fisher wrote: > I am improving the TX81z driver so that you can request individual > patches, banks and performances. This is using the midi remote control > button presses to simulate the user selecting the patch/performance. > > To get a performance o

Re: [Jsynthlib-devel] best way to discard some sysex?

On 27/09/2011 00:36, Martin Tarenskeen wrote: > > > On Tue, 27 Sep 2011, Frankie Fisher wrote: > >> I am improving the TX81z driver so that you can request individual >> patches, banks and performances. This is using the midi remote control >> button presses to s

[Jsynthlib-devel] best way to discard some sysex?

I am improving the TX81z driver so that you can request individual patches, banks and performances. This is using the midi remote control button presses to simulate the user selecting the patch/performance. To get a performance out, I think its unavoidable that some sysex that I don't need gets tr

[Jsynthlib-devel] sysex sending delays

I have just put in a patch that slightly changes the way delays work in sysex. The old behaviour is that no delay is added when sending a sysex from a driver, unless there is a max buffer size set (either in the driver or in global prefs) which causes the message to be split up into fragments as it

Re: [Jsynthlib-devel] 10th anniversary

On 23/09/2011 19:56, William Zwicky wrote: > I'd also like to remove synths from the Preferences page. You should pick > synth(s) when creating libraries and scenes. > how does this fit in with the auto-scan process - do you anticipate doing an autoscan every time you create a library? This doesn'

Re: [Jsynthlib-devel] 10th anniversary

On 23/09/2011 18:57, Joachim wrote: > Hi, > >> Also I noticed this guy Thorsten who has been updating jsynthlib a bit >> over here: http://midibox.org/forums/topic/14981-jsynthlib-update/ >> I'd like to look at getting his work into 0.21 so I'm going to try and >> contact him. > it could be that he

Re: [Jsynthlib-devel] 10th anniversary

On 23/09/2011 17:04, Joe Emenaker wrote: > On 9/23/2011 6:21 AM, frankster wrote: >> From the docs (which have fallen off the internet in the last couple >> of days!): "The advantage of a scene is that it contains the locations >> for the patches in the synth's memories in addition to the patches

Re: [Jsynthlib-devel] 10th anniversary

On 23/09/2011 09:05, Roger Westerlund wrote: > 2011/9/23 William Zwicky : >> On Thu, Sep 22, 2011 at 11:34 PM, Roger Westerlund < >> rog...@users.sourceforge.net> wrote: >> >>> Me myself is very picky when it comes to user interface ... for now I >>> just have to do the talk. >>> >> Well then, how

Re: [Jsynthlib-devel] two ideas for jsynthlib

On 19/09/2011 21:56, Frankie Fisher wrote: > On 19/09/2011 21:34, Maciej Łoziński wrote: >> Hi >> >> I have two ideas that could improve jsynthlib. >> >> One, easier to do is implementing randomization of patches. > I thought there already was a randomise o

Re: [Jsynthlib-devel] no details available

On 20/09/2011 02:41, Joe Emenaker wrote: > On 9/19/2011 6:11 PM, Frankie Fisher wrote: >> Does anybody else see "no details available" in the input midi devices? > Yes, and it bugs me. > >> Currently the device name that is displayed to the user is constructed >

Re: [Jsynthlib-devel] [Jsynthlib-cvs] SF.net SVN: jsynthlib:[1158] trunk/JSynthLib/core

On 20/09/2011 20:42, William Zwicky wrote: > On Tue, Sep 20, 2011 at 10:45 AM, Frankie Fisher < > jsynthlib@terrorise.me.uk> wrote: > >> .. constant re-querying is a pain in the arse .. >> > How about this: jsl only saves a list of which ports were DISabled, by &

Re: [Jsynthlib-devel] [Jsynthlib-cvs] SF.net SVN: jsynthlib:[1158] trunk/JSynthLib/core

On 20/09/2011 15:13, Joe Emenaker wrote: > > I think the toughest part is deciding how JSL should respond when *some* > of the selected interfaces go missing. Suppose I have two USB MIDI > interfaces, and I have some drivers using ports on each one. Then, I > remove one of the MIDI interfaces an

Re: [Jsynthlib-devel] [Jsynthlib-cvs] SF.net SVN: jsynthlib:[1158] trunk/JSynthLib/core

On 20/09/2011 02:40, Joe Emenaker wrote: > While you're in that zone, consider this. In the refactor, the new MIDI > code is going to be able to listen on *all* available input ports at > once, so the current MIDI configuration panel (where you select a single > input and single output port) is

[Jsynthlib-devel] no details available

Does anybody else see "no details available" in the input midi devices? Currently the device name that is displayed to the user is constructed by concatenating DESCRIPTION and NAME, but I wonder if it should instead be based on VENDOR and NAME which should stop this "No details available"? fran

Re: [Jsynthlib-devel] two ideas for jsynthlib

On 19/09/2011 21:34, Maciej Łoziński wrote: > Hi > > I have two ideas that could improve jsynthlib. > > One, easier to do is implementing randomization of patches. It would be > not much work, as we already have all parameter ranges for patches where > there are PatchEditors present. There could

Re: [Jsynthlib-devel] default look and feel

On 18/09/2011 21:06, William Zwicky wrote: > On Sun, Sep 18, 2011 at 9:48 AM, Joe Emenaker wrote: > >> However, supporting Nimbus doesn't mean *requiring* 1.6. We could just >> have JSL check to see what version of Java it's running under. >> >> Personally, my preference for the behavior would be:

Re: [Jsynthlib-devel] default look and feel

well I anticipate that when it creates a configuration for the first time, it checks if nimbus exists and if so sets it to that. otherwise it would default to metal as current. so no, it has no version implications (apart from looking better on 1.6+) frankie On 18/09/2011 16:32, Joachim wrote: >

Re: [Jsynthlib-devel] synth support that's not made it into SVN!!

On 01/09/2011 18:26, F.J. Kraan wrote: > Hi, > > At http://electrickery.xs4all.nl/digaud/mt32/ is a more recent version > of the Roland MT-32 driver. Still incomplete. There is also a > rudimentary driver for the Lexicon LXP5. It shows the settings of a > patch, which is not possible on the LXP5

Re: [Jsynthlib-devel] Compiling for linux

On 12/09/2011 19:49, Joe Emenaker wrote: > Does anybody build JSL for Linux? > > I'm getting some build errors when I try to build the stuff in > midiprovider.LinuxCharDev. i've not been building linuxchardev. I don't think you need it anyway on JDK >= 1.5 frankie -

Re: [Jsynthlib-devel] TC Electronic M350

On 11/09/2011 01:42, Frankie Fisher wrote: > So we've now got a working single patch librarian and editor for the > M350. There isn't any proper documentation in the manual, so I had to > work the SysEx out myself. (For future reference I've documented the > format at &

Re: [Jsynthlib-devel] Two refactoring questions

On 12/09/2011 14:01, Roger Westerlund wrote: > > I am not sure that Maven is the way to go for JSynthLib. I have been > using Maven in my work for the last couple of years and I have seen > Maven being bent over backwards to build a system. It is not a pretty > sight. I think nothing beats Maven wh

[Jsynthlib-devel] TC Electronic M350

So we've now got a working single patch librarian and editor for the M350. There isn't any proper documentation in the manual, so I had to work the SysEx out myself. (For future reference I've documented the format at http://francisfisher.me.uk/problem/2011/deciphering-tc-electronic-m350-sysex-form