Bug'n'buzz OSC ports :
Sooperlooper receive : 9951
osc_sooperlooper_test.py : 192.168.1.108000
Ardour receive : 3819
X-OSC : 192.168.1.30:9000
Old Bitwig receive : 8175 Bitwig send : 8176
License: GNU General Public License v3.0
Bug'n'buzz OSC ports :
Sooperlooper receive : 9951
osc_sooperlooper_test.py : 192.168.1.108000
Ardour receive : 3819
X-OSC : 192.168.1.30:9000
Old Bitwig receive : 8175 Bitwig send : 8176
L'organisation des tracks en banks via OSC4Bitwig, et l'acces aux tracks filles d'un groupe rendent difficile les acces directs aux parametres. Est-t-il envisageable de créer un controller script complet, sans tout recommencer de zero ?
Trouver un moyen de générer une suite de notes
Tester l'état avant d'envoyer un pause
Ce qui entraine la suppression des routages sur Ardour.
Sur le mac :
$osc_sooperlooper_test.py
Traceback (most recent call last):
File "./osc_sooperlooper_test.py", line 155, in
server = MyServer()
File "./osc_sooperlooper_test.py", line 36, in init
self.stdscr.addstr(24,0," stop ",curses.A_REVERSE)
_curses.error: addstr() returned ERR
Tout fonctionnais bien jusqu'à ce que je le lance via Session.sh, et maintenant j'ai cette erreur quelque soit la façon dont je lance osc_sooperlooper_test.py
Mais pas de problèmes quand lancé en ssh dans un term depuis ma machine.
Lors de l'arrêt, on doit sauver et arrêter Ardour avant de quitter NSM sinon on perd le routage.
Peut être parce que SL quitte un peu avant Ardour qui deconnecte SL et sauve ensuite.
Pour éviter le plantage
Impossible de retrouver comment ca fonctionne...
The argument sent by send(self.ardour, ard_path, track, arg) seem to be a int when arg is a tupple (plugins control).
Bonjour,
Je cherche à joindre wargreen (vu que le site du bib est hs, je suppose que les adresses mails en @bib ne fonctionnent plus non plus).
Vous pouvez me joindre à : [email protected]
Merci d'avance ! (et désolée pour le dérangement)
Et empeche la fermeture de la session
osc_sooperlooper_test eat 1 CPU at 100%
Le temps de réponse du X-OSC n'est vraiment pas stable :
mac (filaire) -> box -> xosc
MacBook-Pro-de-cie:~ cieconcordance$ ping 192.168.0.30
PING 192.168.0.30 (192.168.0.30): 56 data bytes
64 bytes from 192.168.0.30: icmp_seq=0 ttl=100 time=19.432 ms
64 bytes from 192.168.0.30: icmp_seq=1 ttl=100 time=9.515 ms
64 bytes from 192.168.0.30: icmp_seq=2 ttl=100 time=7.608 ms
Request timeout for icmp_seq 3
64 bytes from 192.168.0.30: icmp_seq=4 ttl=100 time=7.036 ms
64 bytes from 192.168.0.30: icmp_seq=5 ttl=100 time=15.969 ms
64 bytes from 192.168.0.30: icmp_seq=6 ttl=100 time=6.276 ms
64 bytes from 192.168.0.30: icmp_seq=7 ttl=100 time=6.220 ms
64 bytes from 192.168.0.30: icmp_seq=8 ttl=100 time=7.344 ms
64 bytes from 192.168.0.30: icmp_seq=9 ttl=100 time=12.715 ms
64 bytes from 192.168.0.30: icmp_seq=10 ttl=100 time=6.993 ms
64 bytes from 192.168.0.30: icmp_seq=11 ttl=100 time=5.867 ms
64 bytes from 192.168.0.30: icmp_seq=12 ttl=100 time=8.013 ms
64 bytes from 192.168.0.30: icmp_seq=13 ttl=100 time=9.732 ms
64 bytes from 192.168.0.30: icmp_seq=14 ttl=100 time=15.242 ms
64 bytes from 192.168.0.30: icmp_seq=15 ttl=100 time=6.940 ms
64 bytes from 192.168.0.30: icmp_seq=16 ttl=100 time=5.876 ms
64 bytes from 192.168.0.30: icmp_seq=17 ttl=100 time=8.007 ms
64 bytes from 192.168.0.30: icmp_seq=18 ttl=100 time=17.364 ms
64 bytes from 192.168.0.30: icmp_seq=19 ttl=100 time=6.178 ms
64 bytes from 192.168.0.30: icmp_seq=20 ttl=100 time=5.883 ms
64 bytes from 192.168.0.30: icmp_seq=21 ttl=100 time=6.288 ms
64 bytes from 192.168.0.30: icmp_seq=22 ttl=100 time=7.813 ms
64 bytes from 192.168.0.30: icmp_seq=23 ttl=100 time=18.099 ms
64 bytes from 192.168.0.30: icmp_seq=24 ttl=100 time=6.031 ms
64 bytes from 192.168.0.30: icmp_seq=25 ttl=100 time=7.796 ms
64 bytes from 192.168.0.30: icmp_seq=26 ttl=100 time=8.143 ms
64 bytes from 192.168.0.30: icmp_seq=27 ttl=100 time=9.551 ms
64 bytes from 192.168.0.30: icmp_seq=28 ttl=100 time=8.504 ms
64 bytes from 192.168.0.30: icmp_seq=29 ttl=100 time=5.955 ms
64 bytes from 192.168.0.30: icmp_seq=30 ttl=100 time=9.045 ms
64 bytes from 192.168.0.30: icmp_seq=31 ttl=100 time=12.328 ms
64 bytes from 192.168.0.30: icmp_seq=32 ttl=100 time=16.918 ms
64 bytes from 192.168.0.30: icmp_seq=33 ttl=100 time=7.560 ms
64 bytes from 192.168.0.30: icmp_seq=34 ttl=100 time=7.692 ms
64 bytes from 192.168.0.30: icmp_seq=35 ttl=100 time=5.970 ms
64 bytes from 192.168.0.30: icmp_seq=36 ttl=100 time=9.531 ms
64 bytes from 192.168.0.30: icmp_seq=37 ttl=100 time=8.428 ms
64 bytes from 192.168.0.30: icmp_seq=38 ttl=100 time=8.679 ms
64 bytes from 192.168.0.30: icmp_seq=39 ttl=100 time=7.720 ms
64 bytes from 192.168.0.30: icmp_seq=40 ttl=100 time=8.106 ms
64 bytes from 192.168.0.30: icmp_seq=41 ttl=100 time=15.015 ms
64 bytes from 192.168.0.30: icmp_seq=42 ttl=100 time=8.068 ms
64 bytes from 192.168.0.30: icmp_seq=43 ttl=100 time=5.897 ms
64 bytes from 192.168.0.30: icmp_seq=44 ttl=100 time=6.198 ms
64 bytes from 192.168.0.30: icmp_seq=45 ttl=100 time=10.284 ms
64 bytes from 192.168.0.30: icmp_seq=46 ttl=100 time=6.743 ms
64 bytes from 192.168.0.30: icmp_seq=47 ttl=100 time=8.164 ms
64 bytes from 192.168.0.30: icmp_seq=48 ttl=100 time=6.151 ms
64 bytes from 192.168.0.30: icmp_seq=49 ttl=100 time=10.333 ms
64 bytes from 192.168.0.30: icmp_seq=50 ttl=100 time=18.987 ms
64 bytes from 192.168.0.30: icmp_seq=51 ttl=100 time=7.805 ms
64 bytes from 192.168.0.30: icmp_seq=52 ttl=100 time=16.858 ms
64 bytes from 192.168.0.30: icmp_seq=53 ttl=100 time=9.503 ms
64 bytes from 192.168.0.30: icmp_seq=54 ttl=100 time=18.327 ms
^C
--- 192.168.0.30 ping statistics ---
55 packets transmitted, 54 packets received, 1.8% packet loss
round-trip min/avg/max/stddev = 5.867/9.569/19.432/3.988 ms
mac (wifi) -> box :
MacBook-Pro-de-cie:~ cieconcordance$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=4.159 ms
Request timeout for icmp_seq 1
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.216 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.748 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.401 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=7.034 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1.375 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1.621 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=1.815 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=2.240 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=1.284 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.315 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.138 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.965 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=11.568 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.441 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2.480 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=1.514 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=5.195 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=4.712 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=1.169 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1.238 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=1.229 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=13.251 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=2.196 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=2.197 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=1.226 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=5.441 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=1.278 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=1.770 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=1.198 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=1.207 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=1.443 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=1.145 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=1.707 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=23.158 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=9.995 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=1.248 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=2.130 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=1.794 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=2.028 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=26.117 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=1.597 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=1.202 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=1.244 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=23.152 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=1.286 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=1.143 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=1.702 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=5.949 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=2.471 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=2.488 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=3.341 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=3.007 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=2.800 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=9.753 ms
64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=2.415 ms
64 bytes from 192.168.0.1: icmp_seq=57 ttl=64 time=2.375 ms
64 bytes from 192.168.0.1: icmp_seq=58 ttl=64 time=9.548 ms
64 bytes from 192.168.0.1: icmp_seq=59 ttl=64 time=1.450 ms
64 bytes from 192.168.0.1: icmp_seq=60 ttl=64 time=1.238 ms
64 bytes from 192.168.0.1: icmp_seq=61 ttl=64 time=1.240 ms
64 bytes from 192.168.0.1: icmp_seq=62 ttl=64 time=5.010 ms
64 bytes from 192.168.0.1: icmp_seq=63 ttl=64 time=1.433 ms
^C
--- 192.168.0.1 ping statistics ---
65 packets transmitted, 64 packets received, 1.5% packet loss
round-trip min/avg/max/stddev = 1.138/3.977/26.117/5.256 ms
Pas des plus stable, mais correct.
Mêmes types de pic de latences depuis la tablette vers la passerelle. Un WRT reglerais peut-être ça ?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.