Problem with midi input in Mainstage

Hi all,
I have a keyboard connected to my mac via USB midi interface.
When I'm trying to play midi instruments in Garage Band - it works very well, no significant latency and no other problems.
But in Mainstage the situation with the midi input is different. When I press a key on my keyboard, it plays the sound, then stops responding to other midi commands for about 2-3 seconds. And then after I press another key, it plays it, and stops responding again.
The "CPU" and "Memory" indicators at the top show a low load.
All in all, it's just impossible to play a midi instrument in Mainstage.
As the midi interface is working correctly in GarageBand and doesn't work well in Mainstage, I suspect that it's a Mainstage's software problem. But I haven't found anything like that on the Internet. Any ideas?
Devices: Macbook Pro 13" (2011), M-Audio MidiSport Uno...
Thanks!

I can input Chinese in Firefox, but there are
problems with the display of characters in input
fields for searches, etc.
Can you provide a specific example of a particular search box (url) and exactly what the "problem" is (TC or SC, characters involved, etc)? I would like to try and duplicate it. Perhaps the encoding in View > Text Encoding needs to be adjusted for that page for some reason (though normally that should affect all browsers).
Since Apple has nothing to do with FireFox, you might want to report the issue to the people responsible for that program (mozilla.org I think), since it may be a bug they can fix.

Similar Messages

Having problem with midi?

I am having problem with midi keyboard (korg pa80) I having hard time to midi to logic every time I have to either restart the logic or restart the keyboard or plug out the USB cable and put back in order to work. Plus when I created a new track doen't work with it. I have to do same as above to make it work? help please how can i refresh the midi connection with going throw steps above?

Is it the computer dropping the MIDI interface, or the computer connectin is fine adn Logic is not seeing it?
Run the Audio/MIDI Setup utility and make sure your MIDI device is present. If not, try another USB port, or don't use a hub.
Assuming the connection is solid, in Logic, option-click on File -> New and try it - if it works in that song, but not your own songs, it's a song specific issue, so check your MIDI input handling in the environment.

Problem with the input file format to be stored in database

Hi,
I am facing some problem with the input format. I am using the table name as data.employee. But i could not able to process the message forward. I am getting this error,
com.ibm.db2.jcc.c.SqlException: java.sql.Connection.close() requested while a transaction is in progress on the connection.The transaction remains active, and the connection cannot be closed.
Can you please help me prposing a solution for this format.
Thanks,
SOorya

I think you are missing out the COMMIT operation.
At the DB2 end before closing the connection if you do a 'COMMIT' then this may remove your error.
i.e. after you close the Resultset>close the statement object> perform 'COMMIT' operation--> then close the connection.
Also refer :-
http://www.dbforums.com/archive/index.php/t-976407.html
http://www.dbforums.com/showthread.php?t=1628183
I hope this will help you.
Thanks,
Vijaya

I have to step-input an existing score and tried it with the step-input-window in combination with midi-input from an usb-keyboard.

I have to step-input an existing score and tried it with the step-input-window in combination with midi-input from an usb-keyboard.

Tsk tsk, Nigel, don't you see: this is a story - with a cliffhanger... he said he tried... but he never clarifies if he succeeded or not... but still, he has to do it. It's stronger than him, bigger than him, there's no escaping the step-input and midi-input via usb-keyboard scoring... it's fate I tell you! Fate!

Problems with MIDI, Sound, Etc.

Hi all,
Well, I have grown up on Macs and my dad has brought home everything from the Plus to the IIci to the Classic Colour when I was a kid 20 years go. Circumstances have forced me to move to PC, and I even had one in my home studio, but I recently had the chance to upgrade and was absolutely thrilled at the prospect of getting back into the Mac world after more than 10 years of absence. So, I got myself a Mac Mini 2.53 GHz (I only upgraded the hard drive to a 500 GB 7200-RPM model, as is common in the audio world), with a Focusrite Saffire 24 Pro DSP Firewire audio interface.
Well, I am saddened to say that so far, I have been BITTERLY disappointed. Problems :
1. This Mac is NOISY!!! I don't mean physical computer/fan/etc. noise. I mean static noise going through the interface. The interface is dead-silent during bootup until, at some point in the sequence (when looking at the Apple logo during bootup), the same static hiss and hum comes back that's been plaguing me for a few days. This noise seems to be matching my activities - it changes when I scroll, when I open a program, etc., for example. So, this is DEFINITELY sub-par;
2. Snow Leopard simply refuses to acknowledge my Roland XV-5050's existence on USB. Ableton Live can find it in its list of "destinations" for MIDI data, but Audio Midi Setup simply refuses to even see it, precluding me from using Roland's very handy Editor. Again, unacceptable, given that I've never had this problem with PCs (although, Roland expressly does not support Vista with the XV-5050 USB drivers);
3. There's something weird about the Mac (could also be Live, I suppose, but I never had this problem on PC) where my music applications do not see the Korg Legacy Cell VSTs that are installed, even though they are in the same folder as, say, Sylenth, which Live DOES see. (And they all end in .vst extensions.) What gives?
I think that's it so far. I've got a very important gig coming up around Christmas time that I have to start getting ready for. I had anticipated virtually zero problems with the Mac, which is why I chose to upgrade, but the reality is definitely otherwise. Please, PLEASE don't make me buy the Dell Studio or something!!
Thanks in advance for all the help!
JS

Korg Legacy and the XV are not critical to my workflow, just items I had invested on I would like to keep. I did not research compatibility with Snow Leopard vwery thoroughly for those two, but I certainly did with the interface, which IS critical. Focusrite has released brand-new drivers that are supposed to be compatible with Snow Leopard, as they loudly trumpet on their web site.
And by and large, they do work - there's just that incessant noise. And THAT's an issue, and somehow I doubt it has to do with the interface as, like I mentioned, the noise only appears during the bootup sequence when, I assume, the Firewire drivers are loaded.
Inputs?

Problem with midi on my Macbook pro

Ok, so i've been having this problem for a while now...i came on the forums before and asked about it, and people said to get more RAM...so i've done that...
Before I thought it was a CPU issue, but now i'm realizing it has something to do with MIDI.
I have Pro Tools and Logic on my computer, and whenever I load a MIDI instrument into either program, the CPU usage goes way up...way more than it should. I don't know why this is happening. Right now I only have one piano loaded in Pro Tools and it's taking up so much CPU that the sound cuts in and out. In Logic, the CPU bar goes all the way up.
Does anyone have a solution for this? It's got something to do with the midi...if i bounce the midi track to make it an audio track it works fine. Also, if i restart the computer or close & open the program again it tends to work a little better for a limited amount of time...
I'm running a 2.2 Ghz 2007 Macbook Pro with 4 GB Ram that i recently put in. I have a lot of the MIDI sounds on an external hard drive, but both the external sounds and sounds that are on the computer itself have the same problem.
Thanks,
TJ

?

Samsung hard drive problems with mid 2009 Macbook Pro

Arghh, this is driving me mad.
I'd like to know if anyone has installed a Samsung HM641JI SATA II hard drive into a mid 2009 Macbook Pro (mine is a 2.8Ghz) and, if so, how they managed it. The drive is 640GB. These are the steps I've taken:
1. Swap out the stock drive for the Samsung
2. Boot from a USB drive which contains a mirror of my system
3. When the system identified the new disk, I formatted it with 2 partitions (GUID table, HFS journaled)
4. Reboot
5. System is very slow. Boots from USB but can't use keyboard to login
6. Switch off and try again
7. Remove Samsung drive
8. Reboot from USB (works perfectly)
9. Downgrade firmware to 1.6
10. Replace samsung drive and try again
11. System boots from USB
12. Verify that drive is running at 1.5Ghz
13. Disk utility and system profiler both crash
14. Disk unmounts by itself and other random weirdness
15. Remove Samsung drive
I've read endless reports about the firmware in this model of Macbook Pro and its issues with SATA II but struggling to find anything current and specific. Two questions:
a. Is there anythign I can do to get this drive to play nicely?
b. What drive should I get if the answer to a is no?
As a bit of background.. my system began playing up last week with lots of spinning beach balls resulting in forced switch offs. Booting from a mirror on a USB drive works perfectly so I concluded that the drive was on its way out. A drive test utility confirmed this. I'm now wondering if it really was the drive or the cable or the logic board.
Any advice appreciated.
Cheers
//A

I'm coming around to the idea that this might be a problem with the SATA cable rather than the drive.
I currently have the stock drive (Hitachi) back in the macbook. It mounted for a while and was then ejected when I tried writing data to it. System profiler reports that "There was an error while scanning for Serial-ATA devices."
I was able to mount the same drive in a USB enclosure this afternoon without any problems. Right now, I seem to be having issues with both the Samsung drive and the Hitachi drive - I wasn't suspicious of thr latter because I thought it was failing.
I found one or two accounts of other people having similar problems that were resolved with a new sata cable.
How does a cable fail? Could this be my problem?
Cheers
//A

Problem with direct input program while uploading data into database

TABLES: BGR00,                        " Mappensatz
         BMM00,                        " MM01/MM02 BTCI-Kopfdaten
         BMMH1,                        " MM01/MM02 Hauptdaten
         BMMH2,                        " Länderdaten (Steuern)
         BMMH3,                        " Prognosewerte
         BMMH4,                        " Verbrauchswerte
         BMMH5,                        " Kurztexte
         BMMH6,                        " Mengeneinheiten
         BMMH7,                        " Langtexte
         BMMH8.                        " Referentielle EAN's
       Satztypen
DATA:    MAPPENSATZ LIKE BMM00-STYPE VALUE '0',
         KOPFSATZ    LIKE BMM00-STYPE VALUE '1',
         HAUPTSATZ   LIKE BMM00-STYPE VALUE '2',
         KUN_SATZ    LIKE BMM00-STYPE VALUE 'Z',
         LANDSATZ    LIKE BMM00-STYPE VALUE '3',
         PROGSATZ    LIKE BMM00-STYPE VALUE '4',
         VERBSATZ    LIKE BMM00-STYPE VALUE '5',
         KTEXTSATZ   LIKE BMM00-STYPE VALUE '6',
         MESATZ      LIKE BMM00-STYPE VALUE '7',
         TEXTSATZ    LIKE BMM00-STYPE VALUE '8',
         EANSATZ     LIKE BMM00-STYPE VALUE '9'.
Common Data Bereich fuer die extern aufgerufenen Routinen
       Initialstrukturen
DATA: BEGIN OF COMMON PART RMMMBIMY.
DATA:    BEGIN OF I_BMM00.
           INCLUDE STRUCTURE BMM00.    " Kopfdaten
DATA:    END OF I_BMM00.
DATA:    BEGIN OF I_BMMH1.
           INCLUDE STRUCTURE BMMH1.    " Haupdaten
DATA:    END OF I_BMMH1.
DATA:    BEGIN OF I_BMMH2.
           INCLUDE STRUCTURE BMMH2.    " Länderdaten
DATA:    END OF I_BMMH2.
DATA:    BEGIN OF I_BMMH3.
           INCLUDE STRUCTURE BMMH3.    " Prognosewerte
DATA:    END OF I_BMMH3.
DATA:    BEGIN OF I_BMMH4.
           INCLUDE STRUCTURE BMMH4.    " Verbrauchswerte
DATA:    END OF I_BMMH4.
DATA:    BEGIN OF I_BMMH5.
           INCLUDE STRUCTURE BMMH5.    " Kurztexte
DATA:    END OF I_BMMH5.
DATA:    BEGIN OF I_BMMH6.
           INCLUDE STRUCTURE BMMH6.    " Mengeneinheiten
DATA:    END OF I_BMMH6.
DATA:    BEGIN OF I_BMMH7.
           INCLUDE STRUCTURE BMMH7.    " Textzeilen
DATA:    END OF I_BMMH7.
DATA:    BEGIN OF I_BMMH8.
           INCLUDE STRUCTURE BMMH8.    " Referentielle EAN's
DATA:    END OF I_BMMH8.
DATA: END OF COMMON PART.
DATA: WA LIKE TEDATA-DATA.
       Einzelfelder
DATA:    GROUP_COUNT(6) TYPE C,    " Anzahl Mappen
         TRANS_COUNT(6) TYPE C,    " alte Definition für rmmmbim0
         SATZ_COUNT LIKE MUEB_REST-TRANC, " Trans.zähler neu
         H_IND_COUNT LIKE MUEB_REST-D_IND, " Index welches Feld zurücks.
         SATZ2_COUNT(6) TYPE C.    " Anz. Sätze je Trans. ohne Kopfsatz
DATA:    XEOF(1)          TYPE C, " X=End of File erreicht
         XHAUPTSATZ_EXIST TYPE C, " X=Hauptsatz zum Kopf exi.
         NODATA(1)        TYPE C. " kein BI für dieses Feld
mk/15.08.94:
DATA:    GROUP_OPEN(1) TYPE C.             " X=Mappe schon geöffnet
*eject
       Konstanten
DATA:    C_NODATA(1)    TYPE C VALUE '/'.   " Default für NODATA
DATA:    MATNR_ERW     LIKE MARA-MATNR VALUE '0                 '.
DATA:    MATNR_ERW_INT LIKE MARA-MATNR. "internal sight of '0      '
DATA:    MATNR_LAST    LIKE MARA-MATNR. "Material number
mk/11.08.94 2.1H:
If this flag is initial, the database updates will be done directly
during background maintenance instead of using a separate update
task. (no usage of this flag in dialogue mode!)
DATA: DBUPDATE_VB(1) VALUE ' '.       "note 306628
data: matsync type mat_sync. "wk/99a no update in dialog if called
***INCLUDE ZMUSD070.
TABLES: MARA,                          "Material Master: General Data
        MARC,                          "Material Master: C Segment
        MARD,                          "Material Master: St Loc/Batch
        MBEW,                          "Material Valuation
        MVKE,                          "Material Master: Sales Data
        MLGN,                          "Material Data per Whse Number
        MLAN,                          "Tax Classification: Material
        T001W,                         "Plants/Branches
        TBICU.
DATA: BEGIN OF VALUTAB OCCURS 0.
        INCLUDE STRUCTURE RSPARAMS.
DATA: END OF VALUTAB.
DATA: BEGIN OF VARTECH.
        INCLUDE STRUCTURE VARID.
DATA: END OF VARTECH.
DATA: PARMS LIKE ZXXDCONV.
DATA: REC_COUNT      TYPE I,
      REC_COUNT_BAD TYPE I,
      ZJOBID         LIKE TBIZU-JOBID,
      ZJOBCOUNT      LIKE TBIZU-JOBCOUNT,
      ZMATNR         LIKE MARA-MATNR,
      ZTEXT(80)      TYPE C.
CONSTANTS: LIT_ZERO(18) TYPE C            VALUE '000000000000000000',
           LIT_CHAR      TYPE C            VALUE '_',
           LIT_CREATE    LIKE BMM00-TCODE VALUE 'MM01',
           LIT_CHANGE    LIKE BMM00-TCODE VALUE 'MM02',
           LIT_CHECK(1) TYPE C            VALUE 'X'.
DATA: BEGIN OF INP_DATA OCCURS 0,
         MATNR(18) TYPE C,            " Material code
         UMREN(6)   TYPE C,            " Denominator
         MEINH(3)   TYPE C,            " Alternate UOM
         UMREZ(6)   TYPE C,            " Numerator
       END OF INP_DATA.
*eject
SELECTION-SCREEN BEGIN OF BLOCK INOUT WITH FRAME TITLE TEXT-001.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (13) TEXT-004.
PARAMETERS:     P_PC        RADIOBUTTON GROUP SRC DEFAULT 'X'.
SELECTION-SCREEN COMMENT (6) TEXT-005.
PARAMETERS:     P_UNIX      RADIOBUTTON GROUP SRC.
SELECTION-SCREEN COMMENT (6) TEXT-006.
PARAMETERS:     P_DS_TYP    LIKE     ZXXDCONV-DS_TYP
                               DEFAULT 'ASC'.
SELECTION-SCREEN END OF LINE.
*SELECT-OPTIONS: S_PATH      FOR      PARMS-PATH
                              NO INTERVALS
                              LOWER CASE.
PARAMETERS: P_PATH TYPE RLGRAP-FILENAME.
PARAMETERS:     P_HDRLIN   LIKE     ZXXDCONV-HDR_LINES
                               DEFAULT 0,
                P_JOBNAM   LIKE     TBICU_S-JOBNAME
                               MEMORY ID BM1,
                P_DI_EXE    AS       CHECKBOX
                               DEFAULT LIT_CHECK,
                P_MAPPE     LIKE     BGR00-GROUP
                               DEFAULT 'MRP_UOM_LOAD'
                               NO-DISPLAY.
SELECTION-SCREEN END OF BLOCK INOUT.
*eject
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_PATH.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            PROGRAM_NAME = SYST-REPID
            DYNPRO_NUMBER = SYST-DYNNR
            FIELD_NAME    = 'P_PATH'
       CHANGING
           FILE_NAME     = S_PATH-LOW
            FILE_NAME     = P_PATH
       EXCEPTIONS
            MASK_TOO_LONG = 1
            OTHERS        = 2.
AT SELECTION-SCREEN.
Set up parameter record
PARMS-UNIX      = P_UNIX.
PARMS-PC        = P_PC.
PARMS-DS_TYP    = P_DS_TYP.
PARMS-JOBNAME   = P_JOBNAM.
PARMS-MAPPE     = P_MAPPE.
PARMS-HDR_LINES = P_HDRLIN.
*eject
       Main Processing Routine                                       *
START-OF-SELECTION.
Initialization
PERFORM 0000_HOUSEKEEPING.
Initialize transaction data in I_BM00
PERFORM 0500_INIT_BMM00.
Process input files
SORT S_PATH BY SIGN OPTION LOW.
     MOVE S_PATH-LOW TO PARMS-PATH.
      MOVE P_PATH TO PARMS-PATH.
LOOP AT S_PATH.
   AT NEW LOW.
      CLEAR   INP_DATA.
     REFRESH INP_DATA.
Read source data into internal table
      PERFORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
Processs each record in internal table
      ZTEXT    = TEXT-007.
      ZTEXT+13 = PARMS-DS_NAME.
      PERFORM 4000_PROGRESS_INDICATOR USING ZTEXT.
Initialize transaction data in I_BM00
PERFORM 0500_INIT_BMM00.
      LOOP AT INP_DATA.
Reset tables for each record
        BMM00              = I_BMM00.
        BMMH1              = I_BMMH1.
        BMMH6              = I_BMMH6.
Load structures with data
        MOVE-CORRESPONDING INP_DATA TO BMM00.
        PERFORM 2000_WRITE_OUTPUT USING BMM00.
        MOVE-CORRESPONDING INP_DATA TO BMMH1.
        PERFORM 2000_WRITE_OUTPUT USING BMMH1.
        MOVE-CORRESPONDING INP_DATA TO BMMH6.
        PERFORM 2000_WRITE_OUTPUT USING BMMH6.
        REC_COUNT = REC_COUNT + 1.
      ENDLOOP.
   ENDAT.
ENDLOOP.
IF REC_COUNT GT 0
AND P_DI_EXE EQ LIT_CHECK.
    PERFORM 3000_START_DI_JOB.
ENDIF.
WRITE: / TEXT-008,
           REC_COUNT.
PERFORM 9000_END_OF_JOB.
*eject
Include containing common routines used by direct input programs
INCLUDE ZMUSD071.
*eject
      FORM 0500_INIT_BMM00                                          *
      Initialize I_BMM00 with transaction code and views selected   *
FORM 0500_INIT_BMM00.
***this changes done by samson**
if not inp_data[] is initial.
select single matnr from mara INTO ZMATNR where matnr = inp_data-matnr.
if sy-subrc = 0.
I_BMM00-TCODE = LIT_CHANGE.
Basic data
I_BMM00-XEIK1 = LIT_CHECK.
else.
I_BMM00-TCODE = LIT_CREATE.
Basic data
I_BMM00-XEIK1 = LIT_CHECK.
endif.
endif.
**this changes above done by samson**
Transaction code
I_BMM00-TCODE = LIT_CHANGE.
Basic data
I_BMM00-XEIK1 = LIT_CHECK.
ENDFORM.
INCLUDE ZMUSD069.
*eject
      FORM 0000_HOUSEKEEPING                                        *
      Initialization routines                                       *
FORM 0000_HOUSEKEEPING.
PERFORM 0010_LDS_NAME.
PERFORM 0020_DS_NAME.
PERFORM 0030_OPEN_FILE.
PERFORM 0040_INIT_STRUCTS.
ENDFORM.
*eject
      FORM 0010_LDS_NAME                                            *
      Obtain logical file name from DI job details                  *
FORM 0010_LDS_NAME.
Check valid job name
SELECT SINGLE * FROM TBICU
                  WHERE JOBNAME EQ PARMS-JOBNAME.
IF SY-SUBRC EQ 0.
    CALL FUNCTION 'RS_VARIANT_VALUES_TECH_DATA'
         EXPORTING
              REPORT               = TBICU-REPNAME
              VARIANT              = TBICU-VARIANT
         IMPORTING
              TECHN_DATA           = VARTECH
         TABLES
              VARIANT_VALUES       = VALUTAB
         EXCEPTIONS
              VARIANT_NON_EXISTENT = 1
              VARIANT_OBSOLETE     = 2
              OTHERS               = 3.
    IF SY-SUBRC EQ 0.
      READ TABLE VALUTAB WITH KEY 'LDS_NAME'.
      MOVE VALUTAB-LOW TO PARMS-LDS_NAME.
    ELSE.
      MESSAGE I001 WITH PARMS-JOBNAME.
      MESSAGE A099.
    ENDIF.
ELSE.
    MESSAGE I000 WITH PARMS-JOBNAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
      FORM 0040_INIT_STRUCTS                                        *
      Initialize structures for direct input records                *
FORM 0040_INIT_STRUCTS.
Start of standard SAP initialization from example program RMMMBIME
*------- Write session record -
CLEAR BGR00.
BGR00-STYPE = MAPPENSATZ.
BGR00-GROUP = PARMS-MAPPE.
BGR00-NODATA = C_NODATA.
BGR00-MANDT = SY-MANDT.
BGR00-USNAM = SY-UNAME.
BGR00-START = BGR00-NODATA.
BGR00-XKEEP = BGR00-NODATA.
PERFORM 2000_WRITE_OUTPUT USING BGR00.
*----- Initialize structures -
NODATA = BGR00-NODATA.
PERFORM INIT_STRUKTUREN_ERZEUGEN(RMMMBIMI) USING NODATA.
End of standard SAP initialization from example program RMMMBIME
ENDFORM.
*eject.
      FORM 3000_START_DI_JOB                                        *
      Start direct input job                                        *
FORM 3000_START_DI_JOB.
ZTEXT = 'Starting '(021).
ZTEXT+9 = TBICU-JOBNAME.
PERFORM 4000_PROGRESS_INDICATOR USING ZTEXT.
CALL FUNCTION 'BI_START_JOB'
       EXPORTING
            JOBID                 = ' '
            JOBTEXT               = TBICU-JOBNAME
            REPNAME               = TBICU-REPNAME
            SERVER                = TBICU-EXECSERVER
            VARIANT               = TBICU-VARIANT
            NEW_JOB               = 'X'
            CONTINUE_JOB          = ' '
            START_IMMEDIATE       = 'X'
            DO_NOT_PRINT          = 'X'
            USERNAME              = SY-UNAME
       IMPORTING
            JOBID                 = ZJOBID
            JOBCOUNT              = ZJOBCOUNT
       EXCEPTIONS
            JOB_OPEN_FAILED       = 1
            JOB_CLOSE_FAILED      = 2
            JOB_SUBMIT_FAILED     = 3
            WRONG_PARAMETERS      = 4
            JOB_DOES_NOT_EXIST    = 5
            WRONG_STARTTIME_GIVEN = 6
            JOB_NOT_RELEASED      = 7
            WRONG_VARIANT         = 8
            NO_AUTHORITY          = 9
            DIALOG_CANCELLED      = 10
            JOB_ALREADY_EXISTS    = 11
            PERIODIC_NOT_ALLOWED = 12
            ERROR_NUMBER_GET_NEXT = 13
            OTHERS                = 14.
IF SY-SUBRC EQ 0.
    WRITE: / 'Direct input job'(022), TBICU-JOBNAME, 'started'.
ELSE.
    WRITE: / 'Direct input failed with return code'(023), SY-SUBRC.
ENDIF.
FORM 0020_DS_NAME.
CALL FUNCTION 'FILE_GET_NAME'
       EXPORTING
            CLIENT           = SY-MANDT
            LOGICAL_FILENAME = PARMS-LDS_NAME
            OPERATING_SYSTEM = SY-OPSYS
       IMPORTING
            FILE_NAME        = PARMS-DS_NAME
       EXCEPTIONS
            FILE_NOT_FOUND   = 1
            OTHERS           = 2.
IF SY-SUBRC NE 0.
    MESSAGE E002 WITH PARMS-LDS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
      FORM 0030_OPEN_FILE                                           *
      Open physical file for output                                 *
FORM 0030_OPEN_FILE.
OPEN DATASET PARMS-DS_NAME FOR OUTPUT IN TEXT MODE. "thg191105
OPEN DATASET PARMS-DS_NAME FOR OUTPUT IN TEXT MODE
                                 encoding default. "thg191105
IF SY-SUBRC NE 0.
    MESSAGE E003 WITH PARMS-DS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
      FORM 1000_GET_SOURCE_DATA                                     *
      Read source data into internal table                          *
--> INP_DATA   " Name of internal table passed as parameter       *
FORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
CALL FUNCTION 'Z_FILE_UPLOAD'
       EXPORTING
            UNIX                = PARMS-UNIX
            PC                  = PARMS-PC
            FILETYPE            = PARMS-DS_TYP
            FILENAME            = PARMS-PATH
            HDR_LINES           = PARMS-HDR_LINES
       TABLES
            DATA_TAB            = INP_DATA
       EXCEPTIONS
            CONVERSION_ERROR    = 1
            FILE_OPEN_ERROR     = 2
            FILE_READ_ERROR     = 3
            INVALID_TABLE_WIDTH = 4
            INVALID_TYPE        = 5
            NO_BATCH            = 6
            UNKNOWN_ERROR       = 7
            INVALID_SOURCE      = 8
            OTHERS              = 9.
ENDFORM.
*eject
      FORM 2000_WRITE_OUTPUT                                        *
      Write record in standard SAP structure to UNIX file           *
--> I_STRUCT   " Name of record passed as parameter               *
*FORM 2000_WRITE_OUTPUT USING I_STRUCT."SRY28NOV05
FORM 2000_WRITE_OUTPUT USING I_STRUCT TYPE ANY.      "SRY28NOV05
   TRANSFER I_STRUCT TO PARMS-DS_NAME.
IF SY-SUBRC NE 0.
    MESSAGE E004 WITH PARMS-DS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
*&      Form 2100_WS_DOWNLOAD
      text                                                           *
--> p1        text
<-- p2        text
FORM 2100_WS_DOWNLOAD TABLES INP_DATA.
DATA: FILENAME LIKE RLGRAP-FILENAME.   "SRY28NOV05
DATA: W_FILENAME TYPE STRING.             "SRY28NOV05
DATA: W_FTYP(10) TYPE C VALUE 'DAT'.      "SRY28NOV05
MOVE PARMS-DS_NAME TO FILENAME.       "SRY28NOV05
MOVE PARMS-DS_NAME TO W_FILENAME.      "SRY28NOV05
*BEGIN OF BLOCK COMMENT BY SRY28NOV05
CALL FUNCTION 'WS_DOWNLOAD'
      EXPORTING
        BIN_FILESIZE        = ' '
        CODEPAGE            = ' '
           FILENAME            = FILENAME
           FILETYPE            = 'DAT'
        MODE                = ' '
        WK1_N_FORMAT        = ' '
        WK1_N_SIZE          = ' '
        WK1_T_FORMAT        = ' '
        WK1_T_SIZE          = ' '
        COL_SELECT          = ' '
        COL_SELECTMASK      = ' '
   importing
        filelength          =
      TABLES
           DATA_TAB            = INP_DATA
        FIELDNAMES          =
      EXCEPTIONS
           FILE_OPEN_ERROR     = 1
           FILE_WRITE_ERROR    = 2
           INVALID_FILESIZE    = 3
           INVALID_TABLE_WIDTH = 4
           INVALID_TYPE        = 5
           NO_BATCH            = 6
           UNKNOWN_ERROR       = 7
           OTHERS              = 8.
*END OF BLOCK COMMENT BY SRY28NOV05
*BEGIN OF BLOCK ADDED BY SRY28NOV05
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME                        = W_FILENAME
      FILETYPE                        = W_FTYP
    TABLES
      DATA_TAB                        = INP_DATA
   EXCEPTIONS
     FILE_WRITE_ERROR                = 1
     NO_BATCH                        = 2
     GUI_REFUSE_FILETRANSFER         = 3
     INVALID_TYPE                    = 4
     NO_AUTHORITY                    = 5
     UNKNOWN_ERROR                   = 6
     HEADER_NOT_ALLOWED              = 7
     SEPARATOR_NOT_ALLOWED           = 8
     FILESIZE_NOT_ALLOWED            = 9
     HEADER_TOO_LONG                 = 10
     DP_ERROR_CREATE                 = 11
     DP_ERROR_SEND                   = 12
     DP_ERROR_WRITE                  = 13
     UNKNOWN_DP_ERROR                = 14
     ACCESS_DENIED                   = 15
     DP_OUT_OF_MEMORY                = 16
     DISK_FULL                       = 17
     DP_TIMEOUT                      = 18
     FILE_NOT_FOUND                  = 19
     DATAPROVIDER_EXCEPTION          = 20
     CONTROL_FLUSH_ERROR             = 21
     OTHERS                          = 22.
IF SY-SUBRC NE 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*END OF BLOCK ADDED BY SRY28NOV05
ENDFORM.                               " 2100_WS_DOWNLOAD
*eject
      FORM 4000_PROGRESS_INDICATOR                                  *
      Write progress text to status bar                             *
--> TEXT   " Text passed as parameter                             *
FORM 4000_PROGRESS_INDICATOR USING TEXT.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
       EXPORTING
            PERCENTAGE = 0
            TEXT       = TEXT
       EXCEPTIONS
            OTHERS     = 1.
ENDFORM.
*eject.
      FORM 9000_END_OF_JOB                                          *
      Close files on UNIX                                           *
FORM 9000_END_OF_JOB.
CLOSE DATASET PARMS-DS_NAME.
ENDFORM.
FORM 1000_GET_SOURCE_DATA TABLES INP_DATA.
CALL FUNCTION 'Z_FILE_UPLOAD'
       EXPORTING
            UNIX                = PARMS-UNIX
            PC                  = PARMS-PC
            FILETYPE            = PARMS-DS_TYP
            FILENAME            = PARMS-PATH
            HDR_LINES           = PARMS-HDR_LINES
       TABLES
            DATA_TAB            = INP_DATA
       EXCEPTIONS
            CONVERSION_ERROR    = 1
            FILE_OPEN_ERROR     = 2
            FILE_READ_ERROR     = 3
            INVALID_TABLE_WIDTH = 4
            INVALID_TYPE        = 5
            NO_BATCH            = 6
            UNKNOWN_ERROR       = 7
            INVALID_SOURCE      = 8
            OTHERS              = 9.
ENDFORM.
*eject
      FORM 2000_WRITE_OUTPUT                                        *
      Write record in standard SAP structure to UNIX file           *
--> I_STRUCT   " Name of record passed as parameter               *
*FORM 2000_WRITE_OUTPUT USING I_STRUCT."SRY28NOV05
FORM 2000_WRITE_OUTPUT USING I_STRUCT TYPE ANY.      "SRY28NOV05
   TRANSFER I_STRUCT TO PARMS-DS_NAME.
IF SY-SUBRC NE 0.
    MESSAGE E004 WITH PARMS-DS_NAME.
    MESSAGE A099.
ENDIF.
ENDFORM.
*eject
*&      Form 2100_WS_DOWNLOAD
      text                                                           *
--> p1        text
<-- p2        text
FORM 2100_WS_DOWNLOAD TABLES INP_DATA.

Hi,
Thnaks for your reply, This is my requirement.
Here my problem is i am trying to upload the data from flatfile which contain materil number, denominator, Actual UOM, Nominator field values.
Which is the data i need to upload into MM02 and MM01, if material number is new then it has to create the material, if material is already existing it has to update the UOM values.
here i am getting data into my internal table INP_DATA, from that i am trying to upload the data to database by using job name MRP_MATERIAL_MASTER_DATA_UPLOAD with direct input program RMDATIND.
when i execute my program i am getting success message all the records writtin from flatfile to application server. and job started message.
then if i go into sm37 screen there i execute the job it is also giving active message. if i refresh it it is showing job completed message.
then i look at job log status. there i found that for existing material it is expecting material type, for new material it is giving some gravity error.
So could u help me in this it will be gr8.
Thanks & Regards,
RamNV

Problem using Midi input

Hello,
I'm using java.sound to get MIDI messages from a "physical" midi input.
I get a rather strange behaviour, since some time, the "Midi input" get stuck, and I don't get message from the input.
To be clearer: everything works as intended : I open the device, I get incoming messages... and sometimes, the incoming messages are "lost". If I try to close the corresponding MIDI device, my program freeze... No exception are raised, my program is not CPU consumming, and I'm not able to determine the conditions that leads to this behaviour.
I'm using the last JRE under windows (XP).
I tried the MidiInDump example from jsressource, and I get a similar behaviour.
My problem now is that I don't know what to do to find out the problem. Is there a way to diagnose this kind of problem?
The MIDI interface I use is a "generic" one, that is, it used the standard MIDI driver from windows (no proprietary driver installed)...
Is there a way to size the incoming MIDI buffer?
Any clue?
Any suggestion to track the problem would be grealty appreciated.

Holly,
Have you opened the Audio MIDI Setup app on your mac? It's found in your Launchpad app (on your doc) and Other folder it should be in there. Make sure your MIDI keyboard is recognized and configured for the mac. Also look at your MIDI settings within Logic as well.

Problem with sound input/output settings

Hello--
Last night, my iBook suddenly stopped playing any sounds at all: itunes, CDs, etc, won't play at all. I looked in system preferences/sound, and the computer told me that there are no input or output devices at all. What's more, the sound seems to me on permanent mute, and it won't allow me to change it at all (F4 and F5 functions just show a "mute" sign under the volume bar). Is this a problem with the software, hardware, or what? Thanks in advance for any advice,
JB Coleman

here is a set of weird but probable solutions. Good luck
Solutions

Problem with increasing input field length in module pool programming.

Hi All,
I have created a screen in which i have used table control wizard. In my table control I have an input field. The problem is, this input filed only takes 23 inputs at a time. I need to make this field unfixed. This is an quantity field. I am not understanding why this is happening. Can anybody plz help me in this regard ?
Thanks in advance.
Tripod.

HI Tripod ,
YOu can add Lines to Table control .
Add one button by name ADD LINES : give func code 'ADD'
IN PBO ...
if it_mat[] is not initial .
    describe table it_mat lines ln .
    tab_ctrl-lines = ln .
endif.
case sy-ucomm .
when 'ADD' .
      perform add_lines .
endcase .
form add_lines .
ln = ln + 1 .
clear it_mat .
append initial line to it_mat .
endform .
regards
deepak.

Track audio record , problem with inline input

Hi Forum !
I have a Macbookpro with leopard
I am using logic pro 8
I cannot record my arrangement, with the input line.
Garage band does the same thing.
My sound in the preference is set for input line (not microphone input).
I can only record with the incorporated microphone.
any ideas ?
Thanks
Jules

noeqplease wrote:
No, you can do it, it just takes a little RTFM... that's all...
julesguertin wrote:
I guess I have misinterpret my user manual (French version)
I should had take a English version , the translation is not very good...
You wouldn't say that noeqplease if you had to deal with the French manual like our friend jules here (and myself for that matter) The French manual is a total joke. It was obviously translated by someone who hasn't the first notion of anything vaguely musical or DAW or sequencer or mixing, or of musical equipment of any kind ! Example : Channel strip translates to "Éléments des bandes de canaux" which, if translated back into English becomes "Elements of bands of canals" - and the whole manual is of the same ilk !!! I kind of wonder if the translations weren't done in an automatic translation programme I don't know if other languages suffer from the same "rubbish" translation - it could be subject of an amusing thread here "Silly excerpts from Logic Pro Manuals" or something

Problem with step input using MIDI Keyboard

Hi,
I'm new to Logic Pro X and wanted to know how I can use my MIDI keyboard as a source of Step Input Recording.
I created a new software instrument track, then open Window - > Show step input keyboard.
If I click the keyboard on the screen, it records notes with no problem. However, if I play my MIDI keyboard while on-screen keyboard is shown, it does not record anything even though I hear the sound I played.
Is there anything I can do about this?
Thanks!
-Holly
EDIT : Actually I could solve the problem. I needed to click "MIDI IN" button on "MIDI Region" window.

Holly,
Have you opened the Audio MIDI Setup app on your mac? It's found in your Launchpad app (on your doc) and Other folder it should be in there. Make sure your MIDI keyboard is recognized and configured for the mac. Also look at your MIDI settings within Logic as well.

Score staff problems with keyboard input

Hi. I am trying to input midi keyboard notes, in real time, into Logic Pro. This works fine. However, I'd also like to create a reasonable, normal score from those notes. The problem is that the notes are divided between the bass and treble clefs. This isn't at all readable when, for example, a chord played with the right hand is say, an A minor chord with the C note being middle C. The 3 notes should all appear in the treble clef.
When I try to move the note from the bass clef to the treble clef, I get messages that I need poly voicing and when I follow the help files to add another voice, I get a new clef. The only way I've been able to figure out how to do this is to record the left hand and right hand parts in different tracks, separately, which is quite cumbersome.
This ought to be easy! What am I missing?

i have to say i have created extremely complex and sophisticated concert music scores using logic. it can be done despite a myriad of problems and bugs. it's great advantage is flexibility and speed, there is nothing wrong with what it should be able to do, it just trips you up at the very last hurdle - hugely frustrating because it gets you there well ahead of the game.
i can tell you through the grapevine that improvements and upgrading are on the way for the score editor. it is very useful to have the likes of all the people on this thread posting because score users are under represented on the forum. logic developers don't realize how many of its users depend on its score features, because most of us don't post.
now some important tips:
- you can set a default score style in the arrange window in the paramters box when you click on a midi instrument track. that means whenever you create a midi region it will be in that score style.
- being able to select score styles for different regions is a good thing!!!! this way you can speed up your work flow incredibly - way way faster than sibelius or finale.
Rests have to be written instead of automatically appearing.
rubbish! you can set the rests to appear automatically. use differing score styles.
I wanted to say that I am hugely disappointed with apple's neglect of the score windo
now there i am with you brother.
if you want to see what can be achieved using score in logic, even in the state it's in you can have a look at a sample of my violin concerto i have at my website:
http://www.stevenson.homechoice.co.uk/pdfscores/devil.pdf

Anybody have problems with midi and XP? (especially anybody using a GI-20)

Hi
I'm trying to use my midi device (a Roland GI-20) with boot camp/XP but with no success.
I have downloaded XP drivers from Roland but XP won't let me install them, saying they are no better than the default drivers already installed.
It appears as a device (but XP renames it as a USB sound device and not GI-20) but when I select it in a DAW for example and generate midi nothing gets through.
ANybody else had similar problems?

Korg Legacy and the XV are not critical to my workflow, just items I had invested on I would like to keep. I did not research compatibility with Snow Leopard vwery thoroughly for those two, but I certainly did with the interface, which IS critical. Focusrite has released brand-new drivers that are supposed to be compatible with Snow Leopard, as they loudly trumpet on their web site.
And by and large, they do work - there's just that incessant noise. And THAT's an issue, and somehow I doubt it has to do with the interface as, like I mentioned, the noise only appears during the bootup sequence when, I assume, the Firewire drivers are loaded.
Inputs?

Problem with midi input in Mainstage

Similar Messages

Maybe you are looking for