Serious Bug

adam-swierczynski wrote on 10/2/2018, 12:44 AM

When I use the bass machine instrument I get some serious problems. Playback in the program will fail, and exporting causes the whole program to crash. When I clean the tracks that have the bass machine, the errors go away and the song will export. It seems to have to do with the new low latency audio controller in the system tray. When using the bass machine instrument, sometimes the system tray will have multiple icons for the low latency audio controller.

I am not sure what to do here as this instrument is something that will be a core element of the track, and the error only occurs while the bass machine is playing.

Comments

emmrecs wrote on 10/2/2018, 4:18 AM

Hi.

Without a lot more information from you I suspect we may not be able to offer you any advice!

First, please read this post and then give us ALL the information requested. At the moment we know nothing about your computer nor even the exact version and variant of MM which you are using.

Jeff
Forum Moderator

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

adam-swierczynski wrote on 10/2/2018, 2:48 PM

Win 7 Ultimate

AMD FX-8350

RX480 GPU (MSI)

16 gb ram

128 gb SSD for boot drive (MAGIX is installed here)

MM 27.0.1.23 - Premium Ed 2018, EDM Ed 2018, 80s Ed 2018, Hip Hop Beat Producer Ed 2018

 

Using the bass machine produces this bug. Tried using it with and without effects (compression, EQ, etc.) still causes crashes and playback problems. The export issue happens both when exporting to .wav and .mp3, both with and without normalization option checked. The project settings for the audio quality and the export settings are both 44100 Hz. When I right click and clean the tracks where the bass machine was, the playback and export errors never occur.

I suppose I can use other instruments and get a similar sound. I would prefer to use what I have created so far. These are the settings on the instrument I am using:

emmrecs wrote on 10/2/2018, 3:46 PM

Hi.

Thanks for the additional information.

I can confirm you are running the latest version of MM. Unfortunately, I don't have and don't want to buy the Bass Machine so I cannot test whether this is something particular to your system, or a more widespread problem. Sorry about that.

I did a little research on your CPU and found the PassMark data for it here; it is clearly a very "economical" processor, but its performance ranks quite low when compared with other, similar units. I am not suggesting that your CPU is inferior but I do suspect that the Bass Machine is pretty demanding of any computer configuration.

I have one possible workaround to suggest: have you tried exporting to .wav only your Bass Machine track and then reimporting that track to your project, clearly with the original MIDI track muted. Can you then export the whole project successfully?

HTH

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

browj2 wrote on 10/2/2018, 4:47 PM

Hi,

Using the same version of MMM, I just tested Base Machine along and with other instruments and had no problems exporting to mp3 or importing the results.

Did you try this in a new project in case the first one is corrupt?

I am using W10 on my Surface Pro 4, so the OS could be the problem.

This may be tough to resolve.

John CB

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; 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; 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

adam-swierczynski wrote on 10/2/2018, 5:07 PM

emmrecs:

While my CPU is a bit outdated, I do have it unlocked and have the clockspeed boosted. While videogames are a poor comparison to other types of performance, I have not had any serious issues pushing 4k resolution at around 50fps fps many newer games. I did build this for multipurpose with multitasking in mind. I started a new project and dropped only the bass machine in, and noticed the problems pretty much immediately. I dont think the workaround you suggested will help.

 

browj2:

I started a new project and imported everything and manually redid the settings using screen captures as reference points. This was my first troubleshooting attempt. The problem reproduced itself in the new project just the same.

 

I have used the bass machine without problems maybe 2 updates ago. Seems like the problems started when the low latency application came bundled with one of the updates. It is nice to be able to manage inputs and outputs better, but as far as latency goes it seems to be counterproductive. When I made a new project with only the bass machine to test it out, after about 10 seconds of continuous play the low latency icon in the system tray turned red with a white exclamation point and the playback stopped and resumed once the low latency application turned green again.

I am not sure if it matters, but I have my headphones plugged into a port on the back of a samsung monitor and an AMD HDMI driver is used to feed the audio to the headphones through the display port cable that connects the monitor to the GPU.

daeell29-ukysse wrote on 10/3/2018, 1:15 PM

iIn my opinion , suspect your SSD disk is linked with your crash

emmrecs wrote on 10/3/2018, 2:14 PM

@adam-swierczynski

The suggestion of a failing SSD is certainly a possibility but I wonder whether this may also be a problem of buffer overload.

Can you check the following? With the Program Settings/Audio MIDI tab open, check the settings I have highlighted below:

If you press the highlighted Advanced button it will open the screen on the left. If you press on the highlighted "spanner" you will then see this:

Again, check and adjust the highlighted slider settings (what you can see is what I use but your computer is almost certain to need different settings (I have an external audio interface, hence the mention on that screen of "MOTU..."). You will almost certainly have to increase (slider to the right) those highlighted settings if I'm correct that the problem is buffer overload.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

adam-swierczynski wrote on 10/3/2018, 9:43 PM

So I adjusted the buffers a bit higher. This did help playback in the program to be smoother and without problems. However, the crash during rendering is still an issue.