24 postsPage 1 of 2
1, 2
It has happened to me several times now that I could not label individual channel strips in the MixerConsole.

A double-click in the labeling field does indeed highlight the existing text in blue, but re-labeling or even deleting is not possible.

Only after I close the mixer and open again, a new labeling is possible.
Last edited by maschinenwart on Thu Mar 03, 2022 1:42 am, edited 1 time in total.

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by garyshepherd on Fri Oct 22, 2021 10:55 am
Is it a Midi Instrument track without an Instrument?

Please note that I may express opinions that are different from yours but I do not intend to cause offence.
____________
iMac 27" 3.3 GHz Intel Core i5, 32 GB Ram, Monterey 12.7, 64 bit, Studio One 6.5 Professional (always the latest) , Reason 11, Melodyne 5 Studio, Digital Performer 11.2, Korg Legacy Wavestation and M1, Arturia minimoog V, Helix Native 3.71, Bias FX 2 Elite, Superior Drummer 3, EZkeys, EZbass, Nektar Panorama T4, Motu M4, Faderport 2018, Gibson Les Paul Standard, James Tyler Variax JTV-59 and other gear.
User avatar
by maschinenwart on Fri Oct 22, 2021 3:02 pm
...it is not a specific channel. It happens with an audio channel or with an fx channel

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by maschinenwart on Sun Oct 24, 2021 8:41 am
However, I could only detect this malfunction as soon as the console is decoupled.

Before that i inserted some insert effect or set a send effect or removed it again. the channel type doesn't matter at all. sometimes i had to repeat this a few times...

1. Open and save a new Song
2. Create different channel types (Audio, Instrument, Bus and VCA)
3. Open Console and decouple it
4. Rename any channel - it should be work!
5. Insert some insert effect or set a send effect to any channel
6. Rename any channel - if this work, repeat No.5 or delete the insert effect
7. Rename any channel - now it should not work
8. Close and reopen the console - now it should work!

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by maschinenwart on Thu Mar 03, 2022 1:38 am
The problem is still present even in version 5.5.1.

I still have a problem with labeling individual mixer channels.

But the problem only occurs when the mixer is disengaged!

I have created here for a short video.

[ Play Quicktime file ] MixerProblem.mp4 [ 33.93 MiB | Viewed 5782 times ]


:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by ianaeillo on Thu Mar 03, 2022 3:26 am
I run into this too. After a quick panic check to make sure I didn’t accidentally hit any keyboard shortcuts, I flip back to the edit window and flip back to the mixer and it’s fine. Odd little bug. Can’t figure out how to trigger it.

Studio One Pro 5.5, Studio One Pro 6.12, Faderport 16, Faderport Classic (1.45), Metric Halo ULN-8 MKIV, Presonus Quantum, Presonus Quantum 2, Ferrofish Pulse 16, (2) Digimax DP88, Audient ASP800, BLA HD192, 27-Inch Late 2012 3.2GHZ i5 32 GB 1600 DDR3, 2Tb SSD, 10.13.6 High Sierra + 10.14 Mojave + Windows 10
User avatar
by roland1 on Thu Mar 03, 2022 2:29 pm
ianaeillo wroteI run into this too. After a quick panic check to make sure I didn’t accidentally hit any keyboard shortcuts, I flip back to the edit window and flip back to the mixer and it’s fine. Odd little bug. Can’t figure out how to trigger it.


Interesting what you say: that you flip to another action and then back, which solves the problem.

This is exactly what happens with the "BIGFOOT" stuck MIDI note issue that's being discussed. There too, you have to do something else, and then when you come back, the problem is fixed.

Perhaps underneath all these odd issues is a GUI problem where some part of the code for the visual presentation interferes with other aspects of the code. No idea what...but there it is.

Studio One Pro (v5) on i7 7700 win10 PC w16GB RAM and a Mac Pro Tower (w/RME & Focusrite interfaces.)

I use S1 as an author/musician/multi-media artist.
My work includes the newly released: Clearing a Path to Joy (And finding contentment along the way) [AuroraSkyPublishing.com]
and my upcoming music video, Too Big To Fail, which introduces Citizen Based Social Planning — "the next step in the evolution of democracy." You know...typical everyday stuff. :)
User avatar
by maschinenwart on Thu Mar 03, 2022 3:35 pm
roland1 wrote
...Perhaps underneath all these odd issues is a GUI problem...


I have already thought of that.
as if an invisible layer would lay over it or something like that

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by matthewgorman on Wed Mar 09, 2022 11:41 am
Hi all.

Can someone that is experiencing this issue please take the time to upload a .song file where this is happening? The developers are actively engaged and requesting any affected files to help get to the root cause.

Thanks for your cooperation

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5
User avatar
by maschinenwart on Wed Mar 09, 2022 12:19 pm
Hi Matt,

the error can be reproduced with a completely new song. i tried this on both my systems. sometimes you have to repeat the steps described above.

I have this error on two different systems. On my iMac27 (Big Sur) and on my MacBook Pro (Monterey) and before on Mojave. The MacBook is completely reinstalled without any critical PlugIns.

Best
Eric

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by matthewgorman on Wed Mar 09, 2022 12:38 pm
maschinenwart wroteHi Matt,

the error can be reproduced with a completely new song. i tried this on both my systems. sometimes you have to repeat the steps described above.

I have this error on two different systems. On my iMac27 (Big Sur) and on my MacBook Pro (Monterey) and before on Mojave. The MacBook is completely reinstalled without any critical PlugIns.

Best
Eric


I would like to get the developers the file they are looking for. It will make for a faster debug. If you see it happen, close the song and attach the file.

Thanks

Matt

Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon
Lenovo Thinkpad E520, Windows 7 64bit, 8 GB RAM, Intel i5 Processor

S1Pro V5
User avatar
by maschinenwart on Wed Mar 09, 2022 1:22 pm
...here the desired file

Label_Test.zip
(26.27 KiB) Downloaded 71 times

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by roland1 on Wed Mar 09, 2022 1:54 pm
maschinenwart wrote
roland1 wrote
...Perhaps underneath all these odd issues is a GUI problem...


I have already thought of that.
as if an invisible layer would lay over it or something like that


There are now at least three of us thinking this way — GUI issue that has a widespread affect on various features (requiring keyboard input?).

Studio One Pro (v5) on i7 7700 win10 PC w16GB RAM and a Mac Pro Tower (w/RME & Focusrite interfaces.)

I use S1 as an author/musician/multi-media artist.
My work includes the newly released: Clearing a Path to Joy (And finding contentment along the way) [AuroraSkyPublishing.com]
and my upcoming music video, Too Big To Fail, which introduces Citizen Based Social Planning — "the next step in the evolution of democracy." You know...typical everyday stuff. :)
User avatar
by babulmukherjee on Fri Mar 11, 2022 4:52 pm
I have been fighting this for a while also on latest StudioOne on Mac BigSur.

Not only are the channel/track labels blocked from input as others have said, same goes for other entry points on the channel/track strip (like Preamp gain or Input gain, Pan, etc). Sometimes I can "free" it where I can enter data, but I have not been able to reliably figure out how to work around.

I have songs I can share which exhibit this problem, but would prefer to send directly to support.

Anything I can do to assist troubleshoot this. Thanks!

Apple Mac Studio Max 64gb RAM, Ventura, RME UFX III, Studio One 6, Genelec 8330A w/7350A, Sennheiser HD 650
User avatar
by maschinenwart on Sat Mar 12, 2022 4:29 am
babulmukherjee wrote
...not only are the channel/track labels blocked from input as others have said, same goes for other entry points on the channel/track strip (like Preamp gain or Input gain, Pan, etc)..



that's right, I have also already noticed...

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by babulmukherjee on Thu Apr 14, 2022 7:40 am
Still a problem in StudioOne 5.5.2.

From my session last night, it seems like if I switch to another app (like a browser) and come back to StudioOne, I am able to enter values again.

Apple Mac Studio Max 64gb RAM, Ventura, RME UFX III, Studio One 6, Genelec 8330A w/7350A, Sennheiser HD 650
User avatar
by maschinenwart on Thu Apr 14, 2022 10:51 am
babulmukherjee wroteStill a problem in StudioOne 5.5.2.

From my session last night, it seems like if I switch to another app (like a browser) and come back to StudioOne, I am able to enter values again.




...it should be enough to close the mixer and open it again

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by jazzundso on Thu Apr 14, 2022 1:40 pm
babulmukherjee wroteStill a problem in StudioOne 5.5.2.

This won't change until there are proper repro steps. If we can't reproduce it, there's no way to fix it.

Lukas Ruschitzka
Studio One Specialist
Advanced Studio One Tutorials || Free Studio One Scripts || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ]

Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate
User avatar
by maschinenwart on Sat Apr 16, 2022 2:02 pm
jazzundso wrote
babulmukherjee wroteStill a problem in StudioOne 5.5.2.

This won't change until there are proper repro steps. If we can't reproduce it, there's no way to fix it.



...I have always been able to reproduce the error on three different Mac computers.

My video tutorial and step by step procedure should be sufficient to provoke the error!? :roll:

:: iMacPro
:: MacBook Pro M1 Max
:: Ventura 13.6.1

:: Studio One 6.5.1
:: UAD Apollo 8 Ouad Thunderbolt (10.2.5)
:: StudioLive 16R Series III
User avatar
by teqnotic on Thu Jul 14, 2022 1:21 pm
I'm also experiencing the same. Whenever I have the mixer detached, I doubld click on the track name and cannot name it. All keyboard strokes are being recognized in the arrange window instead. For example, when trying to type in a track name, and I type "d" a track part I had selected gets duplicated. I'm using version 5.5.2 on a Mac Studio M1 max. This isn't an issue on Windows 11.

24 postsPage 1 of 2
1, 2

Who is online

Users browsing this forum: Tacman7 and 89 guests