You are a God :). Thank you soooo much for sharing this. I was able to adopt the code to make 298 cuts for a 4 camera Premiere Pro project. Thank you Thank you Thank you and more grease to your elbows.
Hello there. This video is about the finished effect of PRO ISO. I have a MINI PRO thread. and I don't know how to use this MINI PRO ready effect in DAVINCI or PRIMER PRO. If you know, can you make a video on this topic?
If you don’t have an ISO model, then you cannot re-edit your show afterwards and change shots. The non-ISO models don’t record all the cameras all the time, they only record whatever is live as you’re switching.
Ok, that's pretty awesome, but dang, is this really the best way to do multi-cam from Atom Mini Pro ISO in premiere? You'd think with the multi-cam features in Premiere there would be a way to just tell it somehow that this is a multi-cam sequence. hmm... I haven't used it in years, just getting back into video after 10+ years away, but maybe I should just learn Resolve. I used to be an expert on Premiere, so it does feel like home and keyboard shortcuts feel natural and familiar
Resolve doesn’t do it either. The ATEM doesn’t format the clips in the DRP as multicam clips, it just says hey, here’s a string of single camera clips.
@@smp2 From what I understood, this is what we know going in. Basically the ATM mini Pro ISO creates a timeline with all of your cuts as single clip sources. However, because you have the pro ISO your separate video sources are also included. So you could create a new multi-camera sequence with those clips And if there are any errors in your timeline created by the mini Pro ISO your new timeline could correct that And you would only replace clips or segments at most. I hope this is making sense.
Thank you. Great help. Is it possible to use it in Davinci Resolve ? because their Sync Bin feature is not really intuitive at all like a real Multicam
Well, in theory, if you could get keyboard shortcuts to do the same things, then yes. All this script basically does is press keys. Take a look inside the AHK file, each line is explained. If you can get resolve to do the same actions, it will work the same way.
Hello, thx for super solution!!...just one question...when program automaticly cuts multicam sequence, i allways have same video (TRACK 1) on multicam seq. Its that OK? I thing that will be normaly switching on same original edit clips (same like original edit)...now i must in Multicam seq.change every single edit to right clip? Or i mist something?
I'm not sure I fully understand your question, but if you're working from an ATEM .drp file imported into Premiere, you should leave the ATEM's cuts on V1, and put a multi-camera clip on V2. If you're having an issue where all the cuts made to the multi-camera clip are the same angle (for example, the cuts are in the right place but it's always Camera 1), then you need to start over, and ensure that both V1 and V2 are de-selected (no blue boxes) before running. If you're sure they are, double check that the file names include the camera number. If they look like "[Project Name] Cam 2.mp4", then you should be fine. The script looks for that last number before the .mp4 to decide which camera to cut to.
@@smp2 I followed these instructions and it only changes camera angles once at the beginning and remain on that camera angle for the rest of the cuts. Any ideas on what that is? My files end in the camera number.
@@SoRealSoReal23 it’s possible you may need to change the delays. In the code, pay attention to the number after “sleep”. You can open with notepad and increase that number to make the code run more slowly.
@@smp2 which sleep instance do you recommend changing? I tried making all the sleep functions 175 instead of 75. It didn’t make any camera angle changes. Now trying just adding more sleep to just the sleep instance right after “Change the camera angle on our new clips”
@@SoRealSoReal23 try changing them all to 500 just to rule it out. It’s in milliseconds, so 500 would be half a second. If it’s definitely not that, double check your keyboard shortcuts.
doesn't work for me. script "can't find CAM 1 in file name". the files are named "test12 CAM 1 01", the same as CAM 2 and CAM 3. since the downloaded version of V2 - then you write that there is a problem with the names 01..02 ... has already been resolved - what is he looking for? I tried to rename the files just in CAM 1, CAM 2 - no effect, the same inscription.
I've reviewed other comments here and found an issue between your script and the ATEM's naming convention. When the ATEM is started and stopped multiple times within the same project, and was generating time-of-day timecode, when the xml is exported from DaVinci Resolve it creates one large timeline based on time-of day. Your various sequences are positioned on this timeline according to the time of day when they were recorded (which is perfectly fine). But now what happens to the ISO clips, given that you now have more than one clip for each camera? It adds a suffix number after the camera number. So you'll have CAM 1 01, CAM 1 02, CAM 1 03, then CAM 2 01, CAM 2 02, CAM 2 03, etc. Those are all camera 1, just three different clips that were generated when the ATEM was started and stopped three times. The same will occur for cameras 2 through X. If your script is looking for the last number before the .mp4 to be the camera number, it instead is going to confuse the suffix number for the camera number. This is probably why a number of people have reported cuts to wrong cameras or the same camera over and over. Can this be remedied? I'm desperately trying to fix an ATEM recording where the ATEM was incorrectly set to a low streaming bitrate and the resulting recording is useless - it's a total of 8 hours of recorded material with thousands of cuts that needs to be reconstructed. I saw this script as a Godsend and it took awhile to figure out why the cuts are all wrong. It's mistaking the suffix numbers for camera numbers. Can it be fixed or does this break it altogether? Instead of sampling the last numeric before the .mp4, can it be made instead to search for "CAM X" where X is a number, anywhere in the clip name, and use X as the camera number, ignoring other numbers in the clip name?
The SPECIFIC filenames for the cameras in this project are: "WashDC230414 CAM 1 01.mp4" where we can have "CAM 1" through "CAM 5" and the two digits before .mp4 run from 01 through 15. Then there's a second project almost identical except the root name is WashDC230415 (can you guess when this was shot?). I don't know this scripting language and am desperately trying to get this project repaired on a tight schedule. Any chance of some alternative language for the script that would address this?
Perhaps the script can be remedied, I’d have to devise a way for this to happen. In the meantime, an easy temporary fix would be to rename CAM 1 01.mp4, CAM 1 02.mp4, and CAM 1 03.mp4 to all simply be named CAM 1.mp4, and place them in separate folders within your drive to avoid file name conflicts. This shouldn’t affect the way premiere is able to organize them into a multicam sequence.
@@smp2 Thanks for replying so quickly. I came up with a simpler answer: I edited the script as follows: StringRight, Trimmed1, clipboard, 8 ; Trim the clipboard so we're just looking at the last 8 characters. ; Since it'll be "[Project Name] Cam X YY.mp4", this function will ; trim it down to "X.mp4" As you know (but other readers may not) it was originally "StringRight, Trimmed1, clipboard, 5" which cut the string to the last five characters (which in your case was "X.mp4") and then in a later step you truncated it to just the one digit camera number. By changing from 5 to 8, it now strips off the space after the camera number, plus the two-digit sequence number as well as the .mp4. It worked fine in my first test. Hopefully I can get through the entire project with this fix. Thanks for writing and posting this - it was a lifesaver, even with the need for the minor tweak.
@@PeteGould sure, but do all your files have those trailing digits? I’m curious whether the first time you started/stopped the ATEM will be called PROJECT CAM 1 01.mp4, or simply PROJECT CAM 1.mp4. In any case, I am working on an updated script that uses regex to find the camera number.
I think, in theory, Automator might be able to do this. Unfortunately I don't know too much about it, maybe I'll do some research and see if it's possible.
FFFFFFFFUUUUUUUK no thank you. IDK jack shit about Resolve and just tried to record some shots to edit later. Just getting the ISO file folders to import at all isn't working. Something else must be wrong.
![I Replaced ALL my ADOBE APPS with these [free or cheaper] Alternatives!](/img/n.gif)
This is the most niche and awesome thing I've ever seen.
You are a God :). Thank you soooo much for sharing this. I was able to adopt the code to make 298 cuts for a 4 camera Premiere Pro project. Thank you Thank you Thank you and more grease to your elbows.
at this point i'd rather recut the show with the line cut as one of the multi cams. only change what you need. why bother wasting all this time?
Hello there. This video is about the finished effect of PRO ISO. I have a MINI PRO thread. and I don't know how to use this MINI PRO ready effect in DAVINCI or PRIMER PRO. If you know, can you make a video on this topic?
If you don’t have an ISO model, then you cannot re-edit your show afterwards and change shots. The non-ISO models don’t record all the cameras all the time, they only record whatever is live as you’re switching.
Ok, that's pretty awesome, but dang, is this really the best way to do multi-cam from Atom Mini Pro ISO in premiere? You'd think with the multi-cam features in Premiere there would be a way to just tell it somehow that this is a multi-cam sequence. hmm... I haven't used it in years, just getting back into video after 10+ years away, but maybe I should just learn Resolve. I used to be an expert on Premiere, so it does feel like home and keyboard shortcuts feel natural and familiar
Resolve doesn’t do it either. The ATEM doesn’t format the clips in the DRP as multicam clips, it just says hey, here’s a string of single camera clips.
@@smp2 From what I understood, this is what we know going in. Basically the ATM mini Pro ISO creates a timeline with all of your cuts as single clip sources. However, because you have the pro ISO your separate video sources are also included. So you could create a new multi-camera sequence with those clips And if there are any errors in your timeline created by the mini Pro ISO your new timeline could correct that And you would only replace clips or segments at most. I hope this is making sense.
Thank you. Great help.
Is it possible to use it in Davinci Resolve ? because their Sync Bin feature is not really intuitive at all like a real Multicam
Well, in theory, if you could get keyboard shortcuts to do the same things, then yes. All this script basically does is press keys. Take a look inside the AHK file, each line is explained. If you can get resolve to do the same actions, it will work the same way.
Hello, thx for super solution!!...just one question...when program automaticly cuts multicam sequence, i allways have same video (TRACK 1) on multicam seq. Its that OK? I thing that will be normaly switching on same original edit clips (same like original edit)...now i must in Multicam seq.change every single edit to right clip? Or i mist something?
I'm not sure I fully understand your question, but if you're working from an ATEM .drp file imported into Premiere, you should leave the ATEM's cuts on V1, and put a multi-camera clip on V2. If you're having an issue where all the cuts made to the multi-camera clip are the same angle (for example, the cuts are in the right place but it's always Camera 1), then you need to start over, and ensure that both V1 and V2 are de-selected (no blue boxes) before running. If you're sure they are, double check that the file names include the camera number. If they look like "[Project Name] Cam 2.mp4", then you should be fine. The script looks for that last number before the .mp4 to decide which camera to cut to.
@@smp2 I followed these instructions and it only changes camera angles once at the beginning and remain on that camera angle for the rest of the cuts. Any ideas on what that is? My files end in the camera number.
@@SoRealSoReal23 it’s possible you may need to change the delays. In the code, pay attention to the number after “sleep”. You can open with notepad and increase that number to make the code run more slowly.
@@smp2 which sleep instance do you recommend changing? I tried making all the sleep functions 175 instead of 75. It didn’t make any camera angle changes.
Now trying just adding more sleep to just the sleep instance right after “Change the camera angle on our new clips”
@@SoRealSoReal23 try changing them all to 500 just to rule it out. It’s in milliseconds, so 500 would be half a second. If it’s definitely not that, double check your keyboard shortcuts.
doesn't work for me. script "can't find CAM 1 in file name".
the files are named "test12 CAM 1 01", the same as CAM 2 and CAM 3.
since the downloaded version of V2 - then you write that there is a problem with the names 01..02 ... has already been resolved - what is he looking for?
I tried to rename the files just in CAM 1, CAM 2 - no effect, the same inscription.
I've reviewed other comments here and found an issue between your script and the ATEM's naming convention. When the ATEM is started and stopped multiple times within the same project, and was generating time-of-day timecode, when the xml is exported from DaVinci Resolve it creates one large timeline based on time-of day. Your various sequences are positioned on this timeline according to the time of day when they were recorded (which is perfectly fine). But now what happens to the ISO clips, given that you now have more than one clip for each camera? It adds a suffix number after the camera number. So you'll have CAM 1 01, CAM 1 02, CAM 1 03, then CAM 2 01, CAM 2 02, CAM 2 03, etc. Those are all camera 1, just three different clips that were generated when the ATEM was started and stopped three times. The same will occur for cameras 2 through X. If your script is looking for the last number before the .mp4 to be the camera number, it instead is going to confuse the suffix number for the camera number. This is probably why a number of people have reported cuts to wrong cameras or the same camera over and over. Can this be remedied? I'm desperately trying to fix an ATEM recording where the ATEM was incorrectly set to a low streaming bitrate and the resulting recording is useless - it's a total of 8 hours of recorded material with thousands of cuts that needs to be reconstructed. I saw this script as a Godsend and it took awhile to figure out why the cuts are all wrong. It's mistaking the suffix numbers for camera numbers. Can it be fixed or does this break it altogether? Instead of sampling the last numeric before the .mp4, can it be made instead to search for "CAM X" where X is a number, anywhere in the clip name, and use X as the camera number, ignoring other numbers in the clip name?
The SPECIFIC filenames for the cameras in this project are: "WashDC230414 CAM 1 01.mp4" where we can have "CAM 1" through "CAM 5" and the two digits before .mp4 run from 01 through 15. Then there's a second project almost identical except the root name is WashDC230415 (can you guess when this was shot?). I don't know this scripting language and am desperately trying to get this project repaired on a tight schedule. Any chance of some alternative language for the script that would address this?
Perhaps the script can be remedied, I’d have to devise a way for this to happen. In the meantime, an easy temporary fix would be to rename CAM 1 01.mp4, CAM 1 02.mp4, and CAM 1 03.mp4 to all simply be named CAM 1.mp4, and place them in separate folders within your drive to avoid file name conflicts. This shouldn’t affect the way premiere is able to organize them into a multicam sequence.
@@PeteGould I think tagging you may have been erroneously left out of my other comment, see if that proposed solution works.
@@smp2 Thanks for replying so quickly. I came up with a simpler answer: I edited the script as follows:
StringRight, Trimmed1, clipboard, 8 ; Trim the clipboard so we're just looking at the last 8 characters.
; Since it'll be "[Project Name] Cam X YY.mp4", this function will
; trim it down to "X.mp4"
As you know (but other readers may not) it was originally "StringRight, Trimmed1, clipboard, 5" which cut the string to the last five characters (which in your case was "X.mp4") and then in a later step you truncated it to just the one digit camera number. By changing from 5 to 8, it now strips off the space after the camera number, plus the two-digit sequence number as well as the .mp4. It worked fine in my first test. Hopefully I can get through the entire project with this fix.
Thanks for writing and posting this - it was a lifesaver, even with the need for the minor tweak.
@@PeteGould sure, but do all your files have those trailing digits? I’m curious whether the first time you started/stopped the ATEM will be called PROJECT CAM 1 01.mp4, or simply PROJECT CAM 1.mp4. In any case, I am working on an updated script that uses regex to find the camera number.
Very cool. I sub you
Thanks but thats too much to do
WOW
Please get create it for Mac too! Please!
I think, in theory, Automator might be able to do this. Unfortunately I don't know too much about it, maybe I'll do some research and see if it's possible.
@@smp2 please! Man that would be a great help!
FFFFFFFFUUUUUUUK no thank you. IDK jack shit about Resolve and just tried to record some shots to edit later. Just getting the ISO file folders to import at all isn't working. Something else must be wrong.