BrainModular

Hello Usiners

Did you ever had some problems with remote?
I use Usine with a JLCooper MSC3800 controler (I was using that with my Pyramix), MIDI link with MOTU 828mk2. Everything looks good (possibility to have 1280 rotary buttons learnable with Usine, too much for my brain!!).
Usually, Usine remotes verywell the motorised faders. But sometime not. I use the conductor linked with time code to the sequencer.
SometimesI load a workspace and it was not remoted, if I reload it it's OK. Sometimes I'm going to next marker, the conductor is changing and the remote is not working, it was working ten time before and ten time after. But not during the show on monday!!!!!

So I don't know if the problem comes from Usine or from my controler. Some ideas around there?

Thanks

Sylvain

P.S.: for Olivier, I'm thinking of something better for mixer's snapshots closed to the sequencer, I think my way with the conductor and the time code is not as good as it seems....

This kind of issue use to happen on my system, without to really understand why:
is it a usine pb ? a driver pb in high cpu load situation?

on the dashboard there is a 'U' (update) button made to force the remote to update.

so if it happen again, pressing this button will probably do a good job?

P.S.: for Olivier, I'm thinking of something better for mixer's snapshots closed to the sequencer, I think my way with the conductor and the time code is not as good as it seems....

I'll create a new field in the conductor panel to be able to assign a line to a marker instead the smpte code.
for example say that a particular snapshot will be called when the time line reach a particular marker.

Thanks for answer
Your idea could be good
Another problem I have with the Smpte, it is not enough precise regarding to different tempo.
And sometime, didn't know where to put the remote with loop : if you have a loop and put the remote at the beginning, at each loop, Usine remote the controler, or sometimes it remote the next snapshot puted at the next marker.
I fact, I don't find for know the good way. If you implement this new field, is it possible to think about updating remote just the first time in case of a loop?
Regards
Sylvain

well, well,
there is no evolution of the conductor since the version 2.0.
maybe it's time adapt the conductor to new usine features...

The main problem is that the conductor is not recalled in realtime but in a slower thread to avoid hi cpu load (and clicks). So the recall precision is around 0.1 second.