[quote="Smarty"]I got an error, I think it said something like "protocol not supported" or something like that. Mike, The error that the Profile was refering to is, in the time code menue. The Odetics mode does not support regen time code. Just change the time code to another option and it works great. I use 4 channels Lance/Profile/Odetics on my golf show all the time and it works great.[/quote] Nice one.. I had never heard of that error, and I cannot imagine that certain protocals would be options. Would be nice if the error told you why it wasn't supported. When we do the MSNBC stuff, (not often) they seem to want a profile, because that is what we always use, which makes sense, but the quirks with the Lance I would rather not deal with. We need to be able to do loops (crosstalk boxes, etc). So we need to use odetics, restriping and all that adds to the confusion. We have to ask/fight to just give us a simple Fast Forward with the Lance. Only two channels but a lot easier to load since the tape ops we bring aren't usually familair with loading profiles. If we ever get an EVS only truck we would be in real trouble, they would have to hire and EVS op, wouldn't have a clue how to load stuff into an EVS. Bill

I got an error, I think it said something like "protocol not supported" or something like that. Mike, The error that the Profile was refering to is, in the time code menue. The Odetics mode does not support regen time code. Just change the time code to another option and it works great. I use 4 channels Lance/Profile/Odetics on my golf show all the time and it works great.

[quote="Mike Cumbo"][quote="Bill D"][quote="Mike Cumbo"]Is Odetics protocol included or is it an option?[/quote] I assume you mean an option on the profile? No it is one of the many ways you can control a profile, under one of the windows menus in the VDR panel of the profile.[/quote] Bill, about two weeks back I was on a truck that used a Profile, rather then a Fast Forward or SpotBox, and I tried to change the Profile to Odetics mode. I got an error, I think it said something like "protocol not supported" or something like that. That Is why I asked if Odetics was an option. I had to use the BVW protocol which on that show really didn't make much difference.[/quote] That's another issue I kept having. The only thing was it seemed that the machine would still respond to transport commands. All really wierd stuff. I hope Grass Valley/Bill Lance figures it out at some point.

[quote="Bill D"][quote="Mike Cumbo"]Is Odetics protocol included or is it an option?[/quote] I assume you mean an option on the profile? No it is one of the many ways you can control a profile, under one of the windows menus in the VDR panel of the profile.[/quote] Bill, about two weeks back I was on a truck that used a Profile, rather then a Fast Forward or SpotBox, and I tried to change the Profile to Odetics mode. I got an error, I think it said something like "protocol not supported" or something like that. That Is why I asked if Odetics was an option. I had to use the BVW protocol which on that show really didn't make much difference.

[quote="Bill D"]We have had problems in the past when doing MSNBC shows in trucks. We tried to run profile's in odetics mode using a Lance. Here is an email response from Bill Lance, it was from end of 2004, but I don't think it has changed at all. 1) The Profile must be in Odetics mode to run loops. The commands that are required to do loops are not supported on the Profile when it's in BVW mode. 2) The Profile has a strange idiosyncracy (or a bug) when in Odetics. When it's in Odetics mode, the profile will add the starting time of the clip to the inpoint that the controller is asking for, and try to cue to that time. For example, if the clip starts at 1:00:00:00 and your intime on the controller is 1:00:00:00, the profile will try to cue to 2:00:00:00. It's bizarre, and no one at Tek has ever been able to explain to my why it does that, but it does. Since 2:00:00:00 is possibly a non-existent timecode, the profile just sits there, and doesn't cue. There are two ways around the problem: you can either re-stripe the clip in the profile so that it starts at 00:00:00:00, or you can switch the controller menu to use 'timer' mode instead of TC. This will circumvent the problem.[/quote] You are a genius! Thank you!

[quote="Mike Cumbo"]Is Odetics protocol included or is it an option?[/quote] I assume you mean an option on the profile? No it is one of the many ways you can control a profile, under one of the windows menus in the VDR panel of the profile.

Is Odetics protocol included or is it an option?

We have had problems in the past when doing MSNBC shows in trucks. We tried to run profile's in odetics mode using a Lance. Here is an email response from Bill Lance, it was from end of 2004, but I don't think it has changed at all. 1) The Profile must be in Odetics mode to run loops. The commands that are required to do loops are not supported on the Profile when it's in BVW mode. 2) The Profile has a strange idiosyncracy (or a bug) when in Odetics. When it's in Odetics mode, the profile will add the starting time of the clip to the inpoint that the controller is asking for, and try to cue to that time. For example, if the clip starts at 1:00:00:00 and your intime on the controller is 1:00:00:00, the profile will try to cue to 2:00:00:00. It's bizarre, and no one at Tek has ever been able to explain to my why it does that, but it does. Since 2:00:00:00 is possibly a non-existent timecode, the profile just sits there, and doesn't cue. There are two ways around the problem: you can either re-stripe the clip in the profile so that it starts at 00:00:00:00, or you can switch the controller menu to use 'timer' mode instead of TC. This will circumvent the problem.

Clip names are limited to nine letters (best I can tell from the manual) but it's best to keep the names short.

[quote="Smarty"]Tom- Make sure menu item #4 (CLIP STORE/RECALL) is turned on. In Odetics mode you must recall the clip (even if there is only one clip).[/quote] I understand. The clip list is accessible, although only a certain number of clips show up on the lance. But that's regardless of the fact that I can't functionally use the clip once it has been called up.

Tom- Make sure menu item #4 (CLIP STORE/RECALL) is turned on. In Odetics mode you must recall the clip (even if there is only one clip).

I have never been able to get a profile to work properly with the Lance in Odetics mode. It seemed I was able to use transport functions but when I marked an In and Out for a clip and tried to cue that clip up, it would either error out or do nothing at all. Also, in the clip list on the lance, only certain clips would show up. I've had the problem on two trucks. Really awkward. I've used the SpotBox in odetics mode and worked like a charm every time. Any thoughts?

The "preserve loop" function was added in version three to prevent losing a loop when calling up registers involving other channels. Let's say you had a loop running on channel C and you wanted to call up a 3 channel move on A,B & D. In the earlier versions of software, when you called up the register for the new move, channel C would forget its in and out points (and, indeed the fact that it was looping!) and the animation on C would run past it's end point - disastrous if the loop was the background for the graphics panel you were waiting to wipe off. Bill added the loop lock to v3 so that when you call up any other register (even if it involves the looping channel!) the exisiting loop keeps looping. The only way to break the loop is to send a STOP trigger to the channel (or hit stop with that channel lit on the panel). Now you can call up a new animation/loop whatever. happy looping! dave

[quote="Tom Maslak"]First of all, the Odetics worked... I should've thought of it. I fell victim to the dreaded brain fart... Second, in regards to the Lance/Spotbox issue... I had a spotbox and was controlling 4 channels individually with 4 device addresses, and built 2 EMEMs that would call up clips on Ch. 3 & 4 (learn recall only enabled for those channels), and loop them. That was fine. The problem I had was when I called up any EMEM after that for CH. 1 or 1&2 (with only those channels enabled for learn recall), the clips in CH. 3 &4 would cease to loop and just play through the end of the clip. Anyone ever seen this? Thanks![/quote] I think that is 'normal'. There is a menu option on the Lance that says preserve loop. If you turn this on for ch 3 and 4, then your loop should stay forever. Or I guess until you re-address that channel with an emem recall. Bill

First of all, the Odetics worked... I should've thought of it. I fell victim to the dreaded brain fart... Second, in regards to the Lance/Spotbox issue... I had a spotbox and was controlling 4 channels individually with 4 device addresses, and built 2 EMEMs that would call up clips on Ch. 3 & 4 (learn recall only enabled for those channels), and loop them. That was fine. The problem I had was when I called up any EMEM after that for CH. 1 or 1&2 (with only those channels enabled for learn recall), the clips in CH. 3 &4 would cease to loop and just play through the end of the clip. Anyone ever seen this? Thanks!

two words...... Odetics Protocol. Have your engineers change the box to Odetics if they know how to do it! As for the Lance... while it says it's looping, it IS looping. The Lance sent the command to Loop, but the box isn't set up right for that feature to happen.

I had the same problem using a SpotBox/Lance config. I was on the dual, and both me and the home show TD couldn't get the Loop to work, although the Lance display did say it was looping. Wonderful duals; the other guy rebooted twice to see if it fixed the problem - without warning me first. We were putting wings on some 4x3 footage and the director looked at me disapprovingly every time the animation went away. Go figure!! Any thoughts?

Tom - I use this exact same set up (Lance/Profile). The trick is to set up the Profile in the Oditics protocol instead of the BVW mode. I find that the Profile cues up ever so slightly slower, but as long as you are aware of the cue time then it works great. The Oditics protocol is what is used on the spot box, and the Profile works the same. You can call up individual clips or just make 1 big clip. If you make 1 big clip record more time than what you need because when you hit stop that is the length of the clip, you can?t add any more time to the clip, but you can record over what you have already recorded.