Transport (jog wheel) Issues

Hi, I encountered the following issue

The jog bar isn’t working properly. I’m referring to the jog wheel. Forward (right) works correctly, but Rewind (left) doesn’t. I tried three different Mackie controllers, and the problem persists. According to the MIDI activity monitor, when I turn the wheel to the left, it receives MIDI but it doesn’t send out MIDI messages or it cuts out abruptly. But turning it to the right works as expected.

Thanks

1 Like

I’m encountering the same issue (iCon QCon G2 with mackie control). If I set the project display to “Timecode” it works, but on Bars+Beats it only jogs back to the start of the bar where the playhead currently is. This issue hasn’t occured before I updated to 14.0.30 so I’m thinking it might be related.

1 Like

Thanks, i’ve tried that and it works somehow. Maybe in the next update it will be fixed

Verified on both counts (issue and resolution) using SSL UF1 as well.

2 Likes

Same here. 14.0.30 and SSL UF1

Using the VI-M and tried changing to timecode but still won’t jog left.
This is not good enough from Steinberg . I hope it is fixed soon as I work with this 8 hours a day.

2 Likes

Tnx. I thought my controller was broken. I don’t see any relevant bugfixes in 14.0.30 so I will revert to .20. 8 hours is on the optimistic. Midi remote was corrupted in 12.0.41 and is still not fixed. They introduced bugs in jog functions in 8.5.0 and they are not fixed. Some one at Steinberg really hates remote controllers.

Hi,

This is a known and already reported issue.

1 Like

Thank you Martin

A report of a issue is not a solution.

1 Like

Hi,

At this moment, for the users, it is a solution. You don’t have to search for a solution, because there is none (apart from reverting back to an older version). You cannot change it and you don’t have to report it again.

3 Likes

No, nothing is solved. Reverting to a older version is a solution, but Steinberg download tools can not do that. So you need a guide for the poor users that does not have a backup.

Hi,

If you know a better solution, please share it. Everyone in this thread will be happy. Thank you for your valuable contribution.

1 Like

In the other topic a partial solution was posted, so I removed the solved checkbox here and added it to the linked post below.

Mackie Control JogWheel not responding correctly? for a (limited) workaround

Generic Remotes still works. Midi remote scripts for MCU is reported to be useful. It might be a work-around. But claiming a report is a solution is bogus, so many issues are reported and so few are fixed. But it is interesting. The 14.0.30 was build on 22 May. So about 2 weeks on internal testing and not found. Is there any internal testing of midi controllers before release?

1 Like

Please note my (edited) post above

FWIW, adding a Secondary Time Display (presumably Bars+Beats) and leaving Primary as Timecode also works. However, it seems to cut the resolution of my UF1 jog wheel down about 1/3.

I’m working on a MidiRemote with custom script to mathematically increase the resolution by some factor and will post that if I get anywhere with it.

The Midi Remote Script Editor isn’t exactly my strongest skillset, so if someone else is an expert and can whip it up, that may be a good work-around as well.

Update: I am NOT doing this. After about an hour of ChatGPT hallucinating with truly remarkable “solutions,” (no, really. The things it was saying simply didn’t exist) it turns out I can’t use the MIDI remote API with the SSL UF1 since it’s Mackie. If someone like @m.c has the time to verify this, then I would love to be corrected.

So adding a Secondary Time Display is indeed a work-around, however the scrub amount is cut to 1/3 of the original (I misspoke earlier when I said it reduced by about 1/3, rather it is reduced to about 1/3).

Steinberg have broken it ,so the solution to me is simple…just unbreak it. :nerd_face: :+1:

Hi,

Agree. This is the only proper solution. And I’m sure, Steinberg will fix it in the next update.

So far, here on the forum, we have kept the users informed that this is already a known and reported issue, and provide at least some kind of workaround.

1 Like