If you do not maintain file versioning as part of the file names, you can just edit files in the Audio folder without changing their names, making sure that any edits done to the files within Cubase have been frozen beforehand. Cubase will just use the RX3 edited files as is. RX3 will not open .w64 files, only the .wav ones.
yes Greg that was a great feature ,i used to use this to work in cool edit pro before moving to wavelab . it would be great if it could be reintroduced in some form ,maybe the same way it exists in Halion 5 ?
Yes, Logic, Reaper, Studio One and Live all have the option to edit your audio very neatly in an external editor, Cubase should have this feature also. Or massively expand the internal editors capabilites, but to reach the level of Izotope RX is unlikley that it can be done, and would also add bloat to folks who dont need an advanced editor.
wow - just discovered this. Steinberg, you need to get your act together. As a pro sound designer in the games industry, I want desperately to like Cubase, but things like this just keep getting in the way.
Being able to hook directly to an external sound editor like Sound Forge and Cubase recognise that the file has been updated, is an ABSOLUTE ESSENTIAL feature.
Unbelievable.
If you notice, the parts go from the coarsest at the start, to the finest at the end, so that a raw file listing, sorted by name, will show all the files for one track by code, then instrument, then record date, then edit date.
Such regular formats make it easier to use scripts fies, like vbscript or jscript, to process tracks. I just wish the project files were XML, so that I could automatically update then with the externally edited track versions names.
There are chances that everyone of us in this forum use an audio editor for making/tweaking samples, loops, or any other creative purposes.
Fortunately we have enough choice in that field: from veterans like TwistedWave, Hokusai, WavePad, to newcomers like Auditor and Neon ( even Koala ), to mention just a few.
Often some convenient features found in one app are lacking in others. Some apps have a dense UI with lots of buttons, menus, pages, others are more on the minimalist side, yet sometimes not terribly obvious to use.
Immediate opening of audio files from an integrated browser or from Files ( wav, mp3, m4a, flac, ogg and more ).
Browser with access to any folder in Files ( including external storage ), search function, waveform preview and gapless looping of the selected file,
Drag and drop to the workspace, visible file extension...
I'll be keeping an eye on this app...
...still got some 'bugs' in it and it's quite easy to loose a recording if you tap 'Home' by accident.
Also have not found any way yet to remove markers?!
This isn't a criticism in any way, but it's currently missing only one feature that means I won't be using it often, even though I would really like to. To be useful to me, in most cases, an audio editor has to be able work with tempo, beats and measures.
It would be nice for people who own Adobe Audition, Wavelab, Sound Forge and similar editors to have a function to open an audio file in one of those external editors, with file sharing enabled, directly from Studio One, and any edits done in them automatically updated in Studio One's timeline and file when the external edit is saved and closed.
Open In External Editor, the option and a key binding or modifier to do it, with the user being able to choose the editor to open and edit with in the preference screen, to take advantage of some things those editors may allow, like Spectral Editing.
As an old Cakewalk and Sonar user, I am wondering if it is possible in this new Bandlab edition of the software to add an external audio editor such as Sound Forge under the "utilities" menu for Quick editing of wave files? I have searched but have not been able to find anything covering this topic.
I cannot find a section in the preferences to set the directory of an external audio editor. Reading the reference manual there is an option in Cakewalk.ini - ToolTempFileDir. But I can't seem to get it to work.
I've downloaded your project file and I found the audio to be more than just sometimes "crackly"... in all honesty, the audio is not of real good quality. It seems that your recording levels are set way too high....
The HTML5 version worked in Chrome, IE, and Firefox. However, no sound could be heard when viewing the course in another Chrome-based browser. I found that one of the browser extensions was causing the issue. in my case it was caused by IDM - Internet Download Manager.
Please check for, and disable any extensions from download managers in both browser and actual download manager program. (IDM only stopped interfering when I deselected the advanced browser integration option within the software itself)
It looks like Rutwin is assisting you here, and I'd agree with his recommendation to test and set your recording level within Windows and try to record first outside of Storyline to see how the recording comes through on it's own and when you import into Storyline, and then check recording within Storyline again. If the audio recordings still sound off outside of Storyline, it might be worth looking into updating your headset drivers. These are usually available on the manufacturer's website.
You are quite right that the levels in Storyline were set to high - I had actually done this on purpose because although it decreased the quality of the audio, it could at least be heard! Agreed, it wasn't the best solution.....
I am having a particularly unusual and similar issue. I have video track on my timelines and then separate audio narration tracks. In preview mode they play together fine. However, when publishing the project, when I then play this in Chrome, the audio does not kick in with the video. It WILL HOWEVER kick in, if i quickly click on another tab in Chrome and then head back immediately into the tab where the scorm is playing. I can replicate that each and every time on several different machines. I have even replaced the narration audio files (.WMA format) with .mp3 and it still displays the issue. This is very very odd and really published should mimic published. A deadline looms. Any ideas?
Reaper is open-source software which means that people are able to make contributions that shape the direction of the program. Because of this, blind people, in close collaboration with Cockos, the developers of Reaper, have been able to write a plugin called Osara that adds a number of keyboard actions to Reaper as well as making the product speak in ways it might not otherwise. Reaper runs on both Windows and Mac, and is equally accessible on both platforms.
Although it is possible to use Reaper free forever with just a few reminders to pay for the product, the $60 U.S. is well worth the money for anyone who truly makes use of the product. Whether you are a professional musician, a singer, or someone editing podcasts for others, the sky is pretty much the limit for anyone using Reaper.
Reaper is also a multitrack editor, which means that you can add many layers of sound to a project whether it be birds, rain, wind, and water, or many instruments playing your original composition. You can add effects such as reverb to your project, and manipulate it in a seemingly endless number of ways.
In addition to the Reaper Made Easy site, you can also visit the Reaper Accessibility Website. This site is a Wiki, which means that the site receives regular contributions from experienced users. This is a great resource for starting from the ground floor as far as learning to use Reaper is concerned. Once you become comfortable with the basics, you can move on to more advanced articles of interest to you depending on how you intend to use Reaper, regardless of your operating system of choice. Many people use Reaper on both Windows and Mac, transferring projects from one computer to another for convenient editing.
Another great resource is the Reapers Without Peepers email list. This is a very high-traffic list, but it is well moderated. Although the list owner keeps subjects on topic, Reaper is such a powerful piece of software that many areas of discussion are permitted.
The Reapers Without Peepers (RWP) moderator can also provide you with access to a shared Dropbox folder that contains a ton of great content from tutorials to examples of audio and music produced with Reaper as well as information about virtual instruments and audio interfaces that work with Reaper.
For anyone who is serious about producing high-quality audio using software whose developers are truly interested in making their product accessible to the blind, Reaper is a great program to consider. Making Reaper even more appealing, there are a number of high-quality training resources, both free and paid, that can help you learn Reaper as a blind person. At $60, Reaper is affordably priced for most, and provides a 60-day trial period before you are asked to purchase the software. It runs on Windows and Mac, and works with VoiceOver, JAWS for Windows, and NVDA.
b1e95dc632