tyrebo

I don't use a control surface and have nothing connected to the hub, but I made the change you suggested anyway just now. I have been working all day with no problems after changing threads to automatic. Some more trouble free working hours will verify that was the solution. Thanks for your suggestions. T

have not had random disconnects. When I first got the M1, I had several problems with the original AF cables with adapters, Arturia seemed a bit baffled, or not yet familiar with M1 issues and their stuff. I am connected directly, with a USB mini (or is it micro?) to USB 3.1 cable, as they suggested trying. I'm still not certain if it's a LPX issue, or the Mac, or the Audiofuse. I'll try setting threads to automatic. Thanks for your reply- T

when using an Arturia AudioFuse interface, connected via USB 3.1, when I hit play or record, there is this start/stop stuttering, eventually it starts. Shown here cycling is on, but it makes no difference. Also, whether the Mac, the Audiofuse, or both, is powered externally makes no difference. The CPU meter shows no unusual activity during this. here's a link showing the issue, and a jpeg of the settings is attached, as soon as I change the input and output devices to anything other than the Audiofuse, it works fine. Should I consider this an LPX issue to address, or should I contact Arturia? (rarely a satisfying experience). Until now I've tolerated this, but now I'm doing much more work. Any input much appreciated. Tyler

I'm marking this as a solution, not because the cause of the problem is revealed, but because the undo, after the fact, is here.

aside from the above good advice, turning on plugin latency compensation should take care of any problems. Even if you have your mix bus loaded with plugins, your monitoring, and your bounces, should be fine

I'll try that method too, changing it in the list worked as well. The beat mapping/smart tempo question gets back to why this happened over multiple older projects. I've not intentionally used those tools. Slipping fingers, mystery shortcuts, and this football field trackpad can send me to mistake hell very quickly in LPX so it's possible, but it is too consistent. I always set the project BPM in the LCD display initially, why it changed remains a mystery. Thanks for the help, at least I can see the problem, and fix it in my projects.

I didn't know this, but in the tempo list the BPM shown can be selected and changed, corrected. Of course Locking/unlocking SMPTE Position of audio regions probably needs attention. So I can fix older projects that have to be opened in 10.8.1, but I still have no idea why this is occurring.

no, a little different. Any new project originated in 10.8.1 shows no such discrepancy between the list tempo and the time/beats display, which is also the bpm specified there at project creation. Of course any bounces from those are fine. Only the older projects reopened, I'd have to open several more to see if it happens every time, but I hope to actually get back to work on the first one I reported here. Still of interest that older bounces from those projects are accurate. I just can't track when/what versions, this may show itself

well there it is! I'd never opened that before. The project bouncing out too fast shows 94.2821, the project working properly is the correct 94, as set. How this happened at some point, I have no idea, nor how to correct it back to 94 as specified originally. At any rate, here's clear evidence of the problem finally, thank you. I was about to drop it as I'm the only one that seems to have experienced this.

David, not sure where I might find a tempo list, but scrolling the head from beginning to end shows no change in the control bar display throughout. Fufilth(hah!) the tempo line is solid beginning to end with no automation points. Thank you both for input, it remains a mystery. I'm encountering this again in another old project just newly opened

further info- I found an old stereo mix bounce of the project, way before 10.8.1. BPM is accurate. All this seems to have to do with older projects opened anew in 10.8.1. Of course it could be pre 10.8.1, but this is when I discovered it

I read through the info, thank you. They do seem to have complicated things for us with simple minds. However, "Keep project tempo" is selected, both versions, plugin compensation is on and buffer settings set in main prefs so cross-project. Should have been ok

An older LPX version would be helpful for this, but no I don't have one. Yes your interpretation of my explanation is correct and perhaps this will be clearer- Project One- Originally created in 2017. Don’t recall what version of LPX. It includes audio tracks and virtual instrument midi tracks. It has now been opened in v10.8.1, some work done, stem and test mix bounces revealed slightly inaccurate BPM, too fast. Project Two- Created new in v10.8.1. Identical BPM, time sig, sample rate as “One”. Then each track from “One” was “added” with the file browser. Stem and test mix bounces have accurate BPM. The jpeg above is click bounces of each in a NEW test project just to show the offset. Top pair is start, mid pair mid song showing drift, bottom pair shows clear ~5 second offset at end of song. I hope this clears things up. I'll just proceed with Two, but I have several other older projects to continue work in 10.8.1. I am pondering some version evolution of settings that makes assumptions opening older projects. Thanks for tolerating all this. T

as I said I seem to be creating more confusion than anything else. I thought I described the new and the old. I'll have to try again after more coffee

no, the "old" and the "new" as described. The screenshots are of the click bounces from the 2 projects, displayed in a new clean project just to show. Just describing all this, I create more confusion than I solve !!