Mixer - Cannot get volume change to stick

terrypin wrote on 11/26/2012, 9:21 AM

I've never used the Mixer seriously in any version of MEP, mainly because I've never seemed to need it but also because I find it dauntingly complex!

But this morning I was trying to set a clip to a setting not included in the right click Set Volume menu, so I tried to do this in the mixer. And found an immediate snag that I'm sure will have an embarrassingly simple answer.

When I adjust the vertical slider for a track, as soon as I play it then the slide returns to its previous position. Here's an example:

Or for better quality: https://dl.dropbox.com/u/4019461/MEP2013-Mixer-1.jpg

--
Terry, East Grinstead, UK

Last changed by terrypin on 11/26/2012, 9:21 AM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

Comments

emmrecs wrote on 11/26/2012, 1:19 PM

Hi Terry.

Looking at your screenshot it appears that you have enabled a Volume Curve, the green line on your track.  That will have created a keyframe point which the mixer does not override.  You can easily disable (and remove)  the curve, and so take level control via the mixer, by unticking "volume" on the KF screen.

The mixer values you ask about are "levels".  Theoretically they ought to be in dB (decibels) but they clearly are not.   (In digital terms any level in excess of 0dB = distortion.)

HTH

Jeff

Last changed by emmrecs on 11/26/2012, 1:19 PM, changed a total of 1 times.

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Vegas Pro, 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

terrypin wrote on 11/26/2012, 2:55 PM

Hi Jeff,

Thanks, that's very helpful.

I've been studying this stuff further since I posted and am beginning to make progress. One problem I always have is confusion over the two different volume curves, and the several ways of displaying them. Another new difficulty arose after using the Curve Mode mouse cursor for the first time: the proliferation of points that get created. My object quickly gets peppered with them!

--
Terry, East Grinstead, UK

Last changed by terrypin on 11/26/2012, 2:57 PM, changed a total of 2 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)

johnebaker wrote on 11/26/2012, 3:51 PM

Hi Terry

I cannot reproduce this - I have followed your instructions and even tried with three different levels as shown in the image below- the mixer always shows 0dB for the audio track.

 

BTW those values next to the sliders are dB

John

Last changed by johnebaker on 11/26/2012, 3:51 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.

Scenestealer wrote on 11/26/2012, 5:09 PM

Hi All

Terry - This is because as Jeff has noted you have "Track Curves" activated which has the effect of automating the mixer ie. it sets a node at a point in time if the mixer is moved while a track is playing. The slider is only relevant to a node/level on the green line and not to the volume level in the clip which John has set.

For a full discussion of this please go to the old Magix User board forum and read this topic (which you started) or search "Track Curves" there.

 http://support2.magix.net/boards/magix/index.php?showtopic=53190&hl= track  curves&st=0

Note my summary near the bottom of the first page.

As I have noted the automation is as much use as the drawing mouse mode because it creates far too many nodes making it almost impossible to edit or tweak the levels at different points, afterwards! It would be much more useful if you could choose an interval for the laying down of nodes, say one every half second or something.

Peter

Last changed by Scenestealer on 11/26/2012, 5:09 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

johnebaker wrote on 11/26/2012, 5:23 PM

@ Peter

  I even answered in that one

You must have a very good memory

John

Last changed by johnebaker on 11/26/2012, 5:23 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.

Scenestealer wrote on 11/26/2012, 5:33 PM

John, I was sparing you the embarassment by not mentioning that.

"You must have a very good memory"  - So far so good!

A good resouce that old forum. Long may it remain.

Peter

Last changed by Scenestealer on 11/26/2012, 5:33 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

terrypin wrote on 11/27/2012, 3:29 AM

Hi Peter,

Thanks for reminding me about that thread I started over two years ago. Just re-read it and wish I'd done so earlier.

Yes indeed, I sure miss the old forum, although I do have its large archive handily bookmarked just for its Search facility at

http://support2.magix.net/boards/magix/index.php?showforum=113http://support2.magix.net/boards/magix/index.php?showforum=113

or more conveniently  http://tinyurl.com/5tswdg6

BTW, good to see that with the exceptions of Alwyn (anyone have any contact?) and Carl (who seems active primarily nowadays in Q&A), the 'regulars' remain the same.

This 'volume curve' topic seems one of the most discussed issues, and still remains confusing to me. One primary cause is terminology. Another is Magix's incomplete documentation on it, particulary the lack of detailed practical examples. Yet another is the change in colours over MEP versions. Add a few bugs and quirks and small wonder I've never been comfortable with this area!

Quoting myself from that old thread (replying to a comprehensive explanation from Peter):
"From experience, it's highly unlikely Magix will tidy this up anytime soon. But maybe they could include your explanation in Help, or at least pin it here."
Still waiting...

--
Terry, East Grinstead, UK

 

 

Last changed by terrypin on 11/27/2012, 3:29 AM, changed a total of 1 times.

Terry, East Grinstead, UK. PC: i7 6700K, 4.0 GHz, 32GB with Win 10 pro. Used many earlier versions of MEPP, currently mainly MEPP 2016 & 2017 (Using scores of macro scripts to add functionality, tailored to these versions.)