Comments

CubeAce wrote on 1/21/2021, 8:27 PM

@John-Smith5561

Hi John, and welcome to the user to user forums.

I have had this on a few occasions for no valid reason and have no idea what kicks it off.

I have found it has been generally safe to dismiss the warning and carry on. Then if you save the project at the end of that session it normally doesn't appear again.

Ray.

Windows 10 Enterprise. Version 20H2 OS build 19042.746. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 27.20.100.9168, with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 460.89: 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.79. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

John-Smith5561 wrote on 1/22/2021, 11:02 PM

Sorry my dude, not really feeling like that's an OK answer and that's not your fault. I don't want to just 'dismiss' it and have it adjust settings in the background that I'm not aware of. We need a better answer from support.

emmrecs wrote on 1/23/2021, 3:55 AM

@John-Smith5561

As @CubeAce wrote in his first reply to you, these are user to user forums so not a contact for any Magix staff. To be clear, Magix staff may occasionally visit and read posts here but they do not routinely reply.

If this matter really bothers you (and Ray has explained that it really is "just one of life's mysteries") you will need to open a Support Ticket.

Jeff
Forum Moderator

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

Scenestealer wrote on 1/23/2021, 5:17 AM

@John-Smith5561

I don't want to just 'dismiss' it and have it adjust settings in the background that I'm not aware of.

If you don't want it to adjust anything then just click "Do not adjust". Simple!

If you believe you have set the project / movie frame rate to match your source footage then you should not have a problem.

The only reason I can think of that might be triggering the message is that you are trying to import video that has been shot or captured Variable Frame Rate (VFR) and VPX cannot decide what the actual framerate should be. If it is VFR then you've got bigger problems anyway and you will need to convert the video to Constant FR first, in a Converter program like Handbrake.

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, 2021 (V20.0.1.73) 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.

CubeAce wrote on 1/23/2021, 6:19 AM

@Scenestealer @John-Smith5561 @emmrecs

Hi Peter.

I have had that particular pop-up arise perhaps a total of four times or so.

None of which occurred with variable frame footage as . All projects only had MP-4 format files in them and stills in the form of jpegs. One or two may have had slow motion sections that were recorded in camera that may have been responsible for such a glitch but I can't remember due to me not finding it a problem at the time. I do remember using the speed adjustment on one such project several times at various incrementally adjusted speeds. All of which I assume could bring up such a warning.

Ray.

Windows 10 Enterprise. Version 20H2 OS build 19042.746. Direct X 12. Bios version 1401 latest hardware updates for Western Digital hard drives. Page file space 4.75GB.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version 27.20.100.9168, with 32GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB SSD D: drive for current project. 1 x 250GB SamSung Evo 970 drive for Operating System. + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal backup and 1 for Library clips/sounds/music/stills. Total 12TB of four external WD drives for backup.

Gigabyte NVIDIA G Force GTX 1650 Super . nVidia driver version 460.89: 1280 CUDA cores Direct X 12. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3.

Running MEP Premium 20.0.1.79. and VPX 17.0.3.68 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

John-Smith5561 wrote on 1/23/2021, 1:16 PM

@emmrecs Yea, no sweat. I get the distinct impression that support would really rather not. I would hope at the least they're monitoring these to track new issues or pain points and maybe comment/remark that they're aware or what not. But they're pretty hands off it seems. No matter.

@Scenestealer I think part of the worry I have is that this message suggests that my settings don't match for some reason despite what I'm seeing. It leaves me with a lack of confidence and it would really suck to take on a large project only to find out at the end that something is 'off' and causing bad renders. The variable rate is a good suggestion, I checked though and it's definitely constant. Regardless, I'll keep an eye out for VFR related content, it's a good suggestion.

@CubeAce I suspect that there's more settings that aren't aligned that trigger the prompt, but the devs didn't include it or update the message box to present it.
 

johnebaker wrote on 1/23/2021, 2:38 PM

@John-Smith5561

Hi

From the information you have posted in your other topic the issue with the pop-up is most likely because you are adding Variable Frame rate video to the timeline and although it the project is set to 30fps and the video is tagged as 30 fps, it actually varies and VPX is detecting this.

John EB

Last changed by johnebaker on 1/23/2021, 2:39 PM, changed a total of 1 times.

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021.

Running Windows 10 Professional 20H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

John-Smith5561 wrote on 1/23/2021, 9:37 PM

@johnebaker I thought you were on to something, and you still might be, but I'm able to repro the issue with a video using a constant frame rate. I also checked the color space and audio sampling too. I think the issue is with how the project space is initialized and then later compared. That is, the settings you first start the movie with, are the settings that are used for comparison, regardless if you've manually adjusted the Move settings (File -> Settings -> Movie). No matter what, it still sees it as 'non-matching' and shows the dialogue. Still doesn't assuage my paranoia given the ongoing audio issues though...

johnebaker wrote on 1/24/2021, 6:57 AM

@John-Smith5561

Hi

. . . .  I think the issue is with how the project space is initialized and then later compared. That is, the settings you first start the movie with, are the settings that are used for comparison, regardless if you've manually adjusted the Move settings . . . .

That is correct, additionally if you do click adjust, to an imported clip, it changes the project settings to match that clip, however the next clip added may popup the message again because it is the same as the previous clips before the adjustment - hope that makes sense!

The MediaInfo data you posted in your other topic does explain why you are getting the message - you are mixing 29.97 and 30 fps video.

Colour space should not cause the message to appear - it only pops up when the video resolution and/or framerate is different from what the project is set to.

We recommend the project setting should match the framerate and resolution of the majority video being imported and the 'Adjust' message when importing video not the same as the project settings should be ignored, ie 'Do not adjust'.

HTH

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021.

Running Windows 10 Professional 20H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

browj2 wrote on 1/24/2021, 7:28 AM

@John-Smith5561

Semantics, but just to get the jargon right and to avoid confusion in this thread and your other one, please do not refer to video, audio or image files that you put on the timeline as tracks. Tracks are those horizontal parts in the Project Window numbered from 1 onwards onto which you put objects. Your subject says that you get a warning "when adding tracks." For most users, that would probably mean that you are clicking on the + button in the track header to add a track. You are actually importing video clips onto a track.

I do not recall ever having seen the message pop up when the file being imported is the same as my Project Settings. I have had the message pop up when importing some screen recordings from one session or recording to another. My screen recorder is set to 30 fps but sometimes records at 15 fps, which explains why.

I think that you now have a sufficient answer to your initial question. It would have been helpful if you had made available a couple of short video clips that caused the message to pop up. The same applies to your other thread.

John CB

John C.B.

VideoPro X(12); MEP2021 Plus; MM2021 Premium; see About me for more.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903