Bitwig

peter71@rocketmail.com · Thu Oct 23, 2014 6:51 pm

Thank You for response........ your instructions regarding Slate Tape Machine worked perfectly. It's finally working now.

c-wave · Post by **c-wave** » Thu Oct 23, 2014 9:53 pm

Feedback:
Xfer Serum 1.01 on Win 8.1 Pro x64 / Beta6: drag and drop works great from browser (as well as from Windows explorer).

thanks!
Edit:
Macro names still don't change when they change inside Serum.

Ogopogo · Post by **Ogopogo** » Thu Oct 23, 2014 9:59 pm

Beta 6 is super crashy for me, it crashes after a few seconds of playback, whether in the browser or the project itself.

Mac Mini OSX yosemite i7 3615QM 2.3GHz Mackie Blackjack

I sent in a bunch of crash reports.

Btw, if we send in a crash report do we need to report the bug otherwise or is the crash report the superior way of reporting?
And do we need to include any system info with the report or is it all gathered automatically?

volker@bitwig · Post by **volker@bitwig** » Thu Oct 23, 2014 10:14 pm

Ogopogo wrote:Beta 6 is super crashy for me, it crashes after a few seconds of playing anything, whether in the browser or the project itself.

Mac Mini OSX yosemite i7 3615QM 2.3GHz Mackie Blackjack

I sent in a bunch of crash reports.

Btw, if we send in a crash report do we need to report the bug otherwise or is the crash report the superior way of reporting?
And do we need to include any system info with the report or is it all gathered automatically?

Thanks for sending the crash reports, we will look into it!

When you get the crash report dialog that would be the preferred way, then the report including system information and crash information automatically arrives in our issue tracker. The only extra system information that we don't get automatically is your audio hardware, you can write those into the dialog text field if it was an engine crash. In case you know the steps to reproduce the crash you can write those into the text field as well, no need to write an extra email. Crashes are usually easy to fix once we understand how to reproduce them. But even without any extra description it's already helpful to get the reports because we can at least see the location in the code where it crashed.

Cheers,
Volker

Ogopogo · Post by **Ogopogo** » Thu Oct 23, 2014 10:21 pm

Okey dokey, so if I send in another crash report from Bitwig and include my audio hardware, will it automatically be grouped the other reports I sent in so you will have that info for those too?

Also you might wanna put that info in the sticky.

volker@bitwig · Post by **volker@bitwig** » Thu Oct 23, 2014 10:38 pm

Ogopogo wrote:Okey dokey, so if I send in another crash report from Bitwig and include my audio hardware, will it automatically be grouped the other reports I sent in so you will have that info for those too?

Also you might wanna put that info in the sticky.

Yes it will be grouped with the previous crashes and add your comments from the text field. Also a crash counter gets increased so we see how often a crash happened. One more addition to the above: in case the crash can be reproduced in specific documents after following certain steps, then it would be great if you can write an extra email to support@bitwig.com (or beta@bitwig.com) with that document attached and the steps to reproduce, because we don't get the project files automatically.

I'll ask my support colleagues to make those infos sticky, have never done that before.

Thanks!
Volker

Ogopogo · Post by **Ogopogo** » Thu Oct 23, 2014 11:14 pm

Okels dokels, it's not project specific so I just sent in the crash report. Thanks Volker.

Ogopogo · Post by **Ogopogo** » Thu Oct 23, 2014 11:56 pm

Seems you guys removed the text "name and color" from the inspector when it's showing tracks, but forgot to remove it from the clip display.

Ogopogo · Post by **Ogopogo** » Fri Oct 24, 2014 12:30 am

Was talking about this in another thread; it seems deactivating a clip is just muting it? In that case why have the option to "deactivate" at all, why not just mute? It's weird to hit "deactivate" in the menu and the mute button goes on, two names for the same thing.

volker@bitwig · Post by **volker@bitwig** » Fri Oct 24, 2014 12:33 am

Ogopogo wrote:Was talking about this in another thread; it seems deactivating a clip is just muting it? In that case why have the option to "deactivate" at all, why not just mute? It's weird to hit "deactivate" in the menu and the mute button goes on, two names for the same thing.

It's the same thing, just badly labeled, we plan to have the naming of mute/deactivate and also the shortcuts cleaned up in the next beta version.

nechronics · Post by **nechronics** » Fri Oct 24, 2014 12:46 am

peter71@rocketmail.com wrote:Hi guys sorry for this question but can't seem to find it anywhere in 1.1. Is there actual Grouping Tracks now in this version. I know you can by routing to an audio track.

Another question any of you guys have a problem with slate tape plugin. Gui is not opening. The plug In Opens but half the gui does......so it's unusable.

1.1 is running pretty good now.

Thanks

Yes, the plugin looks like this here - 80% of it is shifted out of screen:

nechronics · Post by **nechronics** » Fri Oct 24, 2014 12:47 am

volker@bitwig wrote:
Ogopogo wrote:Was talking about this in another thread; it seems deactivating a clip is just muting it? In that case why have the option to "deactivate" at all, why not just mute? It's weird to hit "deactivate" in the menu and the mute button goes on, two names for the same thing.
It's the same thing, just badly labeled, we plan to have the naming of mute/deactivate and also the shortcuts cleaned up in the next beta version.

When you say shortcuts - do you mean keyboard shortcuts??

That would really be the icing on the cake for me - please elaborate!

volker@bitwig · Post by **volker@bitwig** » Fri Oct 24, 2014 12:50 am

nechronics wrote:
volker@bitwig wrote:
Ogopogo wrote:Was talking about this in another thread; it seems deactivating a clip is just muting it? In that case why have the option to "deactivate" at all, why not just mute? It's weird to hit "deactivate" in the menu and the mute button goes on, two names for the same thing.
It's the same thing, just badly labeled, we plan to have the naming of mute/deactivate and also the shortcuts cleaned up in the next beta version.
When you say shortcuts - do you mean keyboard shortcuts??
That would really be the icing on the cake for me - please elaborate!

yes, keyboard shortcuts.

shadiradio · Post by **shadiradio** » Fri Oct 24, 2014 12:55 am

dom@bitwig wrote: IMPROVED Audition velocity changes with time threshold instead of playing a new note on each mouse move.

Hooray!

nechronics · Post by **nechronics** » Fri Oct 24, 2014 1:00 am

volker@bitwig wrote:
nechronics wrote:
volker@bitwig wrote:
Ogopogo wrote:Was talking about this in another thread; it seems deactivating a clip is just muting it? In that case why have the option to "deactivate" at all, why not just mute? It's weird to hit "deactivate" in the menu and the mute button goes on, two names for the same thing.
It's the same thing, just badly labeled, we plan to have the naming of mute/deactivate and also the shortcuts cleaned up in the next beta version.
When you say shortcuts - do you mean keyboard shortcuts??
That would really be the icing on the cake for me - please elaborate!
yes, keyboard shortcuts.

Ok, let me make one quick recommendation - rather than having two separate keyboard shortcuts for deactivating/activating clips, tracks, etc. - just make it one command - preferably one key
Cmd-alt D to deactivate and cmd-alt A to activate is redundant since you need to use two separate shortcuts to toggle the same thing.

Would recommend having a single key be the command for this - especially as it can get very heavy use when editing notes in the piano roll - I will sometime duplicate a midi clip to multiple tracks and go through muting/unmuting a slew of notes in each one, experimenting with different combinations of instruments playing different notes from the same clip.

Bitwig

KVR Audio

Bitwig Studio 1.1beta6