it can be (or I canThomasHelzle wrote:Hm - interesting. So it may be some initialization thing.
Thanks, will keep it in mind.
Cheers,
Tom
ofc I've tried it with admin rights too, if the /Users/... entries have been created it can be started
it can be (or I canThomasHelzle wrote:Hm - interesting. So it may be some initialization thing.
Thanks, will keep it in mind.
Cheers,
Tom
Well, that is messing with the installation and of course can create problems.xbitz wrote:it can be (or I canThomasHelzle wrote:Hm - interesting. So it may be some initialization thing.
Thanks, will keep it in mind.
Cheers,
Tom) reproduced if u delete every *bitwig* entry from your user folder (c:\Users\USERNAME\) then try to start the beta
ofc I've tried it with admin rights too, if the /Users/ entries have been created, it's ok
Thank you for making all that clearThomasHelzle wrote:First: you are welcome to discuss the Beta here.![]()
It's only "closed" in the sense that it's limited to current license holders.
Same "rules" as always: Discuss here on KVR if you are unsure if you are doing things properly or how others perceive the changes or to verify weirdness, but bug and crash reports should go to tech-support for solving: http://www.bitwig.com/en/support/tech-support.html
Try to focus on the new features/problems in 1.1 for now and getting them rock solid instead of starting the next round of FRs already.
Each version has it's own preferences since 1.0.14 IIRC. So you shouldn't get interference from running both release and beta side by side, but since the caches are different, VSTs and files may be rescanned each time you switch between beta and release version, so don't be surprised if it takes longer in that case to scan/index! This is to make sure you don't get funky results by inconsistent caches.
1.1 files ARE NOT BACKWARDS COMPATIBLE. So make sure you save to a separate 1.1 copy if you want to be able to go back to the release version!
Give 1.1 a good workout and report as clearly as possible if you find weirdness.
Provide as much info to support as possible to make reproducing possible.
Thank you very much for your patience and I hope you enjoy 1.1!
Cheers,
Tom
Cool. That makes me think that perhaps the preset save dialog box may also not get hidden behind the VST window? That annoys me even more as I always have the VST window open when saving a VST bitwig preset. I'm at work so can't check but hopefully all windows pop up in front of it?goatgirl wrote:Yeah! not seen it in the release notes, there are so many changes though, I may have missed it.
When you close Bitwig, the 'Do you want to save?' dialog box doesn't get hidden behind VST windows any more. How cool is that.![]()
Just checked the save preset dialog and unfortunately the window does not pop up in front of the VSTEchoes in the Attic wrote: Cool. That makes me think that perhaps the preset save dialog box may also not get hidden behind the VST window? That annoys me even more as I always have the VST window open when saving a VST bitwig preset. I'm at work so can't check but hopefully all windows pop up in front of it?
What????? That is HUGE. Will try immediately.Ogopogo wrote:Fyi moving notes with the keyboard now auditions them. Didn't notice that in the list.
Is it true for when you drag the device into the browser to save a preset? Or only when you hit the save preset in the device? I usually drag mine over to custom locations. That's when it would always pop up behind the damn VST window.goatgirl wrote:Just checked the save preset dialog and unfortunately the window does not pop up in front of the VSTEchoes in the Attic wrote: Cool. That makes me think that perhaps the preset save dialog box may also not get hidden behind the VST window? That annoys me even more as I always have the VST window open when saving a VST bitwig preset. I'm at work so can't check but hopefully all windows pop up in front of it?
The VST window goes pooof! and vanishes with anything else that is there and the save preset dialog is magically there, similar to the way the close dialog works.
Just tested that scenario and its not a problem, the VST windows disappear just like the other cases.Echoes in the Attic wrote: Is it true for when you drag the device into the browser to save a preset? Or only when you hit the save preset in the device? I usually drag mine over to custom locations. That's when it would always pop up behind the damn VST window.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026