[Jsynthlib-devel] End of jSynthLib

2014-12-16 Thread Packe
Hi, I’m writing to you to inform you that I have (finally) discovered the Ctrlr project. This project pretty much meets the needs I have for a sysex editor/librarian. The only thing that is currently missing are the drivers. I have therefore decided to abandon the JSL development and instead mo

[Jsynthlib-devel] Another major change in JSL...

2014-10-23 Thread Packe
Hi, I’ve finally had enough of Eclipse’s lousy SVN plugins so I moved the code from SVN to Git on Sourceforge. You can now access the code here instead: http://sourceforge.net/p/jsynthlib/jsynthlib I’ve kept the old repo as a read-only reference. I didn’t move any branches as my impression is

[Jsynthlib-devel] Major code delivery to trunk

2014-10-10 Thread Packe
Hi! Today I have delivered a lot of code to trunk. This is the initial step towards XML drivers. I have ported some drivers (those where I own the synthesizer..) as a proof of concept. There is still a lot of work to do even for these drivers though. The design is made to be backwards compati

Re: [Jsynthlib-devel] how to package from svn sources? (fwd)

2014-03-03 Thread Packe
Hi, I have added a discussion forum on the project page on Sourceforge. Please create a new post there regarding this issue. Br /Pascal > 3 mar 2014 kl. 18:15 skrev Martin Tarenskeen : > > > I am not quite sure what the right place is to report the errormessages and > failure I get after tr

Re: [Jsynthlib-devel] how to package from svn sources?

2014-03-02 Thread Packe
I haven't tested this on Linux. Please post the stacktraces in a bug/support request on sourceforge. If you are running maven you should run Mvn clean xmlbeans:xmlbeans package It will run some tests that probably will fail... /Pascal > 2 mar 2014 kl. 19:56 skrev Martin Tarenskeen : > >

Re: [Jsynthlib-devel] [yamahablackboxes] JSynthLib 1.0 in Windows (fwd)

2014-03-02 Thread Packe
Hi, Please ask the user to submit a bug/support request on sourceforge. Br /Pascal > 2 mar 2014 kl. 10:41 skrev Martin Tarenskeen : > > > Don't know about the details, > I'm just forwarding a message: > > -- Forwarded message -- > Date: 02 Mar 2014 01:02:16 -0800 > From: paul

Re: [Jsynthlib-devel] release 1.0 promotion

2014-02-28 Thread Packe
Hi Frankie, Great idea! I thought I should have sent out an email on the users' list but I forgot... I can do that tonight. Besides that, as I haven't been involved with the project earlier, I have no idea where to publish news except on the sourceforge site. Any help/suggestions are highly

Re: [Jsynthlib-devel] Change project structure

2014-01-03 Thread Packe
no idea what that branch is for. > > Regards, > Joachim > > Am 03.01.2014 22:50, schrieb Packe: > >> Probably yes but I saw that some other branches also had some numbers in >> their name so I thought it wasn't that bad.. >> >> Is it possible to r

Re: [Jsynthlib-devel] Change project structure

2014-01-03 Thread Packe
t also be that I'm currently pretty exhausted. > > Joachim > > Am 03.01.2014 21:55, schrieb Packe: >> Ah crap.. >> >> That's branches that I've created. This is where I was a bit confused with >> SVN. >> >> Are those really folders in th

Re: [Jsynthlib-devel] Change project structure

2014-01-03 Thread Packe
taining syses dumps auto generated and used by my test case. Where have I created more test folders? BR /Pascal 3 jan 2014 kl. 21:11 skrev Joachim : > Hi, > > why are you creating so many 'test' folders? > > Cheers, > Joachim > > Am 20.10.2013 22:09, sch

Re: [Jsynthlib-devel] Change project structure

2014-01-03 Thread Packe
re five system-test folders. Like system-test5 here: > http://sourceforge.net/p/jsynthlib/code/1238 > > Joachim > > Am 03.01.2014 21:39, schrieb Packe: >> >> Hi, >> >> I think I only created one? >> >> I'm not used to SVN so there has been

Re: [Jsynthlib-devel] Change project structure

2013-11-05 Thread Packe
skrev Frankie Fisher : > 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&qu

Re: [Jsynthlib-devel] Change project structure

2013-10-22 Thread Packe
ns of OS X). There is a lot of old documentation describing how to > set up midi providers for java, so some of that might need to get updated. > > > On 20/10/2013 21:09, Packe wrote: >> Hi again, >> >> I have now been given admin rights to this project (thanks Joachim

Re: [Jsynthlib-devel] Change project structure

2013-10-20 Thread Packe
y are submitted. I'll wait one week from now to let you get back with your thoughts before starting any work at all. Chris, would you be able to explain what you did for changes to the ant script on the refactor branch? BR /Pascal 17 okt 2013 kl. 17:07 skrev Packe : > Hi Chris! > &g

Re: [Jsynthlib-devel] Change project structure

2013-10-17 Thread Packe
is project is a good start. Even if it is really messy it has one advantage: it works (at least for the synthesizers I own). BR /Pascal 17 okt 2013 kl. 15:58 skrev "chrisware...@chriswareham.demon.co.uk" : > Hi Pascal, > > Packe [pack...@yahoo.se] wrote: >> >>

Re: [Jsynthlib-devel] Change project structure

2013-10-16 Thread Packe
to handle dependencies. What would you say is left before we can merge the refactor branch to trunk? BR /Pascal 16 okt 2013 kl. 12:46 skrev "chrisware...@chriswareham.demon.co.uk" : > Packe [pack...@yahoo.se]: >> >> Hi again, >> >> I have now committe

[Jsynthlib-devel] Change project structure

2013-10-14 Thread Packe
Hi again, I have now committed my Roland D50 and Emu Proteus/2 contributions. One thing that annoys me is the source code structure. I have seen in previous threads in this mailing list some people suggesting porting JSynthLib to the Maven folder structure. I think this would be a good idea as

Re: [Jsynthlib-devel] Upload code changes

2013-10-03 Thread Packe
ut your docs there. > > It's one of the fields you pass to the constructor for core.Device. You can > see how I do it in synthdrivers/CasioCZ1000/CasioCZ1000Device. > > -Bill Zwicky > > > -Bill Zwicky > > > > On Tue, Oct 1, 2013 at 4:17 AM, Packe wr

Re: [Jsynthlib-devel] Upload code changes

2013-10-01 Thread Packe
ch then submit it via the > sourceforge patch interface. > > > On 01/10/13 10:46, Packe wrote: >> Hi, >> >> I have now implemented jSynthlib Sysex support for both the Roland D50 >> and also the E-MU Proteus/2. >> >> 1. There are some limitations to my imp

[Jsynthlib-devel] Upload code changes

2013-10-01 Thread Packe
Hi, I have now implemented jSynthlib Sysex support for both the Roland D50 and also the E-MU Proteus/2. 1. There are some limitations to my implementation. How do I document these for the end user? 2. How do I upload the source code to Sourceforge? BR /Pascal --

Re: [Jsynthlib-devel] Problem with DeviceListWriter

2013-05-15 Thread Packe
#x27;ve got java 1.7 - which version are you using? > > $ javac -version > javac 1.7.0_15 > > > > On 13/05/2013 20:20, Packe wrote: >> Hi, >> >> I'm trying to write a driver for my Roland D50. I have added the files and >> wanted to generat

[Jsynthlib-devel] Problem with DeviceListWriter

2013-05-13 Thread Packe
Hi, I'm trying to write a driver for my Roland D50. I have added the files and wanted to generate the synthdrivers.properties file. Unfortunately the DeviceListDriver application fails. It creates an empty file only containing the two first lines of comments in the properties file. I have add

Re: [Jsynthlib-devel] OS X Midi Provider

2013-04-03 Thread Packe
And I agree that a separate package would be for interest - I've two other > Java applications which don't work under MacOS anymore, and would be glad to > get them running again. > > Best Regards, Thorsten. > > > Am 02.04.2013 um 23:15 schrieb Packe : > >>

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

2013-04-02 Thread Packe
this library in its own project in Sourceforge as it potentially can be used by other Java applications as well. Any opinions on this? BR /Pascal 29 mar 2013 kl. 23:01 skrev Packe : > Hi, > > I am re-using the CAProvider code and just replacing the Java OSX MIDI API > (which d

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

2013-03-29 Thread Packe
>> De: Frankie Fisher >> À: jsynthlib-devel@lists.sourceforge.net >> Envoyé: Thu, 28 Mar 2013 23:03:41 +0100 (CET) >> Objet: Re: [Jsynthlib-devel] OS X Midi Provider >> >> I think this would be very useful - I'm pretty sure that noone has done >> t

[Jsynthlib-devel] OS X Midi Provider

2013-03-19 Thread Packe
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 layer for new versions of OS X that supports Midi Sysex messages. It has another interface than the Java Midi Device Provider doe