Comments

johnebaker wrote on 12/22/2020, 10:53 AM

@Martin-Wertwijn

Hi

Are the headphones connected by USB, Bluetooth, or 3.5mm stereo jack?

Do they work with other programs?

Connecting any of them, should automatically disable the internal speakers, if not, with the headphones connected try setting them as the default playback device in the Windows Sounds control panel.

What settings in Music maker are you using?

These are the settings I use:

Check under the Advanced button your sound card in/out are selected similar to those shown above - I have Realtek card, if your is not a Realtek the options for your sound card should be similar.

HTH

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Martin-Wertwijn wrote on 12/23/2020, 1:22 PM

Thanks for your answer John. I also sent my question to Magix support and it has been resolved.

johnebaker wrote on 12/23/2020, 1:36 PM

@Martin-Wertwijn

Hi

What was the solution - it may be useful to other users?

John EB

Last changed by johnebaker on 12/23/2020, 1:36 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Martin-Wertwijn wrote on 12/23/2020, 3:36 PM

Hi. This is the full answer from the support team:

This most likely indicates a problem with the audio driver that is automatically set to be used as default driver either interfacing the wrong audio device (i.e. not the one you're actually using for the main audio output on your system), or that particular driver type not working well with your current audio hardware at all. Please take the following steps to rectify this problem and get audio output from the program:

Start the program and proceed to the main screen. Press the "P" hotkey on your keyboard to access Music Maker's program settings dialogue, and proceed to the "Audio/MIDI" tab. On the left-hand side of the dialogue you will see the "Audio playback" section, with the choices for the different driver types the program can use to interface your audio hardware. When first installing and starting the program, you should find that this is set to "ASIO" by default, with the "Magix Low Latency 2016" driver being selected as the actual ASIO driver. Click the "Advanced..." button, which you can also find in this section, to access the detailed configuration dialogue for the selected ASIO driver. Make sure in the list of audio devices in your system to actually select the one that represents your audio hardware/output that you want to use. After confirming all settings, the audio output should now be routed to the correct driver/output.

If the approach above doesn't resolve the issue, or if you have different preferences and requirements for the audio driver you want the program to work with, you can also use the program settings dialogue desribed above to configure any of the other driver types (e.g. Wave, DirectSound or WASAPI), or to choose a different ASIO driver from the drop-down list, if available. The latter option might especially come in handy if you're using a dedicated sound hardware with an official ASIO driver provided by the manufacturer, or if you're using the free generic ASIO driver ASIO4ALL (http://www.asio4all.com) on your system.

Please keep in mind that, if you're planning on any actual audio or MIDI recording workflows, you will need to opt for driver types that help reduce recording latency times to a minimum (i.e. ASIO or WASAPI). If you're exclusively working with the pre-recorded loops and maybe e.g. composing MIDI material via your mouse, such timing issue my not be relevant, and you're free to use Wave or DirectSound drivers as well.


The other issue you indicated is not a technical problem but behaviour by design, and closely related to the driver setting above. It's the expected behaviour when using a driver type that demands exclusive access to the sound hardware/driver resources. This is e.g. the case with ASIO drivers, which will cut off the access to the sound hardware for other applications. If you wish to use other applications that generate audio output at the same time as running Music Maker, a practical workaround solution could be using other driver types/architectures supported by Music Maker which don't demand exclusive access, e.g. Direct Sound. You can configure the audio driver type in the Music Maker program settings dialogue (shortcut "P" key), under the "Audio/MIDI" tab. Please keep in mind that this may only be a feasible option if you don't do any audio or MIDI recordings directly into Music Maker. If you do recordings and you require low recording latency times, you may not get around using ASIO or WASAPI drivers.