Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER General Discussion Forum

Reply
 
Thread Tools Display Modes
Old 01-21-2018, 07:25 AM   #41
DarrenH
Human being with feelings
 
Join Date: Mar 2014
Posts: 347
Default

I don't think any sorcery is at play...I max out resources at times during recording, mainly because I just get into the moment and am sloppy at project maintenance or in the midst of layering or something. That's where freezing tracks happens or simply muting certain things until I'm finished recording. Every DAW has to work with finite CPU and disk access bandwidth.

Glad that things are working out for you however!
DarrenH is offline   Reply With Quote
Old 01-21-2018, 09:39 AM   #42
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Quote:
Originally Posted by schwa View Post
The transport flashes red on a processing underrun, and optionally flashes yellow on a hardware underrun.
Mmh, this doesn't seem to properly here (5.70 x64).


RT CPU = above 100% (crackles and glitches can be heard)

Transport: no flashing


Shouldn't it flash when RT CPU is higher than 100%?
Dstruct is offline   Reply With Quote
Old 01-21-2018, 10:37 AM   #43
Luster
Human being with feelings
 
Luster's Avatar
 
Join Date: Nov 2015
Posts: 642
Default

Quote:
Originally Posted by schwa View Post
There is no persistent indication that an underrun occurred at a particular time, but there is an API function GetUnderrunTime, so one could write a script that would (for example) create a project marker when an overrun occurs.
No offence but wouldn't it make more sense to put this data directly into the interface of Reaper?
Because now we have to don't forget about the script and run it everytime we record something or put it in the default startup script, which is cumbersome when there is already something in it. This is very useful and can help everyone. Not just the ones checking our cool script heros work.
For example a little infotext in the record conformation prompt window would do it - which appears only when a dropout occured in case you switched that feature off.
Luster is offline   Reply With Quote
Old 01-25-2018, 03:40 AM   #44
nid
Human being with feelings
 
Join Date: Mar 2017
Posts: 19
Default

Quote:
Originally Posted by Luster View Post
No offence but wouldn't it make more sense to put this data directly into the interface of Reaper?
Because now we have to don't forget about the script and run it everytime we record something or put it in the default startup script, which is cumbersome when there is already something in it. This is very useful and can help everyone. Not just the ones checking our cool script heros work.
For example a little infotext in the record conformation prompt window would do it - which appears only when a dropout occured in case you switched that feature off.
That's exactly what Samplitude has and I don't know of any other DAW that does. At stop after rec/play it is informing you about how many asio errors occurred and putting a marker on the locations they happened (well some of them at least). Not all audible clicks are documented though. And BTW in a rec situation the dropouts are usually only "heard" and less often printed to file, but this I guess has to do with various system specific factors.
nid is offline   Reply With Quote
Old 01-25-2018, 06:16 AM   #45
Jack Winter
Human being with feelings
 
Jack Winter's Avatar
 
Join Date: Aug 2007
Location: Luxembourg/Spain
Posts: 1,922
Default

If I might ask, what ASIO drivers actually returns an error on under/over-runs?
__________________
Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
Jack Winter is offline   Reply With Quote
Old 01-25-2018, 06:20 AM   #46
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

None so far I think.


Posted this in the RME forums https://www.forum.rme-audio.de/viewtopic.php?id=26601 but no one seems to answer.
Dstruct is offline   Reply With Quote
Old 01-25-2018, 06:36 AM   #47
Jack Winter
Human being with feelings
 
Jack Winter's Avatar
 
Join Date: Aug 2007
Location: Luxembourg/Spain
Posts: 1,922
Default

In our testing RME didn't report it, though we haven't tested all RME cards..

Edit: It was my cynical suspicion that there was no commercial incentive in supporting this feature of ASIO, and unfortunately I get the feeling I was right :S
__________________
Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
Jack Winter is offline   Reply With Quote
Old 01-25-2018, 06:43 AM   #48
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,260
Default

Quote:
And BTW in a rec situation the dropouts are usually only "heard" and less often printed to file, but this I guess has to do with various system specific factors.
Seems an important distinction since I don't think I've had pop/click/artifact in an actual recording since maybe 2001? IOW, it has to get the data to the speakers in real time, not so on it's way to disk.
__________________
Music is what feelings sound like.
karbomusic is offline   Reply With Quote
Old 01-25-2018, 07:24 AM   #49
nid
Human being with feelings
 
Join Date: Mar 2017
Posts: 19
Default

Quote:
Originally Posted by Dstruct View Post
None so far I think.


Posted this in the RME forums https://www.forum.rme-audio.de/viewtopic.php?id=26601 but no one seems to answer.
So what is it that Samplitude is reporting as "Lost ASIO buffer: X" ? From where does it get that information? (X = number of lost asio buffers)
nid is offline   Reply With Quote
Old 01-25-2018, 07:25 AM   #50
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Maybe the same as REAPER's red flashing transport.
Dstruct is offline   Reply With Quote
Old 01-25-2018, 09:38 AM   #51
nid
Human being with feelings
 
Join Date: Mar 2017
Posts: 19
Default

In both programs there may be audible clicks that are not being reported in any way... Go figure...
nid is offline   Reply With Quote
Old 01-25-2018, 11:11 AM   #52
Jack Winter
Human being with feelings
 
Jack Winter's Avatar
 
Join Date: Aug 2007
Location: Luxembourg/Spain
Posts: 1,922
Default

Both CoreAudio and ALSA ought to report it to reaper, so it ought to work on both OS/X and Linux. Too bad that ASIO drivers don't seem to implement that part of the specification.
__________________
Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
Jack Winter is offline   Reply With Quote
Old 02-04-2018, 06:49 PM   #53
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Quote:
Originally Posted by nid View Post
So what is it that Samplitude is reporting as "Lost ASIO buffer: X" ? From where does it get that information? (X = number of lost asio buffers)
RME statement:

Quote:
Originally Posted by MC
kAsioOverload was supported in our HDSP drivers a long time ago. It worked with Samplitude, and maybe Samplitude only. It needs support in our hardware (!) and driver for this special function, but still was not 100% reliable. So it died for several reasons, and is now no longer present in our current drivers and hardware
Dstruct is offline   Reply With Quote
Old 02-04-2018, 06:49 PM   #54
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Quote:
Originally Posted by Dstruct View Post
RT CPU = above 100% (crackles and glitches can be heard)

Transport: no flashing


Shouldn't it flash when RT CPU is higher than 100%?

What about this? I'm the only one with that?
Dstruct is offline   Reply With Quote
Old 02-04-2018, 10:06 PM   #55
hopi
Human being with feelings
 
hopi's Avatar
 
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
Default

back to the OP.... yeah, it's a trick, but hey... it's a good one!
__________________
...should be fixed for the next build... http://tinyurl.com/cr7o7yl
https://soundcloud.com/hopikiva
hopi is offline   Reply With Quote
Old 02-05-2018, 02:38 AM   #56
Aux13
Human being with feelings
 
Join Date: Sep 2013
Location: Slovenia
Posts: 207
Default

Quote:
Originally Posted by ivansc View Post
They have just as many delusional immature users as we do and hopefully an even larger number of rational human beings to counterbalance them, like we do.
But they don't have Mac users, like we do.
Aux13 is offline   Reply With Quote
Old 02-05-2018, 07:54 AM   #57
clepsydrae
Human being with feelings
 
clepsydrae's Avatar
 
Join Date: Nov 2011
Posts: 3,409
Default

Quote:
Originally Posted by Dstruct View Post
What about this? I'm the only one with that?
Crackles and glitches in monitoring only or in the recorded audio?
Did I read/hear that the red flashing is for the latter?
clepsydrae is offline   Reply With Quote
Old 02-05-2018, 08:05 AM   #58
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Quote:
Originally Posted by clepsydrae View Post
Crackles and glitches in monitoring only or in the recorded audio?
Just playback.


Quote:
Originally Posted by clepsydrae View Post
Did I read/hear that the red flashing is for the latter?
Only to show hard disc access problems?
Dstruct is offline   Reply With Quote
Old 02-05-2018, 08:08 AM   #59
clepsydrae
Human being with feelings
 
clepsydrae's Avatar
 
Join Date: Nov 2011
Posts: 3,409
Default

Quote:
Originally Posted by Dstruct View Post
Only to show hard disc access problems?
Or when RT CPU thread drops incoming samples due to overload? I assume incoming audio buffers are treated with higher priority than outgoing, so outgoing would fail sooner...
clepsydrae is offline   Reply With Quote
Old 02-05-2018, 11:28 AM   #60
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Maybe.


But shouldn't the transport always flash when RT CPU is above 100%? Currently it doesn't.
Dstruct is offline   Reply With Quote
Old 02-05-2018, 11:56 AM   #61
clepsydrae
Human being with feelings
 
clepsydrae's Avatar
 
Join Date: Nov 2011
Posts: 3,409
Default

Quote:
Originally Posted by Dstruct View Post
But shouldn't the transport always flash when RT CPU is above 100%? Currently it doesn't.
I'm in favor. I can see the rationale for only flashing when incoming audio is lost (the dropouts/crackles function as a sort of warning, after all) but I like the idea of advance warning and feedback on this stuff, in general. E.g. some indication when the RT is over 75, 90, 95, etc. Arguably the RT meter itself is that feedback, but something low-profile and integrated (e.g. color changes in the transport bar) would be nice.
clepsydrae is offline   Reply With Quote
Old 02-05-2018, 11:59 AM   #62
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Exactly. +1
Dstruct is offline   Reply With Quote
Old 02-05-2018, 12:30 PM   #63
Jack Winter
Human being with feelings
 
Jack Winter's Avatar
 
Join Date: Aug 2007
Location: Luxembourg/Spain
Posts: 1,922
Default

Would be nice with a small bar meter in the right top or the transport showing current CPU & RT CPU. Extra points for a sticky over indicator too. Clicking on it could bring up the performance window.
__________________
Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
Jack Winter is offline   Reply With Quote
Old 02-05-2018, 12:47 PM   #64
clepsydrae
Human being with feelings
 
clepsydrae's Avatar
 
Join Date: Nov 2011
Posts: 3,409
Default

Quote:
Originally Posted by Jack Winter View Post
Would be nice with a small bar meter in the right top or the transport showing current CPU & RT CPU. Extra points for a sticky over indicator too. Clicking on it could bring up the performance window.
I'd also vote for the perf meter not hiding the RT thread by default, though i can see it both ways...
clepsydrae is offline   Reply With Quote
Old 02-07-2018, 02:17 AM   #65
ivansc
Human being with feelings
 
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Default

Quote:
Originally Posted by Aux13 View Post
But they don't have Mac users, like we do.
True...
__________________
Ici on parles Franglais
ivansc is offline   Reply With Quote
Old 07-16-2018, 03:08 PM   #66
Triode
Human being with feelings
 
Triode's Avatar
 
Join Date: Jan 2012
Posts: 1,180
Default

Quote:
Originally Posted by nid View Post

By the way is there any way of asio errors / dropouts indication in Reaper?
Isn't this reported in the Performance Meter under "RT xruns" ?

Incidentally I notice that when using the action via a key command to "Reset graph" this value is not reset to zero although when selecting the same function via the contextual menu right click it is reset.
__________________
Mixing / Brush and Beater Drums Online: www.outoftheboxsounds.com
Triode is offline   Reply With Quote
Old 07-16-2018, 10:28 PM   #67
cfillion
Human being with feelings
 
cfillion's Avatar
 
Join Date: May 2015
Location: Québec, Canada
Posts: 4,937
Default

Quote:
Originally Posted by Triode View Post
Isn't this reported in the Performance Meter under "RT xruns" ?
Yes, but it wasn't back in January (this feature was added in v5.79 - April 16 2018).
cfillion is offline   Reply With Quote
Old 11-09-2018, 09:42 AM   #68
mathieujm
Human being with feelings
 
Join Date: Mar 2008
Posts: 2
Default

Quote:
Originally Posted by Jack Winter View Post
Both CoreAudio and ALSA ought to report it to reaper, so it ought to work on both OS/X and Linux. Too bad that ASIO drivers don't seem to implement that part of the specification.
I am new here because I am tired with Lost Asio Buffers in Samplitude and Reaper seems really a good DAW in managing ASIO on PC.
But I have the same interrogation as Nid.
And even if I have glitches with very low buffers in Reaper, the xruns counters stay at 0. Actually I use a Tascam US-4x4 interface. I suppose the ASIO driver don't manage xruns ?
mathieujm is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 07:39 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.