It seems like the jack transport doesn’t play until you play something in the sequencer, preventing sooperlooper from working at startup, is there a way to work around this? Is there possibly a way I can force it to play a midi file when it starts for instance?
That is probably best reported as a bug.
The webconf has a handy button for that, as it’s helpful to file info for events in a structured way, and that button does it…
The snapshot last state is the instance that is loaded on start up and I’ve used this to start up audio events from the zynsampler, I’m pretty sure I’ve done similar with the sequence for bells but couldn’t put my hand on it.
But that’s not probably not the best or indeed least brittle way of doing this…
How are you operating your MIDI transport control infrastructure?
What do you use as a Master device?
I’ve got a simple midi controller plugged in at the moment, it’s an APC25, to my knowledge it doesn’t provide any clock over usb, as for my audio interface thats on it right now, it’s an m-audio, it doesn’t have midi ports.
I’ve set zynthians clock to internal and internal send to test, it didn’t make a difference to this, the clock, metronome, and jack transport starts when something plays however, indicating that I can work around this by playing something on startup.
I noticed for instance the metronome only started after playing something from the sequencer or a midi file, then sooperlooper would work in its sync2clock preset, so my thoughts was maybe I could just trigger a blank midi file or something
You’re right that once I know exactly whats going on a bug report is appropriate, I was hoping to include a description of my workaround in the bug report
Yep, that’s certainly something it suggests.
As with any repeated task it develops in the use. I occasionally manage to submit something that’s half readable…
what I noticed is that sending jack transport a play command via cli didn’t work, zynthian stops it as soon as it starts, so I have to play nice with the python scripts
I’ll dig around a bit, there might be a way I can trigger it easily
We currently use jack transport for sequences and midi playback sync. So starting a sequence will start the transport and, when all clients that have started it have subsequently requested a stop, the transport will stop.
However, you don’t need jack transport running for sooperlooper to work, and indeed, using the “default” preset, the sync setting is set to loop 1 so it just works.
You can choose what source sooperlooper syncs to. There is a parameter exposed in zynthian.
is there a way I can perhaps trigger a midi playback or a sequencer playback on start using the cli? can they be started via osc?
I normally have sooperlooper running on startup. Chosing default preset instead of syn2clock will do the trick. You can also adjust the sync parameters in sooperlooper and they wiill be saved/restored with the snapshot.
Regards
1 Like
Yes and no. I mean, we have not implemented this but you could have a script to do it by sending CUIA via OSC or MIDI. The script should be run after the UI is totally up. You could monitor the UI log from your script and await the right moment to send the CUIA. Sending CUIA via MIDI and OSC is documented in the wiki.
Anyway, this could be a interesting feature to add. Please, open a feature request for It in our tracking system.
Regards
1 Like
send_osc 1370 /cuia/reboot
works
send_osc 1370 /cuia/start_audio_play
works
but
send_osc 1370 /cuia/start_midi_play
doesnt appear to work
should I be logging this as a bug?
No. It’s a feature request.
alright, so starting midi play over osc not working yet is normal, its just not implemented yet?
I saw the name in the documentation was expecting it to work
send_osc 1370 /cuia/start_midi_play
is what I was expecting to start the midi playback
so starting midi playback from the keyboard shortcut also fails… but starting it from the tempo screen succeeds…