2011/9/19 frankster :
> On 09/19/11 18:31, Joe Emenaker wrote:
>> On 9/16/2011 7:24 AM, frankster wrote:
>>> Just noticed that the sf.net page was registered in december 2001, which
>>> means that JSL is nearly 10 years old!
>> Should we release a special "Collector's Edition"? It could come with a
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 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
> by concatenating DESCRIPTION and NAME, but I wonder if it should instead
> be based
On 9/19/2011 6:08 PM, franks...@users.sourceforge.net wrote:
> fixed crash which can occur at startup when less midi devices are installed
> than when prefs were saved.
>
> The problem was that the midi device is stored in the prefs as an integer.
> When the prefs are loaded, the device number is
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
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
Most (if not all) Swing components render html:
http://download.oracle.com/javase/tutorial/uiswing/components/html.html
cheers
Maciek
W dniu 17.09.2011 20:18, frankster pisze:
>
> I suppose that a separate file would be best as it would mean that
> programming skills (however minimal) wouldn't b
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 be two options - randomize
all parameters, or only para
On 9/14/2011 2:19 PM, Frankie Fisher wrote:
> I have been looking at doing a driver for the Roland U220 at the
> moment and that uses the same memory-mapped bulk data transfer as the
> MT32, I wonder if there is scope for commonality between some of the
> Roland drivers.
I think I put that idea
On 09/19/11 18:31, Joe Emenaker wrote:
> On 9/16/2011 7:24 AM, frankster wrote:
>> Just noticed that the sf.net page was registered in december 2001, which
>> means that JSL is nearly 10 years old!
> Should we release a special "Collector's Edition"? It could come with a
> certificate of authentici
On 9/16/2011 7:24 AM, frankster wrote:
> Just noticed that the sf.net page was registered in december 2001, which
> means that JSL is nearly 10 years old!
Should we release a special "Collector's Edition"? It could come with a
certificate of authenticity signed by all of us. :-)
Or, maybe... we
> would this mean that JSynthlib runs only with JRE 1.6?
>
> Anyway: Is anyone even using a version prior to JRE 1.6?
> 1.6 has been out for a couple of years.
Java 1.5 (and before) is End Of Life so there is no reason to support
anything older than 1.6. (And 1.6 has been around for ages.)
Regard
12 matches
Mail list logo
