Hello,
I'm a new user of Usine, and I think it's a powerful software. I'm sorry because maybe it's the wrong place in this forum to tell you the following issue.
I'm creating a project in order to modulate the parameters or my hardware synth (Ultranova) with my actual gestures (with the Myo armband).
For the moment, everything's fine (I created a script, I routed some modules, etc.), but I have ONE BIG ISSUE which destroys all of my work : sometimes, the GUI freezes suddenly, and in the same time, the Trace window pops up and is totally blank. I could do nothing but quit Usine. It's not an actual freeze since I can save my project with ctrl+S command. Usine receives the keyboard commands, but I can't click anymore on any device or anything else you could imagine (options, windows...).
It's very odd and I'm frustrated because it involves that it's not usable in a live situation.
The "bug" is very irregular. In this example (Usine GUI bug), it's when I double click on a Change Scale module, and the next time, it's probably something else that will cause the bug.
Does the problem could come from my video card (GTX960M) ? Or from a DPI parameter of windows 10 ?
In any case, it is not related to the script or the OSC
Is there a kind of log that Usine generates in order to know what exactly happens?
I really don't know. Another thing, not connected to Usine, but that could be related to this problem : every bridged plugin window is blank in Ableton Live x64.
Configuration : MSI GE62 6QD, Windows 10 x64 anniversary edition, Usine 2.0.084a x64.
My project is here : Usine project with GUI problem
Sorry for my english.
I hope someone can help me.
Bye,
Cyril.
GUI freeze with my project
played for a while with workspace and couldn't reproduce here, script seems ok ,the thing that differs is i don't get OSC messages as not having the hardware, how can you be sure it's not comming from osc?
same here, nothing special in your patch which can result a bug, but as 23FX say, can be the OSC, specially if there is a overflow of messages ?
have you test different block size value in the setup/audio tab ?
have you test different block size value in the setup/audio tab ?
If you use more than one osc receive module with thé same adress that coule happen.
I'll suggest that all OSC receive module are placed in a device instead of directly inside a patch.
Use busses from device To patches
I'll suggest that all OSC receive module are placed in a device instead of directly inside a patch.
Use busses from device To patches
http://oli-lab.org
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Hello,
thank you for helping me.
As you say, it's probably the OSC that causes the problem.
It is strange : when DSP is off, the freeze happens, but when the OSC is disabled (in the preferences) there is no freeze anymore. And it is not related to the OSC device, because it freezes even if it switched off. So, it cannot be an overflow (there is no flow when DSP and the device are off).
I don't know how to put the OSC lister (the only OSC module) in the device panel. The "where" section is not showed when I select this module.
A member of Senso suggested me to put a Clock module in order to filter the quantity of received messages. I just have to find out how to put this Clock right after the OSC Lister and without losing the data coming to the Change Scale modules or the Script itself.
I will try to find in which cases precisely the freeze comes (DSP on/off, OSC enabled/disabled, hardware on/off, OSC lister present/removed, etc.) and I will post the table.
Thank you.
thank you for helping me.
As you say, it's probably the OSC that causes the problem.
It is strange : when DSP is off, the freeze happens, but when the OSC is disabled (in the preferences) there is no freeze anymore. And it is not related to the OSC device, because it freezes even if it switched off. So, it cannot be an overflow (there is no flow when DSP and the device are off).
I don't know how to put the OSC lister (the only OSC module) in the device panel. The "where" section is not showed when I select this module.
A member of Senso suggested me to put a Clock module in order to filter the quantity of received messages. I just have to find out how to put this Clock right after the OSC Lister and without losing the data coming to the Change Scale modules or the Script itself.
I will try to find in which cases precisely the freeze comes (DSP on/off, OSC enabled/disabled, hardware on/off, OSC lister present/removed, etc.) and I will post the table.
Thank you.
hi !
there is no gui for OSC receive module, so no "where" option
try the device trick by putting the osc lister in a device
and also check the port numbers :
the Usine OSC listen port should be different from any other port that send OSC from Usine. and different from the artnet port and chart port if any
there is no gui for OSC receive module, so no "where" option
try the device trick by putting the osc lister in a device
and also check the port numbers :
the Usine OSC listen port should be different from any other port that send OSC from Usine. and different from the artnet port and chart port if any
http://oli-lab.org
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Who is online
Users browsing this forum: No registered users and 14 guests
