Well, I guess an editor window with most controls, and a library window
with most patches are bound to overwhelmingly impress an unsuspecting
bystander.
On 10/05/2011 08:19 AM, frankster wrote:
> Could maybe do with some up-to-date screenshots for the next release to
> put on freshmeat.net.
>
>
Hey, maybe this would be good moment to maybe contemplate on maybe
uhmm... name change?
JSynthLib sounds like library, not application. For this reason I passed
by it in searches when looking for synth applications.
How about SynthJ for the first contest entry?
On 09/23/2011 10:04 AM, Joe Eme
On 09/19/2011 03:56 PM, Frankie Fisher wrote:
>> Second idea is more complicated and to be honest I have no idea how to
>> > realize it:-D But It would be great to be able to translate patches
>> > between synths, at least to some extent.
> You're right, this is ridiculously complicated!
Actual
On 09/12/2011 04:27 AM, Martin Tarenskeen wrote:
>
> I don't know much about the internals of JSynthLib. But I have a feeling
> SysEx bank/patch recognition can be improved.
[...]
> If I would be a Java programmer I would take a look at it myself.
> But I have succesfully used tricks like these in
On 09/10/2011 08:25 AM, Joe Emenaker wrote:
>
> So, I finally got rid of all of the compile-time errors from my
> refactored code... and now I'm getting this error at the end of the compile:
>
>
> I tried compiling trunk and I also get this error. I even tried the
> latest copy of the groovy JAR
On 09/08/2011 04:31 AM, frankster wrote:
> Can anyone think of anything simpler that would do the job? Although one
> advantage of this is that it would
> keep the driver simple, and all the complexity would be in core base
> classes.
>
Well, i can think of something more complicated, but maybe mo
On 09/06/2011 11:20 PM, Joe Emenaker wrote:
> On 9/6/2011 3:04 PM, Joachim wrote:
>> > Hi Joe,
>> >
>> > according to the CVS-list it worked now.
>> > Can you tell us the commands you used?
> Well, you're going to be a bit disappointed.
>
So I was trying to figure out what might be wrong with l
On 09/06/2011 11:19 AM, Joe Emenaker wrote:
> I can't make a branch for my refactor. When I try it from the command
> line on my Ubuntu box, I do...
>
>> > svn copy
>> > https://jsynthlib.svn.sourceforge.net/svnroot/jsynthlib/trunk@r1051
>> >
>> > https://jsynthlib.svn.sourceforge.net/svnroot/j
On 09/04/2011 06:33 AM, frankster wrote:
> Assuming that it is the Keystation Pro 88 that is responding, then of
Did you try to autoscan when nothing but keystation is connected?
--
Vladimir
--
Special Offer -- Download
Hey,
Why do we have the synthdrivers.properties file under version control?
It is autogenerated during build, right. Am I missing something?
--
Vladimir
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a
On 09/03/2011 04:16 AM, William Zwicky wrote:
>> Well, it seems a little silly to me that we would need to make a new
>> > release number any time someone makes a new driver.
>> >
> Really? It's seems silly to me to make the user rummage around either
> SourceForge or a custom GUI for what amount
Hey,
I do not see a way I can assign bug report to myself. Is this
administrator only function?
--
Vladimir
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an ev
On 09/02/2011 11:57 AM, Joachim wrote:
> Ah, I don't think it makes sense to make a branch for every bug.
Not every bug, just complicated ones, involving non-obvious changes and
requiring extensive testing
>
> > and it might be not clear at start towards what release it
> > will be targete
On 09/02/2011 11:25 AM, Joachim wrote:
> Hi,
>
> > I could think of three directories: fixes, features, users.
>
> Normally branches are made for different releases. I don't see
> a benefit in these three suggested branches as bug fixes have to
> be merged with new features anyway. The users bra
Hey,
Is anyone else having problem not being able to diff build.xml from svn
clients. I get this error:
$ svn diff -r 1094 build.xml
Index: build.xml
===
Cannot display: file marked as a binary type.
svn:mime-type = application/xml
On 09/02/2011 09:38 AM, Joe Emenaker wrote:
> 1 - Will we want to manage the source for JSL and the drivers
> *separately* at that point? Would we have a branch for every driver, or
> have a branch for*all* of the drivers? Or is there a better way to do
> this than to use branches?
I would think
Frankie:
I was planning to apply my patch for sy77 on a separate branch once I
get svn access from Joachim. And from there I was thinking to
investigate how to make a pre-built binary available for download at SF
for anyone with actual hardware willing to test.
But in general synth drivers are
On 09/01/2011 07:54 PM, Joe Emenaker wrote:
>
> Okay, I think I understand Subversion enough to be dangerous.
>
> I'll need to make a branch to upload my refactored version to. All of
> the branches seem to be named after version numbers, but my
> understanding is that we can name them anything (li
On 09/01/2011 12:01 PM, Joe Emenaker wrote:
> On 9/1/2011 7:49 AM, Vladimir Avdonin wrote:
>> Regarding you experimental work:
>>
>> The mechanism for such activity provided by subversion is branch. Once you
>> created you branch you can screw it around in any way y
On 09/01/2011 11:44 AM, Joachim wrote:
> I tried but I didn't find your SourceForge user. If you mail it to me
> (off-list)
> or to the list I'm able to add you.
Thanks, but I am not sure the amount of effort I could currently afford to
contribute to the project would justify adding me as a dev
On 09/01/2011 10:02 AM, Joe Emenaker wrote:
> One of the things I'd like to see next is a mechanism to load just the
> synth drivers that you need. As things are now, compiling JSynthLib
> means compiling*all* of the synth drivers, and the same goes for
> distributing it. If we hope to add many mo
I think what the project is missing is releasing binary builds from svn for
download on regular basis.
That would allow more extensive testing of experimental code by people without
programming skills required to build themselves, but who really could use the
program in real world.
That probab
Joe,
You are listed as project admin. Did you ever try adding anyone to svn access?
Few months ago you said you could add me to the project, but that ended with
nothing. Did any other admins objected? Or it just did not work technically?
Regarding you experimental work:
The mechanism for such
Well, after looking carefully at developer section of the project I discovered
civilized way for occasional developer to submit changes. There is a patch
section. The lonely patch that i found in there was molding there since 2009.
The patch added support for SY85.
So I added a couple of patch
If you want to do something,
> simply do it and don't just talk about doing it.
>
> Cheers
> Joachim
>
> Am 31.08.2011 20:20, schrieb Vladimir Avdonin:
>> Hi,
>>
>> The project definitely feels dead. Maybe it is time for someone with enough
>> interest
Hi,
The project definitely feels dead. Maybe it is time for someone with enough
interest and time to fork it into fresh active project.
I was considering forking myself, but was not sure I could commit to
maintaining the whole project. I could contribute in developing and supporting
few synths
Hey,
I would like to spend some time developing for JSynthLib. Calling admins of the
project to allow me join the project.
I created a librarian plugin for yamaha SY77 that I would like to commit, and I
am willing to do some improvements to core source.
Thanks,
Vladimir
--
27 matches
Mail list logo
