Pro 15 can record with ASIO, but cursor won't move on playback

gamehits wrote on 7/29/2018, 9:13 PM

I'm using a USB interface, specifically a Steinberg UR44. Recording audio is no problem, but as I said, when I play back, the cursor won't move. Sample rate is kosher...the track properties show it being 48k, the interface shows 48k, as does the project settings. I'm using the latest USB driver from Steinberg as well. Suggestions??

Comments

Former user wrote on 7/29/2018, 10:42 PM

Usually cursor movement problems are related to the video card/drivers.

gamehits wrote on 7/29/2018, 10:48 PM

Usually cursor movement problems are related to the video card/drivers.

rendering is no problem. if i'm using windows audio drivers everything works. of course, recording audio doesn't really work as well, so that's why I would asio drivers to work. but every time I switch to an asio driver, there's no playback.

Former user wrote on 7/29/2018, 11:02 PM

Maybe I misunderstood. Do you mean the audio doesn't play back at all or just the cursor doesn't move, but the audio plays?

gamehits wrote on 7/29/2018, 11:09 PM

Maybe I misunderstood. Do you mean the audio doesn't play back at all or just the cursor doesn't move, but the audio plays?

both. when I select the Steinberg asio driver, the cursor won't move, the audio won't play, and the program transport play button flashes in and out of play almost instantly. when I switch back to the windows driver, vegas operates normally. let me add, if I arm the track for recording audio, when I hit record, THAT works. but when I try to play that back, the cursor won't move, play engages then instantaneously disengages. suggestions?

VStoyanov wrote on 8/10/2018, 5:22 PM

Hi. I have exactly the same problem with Steinberg ASIO drivers of my UR 242. When I switch to Steinberg audio ASIO drivers - the playback doesn't work. When I switch back to windows driver - vegas operates normally.

Is there a solution to the problem? I want to use my Steinberg low latency drivers that working brilliantly in all other DAW programs.

gamehits wrote on 9/2/2018, 1:32 AM

crickets from the developers on this front. VP16 has same issue...

fr0sty wrote on 9/2/2018, 8:52 AM

I've seen other DAWs do this when there are incorrect settings in the ASIO driver vs. internal settings for the DAW, for instance buffer or sample rate conflicts.

gamehits wrote on 9/2/2018, 9:09 AM

I've seen other DAWs do this when there are incorrect settings in the ASIO driver vs. internal settings for the DAW, for instance buffer or sample rate conflicts.

Yeah, no. I run 3 DAWs, resolve, wavelab, and I’m an audio engineer. This is a Vegas problem

fr0sty wrote on 9/2/2018, 9:22 AM

I too am an audio engineer, I run Vegas, Reaper, and Cubase, and I've seen this problem affect all 3. Have you checked Vegas' preferences to make sure those settings match the settings of your ASIO driver? Are you using ASIO4ALL (it has its own bugs it can cause)? I'm not implying it can't be a Vegas bug, just stating I've seen this exact same behavior in other apps (Vegas included) before due to settings conflicts.

gamehits wrote on 9/2/2018, 9:25 AM

I too am an audio engineer, I run Vegas, Reaper, and Cubase, and I've seen this problem affect all 3. Have you checked Vegas' preferences to make sure those settings match the settings of your ASIO driver? Are you using ASIO4ALL (it has its own bugs it can cause)? I'm not implying it can't be a Vegas bug, just stating I've seen this exact same behavior in other apps (Vegas included) before due to settings conflicts.

Yes to all of your questions. Have you used a steinberg interface with Vegas? Or a focusrite usb interface, and recorded tracks successfully?

fr0sty wrote on 9/2/2018, 11:19 AM

Also make sure your buffer settings match in both driver and vegas. I haven't used Vegas to record tracks in a while, Reaper has been my go-to DAW for a minute (Cubase is great, but I like Reaper's insane level of customization). I'm currently using a Behringer interface. Next time I'm at the studio, I will fire up Vegas and see if I can replicate the problem.