Automation Blocks plugin: Trouble when setting up rendering from bin

[HAVAX]

Hey guys, it seems i can't wrap my head around the ''for each project item" block.

From my understanding each item present in my premiere bin is saved temporarely in the ''my item'' variable.

When i add an ''add to media encoder'' block inside the ''for each project item", it works only with ''active sequence'' but not when i add the ''my item'' variable.

Am i missing something?

My objective is to export multiple sequences from one premiere bin in a predetermined folder.

It seems like it only works if i use elements from the ''Pr project item'' tab in Automation block.

I attached an image so you can see what am i talking about. I circled in pink the variable i think is the problem.

 Thank you so much for your attention.

[Mathias Moehl]

Hi @HAVAX,

you are correct that "my item" is temporarily replaced by each item in the chosen bin. In other words, in your code the "add to Adobe Media Encoder queue" block is executed many times - one time for each of the items - and each time "my item" is replaced by a different item in that folder.

I think the issue here is the filtering. The "for each item" block contains these checkboxes to decide, which items you actually want to process. Since you also checked "bins" and "other files", Automation Blocks will try to send any subbins or text files, for example, to Adobe Media Encoder, too. But since Media Encoder can only render footage and sequences, this will fail.

See attached screenshot:

[HAVAX]

Hey i don't think that is the issue, i tested every single combination o those checkboxes and it still it is not executing properly.

 I also checked the console and it says this: ''execution result:"TypeError: null is not an object (line 6)'', still can't find the error...

Everything  else in the console seems right to me (filepath, export module, file name ecc)
Thank you for your reply 🙏🏻

(I attached the color code i get for the blocks when i execute the script, maybe you can get some more info with that)

[Mathias Moehl]

I suggest that you add a write to console block before the "add to AME queue" block and use it to output "my Item".

Then in each iteration of the loop it will first print the item to the console before trying to add it to AME's queue. Then you know that the last item it outputs before the error message is the one that causes the issue and you can check if it is an item which actually can be queued.

The block where the execution stops is always highlighted. In your screenshot it looks like the "Send to AME" block is highlighted. If you took that screenshot after the error occurred, then this indicates that the error happened at that block.

[HAVAX]

Thank you for your suggestion!
I added the ''write to console block'' and i can see it's actually stopping on the first iteration of the loop. In the console i still get the ''TypeError: null is not an object (line 6)" as the final line of the console.

The problem is that is not even triggering the launch of AME or the queuing onf the sequence.

From my understanding

the first line is the ''write to console block''

the second is the ''add to AME block''

both seem right to me when i check each file path or Pr Item path.

I don't understand the last 2 lines i get in the console.

[Mathias Moehl]

Yes, the first line is the "write to console" and the second one comes from the "add to AME queue" block.
Do you see the same behavior if you remove the loop and just execute the "add to AME queue" with a single hardcoded project item (using the project item block, which is in there by default, instead of "my item")? If this also fails, we know that the issue is not the loop.

Also, are you using the most recent version (1.0.016) of Automation Blocks? It contains various bug fixes - for example issues with accessing project items which have extra spaces at the end of their names. Maybe such a kind of bug causes the problem that you cannot access the project item.

Concerning the "descructor final end point reached" message: You can ignore this. In a nutshell, it says that the script is done executing. The message is so complicated,  since "done executing" can mean different things like "this script is really finished completely" or "all commands which needed to be executed for now have been executed, but I am still waitinig for the render queue to finish and when that is done, I will continue executing more blocks again". In the latter situation you will see messages that some end points have been reached, but not yet the final end point.

[HAVAX]

I just tried the solution you proposed and it's still not working...

It's only partially working when i leave it to ''active sequence'' (default add to AME queue block object). I was expecting to see multiple entries (same number as items in my bin as ''for each item'' block implies) in AME, with each entry having the name of my bin sequences, but i only got the first one.

I am currently running the latest version, and in my sequences names ther's not any spaces in the naming.

If my sequences have different aspect ratio (1x1,9x16) it shouldn't matter right? (As export preset .epr i'm using h264 match source)

I can't figure out what's the problem.

[Mathias Moehl]

Are you able to share your project and Automation Blocks script? Can you send it to info@mamoworld.com

Then I can check if it works on my machine or not.

[HAVAX]

Yes i'll send it to you right now, thanky you!