Rayzoon Technologies LLC

[zeph_yrus]

Can confirm here.
Plus, the jamstix window constantly steals focus in reaper when you click on it, mainly noticed when you are in fullscreen mode. I think this is a main problem with the new concept due the plugin server window. I stick with the 3.5. The dropdown issues (mouse pointer, slow doesn't recognize every movement when moved fast) also present. All in all it feels very clunky. rzdlog doesn't show any errors.

[minerman_1]

So far so good with Beta 14...I did have an issue where I used the "Undo history" in Reaper to take the project back to intital state, Jamstix wouldn't trigger the samples again, but, closed the project, re-opened it, & everything's been ok since....fingers crossed..

Wanna say thanks for all the hard work Ralph, I'm sure all this is very tedious/hair pulling stuff, but I really do appreciate all the work & dedication you put into Jamstix.....Great drum app!!!!!!

[craig_glenn]

Ralph, first with Beat 13 and with Beta 14 (Reaper 64bit) ...

still having sync issues...i have to have the icon (black dot) on the time line all the way over to the right 50ms behind beat i think it is in order to sync it to the song 120bpm...

bearing in mind i have been working on this song for a while...didnt have this issue with 3.5.1. beta 8

[somebody_else_uk]

Followed the instructions for JS36b14 install - removing the relevant files as per earlier post - and found the GUI won't load at all in Reaper 4.591x64. Couldn't send a log file as it didn't generate one.
Restored PC back to before install, now on JS36b13, all fine.
Gonna try just installing b14 'over the top' later, without the file removals...

[keys_reaper]

[jas_lan]

I installed Beta 14 two days ago. I have loaded and played around with it a fair amount. I have not seen any errors thus far. Particularly, I have NOT seen that white screen GUI with the error message, "can not create core element" at all since (I think) beta 12. I have not done a lot of creating NEW songs, parts, etc., but have done some editing of existing songs, parts, played with the mixer and kits, etc.

Bottom line: It seems to be working great!

After using it a while, I would like to comment on the new system of "sub-menus". I PREFER the new "click" in order to get the sub-menu as opposed to the "pause" or "hover" and then sliding the mouse horizontally. I am reminded that with the old hover system, it was a tad annoying to wait for the menu and then have to be careful, as you slide the mouse horizontally, that you do NOT move vertically BEFORE you get over to the sub-menu. I honestly think the click is easier and faster. I guess the absolute BEST solution is a "hover" or "click" option. For example, hover and wait it you like it and don't want to click, OR, click without waiting and have the click "pin down" the sub-menu so I can move my mouse DIRECTLY to the item in the sub-menu without having to carefully go across and then vertical. Of course, "better" is sometimes the enemy of "good enough".

That being said, I do see the worth of having the new sub-menu pop up beside the parent menu as opposed to REPLACING it. The replacing of the parent menu can be slightly "disorienting" and is not an inherently "natural" form of navigation. It certainly can be gotten used to and therefore not a major design problem. The second minor advantage of keeping the parent menu visible is that, sometimes, when looking for a particular command, or a "hit", it helps to be able to see what the other choices on the parent menu were (without losing the current sub-menu).

I also realize that with the multiple layers of sub-menus, the "placement" of those sub-menus becomes tricky for the GUI to handle and results in the displaced sub-menus on multiple monitors we were seeing before.

BOTTOM LINE on the sub-menu behavior...
I prefer the clicks to the hover but, if I could still see the parent menu, I would like it slightly more. It is perfectly acceptable and usable as is.

J.L.
_________________
Core i7 4712QM, 16GB, Cubase 9 Pro on Windows 10. Scarlett 2i2. M-Audio Axiom Pro 61. Komplete 8. Jamstix 3.6. Absolute 3 VST. 418 Carrier Landings.
SoundCloud

[Ralph [RZ]]

@funkycornwall: please email me rzdlog.txt and a screenshot of the GUI problems.

@zephyrus: please add this line to your jamstix3.ini file in the [GENERAL] section avoid the focus stealing:

PopupMode=1

@craig_glenn: please email me rzdlog.txt

@somebody_else_uk: sounds as if you have the old jamstix3.dll loading. Please double-check after B14 installation that the jamstix3.dll in your plugin search path is updated.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[max.noise]

[Ralph [RZ]]

Max, the log you sent shows no decomp errors. Please repeat the problem, close the host and then send rzdlog.txt again.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[max.noise]

[The_Dissonance]

since installing this beta, I have noticed my system audio acting strange. Not sure if it's related.

[Ralph [RZ]]

[The_Dissonance]

something is preventing my windows sound from working at all, even though my project with jamstix open is working. I am going to try a reboot first - but I figured I would post this in case somehow this sounds like something jamstix can do. I also find that projects with jamstix seem to freeze my whole computer for a bit when they are loading.

This could also be due to many factors, so I wouldn't take it too seriously yet. I will do a reboot.

[craig_glenn]

Hey Ralph...emailed you the log

[The_Dissonance]

ok, restarted and it must have been something else.