Jack Audio & MIDI support for energyXT2 [Linux]

Official support for: energy-xt.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Last edited by OBSOLETE160530 on Tue Jun 14, 2022 10:58 am, edited 2 times in total.

Post

Excellent ! Great job ! I'll give a try as soon as possible.

Just a question, can you post a compiled version on your ubuntu ppa ?

/Fabien

PS : for the 32 bits jack, did you try to compile jack with the mixed mode (32/64 support for 64 bits systems) ?

Post

Last edited by OBSOLETE160530 on Tue Jun 14, 2022 10:58 am, edited 1 time in total.

Post

Last edited by OBSOLETE160530 on Tue Jun 14, 2022 10:58 am, edited 1 time in total.

Post

falkTX wrote:I've updated the source and it doesn't require Jack2 anymore, with also a fix for input midi ports.

Download -> http://sourceforge.net/projects/libaam- ... z/download
Thank you ! Going to try away right now (I wish you included binaries, though.. :)

Post

Last edited by OBSOLETE160530 on Tue Jun 14, 2022 10:58 am, edited 1 time in total.

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
Hi !

First, thank you very much for writing the source code!
I'm using OpenSuse 12.2 64bit, with JACK2.

The problem I'll explain happens on my 64bit OS, but on my 32bit OpenSuse 12.2 laptop, I could compile and enjoy energyXT/libaam.so with JACK2 perfectly.

I can play sounds with all jack applications, except EnergyXT...

I compiled libaam.cpp using "make", and xt2-config as well (by following this : "http://www.timelordz.com/blog/2011/01/c ... on-64-bit/ (http://www.timelordz.com/blog/2011/01/compiling-libaam-so-for-energyxt2-on-64-bit/)")
When I launch eXT, it finds the Jack Server "JACK Audio v1.9.8", shows inputs and outputs as configured with xt2-config, and energyXT appears in Jack-Connect Tab.

All is connected, but energyXT won't play any sound.. (the demo songs seem to play, and volume is at maximum (I also checked the Modular tab))

Here is the output of energyXT in the terminal :

Code: Select all (#)

Jack: JackClient::SetupDriverSync driver sem in flush mode
Jack: JackPosixSemaphore::Connect name = jack_sem.1000_default_energyXT2
Jack: JackPosixSemaphore::Connect sem_getvalue 0
Jack: Clock source : unknown
Jack: JackLibClient::Open name = energyXT2 refnum = 6
Jack: JackClient::PortRegister ref = 6 name = energyXT2:audio_in_ 1 type = 32 bit float mono audio port_index = 30
Jack: JackClient::PortRegister ref = 6 name = energyXT2:audio_in_ 2 type = 32 bit float mono audio port_index = 31
Jack: JackClient::PortRegister ref = 6 name = energyXT2:audio_out_ 1 type = 32 bit float mono audio port_index = 32
Jack: JackClient::PortRegister ref = 6 name = energyXT2:audio_out_ 2 type = 32 bit float mono audio port_index = 33
Jack: JackClient::PortRegister ref = 6 name = energyXT2:midi_in_1 type = 8 bit raw midi port_index = 34
Jack: JackClient::PortRegister ref = 6 name = energyXT2:midi_in_2 type = 8 bit raw midi port_index = 35
Jack: JackClient::Activate
Jack: JackClient::StartThread : period = -2147483648 computation = 5333 constraint = 100
Jack: Create non RT thread
Jack: ThreadHandler: start
Jack: JackClient::kBufferSizeCallback buffer_size = 256
Jack: JackClient::ClientNotify ref = 6 name = energyXT2 notify = 2
Jack: JackClient::kActivateClient name = energyXT2 ref = 6 
Jack: JackClient::ClientNotify ref = 6 name = energyXT2 notify = 18
Jack: JackClient::ClientNotify ref = 6 name = energyXT2 notify = 18
Jack: JackClient::ClientNotify ref = 6 name = energyXT2 notify = 18
Jack: JackClient::ClientNotify ref = 6 name = energyXT2 notify = 18
Jack: JackGraphManager::GetBuffer : port = 30 is released state
Jack: JackGraphManager::GetBuffer : port = 31 is released state
Jack: JackGraphManager::GetBuffer : port = 32 is released state
Jack: JackGraphManager::GetBuffer : port = 33 is released state
Jack: JackGraphManager::GetBuffer : port = 30 is released state
Jack: JackGraphManager::GetBuffer : port = 31 is released state

[...] [u][b][color=red]<-- As long as energyXT is running, this message is appearing (a lot of time)[/color][/b][/u]

Jack: JackGraphManager::GetBuffer : port = 32 is released state
Jack: JackGraphManager::GetBuffer : port = 33 is released state
Jack: JackGraphManager::GetBuffer : port = 30 is released state
Jack: JackGraphManager::GetBuffer : port = 31 is released state
Jack: JackGraphManager::GetBuffer : port = 32 is released state
Jack: JackGraphManager::GetBuffer : port = 33 is released state
Jack: JackGraphManager::GetBuffer : port = 30 is released state
Jack: JackClient::Deactivate [b][u][color=red]<-- When I exit energyXT[/color][/u][/b]
Jack: JackClient::Deactivate res = 0
Jack: JackPosixThread::Kill
Jack: jack_client_close
Jack: JackClient::Close ref = 6
Jack: JackClient::Deactivate
Jack: JackSocketClientChannel::Stop
Jack: JackPosixThread::Kill
Jack: JackClientSocket::Close
Jack: JackClientSocket::Close
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_energyXT2
Jack: JackLibClient::~JackLibClient
Jack: JackShmReadWritePtr1::~JackShmReadWritePtr1 6
Jack: Succeeded in unlocking 384 byte memory area
Jack: JackLibGlobals Destroy ac5d678
Jack: ~JackLibGlobals
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_system
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_freewheel
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_qjackctl
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_rakarrack
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_ardour
Jack: JackPosixSemaphore::Disconnect name = jack_sem.1000_default_exaile.py
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: ThreadHandler: exit
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 1
Jack: Succeeded in unlocking 1040 byte memory area
Jack: JackShmReadWritePtr::~JackShmReadWritePtr 0
Jack: Succeeded in unlocking 86577696 byte memory area
Jack: jack_client_close res = 0

I don't have this output with other jack clients, so maybe it's related to the problem?

Did you have any issue like this while testing ?

Post Reply

Return to “energyXT”