I think that considering the scope of the problem, that not testing with 0.9.1 is OK.
I do not know much about super colliders, pds, keykits and all the like. I'm more of a regular audio plugin/DAW type. So the first thing I'm interested in is what can Architect bring to the creative process, eg. how it can augment it and offer possibilities. As such I start at page 1 of the quick start guide and follow along, while at times adding other instruments I'm used with in regular work flows.
And so I started with the mono sequencer. When I got a simple sequence going I thought of adding a drum machine, a sequencer, a synth. It did not went very far though. Hence, I hope this bug report is concise enough to describe this very repeatable problem.
A side problem to this, which could have its own bug report, is that the Architect UI will not always show up when launched. Like for the past 5 or 6 times it is impossible to see the UI. Please find all environment details below related to the main problem. Let me know if things are missing. - Cheers.
Code: Select all
Problem
Audio crash when the Architect UI is brought back into view
after being minimized only when playing along a Windows VST. It does
not matter if the Windows VST is a sequencer or a synth.
Environment
Linux Mint 18 KDE
Bitwig 2.4.3
jackd 1.9.10+20150825git1ed50c92~dfsg-1ubuntu1
Plugins
Track 1: Architect 0.9.0 64-bit, StringVST
Track 2: Sonic Charge Microtonic (Windows VST run using linvst and
wine-staging) current version
Track 2 variation: Melda Production MDrummer (Windows VST run using
linvst and wine-staging) current version
Track 2 variation: Monoplug B-Step2 sequencer (native Linux)
current version
Track 2 variation: Tone2 Ray Blaster IMS synth (Windows VST)
Reproducible
always
Background
All Windows VST can play along with all Linux VST plugins in any
combination whatsover.
Note
For test purposes, jackd can be launched within a console which makes
it easy to see when it crashes. Command lime used for a M-Audio
1010LT audio card:
/usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:M1010LT -r44100 -p512 -n8
Steps (see also variations 1 to 5)
1) Put Architect on a track
2) Add a mono sequencer and write 8 notes
3) Resize total bar to 8 bars
4) Add MIDI output to host and link to sequencer
5) Add StringVST to track
6) Press play button in Bitwig
Result: Sequence loops using a StringVST sound
7) Minimize Architect by clicking on the X right-hand corner of its
window
8) Create another track
9) Add Sonic Charge Microtonic drum machine
Result: Microtonic will start playing automatically using a default
pattern
Result: Both Architect and Microtonic are playing
10) Minimize Microtonic
11) Bring back Architect by clicking on its Bitwig device panel
interface icon.
Result: jackd audio crash. Bitwig process has to be killed
Variation 1 (also happens every time)
To minimize Architect, use the down arrow button in the right hand
corner of its window instead of the X
Result: Adding Microtonic will not work, audio will crash
immediately after double-clicking on Microtonic to load it.
Variation 2 (also happens every time)
As before, but do not minimize Architect at all
Result: As in variation 1
Variation 3 (also happens every time)
As before, but instead of Microtonic, use Melda Production MDrummer:
1) Minimize Architect using the X button
2) Create another track, put MDrummer
3) Load a drumset, load a rhythm, press play
Result: Both Architect and MDrummer are playing
4) Bring back Architect to view as before
Result: audio crash, Bitwig needs to be manually terminated.
Variation 4
As before but instead of using a Windows VST sequencer use a Windows
VST soft synth such as Tone2's Ray Blaster IMS.
Result: audio crash
Variation 5
As before but instead of Microtonic use Monoplug's B-Step2 sequencer
(native Linux)
1) Minimize Architect window by clicking on the X
2) Create another track, add B-Step2 sequencer
3) Put a few notes in B-Step2
4) Add StringVST to the track
Result: Both Architect and B-Step2 are playing
5) Bring back Architect into view
Result: no crash
