Vocals Won't Play Back

Interlude wrote on 11/14/2019, 5:42 AM

I'm hoping someone can help me. I've got Magix Music Maker 2020 and am using a Blue Yeti mic. I am not a tech wizard by any means - just a songwriter who wants a quick fix to record.

The Magix software is picking up the vocals and I can hear myself when I'm recording. But my vocals won't play back. Blue Yeti doesn't appear on my output devices so I can record but not hear the vocals through my headphones afterwards. I've tried everything and can't figure out how to rectify this issue. Any advice would be greatly appreciated.

Comments

Graham-Hawker wrote on 11/14/2019, 9:09 AM

Is that the screen shot of when you play back? The vocal track is still set to record. Mine wouldn't playback in that state. When turned off it is fine.

Interlude wrote on 11/15/2019, 11:47 AM

Is that the screen shot of when you play back? The vocal track is still set to record. Mine wouldn't playback in that state. When turned off it is fine.

Thank you for your response. What I'm confused about is, when I take it off record, it takes me to 'vita solo instruments' (as shown in screenshot). I then have to choose either keyboards or drums which converts the bar to MIDI instead of audio recording. Do you know how I can keep it on vocals?

Interlude wrote on 11/15/2019, 11:52 AM

Sorry cancel that, I think I've got it now. I just have to keep pressing 'audio record' to record the audio, then switch it back to 'rec' to hear the playback. I must be the least tech-minded person on here (sorry!!) I had been using Magix Music Maker 2005 for years and simply pressed the record button and away I would go...I miss the simplicity of it! Thank you for your help.

browj2 wrote on 11/15/2019, 12:12 PM

Glad to see that you've got it.

We have all been caught with that. It's not obvious.

John CB

John C.B.

VideoPro X(17U); Video Deluxe 2026 Plus, Movie Studio 2025 Platinum; Music Maker 2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 11 Pro 24H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB, 12TB, 14TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

ralftaro wrote on 11/19/2019, 9:06 AM

We have all been caught with that. It's not obvious.

"Not obvious" is a horribly kind and politically correct way to describe this bug, John. 😅

I can confirm that this is definitely still on the development agenda. However, this unintuitive program behaviour is probably only going to change in the next major version. That version should see a big overhaul of the audio recording engine, pretty much in the same manner that a lot of the MIDI issues got fixed in generation 28.x. This will include the multiple other issues that you reported in that area.

Cheers!