UVI Workstation (release)

[spidermix]

1.06 BUG

Running in stand alone mode:
Installed 1.06. Plugin automatically defaults to core audio integrated sound card. I select my Focusrite as the preferred audio device and all is well. I then try to select my Axiom Midi controller under the midi tab and get the spinning beach ball, then program lockup. I then reinstall 1.05 issue not there; program automatically defaults to correct audio and I can select any midi device without causing the UVI to crash. I'm going to try it inside Cubase to see if more stable there, or will possibly have to go back to 1.05 until this gets ironed out.

SpiderMix

[otristan]

By the way, I forgot to add in the Changelog

Single preset saving which was asked by quite a number of you.

Have fun !

[frankbou]

Olivier, here is a few problems about your Mute/Solo system:

1- You can have a track set to Mute and Solo at the same time which is kind of weird

2- When Soloing a track it doesn't Mute all other tracks which bring you in a state where when you Solo track other tracks aren't neither Soloed or Muted.

3- Aux FX aren't muted on a Mute track so only the Dry signal is getting mute and not the wet signal which is not really useful.

4- We already discussed about this, but CPU is still used on Mute track even if you do not hear them.

Looking at the last two points make me curious about the reason of your implementation of the Mute/Solo at this stage in the audio engine. Will it not be a lot more easy to put it at the input stage where you just filter in or out midi data to mute or not a track?

By the way using MOTU SI inside UVI is really nice, thank you for that. You make me regret now to have not bought Ethno instrument as well....

Merci.

[Bass108]

1.0.6 fails au validation in logic now...

...i was hoping to save me some presets.

its logic 8.0.2 on OSX 10.4

i can send you a log if necessary

[otristan]

Olivier, here is a few problems about your Mute/Solo system:

1- You can have a track set to Mute and Solo at the same time which is kind of weird

2- When Soloing a track it doesn't Mute all other tracks which bring you in a state where when you Solo track other tracks aren't neither Soloed or Muted.

3- Aux FX aren't muted on a Mute track so only the Dry signal is getting mute and not the wet signal which is not really useful.

4- We already discussed about this, but CPU is still used on Mute track even if you do not hear them.

Looking at the last two points make me curious about the reason of your implementation of the Mute/Solo at this stage in the audio engine. Will it not be a lot more easy to put it at the input stage where you just filter in or out midi data to mute or not a track?

By the way using MOTU SI inside UVI is really nice, thank you for that. You make me regret now to have not bought Ethno instrument as well....

Merci.

I agree about 3, mute should happen before aux send. We'll fix this.

Regarding 1 and 2, I remember checking in some hosts and tried to keep the same kind of feeling.
The current situation is imho the most flexible one.

Guys ?


4 I still prefer audio muting as it's more natural at CPU expense I agree.

[otristan]

1.0.6 fails au validation in logic now...

...i was hoping to save me some presets.

its logic 8.0.2 on OSX 10.4

i can send you a log if necessary

Yeah some issue when copying the bundle not changing the bundle rsrc.
(I like Xcode a lot )

1.0.7 will fix this.

By the way, loading EThno and MSI stil fails on mac and may lead to crash when found in the UVISoundbank folder.
SHould be fixed in 1.0.7.

[frankbou]

Olivier, here is a few problems about your Mute/Solo system:

1- You can have a track set to Mute and Solo at the same time which is kind of weird

2- When Soloing a track it doesn't Mute all other tracks which bring you in a state where when you Solo track other tracks aren't neither Soloed or Muted.

3- Aux FX aren't muted on a Mute track so only the Dry signal is getting mute and not the wet signal which is not really useful.

4- We already discussed about this, but CPU is still used on Mute track even if you do not hear them.

Looking at the last two points make me curious about the reason of your implementation of the Mute/Solo at this stage in the audio engine. Will it not be a lot more easy to put it at the input stage where you just filter in or out midi data to mute or not a track?

By the way using MOTU SI inside UVI is really nice, thank you for that. You make me regret now to have not bought Ethno instrument as well....

Merci.

I agree about 3, mute should happen before aux send. We'll fix this.

Regarding 1 and 2, I remember checking in some hosts and tried to keep the same kind of feeling.
The current situation is imho the most flexible one.

Guys ?


4 I still prefer audio muting as it's more natural at CPU expense I agree.

At some point you mentioned implementing another mute mechanism at the midi level, is it still in the plan?

[jobromedia]

Well, to get a declaration of love from me Olivier will need to do something about the readability of the light blue on blue background. It may look nice, but working with it for hours is another story.

I concour with fortisimo on that one! I have a heck a hard time to see on the GUI. It looks nice, but please allow an alternative display to be selectable. I would much rather see a dark dark brown background with bright amber yellow controls. Fits the FL Studio skins better, and it saves the eyes. A brightnes control would also be nice to have handy.

[dbender]

Problem w/ 1.06 Standalone --

- using: MacBook C2D 2 GHz OS X 10.4.11

- New Problem w/ Beta 1.06: Midi input silences audio out of UVI Workstation:

Anytime I press a key on any selected midi controller, it silences the sound coming out of UVI Workstation.

And, UVI Workstation hangs after making changes to audio/midi settings.

I went to /users/me/library/preferences/ hoping to delete UVI Workstation prefs in an attempt to try and fix this, but found many, many prefs for it:

1. com.uvi.com.uvi.UVIWorkstation.plist
2. com.uvi.UVIWorkstation.plist
3. com.uvisoundsource.com.uvisoundsource.UVIWorkstation.plist
4. com.uvisoundsource.UVIWorkstation.plist
5. com.uvisoundsource.UVIWorkstation.SA.plist
6. com.uvisoundsource.UVIWorkstationSA.plist
7. UVIWorkstation_StandAlone.properties

I've been using UVI Workstation since the first beta, and have been installing all the beta versions since the first one.

-Are some of these files vestigial from older betas that should be removed?
-Which ones should I delete to make sure UVI Workstation is functioning properly?
-Should I delete all of them, and just let UVI Workstation beta 1.06 rebuild the prefs it needs, so as to fix the problem described above (midi input silences UVI Workstation)?
-Is the problem I reported just a bug, so that I need not delete any of these pref files, and just wait for it to be fixed in the next beta version 1.07?

NOTE: As a plug in, v1.0.6 passed a validation scan in Digital Performer (athough DP uses the MAS version, not the au version), and, the midi problem reported above does not affect the plug in DP and it receives midi notes and plays ok, unlike the standalone version as reported above.

Thanks

[DHR53]

Hmmm... 1.06 is got problems with OSX 10.5.4. Crashes setting up the Audio Midi settings, and still shows as 1.05 after installing 1.06??? Any other things I don't know about... Haven't even opened it in Logic?

[dbender]

Hmmm... 1.06 is got problems with OSX 10.5.4. Crashes setting up the Audio Midi settings, and still shows as 1.05 after installing 1.06??? Any other things I don't know about... Haven't even opened it in Logic?

I too saw that the version of the standalone remained at 1.05 when looking at the file in the finder, but when opening the standalone it does say 1.06 on the lower right hand corner of the GUI.

And, yes, I too get the crashing after changing Audio Midi settings, in addition to any midi in not playing, and then silencing UVI Workstation, even when playing the on screen little keyboard in its gui.

[OS X 10.4.11, MacBook C2D 2 GHz]

[otristan]

Problem w/ 1.06 Standalone --

- using: MacBook C2D 2 GHz OS X 10.4.11

- New Problem w/ Beta 1.06: Midi input silences audio out of UVI Workstation:

Anytime I press a key on any selected midi controller, it silences the sound coming out of UVI Workstation.

And, UVI Workstation hangs after making changes to audio/midi settings.

I went to /users/me/library/preferences/ hoping to delete UVI Workstation prefs in an attempt to try and fix this, but found many, many prefs for it:

1. com.uvi.com.uvi.UVIWorkstation.plist
2. com.uvi.UVIWorkstation.plist
3. com.uvisoundsource.com.uvisoundsource.UVIWorkstation.plist
4. com.uvisoundsource.UVIWorkstation.plist
5. com.uvisoundsource.UVIWorkstation.SA.plist
6. com.uvisoundsource.UVIWorkstationSA.plist
7. UVIWorkstation_StandAlone.properties

I've been using UVI Workstation since the first beta, and have been installing all the beta versions since the first one.

-Are some of these files vestigial from older betas that should be removed?
-Which ones should I delete to make sure UVI Workstation is functioning properly?
-Should I delete all of them, and just let UVI Workstation beta 1.06 rebuild the prefs it needs, so as to fix the problem described above (midi input silences UVI Workstation)?
-Is the problem I reported just a bug, so that I need not delete any of these pref files, and just wait for it to be fixed in the next beta version 1.07?

NOTE: As a plug in, v1.0.6 passed a validation scan in Digital Performer (athough DP uses the MAS version, not the au version), and, the midi problem reported above does not affect the plug in DP and it receives midi notes and plays ok, unlike the standalone version as reported above.

Thanks

In doubt remove all of those.
The MIDI thing is very strange.

Let us know if this still happen removing all pref files.

Thx

[dbender]

Problem w/ 1.06 Standalone --

- using: MacBook C2D 2 GHz OS X 10.4.11

- New Problem w/ Beta 1.06: Midi input silences audio out of UVI Workstation:

Anytime I press a key on any selected midi controller, it silences the sound coming out of UVI Workstation.

And, UVI Workstation hangs after making changes to audio/midi settings.

I went to /users/me/library/preferences/ hoping to delete UVI Workstation prefs in an attempt to try and fix this, but found many, many prefs for it:

1. com.uvi.com.uvi.UVIWorkstation.plist
2. com.uvi.UVIWorkstation.plist
3. com.uvisoundsource.com.uvisoundsource.UVIWorkstation.plist
4. com.uvisoundsource.UVIWorkstation.plist
5. com.uvisoundsource.UVIWorkstation.SA.plist
6. com.uvisoundsource.UVIWorkstationSA.plist
7. UVIWorkstation_StandAlone.properties

I've been using UVI Workstation since the first beta, and have been installing all the beta versions since the first one.

-Are some of these files vestigial from older betas that should be removed?
-Which ones should I delete to make sure UVI Workstation is functioning properly?
-Should I delete all of them, and just let UVI Workstation beta 1.06 rebuild the prefs it needs, so as to fix the problem described above (midi input silences UVI Workstation)?
-Is the problem I reported just a bug, so that I need not delete any of these pref files, and just wait for it to be fixed in the next beta version 1.07?

NOTE: As a plug in, v1.0.6 passed a validation scan in Digital Performer (athough DP uses the MAS version, not the au version), and, the midi problem reported above does not affect the plug in DP and it receives midi notes and plays ok, unlike the standalone version as reported above.

Thanks

In doubt remove all of those.
The MIDI thing is very strange.

Let us know if this still happen removing all pref files.

Thx

Yes, still happening ...............

More testing......

I removed all those 7 pref files. Restarted UVI Workstation. Now the only prefs file is = com.uvisoundsource.UVIWorkstationSA.plist

I still get the midi problem, and the crash/hang problem.

The midi problem is that when hitting a note on my midi keyboard controller that I've selected in UVI Workstation's audio/midi prefs settings, no sound is output - UVI Workstation does not output any sound (and no activity on its level meters also), and, also, it makes no sound even using the gui keyboard (whereas the gui keyboard did produce sound before hitting a note on the midi keyboard controller). HAve to quit and restart to get it to output any sound.

The crash/hang happens at this point when trying to access UVI Workstation's audio/midi settings again after this. It'll then hang (and sometimes crash and quit).

Also, re: audio settings, they're not remembered and always go back to Internal even though I last had it set for MOTU 828 Mk 2. And, when I set it to that, the physical outputs for it don't show, you have to close the audi/midi settings window, then reopen it, to have the 828's outs show up in the physical outputs window in UVI Workstation's audio/midi settings.

Hopes this helps you fix it. This "midi problem" and hang/crash problem is new with v 1.06, and didn't happen in v. 1.05.

(PS -- Really happy you added the ability to save individual presets -- been wanting that since I bought Plug-Sound Pro!!! ]

[fst]

I'm also seeing the MIDI issue in OSX 10.5.4 as reported above (MIDI input causes hang) - tried total deletion of all prefs/UVI related files & re-install, didn't help. Curiously, when it hangs, syslogd also goes mad and has to be manually killed.

[otristan]

Hopes this helps you fix it. This "midi problem" and hang/crash problem is new with v 1.06, and didn't happen in v. 1.05.

(PS -- Really happy you added the ability to save individual presets -- been wanting that since I bought Plug-Sound Pro!!! ]

We move the whole StandAlone system from 1.0.5 to 1.0.6 in order to fix crashing issue with some audio card. It looks like it's not perfect yet.
What s your MIDI device ?

Thx