Rayzoon Technologies LLC

[Tech_DAWg]

[Dewdman42]

jackwasio is the virtual ASIO driver, wineasio.dll.so, that is installed in the wineskin to make it work.

[Dewdman42]

So I see that .90 beta9 is beta version introduced for Lion and Mountain Lion compatibility. The bad news is that this new version of Jackosx may not be backwards compatible with wineasio. when I get some time I will try to install that version of JackOSX to see if it works for me on Snow Leopard or not. But I am guessing that is the culprit. Either because its beta or because they have changed something fundamental in the JackOSX subsystem which breaks compatibility with wineasio. wineasio interacts with jackOSX directly.

This is yet another reason I'm not leaving Snow Leopard any time soon.

[Saw]

I use Jamstix with topicstarter help

I have Mountain Lion 10.8.2.- there are no problem with Jamstix.

[kalkenji_92]

How do you get Jamstix Wine to work with Mountain Lion, Saw?

I have Mountain 10.8.3 but can't seem to install due to the JackOsx not installed error. I use JackOsx 0.9 beta 13

[Dewdman42]

I figured out the problem with JackOSX 0.90. They have changed it again in a way that broke compatability with Wineasio. They changed the location of some framework libraries which were previously in /LibraryFrameworks and now they are in /System/Library/Frameworks.

To make this work with JackOSX 0.90, install Jack first, then have a look at /usr/local/lib. Look at all the jack related sym links that there (see below). Those sym links all need to be created in /usr/lib. If you had this working before then you must have done the other hack that copies the old sym links from Jack .89. but those sym links have changed, and so the changed ones now have to be copied again to /usr/lib.

Then I believe Jack .90 will work.

[Dewdman42]

This is how I think you can easily recreate the proper sym links after installing JackOSX 0.90, run as root.

[Dewdman42]

I installed JackOSX 0.90 on my Snow Leo system here and ran the above little hack to correct the sym links and it seems to be working fine, so I believe that is the correct solution when using JackOSX 0.90.

Explanation

1. JackOSX installs a number of Framework files in a working OSX system. It also installs some sym links to those libraries as well.
   
2. Under Leopard, those sym links seemed to be located in /usr/lib, and wineasio needed to locate them there, and worked fine as is.
   
3. Under Snow Leopard, for some reason wineasio broke. Some people figured out that the sym links needed to be copied from /usr/local/lib to /usr/lib in oder for JackOSX/wineasio combo to work together. It seems that JackOSX changed the location of those sym links, but copying the sym links to the old location kept wineasio working. See http://forum.winehq.org/viewtopic.php?t=7938
   
4. JackOSX 0.90 further changed, in so much that the actual Framework files have been moved from /Library/Frameworks/... to /System/Library/Frameworks/.. JackOSX installs correct sym links to those new Framework locations, but again, they are put in /usr/local/lib and we have to copy them from there to /usr/lib in order for 0.90 to play well with wineasio.
   
5. The little tar script I provided is the only way I know to cleanly copy sym links. It seems to work on my Snow Leo system. I can't vouch for Lion or ML, but I imagine they will work also, since the problem is the need by wineasio to see those libs in /usr/lib.
   

[Dewdman42]

New version of the JamstixWine installer is posted at the top of this thread. Nothing major, it just deals with some incompatibilities with the latest version of JackOSX.

[Bagatell_]

[ricinro]

http://www.emusician.com/news/0766/apple-logic-pro-x-%E2%80%93-an-exclusive-first-look/152186

I am not going to upgrade my OSX to get logic pro X but it seems that Apple has adopted the jamstix idea. Maybe it is jamstix?

Still looking forward to Jamstix for OSX!

[Dewdman42]

we'll see how it turns out, but my impression is that this will be more like garageband type behavior. It looks to me like it has a lot of focus on how the produced drums sound...mic placement, etc....with perhaps a library of preset patterns to choose from, perhaps some slight variations in the way patterns are arranged or tweaked slightly.

Jamstix has orders of magnitude more intelligence in terms of modeling drummer behavior....but let's see how the reviews come out. My personal feeling is that the new Drummer instrument in Logic will end up turning out hoardes of tracks that all sound kind of vanilla.

Jamstix also has the percussion engine, etc.. Its not going to replace Jamstix.

But it DOES run on a mac!

[willowhaus]

Finally got it working on my Mac! Thanks, this worked really great (although it was s-l-o-w to load all my Drum Paks...but I ain't complaining!)

One thing I can't figure out yet, though, is getting MIDI output recorded. I'd like to use JS to compose a part & fly it back into a native DAW. Tried arming the track in Reaper & setting it to record MIDI In, but it's just not doing it. Any thoughts?

[Dewdman42]

The best way to get the midi back to your main DAW is to develop the midi tracks in Reaper-win32 and then export the midi tracks to file(s) and then import those midi tracks in your OSX DAW.

Consult the reaper and jamstix manuals for how to record your drum parts from jamstix onto a midi track of the host daw.

I find that the easiest way is to develop the whole song inside Jamstix. When you feel the parts are ready you can click-drag the parts from the jamstix window over to midi tracks on reaper and they will plop into place. From reaper you can export them as midi files. And this works fine under the wine environment (because the drag and drop is all within the reaper-win32 program).

Then import the midi files to your OSX daw.

There are other ways to capture the midi too, I think you can enable the midi out of Jamstix, as if you were using it to drive a seperate drum sampler or something like that. Then you should be able to record-arm a track and record it, but I like the drag and drop method better.

You can also send the midi output out of reaper-win32, over apple iAC and into your host OSX DAW and record it there in real time that way too. that's good to setup while you're writing the song so that you can hear the actual drum sounds you will use. Takes some fiddling to set that up. However you get a bit of delay that way due to the IAC process, its not noticeable, but I sleep better at night about it by just exporting tight midi files from Jamstix and reaper, then they are exactly what jamstix intended.

[willowhaus]