Sending Midi-command on Wholehog 3

Hello Nalle, I have looked at your issue and I think the command you are seeing from the Hog is a MSC Go for Cue 2 of Cuelist 1.

I was able to get the message you needed sent from the Hog with the following syntax

MSh1/f0 7f 01 06 07 f7

Playing the cue with the Output Midi String Macro above will also send the MSC Go command for the cue, which is what you were originally seeing. In the Cuelist Options window there is an option to Suppress MSC Out, this will only allow the Midi Macro to be sent and not the MSC Go for the Cue.

Thanks,
Mitch

Nalle,

Mitch is absolutely correct.

There is also a way to disable MSC out for all cuelists, if you'd like. This will not interfere with sending MIDI strings.

Setup -> Network
Click on the Hog3 Console.
Click the Settings button.
On the MIDI tab, deselect MSC Out.

Another thing that I noticed is that your MMC command string is to send a Record Exit (punch out) command. I'm not sure if this is what your device is expecting, but it would make more sense to me if you were sending a play message.

This would be the syntax to send a MMC Play message to device 1 from the Wholehog 3 console:

MSh1/f0 7f 01 06 02 f7

I hope this helps.

Thank you both for the quick replies!
I am now a little wiser about the MSC function of the Wholhog 3.
Now for the $10 000 question/problem:

I have entered the above mentioned syntaxes in the Macros field in the cuelist and the Wholehog has accepted the format although it removes the zeroes in 01 06 02, becoming 1 6 2. I believe this to be normal?

When running the cues and MSC is enabled I can get a readout from the MIDI which looks like a standard MSC message (mentioned above) however, there is no sign of the midistring entered into the macros field. When supressing MSC the readout from the MIDI is nonexistant.

Is there something I have to do to enable MIDIsyntax in the Cuelist?

Thank you for all your help!

Regards
Nalle

Hello, if the cue syntax is sent, the the MIDI string should be sent as well.

Is there any chance you have the console set to a different number than what is being used in the MIDI string?

For example if the following syntax is used, MSh1/f0 7f 01 06 02 f7, this message will only be sent out if the console is set to console number 1.

In the start show window there is a button called SETTING, select this and there will be options for the Console Number and Port Number, check to see if the console is set to number 1.

Thanks,
Mitch

Hello Mitch!The device ID is 1 and Device Group ID is 112, standard settings so to speak, but still no output from the desk. I have also tried this one a Hog IPC and there is no change.Regards, Nalle.

To be a big wiser:

www.borg.com/~jglatt/tech/showctl.htm

For your problem:

I think you don't set the console to Midi out...


Amir

Hello Nalle, in the Hog 3 Start window where you select Launch Existing Show, Create New Show etc, there is a button SETTINGS. Press this and check the console number there.

Thanks,
Mitch

Nalle,

What software version are you currently using?
I don't recall that we've had any problems with MIDI strings lately, but I'd be glad to try and duplicate your setup here in our test lab.

How are you arriving at the conclusion that the string from the comment macro isn't being sent? Are you using something to view your data, or just inferring this because your receiving device isn't working?

To offer a couple of points of clarification:

1) MSC Out does not have to be enabled to send MIDI strings using comment macros.

2) The syntax for the MIDI string begins with the format MSh1.
MS = MIDI String comment macro
h = Send output from the console. This could also be i if you are using one of our MIDI / Timecode processor rack units.
1 = The network number of the device to send from. Mitch described above how to determine this on the console. On the MIDI / Timecode processor this is the large number displayed on the screen during normal operation.

MSh1 is the most common variation, but it may not be correct for your setup.

Hello again guys!

Thanks for all your help with this problem.

The software version we're using is 1.4.1.1129.
The Device ID in the settings window is nr 1.

I have connected the MIDI out from the console to MIDI IN on a computer running a program called MIDIview which lets you see all I/O traffic over a user-specified MIDI-interface. First I connected the Yamaha DM2000 to get the working MIDI-string which I have used for some time. The software got the MIDI-string and also a few other MIDI-strings that I tried to send from the Yamaha.

I then disconnected the Yamaha desk and plugged in the Wholehog, With the same cables. When MSC is enabled i get the MSC-code, no problem, and the value changes as it should depending on the cue-list number, but the MSxxxxxxxxx syntax is nowhere to be seen.

In otger words; I'm able to see the MSC-MIDIcommands sent by the Wholehog software, but not the standard MIDI-strings.

I've tried using a Dell PC running the wholehog software and a M-audio MIDI-interface, and I've also tried using an IPC but the results are the same. I've also checked and re-checked the syntax for any errors on my part, but everything looks ok.

Soo... I hope you can still help me! :)

Regards,
Nalle

Nalle,

I didn't realize that you were using a Hog iPC. I had been testing this using a Wholehog 3 console. I'll try it with a Hog iPC in our test lab on Monday to make sure that we don't have any problems sending MIDI strings from Hog 3PC.

I'll let you know what I find.

Thanks.

Hello Tom!

We are using a HOG-PC 3 system but I have borrowed an IPC to try an isolate the problem. :)

Thanks!
Nalle

Nalle,

It looks like we currently have a problem with sending MIDI strings from our Hog 3PC products. I've opened bug #9733 for this issue and I've added your comments to the defect.

One of our developers will take a look at this problem and I'll let you know when I get an update.

Thanks for the good report.

Nalle,

One of our developers has tracked down what's happening here and believes that he has a fix for it. I'm still waiting to get a software drop that I can test this with, but I wanted you to know that we're hoping to get this fixed for our next software release.

Thanks.

Hello again!

Thank you for the information! I hope the next release will be out soon =)

Regards,
Nalle.