Waveform 13 missing option

[davidls]

I do have click enabled, and can hear it in my headphones. Also, what causes the click to be recorded? Somehow I've enable that!
The cursor is moving on playback.
I am not familiar yet with snap or punch-in yet- I don't believe they are enabled. How are they used?
My computer is a Dell Latitude 64-bit, core i7. I'm using a Bomge interface.
Another thing I've noticed is that the audio device type reverts back from Windows Audio to Directsound often- not sure why. When something is not working when ready to record, I check that and find that it has changed.
Thanks for your help, Peter.

[Peter Widdicombe]

1. Fact that you can record the click indicates a "feedback loop" - what it outputs to ends up back in the audio input path. This shouldn't happen. You want what is being recorded on each track to ONLY be what you intend, not new track with an echo of everything else you can hear. There may be a switch on the audio interface (or another virtual device name?) that allows you to record ONLY what comes in on an audio port of that interface.
2. Windows audio and directsound tend to be easy, but problematic. They are convenient in that you can record in Waveform while a Youtube is playing, but typically introduce some delay.
3. Find and download Asio4all. It's basically a faster dedicated interface for audio devices with lower latency. Once installed, it will load automatically with Waveform and show up as a new interface, with selectable interfaces in it's control menu. It also will allow you to have multiple devices - like a USB headset and a USB interface like your current one.

[davidls]

Unfortunately I've found that the Bomge interface cannot use Asio4All, but I've seen a blog which says you can use FlexAsio with it. Do you know if FlexAsio would be a better driver than the windows driver??

[Peter Widdicombe]

Don't know which BOMGE interface you have, but some have a "loopback" button on it. When recording, you probably want that OFF so your whole mix (including click ) doesn't get echoed back to the computer and recorded along with what you INTEND to record.

Flexasio sounds "more difficult" to set up, but allows you to watch youtube while running Waveform, supposedly; and you have to install the referred gui to customize (or really know what you are doing and edit the INI file). I didn't realize Asio4All is actually a "shim" that LOOKS like ASIO but works with generic Windows audio devices, but only in exclusive mode - so may actually work in your case. Did you try and it didn't...?

I've always used Asio4All, but don't have any high end interfaces (some USB, and also built-in devices); and it allows me to run multiple devices, as long as they're all running at the same sample rate.

[davidls]

Thanks for that Peter. I had an issue downloading Flexasio, so tried using the windows low latency driver that is already onboard. It seems to be working OK. Somehow I've managed to remove the clicks from the recording but am unsure how I did it! These programs are complicated for us beginners!
It looks like the headphone input on the Bomge will only provide input, not output- tried several times to get output with no luck. Perhaps the Bomge speaker outputs are the only option (which I'm not currently using).

[davidls]

I am getting output from my computer headphone jack.

[Peter Widdicombe]

It can be a bit of a learning curve. You THINK you're only dealing with Waveform; but actually, you are also dealing with the entire audio chain. Remember Waveform only "sees" selected inputs on the devices you have selected, and will output where you selected. What happens on the input side and output is actually related to:

1. Operating system quirks
2. With windows and Linux, drivers and system audio
3. The external interface connection (USB?)
4. Settings on the interface. Does USB input get "bounced" back to the comuter or not? If you use headphones, can THEY hear input devices, or computer output, or both? Can headphones hear both, but only return "new" source (i.e. guitar, base, drums, vocals), or the same mix that you may want in the headphones?
5. Remember your little USB audio device is actually a mixer - even if it only has 2 inputs and a headphone jack. Logically, you still have 2 busses (hopefully distinct), so headphone and USB send to computer are not necessarily the same. Monitoring mode may affect that.


6. Monitoring - do you want to hear the input direct from the interface's input devices, or echoed from the DAW? Sounds simple. Many smaller mixers can't support all of that; and if they do it may be mono.
7. Read the manual on the audio interface. To get the most out of them you have to understand what all the buttons REALLY can affect. Otherwise, you play with connections and buttons until it SEEMS to do what you want, until you get back to your tracks and realize your vocal track actually contains vocals plus the piano or guitar part you were listening to as you were recording...
8. Use the Waveform input-device display in the input device context display (you NEED to know how to bring it up, and it is USEFUL at this time) to get those nice big meters at the bottom when setting up. Make sure levels are OK, and that you ONLY get input when you expect to. If you see, for instance, the meters bouncing while recording vocals and you aren't singing, you're getting echo/bleed from somewhere else !

PS - which Bomge interface? buttons are labelled differently on different models, by the looks of it.

[davidls]

Thanks Peter- lots of good advice there. My Bomge model is BMG22. It wasn't expensive and may have limited features.

[tbeauvais]

This is honestly crazy that they removed this simple and STANDARD feature from the application. This makes me want to stop using it completely. I was getting a hang of this DAW and excited to progress to buy it, though if this is how they play, I might just start with a different DAW.

[talby]

What are you speaking about?

[pough]

What are you speaking about?

Probably talking about the original topic, which is the "return to start on play" option. It's available in the Pro version but not the Free version. And some people seem to believe that if they don't get all the features they really want for free, there is no incentive to pay. I can't honestly say that makes sense to me.

[talby]

Yes, I totally agree.
If this (or other) function is essential for someone to use, and the app appears to otherwise fit the needs, then getting this essential but in the FREE version missing feature with the purchase of the PRO version should be motivation enough to start monetarily supporting the app development by upgrading to the PRO version.

The FREE version basically allows you to achieve all what your musicianship asks for. So, everybody is basically supported. Everybody is then free to add some extra instruments and sounds, or use some more sophisticated MIDI editing features as an example, from a third party.

But if you want a faster workflow, some more comfort, finding certain functionality better integrated than possibly achieved by third party tools, or if you simply do not want to lose time searching elsewhere for all the extras, then go PRO, because this is what PRO means.