g&s productions wrotethe support wrote:I've logged your ticket with our development team, I do not have any information if or when this issue will be addressed. Wow!, that is disappointing,. Just can't believe this issue is not being looked at??. What was the last known version to actually work? |
snb1 wroteWorking with the arranger track seems to be buggy. Moving one section from one scratch pad to another seems to lock it up after a while. I love using the Arranger and Scratch Pad. What do you mean by lock up? I work with scratch pads, so I would like to try to recreate your issue at home... just curious.
Studio https://redpeakaudio.com
CPU: Intel Core i7-7700 (Kaby Lake) RAM: Kingston 2x8GB DDR4 2400MHz CL15 MoBo: Gigabyte B250-HD3P GPU: EVGA GTX 1080 FTW GAMING ACX 3.0, 8GB GDDR5 DAW: StudioOne 4.6.0 OS: Win 10 x64 Interface: Focusrite Saffire Pro 14 |
What do you mean by lock up? I work with scratch pads, so I would like to try to recreate your issue at home... just curious.[/quote]
If you send an 8 bar loop with an arranger on it to the scratch pad, and duplicate the scratch pad like 8 times. Open the arranger track by pressing the command key (i) and selecting the arranger track in the sequencer. Now try rearranging the arrangers by moving them to different scratch pads and tell me if you discover a bug in the process. Try copying them as well to different scratch pads. |
Okay, I'll try that.
Studio https://redpeakaudio.com
CPU: Intel Core i7-7700 (Kaby Lake) RAM: Kingston 2x8GB DDR4 2400MHz CL15 MoBo: Gigabyte B250-HD3P GPU: EVGA GTX 1080 FTW GAMING ACX 3.0, 8GB GDDR5 DAW: StudioOne 4.6.0 OS: Win 10 x64 Interface: Focusrite Saffire Pro 14 |
I just realized wait for midi is impossible for certain daws if they have the ability to route anything to the transport bar.
and daws with wait for midi can't route to the transport bar. So rewire or overdubbing are the only options. Ah I'd rather it be that way then. |
Users browsing this forum: No registered users and 79 guests