Bitwig Studio 1.2 BETA 4

[c-wave]

In fact thinking about it, I'd much prefer a smarter input, so that as I type, the software is already making a tag by putting a tag graphic around it. Then there would be no room for misunderstanding.

This makes the most sense.

Right when you type in a letter, the first tag is created and you see the rect border. You type more letters to spell the word, the existing tag is just getting expanded, once you hit space Bitwig could finalize the tag behind the scenes and as soon as a non space character is typed this operation repeats itself.

Having this setup, you will always see a border rect around everything, even the last one. Instead of typing space at the end or seeing "naked" text, people would know all tags have been recorded and when OK is pressed life's balance returns to normal.

Mike

Yes I agree with Goatgirl too.. I just hope Bitwig does then this would be the best implementation (and probably harder to code) .. Also I agree that one word tags makes more sense as this would still not keep a user from using multiple words on search; same effect.

[ThomasHelzle]

Ctrl / Cmd or any other key makes no difference. Though I agree it would be a good way to produce multiword tags, should they choose to allow it.

I wholeheartedly agree with goatgirl here. If I enter something into the tagline, I expect it to become a tag when I press OK. Everything else is either tedious, non-self-explanatory or silly.
I don't write anything into a tag line I don't want to become a tag ever.
It makes no sense to add additional buttons or other stuff for something as simple.

As for two word tags: There is no difference when searching between the two tags "bass" and "synth" or one tag "bass synth".
And if it is important for somebody to explicitly have it as one tag, I'd also say make it "bass-synth".
Otherwise one would have to create tags with commas between them instead of spaces, which is how many other systems do it.
I personally prefer the current method with the fine-grained tags that I combine in my searches as I see fit.

Just my 2 cent

Cheers,

Tom

[dsan@mail.com]

IMHO, routing in BWS is a bit unintuitive; that is to say, until one gets used to it and learns how it's done in BWS. It is definitely different in other DAW's. (Easier too IMO).

Not to say you have not run into a bug psydave, but my best guess is something went askew with your routing and if you take a very close look I believe you will find the problem.

One thing I have noticed is occassionally a track must be enabled for record to be able to hear the playback. It may depend on the vst being used.

But then, other times it seems to play just fine without record enabled, so it is difficult to determine exactly what is happening.

As such, since I am unable to describe the problem accurately, I have not reported these incidents.

Once things calm down with the BETA's, and the devs have more time to devote to anomolies, I will certainly address issues such as this.

I think though that you should go through your routing carefully to find the problem. Also take a look to be sure the audio engine for each instrument is on. Sometimes it gets turned off somehow.

Cheers!
dsan

[u-u-u]

Ctrl / Cmd or any other key makes no difference. Though I agree it would be a good way to produce multiword tags, should they choose to allow it.

I wholeheartedly agree with goatgirl here. If I enter something into the tagline, I expect it to become a tag when I press OK. Everything else is either tedious, non-self-explanatory or silly.
I don't write anything into a tag line I don't want to become a tag ever.
It makes no sense to add additional buttons or other stuff for something as simple.

As for two word tags: There is no difference when searching between the two tags "bass" and "synth" or one tag "bass synth".
And if it is important for somebody to explicitly have it as one tag, I'd also say make it "bass-synth".
Otherwise one would have to create tags with commas between them instead of spaces, which is how many other systems do it.
I personally prefer the current method with the fine-grained tags that I combine in my searches as I see fit.

Agree here. I don't need multiword tags.
So for me space to saperate multiple tags is fine (and also used by other tagging systems. If I remember correctly, e.g. by Soundcloud). Only the last one entered into the tag line shouldn't have to be finished with a space. In case of only one tag you'd just type in the text and press OK. That would do it for me.

[c-wave]

Ok Dom, we're made up our minds.

[dsan@mail.com]

Ok Dom, we're made up Your minds.

FTFY c-wave

Cheers!
dsan

[kurasu]

a bug obviously

[goatgirl]

a bug obviously

[Ogopogo]

As for two word tags: There is no difference when searching between the two tags "bass" and "synth" or one tag "bass synth".
And if it is important for somebody to explicitly have it as one tag, I'd also say make it "bass-synth".
Otherwise one would have to create tags with commas between them instead of spaces, which is how many other systems do it.
I personally prefer the current method with the fine-grained tags that I combine in my searches as I see fit.

Just my 2 cent

Cheers,

Tom

Well I was thinking of phrases that it wouldn't make sense to reduce down, like "old school," "gangsta rap," or "les paul." It would be a bit weird to have to use hypens for all that stuff. You could search for it successfully if you split it up I guess but it wouldn't be right if you're just browsing. But maybe it's not worth it.

[c-wave]

a bug obviously

[c-wave]

As for two word tags: There is no difference when searching between the two tags "bass" and "synth" or one tag "bass synth".
And if it is important for somebody to explicitly have it as one tag, I'd also say make it "bass-synth".
Otherwise one would have to create tags with commas between them instead of spaces, which is how many other systems do it.
I personally prefer the current method with the fine-grained tags that I combine in my searches as I see fit.

Just my 2 cent

Cheers,

Tom

Well I was thinking of phrases that it wouldn't make sense to reduce down, like "old school," "gangsta rap," or "les paul." It would be a bit weird to have to use hypens for all that stuff. You could search for it successfully if you split it up I guess but it wouldn't be right if you're just browsing. But maybe it's not worth it.

Think of it as the lesser of two evils.. for lack of a better term.

[Ogopogo]

a bug obviously

Uh, so does that mean two word tags are intended? Or is that a separate issue.

[gesslr]

Hi.

I'm getting some weird behavior with Beta 4.

I have a lot of hardware synth units. I'm trying to set up a template for them. So right now I have one instrument track sending midi to a HW unit via a HW Instrument Device and a separate audio track set up to record the resulting audio. (I'm choosing not to use the audio in in the HW Instrument Device.)

Everything is great until I get to three of the synths. For each, I can only hear the synth if I select the exact same audio input for each one...but they are all patched into different inputs on my audio interface. In this case I have to select "MicroQ" (the audio input for my MicroQ) for the MicroQ (of course), but also for 2 other synths. If I select their labelled inputs, I hear nothing. But if I select "MicroQ" for all three, I hear three distinct synths playing on three different inputs. It is very bizarre.

Before you go there, my inputs are labeled correctly, and my current set up works in Cubase, Studio One, and DP without incident.

I'm not sure, that I'm explaining it correctly, so I made a video. It's 5 minutes long and I ramble a bit (my first one), but at 2:25 I get to the crux of the problem. Before that I provide context and show it working with other synths. I should also say that this is an early effort to start working on a template in 1.2 as I just got started.



I "hope" it's a bug and not FOUE (friggin obvious user error), but I'm stumped.

MacPro 5,1
OSX 10.10.5
28 gb ram
Motu 828 Mk2 & Mk3 audio interfaces
Motu Midi Express 128s

Thoughts appreciated.

Thanks.

OK. Got the above sorted.

As near as I can tell, my prefs (or something) must have become corrupted. I began getting strange behaviors in other applications. I pulled out my hair trying to figure this out, then just said f-it and re-installed my audio and midi drivers. Everything looks to be working now.

Sorry for the troubles....

G

[ThomasHelzle]

[Kung VU]

Regarding the tag editor. If you look for user friendly interfaces just have a look at the way successful Mac programs handle similar problems. This is how the tagging could be handled for example. This would also include spaces if you want (as you can see by just clicking in the newly created tag and hitting space). Each entry becomes a tag by hitting enter.

P.S. ignore the And, Or etc. box below