Jamstix & Cubase
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Jamstix & Cubase
Just to clarify: you touch the volume slider in Cubase, sound stops and never comes back?
Ralph
Rayzoon Technologies LLC
Rayzoon Technologies LLC
Jamstix & Cubase
Hello, Ralph! Yes, that's right - the sound completely lost and not recovered. In this case, MIDI messages arrive in JS. Perhaps the problem in Cubase, expected next update, there are still a number of problems - for example, switching presets BFD3. I'm going to place the information in support Steinberg, but I need to make sure that there are no problems in JS.
Jamstix & Cubase
Problem solved after installing the update Cubase Pro 8.0.10.
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Jamstix & Cubase
Hello, Ralph! Again, I turn to you with a problem. The gist of it is this:
1. Launch JS3.6.1 in Cubase 8.0.10 as Rack Instrument.
2. Run the drum module (tested BFD2, BFD3, BFD ECO, Steinberg Groove Agent 4.2, SSD4) - adjusts them as input Jamstix 3 MIDI Out.
3. Checking - MIDI messages coming from JS3 to another module, and when you click the mouse, and using a MIDI keyboard.
4. loading style - starts playback sequencer DAW - all wonderful, generated JS 3 rhythm play sound of the drum unit (hereinafter vozmem, for example BFD).
5. Next - problem. When you try to click on another track in the DAW playback becomes wrong - lost some blows, the pace becomes arbitrary. Also, when you try to stop the playback DAW - Jamstix continues to work and send messages.
The problem I noticed on two computers:
Both Win7 (one - 32bit, the other 64 bits)
DAW - Cubase 8 Pro and Cubase 8 Elements (version 8.0.10).
That's the same in Cubase 7.5.40 version works without comment.
Please help. JS3 file attached.
https://cloud.mail.ru/public/vq8Zw83hjMcT/rzdlog.txt
1. Launch JS3.6.1 in Cubase 8.0.10 as Rack Instrument.
2. Run the drum module (tested BFD2, BFD3, BFD ECO, Steinberg Groove Agent 4.2, SSD4) - adjusts them as input Jamstix 3 MIDI Out.
3. Checking - MIDI messages coming from JS3 to another module, and when you click the mouse, and using a MIDI keyboard.
4. loading style - starts playback sequencer DAW - all wonderful, generated JS 3 rhythm play sound of the drum unit (hereinafter vozmem, for example BFD).
5. Next - problem. When you try to click on another track in the DAW playback becomes wrong - lost some blows, the pace becomes arbitrary. Also, when you try to stop the playback DAW - Jamstix continues to work and send messages.
The problem I noticed on two computers:
Both Win7 (one - 32bit, the other 64 bits)
DAW - Cubase 8 Pro and Cubase 8 Elements (version 8.0.10).
That's the same in Cubase 7.5.40 version works without comment.
Please help. JS3 file attached.
https://cloud.mail.ru/public/vq8Zw83hjMcT/rzdlog.txt
-
Ralph @ Rayzoon
- Site Admin
- Posts: 5858
- Joined: Wed Jan 02, 2008 6:24 pm
Jamstix & Cubase
Before playing, use task manager to set the priority on 'jamstix.exe' to 'High' and see if that affects the behavior.
Ralph
Rayzoon Technologies LLC
Rayzoon Technologies LLC
Jamstix & Cubase
Jamstix has priority "High" on a different computer. The problem remains. Helped set a priority "in real time".
Jamstix & Cubase
I am a newbie with Jamstix, but so far I have not seen this problem in my Cubase 8.0.10 running on Windows 8.1
I start Cubase as "run as administrator". Have you tried if this makes a difference?
I start Cubase as "run as administrator". Have you tried if this makes a difference?
Jamstix & Cubase
Thanks for the advice. But I always start Cubase and any other DAW as an administrator. As many of the plug-ins require such rights.pumafred_ wrote:I am a newbie with Jamstix, but so far I have not seen this problem in my Cubase 8.0.10 running on Windows 8.1
I start Cubase as "run as administrator". Have you tried if this makes a difference?
Jamstix & Cubase
This hasn't been true in ages, and was only for a very isolated use case.dimapet_3 wrote: But I always start Cubase and any other DAW as an administrator. As many of the plug-ins require such rights.