Comments

Grazie wrote on 4/23/2014, 6:02 AM
You are right. In everything with MBL an update would have replaced the existing. BUT, this update has some major stuff going on and I'd suspect that they are different enough to be firewalled from one another. I have NO idea if they'd be issues.

Ask RED GIANT.

Grazie

Dexcon wrote on 4/23/2014, 6:11 AM
A very good question as I also have the 2 versions of MBL after installing 2.5 today (and the new features look great). I wonder if projects where the earlier version of MBL has been used will still want that earlier version installed or if it will happily be captured by MBL 2.5. I'll have to have a play around with it to find out.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

ushere wrote on 4/23/2014, 6:56 AM
please let us know what you find out dexcon...
Dexcon wrote on 4/23/2014, 6:58 AM
It looks like you need to keep both MBL versions installed if you have used MBL prior to version 2.5.

I created a test project in VP13 using a random effect from the earlier MBL version. After closing VP, I uninstalled the earlier version of MBL and then reopened VP13. VP then came up with the 'missing plug in' dialogue box - and the clip on the timeline was no longer showing the green video FX indicator. So MBL 2.5 doesn't recognise FX from the earlier MBL version from this test. After reinstalling the earlier MBL version, the MBL FX on the test project sprang back into life.

I'll therefore keep both versions installed.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

ushere wrote on 4/23/2014, 7:32 AM
thanks for that dexcon
PhillB wrote on 4/23/2014, 11:19 AM
Confused now, just had this chat with Red Giant as below.
Maybe I'll try the un install and re install.

Eric L
Hello Phill. How may I help you?
Phill
Hi,
I've just upgraded to MBL 2.5 on vegas pro 13. Do I need to keep both versions on my system, as I now have two versions of MBL on my system.
Eric L
No, you don't. You can get rid of the old version. The version previous to 2.5 was reliant on a standalone program, while version 2.5 is a self-contained plugin.
Phill
ok, so will older projects that used the previous version still be recognised by ver 2.5
Eric L
Yes, it's backwards compatible with projects that used older versions of Magic Bullet Looks 2.
Phill
OK, thanks eric, so I'll go ahead and un install both versions and re install ver 2.5
5:14 pm
Eric L
Sounds good! Sorry for any confusion. Have a great day.
Phill
ok, thanks for your help.
PhillB wrote on 4/23/2014, 12:53 PM
Well that didn't work.
Your right Dexcon we need to have both versions installed.
Spoke again to Red Giant who now realise there is no backward compatibility for Vegas Pro 13 users when moving to version 2.5.

But all is not totally lost because if you have been creating custom pre sets, ver 2.5 can find these no problem so you could convert a project to ver 2.5 for a re edit if needed.
Now we just need Gary to give us a Pro 13 version of TLT's Please............
ushere wrote on 4/23/2014, 5:54 PM
how does one remove the old version yet keep the new 2.5?

uninstall completely and reinstall just the 'update'?

if above, does 2.5 automatically pickup serial number?
Dexcon wrote on 4/23/2014, 8:08 PM
Ushere, from what I can make out, version 2.5 is effectively a new programme rather than being an update - sort of like buying the VP update to VP13 though you can decide whether to keep VP12 (or earlier) installed or to uninstall it.

Under Windows Control Panel "Uninstall or change a program", the 2.5 version MBL appears as "Color Suite v11.1.0" whereas the previous version of MBL appears as "Magic Bullet Suite 64-bit" - or at least it does on my system. Uninstalling the latter does not seem to effect the 2.5 install.

When installing 2.5, the field was still there to code in the serial number even though MBL was coded in the licensing panel below it as already being licensed (including the serial number). I still coded the serial number so I don't know what would happen if I didn't code it, though I suspect that it still would have proceeded given that MBL showed as being currently licensed.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

ushere wrote on 4/23/2014, 10:36 PM
interesting, i only see one entry for mb in con panel>progs.

also, if i do uninstall mb suite will i get the option with 2,5 to install back to cs6 (ps and prem)?
Dexcon wrote on 4/24/2014, 2:04 AM
Ushere, I think I've worked out why I have two MBL entries in Control Panel/Uninstall.

The older version of MBL I had installed is version 11.4.3 which is apparently the last of the MBL updates when MBL was a programme unto its own (possibly from April last year). At some stage, MBL got absorbed into Red Giant's ColorSuite bundle which has update numbering of 2.0.? and 2.1.? (ending with the latest 2.5 version).

I think that after rebuilding my computer last time, I inadvertently installed 11.4.3 rather than 2.1 - which I think explains why there are 2 separate programmes installed on my system. Whereas 2.5 may possibly override 2.0 or 2.1 (though I haven't tested that), it seems that 2.5 doesn't override 11.4.3

Nevertheless, my test does show that MBL FX created in 11.4.3 - and presumably versions earlier to that aren't captured by the latest 2.5 version.

Sorry for any confusion that I may have caused.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

CJB wrote on 4/25/2014, 10:13 AM
I am having a problem with the install of 2.5. It works for me with 8bit color space on project settings, but as soon as I go to 32 bit floating point (either video or full range) it only processes 1/4 of image. Can anyone else verify this problem?

BTW my previous version of MBL still works.