IMPORTING SOUND MODULE PATCH NAMES

I am trying to set up several sound modules in logic and want to know if there is a way to import the present names / banks from the modules. Am using vintage keys, Alesis nano bass and QSR and Roland JV1080
Cheers,
Paul.

Logic 8 can (mostly) load songs from Logic 5 through to 8.
If the songs are in version 4.x formats or earlier, they will need to be loaded into LP7 first and resaved, before 8 can get access to their contents.

Similar Messages

Where are my sound module preset names in the track list?

I've been using Logic since version 2.5 and, since I have several MIDI sound modules whose sounds I'm perfectly happy with, I am now using those sound modules with Logic 8.
But having just upgraded to 8 from 7, I've discovered something I think is missing, which is a bit of an annoyance.
In all previous versions of Logic, if you set up a instrument in the Environment for a MIDI sound module and then added all the preset names when you set up the bank/program change commands, when you select a preset from the track list in the Arrange window, the name in the track list changed from the name of the instrument to the name of the preset.
For example, the name would change from 'Fantom XR' (the name I'd called the instrument in the Environment) to 'PNO SoTrue' (the name of the preset) in the track list when I selected that preset via Logic.
However, in Logic 8, when I select a preset, the name on the track list now stays as 'Fantom XR' (or whatever the name of the instrument is) and doesn't change to that of the preset.
Given that I use six MIDI modulss, keeping track of the sounds by having the trak list name change to that of the presets was really useful for keeping track of what was what.
Have I just missed something with how to do it, or is a permanent change? I really hope not.

No, it's still there, but the interface has changed.
Right-click on a track and select "Configure Track Header"
In the box that comes up, enable the checkbox under "Names" and next to it (the second flip menu), select "Software Instrument Setting Name".
Now the program names in your multi-instruments are displayed in the manner you have been accustomed to.
As ever, save this stuff in your autoload to always have you own configs available.
You have some options there in that the two flip menus determine the first and second displayed track name, so you can set up how you like - it's more flexible than earlier versions of Logic.

How to Import Yamaha Motif XS 8 Patch Names into Logic?

Hello -
I am a new user of MAC plus Logic. I just installed Logic Studio with Apogee ensemble. The virtual instruments are working great and I am able to browse the patch names by banks and catagories. Just downloaded a logic patch file from yamaha site for my Motif XS 8 Synthesizer. The has a .LSO extention. When I click on the file, the logic environment window opens up and I can see the patches. How do I import these patches into my project environment.
Any help on this will be greatly appreciated.

Open up the source song, the one you downloaded with the environment (old Logic songs were *.lso files).
You'll probably see an environment window, showing a multiinstrument - it's this that has the bank messages and the patch names defined.
Select the multiinstrument, and edit -> copy.
Now close that song.
Open up your default startup template song (the "destination" song), open the environment on a layer of your choosing, and select edit -> paste, to paste that multi-instrument into the environment of this song.
Change the MIDI port on that multi-instrument so it's sending to the port your hardware is connected to. Close the environment window, and resave the song as your startup template.
(You may wish to preassign the 16 multi-instrument sub MIDI channels to arrange tracks if you are regularly sequencing them, to save time so these are already assigned to tracks when you start.)
Now for every song you start, it will have your setup for the Motif.
Does that help?

Importing patch names into Logic Express

Anyone know of a utility that will allow me to get the patch names out of my hardware synths and into Logic?

Yes, but the utility built into Logic is a simple cut/paste from a text file. I have 6 synths each with multiple banks and a lot of custom patches. Even if I could find the patch lists in .txt format it would still be a lot of typing. There has to be a better way. I've seen PC software that can pull patch names directly from synths via sysex. Logic can't do this as far as I know so I'm looking for a 'helper app' that can. I know Sound Diver used to be a way of doing this but as far as I know it's pretty much dead.

How to import patch names?

I am trying to load the patch names for a roland fantom xr. I've read about 50 posts regarding this but all seem very convoluted. In ProTools, you simply load the .midnam file. What's the best way to do this in logic 9

Hi
Unless you can find a ready-made Environment MultiInstrument with all the right patch names, Bank Select messages etc., you have a boatload of copy & pasting (you have to do this a bank at a time from some kind of text file of the patch names).
Perhaps this will get you in the right direction?
http://www.logicprohelp.com/forum/viewtopic.php?f=9&t=5419
CCT

Using my external midi instrument, Yamaha PSR-540 as a sound module

I use Logic Studio/Logic Pro 8.0.2. I have figured out how to record rhythms from my Yamaha PSR-540 keyboard as midi onto my arrange window as I couldn't find a similar loop within Logic. Due to my keyboard's timing being different to Logic I have now figured out how to get Logic to trigger my keyboard as a sound module/source also; however, Logic is only seeing a random selection of 128 of the 707 XG/GM sounds on my keyboard and not the sound I need (which is an XG [Expanded General Midi] sound = Rock Toms). These 128 sounds are listed via the Environment window, clicking box 1 on the multi-track instrument object shown and then double-clicking on box 1. This window details two key things as well, Bank: (No Bank specified, Names of Bank 0 used) and Bank Message: (Control 32). I've tried altering these in the hope Logic brings up a different listing of my keyboard's sounds but to no luck. Please help if you can. Thank you very much.

Antidisestablishmentistarism wrote:
Thanks. I checked out those XG synth specs v1.26 and I looked at Logic's manual page 887 etc. I then looked at my keyboard's manual again and although it didn't tell me much, I think I'm after LSB rather than MSB. By now having these two other places to look it allows me to make many variations; however, I don't really know how to really connect the dots between those synth specs v1.26 and making the appropriate changes in the Define Custom Bank Messages and Multi Instrument Windows. Bit over my head and have been trying for about 10 hours since. Is it possible to get my hands on an environment with all the correct presets for such a problem?
A site that's been around for ages.
http://www.swiftkick.com/
Under downloads Logic Environments/Logic Users Group/Synth Editors
It's been a long time since I looked at any of these, they're from older versions of Logic but probably can be imported by layer.
pancenter-

Patch names for Roland?

I'm getting lost in the Environment chapter. I'm trying to set up my Roland JV-1010 external synth module, and not getting the sounds working right. I'm sure there are several problems, which I'll work through one by one, but this I can see is going to be a key:
Is there some way to get the Roland's several banks of patch names to appear automatically in LE8, without the huge and error-prone task of typing them all in?
I just want to be able to select the JV-1010 as the MIDI instrument for a track, and go through the list of patch names and choose. Am I missing a basic principle here?

Charles: I had the very same problem using a Yamaha Motif ES8 keyboard. I wanted to find a way to have logic recognize the patch names and bank numbers. I didn't find my answers here. I was very lucky to go on to the Yamaha Motif users group and find someone there that had done all of the leg work as far a typing out the patch names and bank changes and then saved it in logic as a .logic file. So I downloaded that project file from the yamaha users group and opened up that project in logic express but before I recorded anything on it, I saved the blank project with the yamaha midi info as a template. Now, every time I open up a new project, I have the option to open up that template and it has all of my patches and bank numbers pre-loaded.
If I were you, I would look around and try to find a Roland JV-1010 users group and see if you have the same good fortune.
Good Luck

How do I use logic as a mulit timbre sound module???

Whats up people,
Im trying to trigger all the sounds in logic via a hardware controller (mpc) separating everything on separate channels. I got it to read on just one channel at a time, but multi?? Forget about it.... I read other posts in regards to this same question and have run thru the suggestion switched midi setting to auto demix etc...
Doesn't respond if i go to another channel on my hardware and select the new instrument to the same channel in logic it still only allows playback from one channel at a time?? Huh is my theory even possible folks!?? I would think it is.
Im trying to comprehend the instructions in the manual for the environment setup, to see if i need to make any changes their. I thrown in a channel splitter, a seq input, a transformer but i have no idea if im doing it right?? I must be slow cos to me that enviroment chapter reads like riddles! (LAYMAN TERMS SOMEONE PLEASE!!)
If anyone can assist in this id appreciate it. Any and all suggestions are welcome.
Good lookin out
peace
D.

Greetings people,
The latest.............okay where do i start. Well i actually followed everybody suggestion on this thread and actually as a result now understand the enviroment a little better. But i have still been unable to get my multi playback channels. I managed to get access to all 16 channels etc.
Right now i have my physical input going thru the monitor to the channel splitter, each channel is cabled to my audio instrument(which im assuming is the multi inst i created as to represent the mpc) channels are set to all and then i have the out of my audio instrument going to the seq input. I hear my sounds and have actually triggered the internal sounds from the mpc pads no problem (did that b4 i posted)
but now say i select midi channel 1 on my mpc, which in turn is instrument 1, double click it to get the audio window select ultrabeat, go back to the mpc and program some drums using ultrabeats sounds. Now remember all im doing is recording midi signals into my mpc which is triggering logics sounds right. okay so now, im saying i want to go to the next channel/audio instrument/ and now use sculpture and put a nice fat bass on it. so i select the patch i want hit play on my mpc hoping that it plays back the drums, but NO! now i have selected a new track it pulls over the programming i did for ultrabeat into the sculpture patch.....follow me??
I tested logic to just record one at a time in the arrange, and it does but it records real erratic. btw my mpc is strung up thru my midisport usb which i did select in the enviroment window..check!
I tried Mac's method of dragging the audio instrument into the arrange and selecting the track with a corresponding sub channel etc but got allot of midi feedback!!??? I know that going to settings - record-auto demix etc is supposed to do the trick, well it aint for me?? Please what am i doing wrong??
Ultimately i want to be able to program my mpc using logics sounds via the midi channels simultaneously, and then dump it all down into logic once i am happy with the outcome. Am i asking too much for logic to be a sound source and recorder at the same time??
I dont mean to sound naive or ignorant but i have just started using software for the first time. i use to go the hardware route using digital recorders allday but it was a simpler routing method since my sound sources were seperate(keyboards, sound modules etc). obviously now im tryint to intergrate my old style with the new, but im getting very fustrated and creativley lathalgic from this setback. Many have suggested tossing the mpc and using logic for drums, but sorry i just cant do it i love that boom bap to much.
Anway sorry for the rambling its late and ive just spent the last 5 hours beating my head upside the g5. If anyone out their hasd a similar setup to me whether successful or not, get at me lets trade off techniques and ideas.
Thanks again for taking the time to read the thread and offering your help, please keep it coming.
peace
D.

Patch Names once and for all

Not sure how where to post this suggestion to Apple, but wouldn't it make more sense to import patch names for Devices, more "up stream" into the Audio Midi Setup, rather than LogicPro9?
This would then make patch names available for any software "trained" to read them from the "Audio Midi Setup." Finale, Band-in-a-Box, etc. could all be trained to do that.
This is the way Opcode did it back in Studio Vision days with OMS.
Where can I post this suggestion to Apple?

It probably would make sense, but on the list of development priorities for OSX, I expect it would lie pretty low, as the percentage of MIDI-hardware owning Mac owners will be minutely small.
I think Apple's policy in the main is that most people are using in-the-box instruments - they will obviously continue to support external MIDI instruments, they are not going to remove that facility in Logic, for instance, but the amount of active development in that direction is pretty small.
One of the fundamental reasons for Logic's environment, for example, is to interface, manage, and let you control and route external MIDI hardware, back in the days when Logic was only a MIDI sequencer.
Over fifteen years of development, that side of Logic has hardly been added to at all, whereas the audio playback, processing and software instrument side has undergone massive development.
By all means add the feedback, but I wouldn't be massively optimistic about it...

How to reload sound modules?

I'm using alsa + pulse sound system. I also have Openbox as a stand-alone WM and lightDM, but the same thing occurs on my debian testing + gnome. I've been trying to solve this issue for several days but with no success.
Below is the output from alsa-info.sh script
http://www.alsa-project.org/db/?f=9f32f … f7cdddcc40
Installed packages:
morfik:~$ pacman -Qs alsa
local/alsa-lib 1.0.27-1
An alternative implementation of Linux sound support
local/alsa-plugins 1.0.27-1
Extra alsa plugins
local/alsa-utils 1.0.27-4
An alternative implementation of Linux sound support
local/pulseaudio-alsa 2-2
ALSA Configuration for PulseAudio
morfik:~$ pacman -Qs pulse
local/libao 1.1.0-3
Cross-platform audio output library and plugins
local/libcanberra-pulse 0.30-3
PulseAudio plugin for libcanberra
local/libpulse 3.0-3
A featureful, general-purpose sound server (client library)
local/paprefs 0.9.10-2
A simple GTK-based configuration dialog for PulseAudio
local/pavucontrol 2.0-1
A GTK volume control tool for PulseAudio
local/pulseaudio 3.0-3
A featureful, general-purpose sound server
local/pulseaudio-alsa 2-2
ALSA Configuration for PulseAudio
Everything works fine until hibernation. After my system goes up, one speeker (of 4) is missing, I mean that 3 others play sound well, but the rear-left is silent. I don't know what is wrong, but on debian I can deal with it by reloading sound modules:
$ pulseaudio -k
# alsa force-reload
$ pulseaudio -D
But unfortunately there is no such a thing like "alsa" in Arch. When I type alsa force-reload on my debian, I get this:
root:/# alsa force-reload
Unloading ALSA sound driver modules: snd-ca0106 snd-seq-midi snd-seq-midi-event snd-rawmidi snd-ac97-codec snd-pcm snd-page-alloc snd-seq snd-seq-device snd-timer.
Loading ALSA sound driver modules: snd-ca0106 snd-seq-midi snd-seq-midi-event snd-rawmidi snd-ac97-codec snd-pcm snd-page-alloc snd-seq snd-seq-device snd-timer.
I tried to change a little pulse settings in /etc/pusle/daemon.conf but this does nothing. Now the file looks like this:
daemonize = yes
allow-exit = yes
use-pid-file = yes
exit-idle-time=0
resample-method=speex-float-0
default-sample-rate = 44100
alternate-sample-rate = 48000
default-sample-channels = 4
default-channel-map = front-left,front-right,rear-left,rear-right
I can't use hibernation because after my system comes to life, I have to reboot it in order to make sound work properly.
I don't know what info I should provide, so if you want to know something more about configuration of my pc, feel free and ask, I'll post the info as soon as possible.

Raynman -- thanks for the hint. I looked for the alsa script on debian, and it exists, so I moved it to arch.
This is the script:
#!/bin/sh
# alsa-base control script
# Description: Used to load and unload ALSA modules and
# restore and store mixer levels. There is no
# longer any need to run this script on bootup
# or shutdown. It is now moved to /usr/sbin.
set -e
# Exit if alsa-base package is not installed
[ -f /etc/modprobe.d/alsa-base.conf ] || exit 0
MYNAME=/usr/sbin/alsa
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
# Default values of variables in /etc/default/alsa
force_unload_modules_before_suspend=""
[ -f /etc/default/alsa ] && . /etc/default/alsa
# $* MESSAGE
warn() { echo "${MYNAME}: Warning: $* " >&2 ; }
# Attempt to create /var/run/alsa if it is absent.
# Return true if /var/run/alsa exists after this attempt,
# otherwise false.
check_run_dir()
[ -d /var/run/alsa ] && return 0
# We have no business creating /var/run if it doesn't exist
if ! [ -d /var/run ] ; then
warn "Could not create /var/run/alsa/ because /var/run/ is not present."
return 1
fi
if ! mkdir --mode=755 /var/run/alsa ; then
warn "Failed to create /var/run/alsa/."
return 1
fi
[ -d /var/run/alsa ] && return 0
return 1
echo_procs_using_sound()
for i in /proc/[0-9]*/fd/* ; do
var="$(readlink $i)"
if test x"$var" != x"${var#/dev/snd/pcm}" ; then
IFS=/; set -- $i; unset IFS; echo $3
fi
done
# $* [PID]...
echo_with_command_names()
[ "$1" ] || return 0
echo $( \
ps --no-headers -o "%p %c" "$@" \
| sed -e 's/$[0-9][0-9]*$ $.*$/\1(\2)/' \
kill_procs_using_sound()
procs_using_sound="$(echo_procs_using_sound)"
if [ "$procs_using_sound" ] ; then
echo -n "Terminating processes:"
for attempt in 1 2 3 4 ; do
echo -n " ${procs_using_sound}"
kill $procs_using_sound || :
sleep 1
procs_using_sound="$(echo_procs_using_sound)"
[ "$procs_using_sound" ] || break
done
# Either no more procs using sound or attempts ran out
if [ "$procs_using_sound" ] ; then
echo -n " (with SIGKILL:) ${procs_using_sound}"
kill -9 $procs_using_sound || :
sleep 1
fi
procs_using_sound="$(echo_procs_using_sound)"
if [ "$procs_using_sound" ] ; then
echo " (failed: processes still using sound devices: $(echo_with_command_names $procs_using_sound))."
return 1
fi
echo "."
fi
return 0
# $* MODULE-NAME [MODULE-NAME]... | "all"
unload_modules()
procs_using_sound="$(echo_procs_using_sound)"
if [ "$procs_using_sound" ] ; then
warn "Processes using sound devices: $(echo_with_command_names $procs_using_sound)."
fi
if check_run_dir ; then
:> /var/run/alsa/modules-removed
else
warn "Not keeping list of removed modules because /var/run/alsa is absent.
It will not be possible automatically to reload these modules."
fi
echo -n "Unloading ALSA sound driver modules:"
[ -d /proc/asound ] || { echo " (none loaded)." ; return 0 ; }
echo_snd_modules_loaded()
lsmod \
| sed -n -e 's/^$snd[-_][^[:space:]]*$[[:space:]].*/\1/p' \
| sed -e 's/_/-/g'
for FSMBS in $* ; do
MODULES_TO_REMOVE=""
SND_MODULES_LOADED="$(echo_snd_modules_loaded)"
case "$FSMBS" in
all)
MODULES_TO_REMOVE="$SND_MODULES_LOADED"
snd_*|snd-*)
FSMBS="$(echo "$FSMBS" | sed -e 's/_/-/g')"
for M in $SND_MODULES_LOADED ; do
if [ "$FSMBS" = "$M" ] ; then
MODULES_TO_REMOVE="$FSMBS"
break
fi
done
esac
[ "$MODULES_TO_REMOVE" ] || continue
if [ -d /var/run/alsa ] ; then
echo "$MODULES_TO_REMOVE" >> /var/run/alsa/modules-removed
fi
for M in $MODULES_TO_REMOVE ; do
echo -n " ${M}"
modprobe -r "$M" >/dev/null 2>&1 || :
done
done
if [ -f /var/run/alsa/modules-removed ] ; then
MODULES_STILL_LOADED="$(echo_snd_modules_loaded | grep -F -f /var/run/alsa/modules-removed)"
MODULES_STILL_LOADED="$(echo $MODULES_STILL_LOADED)"
else
MODULES_STILL_LOADED=""
fi
if [ "$MODULES_STILL_LOADED" ] ; then
echo " (failed: modules still loaded: ${MODULES_STILL_LOADED})."
return 1
else
echo "."
return 0
fi
# $* MODULE-NAME [MODULE-NAME]... | "all"
force_unload_modules()
kill_procs_using_sound || :
unload_modules "$@" || return 1
return 0
load_unloaded_modules()
LUM_RETURNSTATUS=0
MODULES_TO_LOAD=""
[ -d /var/run/alsa ] || warn "Directory /var/run/alsa is absent."
echo -n "Loading ALSA sound driver modules:"
[ -f /var/run/alsa/modules-removed ] && MODULES_TO_LOAD="$(echo $(cat /var/run/alsa/modules-removed))"
[ "$MODULES_TO_LOAD" ] || { echo " (none to reload)." ; return $LUM_RETURNSTATUS ; }
echo -n " $MODULES_TO_LOAD"
for MDL in $MODULES_TO_LOAD ; do
modprobe $MDL || LUM_RETURNSTATUS=1
done
case "$LUM_RETURNSTATUS" in
0) echo "." ;;
*) echo " (failed)." ;;
esac
return $LUM_RETURNSTATUS
case "$1" in
unload)
unload_modules all || exit $?
reload)
EXITSTATUS=0
unload_modules all || EXITSTATUS=1
load_unloaded_modules || EXITSTATUS=1
exit $EXITSTATUS
force-unload)
force_unload_modules all || exit $?
force-reload)
EXITSTATUS=0
force_unload_modules all || EXITSTATUS=1
load_unloaded_modules || EXITSTATUS=1
exit $EXITSTATUS
suspend)
case "$force_unload_modules_before_suspend" in
""|false) : ;;
all|true) force_unload_modules all || exit $? ;;
*) force_unload_modules $force_unload_modules_before_suspend || exit $? ;;
esac
resume)
case "$force_unload_modules_before_suspend" in
""|false) : ;;
*) load_unloaded_modules || exit $? ;;
esac
echo "Usage: $MYNAME {unload|reload|force-unload|force-reload|suspend|resume}" >&2
exit 3
esac
It requires two other files in /etc/modprobe.d/ . I also moved them from debian:
alsa-base-blacklist.conf
# Uncomment these entries in order to blacklist unwanted modem drivers
# blacklist snd-atiixp-modem
# blacklist snd-intel8x0m
# blacklist snd-via82xx-modem
# Comment this entry in order to load snd-pcsp driver
blacklist snd-pcsp
alsa-base.conf
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; : ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-ca0106 index=0
options snd-hda-intel index=1
After hibernation, the script provides sound as expected. I also notticed that I can reload only snd-ca0106 and the sound comes back.
Now I have to make a .service file that could make my sound work. But I need more info how to do so.

Module Function Name Resolution - Issues with DefaultCommandPrefix

Just getting started on module development, running PS4, and I've run into an... inconsistency... that I'm trying to understand. I've got two test functions, Get-Something and Set-Something in a script module. In my manifest file I specify a DefaultCommandPrefix
of 'Test'.
My issue is the function name resolution doesn't result in an executable result if you leave PowerShell up to it's own process.
To begin with I closed all sessions and deleted all files in the CommandAnalysis directory. After starting a session I waited for the CommandAnalysis cache to populate. Then I ran a series of test commands to illustrate how, most of the time, the function
name PowerShell registers with tab completion can't be executed because it lacks the 'Test' prefix. Even worse, much of the time tab completion won't recognize the correct (i.e., with prefix) name of the function and honor tab completion for it.
Having just learned of the CommandAnalysis cache I assumed I would see it change as PowerShell 'learned' more about the module because the name resolves differently over time. I've included three files at the end of this post, the module code (ModuleTest.psm1),
the manifest (ModuleTest.psd1) and the capture of output to the PowerShell session (ModuleTest.txt). I've tried to include the times I used <tab> and <ret> for tab completion and execution as well as (comments in parenthesis for things I did like
starting a new session and checking the CommandAnalysis cache for changes).
An example is, when first starting a session typing 'get-som<tab>' will resolve to 'Get-Something' (prefix 'Test' missing) and typing 'get-test<tab>' won't resolve to 'Get-TestSomething'. Try to execute the 'Get-Something' from tab completion
and you'll get the 'name not recognized, blah, blah'.
Now if you type 'get-som<tab>' PowerShell will resolve to 'ModuleTest\Get-Something' - looks promising... but no. Try to execute the 'ModuleTest\Get-Something' from tab completion and you'll still get the 'name not recognized, blah, blah'.
Even though the same key strokes resolved differently there were no changes made to the CommandAnalysis cache so I'm lost on why it produces two different (though equally useless) results.
Manually importing the module and sometimes running Get-Command -Module ModuleTest will make tab completion of the function names behave correctly. Is this a known issue with using DefaultCommandPrefix in script modules or is there something I need to include
in the manifest to enforce strict name recognition (including the prefix)?
<ModuleTest.psm1>
function Get-Something
Write-Host "Get-Something Executed"
function Set-Something
Write-Host "Set-Something Executed"
<ModuleTest.psd1>
# Script module or binary module file associated with this manifest
ModuleToProcess = 'ModuleTest.psm1'
# Version number of this module.
ModuleVersion = '1.0.0.0'
# ID used to uniquely identify this module
GUID = '241877ff-64be-40c8-a603-8d5acf7a48d8'
# Author of this module
Author = 'wb3'
# Company or vendor of this module
CompanyName = ''
# Copyright statement for this module
Copyright = '(c) 2015. All rights reserved.'
# Description of the functionality provided by this module
Description = 'Module description'
# Minimum version of the Windows PowerShell engine required by this module
PowerShellVersion = '2.0'
# Name of the Windows PowerShell host required by this module
PowerShellHostName = ''
# Minimum version of the Windows PowerShell host required by this module
PowerShellHostVersion = ''
# Minimum version of the .NET Framework required by this module
DotNetFrameworkVersion = '2.0'
# Minimum version of the common language runtime (CLR) required by this module
CLRVersion = '2.0.50727'
# Processor architecture (None, X86, Amd64, IA64) required by this module
ProcessorArchitecture = 'None'
# Modules that must be imported into the global environment prior to importing
# this module
RequiredModules = @()
# Assemblies that must be loaded prior to importing this module
RequiredAssemblies = @()
# Script files (.ps1) that are run in the caller's environment prior to
# importing this module
ScriptsToProcess = @()
# Type files (.ps1xml) to be loaded when importing this module
TypesToProcess = @()
# Format files (.ps1xml) to be loaded when importing this module
FormatsToProcess = @()
# Modules to import as nested modules of the module specified in
# ModuleToProcess
NestedModules = @()
# Default command prefix
DefaultCommandPrefix = 'Test'
# Functions to export from this module
FunctionsToExport = '*'
# Cmdlets to export from this module
CmdletsToExport = '*'
# Variables to export from this module
VariablesToExport = '*'
# Aliases to export from this module
AliasesToExport = '*'
# List of all modules packaged with this module
ModuleList = @()
# List of all files packaged with this module
FileList = @()
# Private data to pass to the module specified in ModuleToProcess
PrivateData = ''
<ModuleTest.output>
PS C:\Scripts\PowerShell> Get-ChildItem -Path 'C:\Program Files\WindowsPowerShell\Modules' -Recurse<ret>
    Directory: C:\Program Files\WindowsPowerShell\Modules
Mode                LastWriteTime     Length Name
d----          3/5/2015   9:06 AM            ModuleTest
    Directory: C:\Program Files\WindowsPowerShell\Modules\ModuleTest
Mode                LastWriteTime     Length Name
-a---          3/5/2015   8:50 AM       2907 ModuleTest.psd1
-a---          3/5/2015   9:01 AM        140 ModuleTest.psm1
PS C:\Scripts\PowerShell> Get-Module -ListAvailable<ret>
    Directory: C:\Program Files\WindowsPowerShell\Modules
ModuleType Version    Name                                ExportedCommands
Script     1.0.0.0    ModuleTest                          {Get-Something, Set-Something}
PS C:\Scripts\PowerShell> get-som<tab>
PS C:\Scripts\PowerShell> Get-Something<ret>
Get-Something : The term 'Get-Something' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Get-Something
+ ~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-Something:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
(No change in CommandAnalysis cache)
PS C:\Scripts\PowerShell> get-som<tab>
PS C:\Scripts\PowerShell> ModuleTest\Get-Something<ret>
ModuleTest\Get-Something : The term 'ModuleTest\Get-Something' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ ModuleTest\Get-Something
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (ModuleTest\Get-Something:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
(No change in CommandAnalysis cache)
PS C:\Scripts\PowerShell> get-tes<tab>
PS C:\Scripts\PowerShell> Get-TestSomething<ret>
Get-Something Executed
(New Session)
(No change in CommandAnalysis cache)
PS C:\Scripts\PowerShell> get-tes<tab><ret>
get-tes : The term 'get-tes' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ get-tes
+ ~~~~~~~
    + CategoryInfo          : ObjectNotFound: (get-tes:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
PS C:\Scripts\PowerShell> Import-Module ModuleTest<ret>
(No change in CommandAnalysis cache)
PS C:\Scripts\PowerShell> get-tes<tab><ret>
PS C:\Scripts\PowerShell> Get-TestSomething
Get-Something Executed
(New Session)
(No change in CommandAnalysis cache)
PS C:\Scripts\PowerShell> get-tes<tab><ret>
get-tes : The term 'get-tes' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ get-tes
+ ~~~~~~~
    + CategoryInfo          : ObjectNotFound: (get-tes:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
PS C:\Scripts\PowerShell> Get-Command -Module ModuleTest<ret>
CommandType     Name
ModuleName
Function        Get-TestSomething
ModuleTest
Function        Set-TestSomething
ModuleTest
(No change in CommandAnalysis cache)
PS C:\Scripts\PowerShell> get-tes<tab>
PS C:\Scripts\PowerShell> Get-TestSomething<ret>
Get-Something Executed
PS C:\Scripts\PowerShell> moduletest\get<tab><ret>
PS C:\Scripts\PowerShell> Get-TestSomething<ret>
Get-Something Executed
William Busby, PMP

Hi William,
yes, that's something you'll either have to do the hard way or live with admin confusion.
If you're using Sapien's PowerShell Studio as an Editor (hint: Usually a great idea), you can very easily rename a function, even in a multi-file module project, by rightcklicking on the function-name and selecting "rename".
Alternatively you can do a bulk rename with Powershell:
Get all functions in your module (Load it and check exportedcommands)
loop over each function-name
calculate new name
search your entire project for all references and replace them.
Let me see ...
function Rename-ModulePrefix
[CmdletBinding()]
Param (
[Parameter(Position = 0, Mandatory = $true)]
[string]
$ModuleName,
[Parameter(Position = 1, Mandatory = $true)]
[string]
$OldPrefix,
[Parameter(Position = 2, Mandatory = $true)]
[string]
$NewPrefix,
[Parameter(Position = 3)]
[string]
$Path
# Catch all typos
Import-Module $ModuleName -ErrorAction 'Stop'
# Get root path if not manually passed
if (-not $PSBoundParameters["Path"])
$Path = (Get-Module $ModuleName).Path
# Get module files
$Files = Get-ChildItem -Path $path -Recurse -Include "*.ps1", "*.psm1", "*.psd1"
# Iterate over each file
foreach ($file in $Files)
# Null variable in case you get an empty file somewhere and run this from Win 7
$data = $null
# Get Content of file
$data = Get-Content $file
# Replace strings
foreach ($c in (Get-Module $ModuleName).ExportedCommands)
$newName = $c.Name -replace $OldPrefix, $NewPrefix
$data = $data | ForEach-Object { $_ -replace $c.Name, $newName }
# Write back to file
$data | Set-Content $file
While I didn't proof it, in theory this should do it (Make a backup before running it :) ).
Cheers,
Fred
There's no place like 127.0.0.1

Using External Sound Modules (Synths) in Logic Express?

Hi all,
I don't have Logic Express yet. I want to know if what I want to do is possible before I purchase. It may sound trivial, but I'm very new to the whole DAW environment. Apparently Garageband can't support my external sound modules so I'm hoping Logic Express will.
To help, please see my hardware midi setup diagram here:
http://www.greddin.com/images/My-Midi-Setup.jpg
Will I be able to add tracks that will play the external sound devices like the Wavestation and JD-990? Can you change the sounds through Logic? To what extent can I use my external sound modules?
Thanks all,
-Greg

Hi,
1st: Yes, Logic Express has "external MIDI" tracks that function similar to the "software instrument" tracks but trigger external instruments.
2nd: But: To setup these tracks, especially with more than one device, needs some experience with MIDI, the channels, patch selection via MIDI etc. The real downside is you have to find out which commands you need to "tell" your devices to change sounds and these things. Since there is no standard command for this, you'll have to look it up in your devices manual and use the MSB/LSB Values- which you have to enter manually. However, once you found it out, you can save these things as templates and use them in the future. So yes, it is very possible, but expect some learning curve.
3rd: You can use your sound modules to their full extent. Logic features a mighty MIDI environment setup once you learned how to use it.
Fox

Importing sound into Premier Pro CS3

I have a Sony HDR-XR100 HD video camera. It saves files with an .m2ts extension. This extension is not supported by CS3. Using Sony's PMB (Picture Motion Browser), I convert the .m2ts files to .mpeg2. When I import these files into Premier, they appear, but have no audio. How do I import the audio? Thanks.
David

I put it in the main Premier folder, presumably like you did, and it worked. I'm not real familiar with Macs, but the folder I put it in was "C:\Program Files\Adobe\Adobe Premiere Pro CS3". There are several other files there with similar names. If that doesn't work, I'm lost, since obviously I had to come here for help myself :).
David
Date: Fri, 23 Jul 2010 19:40:24 -0600
From: [email protected]
To: [email protected]
Subject: Importing sound into Premier Pro CS3
Hey, I'm using CS for Mac and I'm having the same issue , importing .mpg into PPro and get no audio.
I found the ad2ac3dec.dll file online but I'm not sure what folder to place it in. I've found the folder named Adobe Premire Pro CS3 and just pasted it into that but it didn't work.
My camera only records in .mpg and I really don't want to spend money on a converter after spending a bucketload for CS3...
Any help would be much appreciated!
>

External sound module

Is it possible to connect an external sound module to iMac/Garageband so as not to use the quicktime software sounds?
iMac Mac OS X (10.4.5)

I don't understand that question! GB has midi input, but that doesn't help if you want to record the audio output of the sound module.
How would you do that? I don't know if MidiO is functional in the record mode - then you could just record the sound from the module while it is triggered by the midi out. If not, I'd record it in the background to an audio editor while playing back the GB file and later import that audio.
But as I said, that's theoretical reasoning, since I haven't used MidiO. MyMac should know more.

How to Import Knowledge Modules

Hi,
I am patching the ODI to 10.1.5.3 and successfully updated the install folder and imported technologies as described in the patchset. At the end I find a last step to import Knowledge Modules, but I can't see how this step is performed.
Could you explain me how to do this?
Thanks
Fabio D'Alfonso

Hi,
In any of KM types, right-click and choose "Import KM" and, after that, in the first textbox, go the ODI install directory and drill drow until "impexp" directory (Example: C:\OraHome_1\oracledi\impexp).
Don't "open" the diretory, just choose it and click OK. The KM list should appears to you.
Works?
Cezar Santos
http://odiexperts.com

IMPORTING SOUND MODULE PATCH NAMES

Similar Messages

Maybe you are looking for