BUG con tracce midi & VSTi?

Buonasera a tutti.

Premessa:
Ho un mac book pro M2 MAX ed ho aggiornato all’ultima pre-relase il VST LIVE pro 2.

Ora la domanda: anche a voi capita questi (a mio parere)BUG?
vi spiego cosa mi succede.

BUG 1
Ho 2 song, entrambe divise ognuna per parti, ovvero strofa ritornello ponte ecc…

Per ogni song ho una traccia midi ( oltre le altre audio di sequenze) in cui mando il click per il metronomo con un suono diverso da quelli interni, usando groove agent 2.

Il problema è il seguente… ho inviato il click, ad una uscita separata apposita, che va nel mixer digitale in un canale apposito per il batterista.

Quando suono la song 1, tutto perfetto.

quando suono la song 2, il click me lo fa uscire nel master. devo andare mel mixer di live e ri-dirottare l’uscita sull’uscita che avevo dedicato.

se ora torno alla song 1 il metronomo suona regolarmente come programmato.

Se torno alla song 2 me lo rimette sul master!

Le ho provate di tutti i colori, ma non c’è verso, la song 2 suona con il metronomo sul master, devo spostarlo a mano. ma possibile sta cosa???
Sembra che con la traccia midi e il VST instrument abbia questi problemi…

BUG 2
Ho provato ad utilizzare il FLEXLOOP per capirne il funzionamento.
Dopo qualche minuto che lo uso, non funziona più bene.
Non prende “la prenotazione” della part che si sceglie.

Hi,

I’ve used an “Italian ↔ English” translator, but I am not sure if I understand everything.

Let me ask : Are you working with the latest version? You can download it here?

Bug #1
Can you give use access to your project? Then we can analyse it. Please use the “VST Live / Menu / Save Archive…” and save the project to empty folder. Zip that folder and drop it here or send me a PM:

Bug #2
We need more information what is not working.

See you
Michael.

Fantastico.
Domani (domenica) vi mando tutto.
Se riesco anche qualche screenshot x essere il più comprensibile possibile.

Thnks.

Good morning.

I am attaching the requested file.
I will try to explain as best as possible what is happening to me.

My computer:
Mac Book Pro 14’’ - M2 MAX 32gb 1Tb
I have two audio cards connected, but in the project I use the Mackie DL32R digital mixer, however the problem occurs even if I use the other one: RME FIREFACE800.

The problems I encounter are 4. (maybe it’s my fault I have been using this software for a very short time, but I have been using Cubase since 1990)
The projects are prepared in Cubase 14 pro, and exported for VSTLive2 pro.
I confirm that I have installed the latest pre release: 2.1.22.239

Error 1

  • Loading the “live Band” project in VSTlive2
  • I play song 1 (Johnny B Goode)
  • From the “johnny B goode” mixer I can see that track #15 is routed to the green mixer output called CLICK. (explanation: track #15 is a midi track. I use it with the GrooveAgent SE vst-instrument, to have a custom click sound)
  • so far so good.
  • I play song #2 (si Viaggiare)
  • From the “Si Viaggiare” mixer the equivalent track for the click is #18 but it comes out on the wrong output. Even if I manually correct it by inserting the “CLICK” output, it does not maintain the change.
    After playing the 1st song, and then playing the 2nd Song again, it comes back with the wrong output.
    NB.
    for example, the bass track on both “johnny B Goode” and “si viaggiare” is routed to its own output which in the mixer is called “BASSO” and in this case it maintains the setting on both songs. The only difference is that it is not a midi track but an audio track, I don’t know if that’s relevant.

Error 2
By clicking on the NOTES icon I can’t write on it, maybe it’s my fault, but I’ve tried everything.

Error 3
Using the FLEXLOOP after using it for a while it no longer takes my commands.
It doesn’t book the “part” I choose… or it skips incorrectly.

Error 4 (bonus):grin:
I discovered that even though it did NOT show the FLAG on Rosetta, VSTLIVE2 started in rosetta mode.
To make it start in ARM mode I first had to put the FLAG on rosetta, start it, close it, and remove the FLAG on rosetta.
Now it starts in ARM mode to verify it I clicked “next to the apple” on “VST Live” and chose About VST Live where it specifies next to the version number that it is in ARM mode.

I leave the link below to download my project
HELP - VSTLIVE2.zip
Thank you for your kindness and availability, I hope I have been helpful in solving the problems.
Greetings
Eugenio.

… thank you. I’ve requested there to get access to the project. Then I can start to analyse it.

/Michael.

- BUG#5

Good morning,

This morning I added another song to the playlist.

lyrics and Chord are visible correctly, but in track edit they are only present for half the song.

In the last part they are not seen, yet in lyrics edit they are there.

I created this song in Cubase and then exported it as a project for VST Live2 (exactly like all the others song)

BUG 5#.mp4

Hi.
Eugenio.

It is routed to “Si viaggiare”, which is a Group Channel that is routed to “SEQUENCE”, which goes to main output “MAIN”. Looks and sounds all ok to me.

If I change the Groove Agent channel (called “CLICKGroove”) to the (grren) “CLICK” output, it appears there as expected.

Not for me.
I had set the click channel of 2nd Song to “CLICK” and there it sounded. Then switched to Song 1 (where the other click track also sounded on CLICK as set already), then back to Song 2 - and all is good.

Works fine here. Maybe you need to press “return” once to get to the next line?

[quote=“eurag, post:4, topic:953834”]

Don’t understand that one, could you explain a bit more?

Are you really sure? Before we keep searching for your other reports, and as such tests eat a lot of time, we’d like to be absolutely sure. Pls check “Help/About” to assure the correct version, thanks.

| musicullum
November 26 |

  • | - |

eurag:

From the “Si Viaggiare” mixer the equivalent track for the click is #18 but it comes out on the wrong output.

It is routed to “Si viaggiare”, which is a Group Channel that is routed to “SEQUENCE”, which goes to main output “MAIN”. Looks and sounds all ok to me.

NO! IT MUST COME OUT AS IN “JOHNNY B GOODE” OR ROUTE IN SIVIAGIARE AND THEN NOT “SEQUENCE” BUT OUT CLICK. IF I PUT IT IN THE OUT CALLED “CLICK” IT DOES NOT KEEP THE SETTING. CHANGING SONG AND THEN GOING BACK TO “SI VIAGGIARE” I FIND IT IN “SEQUENCE” OUT!

eurag:

Even if I manually correct it by inserting the “CLICK” output, it does not maintain the change.

If I change the Groove Agent channel (called “CLICKGroove”) to the (grren) “CLICK” output, it appears there as expected.

It doesn’t work for me, it does exactly as described above

eurag:

After playing the 1st song, and then playing the 2nd Song again, it comes back with the wrong output.

Not for me.
I had set the click channel of 2nd Song to “CLICK” and there it sounded. Then switched to Song 1 (where the other click track also sounded on CLICK as set already), then back to Song 2 - and all is good.

It doesn’t work for me, it does exactly as described above

eurag:

By clicking on the NOTES icon I can’t write on it, maybe it’s my fault, but I’ve tried everything.

Works fine here. Maybe you need to press “return” once to get to the next line?

[quote=“eurag, post:4, topic:953834”]

eurag:

Using the FLEXLOOP after using it for a while it no longer takes my commands.
It doesn’t book the “part” I choose… or it skips incorrectly.

Don’t understand that one, could you explain a bit more?

eurag:

I confirm that I have installed the latest pre release: 2.1.22.239

Are you really sure? Before we keep searching for your other reports, and as such tests eat a lot of time, we’d like to be absolutely sure. Pls check “Help/About” to assure the correct version, thanks.

today’s news.

in addition to all the problems already explained and not solved, today I added a 3rd song.

similar to the previous ones and 2 problems occurred.
1 - I sent one the other day in the video.

2 - the other can be seen from the following screen:

<b>"the system has run out of available memory for applications."
 </b>

Mac M2 MAX with 32GB seems crazy to me that this could happen

Pls try again with the next version. It works here (with changes not yet published), maybe some fixes are helping.