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

Re: Fwd: Re: [Jsynthlib-devel] Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

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

Jeff Weber wrote:

>--- Joe Emenaker <jo...@em...> wrote:
>  
>
>>I can only think of *two*
>>different ways of doing the 
>>conversion that aren't completely insane...
>>    
>>
>For each group of seven bytes the FCB1010 takes bit 8
>from each byte and creates and 8th byte at the end of
>the group. The representation of the 8th byte is:
>0, msb byte 6, msb byte 5, msb byte 4...msb byte 0
>
>Make sense?
>  
>
Doh! That's one of the "insane" ways. :) After thinking about it, it's 
probably not all that insane. In fact, the code to to the 
encoding/decoding is probably tighter than the code to do it the Alesis way.

The Alesis way is a little easier to draw on paper. Just take the 
meaningful 7 bits of the eight MIDI bytes and string them together. You 
now have 56 bits. Take the first 8 and that's your first "real" byte, 
the next 8 are your next byte, etc.

So, MIDI bytes like 0x37 0x21 0x44 ... would give you a string of bits like:
  0110111 0100001 1000100 ...

re-grouped as 8-bit sets, you get:
 01101110 10000110 00100...
or...
 0x6E 0x86 ...

Anyhow, I'm still not convinced that each synthdriver author should have 
to re-write nibbilizers each time. I'm sure that there are a fixed 
number of ways were going to see this done in real life... and they're 
all going to need to be accessible to the XML driver *anyway*... so I 
still vote for consolidating them somewhere.

- Joe

Re: Fwd: Re: [Jsynthlib-devel] Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

[Jeff W. <jww...@ya...>]

--- Joe Emenaker <jo...@em...> wrote:

> This is what I was concerned about in my original
> post.... that it's 
> common enough that people have implemented it
> several times in various 
> synthdrivers.
> 
> We should see if the FCB1010 does it the same way as
> the Alesis and/or 
> the XML driver and, if they're the same, move them
> into the general 
> synthdriver utils. I can only think of *two*
> different ways of doing the 
> conversion that aren't completely insane... and one
> of them makes a lot 
> more sense than the other. So, it's very likely that
> they're all the 
> same and we can have a global
> deNibbilize/reNibbilize.
> 
> - Joe
> 

For each group of seven bytes the FCB1010 takes bit 8
from each byte and creates and 8th byte at the end of
the group. The representation of the 8th byte is:
0, msb byte 6, msb byte 5, msb byte 4...msb byte 0

Make sense?

I just took a quick look at the Aleses sysex spec and
I suspect that they might be putting the eighth byte
at the beginning of the sequence (although I did not
read deep enough into it to tell for sure). You would
also have to know if they're storing the bits of the
eighth byte in the same order or the opposite order as
the FCB1010.

Jeff



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

Re: [Jsynthlib-devel] Behringer V-Amp 2 Support

[Jeff W. <jww...@ya...>]

--- Joe Emenaker <jo...@em...> wrote:

> No, but I just got my Bass V-Amp today, and there's
> probably a lot of 
> similarity between them. We should probably
> collaborate and put as many 
> common functions into common files.
> 
> - Joe
> 

Joe,

Sounds like a plan. I've already got a set of working
drivers and was planning to start on the editor this
weekend. One problem though--I have a sysex spec for
the original V-Amp but I haven't been able to locate
one for the V-Amp 2. Behringer doesn't have any specs
posted for either of the guitar V-Amps, the V-ampire
or the V-Amp Pro on their website. I haven't checked
if they have any for the Bass V-Amp.

Anyway I figured I'd have to just write some code and
figure it out the differences on my own.

How do you think we should proceed?

Jeff

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

Re: [Jsynthlib-devel] Behringer V-Amp 2 Support

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

Jeff Weber wrote:

>My wife gave me a Behringer V-Amp 2 for Christmas. I
>would like to write drivers and an editor for it. Is
>anyone else already working on this?
>  
>
No, but I just got my Bass V-Amp today, and there's probably a lot of 
similarity between them. We should probably collaborate and put as many 
common functions into common files.

- Joe

Re: Fwd: Re: [Jsynthlib-devel] Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

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

Jeff Weber wrote:

>There are two methods, deNibblize, which converts
>the 8 byte format to the seven byte format and
>reNibblize which converts it back again.
>
>This might not be exactly the same but you could copy
>this code and modify it to suit your needs.
>  
>
This is what I was concerned about in my original post.... that it's 
common enough that people have implemented it several times in various 
synthdrivers.

We should see if the FCB1010 does it the same way as the Alesis and/or 
the XML driver and, if they're the same, move them into the general 
synthdriver utils. I can only think of *two* different ways of doing the 
conversion that aren't completely insane... and one of them makes a lot 
more sense than the other. So, it's very likely that they're all the 
same and we can have a global deNibbilize/reNibbilize.

- Joe

[Jsynthlib-devel] Behringer V-Amp 2 Support

[Jeff W. <jww...@ya...>]

My wife gave me a Behringer V-Amp 2 for Christmas. I
would like to write drivers and an editor for it. Is
anyone else already working on this?

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

Fwd: Re: [Jsynthlib-devel] Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

[Jeff W. <jww...@ya...>]

Joe,
 
The Behringer FCB1010 MIDI foot controller has a
similar format. Check out FCB1010ParamModel.java in
the BehringerFCB1010 package.
There are two methods, deNibblize, which converts
the 8 byte format to the seven byte format and
reNibblize which converts it back again.

This might not be exactly the same but you could copy
this code and modify it to suit your needs.

Jeff


> --- Joe Emenaker <jo...@em...> wrote:
> 
> > I'm reading the sysex spec on the Alesis SR-16
> drum
> > machine.
> > 
> > Since it uses full 8-bit values in for some
> > settings, it turns each set 
> > of 7 8-bit bytes into 8 7-bit bytes.
> > 
> > Seems like it would be something that happens in
> > other synths. Is there 
> > already a function in JSL that does this so that I
> > don't have to write 
> > it again?
> > 
> > - Joe
> > 
> > 
> >
>
-------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT
> > Products from real users.
> > Discover which products truly live up to the hype.
> > Start reading now.
> >
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > Jsynthlib-devel mailing list
> > Jsy...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
> > 
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Take Yahoo! Mail with you! Get it on your mobile
> phone. 
> http://mobile.yahoo.com/maildemo 
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail

Re: [Jsynthlib-devel] So, what's the next big feature?

[Hiroo H. <hir...@co...>]

OK.  I'll add some more information on the comment.

Thanks.

Rib> The problem was that you not only had to set the JMenuBar to null, but
Rib> also deactivate and then reactivate the window before disposing it.
Rib> The new URL is http://lists.apple.com/archives/java-dev/2003/Dec/msg00122.html
Rib> 
Rib> It seems Apple was investigating the problem last July. I just tested
Rib> it though, and unfortunately it still has not been fixed in the
Rib> current Java release.
Rib> However, instead of deactivating and activating the frame we can call
Rib> both setMenuBar(null) and setJMenuBar(null).
-- 
Hiroo Hayashi

Re: [Jsynthlib-devel] So, what's the next big feature?

[Hiroo H. <hir...@co...>]

Hi Rib,

Rib> Of course we need to move the menu stuff out of the Desktop classes
Rib> first, 

I've been working on this and it is almost done on my local work space. 
Once 0.20 CVS tag will be made I'll check it in.

I have two questions to you to complete the work.  JSLFrame has the
following code for Mac OS.

	public void setVisible(boolean b) {
	    if (MacUtils.isMac()) {
		if (b && getJMenuBar() == null) {
		    setJMenuBar(Actions.createMenuBar());
		} else if (!b) {
		    // Remove menubar so frame can be disposed.
		    // http://archives:arc...@li.../archives/java-dev/2003/Dec/04/disposingofjframesusescr.001.txt
		    //JMenuBar mb = getJMenuBar();
		    setJMenuBar(null);

		    desktop.getInvisible().getJFrame().requestFocus();
		    requestFocus();
		}
	    }
        ....

Q1. It seems that a frame can not be disposed unless menu bar is removed
by calling setJMenuBar(null).  Is it still true for J2SE 1.4 and/or
later which is the requirement of JSynthLib?  (In other words, do we
still have to do this hack?)  The URL in the comment above is not valid
now.

Q2. There are two requestFocus() call in the code above.  Do we really
need the first one ("desktop.getInvisible().getJFrame().requestFocus();")? 
I think the effect of the first one is hidden by the second one.

Thanks.
-- 
Hiroo Hayashi

[Jsynthlib-devel] Re: Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

[Rib R. <ri...@gm...>]

The org.jsynthlib.plugins.Decoder class is designed for sharing this
type of functionality.  However, it would probably be difficult to use
outside of an XML driver and XML drivers aren't very useful until the
XML Editor support is finished.


On Tue, 22 Feb 2005 03:18:25 -0800, Joe Emenaker <jo...@em...> wrote:
> I'm reading the sysex spec on the Alesis SR-16 drum machine.
>
> Since it uses full 8-bit values in for some settings, it turns each set
> of 7 8-bit bytes into 8 7-bit bytes.
>
> Seems like it would be something that happens in other synths. Is there
> already a function in JSL that does this so that I don't have to write
> it again?
>
> - Joe
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>

Re: [Jsynthlib-devel] Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

[Peter H. <pe...@ha...>]

The Alesis DM Pro driver uses the same method, as does the QS(?). It's not 
shared though, perhaps it should be?

/Peter


> I'm reading the sysex spec on the Alesis SR-16 drum machine.
>
> Since it uses full 8-bit values in for some settings, it turns each set of 
> 7 8-bit bytes into 8 7-bit bytes.
>
> Seems like it would be something that happens in other synths. Is there 
> already a function in JSL that does this so that I don't have to write it 
> again?
>
> - Joe

[Jsynthlib-devel] Method to pack/unpack 7-bit bytes to/from 8-bit bytes?

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

I'm reading the sysex spec on the Alesis SR-16 drum machine.

Since it uses full 8-bit values in for some settings, it turns each set 
of 7 8-bit bytes into 8 7-bit bytes.

Seems like it would be something that happens in other synths. Is there 
already a function in JSL that does this so that I don't have to write 
it again?

- Joe

Re: AW: [Jsynthlib-devel] Compiling the OSX driver code. Not using com.apple.jar?

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

denis queffeulou wrote:

> I prefer the couple ant/JEdit to Eclipse or Netbeans when doing simple 
> developpement (I hate wasting time to configure IDE).
>
> I think it's a good thing to maintain the build.xml because it can be 
> used as well in IDE as input for project or with ant. Also, it 
> describes the main tasks of building JSynthLib in a clear manner.

I love using ant/JEdit, too. Up until I tried NetBeans and Eclipse, most 
IDE's merely provided syntax highlighting, an easy way to invoke the 
compiler, and, most importantly, possibly a debugging environment.

Eclipse and IDEA now provide some things that just make it *really* nice 
to use them, these days. One thing that I really like is being able to 
right-click on any identifier and I can choose "Go To -> Declaration" 
and it will take me to where I declared that variable. Then, I can do 
the same thing to the classname and go directly to the class definition. 
It really makes it easy to find things. Another big advantage is that 
the IDE does completion. I can type "someobject.set" and the IDE will 
quickly find out what class "someobject" is and it will give me a list 
of all of the methods that begin with "set". It will also show me the 
parameters and return-values that they use.

We're way off-topic now, and I don't want to start a religious war. I 
just wanted to point out that I *do* like the ant/JEdit combination (and 
still use it for things like JSP development), but the IDE's that are 
available these days really do make it nicer to work on projects the 
size of JSL.

- Joe

Re: [Jsynthlib-devel] Eclipse

[Hiroo H. <hir...@co...>]

Steven> Have you (needed to) set up any specific user libraries in eclipse for 
Steven> this project?

See "How to set up Eclipse for JSynthLib?" on the FAQ in programming.html.
-- 
Hiroo Hayashi

[Jsynthlib-devel] Eclipse

[Steven S. <ste...@co...>]

Joe Emenaker wrote:

> Hiroo Hayashi wrote:
>
>> Could you teach me where this feature is described in Eclipse help?
>>
>> I found
>>  Java Development User Guide->Tasks->Refactoring->Renaming a package
>> but this just renames a package and is not what I'm looking for.
>>
>> Or does the way described in
>>  Java Development User Guide->Tasks->Using the Package Explorer->
>>  Moving folders, packages, and file
>> change package and import statements?
>>  
>>
> Well, I just tried it in Eclipse 3.0.1 and it seems to work. Here's how:

Have you (needed to) set up any specific user libraries in eclipse for 
this project?

Re: AW: [Jsynthlib-devel] Compiling the OSX driver code. Not using com.apple.jar?

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

> Anyway it seems to me that I'm the only one
> using ANT for compilation.

I also use ant since I discovered it was installed on my mac !

I prefer the couple ant/JEdit to Eclipse or Netbeans when doing simple 
developpement (I hate wasting time to configure IDE).

I think it's a good thing to maintain the build.xml because it can be used as 
well in IDE as input for project or with ant. Also, it describes the main tasks 
of building JSynthLib in a clear manner.

-- 
Denis

Re: [Jsynthlib-devel] So, what's the next big feature?

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

Hiroo Hayashi wrote:

>Could you teach me where this feature is described in Eclipse help?
>
>I found
>  Java Development User Guide->Tasks->Refactoring->Renaming a package
>but this just renames a package and is not what I'm looking for.
>
>Or does the way described in
>  Java Development User Guide->Tasks->Using the Package Explorer->
>  Moving folders, packages, and file
>change package and import statements?
>  
>
Well, I just tried it in Eclipse 3.0.1 and it seems to work. Here's how:

You must be in the *Java* perspective.
 From there, you right-click on a file and select "Refactor->Move..." 
and it presents you with the current list of packages (like like IDEA 
does). There is also a checkbox to tell it to update all references to 
the moved files.

I guess... now the only real question is how to arrange the new package 
structure. Since this is probably going to cause a hiccup in the CVS 
revisions of all of the files, we don't want to have to do this *again* 
in the future. Let's make sure that we get it right this time.

- Joe

Re: [Jsynthlib-devel] So, what's the next big feature?

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

Hiroo Hayashi wrote:

>Rib,
>
>Rib> > I think the refactoring feature in Eclipse may reduce the work a lot,
>Rib> > but I'm not sure.
>Rib> 
>Rib> Yeah. Most of it should probably take an hour or so using eclipse.
>Rib> Splitting the synthdrivers into manufacturer packages might be harder,
>Rib> though.
>
>Could you teach me where this feature is described in Eclipse help?
>  
>
I could look around. What version of Eclipse are you using?

I just tried it in IDEA and it is *obscenely* easy. You just select 
file(s), right-click, and select "Refactor->Move...". It then prompts 
you with a list of all of the existing packages. I could probably do it 
in a little over a minute.

It shouldn't be too difficult, however, to do it with a global 
search-replace. You'd need to do four of them:
  search for "package core" and replace with "package org.jsynthlib"
  search for "import core" and replace with "import org.jsynthlib"
  search for "package synthdrivers" and replace with "package synthdrivers"
  search for "import synthdrivers" and replace with "import 
org.jsynthlib.synthdrivers"

Then, drag all files and folders "core/" into "org/jsynthlib/" and drag 
the synthdrivers/ directory into "org/jsynthlib/" as well. That would 
get you 90% of the way there. The nice thing about it is that it should 
work for stuff with text *after* it. For example "package 
synthdrivers.Alesis5M" would also get turned into "package 
org.jsynthlib.synthdrivers.Alesis5M", etc.

- Joe
 

Re: [Jsynthlib-devel] So, what's the next big feature?

[Hiroo H. <hir...@co...>]

Rib,

Rib> > I think the refactoring feature in Eclipse may reduce the work a lot,
Rib> > but I'm not sure.
Rib> 
Rib> Yeah. Most of it should probably take an hour or so using eclipse.
Rib> Splitting the synthdrivers into manufacturer packages might be harder,
Rib> though.

Could you teach me where this feature is described in Eclipse help?

I found
  Java Development User Guide->Tasks->Refactoring->Renaming a package
but this just renames a package and is not what I'm looking for.

Or does the way described in
  Java Development User Guide->Tasks->Using the Package Explorer->
  Moving folders, packages, and file
change package and import statements?
-- 
Hiroo Hayashi

Re: [Jsynthlib-devel] F0 Byte of sysex record getting corrupted

[Jeff W. <jww...@ya...>]

I found the problem. It was happening with the
AlesisDM5SysInfoDriver. I ran into this before with
patches that do not have a checksum. I was forgetting
to override Driver.calculateCheckSum with a null
method.

Sorry for the false alarm.

Jeff


		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 

Re: [Jsynthlib-devel] Compiling the OSX driver code. Not using com.apple.jar?

[Hiroo H. <hir...@co...>]

Joe,

Quick answer before going to office.

Joe> Since there doesn't seem to be any updated com.apple.jar in the CVS, how 
Joe> are people compiling the OSX driver on non-OSX machines (or *are* you 
Joe> even compiling them. Are you excluding them from the compilation?).

Don't *include* MIDI provider for other OS.  Build a MIDI provider you
need it.  This is the current way.  Simpler than before.

See programmers.html.
-- 
Hiroo Hayashi

AW: [Jsynthlib-devel] Compiling the OSX driver code. Not using com.apple.jar?

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

> Since there doesn't seem to be any updated com.apple.jar in=20
> the CVS, how=20
> are people compiling the OSX driver on non-OSX machines (or *are* you=20
> even compiling them. Are you excluding them from the compilation?).

In Eclipse I exclude the OSX classes from the build process.

And when I use ANT it is also excluded.

As I don't have a Mac OS X development computer
I haven't created an ANT task that compiles=20
this stuff.
Anyway it seems to me that I'm the only one
using ANT for compilation.

Regards,
Joachim Backhaus

[Jsynthlib-devel] Compiling the OSX driver code. Not using com.apple.jar?

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

The last time I tried to compile the entire CVS tree from scratch, the 
compile failed because I didn't have the OSX MIDI classes available 
(because I wasn't using OSX).

To get around the problem, I made some pseudo classes  that did nothing, 
but which, at least, had the correct method and property definitions so 
that the compilation could proceed without errors. I uploaded it to the 
Yahoo groups at the time and then Hiroo re-submitted them as a .jar file.

Now, using the old .jar file, I got compilation errors again, since the 
OSX driver seems to have been modified to use some methods and 
properties that weren't in the original com.apple.jar. I've updated them 
so that they work again, but this brings up a question:

Since there doesn't seem to be any updated com.apple.jar in the CVS, how 
are people compiling the OSX driver on non-OSX machines (or *are* you 
even compiling them. Are you excluding them from the compilation?).

- Joe

Re: [Jsynthlib-devel] So, what's the next big feature?

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

Hiroo Hayashi wrote:

>2. package structure change (move to org.jsynthlib)
>
>2.1 making consensus
>We had discussion and I made summary a few times.  But I could not
>continue the job for my laziness.
>
>2.2 making change
>It is too much work for a person to make the all of changes.  How can we
>share the work?
>
>I think the refactoring feature in Eclipse may reduce the work a lot,
>but I'm not sure.
>  
>
Yes, it would. Also, IDEA has the same refactoring features and it 
really does work very easily. I could probably do all of this in an evening.

Although I was a big proponent of this idea back when I proposed it a 
couple of years ago (and I still would like to see it happen) one big 
downside to this has occured to me (which has probably been mentioned 
already). This will probably have *dramatic* effects on 
version-comparison in the CVS tree. Right now, on SourceForge, you can 
go into the CVS tree and compare any verison of a file to any other 
version of it. If we move the files in the CVS tree, I fear that CVS 
will think that we deleted a file and added another (instead of figuring 
out that we just moved one). I don't know how smart CVS is about things 
like that.

The alternative would be to merely change the *package* directives in 
the source so that they *compiled* to a different directory structure, 
while leaving the *source* files in their *old* structure. This would be 
the worst possible solution, in my opinion. In fact, I feel that it 
would be worse than how it is *now*.

Has this consideration already been addressed?

- Joe

Re: [Jsynthlib-devel] F0 Byte of sysex record getting corrupted

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

Jeff Weber wrote:

>There seems to be an intermittant bug somewhere in the
>core code where the start byte (the F0 byte) of the
>sysex record sometimes gets overwritten.
>
Well, I don't know if the midi test methods I wrote 2 years ago are 
still in the source but, if they are, you can use them (with a midi 
cable looping your interface's OUT to the IN) to do a "sanity check". 
This would let you know if the problem lies in the low-level parts (ie a 
problem in the methods of your current java-midi driver, or the 
lower-level midi drivers in your OS, or the midi interface itself or the 
cable).

The way things were headed back before the aliens abducted me, the midi 
layer was intended to completely encapsulate the creation, sending, and 
receiving of all midi messages. So, if things are still 
well-encapsulated, the problem *should* be in the midi driver. Which one 
are you using? I'm not even sure which ones are still in the package. 
JavaMidi, jMidi, ALSA, OSX?

- Joe