View Issue Details

IDProjectCategoryView StatusLast Update
0009747ardourbugspublic2024-09-16 23:05
ReporterColincampbellvoice Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
PlatformMicrosoftOSWindowsOS Version11
Summary0009747: Arm RECORD arms ALL tracks.
DescriptionWith Mackie control, while intending to arm one track to record, all tracks arm for recording.
Steps To Reproduce
Use Mackie control surface, in my case a Tascam model 12, create a few tracks and arm the first few. From then on, arming and disarming is global (all tracks.)
Additional InformationMy control surface is known good on many other DAWS that use Mackie Control. (MCU)
TagsNo tags attached.

Activities

paul

2024-08-01 03:27

administrator   ~0028880

You would need to get a debug build (available on nightly.ardour.org), run it from the command line with -D mackiecontrol and find out what the button sends.

Or use a MIDI monitor app for windows, connected to the Tascam 12, to discover the same thing.

I have multiple Mackie Control devices for testing, and have never seen this behavior using any of them.

Colincampbellvoice

2024-08-01 04:04

reporter   ~0028882

This behavior is NOT exhibited while using the Tascam Model 12 in DAW Control Mode with Adobe Audition, Presonus Studio One or Reaper which arm all tracks normally, one at a time. Adobe Audion and Reaper are simply set to receive MCU (generic Mackie control) while Studio One is set to receive the Tascam Model 12 specifically. I only see this behavior using the Tascam Model 12 with Ardour. I have tested it multiple times. It would seem to me that the Tascam is sending the prescribed code for "arm track" since the other DAW's do not have the issue.

paul

2024-08-01 04:37

administrator   ~0028883

I have 3 MCP devices here on my desk. They all send the MCP message for the global rec-arm button. This does not lead to the behavior you describe.

Ergo, either the Tascam 12 sends something different, or there is something else about your session that leads to the behavior indepdendently of Mackie Control.

j4strngs

2024-08-17 02:00

reporter   ~0028931

I also have a Model 12 and can confirm this behavior.
Attaching a midimonitor to the M12:DAW_CONTROL_OUT shows engaging the channel record arm sends Ch1 note_on=$notenum vel=127
(There are 8 strips: M12 Ch1 sends C -1, Ch8 sends G -1)
Attaching it to ardour:mackiecontrol_out and using any M12 track arm button track arm results in ardour sending every track an arm mesg
There are 9 msgs sent. I'm not sure what the first one is bound to, but the rest is the array of channels
Ardour+TascamM12_Out.png (416,003 bytes)

Colincampbellvoice

2024-08-17 02:43

reporter   ~0028932

Thank you. I’m not crazy. I do lack the knowledge to do that research. When Ardour was the only DAW out of 4 to exhibit this behavior, I felt the Tascam was surely not at fault.

j4strngs

2024-09-16 20:42

reporter   ~0028979

I just built 8.7 and this works properly now. Thanks!

Colincampbellvoice

2024-09-16 21:48

reporter   ~0028980

I just downloaded and installed 8.7 and I am sorry to say that the stated behavior remains. With my Tascam Model 12 in DAW control mode and Ardour set to Mackie Control, arming one track for RECORD on the controller arms ALL tracks for RECORD in Ardour.

j4strngs

2024-09-16 23:05

reporter   ~0028981

You are correct sir. I was not in DAw mode

Issue History

Date Modified Username Field Change
2024-07-19 14:31 Colincampbellvoice New Issue
2024-08-01 03:27 paul Note Added: 0028880
2024-08-01 04:04 Colincampbellvoice Note Added: 0028882
2024-08-01 04:37 paul Note Added: 0028883
2024-08-17 02:00 j4strngs Note Added: 0028931
2024-08-17 02:00 j4strngs File Added: Ardour+TascamM12_Out.png
2024-08-17 02:00 j4strngs File Added: Tascam_Model_12_track_arm_MIDI_output.png
2024-08-17 02:43 Colincampbellvoice Note Added: 0028932
2024-09-16 20:42 j4strngs Note Added: 0028979
2024-09-16 21:48 Colincampbellvoice Note Added: 0028980
2024-09-16 23:05 j4strngs Note Added: 0028981