Reason 13 Bug - track muted on export
-
- Posts: 16
- Joined: 03 Nov 2016
- Location: Memphis
Hey folks. I'm having a weird issue I can't figure out how to solve. It only started happening on this track this evening -- previously it worked fine.
I noticed after exporting a song one of the tracks was missing. Playing it back in Reason, I can see it's there, unmuted, and it plays during playback. However, when I watch it exporting, I notice this track mutes itself halfway through export.
It is an audio track, not MIDI, and it doesn't have any VSTs or non-built-in effects on it, just a compressor and reverb. As far as I can tell, this is the only track doing this, but now I'm worried it could be doing this without me noticing.
I have Mac OS 15.2, I confirmed Reason is up to date, and the issue occurs both with Rosetta enabled and in native Silicon.
I noticed after exporting a song one of the tracks was missing. Playing it back in Reason, I can see it's there, unmuted, and it plays during playback. However, when I watch it exporting, I notice this track mutes itself halfway through export.
It is an audio track, not MIDI, and it doesn't have any VSTs or non-built-in effects on it, just a compressor and reverb. As far as I can tell, this is the only track doing this, but now I'm worried it could be doing this without me noticing.
I have Mac OS 15.2, I confirmed Reason is up to date, and the issue occurs both with Rosetta enabled and in native Silicon.
-
- Moderator
- Posts: 11553
- Joined: 28 Dec 2015
What does it mean, you see it muting itself?
Reason13, Win10
-
- Posts: 16
- Joined: 03 Nov 2016
- Location: Memphis
-
- Moderator
- Posts: 11553
- Joined: 28 Dec 2015
Ok. It just doesn't generate any audible sound.
Can you post a picture of the instrument area from the back of the rack? Which instruments and effects are on it?
Does it happens only on export, I speculate it is a VST with some export restrictions. Maybe not a full license.
Can you post a picture of the instrument area from the back of the rack? Which instruments and effects are on it?
Does it happens only on export, I speculate it is a VST with some export restrictions. Maybe not a full license.
Reason13, Win10
-
- Posts: 16
- Joined: 03 Nov 2016
- Location: Memphis
As I mentioned, it's just in-the-box stuff. Compression and reverb. The "Hi Shaker" is not exporting out as expected.Loque wrote: ↑22 Jan 2025Ok. It just doesn't generate any audible sound.
Can you post a picture of the instrument area from the back of the rack? Which instruments and effects are on it?
Does it happens only on export, I speculate it is a VST with some export restrictions. Maybe not a full license.
Edit: Here's a drive link:
-
- Moderator
- Posts: 11553
- Joined: 28 Dec 2015
And I think, you already checked the automation of the audio channel...
If the automation is ok or there isn't any, that is seriously odd...
Maybe someone else has an idea or let someone else try to render your audio and see what happens.
If the automation is ok or there isn't any, that is seriously odd...
Maybe someone else has an idea or let someone else try to render your audio and see what happens.
Reason13, Win10
-
- RE Developer
- Posts: 12360
- Joined: 15 Jan 2015
- Location: The NorthWoods, CT, USA
Have you done any basic troubleshooting yet?
Here is where I would start if experiencing ‘weirdness’.
Things to try…
Remove any possible variables:
Bypass or remove the inserts and test.
Solo the shaker and test.
Render just the part where the problem starts.
Also (assuming you’re “exporting audio”):
Try a “bounce mixer channels” instead with just the master channel selected - same problem?
Try a REC SOURCE bounce from the Master Channel to an new audio channel (real time bounce) - same problem?
Here is where I would start if experiencing ‘weirdness’.
Things to try…
Remove any possible variables:
Bypass or remove the inserts and test.
Solo the shaker and test.
Render just the part where the problem starts.
Also (assuming you’re “exporting audio”):
Try a “bounce mixer channels” instead with just the master channel selected - same problem?
Try a REC SOURCE bounce from the Master Channel to an new audio channel (real time bounce) - same problem?
Selig Audio, LLC
-
- Posts: 16
- Joined: 03 Nov 2016
- Location: Memphis
All of these render the same effect:selig wrote: ↑22 Jan 2025Have you done any basic troubleshooting yet?
Here is where I would start if experiencing ‘weirdness’.
Things to try…
Remove any possible variables:
Bypass or remove the inserts and test.
Solo the shaker and test.
Render just the part where the problem starts.
Also (assuming you’re “exporting audio”):
Try a “bounce mixer channels” instead with just the master channel selected - same problem?
Try a REC SOURCE bounce from the Master Channel to an new audio channel (real time bounce) - same problem?
-- Bouncing solo with no effects or automation
-- Bouncing the master track
-- Bouncing only the section of the song where it occurs
-- Exporting the track solo
-- Exporting the song
-- Exporting a loop
-- Exporting a loop starting from after the point where the issue occurs
This is the only way I've gotten it to work:
-- Use Loopback to record me playing the song back live in Audacity -- I think this is like REC SOURCE?
-
- Moderator
- Posts: 11553
- Joined: 28 Dec 2015
Than it could be a bug and you should raise a ticket.
Reason13, Win10
-
- RE Developer
- Posts: 12360
- Joined: 15 Jan 2015
- Location: The NorthWoods, CT, USA
Yes, REC Source is internal "loop back", so technically a shorter path (and a simpler setup!).HuskyInDenial wrote: ↑22 Jan 2025All of these render the same effect:selig wrote: ↑22 Jan 2025Have you done any basic troubleshooting yet?
Here is where I would start if experiencing ‘weirdness’.
Things to try…
Remove any possible variables:
Bypass or remove the inserts and test.
Solo the shaker and test.
Render just the part where the problem starts.
Also (assuming you’re “exporting audio”):
Try a “bounce mixer channels” instead with just the master channel selected - same problem?
Try a REC SOURCE bounce from the Master Channel to an new audio channel (real time bounce) - same problem?
-- Bouncing solo with no effects or automation
-- Bouncing the master track
-- Bouncing only the section of the song where it occurs
-- Exporting the track solo
-- Exporting the song
-- Exporting a loop
-- Exporting a loop starting from after the point where the issue occurs
This is the only way I've gotten it to work:
-- Use Loopback to record me playing the song back live in Audacity -- I think this is like REC SOURCE?
I was also going to ask if the track is muting (is the mute button lighting) or is it just glitching out at that point with otherwise no indication?
Is there any way to re-render the audio, or copy the first part over the later part, or re-import the audio?
Or even just try this: create a new empty audio track and drag the clip into this track and see if the problem is with the audio file/clip or with the track/channel.
Selig Audio, LLC
-
- Posts: 16
- Joined: 03 Nov 2016
- Location: Memphis
Just to answer what I can, the track doesn't activate mute or anything. It's as if there's nothing on the track after a certain point.selig wrote: ↑22 Jan 2025Yes, REC Source is internal "loop back", so technically a shorter path (and a simpler setup!).HuskyInDenial wrote: ↑22 Jan 2025
All of these render the same effect:
-- Bouncing solo with no effects or automation
-- Bouncing the master track
-- Bouncing only the section of the song where it occurs
-- Exporting the track solo
-- Exporting the song
-- Exporting a loop
-- Exporting a loop starting from after the point where the issue occurs
This is the only way I've gotten it to work:
-- Use Loopback to record me playing the song back live in Audacity -- I think this is like REC SOURCE?
I was also going to ask if the track is muting (is the mute button lighting) or is it just glitching out at that point with otherwise no indication?
Is there any way to re-render the audio, or copy the first part over the later part, or re-import the audio?
Or even just try this: create a new empty audio track and drag the clip into this track and see if the problem is with the audio file/clip or with the track/channel.
-- When I tried simply duplicating the track and exporting the newer version, the issue still occurred.
Haven't tried the other stuff yet.
-
- RE Developer
- Posts: 12360
- Joined: 15 Jan 2015
- Location: The NorthWoods, CT, USA
It’s likely a weird and rare file corruption of some sort, which is why duplicating won’t change anything (you are copying the ‘error’). That’s why I suggested creating a NEW track and dragging a copy of the audio clip there. If it solves the issue it was corruption of the channel data. If not, it is likely the audio file.HuskyInDenial wrote: ↑24 Jan 2025Just to answer what I can, the track doesn't activate mute or anything. It's as if there's nothing on the track after a certain point.selig wrote: ↑22 Jan 2025
Yes, REC Source is internal "loop back", so technically a shorter path (and a simpler setup!).
I was also going to ask if the track is muting (is the mute button lighting) or is it just glitching out at that point with otherwise no indication?
Is there any way to re-render the audio, or copy the first part over the later part, or re-import the audio?
Or even just try this: create a new empty audio track and drag the clip into this track and see if the problem is with the audio file/clip or with the track/channel.
-- When I tried simply duplicating the track and exporting the newer version, the issue still occurred.
Haven't tried the other stuff yet.
Since it’s just one audio file, you could also try to bounce just that audio file, using REC SOURCE to a new audio track because you say it plays fine, right? It would be HIGHLY unlikely to copy the error to the new file, so definitely try this so you can move on and get work done!
Selig Audio, LLC
-
- Posts: 16
- Joined: 03 Nov 2016
- Location: Memphis
I contacted Reason support, and they had me install a logging version of Reason.
In the logging version of the app, the audio in the track actually DOES cut off. Even when doing playback, the audio information is MISSING, visibly!
.... and now when I open the file in the regular version of Reason 13, the audio is gone ;_____________; I tried downloading an old backup file from before I made edits this month, and it's gone from there, too!
I remembered I'd been using a beta version of the app, and even after re-installing the latest beta, the data is gone, even from old files, even after deleting and redownloading my backup.
I tried opening up the old original one in Reason 12 where it was originally created, and now it's gone there, too, and I just don't understand how after installing a logging version it's just gone in every version of the file I have, even ones from March of last year. Objectively, the audio was THERE a week ago!
I have audio proof that it used to be there and that it's not anymore.
Now what do I do? Do I really have to go back and rerecord this stuff? Why would this happen? Why would it happen RETROACTIVELY?
I sent the logs to Reason's support, along with audio files, but like... man. I shouldn't have to worry about this happening.
-----------------------------
EDIT:
So, I kept playing with it, and if I "disable stretch," then all the audio comes back. So I guess some kind of glitch happened there. Audio is recovered and bounced, and that's what matters.
In the logging version of the app, the audio in the track actually DOES cut off. Even when doing playback, the audio information is MISSING, visibly!
.... and now when I open the file in the regular version of Reason 13, the audio is gone ;_____________; I tried downloading an old backup file from before I made edits this month, and it's gone from there, too!
I remembered I'd been using a beta version of the app, and even after re-installing the latest beta, the data is gone, even from old files, even after deleting and redownloading my backup.
I tried opening up the old original one in Reason 12 where it was originally created, and now it's gone there, too, and I just don't understand how after installing a logging version it's just gone in every version of the file I have, even ones from March of last year. Objectively, the audio was THERE a week ago!
I have audio proof that it used to be there and that it's not anymore.
Now what do I do? Do I really have to go back and rerecord this stuff? Why would this happen? Why would it happen RETROACTIVELY?
I sent the logs to Reason's support, along with audio files, but like... man. I shouldn't have to worry about this happening.
-----------------------------
EDIT:
So, I kept playing with it, and if I "disable stretch," then all the audio comes back. So I guess some kind of glitch happened there. Audio is recovered and bounced, and that's what matters.
-
- Posts: 680
- Joined: 16 Jan 2015
My understanding of the way Reason handles audio is that only the original recording is saved into the song file, along with data describing any further processing performed (time stretch, sample rate conversion, etc). The final rendered result of any additional processing is stored in the scratch disk, which then functions like a cache when loading the song file.
I would guess that there was some issue with the contents of your scratch disk (the time stretched audio). Since that data isn't actually stored in the song file, it makes sense that even old song files would have the issue despite no changes. By disabling stretch, you're no longer loading the corrupt time stretched audio from the scratch disk.
I would guess that there was some issue with the contents of your scratch disk (the time stretched audio). Since that data isn't actually stored in the song file, it makes sense that even old song files would have the issue despite no changes. By disabling stretch, you're no longer loading the corrupt time stretched audio from the scratch disk.
-
- Information
-
Who is online
Users browsing this forum: Ahrefs [Bot], CommonCrawl [Bot], tarsiidea and 5 guests