cell command as NOP

[sweetness]

i have a cell command as NOP.
when blanking/bypassing should i just 1. leave it 2.remove it or 3. move it into the pre-commands before the post?

[jeanl]

mmm i'm not too sure what you mean by blanking/bypassing, but I don't think it will make any difference whether you leave it, remove it, or copy it elsewhere, unless I'm missing something. NOP does not do anything, as far as I know. But I'd be curious to hear what the experts have to say!
Jeanl

[mpucoder]

I'm not sure what the objective is. But - a NOP as a cell command has the effect of pausing the playback as cell commands, by definition, are non-seamless.

[blutach]

Must be a button there or something, then?

[mpucoder]

Not necessarily, but the presence of a cell command, even a NOP, makes the player finish the cell, execute the command, then start loading buffers for the next cell, causing a slight pause. It might be intentional to hold the last frame a little longer, or it could just be sloppy authoring.

[sweetness]

mmm i'm not too sure what you mean by blanking/bypassing
sorry for being a little unclear, but i meant blanking with vobblanker or bypassing (maybe should have said kill play back) with pgcedit. where both programs move the post's to pre's but warns if they is a cell command.
It might be intentional to hold the last frame a little longer, or it could just be sloppy authoring.
i knew NOP does not do anything directly but i thought it might have done something indirectly. if that's the case i'm just going to remove it. thanks

[blutach]

Well! I just got my first one of these.

It is a NOP cell command in the program before the layer break (which ends as a fade to black). So, it's probably like mpucoder says, just trying to hold the frame a bit.

In the interests of seamless playback, I have eliminated the cell command, and using PgcEdit, eliminated the layer break, too.

Anybody see a problem with this?

Regards