UVI Workstation (release)

[otristan]

hmm finally downloaded this. the au is crashing host on exit..

Which host ?
Could you send me the crashlog in PM ?

Thanks,

[ObsoleteAcc99]

[DELETED]

[otristan]

But this is not really the major problem, as it could be a design feature. The main problem is, that it would only make sound, i.e. an audio preview, of one of the loops in that folder. So even though that loop had no markers, with that ONE it still guessed correctly and previewed it correctly in project tempo. When i would flick through the other sounds in the same folder with the uvi browser, they would make no sound at ALL. just silent, until i actually imported them. I am guessing, this happened, because UVI couldn't guess their tempo, but, IMO, it should still be able to preview the sound of them, even if it's not able to guess their tempo. I think it's a bad design feature, personally, to just make no sound at all in the browser, if the tempo is not being guessed.

Personally my request would be, that the browser incorporates tempo guessing for loops without markers... This would be an amazing feature, and would save me rewiring live to logic, because thats the only reason i use live for.

UVIWorkstation will not detect tempo of loops that do not contains this info(by design indeed)

Regarding sounds that do not make sounds at all, does it displays the waveform correctly ?
Care to share one this sample so we can see why it fails ?
Be aware that if those files are aiff caf (core audio format) with aac encoding ones, you'll need to install quicktime for UVIWorkstation to read those if you're on Windows.

Thanks for your report

[blue smoke]

So many pages, maybe I missed something, but this beta release crashes on launch for me every time. Standalone and plug-in. I'm on PPC 10.4.9. Any ideas?

Could you send me the crashlog in PM ?
I'm not aware of such issue in latest releases so I'd be happy to take a look.

Thanks,

Installing the 1.0.9 now and will see if that fixes it.

[ObsoleteAcc99]

[DELETED]

[mdsp]

But this is not really the major problem, as it could be a design feature. The main problem is, that it would only make sound, i.e. an audio preview, of one of the loops in that folder. So even though that loop had no markers, with that ONE it still guessed correctly and previewed it correctly in project tempo. When i would flick through the other sounds in the same folder with the uvi browser, they would make no sound at ALL. just silent, until i actually imported them. I am guessing, this happened, because UVI couldn't guess their tempo, but, IMO, it should still be able to preview the sound of them, even if it's not able to guess their tempo. I think it's a bad design feature, personally, to just make no sound at all in the browser, if the tempo is not being guessed.

Personally my request would be, that the browser incorporates tempo guessing for loops without markers... This would be an amazing feature, and would save me rewiring live to logic, because thats the only reason i use live for.

The decision logic in the browser is that if a sample doesn't contain tempo information/markers then it's loaded as an instrument sample and not as a loop. And instruments need to be played in order to make sound. Does it explain your situation?

best

remy

[mdsp]

BUT, could I make a feature request? TO INDEED preview loops in tempo that don't have the metadata, by guessing, just like Live, acid and Cubase4 do! It's possible! Pretty please??

It would make sense to preview samples without any loop hints as oneshots.

[Dudulle]

Hi there,

Tried the 1.0.9. version this afternoon. Seems to run well

At first, I had this message using the vst version in one of my cubase project:

Couldn't load the file '$Retrokeyboards.ufs.lnk/Samples/clavBC FX/Rel WET/clav BC Rel Vel1 A#1.aif'

and dozens of them under.

But I did'nt use the Multis.
When I saved the sounds in a multi; it launches well after when re-opening the project.

So, we have to save all parameters and sounds in a multi even in the VST version. I didn't know...sorry

The PACE problem with Autotune 5 seems to have disappear.

So I'm very happy

I let you know if I discover something else.

Thank you guys.

[frankbou]

Salut Olivier,

Midi mute is really nice and works well, thanks.

To add to the FX save preset feature request, it will be really cool to know also the preset name of the FX in the header of the FX box. By example, right now you only know that IR Reverb is load up, but after the fact you have no way to know which IR impulse is used which can become confusing.

On the feature request side, I was thinking that it could be really cool to be able to create some kind of container on track that could contain multiple patch inside them. So these could be saved as instrument preset. The reason I'm puting that up is because I realize that even if preset saving is a cool addition, I can't use it much since most of the instrument I'm puting together contain more than one patch. However, for those multi are overkill since I don't want to save and recall the whole thing, but just what is contain under the same midi channel. On the plus side as well, these track container could also simplify midi routing, create an overall volume and pan control, FX control, ...

Merci.

[otristan]

Hi there,

Tried the 1.0.9. version this afternoon. Seems to run well

At first, I had this message using the vst version in one of my cubase project:

Couldn't load the file '$Retrokeyboards.ufs.lnk/Samples/clavBC FX/Rel WET/clav BC Rel Vel1 A#1.aif'


Thank you guys.

It looks you're using a shortcut for this ufs file.
I remember changing some stuff in there.
So reloading old session might cause some issue.

Does this happen if you reload the instrument back, save the session and reload it ?

thanks,

[Dudulle]

It looks you're using a shortcut for this ufs file.
I remember changing some stuff in there.
So reloading old session might cause some issue.

Does this happen if you reload the instrument back, save the session and reload it ?

thanks,

Yes, I use shorcuts for all ufs files (got 2 HDD).

No issues when reloading old sessions if I've saved all UVIWorkstation stuff in a multi.

These issues happen only when no multi was saved within the project.

[otristan]

It looks you're using a shortcut for this ufs file.
I remember changing some stuff in there.
So reloading old session might cause some issue.

Does this happen if you reload the instrument back, save the session and reload it ?

thanks,

Yes, I use shorcuts for all ufs files (got 2 HDD).

No issues when reloading old sessions if I've saved all UVIWorkstation stuff in a multi.

These issues happen only when no multi was saved within the project.

After checking, it shouldn't happen with new project, can you confirm this ?

Thanks,

[Sascha Franck]

here's one from last week in the south west of france:



Obviously I'm not the one on the picture but I went surfing that day.

Hm. I'd really prefer to be polite, but can I just say "f**k!"? (I know I can't anyways, due to the rather newish KVR curse word blocker)

In other words, I'd love to be there right now. Ok, I just had 3 weeks of vacation on Crete, so I probably shouldn't complain (yet, we didn't have any comparable waves).

Ok, sorry for messing the thread up. Back to your UVI engine (will happily give the new version a testride tomorrow).

[hibidy]

I there a known bug with the some of the PSP loops not playing or they sound "clicky"?

PC, 1.09, standalone

When I load any of the guitar loops, they do not sound
When I load any of the vocal loops, they do not sound
The bass loops are clicky, regardless of tempo

The others are fine

[ObsoleteAcc99]

[DELETED]