THM
February 2, 2026, 3:25pm
1
Hi all,
I have a strange issue. In my JUCE/TE project if I go the AudioDeviceManager windows (the classic from JUCE) and I click test I ear audio and I can also see audio coming from the inputs.
But when I add a clips (midi or audio) to the edit I ear nothing and I don’t see the mixer moving.
What I’m missing? There is something to do to match the JUCE audio device to the edit?
Before it was working but then it stops and I don’t find the problem
Another point is that is working on my windows dev PC but not on the raspberry with HiFi Berry.
But on the raspberry if I do some test via command line I can ear sound!
Thanks in advance!
Without showing your code, nobody will know whats going on. What is about the demo projects? Does it works?
THM
February 4, 2026, 11:19am
3
@baramgb you are right sorry.
Basically I have this in my App.cpp
App::App(tracktion::Engine& engineRef)
: engine(engineRef)
{
App::instance = this;
auto& dm = engine.getDeviceManager();
dm.initialise();
dm.rescanWaveDeviceList();
dm.rescanMidiDeviceList();
auto& juceDM = dm.deviceManager;
#if JUCE_LINUX
juceDM.setCurrentAudioDeviceType("ALSA", true);
#endif
auto result = juceDM.initialiseWithDefaultDevices(/*ins*/0, /*outs*/2);
if (result.isNotEmpty())
{
juce::Logger::writeToLog("MINBOOT: FAILED initialiseWithDefaultDevices: " + result);
}
else
{
if (auto* dev = juceDM.getCurrentAudioDevice())
{
juce::Logger::writeToLog("JUCE DEV OK: " + dev->getName()
+ " type=" + juceDM.getCurrentAudioDeviceType()
+ " sr=" + juce::String(dev->getCurrentSampleRate(), 0)
+ " bs=" + juce::String(dev->getCurrentBufferSizeSamples())
+ " outs=" + juce::String(dev->getOutputChannelNames().size())
+ " ins=" + juce::String(dev->getInputChannelNames().size()));
}
else
{
juce::Logger::writeToLog("JUCE DEV NULL after init");
}
}
...
And I see this:
Log started: 4 Feb 2026 12:11:19pm
Logger enabled
Audio block size: 64 Rate: 48000
JUCE DEV OK: default type=ALSA sr=44100 bs=512 outs=256 ins=0
[4 Feb 2026 12:11:22pm] TRACKTION outputs: num=1
[4 Feb 2026 12:11:22pm] Track 'Track 1' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 2' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 3' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 4' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 5' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 6' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 7' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 8' outDeviceID=(default audio output)
[4 Feb 2026 12:11:22pm] Track 'Track 9' outDeviceID=(default audio output)
device=default activeOut=11
outputs num=1
And If I go in the audio panel created by default from juce with the test button I ear sound correcty.
In the Demo of TE I can ear audio so I’m confused
Thanks
THM
February 4, 2026, 2:10pm
4
At the end I copied the Settings.xml from the DemoRunner and now it works again!
I guess you should not manage the device manager. The engine is handle the device manager. So if you load the settings of the demo, you repair the device manager. Have a look at GitHub - debrisapron/tracktion-engine-hello-world: A super-simple JUCE/tracktion_engine app which nevertheless makes a sound
THM
February 9, 2026, 2:57pm
6
So you mean no deviceManager activation on the start of the app?
dave96
February 9, 2026, 3:09pm
7
That’s handled by the Engine constructor.