benkuper / chataigne Goto Github PK

I don’t know if there is a link with crash with script but since I have crash, the condition of state don’t save there value.
For example, if I have a condition of a value state_1_1 to have to be at 4, it return to 0 when I launch the program

Hello Ben. I hope you are fine. I will use chataigne for a show saturday. So I tcheck the new version 1.4.1 and I have a little problem with this version.
The mapping activated send continuously data, even if the controller who manage this variable is inactif and nothing is send. It wasn't like this before. Is it normal?

Hi there! I'm willing to use your lovely software for a bunch of projects and just started playing with it.
My first impression on a 1080p screen was that the font size (+ windows controls) is quite large, see the screenshot. Any particular reason for that? Could it be reduced a bit?
Thanks.

Hello I have shown chataigne during a workshop with digital animator to give to us solution to control music.
One of the animateur have installed chataigne on linux 64 bit. It works fine but it had no command to close the software or minimize it.
The only way is to use alt+tab to navigate in another softwate or alt+f4 to quit.

The combo box displays "Choose an audio module" but is disabled, and no audio is played if a audio file is loaded.

ip for osc input is not selectable, only port

It occur when doing a "Mapping" inside a "State Machine". When reloading the project the "Convert-to-int" is replaced by a "Convert-to-String" module.
In Chataigne 1.6.0

Specifically the Projucer part. This would allow Chataigne to be packaged for Arch Linux.

When loading a file, if parameter expressions evaluate before everything is setup, they get an error an deactivate their timers. Expressions should be evaluated after engine loading.

This would make the build easier.

this is the case on all mac os builds, will test on raspberry pi and windows

Salut Ben c'est Manu (Londres)
Je viens de voir un probleme avec la derniere version qui ne se connecte plus sur le port IAC du mac. Le port est bien affiché mais les voyants OUT ne s'eclairent pas.
J'ai réinstallé la version précédente et c'est revenu.

Bise

Emmanuel

Hello Ben. It's been a long time I didn't had variable in my different module so I don't know if this problem is with the new release or if it come long time ago.
When I want to add a variable on my module LGML with auto-add, is different of the old variable. The variable is with a minimum and maximum at 0, the variable in the inspector of the module is little bit transparent and when I put a condition on it, even I change the maximum and minimum, the condition don't care about my variable.

I join you the files of my project. To experiment the bug, you just have to had a variable mute from LGML with auto-add. I have added .txt on files because the extentions of LGML et Chataigne can't be uploaded.

adopo-center-openstage-1.2.15 copie.noisette.txt
Black Looper 6 copie.lgml.txt

have worked around by always using non zero presets
this is the case on all mac os builds , will test same on rasberry pi and windows

instant crash when trying to record a 2D value (Osc input)

hi Ben
nice new version. just found an easy to repair but annoying issue.
router modules are not saved (or maybe just read and update) correctly in 1.3.10.
it keeps the modules in each router, with the right notes to route, but doesn't keep custom name, type, channel nor pitch/number

seen on a file created with an older version, app updated via the new update feature, bug appeared.
tried to create a new file from scratch, same problem

cheers bro

Is it possible to create a bridge, using wilcards, ranges an basic logic, like if/then/else?
Does is support sysex commands?

Chataigne 1.2.13

State machine (visual) size don't get saved when saving then opening a project

Chataigne 1.5.2 / MacBook Pro 13" mid-2012 / Mojave OSX 10.14.1 up to date
Open chataigne -> clic on State Machine Area -> press spacebar -> crash

Replication :

• Launch Chataigne (win64 1.0.1)
• create timeline
• random clics (had one crash on clic timeline, one on clicing empty space)

-> Crash

-> hard to replicate

When you put a midi value for the exit of a mapping, it’s not possible to use the entry for mapping

Hi @benkuper, thanks for making this interesting application available as an AppImage for Linux. Currently it is missing a library which should (along with its dependencies) be bundled inside the AppImage:

Chataigne: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory

Reference:
AppImage/appimage.github.io#2020

Timeline > Trigger (Text) > Korean font write

The procedure entry point MapViewOffileFromApp couldnot be located in the dynamic link library Kernel32.dll

http://benjamin.kuperberg.fr/chataigne/forum/d/14-a-propos-des-s-quences/2

Chataigne 1.5.2 / midi input APC40 / midi ouput loopmidi
MIDI module output sends note instead of channels and values instead of notes
SEND Channel 2 / note 53 / value 127
RECEIVE in external midi monitor : Channel 53 / note 127 / value 1

same test done on an old chataigne 1.3.10 on the same computer and same monitor, it works well

Hello Ben. Since the release 1.4.3, I can't open my project. I put with this post the file.

adopo-center-openstage update.noisette.txt

When initially adding an audio layer clip to a sequence, the position is not saved during project save or undo unless a mouse drag event performed.

The JACK system (along with the LV2 plugin format) has support for passing audio rate parameter control "CV" signals between apps (and plugins) for uses including gate/triggers and modulation.

This port type ("CV" in JACK, "CVPort" in LV2) has more recently started seeing support in various software projects. More details on the subject can be found on this post.

Might this be something Chataigne could get support for?

Hello Ben. I hope you are fine.

There is a bug in chataigne. The OSC message in float can be just between 0 and 1. But I have a program who have to communicate with chataigne. But this program send only float and can send numbers superior of 1.
For example in the other program I have a switch who send value in float and this value can be 1 and 2. And Chataigne don't like this. The condition in state are lost when I ask for exemple to be validate if value is superior of 1, I can't put valeur equal 2. Sometimes the value of OSC in module when chataigne receive it is 2 but after can be superior of 1. And when I whant to delete the value, chataigne crash.

When opening a .noisette file which contains an "play at load" Sequence the sequence get triggered correctly but not its content.

Tested with having triggers launching some application with the OS Module.

When launching the .noisette file, the sequence plays but the trigger starting the app don't work.
When clicking on Play on the sequence, it works.

Hello Ben I hope you are fine. It's been a long time. I just put a little issue because I have seen a little bug in chataigne.

When you define a wiimote in a value condition in action, if you select + button he select - button. So there is no way to select - button.

Big up for your software. I met à song ingineer in belgium and he knew it. Lot of people had ever eared about chataigne. It's cool !

When a mapping is create and there is an entry if the state is delete, chataigne crash

When mapping values in a module routeur to a MIDI channel, the default value is Control Change. A dropdown needs 2 clics and 1 move. Mapping 60 informations to notes means 180 clic and moves :)

It could be better in one of the following way :

• allow multiple change : select multiple lines, open one of their dropdown, change applied to all
• change defaults preferences : allow to set default to either control change OR note on OR note off
• replace dropdown with a radiobuttons form. (not the best one, but already better)

thanks !!

Hello,
when i run Chataigne on linux Mint 19.2 :

~/Bureau$ ./Chataigne-linux-x64-1.6.9b3.AppImage

Chataigne: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory

Maybe something missing...
Thank you!

Hello!

First, the soft seems nice, but I cannot see any of my network interfaces in a DMX module with artnet.

I'm running macos mojave (hackintosh), and I can see my usb c ethernet adapter and send artnet with madmapper or vezér.

Regards

Hello,
I get a segfault crash when I try to create a Command Template for OSC modules that have been renamed.

Steps to reproduce :

• create an OSC module
• rename it
• create a Command Template

It only happens for OSC modules, and only after they have been renamed.

Backtrace :

#0 0x000055555572f930 in juce::HeapBlock<CommandDefinition*, false>::operator CommandDefinition** (this=0x668)
at /home/tom/JUCE/modules/juce_core/memory/juce_HeapBlock.h:155
#1 0x00005555557321a0 in juce::OwnedArray<CommandDefinition, juce::DummyCriticalSection>::begin (this=0x668)
at /home/tom/JUCE/modules/juce_core/containers/juce_OwnedArray.h:218
#2 0x0000555555956ebd in Module::getCommands (this=0x0, includeTemplateCommands=false)
at ../../Source/Module/Module.cpp:95
#3 0x000055555572d6a3 in CommandTemplate::CommandTemplate (this=0x555556d59170, params=...)
at ../../Source/Common/Command/Template/CommandTemplate.cpp:47
#4 0x0000555555731750 in CommandTemplate::create (params=...)
at ../../Source/Common/Command/Template/CommandTemplate.h:60
#5 0x0000555555733487 in std::_Function_handler<CommandTemplate* (juce::var), CommandTemplate* ()(juce::var)>::_M_invoke(std::_Any_data const&, juce::var&&) (__functor=..., __args#0=...)
at /usr/include/c++/8.1.1/bits/std_function.h:282
#6 0x0000555555723fff in std::function<CommandTemplate (juce::var)>::operator()(juce::var) const (
this=0x555556d305f0, __args#0=...) at /usr/include/c++/8.1.1/bits/std_function.h:687
#7 0x0000555555722b9d in Factory::create (this=0x555556d136d8, type=...)
at ../../../JUCE Modules/juce_organicui/manager/Factory.h:122
#8 0x000055555572142e in Factory::createFromMenuResult (this=0x555556d136d8, result=1)
at ../../../JUCE Modules/juce_organicui/manager/Factory.h:113
#9 0x000055555571fd8a in Factory::showCreateMenu (this=0x555556d136d8)
at ../../../JUCE Modules/juce_organicui/manager/Factory.h:98
#10 0x000055555571cf22 in BaseManagerUI<CommandTemplateManager, CommandTemplate, BaseItemUI >::showMenuAndAddItem (this=0x555556d324f0, isFromAddButton=true, mouseDownPos=...)
at ../../../JUCE Modules/juce_organicui/manager/ui/BaseManagerUI.h:524
#11 0x000055555571de04 in BaseManagerUI<CommandTemplateManager, CommandTemplate, BaseItemUI >::buttonClicked (this=0x555556d324f0, b=0x555556d36f50)
at ../../../JUCE Modules/juce_organicui/manager/ui/BaseManagerUI.h:743
#12 0x0000555555dbcfd9 in juce::Button::<lambda(juce::Button::Listener&)>::operator()(juce::Button::Listener &) const (__closure=0x7fffffffd790, l=...) at /home/tom/JUCE/modules/juce_gui_basics/buttons/juce_Button.cpp:402
#13 0x0000555555e5857a in juce::ListenerList<juce::Button::Listener, juce::Array<juce::Button::Listener*, juce::DummyCriticalSection, 0> >::callChecked<juce::Button::sendClickMessage(const juce::ModifierKeys&)::<lambda(juce::Button::Listener&)>, juce::Component::BailOutChecker>(const juce::Component::BailOutChecker &, juce::Button::<lambda(juce::Button::Listener&)> &&) (this=0x555556d37098, bailOutChecker=..., callback=...)
at /home/tom/JUCE/modules/juce_core/containers/juce_ListenerList.h:153
#14 0x0000555555dbd0dc in juce::Button::sendClickMessage (this=0x555556d36f50, modifiers=...)
at /home/tom/JUCE/modules/juce_gui_basics/buttons/juce_Button.cpp:402
#15 0x0000555555dbce86 in juce::Button::internalClickCallback (this=0x555556d36f50, modifiers=...)
at /home/tom/JUCE/modules/juce_gui_basics/buttons/juce_Button.cpp:351
#16 0x0000555555dbd526 in juce::Button::mouseUp (this=0x555556d36f50, e=...)
at /home/tom/JUCE/modules/juce_gui_basics/buttons/juce_Button.cpp:471
#17 0x0000555555db19d8 in juce::Component::internalMouseUp (this=0x555556d36f50, source=..., relativePos=...,
time=..., oldModifiers=..., pressure=0, orientation=0, rotation=0, tiltX=0, tiltY=0)
at /home/tom/JUCE/modules/juce_gui_basics/components/juce_Component.cpp:2383
#18 0x0000555555e691de in juce::MouseInputSourceInternal::sendMouseUp (this=0x555556b04c50, comp=...,
screenPos=..., time=..., oldMods=...)
at /home/tom/JUCE/modules/juce_gui_basics/mouse/juce_MouseInputSource.cpp:155
---Type to continue, or q to quit---
#19 0x0000555555e69660 in juce::MouseInputSourceInternal::setButtons (this=0x555556b04c50, screenPos=...,
time=..., newButtonState=...) at /home/tom/JUCE/modules/juce_gui_basics/mouse/juce_MouseInputSource.cpp:197
#20 0x0000555555e6a265 in juce::MouseInputSourceInternal::handleEvent (this=0x555556b04c50, newPeer=...,
positionWithinPeer=..., time=..., newMods=..., newPressure=0, newOrientation=0, pen=...)
at /home/tom/JUCE/modules/juce_gui_basics/mouse/juce_MouseInputSource.cpp:331
#21 0x0000555555db4a09 in juce::MouseInputSource::handleEvent (this=0x7fffffffdc30, peer=..., pos=...,
time=1529315697282, mods=..., pressure=0, orientation=0, penDetails=...)
at /home/tom/JUCE/modules/juce_gui_basics/mouse/juce_MouseInputSource.cpp:631
#22 0x0000555555e42232 in juce::ComponentPeer::handleMouseEvent (this=0x555556b3e0f0,
type=juce::MouseInputSource::mouse, pos=..., newMods=..., newPressure=0, newOrientation=0,
time=1529315697282, pen=..., touchIndex=0)
at /home/tom/JUCE/modules/juce_gui_basics/windows/juce_ComponentPeer.cpp:88
#23 0x0000555555ea9ceb in juce::LinuxComponentPeer::handleButtonReleaseEvent (this=0x555556b3e0f0,
buttonRelEvent=...) at /home/tom/JUCE/modules/juce_gui_basics/native/juce_linux_X11_Windowing.cpp:2292
#24 0x0000555555ea8e76 in juce::LinuxComponentPeer::handleWindowMessage (this=0x555556b3e0f0, event=...)
at /home/tom/JUCE/modules/juce_gui_basics/native/juce_linux_X11_Windowing.cpp:2018
#25 0x0000555555e54bb5 in juce::WindowingHelpers::windowMessageReceive (event=...)
at /home/tom/JUCE/modules/juce_gui_basics/native/juce_linux_X11_Windowing.cpp:3775
#26 0x0000555555e52c6e in juce::XWindowSystem::<lambda(int)>::operator()(int) const (__closure=0x555556b61fc0)
at /home/tom/JUCE/modules/juce_gui_basics/native/juce_linux_X11.cpp:217
#27 0x0000555555e63fd4 in juce::LinuxEventLoop::CallbackFunction<juce::XWindowSystem::initialiseXDisplay()::<lambda(int)> >::operator()(int) (this=0x555556b61fb0, fd=6)
at /home/tom/JUCE/modules/juce_events/native/juce_linux_EventLoop.h:42
#28 0x0000555555cbcd13 in juce::InternalMessageQueue::dispatchNextEvent (this=0x555556b03e50)
at /home/tom/JUCE/modules/juce_events/native/juce_linux_Messaging.cpp:121
#29 0x0000555555cb9c90 in juce::MessageManager::dispatchNextMessageOnSystemQueue (
returnIfNoPendingMessages=false) at /home/tom/JUCE/modules/juce_events/native/juce_linux_Messaging.cpp:237
#30 0x0000555555cb5b8b in juce::MessageManager::runDispatchLoop (this=0x555556b03de0)
at /home/tom/JUCE/modules/juce_events/messages/juce_MessageManager.cpp:128
#31 0x0000555555cb4fee in juce::JUCEApplicationBase::main ()
at /home/tom/JUCE/modules/juce_events/messages/juce_ApplicationBase.cpp:262
#32 0x0000555555cb4ef0 in juce::JUCEApplicationBase::main (argc=1, argv=0x7fffffffe058)
at /home/tom/JUCE/modules/juce_events/messages/juce_ApplicationBase.cpp:240
#33 0x0000555555a97e23 in main (argc=1, argv=0x7fffffffe058) at ../../Source/Main.h:36

Hello I have a problem with message OSC. I think is a bug.

I have an ipad with 2 toggles. When the first toggle is activated, chataigne have to activate the second one but the second one don't have to send message. This is ok.

But when I want to desactivate the second toggle, for chataigne, is already desactivate. So the condition on my state isn't activated...
I have some difficulties to explain this problem in english. I hope you understand what I want to say

Replication procedure :

• launch Chataigne (win64 1.0.1)
• Add osc module
• Add command test
• Add two int arguments
• Change receive port to 9000
• Trigger command

-> Crash

Hello Ben. Do you have script function to send midi in module midi like send() on module osc?

http://benjamin.kuperberg.fr/chataigne/forum/d/14-a-propos-des-s-quences/2

Je me suis remis à bosser mon projet et je me suis rendu compte qu'un gros bus est apparu sur la dernière version. J'ai retesté la 1.2.10 le bug n'y est pas. On ne peut plus activer de routage dans le module routeur. Les cases à cocher ne sont plus présente plus aucun message ne peut passer par le module routeur