Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Andrew Broughton]

The rule against it is in the licence agreement that a licensee must sign when joining the program.

"A license agreement to use the SD standards"
https://www.sdcard.org/join/pdf/SDA-License-Agreement.pdf

As can been seen in the attached picture there exist only three standards.

The license could be nothing more than permission to use the SD card logo. I still haven't seen anything anywhere that clearly states that it's illegal or otherwise not permitted to format SDXC in FAT32 > 32gig.

[Corey Scogin]

I did this quick(?) video showing how-to import xlive audio into some daws.

Enjoy!

https://youtu.be/hOaTGyo2xYg

If you picked "Single Track" when importing into Reaper, you wouldn't have to drag/drop them to get them to line up.

After splitting, select all the new tracks and render stems gives you full-length files.

[Robert Lofgren]

I had issues in some daw where the files were imported out of order or backwards so I opted for the safe approach.

Each daw had it own quirks when it came to multi-channel wave files :-(

If you picked "Single Track" when importing into Reaper, you wouldn't have to drag/drop them to get them to line up.

After splitting, select all the new tracks and render stems gives you full-length files.

[Corey Scogin]

I did this quick(?) video showing how-to import xlive audio into some daws.
Enjoy!
https://youtu.be/hOaTGyo2xYg

For anyone interested in a faster way to explode X-Live wav files in Reaper, I created a custom script. You can download it here. (save the link target to a file)

To install it: Download it. In Reaper type "?" to bring up the actions list. Next to ReaScript, click Load. Select the downloaded script.

To use it: Select a multi-channel item in Reaper and run the script. It will explode the item immediately without rendering. You can then select the tracks you need as mono files and render stems as usual in Reaper. This script will work for multiple files/items.

Edit: updated for direct link to file.

[Will "GLiDE" Mims]

For anyone interested in a faster way to explode X-Live wav files in Reaper, I created a custom script. You can download it on Github here.

The script is in the Items Editing subfolder. It's named "CoreyScogin_Explode multi-channel items to mono without rendering.lua". It's the only script there for now.

To install it: Download it. In Reaper type "?" to bring up the actions list. Next to ReaScript, click Load. Select the downloaded script.

To use it: Select a multi-channel item in Reaper and run the script. It will explode the item immediately without rendering. You can then select the tracks you need as mono files and render stems as usual in Reaper. This script will work for multiple files/items.

Call me stupid, but I put all of the .wav files into one track, selected them all in that track and ran the script.  This is what I got in a window:

"  ...xplode multi-channel items to mono without rendering.lua:7: unexpected symbol near '<'    "

[Corey Scogin]

Call me stupid, but I put all of the .wav files into one track, selected them all in that track and ran the script.  This is what I got in a window:

"  ...xplode multi-channel items to mono without rendering.lua:7: unexpected symbol near '<'    "

That had me confused for a minute. I didn't realize that GitHub doesn't really let you download individual files correctly. It saves a file with the right extension but the file is actually an html file, not the source file.

Download the whole repository as a zip using the Clone or Download link, unzip it, then find the file you need.

I changed the README to reflect the more precise instructions. Apologies for the confusion.

[Scott Holtzman]

That had me confused for a minute. I didn't realize that GitHub doesn't really let you download individual files correctly. It saves a file with the right extension but the file is actually an html file, not the source file.

Download the whole repository as a zip using the Clone or Download link, unzip it, then find the file you need.

I changed the README to reflect the more precise instructions. Apologies for the confusion.

Corey I don't thing you are "getting" git.  You need to download git tools for whatever platform you are using.  Linux has the best tools.  You then "checkout" your project and can fork it (branch revisions) or simply have a local sync'd clone. 

Github has a nice desktop utility https://desktop.github.com/

[Corey Scogin]

Corey I don't thing you are "getting" git.  You need to download git tools for whatever platform you are using.  Linux has the best tools.  You then "checkout" your project and can fork it (branch revisions) or simply have a local sync'd clone. 

Github has a nice desktop utility https://desktop.github.com/

Scott, I know how to use Git. I included instructions for those just needing access to the script file. If someone just needs a single script file from a larger repo (granted, the one I linked is just 1 file) they don't need to install the Git tools, they just need to download the file. Github doesn't let you download single files via a web browser so downloading the repo as a zip is the best option.

I didn't realize that on GitHub, if you right/ctrl click on a file and download it, it saves it as the full file name with the extension but the file contents are html. This makes no sense from an expected functionality perspective.

[Wes Garland]

You can download a single file from a github repo - you just need to use the raw file option, like this:
https://raw.githubusercontent.com/wesgarland/gpsee/master/modules/gffi/WillFinalize.c

instead of this:
https://github.com/wesgarland/gpsee/blob/master/modules/gffi/WillFinalize.c

[Corey Scogin]

You can download a single file from a github repo - you just need to use the raw file option, like this:
https://raw.githubusercontent.com/wesgarland/gpsee/master/modules/gffi/WillFinalize.c

instead of this:
https://github.com/wesgarland/gpsee/blob/master/modules/gffi/WillFinalize.c

I'm not new to Git but I haven't used GitHub much. Thanks for the tip. I'll update my link above to reflect this.

[ProSoundWeb Community]