|
|
|
05-27-2020, 11:32 PM
|
#1
|
Human being with feelings
Join Date: Feb 2012
Location: Pittsburgh, PA
Posts: 107
|
So Mad I Can't Stand It
Ach du frickin' lieber..............
Time sensitive trying to get a groove on and ......merde....scheisse
For no damned reason my midi virtual instruments are no longer audible.....scheisse.....when they were yesterday and not a blessed thing has changed...........so much for groove.
Reaper current update.
Apollo Twin USB
Yamaha piano through Roland Quad Capture for midi instruments - - - -
Shiite
Tracks very much appear to be getting signal but ZERO audible output..........I absolutely do not get this.
Used Reaper for years and love it..........but something is seriously amiss................ and I cannot fricking figure it out.....
And I am whining and crying cuz ..........................hours ago I had a creative idea that is long since dead...............merde.
|
|
|
05-27-2020, 11:41 PM
|
#2
|
Human being with feelings
Join Date: Jan 2020
Posts: 1,927
|
You can see tracks registering MIDI input, but hear no sound?
|
|
|
05-28-2020, 03:12 AM
|
#3
|
Human being with feelings
Join Date: Feb 2008
Location: 6950 DK
Posts: 661
|
Apologies if this sounds too simple but have you switched on the channel monitoring?
__________________
REAPING HAVOC SINCE 2008
|
|
|
05-28-2020, 07:26 AM
|
#4
|
Human being with feelings
Join Date: Dec 2009
Location: Chicago, Il USA
Posts: 706
|
Same issue going on here? What at the chances of that? I swear MS is messin with our drivers with all these updates. Just have to keep pushing buttons till I hear something.
__________________
"significantly better than bad..." - Dell XPS i7, 16G Ram, Win 10 64Bit, REAPER 64Bit, MOTU Audio Express, PG Music - BIAB 2020, Kontakt 5, more VSTs than I know what to do with. Will trade all to play the guitar and keys better!
|
|
|
05-28-2020, 01:00 PM
|
#5
|
Human being with feelings
Join Date: Jan 2020
Posts: 680
|
Very upsetting and frustrating things like that....
Hope I am not teaching you to suck eggs........
Do you know if it is a Reaper issue or a PC/monitoring problem? That must be the first step.
Suggest:
Monitor with h/s on pc sound card output. Play m/soft test sounds. Next playback another source such as a youtube video or browser/soundcloud or similar source or cd.
Then a known good Reaper project rather than your current one via sound card then via your normal monitoring route.
Then your current project.
Results:
By now you should know if it is an 'external to Reaper, internal Reaper/interfacing issue or a current project setting monitoring problem.....and then take it from there.
|
|
|
05-28-2020, 01:45 PM
|
#6
|
Human being with feelings
Join Date: Jan 2014
Posts: 5,220
|
Check your volume CC
|
|
|
05-29-2020, 05:30 AM
|
#7
|
Human being with feelings
Join Date: May 2006
Location: Surrey, UK
Posts: 19,681
|
Perhaps you could compress a simple problem project file, using ReaSynth (no audio samples needed) into a ZIP file and post it here as an attachment so that we can have a look at it and see what's (not) happening?
How to post attachments (in Post #1)
__________________
DarkStar ... interesting, if true. . . . Inspired by ...
|
|
|
05-29-2020, 07:54 AM
|
#8
|
Human being with feelings
Join Date: Jul 2010
Posts: 389
|
I had a similar situation recently after upgrading both Reaper and Steven Slate Drums 5 to 5.5 (on MacOS 10.15 Catalina). It was a challenge to figure out, but I ended up manually deleting and rebuilding the routing for each SSD output/Reaper track and things are back to normal. I initially thought that this was a SSD issue, but reading through this thread, maybe it was a Reaper issue.
|
|
|
05-29-2020, 04:58 PM
|
#9
|
Human being with feelings
Join Date: Feb 2012
Posts: 477
|
This is the kind of thing that makes me cautious about immediately installing REAPER updates and keeps me away from exclusively switching to Windows 10.
|
|
|
06-04-2020, 05:39 AM
|
#10
|
Human being with feelings
Join Date: Feb 2008
Location: 6950 DK
Posts: 661
|
Quote:
Originally Posted by Peterk312
This is the kind of thing that makes me cautious about immediately installing REAPER updates and keeps me away from exclusively switching to Windows 10.
|
Still on 5,98 and win 7 here... LOL
__________________
REAPING HAVOC SINCE 2008
|
|
|
06-04-2020, 06:26 AM
|
#11
|
Human being with feelings
Join Date: Oct 2010
Location: Charleston, SC
Posts: 12,792
|
Quote:
Originally Posted by Peterk312
This is the kind of thing that makes me cautious about immediately installing REAPER updates and keeps me away from exclusively switching to Windows 10.
|
It's easy to reinstall an earlier version Reaper though if you have problems. Like right now with the freeze issues I'm going to roll back until that gets fixed
|
|
|
06-05-2020, 01:48 AM
|
#12
|
Human being with feelings
Join Date: Apr 2013
Location: Perth, Australia
Posts: 169
|
After Reaper update to 6.11 a similar thing happened to me, only it was just one audio input of my RME digiface was not showing a signal even though I tested on other programs and older Reaper and it worked there.
It turned out after an hour or so of frustration that dulled my creative spark somewhat, it was a setting buried deep that I hadn't changed since the previous version.
It was in Preferences by selecting "Audio" on the left (which is actually a main heading)> on the right at the bottom in Channel naming/mapping, input section > Edit Names/Mapping, and there I found that my named input 5 was assigned to the physical input 4 also. Hence input five was skipped! unknown and inaccessible to Reaper due to this.
Check your output assignments here. Bearing in mind there is also the setting directly under "Audio" main heading called "Device" where there are also io assignments to be made. That was what put me out, cause I was only checking in Device assignments.
Last edited by bcslaam; 06-05-2020 at 01:58 AM.
|
|
|
06-05-2020, 02:43 PM
|
#13
|
Human being with feelings
Join Date: Dec 2010
Location: Hampstead, NC
Posts: 241
|
MAYBE related 6.11 symptom here as well. Have NOT tackled it yet, as I just reverted to back to 6.10 as a workaround.
- Upgraded to 6.11 from 6.10.
- Opened up a VERY involved project - 85 tracks
- Soloed ONE track for a special one-off rendering
- Played the song in real time - could hear the soloed track (meters displaying, etc)
- The song has a single region so no lead-in or extra fade-out in in the rendered file
- Open Render, and render regions, just one. Fast offline render.
- The rendered file is empty, full length
- When rendering there was no action visible in the meter in the render dialog.
Reverted back to 6.10 - no repro.
Going to investigate later. If it doesn't repro, so be it.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 01:10 PM.
|