I am trying to rename my audio device name. but it doesn't do anything when I rename it. it just simply close the setting. My setting for RDP is Local Resource-->play on this computer.
Its not possible to rename the audio device name on the VM as you are using remote audio driver from Microsoft to output the sound to your local machine . The driver name is bydefault remote audio.
Related
I have to push firmware files to multiple usb devices (2 files per device) via ymodem file transfer. However just before uploading the files the device needs to be rebooted to get access to the file transfer menu. Once it reboots the port that it gets assigned to is no longer the same - due to re-enumeration. As a result trying to open the port, that it was originally assigned to transfer the file gives an error. Is there a way around this or perhaps have a dedicated port for each device???
Thanks,
Archie
My project is to stream audio online with my PC as the server.
I have a HP Proliant ML110 G7 server PC, which does not have any integrated sound device in motherboard, nor any kind of sound device.
I am currently using ubuntu 16.04 in my PC, and I cannot configure IceCast and Ices2/Darkice properly, but I could do it following the same instructions in another laptop with same os same version, which has an integrated sound device.
Is an integrated sound device needed to make an audio streaming server?
Thank you.
Icecast itself just passes data on through. It requires no sound device at all.
Your source client, such as IceS, can be used to read audio from a sound device or just to read audio from files. If you have no sound device, you'll need to use some other audio source of course.
Is it possible to use the BB as Mass Storage Device?
I want it to be connected to an audio player that can read files from USB connectivity (such as USB flash drive) and act as data storage device containing one specific folder (and its sub-folders) from the file system (if possible, on a flash drive connected to the board.).
As the device specs says, it has connectivity of:
USB client for power & communications
USB host
Operating system will probably be Ubuntu but can be changed.
What drivers or configurations needs to be done in order to achieve this?
The latest images have already the mass storage usb gadget active, so a mass storage peripheral should be recognized by your system upon connection.
A quick google search reveals this discussion about a user trying to disable the USB MS gadget:
From the discussion, the files where the magic happens are:
Debian: /opt/scripts/boot/am335x_evm.sh
Ubuntu: /opt/scripts/boot/am335*
Armstrong: /usr/bin/g-ether-load.sh
In my Debian image the line you want to modify is:
modprobe g_multi file=${gadget_partition} cdrom=0 stall=0 removable=1 nofua=1 iSerialNumber=${SERIAL_NUMBER} iManufacturer=Circuitco iProduct=BeagleBone${BLACK} host_addr=${cpsw_1_mac}
and the corresponding $gadget_partition variable that is set just before that in order to customize the folder you want to expose.
Note that the g_multi gadget in its standard configuration presents 3 different devices: an ethernet interface, a mass storage peripheral and a serial interface. If you want to customize the parameters you can refer to the g_multi documentation (kernel.org)
enter image description here cant access the directories in media file system on my mobile via my Ubuntu 14.04
can anyone help me?
Restart the ubuntu system and your phone. Try it again.
Which connection mode your phone is in? MTP or USB mass storage?
Check your cable. And are you able to connect and use other USB devices on this system? Are you able to use this phone to do transfers on other computer?
In iOS , I can get camera buffer image from the SDK, but in the Linux world, if I plug a camera to the machine, how can I get the camera buffer in Linux system? Thanks.
Each device in Linux word is linked to a file into the /dev directory. Precisely, the video devices usually are located into the /dev/v4l folder. In the folder you should find symbolic links that point to the /dev/video0 (the real file associated with the physical device file).
If you need to access to the buffer of the cam, you just need to open the file and start reading.